Red Hat Bugzilla – Bug 800405
Fedora guest's kernel crashes in runlevels 3 and 5
Last modified: 2012-11-14 11:32:50 EST
Created attachment 567942 [details]
Description of problem:
Every time I boot Fedora 32/64 guest and connect to it via spice it freezes and attached trace is printed. I tried to obtain more info with no success, installed kexec-tools, crash, kernel-debuginfo, set crashmemory as kernel parameter but nothing is written to /var/crash. I'm attaching boot.log and dmesg. It doesn't occur when I boot into single user mode and start network.
The VM is run from oVirt management with following parameters
/usr/bin/qemu-kvm -S -M pc-0.14 -cpu core2duo,+lahf_lm,-monitor,-vme -enable-kvm -m 1024 -smp 2,sockets=1,cores=2,threads=1 -name Fedora-64 -uuid f247b62f-ee9e-41c8-800f-2f7d3365d98d -smbios type=1,manufacturer=Red Hat,product=RHEV Hypervisor,version=16-1,serial=FF094200-0B8C-384C-AE3C-22802EC26045_E4:1F:13:69:C4:74,uuid=f247b62f-ee9e-41c8-800f-2f7d3365d98d -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Fedora-64.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2012-03-06T12:42:43,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive file=/rhev/data-center/7e26e5c4-f765-4388-ad75-ade0f81a7a72/a7d5095e-133e-4832-b7d8-7bd3780ea67a/images/9c3f72ef-bb5a-4b25-88b6-e62f47e964f2/81cd837f-abde-4e5d-ac6c-f3e7cc0a8efd,if=none,id=drive-virtio-disk0,format=qcow2,serial=9c3f72ef-bb5a-4b25-88b6-e62f47e964f2,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:31:3f:03,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/Fedora-64.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -usb -spice port=5900,tls-port=5901,addr=10.34.63.208,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=inputs -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Fedora guest OS from oVirt mgmt
Attached screenshot with trace. Please ask for other relevant files.
Can you boot the image, connect to it with ssh and tail messages before you connect to it with spice to see if you can find any better information?
Please create a new image on raw or qcow file backed storage and post the image for download somewhere to give any chance of meaningful debugging.
The image link you gave me tells me gives a 403 on download attempts. Fix perms perhaps?
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Still reproducible with kernel 3.3.0-8.fc16
Are you still seeing this with 3.4.9-2? If so, can you please do what Justin suggested in comment #2?
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.