Bug 702196 - the VM kills itself
Summary: the VM kills itself
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 02:51 UTC by qinguan0619
Modified: 2016-03-23 12:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 12:39:19 UTC


Attachments (Terms of Use)
dmesg information (116.50 KB, application/octet-stream)
2011-05-05 02:51 UTC, qinguan0619
no flags Details

Description qinguan0619 2011-05-05 02:51:39 UTC
Created attachment 496963 [details]
dmesg information

Description of problem:
I use the VT-d through libvirt under the linux debian6.0.1a.
when I create a VM by "virsh create ubuntu.xml",it shows that:
root@shahe26:~# virsh create ubuntu.xml 
Domain ubuntu created from ubuntu.xml

root@shahe26:~# virsh list
 Id Name                 State
----------------------------------
  8 ubuntu               running

root@shahe26:~# virsh list
 Id Name                 State
----------------------------------
  8 ubuntu               running

root@shahe26:~# virsh list
 Id Name                 State
----------------------------------

root@shahe26:~# 
the VM kills itself.

root@shahe26:~# cat ubuntu.xml 
<domain type='kvm'>
	<name>ubuntu</name>
	<description>just test using sriov!</description>
	<os>
		<type>hvm</type>
		<boot dev='hd'/>
	</os>

<!-->
	<cpu match='exect'>
		<model>qemu64</model>
		<feature model='13'/>
	</cpu>
</!-->
	<memory>524288</memory>
	<currentMemory>524288</currentMemory>
	<on_poweroff>destroy</on_poweroff>
	<on_reboot>restart</on_reboot>
	<on_crash>restart</on_crash>
	
	<features><pae/><acpi/><apic/></features>
	<clock offset='utc'/>
	<devices>
		<input type='mouse' bus='usb'/>		
		<disk type='file' device='disk'>
			<source file='/root/ubuntu_2.img'/>
		
			<!-->  use virtio or /'ide' in ide io </!-->
			<target dev='hda' bus='virtio'/>
		</disk>
		
		<emulator>/usr/bin/kvm</emulator>
		<graphics type='vnc' port='-1'/>
		<!-->
			VT-d or sr-iov assign a pci device just use the hostdev element!
			When managed is "yes" for a PCI device, 
			it is detached from the host before being passed on to the guest.
		</!-->
		<hostdev mode='subsystem' type='pci' managed='yes'>
			<source>
				<address bus='0x2' slot='0x0' function='0x1'/>
			</source>
		</hostdev>
		
		<!-->
		Direct attachment to physical interface.requires the Linux macvtap driver.
		<interface type='direct'>
			<source dev='eth0' mode='vepa'>
		</interface>
		</!-->
		
	</devices>
</domain>

user.log:
May  4 19:43:03 shahe26 libvirtd: 19:43:03.477: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:03 shahe26 libvirtd: 19:43:03.637: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:07 shahe26 libvirtd: 19:43:07.376: error : qemuMonitorCommandWithHandler:255 : cannot send monitor command 'info balloon': Connection reset by peer
May  4 19:43:07 shahe26 libvirtd: 19:43:07.377: error : qemuMonitorTextGetBalloonInfo:555 : operation failed: could not query memory balloon allocation
May  4 19:43:14 shahe26 libvirtd: 19:43:14.301: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:14 shahe26 libvirtd: 19:43:14.461: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed

