Qemu/KVM Ubuntu 10.04 guest reboots itself

[Jayson Vaughn]

Binary package hint: qemu-kvm

I am running Ubuntu 10.04 as a VM Hypervisor using libvirt+Qemu+KVM.
I have a guest vm running Ubuntu 10.04.

I am having issues with the guest VM rebooting itself periodically.

Here is an excerpt from 'last(1)'

reboot system boot 2.6.32-21-generi Sat May 22 21:47 - 09:08 (1+11:20)
reboot system boot 2.6.32-21-generi Sat May 22 19:25 - 21:47 (02:22)
reboot system boot 2.6.32-21-generi Sat May 22 16:52 - 19:25 (02:33)
reboot system boot 2.6.32-21-generi Sat May 22 16:44 - 16:52 (00:07)
reboot system boot 2.6.32-21-generi Sat May 22 16:11 - 16:44 (00:32)

After turning on debug logging with libvirt, I get the follow output in /var/log/messages:

May 24 09:28:25 hv1 libvirtd: 09:28:25.059: info : networkReloadIptablesRules:815 : Reloading iptables rules
May 24 09:28:25 hv1 libvirtd: 09:28:25.062: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.065: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.069: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.071: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.075: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.077: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.081: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.084: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.088: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.091: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.095: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.097: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.101: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.104: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.107: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.110: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.113: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.116: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.119: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.122: info : qemudDispatchSignalEvent:390 : Received unexpected signal 17
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXSYSTM:00' does not have property 'DRIVER'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXSYSTM:00' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXSYSTM:00' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXSYSTM:00'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:00' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:00' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:00'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:00'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:01' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:01' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:01'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:01'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:02' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:02' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:02'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:02'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:03' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:03' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:03'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:03'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:04' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:04' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:04'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:04'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:05' does not have property 'PCI_CLASS'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:05' does not have property 'INTERFACE'
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceType:1082 : Could not determine device type for device with sysfs path 'LNXCPU:05'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevProcessDeviceListEntry:1267 : Failed to create node device for udev device '/sys/devices/LNXSYSTM:00/LNXCPU:05'#012
May 24 09:28:25 hv1 libvirtd: 09:28:25.127: info : udevGetDeviceProperty:111 : udev reports device 'LNXCPU:06' does not have property 'PCI_CLASS'

Please assist!

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: kvm (not installed)
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
Architecture: i386
Date: Mon May 24 10:11:34 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: qemu-kvm

[Scott Moser (smoser)]

Does 09:28:25 correlate with the time of reboot ?
How quickly does the reboot occur?

Also, could you please run 'apport-collect 585002', which will attach debugging information to this bug.

[Launchpad Janitor (janitor)]

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]