GNOME Bugzilla – Bug 695283
Can't boot Fedora 18 GNOME desktop live cd
Last modified: 2016-03-31 13:22:07 UTC
1. Downloading Fedora 18 GNOME desktop live cd iso 2. Opening GNOME Boxes 3. Creating new virtual machine with iso 4. Launching it Expected results: GNOME Shell loads normally Results I got: Message with sad computer icon "Oh, no! Something has gone wrong."
I'll try to reproduce locally. In the meantime, could you provide this info: 1. Exact version of Boxes. 3.6.3? 2. Host RAM size 3. Output of 'virsh capabilities'.
1. Yes 2. 4 GB (3935092 in top) 3. Output here: <capabilities> <host> <uuid>a261f10c-a774-3cf0-b774-41917b587fa3</uuid> <cpu> <arch>x86_64</arch> <model>Nehalem</model> <vendor>Intel</vendor> <topology sockets='1' cores='2' threads='2'/> <feature name='rdtscp'/> <feature name='avx'/> <feature name='osxsave'/> <feature name='xsave'/> <feature name='tsc-deadline'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pclmuldq'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> <power_management> <suspend_mem/> <suspend_disk/> <suspend_hybrid/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> <topology> <cells num='1'> <cell id='0'> <cpus num='4'> <cpu id='0'/> <cpu id='1'/> <cpu id='2'/> <cpu id='3'/> </cpus> </cell> </cells> </topology> <secmodel> <model>selinux</model> <doi>0</doi> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-i386</emulator> <machine>pc-1.2</machine> <machine>none</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine>pc-1.2</machine> <machine>none</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <pae/> <nonpae/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine>pc-1.2</machine> <machine>none</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine>pc-1.2</machine> <machine>none</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='arm'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-arm</emulator> <machine>integratorcp</machine> <machine>none</machine> <machine>collie</machine> <machine>nuri</machine> <machine>smdkc210</machine> <machine>connex</machine> <machine>verdex</machine> <machine>highbank</machine> <machine>kzm</machine> <machine>mainstone</machine> <machine>musicpal</machine> <machine>n800</machine> <machine>n810</machine> <machine>sx1</machine> <machine>sx1-v1</machine> <machine>cheetah</machine> <machine>realview-eb</machine> <machine>realview-eb-mpcore</machine> <machine>realview-pb-a8</machine> <machine>realview-pbx-a9</machine> <machine>akita</machine> <machine>spitz</machine> <machine>borzoi</machine> <machine>terrier</machine> <machine>lm3s811evb</machine> <machine>lm3s6965evb</machine> <machine>tosa</machine> <machine>versatilepb</machine> <machine>versatileab</machine> <machine>vexpress-a9</machine> <machine>vexpress-a15</machine> <machine>xilinx-zynq-a9</machine> <machine>z2</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-arm</emulator> </domain> </arch> <features> <deviceboot/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='microblaze'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-microblaze</emulator> <machine>petalogix-s3adsp1800</machine> <machine>none</machine> <machine>petalogix-ml605</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-microblaze</emulator> </domain> </arch> </guest> <guest> <os_type>hvm</os_type> <arch name='microblazeel'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-microblazeel</emulator> <machine>petalogix-s3adsp1800</machine> <machine>none</machine> <machine>petalogix-ml605</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-microblazeel</emulator> </domain> </arch> </guest> <guest> <os_type>hvm</os_type> <arch name='mips'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-mips</emulator> <machine>malta</machine> <machine>none</machine> <machine>magnum</machine> <machine>pica61</machine> <machine>mipssim</machine> <machine>mips</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-mips</emulator> </domain> </arch> <features> <deviceboot/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='mipsel'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-mipsel</emulator> <machine>malta</machine> <machine>none</machine> <machine>magnum</machine> <machine>pica61</machine> <machine>mipssim</machine> <machine>mips</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-mipsel</emulator> </domain> </arch> <features> <deviceboot/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='sparc'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-sparc</emulator> <machine>SS-5</machine> <machine>none</machine> <machine>leon3_generic</machine> <machine>SS-10</machine> <machine>SS-600MP</machine> <machine>SS-20</machine> <machine>Voyager</machine> <machine>LX</machine> <machine>SS-4</machine> <machine>SPARCClassic</machine> <machine>SPARCbook</machine> <machine>SS-1000</machine> <machine>SS-2000</machine> <machine>SS-2</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-sparc</emulator> </domain> </arch> </guest> <guest> <os_type>hvm</os_type> <arch name='ppc'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-ppc</emulator> <machine>g3beige</machine> <machine>none</machine> <machine>ref405ep</machine> <machine>taihu</machine> <machine>bamboo</machine> <machine>mac99</machine> <machine>prep</machine> <machine>virtex-ml507</machine> <machine>ppce500</machine> <machine>mpc8544ds</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-ppc</emulator> </domain> </arch> <features> <deviceboot/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='ppc64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-ppc64</emulator> <machine>mac99</machine> <machine>none</machine> <machine>ref405ep</machine> <machine>taihu</machine> <machine>bamboo</machine> <machine>g3beige</machine> <machine>prep</machine> <machine>pseries</machine> <machine>virtex-ml507</machine> <machine>ppce500</machine> <machine>mpc8544ds</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-ppc64</emulator> </domain> </arch> <features> <cpuselection/> <deviceboot/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='s390x'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-s390x</emulator> <machine>s390-virtio</machine> <machine>none</machine> <machine canonical='s390-virtio'>s390</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-s390x</emulator> </domain> </arch> </guest> </capabilities>
Thanks for providing that info. That looks pretty normal. I assume you tried 64-bit ISO? I just tried to reproduce with git master here but it worked just fine. I'll now try with 3.6.3. Judging from symptoms only and past experience, its *likely* that bug is in Qemu so I'd recommend ensuring you are using latest Qemu packages available in F18 repo.
I just tried with 3.6.3 and was able to boot smoothly into gnome-shell from a 64-bit F18 live ISO. I presumed the host is Fedora as well. Is it? Which qemu version is this? 1.2.2 here.
1. I tried both 64-bit (first stable release) and 32-bit iso (respin); 2. 'rpm -q qemu' gives me qemu-1.2.2-6.fc18.x86_64 3. Boxes is 3.6.3 I just tried it again just to be sure. Maybe interesting detail is that Fedora in VM tries to launch GS for some 3 mins and only after that gives that error message.
(In reply to comment #5) > 1. I tried both 64-bit (first stable release) and 32-bit iso (respin); > 2. 'rpm -q qemu' gives me qemu-1.2.2-6.fc18.x86_64 > 3. Boxes is 3.6.3 Thanks. > I just tried it again just to be sure. Maybe interesting detail is that Fedora > in VM tries to launch GS for some 3 mins and only after that gives that error > message. Hm.. still doesn't say whats going wrong. Since I failed to reproduce this, if you could try launching the qemu commandline manually, that would be nice: /usr/bin/qemu-kvm -name fedora18 -M pc-1.2 -cpu Westmere,+rdtscp,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 1152 -smp 4,sockets=1,cores=2,threads=2 -rtc base=utc,driftfix=slew -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -cdrom ~/Downloads/Fedora-18-x86_64-Live-Desktop.iso -chardev pty,id=charserial0 -device usb-tablet,id=input0 -device AC97,id=sound0,bus=pci.0,addr=0x4 If this doesn't work, we could be pretty sure the issue is in qemu.
Oh, you might want to update the path to ISO in the qemu commandline :)
With given command line GNOME Shell launches, however graphics are a little bit glitchy. Boxes still gives me that error. I tried to give same amount of memory (~ 1.2 GB) to VM - still same.
(In reply to comment #8) > With given command line GNOME Shell launches, however graphics are a little bit > glitchy. Same here. > Boxes still gives me that error. I tried to give same amount of memory (~ 1.2 > GB) to VM - still same. Darn. I'm going out of clues now.
(In reply to comment #9) > (In reply to comment #8) > > With given command line GNOME Shell launches, however graphics are a little bit > > glitchy. > > Same here. > > > Boxes still gives me that error. I tried to give same amount of memory (~ 1.2 > > GB) to VM - still same. > > Darn. I'm going out of clues now. One thing that I should have asked for in the beginning: Could you paste here the console output from Boxes if you run it with: G_MESSAGES_DEBUG=Boxes gnome-boxes ?
Created attachment 239351 [details] Output of G_MESSAGES_DEBUG=Boxes gnome-boxes trying to run Fedora 18 64-bit LiveCD Here it is. Nothing exceptional though.
(In reply to comment #8) > With given command line GNOME Shell launches, however graphics are a little bit > glitchy. I had omitted spice and qxl from commandline to make testing easy. Since this could very well be a qxl issue, could you please try the same commandline with spice and qxl included? You can find the parameters to use by looking at the qemu commandline launched by Boxes. If you have trouble with that, let me know and I'll give you the complete commandline.
(In reply to comment #12) > (In reply to comment #8) > > With given command line GNOME Shell launches, however graphics are a little bit > > glitchy. > > I had omitted spice and qxl from commandline to make testing easy. Since this > could very well be a qxl issue, could you please try the same commandline with > spice and qxl included? You can find the parameters to use by looking at the > qemu commandline launched by Boxes. If you have trouble with that, let me know > and I'll give you the complete commandline. Forgot to mention that using spice would mean that you'll have to use a spice client to see the console/display. Either of spicy, spicec, remote-viewer would do. You can also use Boxes as spice-client only. :)
Another thing that struck me recently from the log: (gnome-boxes:7012): Boxes-DEBUG: fedora-installer.vala:167: Couldn't find a console layout for X layout 'lv', falling back to 'us'.. What locale are you using? (it's in LANG or LC_ALL)
Locale is LANG=lv_LV.utf8, t.i. Latvian with UTF-8
I used these instructions http://www.linux-kvm.org/page/SPICE to enable spice and with this command line: /usr/bin/qemu-kvm -name fedora18 -M pc-1.2 -cpu Westmere,+rdtscp,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 1152 -smp 4,sockets=1,cores=2,threads=2 -rtc base=utc,driftfix=slew -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -cdrom ~/Downloads/Fedora-18-x86_64-Live-Desktop.iso -chardev pty,id=charserial0 -device usb-tablet,id=input0 -device AC97,id=sound0,bus=pci.0,addr=0x4 -vga qxl -spice port=5900,addr=127.0.0.1,disable-ticketing I can connect to it using: spicec -h 127.0.0.1 -p 5900 And it does show properly loaded GNOME Shell, so qemu and spice seems fine. I don't know what command Boxes uses though, where you can see it in 3.6.3?
(In reply to comment #16) > I used these instructions http://www.linux-kvm.org/page/SPICE to enable spice > and with this command line: > > /usr/bin/qemu-kvm -name fedora18 -M pc-1.2 -cpu >.. > I can connect to it using: > > spicec -h 127.0.0.1 -p 5900 > > And it does show properly loaded GNOME Shell, so qemu and spice seems fine. Hmm.. thanks for trrying. :) > I don't know what command Boxes uses though, where you can see it in 3.6.3? When the box is running, just do `ps -ef|grep qemu`.
When running Boxes and getting that error, qemu had such command line. I removed virtual hard disk options and tried to run it with qemu-kvm and spicec. All I got was blank screen and warning "Warning: no factory for 9". /usr/bin/qemu-kvm -name fedora18 -S -M pc-1.2 -cpu Nehalem,+rdtscp,+avx,+osxsave,+xsave,+tsc-deadline,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 1152 -smp 4,sockets=1,cores=2,threads=2 -uuid e9acd27d-2ac9-b97b-3884-8d81d7a0a2f8 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/peteris/.config/libvirt/qemu/lib/fedora18.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-reboot -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/home/peteris/.local/share/gnome-boxes/images/fedora18,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/home/peteris/Fedora-18-x86_64-Live-Desktop.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:a7:48:6d,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
So I finally got it working with your help (thanks!). It seems that my system didn't like qemu -cpu flag created by Boxes. 1. I took and ran simple VM with Fedora 18 64-bit Live CD in Boxes and encountered error described above; 2. Opened Terminal, copied qemu command line issued by Boxes to text editor 3. Closed Boxes 4. Changed -cpu flag in qemu command line to -cpu Westmere,+rdtscp,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme 5. Ran it 6. Launched remote-viewer to see it working finally My system's /proc/cpuinfo is: [peteris@localhost Darbs]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz stepping : 7 microcode : 0x28 cpu MHz : 1600.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 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 eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6584.63 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz stepping : 7 microcode : 0x28 cpu MHz : 1600.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 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 eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6584.63 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz stepping : 7 microcode : 0x28 cpu MHz : 1600.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 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 eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6584.63 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz stepping : 7 microcode : 0x28 cpu MHz : 1600.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 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 eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6584.63 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
Post scriptum: for clarity, I also had to remove -S flag from qemu-kvm command line to get it running.
With several tries +avx CPU flag was isolated as one causing this bug.
libvirt version for all related packages is 0.10.2.3-1.fc18
15:14 < pecisk> one more thing - dmesg for livecd shows something like this: traps: gnome-shell[1289] trap invalid opcode ip:xxxxxxxxxxx sp:xxxxxxxxxx error:0 is what made us look at the -cpu flags. The core i3 2120 does support avx: http://ark.intel.com/products/53426/Intel-Core-i3-2120-Processor-3M-Cache-3_30-GHz
Peteris, if you are still around, could you check if /var/spool/abrt has a gnome-shell-2013-xxxx directory and attach the content of that directory?
Sorry for long delay, had exams to deal with. No, I can't find any gnome-shell-* directory within /var/spool/abrt on VM, only ccpp-2013-xxxx.
Hmm should do, can you paste the content of the backtrace file from this directory? Also, can you paste ls -l /var/spool/abrt/ccpp-2013-xxx/ ?
Created attachment 242540 [details] List of ccpp directory in /var/spool/abrt - screenshot #1
Created attachment 242541 [details] List of ccpp directory in /var/spool/abrt - screenshot #2
Created attachment 242542 [details] core_backtrace of ccpp directory in /var/spool/abrt
Sorry, couldn't find easy enough way to get traces out of VM in short time, so just snapshotted screens of ls -l and cat core_backtrace.
Would be great if you could extract the coredump file from that directory
Can anyone who can reproduce this reproduce it with a bare-metal configuration? I'm not convinced this isn't a bug in kvm's avx emulation.
https://bugzilla.redhat.com/show_bug.cgi?id=870071 could be related, and would confirm your suspicion.