message.log:
May  4 19:43:03 shahe26 libvirtd: 19:43:03.477: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:03 shahe26 kernel: [48352.538306] ixgbe: eth2: ixgbe_remove: complete
May  4 19:43:03 shahe26 kernel: [48352.538323] ixgbe 0000:02:00.1: PCI INT B disabled
May  4 19:43:03 shahe26 kernel: [48352.538364] pci-stub 0000:02:00.1: claimed by stub
May  4 19:43:03 shahe26 libvirtd: 19:43:03.637: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:03 shahe26 kernel: [48352.644590] pci-stub 0000:02:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
May  4 19:43:06 shahe26 kernel: [48355.867925] pci-stub 0000:02:00.1: PCI INT B disabled
May  4 19:43:07 shahe26 kernel: [48356.363862] ixgbe 0000:02:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
May  4 19:43:07 shahe26 kernel: [48356.495457] ixgbe: 0000:02:00.1: ixgbe_init_interrupt_scheme: Multiqueue Enabled: Rx Queue count = 16, Tx Queue count = 16
May  4 19:43:07 shahe26 kernel: [48356.495462] ixgbe 0000:02:00.1: (PCI Express:5.0Gb/s:Width x8) 00:a0:d1:ec:dc:49
May  4 19:43:07 shahe26 kernel: [48356.495547] ixgbe 0000:02:00.1: MAC: 2, PHY: 7, SFP+: 3, PBA No: ffffff-0ff
May  4 19:43:07 shahe26 kernel: [48356.496541] ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
May  4 19:43:14 shahe26 libvirtd: 19:43:14.301: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:14 shahe26 kernel: [48363.345922] ixgbe: eth2: ixgbe_remove: complete
May  4 19:43:14 shahe26 kernel: [48363.345939] ixgbe 0000:02:00.1: PCI INT B disabled
May  4 19:43:14 shahe26 kernel: [48363.345979] pci-stub 0000:02:00.1: claimed by stub
May  4 19:43:14 shahe26 libvirtd: 19:43:14.461: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
May  4 19:43:14 shahe26 kernel: [48363.452209] pci-stub 0000:02:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
May  4 19:43:17 shahe26 kernel: [48366.411939] pci-stub 0000:02:00.1: PCI INT B disabled
May  4 19:43:17 shahe26 kernel: [48366.903376] ixgbe 0000:02:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
May  4 19:43:18 shahe26 kernel: [48367.023530] ixgbe: 0000:02:00.1: ixgbe_init_interrupt_scheme: Multiqueue Enabled: Rx Queue count = 16, Tx Queue count = 16
May  4 19:43:18 shahe26 kernel: [48367.023535] ixgbe 0000:02:00.1: (PCI Express:5.0Gb/s:Width x8) 00:a0:d1:ec:dc:49
May  4 19:43:18 shahe26 kernel: [48367.023619] ixgbe 0000:02:00.1: MAC: 2, PHY: 7, SFP+: 3, PBA No: ffffff-0ff
May  4 19:43:18 shahe26 kernel: [48367.024619] ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection

libvirt/qemu/ubuntu.log:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name ubuntu -uuid 34d6f8f8-4308-3d14-7e1c-dfd2f1bbb431 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/ubuntu.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/root/ubuntu_2.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 -usb -device usb-mouse,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device pci-assign,host=02:00.1,id=hostdev0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to assign irq for "hostdev0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
assigned_dev_pci_read_config: pread failed, ret = 0 errno = 1

Version-Release number of selected component (if applicable):
root@shahe26:~# uname -a
Linux shahe26 2.6.32 #1 SMP Wed Apr 27 21:52:04 PDT 2011 x86_64 GNU/Linux
root@shahe26:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32 root=UUID=1c4d970f-a7fa-4c41-aaea-0e841b1cb41f ro quiet intel_iommu=on pci=assign-busses
root@shahe26:~# libvirtd --version
libvirtd (libvirt) 0.9.0
root@shahe26:~# kvm --version
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard
root@shahe26:/var/log/libvirt/qemu# lspci | grep Eth
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
02:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
root@shahe26:/var/log/libvirt/qemu# 

How reproducible:


Steps to Reproduce:
1.virsh create ubuntu.xml
2.do "virsh list " some times
  
Actual results:
VM kills itself.

Expected results:
Start VM and can enter it by virt-viewer.

Additional info:
dmesg information please look into attachment.

Comment 1 Cole Robinson 2016-03-23 12:39:19 UTC
Sorry this never received a response. PCI passthrough has changed a lot on qemu and libvirt since this was filed, so I suspect this crash no longer exists. Closing as DEFERRED

if anyone can still reproduce crashes with latest libvirt and qemu, please file a new bug


Note You need to log in before you can comment on or make changes to this bug.