On 6/6/2016 9:16 AM, Damir Chanyshev wrote:
> Hello. Are there any plans to include mdadm?
eh sure... adding it now...
I'll add it to the storage-utils bundle
--> CPU:
/proc/cpuinfo: for processor 0-4
vendor_id : GenuineIntel
cpu family : 6
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz
stepping : 5
microcode : 0x5
cpu MHz : 933.000
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi
flexpriority ept vpid
bugs :
bogomips : 3457.98
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
--> OVMF.fd:
http://www.tianocore.org/ovmf/ -> Release r15214: X64 (zip)
--> qemu (build from git source):
~/qemu/x86_64-softmmu/qemu-system-x86_64 --version
QEMU emulator version 2.6.50, Copyright (c) 2003-2008 Fabrice Bellard
unxz images:
clear-8570-kvm.img
clear-8570-live.img
--> Test:
~/qemu/x86_64-softmmu/qemu-system-x86_64 -bios ./OVMF-X64-r15214/OVMF.fd
-m 1024 -smp 2 -cpu host -vga cirrus -nographic -enable-kvm -drive
file=./clear-8570-kvm.img,if=virtio,aio=threads -vga none -net user -net
nic,model=virtio
Boot Failed. EFI DVD/CDROM
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
.
after some time i get
UEFI Interactive Shell v2.0
EDK II
UEFI v2.40 (EDK II, 0x00010000)
Mapping table
FS0: Alias(s):HD12b:;BLK4:
PciRoot(0x0)/Pci(0x3,0x0)/HD(1,GPT,1C006B6D-CC21-4105-B51F-F14338D97618,0x800,0x1F800)
BLK2: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
BLK3: Alias(s):
PciRoot(0x0)/Pci(0x3,0x0)
BLK5: Alias(s):
PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,4983B0C8-71BE-4981-865D-ECCA422E8B76,0x20000,0xA00000)
BLK0: Alias(s):
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x0)
BLK1: Alias(s):
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x1)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>
nothing more - for the live and kvm image
Am 05.06.2016 um 20:10 schrieb Douglas, William:
> On Sun, Jun 5, 2016 at 11:06 AM, Dennis Luehring <dl.soluz(a)gmx.net> wrote:
> > Am 05.06.2016 um 18:59 schrieb Douglas, William:
> >>
> >> So we currently have an open issue when running non-console modes
> >> under qemu and from your problem description it sounds like it may be
> >> impacting other virtualization run times as well. I'm not sure if
> >> vmware player or virtualbox support qemu's -nographic -vga none
> >> options to run the vm in a console but is the current work around for
> >> qemu.
> >
> > i don't known an option (in player or virtualbox) that can mimic these qemu
> > features (but maybe there are)
> > i'll check running clearlinux under qemu tomorrow - do i need to use the
> > live or kvm image?
>
> Either of those images will work.
Am 05.06.2016 um 18:59 schrieb Douglas, William:
> So we currently have an open issue when running non-console modes
> under qemu and from your problem description it sounds like it may be
> impacting other virtualization run times as well. I'm not sure if
> vmware player or virtualbox support qemu's -nographic -vga none
> options to run the vm in a console but is the current work around for
> qemu.
i don't known an option (in player or virtualbox) that can mimic these
qemu features (but maybe there are)
i'll check running clearlinux under qemu tomorrow - do i need to use the
live or kvm image?
Am 05.06.2016 um 18:59 schrieb Douglas, William:
> So we currently have an open issue when running non-console modes
> under qemu and from your problem description it sounds like it may be
> impacting other virtualization run times as well. I'm not sure if
> vmware player or virtualbox support qemu's -nographic -vga none
> options to run the vm in a console but is the current work around for
> qemu.
i've got qemu 2.6.x running
but what parameters needed (missing qemu section on the clearlinux
homepage?)
for using
https://download.clearlinux.org/releases/8570/clear/clear-8570-live.img.xz
with qemu
> On Sun, Jun 5, 2016 at 12:26 AM, Dennis Luehring <dl.soluz(a)gmx.net> wrote:
> > i've tested another System with VirtualBox/VmWare Player
> >
> > these are my specs:
> >
> > CPU-Z version 1.76.0.x64
> >
> > my Laptop:
> > Processor 1 ID = 0
> > Number of cores 4 (max 8)
> > Number of threads 8 (max 16)
> > Name Intel Core i7 740QM
> > Codename Clarksfield
> > Specification Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz
> > Package (platform ID) Socket 989 rPGA (0x4)
> > CPUID 6.E.5
> > Extended CPUID 6.1E
> > Core Stepping B1
> > Technology 45 nm
> > TDP Limit 45.0 Watts
> > Core Speed 1837.2 MHz
> > Multiplier x Bus Speed 14.0 x 131.2 MHz
> > Rated Bus speed 2099.6 MHz
> > Stock frequency 1733 MHz
> > Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T,
> > VT-x
> > L1 Data cache 4 x 32 KBytes, 8-way set associative, 64-byte line
> > size
> > L1 Instruction cache 4 x 32 KBytes, 4-way set associative, 64-byte
> > line size
> > L2 cache 4 x 256 KBytes, 8-way set associative, 64-byte line size
> > L3 cache 6 MBytes, 12-way set associative, 64-byte line size
> > FID/VID Control yes
> >
> > my Workstation:
> > Processor 1 ID = 0
> > Number of cores 4 (max 4)
> > Number of threads 4 (max 4)
> > Name Intel Core 2 Quad Q8300
> > Codename Yorkfield
> > Specification Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
> > Package (platform ID) Socket 775 LGA (0x4)
> > CPUID 6.7.A
> > Extended CPUID 6.17
> > Core Stepping R0
> > Technology 45 nm
> > TDP Limit 95.0 Watts
> > Core Speed 1994.8 MHz
> > Multiplier x Bus Speed 6.0 x 332.5 MHz
> > Rated Bus speed 1329.9 MHz
> > Stock frequency 2500 MHz
> > Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T, VT-x
> > L1 Data cache 4 x 32 KBytes, 8-way set associative, 64-byte line
> > size
> > L1 Instruction cache 4 x 32 KBytes, 8-way set associative, 64-byte
> > line size
> > L2 cache 2 x 2048 KBytes, 8-way set associative, 64-byte line
> > size
> > FID/VID Control yes
> > FID range 6.0x - 7.5x
> > Max VID 1.288 V
> >
> > both supporting SSE4.1, the i7 supports even SSE4.2
> >
> > i've recheck all settings like efi-boot, SATA 0:1 etc. but i still can't get
> > clearlinux to boot
> >
> > so SSE4.1 is not enough i think
> >
> >
> > Am 04.06.2016 um 20:33 schrieb Arjan van de Ven:
> >>
> >> On 6/3/2016 11:23 PM, Dennis Luehring wrote:
> >> > my system specs: Win7 x64 Professional, Intel Core 2 Quad CPU Q8300
> >> > @2.50Ghz, 8 GB RAM
> >>
> >> hmm that likely is too old to run Clear Linux; we're assuming a system
> >> with at least SSE4.1 (e.g. westmere) so
> >> that the compiler can use autovectorization more effectively.
> >>
> >> (every distro needs to set a bar, and once you set it, it's really not
> >> good to move it, so we tried to balance
> >> picking something not-too-recent, while also picking something with a rich
> >> enough instruction set where
> >> the compiler can really use the instructions)
> >>
> >>
> >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)lists.clearlinux.org
> > https://lists.clearlinux.org/mailman/listinfo/dev
player (12.x) and virtualbox (5.x) are up to date and i followed both
install descriptions twice (image conversion etc.)
but after VM startup nothing happens (blank screen)
my system specs: Win7 x64 Professional, Intel Core 2 Quad CPU Q8300
@2.50Ghz, 8 GB RAM
any ideas?
Hi,
I've been experimenting with a slight change in how some of our bundles are structured, and it's looking promising so far,
so time for feedback...
The basic idea is that for every bundle "foo" that we have in the OS, we auto-generate a bundle "foo-dev" which contains
1) All the OS content that was used to create what is in "foo" (e.g. the full build deps)
2) All the -dev content for the packages in foo itself (headers/.so files etc)
It's done such that if bundle "foo" includes (extends) bundle "bar", "foo-dev" would include "bar-dev"
(this is to keep sizes/updates to this managable)
There are some logistical challenges to do this for ALL the bundles we have (in terms of disk space etc)
so we may start with a smaller set of bundles to do this for.
So the question is if folks think that this is useful to have, and if there's tweaks/etc we can do to make these
even more useful... Also if there's requests to do specific bundles before others (given the logistics/diskspace issues
we need to work through).. please speak up.
