[Qemu-devel] [Bug 994378] Re: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line.
after echo 1 /sys/modules/kvm/parameters/ignore_msrs in host, the guest (with my own kernel config) boot up fine. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/994378 Title: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/994378/+subscriptions
[Qemu-devel] [Bug 1207623] [NEW] 64bit RHEL6.4 guest crashes and reboots continuously
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git next Commit:9576c4cd6b6fa5716400e63618757b76cff6a813 qemu-kvm uq/master Commit:0779caeb1a17f4d3ed14e2925b36ba09b084fb7b Host Kernel Version:3.11.0-rc1 Hardware: SandyBridge-EP Bug detailed description: -- RHEL6.4 guest alwasy crashes and reboots. 32bit RHEL6.4 and 64bit RHEL6.3 guest can work fine. kvm next + qemu-kvm uq/master = result 9576c4cd + 0779caeb = bad 9576c4cd + c3cb8e77 = good seems the following commit is the culprit commit. commit 0779caeb1a17f4d3ed14e2925b36ba09b084fb7b Author: Arthur Chunqi Li yzt...@gmail.com Date: Sun Jul 7 23:13:37 2013 +0800 Initialize IA32_FEATURE_CONTROL MSR in reset and migration The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs to clear this MSR when reset vCPU and keep the value of it when migration. This patch add this feature. Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow Current result: guest reboot continuously Expected result: guest boot up fine Basic root-causing log: -- (guest serial port log is attached.) ** Affects: qemu-kvm Importance: Undecided Status: New ** Project changed: qemu = qemu-kvm -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1207623 Title: 64bit RHEL6.4 guest crashes and reboots continuously Status in qemu-kvm: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git next Commit:9576c4cd6b6fa5716400e63618757b76cff6a813 qemu-kvm uq/master Commit:0779caeb1a17f4d3ed14e2925b36ba09b084fb7b Host Kernel Version:3.11.0-rc1 Hardware: SandyBridge-EP Bug detailed description: -- RHEL6.4 guest alwasy crashes and reboots. 32bit RHEL6.4 and 64bit RHEL6.3 guest can work fine. kvm next + qemu-kvm uq/master = result 9576c4cd + 0779caeb = bad 9576c4cd + c3cb8e77 = good seems the following commit is the culprit commit. commit 0779caeb1a17f4d3ed14e2925b36ba09b084fb7b Author: Arthur Chunqi Li yzt...@gmail.com Date: Sun Jul 7 23:13:37 2013 +0800 Initialize IA32_FEATURE_CONTROL MSR in reset and migration The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs to clear this MSR when reset vCPU and keep the value of it when migration. This patch add this feature. Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow Current result: guest reboot continuously Expected result: guest boot up fine Basic root-causing log: -- (guest serial port log is attached.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-kvm/+bug/1207623/+subscriptions
[Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC assigned
Re-tested this bug with: kvm.git(next tree):e47a5f5fb715b90b40747e9e235de557c6abd56c qemu-kvm.git(uq/master tree): 199472259a41677417fb7de168bd8c589383c6de This bug has been fixed. ** Changed in: qemu Status: New = Fix Committed ** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1182716 Title: guest cannot boot up when Intel 82572 NIC assigned Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions
[Qemu-devel] [Bug 1185228] [NEW] with 'monitor pty', it needs to flush pts device after sending command to it
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit: 660696d1d16a71e15549ce1bf74953be1592bcd3 qemu.git Commit: 64afc2b4d48fb21e085517c38a59a3f61a11283c Host Kernel Version:3.9.0-rc3 Hardware: SandyBridge Bug detailed description: -- when creating guest with parameter -monitor pty, then send command (e.g. migrate, device_add) to the pts device. If I don't flush the pts device (e.g. using cat /dev/pts/8) to flush the pts device, the monitor command doesn't take effect. I know some old qemu (e.g. 1.3) didn't have this issue. create KVM guest: [root@vt-snb9 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/cathy/rhel6u4.qcow -monitor pty char device redirected to /dev/pts/8 (label compat_monitor0) VNC server running on `::1:5900' hot plug a PCI device: [root@vt-snb9 ~]# echo device_add pci-assign,host=05:10.0,id=nic /dev/pts/8 (here, the device cannot hot plug to the guest.) if you run command cat /dev/pts/8, the device will hot plug to the guest. hot remove the device: [root@vt-snb9 ~]# echo device_del nic/dev/pts/8 (here, the device cannot hot remove from the guest.) if you run command cat /dev/pts/8 the device can hot remove from the guest Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/cathy/rhel6u4.qcow -monitor pty 2. echo device_add pci-assign,host=05:10.0,id=nic /dev/pts/8 (or using 'migrate' command in qemu monitor redirection device /dev/pts/8 ) Current result: device can not hot plug or hot remove from the guest before exec 'cat /dev/pts/8'. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1185228 Title: with 'monitor pty', it needs to flush pts device after sending command to it Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit: 660696d1d16a71e15549ce1bf74953be1592bcd3 qemu.git Commit: 64afc2b4d48fb21e085517c38a59a3f61a11283c Host Kernel Version:3.9.0-rc3 Hardware: SandyBridge Bug detailed description: -- when creating guest with parameter -monitor pty, then send command (e.g. migrate, device_add) to the pts device. If I don't flush the pts device (e.g. using cat /dev/pts/8) to flush the pts device, the monitor command doesn't take effect. I know some old qemu (e.g. 1.3) didn't have this issue. create KVM guest: [root@vt-snb9 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/cathy/rhel6u4.qcow -monitor pty char device redirected to /dev/pts/8 (label compat_monitor0) VNC server running on `::1:5900' hot plug a PCI device: [root@vt-snb9 ~]# echo device_add pci-assign,host=05:10.0,id=nic /dev/pts/8 (here, the device cannot hot plug to the guest.) if you run command cat /dev/pts/8, the device will hot plug to the guest. hot remove the device: [root@vt-snb9 ~]# echo device_del nic/dev/pts/8 (here, the device cannot hot remove from the guest.) if you run command cat /dev/pts/8 the device can hot remove from the guest Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/cathy/rhel6u4.qcow -monitor pty 2. echo device_add pci-assign,host=05:10.0,id=nic /dev/pts/8 (or using 'migrate' command in qemu monitor redirection device /dev/pts/8 ) Current result: device can not hot plug or hot remove from the guest before exec 'cat /dev/pts/8'. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1185228/+subscriptions
[Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC assigned
** Attachment added: lspci-in-host https://bugs.launchpad.net/qemu/+bug/1182716/+attachment/3683492/+files/lspci.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1182716 Title: guest cannot boot up when Intel 82572 NIC assigned Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions
[Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC assigned
** Attachment added: dmesg-in-host https://bugs.launchpad.net/qemu/+bug/1182716/+attachment/3683493/+files/host-dmesg.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1182716 Title: guest cannot boot up when Intel 82572 NIC assigned Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions
[Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC assigned
the output of 'dmesg' and 'lspci' command in host is attached as above. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1182716 Title: guest cannot boot up when Intel 82572 NIC assigned Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions
[Qemu-devel] [Bug 1182716] [NEW] guest cannot boot up when Intel 82572 NIC assigned
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1182716 Title: guest cannot boot up when Intel 82572 NIC assigned Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3 qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec Host Kernel Version:3.9.0-rc3 Hardware: IvyBridge-EP Bug detailed description: -- When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will get Invalid ROM contents error and the guest cannot boot up. This should be a qemu-kvm bug. kvm + qemu-kvm = result 660696d1 + 9953f882 = bad 660696d1 + 5098699a = good note: 1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb driver), the PF works fine in guest. 2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 82599, the VF works fine in guest. Reproduce steps: 1. start up a host with kvm (commit: 660696d1) 2. ./pcistub.sh -h 07:00.0 ( to hide a device) 3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none rhel6u4.img Current result: the guest cannot boot up. [root@vt-ivt2 ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device pci-assign,host=07:00.0 -net none /root/rhel6u4.img qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read from host /sys/bus/pci/devices/:07:00.0/rom Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Segmentation fault (core dumped) Expected result: the guest can boot up, and the device works fine in guest. Basic root-causing log: (some log in 'dmesg') -- assign device 0:7:0.0 pci-stub :07:00.0: Invalid ROM contents qemu-system-x86[6977]: segfault at 7f59afb8 ip 7f59fe9f46ec sp 7fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions
[Qemu-devel] [Bug 1096814] [NEW] Guest hang when doing kernel build and writing date in guest
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:e11ae1a102b46f76441e328a2743ae5d6e201423
qemu-kvm Commit:4d9367b76f71c6d938cf8201392abe4bfb1136cb
Host Kernel Version:3.7.0
Hardware:Romley-EP, WSM-EP
Bug detailed description:
--
When writing date to remote filesystem (e.g. NFS) and compiling kernel in a
guest, the guest will hang occasionally.
This can't be reproduced every time.
Reproduce steps:
1. star a guest: qemu-system-x86_64 -m 4096 -smp 4 -drive
file=rhel6u3-b.img,if=virtio -net nic,macaddr=00:16:13:52:24:11 -net tap
2. in guest: mount my-nfs:/temp /mnt
3. do kernel build and write some data in /mnt dir
Current result:
host serial port will print “call trace”message
Expected result:
Guest work fine.
Basic root-causing log:
--
(some log in the host side)
INFO: rcu_sched self-detected stall on CPU { 7} (t=21000 jiffies g=6506 c=6505
q=803)
sending NMI to all CPUs:
NMI backtrace for cpu 7
CPU 7
Pid: 10664, comm: qemu-system-x86 Tainted: P 3.7.0 #2 Intel
Corporation S2600CP/S2600CP
RIP: 0010:[8121d28b] [8121d28b] find_next_bit+0x3f/0x9d
RSP: 0018:88043f6e3ce8 EFLAGS: 0006
RAX: ff00fe00 RBX: 88083f20cdd0 RCX: 0009
RDX: 0009 RSI: 00ff RDI: 00ff
RBP: 88043f6e3ce8 R08: R09: 88043f6ecdf0
R10: 0004 R11: R12: 88043f6ecdf0
R13: cdc0 R14: cdd0 R15: 0002
FS: 7fda02753700() GS:88043f6e() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0031db8df760 CR3: 00042c82d000 CR4: 000427e0
DR0: DR1: DR2:
DR3: DR6: 0ff0 DR7: 0400
Process qemu-system-x86 (pid: 10664, threadinfo 88042b31, task
880424d03800)
Stack:
88043f6e3d08 81210366 88043f6ecdf0 0008
88043f6e3d78 81022a57 88043f6e3f48 7fff00020001
0007 0008813fe374 88083f20cdd0 0096
Call Trace:
IRQ
[81210366] cpumask_next_and+0x2c/0x39
[81022a57] __x2apic_send_IPI_mask+0xa9/0x129
[81022aee] x2apic_send_IPI_all+0x17/0x19
[8101fdc0] arch_trigger_all_cpu_backtrace+0x52/0x8a
[8109e683] print_cpu_stall+0xcc/0x15b
[8109e989] __rcu_pending+0x5d/0x166
[8109eb62] rcu_check_callbacks+0xd0/0x132
[8103fd16] update_process_times+0x3c/0x72
[81074770] tick_sched_handle+0x45/0x54
[8107492c] tick_sched_timer+0x58/0x77
[81051eee] __run_hrtimer+0xd6/0x161
[810748d4] ? tick_nohz_handler+0xab/0xab
[81039144] ? __do_softirq+0x182/0x1b4
[810522a5] hrtimer_interrupt+0xce/0x1b0
[8101f9a9] smp_apic_timer_interrupt+0x81/0x94
[81407d4a] apic_timer_interrupt+0x6a/0x70
EOI
[813622a2] ? skb_flow_dissect+0xca/0x33c
[81358107] ? sock_alloc_send_pskb+0x10d/0x337
[8135f622] ? skb_copy_datagram_from_iovec+0x58/0x20f
[81365fe2] __skb_get_rxhash+0x15/0xc0
[a02e04c5] tun_get_user+0x471/0x4e8 [tun]
[a02e05ac] ? tun_sendmsg+0x70/0x70 [tun]
[a02e0627] tun_chr_aio_write+0x7b/0x93 [tun]
[81108cdc] do_sync_readv_writev+0x93/0xd1
[8110932d] do_readv_writev+0xb6/0x17f
[81407120] ? ret_from_fork+0xb0/0xb0
[811170de] ? do_vfs_ioctl+0x255/0x271
[81109434] vfs_writev+0x3e/0x49
[8110952e] sys_writev+0x4f/0x9e
[81407192] system_call_fastpath+0x16/0x1b
Code: 89 d0 48 c1 e9 06 49 83 e0 c0 4c 8d 0c cf 48 89 f7 4c 29 c7 83 e2 3f 74
39 48 83 c8 ff 88 d1 48 d3 e0 49 23 01 48 83 ff 3f 76 3b 48 85 c0 75 4f 49 83
c1 08 48 83 ef 40 49 83 c0 40 eb 14 49 8b
** Affects: qemu
Importance: Undecided
Status: New
** Attachment added: host serial port log
https://bugs.launchpad.net/bugs/1096814/+attachment/3476027/+files/host-serial.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096814
Title:
Guest hang when doing kernel build and writing date in guest
Status in QEMU:
New
Bug description:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:e11ae1a102b46f76441e328a2743ae5d6e201423
qemu-kvm Commit:4d9367b76f71c6d938cf8201392abe4bfb1136cb
Host Kernel Version:3.7.0
Hardware:Romley-EP, WSM-EP
Bug detailed description:
--
When writing date to remote filesystem (e.g. NFS) and compiling kernel in a
guest, the guest will hang occasionally.
This can't
[Qemu-devel] [Bug 1096814] Re: Guest hang when doing kernel build and writing date in guest
I used a small script in the guest to touch files in NFS.
#!/bin/bash
mount vt-nfs:/temp /mnt
cd /mnt
# create files endlessly
for ((i=0; ; i++))
do
mkdir $i
cd $i
# 1 files at most in a directory
for ((j=0; j1; j++))
do
touch $j
done
done
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096814
Title:
Guest hang when doing kernel build and writing date in guest
Status in QEMU:
New
Bug description:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:e11ae1a102b46f76441e328a2743ae5d6e201423
qemu-kvm Commit:4d9367b76f71c6d938cf8201392abe4bfb1136cb
Host Kernel Version:3.7.0
Hardware:Romley-EP, WSM-EP
Bug detailed description:
--
When writing date to remote filesystem (e.g. NFS) and compiling kernel in a
guest, the guest will hang occasionally.
This can't be reproduced every time.
Reproduce steps:
1. star a guest: qemu-system-x86_64 -m 4096 -smp 4 -drive
file=rhel6u3-b.img,if=virtio -net nic,macaddr=00:16:13:52:24:11 -net tap
2. in guest: mount my-nfs:/temp /mnt
3. do kernel build and write some data in /mnt dir
Current result:
host serial port will print “call trace”message
Expected result:
Guest work fine.
Basic root-causing log:
--
(some log in the host side)
INFO: rcu_sched self-detected stall on CPU { 7} (t=21000 jiffies g=6506
c=6505
q=803)
sending NMI to all CPUs:
NMI backtrace for cpu 7
CPU 7
Pid: 10664, comm: qemu-system-x86 Tainted: P 3.7.0 #2 Intel
Corporation S2600CP/S2600CP
RIP: 0010:[8121d28b] [8121d28b] find_next_bit+0x3f/0x9d
RSP: 0018:88043f6e3ce8 EFLAGS: 0006
RAX: ff00fe00 RBX: 88083f20cdd0 RCX: 0009
RDX: 0009 RSI: 00ff RDI: 00ff
RBP: 88043f6e3ce8 R08: R09: 88043f6ecdf0
R10: 0004 R11: R12: 88043f6ecdf0
R13: cdc0 R14: cdd0 R15: 0002
FS: 7fda02753700() GS:88043f6e() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0031db8df760 CR3: 00042c82d000 CR4: 000427e0
DR0: DR1: DR2:
DR3: DR6: 0ff0 DR7: 0400
Process qemu-system-x86 (pid: 10664, threadinfo 88042b31, task
880424d03800)
Stack:
88043f6e3d08 81210366 88043f6ecdf0 0008
88043f6e3d78 81022a57 88043f6e3f48 7fff00020001
0007 0008813fe374 88083f20cdd0 0096
Call Trace:
IRQ
[81210366] cpumask_next_and+0x2c/0x39
[81022a57] __x2apic_send_IPI_mask+0xa9/0x129
[81022aee] x2apic_send_IPI_all+0x17/0x19
[8101fdc0] arch_trigger_all_cpu_backtrace+0x52/0x8a
[8109e683] print_cpu_stall+0xcc/0x15b
[8109e989] __rcu_pending+0x5d/0x166
[8109eb62] rcu_check_callbacks+0xd0/0x132
[8103fd16] update_process_times+0x3c/0x72
[81074770] tick_sched_handle+0x45/0x54
[8107492c] tick_sched_timer+0x58/0x77
[81051eee] __run_hrtimer+0xd6/0x161
[810748d4] ? tick_nohz_handler+0xab/0xab
[81039144] ? __do_softirq+0x182/0x1b4
[810522a5] hrtimer_interrupt+0xce/0x1b0
[8101f9a9] smp_apic_timer_interrupt+0x81/0x94
[81407d4a] apic_timer_interrupt+0x6a/0x70
EOI
[813622a2] ? skb_flow_dissect+0xca/0x33c
[81358107] ? sock_alloc_send_pskb+0x10d/0x337
[8135f622] ? skb_copy_datagram_from_iovec+0x58/0x20f
[81365fe2] __skb_get_rxhash+0x15/0xc0
[a02e04c5] tun_get_user+0x471/0x4e8 [tun]
[a02e05ac] ? tun_sendmsg+0x70/0x70 [tun]
[a02e0627] tun_chr_aio_write+0x7b/0x93 [tun]
[81108cdc] do_sync_readv_writev+0x93/0xd1
[8110932d] do_readv_writev+0xb6/0x17f
[81407120] ? ret_from_fork+0xb0/0xb0
[811170de] ? do_vfs_ioctl+0x255/0x271
[81109434] vfs_writev+0x3e/0x49
[8110952e] sys_writev+0x4f/0x9e
[81407192] system_call_fastpath+0x16/0x1b
Code: 89 d0 48 c1 e9 06 49 83 e0 c0 4c 8d 0c cf 48 89 f7 4c 29 c7 83 e2 3f 74
39 48 83 c8 ff 88 d1 48 d3 e0 49 23 01 48 83 ff 3f 76 3b 48 85 c0 75 4f 49
83
c1 08 48 83 ef 40 49 83 c0 40 eb 14 49 8b
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1096814/+subscriptions
[Qemu-devel] [Bug 1042561] [NEW] Guest has no xsave feature with parameter -cpu qemu64, +xsave in qemu command line.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:1a577b72475d161b6677c05abe57301362023bb2 qemu-kvm Commit:98f1f30a89901c416e51cc70c1a08d9dc15a2ad4 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, Ivy-bridge Bug detailed description: -- Guest has no xsave feature when create guest with parameter -cpu qemu64,+xsave,+avx in qemu command line, but the guest has avx feature. When starting a guest with parameter -cpu host in qemu command line, the guest has 'avx' and 'xsave' features (as /proc/cpuinfo shows). This is not a recent regression; it exists for a long time. Reproduce steps: 1. qemu-system-x86_64 -m 1024 -smp 2 -hda rhel6u3.img -cpu qemu64,+xsave 2. cat /proc/cpuinfo | grep xsave ( check guest's xsave feature) Current result: The guest has no xsave feature Expected result: The guest has xsave feature Basic root-causing log: ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1042561 Title: Guest has no xsave feature with parameter -cpu qemu64,+xsave in qemu command line. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:1a577b72475d161b6677c05abe57301362023bb2 qemu-kvm Commit:98f1f30a89901c416e51cc70c1a08d9dc15a2ad4 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, Ivy-bridge Bug detailed description: -- Guest has no xsave feature when create guest with parameter -cpu qemu64,+xsave,+avx in qemu command line, but the guest has avx feature. When starting a guest with parameter -cpu host in qemu command line, the guest has 'avx' and 'xsave' features (as /proc/cpuinfo shows). This is not a recent regression; it exists for a long time. Reproduce steps: 1. qemu-system-x86_64 -m 1024 -smp 2 -hda rhel6u3.img -cpu qemu64,+xsave 2. cat /proc/cpuinfo | grep xsave ( check guest's xsave feature) Current result: The guest has no xsave feature Expected result: The guest has xsave feature Basic root-causing log: To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1042561/+subscriptions
[Qemu-devel] [Bug 744195] Re: guest cannot boot with 8 VFs or more
This was fixed a long time ago. I just verified it with latest qemu-kvm.git and kvm.git. A RHEL6.3 guest can boot up with 10 VFs, and each VF has good network. So, mark this bug as fixed and verified. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/744195 Title: guest cannot boot with 8 VFs or more Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows): Linux kvm.git Commit:a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f qemu-kvm Commit:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- Guest cannot boot with 8 VFs or more VFs, but guest can boot with 7 VFs. If you assign hot-plug VFs, after you assigning the 8th VF, you may get the following message in host. kvm_alloc_slot: no free slot available. And the guest aborts. Reproduce steps: 1.try to create a guest with 8 VFs:(the guest cannot boot) qemu-system-x86_64 -smp 2 -m 1024 -net none -hda /root/rhel6.1-beta1.img -device pci-assign,host=04:10.0 -device pci-assign,host=04:10.1 -device pci-assign,host=04:10.2 -device pci-assign,host=04:10.3 -device pci-assign,host=04:10.4 -device pci-assign,host=04:10.5 -device pci-assign,host=04:10.6 -device pci-assign,host=04:10.7 2.If you want to assign 8 hot-plug VFs, you may use following command in qemu monitor after you start a guest. device_add pci-assign,host=00:19.0,id=my_nic To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/744195/+subscriptions
[Qemu-devel] [Bug 1007269] Re: Can’t install or boot up 32bit win8 guest.
qemu64 cpu model has PAE/NX/SSE2 Support by default. Also, after I used -cpu qemu64,+3dnow, 32bit Win8 also can't be installed and had a BSOD with Error code: 0x005D. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1007269 Title: Can’t install or boot up 32bit win8 guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- 0x005D code means UNSUPPORTED_PROCESSOR in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1007269/+subscriptions
[Qemu-devel] [Bug 1013467] Re: network in bridge mode doesn't work in SMP Linux guest
Verified this bug against latest qemu-kvm upstream. kvm + qemu-kvm: ae7a2a3f + a212f79f.. The following commit fixed it. commit a212f79fc4596570124fb864425b980c157cd001 Author: Jason Wang jasow...@redhat.com Date: Thu May 17 13:25:43 2012 +0800 rtl8139: validate rx ring before receiving packets Commit ff71f2e8cacefae99179993204172bc65e4303df prevent the possible crash during initialization of linux driver by checking the operating mode.This seems too strict as: - the real card could still work in mode other than normal - some buggy driver who does not set correct opmode after eeprom access So, considering rx ring address were reset to zero (which could be safely trated as an address not intened to DMA to), in order to both letting old guest work and preventing the unexpected DMA to guest, we can forbid packet receiving when rx ring address is zero. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1013467 Title: network in bridge mode doesn't work in SMP Linux guest Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120 qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038 Host Kernel Version:3.5.0-rc1 Hardware:WSM-EP, Romley-EP Bug detailed description: -- Network in bridge mode doesn't work in SMP RHEL6.1/6.2 guest. After booting up, use “dhclient ethX” to get IP (we use DHCP in the network), guest can not get IP. Note: 1. UP guest(-smp 1) doesn’t have this issue. 2. Windows(e.g. Win7) guest(-smp 4) has no issue. This should be a qemu-kvm bug. kvm + qemu-kvm = result 25e531a9 + 0a948cbb= bad 25e531a9 + 18b01275 = good Reproduce steps: 1.start up a host with kvm(25e531a9) + qemu-kvm (0a948cbb) 2.qemu-system-x86_64 -m 1024 -smp 4 –net nic,model=rt18139 –net tap,script=/etc/kvm/qemu-ifup –hda /root/rhel6u1.qcow 3. ifconfig 4. ping 192.168.199.98 (a IP in the same subnet) 5. dhclient ethx (can't get dynamic IP address) Current result: The guest can not get IP Expected result: The guest get IP and work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1013467/+subscriptions
[Qemu-devel] [Bug 1019179] [NEW] vCPU hot-add makes the guest abort
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(RHEL6u1) kvm.git Commit:ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb qemu-kvm Commit:a212f79fc4596570124fb864425b980c157cd001 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, WSM-EP Bug detailed description: -- Hot-add vcpu for a guest in qemu monitor will make the guest abort. (QEMU process is killed.) After Hot-removing vcpu for the guest in qemu monitor, the guest will be still alive but the the number of vCPU in the guest doesn't decrease. Reproduce steps: Hot-add vCPU: 1.start up a host with kvm (commit: ae7a2a3f)and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 5 online Hot-remove vCPU: 1.start up a host with kvm (commit: ae7a2a3f) and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 2 offline 6. ctrl+alt+1 7. ls /sys/devices/system/cpu/(to check CPUs in guest) Current result: vCPU hot-add will cause guest abort. vCPU hot-remove doesn't decrease the number of vCPU in guest. Expected result: The number of the guest’s cpu changes as we expect. Basic root-causing log: -- [root@vt-snb9 ~]# qemu-system-x86_64 -m 1024 -smp 4,maxcpus=10 -hda /root/rhel6u3.qcow VNC server running on `::1:5900' qemu-system-x86_64: hw/qdev.c:84: qdev_set_parent_bus: Assertion `bus-allow_hotplug' failed. Aborted (core dumped) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1019179 Title: vCPU hot-add makes the guest abort Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(RHEL6u1) kvm.git Commit:ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb qemu-kvm Commit:a212f79fc4596570124fb864425b980c157cd001 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, WSM-EP Bug detailed description: -- Hot-add vcpu for a guest in qemu monitor will make the guest abort. (QEMU process is killed.) After Hot-removing vcpu for the guest in qemu monitor, the guest will be still alive but the the number of vCPU in the guest doesn't decrease. Reproduce steps: Hot-add vCPU: 1.start up a host with kvm (commit: ae7a2a3f)and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 5 online Hot-remove vCPU: 1.start up a host with kvm (commit: ae7a2a3f) and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 2 offline 6. ctrl+alt+1 7. ls /sys/devices/system/cpu/(to check CPUs in guest) Current result: vCPU hot-add will cause guest abort. vCPU hot-remove doesn't decrease the number of vCPU in guest. Expected result: The number of the guest’s cpu changes as we expect. Basic root-causing log: -- [root@vt-snb9 ~]# qemu-system-x86_64 -m 1024 -smp 4,maxcpus=10 -hda /root/rhel6u3.qcow VNC server running on `::1:5900' qemu-system-x86_64: hw/qdev.c:84: qdev_set_parent_bus: Assertion `bus-allow_hotplug' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1019179/+subscriptions
[Qemu-devel] [Bug 1013467] Re: network in bridge mode doesn't work in SMP Linux guest
** Attachment added: guest dmesg log https://bugs.launchpad.net/qemu/+bug/1013467/+attachment/3190179/+files/dmesg-guest.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1013467 Title: network in bridge mode doesn't work in SMP Linux guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120 qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038 Host Kernel Version:3.5.0-rc1 Hardware:WSM-EP, Romley-EP Bug detailed description: -- Network in bridge mode doesn't work in SMP RHEL6.1/6.2 guest. After booting up, use “dhclient ethX” to get IP (we use DHCP in the network), guest can not get IP. Note: 1. UP guest(-smp 1) doesn’t have this issue. 2. Windows(e.g. Win7) guest(-smp 4) has no issue. This should be a qemu-kvm bug. kvm + qemu-kvm = result 25e531a9 + 0a948cbb= bad 25e531a9 + 18b01275 = good Reproduce steps: 1.start up a host with kvm(25e531a9) + qemu-kvm (0a948cbb) 2.qemu-system-x86_64 -m 1024 -smp 4 –net nic,model=rt18139 –net tap,script=/etc/kvm/qemu-ifup –hda /root/rhel6u1.qcow 3. ifconfig 4. ping 192.168.199.98 (a IP in the same subnet) 5. dhclient ethx (can't get dynamic IP address) Current result: The guest can not get IP Expected result: The guest get IP and work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1013467/+subscriptions
[Qemu-devel] [Bug 1013467] Re: network in bridge mode doesn't work in SMP Linux guest
** Attachment added: lspci -vvv in guest https://bugs.launchpad.net/qemu/+bug/1013467/+attachment/3190180/+files/lspci-guest.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1013467 Title: network in bridge mode doesn't work in SMP Linux guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120 qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038 Host Kernel Version:3.5.0-rc1 Hardware:WSM-EP, Romley-EP Bug detailed description: -- Network in bridge mode doesn't work in SMP RHEL6.1/6.2 guest. After booting up, use “dhclient ethX” to get IP (we use DHCP in the network), guest can not get IP. Note: 1. UP guest(-smp 1) doesn’t have this issue. 2. Windows(e.g. Win7) guest(-smp 4) has no issue. This should be a qemu-kvm bug. kvm + qemu-kvm = result 25e531a9 + 0a948cbb= bad 25e531a9 + 18b01275 = good Reproduce steps: 1.start up a host with kvm(25e531a9) + qemu-kvm (0a948cbb) 2.qemu-system-x86_64 -m 1024 -smp 4 –net nic,model=rt18139 –net tap,script=/etc/kvm/qemu-ifup –hda /root/rhel6u1.qcow 3. ifconfig 4. ping 192.168.199.98 (a IP in the same subnet) 5. dhclient ethx (can't get dynamic IP address) Current result: The guest can not get IP Expected result: The guest get IP and work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1013467/+subscriptions
[Qemu-devel] [Bug 1013467] [NEW] network in bridge mode doesn't work in SMP Linux guest
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120 qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038 Host Kernel Version:3.5.0-rc1 Hardware:WSM-EP, Romley-EP Bug detailed description: -- Network in bridge mode doesn't work in SMP RHEL6.1/6.2 guest. After booting up, use “dhclient ethX” to get IP (we use DHCP in the network), guest can not get IP. Note: 1. UP guest(-smp 1) doesn’t have this issue. 2. Windows(e.g. Win7) guest(-smp 4) has no issue. This should be a qemu-kvm bug. kvm + qemu-kvm = result 25e531a9 + 0a948cbb= bad 25e531a9 + 18b01275 = good Reproduce steps: 1.start up a host with kvm(25e531a9) + qemu-kvm (0a948cbb) 2.qemu-system-x86_64 -m 1024 -smp 4 –net nic,model=rt18139 –net tap,script=/etc/kvm/qemu-ifup –hda /root/rhel6u1.qcow 3. ifconfig 4. ping 192.168.199.98 (a IP in the same subnet) 5. dhclient ethx (can't get dynamic IP address) Current result: The guest can not get IP Expected result: The guest get IP and work fine. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1013467 Title: network in bridge mode doesn't work in SMP Linux guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120 qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038 Host Kernel Version:3.5.0-rc1 Hardware:WSM-EP, Romley-EP Bug detailed description: -- Network in bridge mode doesn't work in SMP RHEL6.1/6.2 guest. After booting up, use “dhclient ethX” to get IP (we use DHCP in the network), guest can not get IP. Note: 1. UP guest(-smp 1) doesn’t have this issue. 2. Windows(e.g. Win7) guest(-smp 4) has no issue. This should be a qemu-kvm bug. kvm + qemu-kvm = result 25e531a9 + 0a948cbb= bad 25e531a9 + 18b01275 = good Reproduce steps: 1.start up a host with kvm(25e531a9) + qemu-kvm (0a948cbb) 2.qemu-system-x86_64 -m 1024 -smp 4 –net nic,model=rt18139 –net tap,script=/etc/kvm/qemu-ifup –hda /root/rhel6u1.qcow 3. ifconfig 4. ping 192.168.199.98 (a IP in the same subnet) 5. dhclient ethx (can't get dynamic IP address) Current result: The guest can not get IP Expected result: The guest get IP and work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1013467/+subscriptions
[Qemu-devel] [Bug 1002121] Re: disk error when guest boot up via qcow2 image
Re-tested against latest qemu-kvm master branch with commit 0a948cbb. And found this issue has gone. Jan Kiszka's following patch fixed this bug. commit 0cdd3d14447da1a04e778c219c77db8b96f9cf33 Author: Jan Kiszka Date: Wed Jun 6 16:28:42 2012 +0200 kvm: i8254: Fix conversion of in-kernel to userspace state Due to a offset between the clock used to generate the in-kernel count_load_time (CLOCK_MONOTONIC) and the clock used for processing this in userspace (vm_clock), reading back the output of PIT channel 2 via port 0x61 was broken. One use cases that suffered from it was the CPU frequency calibration of SeaBIOS, which also affected IDE/AHCI timeouts. This fixes it by calibrating the offset between both clocks on kvm_pit_get and adjusting the kernel value before saving it in the userspace state. As the calibration only works while the vm_clock is running, we cache the in-kernel state across stopped phases. Signed-off-by: Jan Kiszka ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: Fix Released Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 1002121] Re: disk error when guest boot up via qcow2 image
reply to Jan Kiszka: I looked at the patch in uq/master branch in qemu-kvm.git as you mentioned. There's another issue in uq/master branch, so I can't conclude whether your patch will make a difference. The issue is Windows(e.g. win7) will get a BSOD with a message STOP: ox005D. RAW Windows image or qcow image will have the same BSOD issue. And Linux guest also has similar issue with uq/master branch. You can use the following commit in uq/master branch to have a try. commit: d3d3bef0a (before your patch i8254: Fix conversion of in-kernel to userspace state) latest commit: 0cdd3d14 (already included your pathch) And, qemu-kvm.git master branch (18b01275) doesn't have the BSOD issue. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: New Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 1002121] Re: disk error when guest boot up via qcow2 image
reply to Michael Tokarev: Windows qcow2 image will be more easier for reproducing the issue I reported. And there's a great chance to reproduce it when you do the first try after rebooting the system. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: New Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 1002121] Re: disk error when guest boot up via qcow2 image
after reverting bef0fd59 in qemu-kvm, this issue doesn't exist. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: New Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 1007269] Re: Can’t install or boot up 32bit win8 guest.
64bit Win8 client can work fine as a kvm guest, however, 32bit can't work. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1007269 Title: Can’t install or boot up 32bit win8 guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- 0x005D code means UNSUPPORTED_PROCESSOR in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1007269/+subscriptions
[Qemu-devel] [Bug 1007269] Re: Can’t install or boot up 32bit win8 guest.
For 32bit Win8, I used different cpu mode and got different results as following. n270: can boot up athlon: fail (Error code: 0x005D) pentium3: can boot up pentium2: fail(Error code: 0x005D) Pentium: fail(error code: 0xc260) 486: fail(error code: 0xc260) Coreduo: can boog up Kvm32: can boot up Qemu32: can boot up Kvm64: can bootup Core2duo: can boot up Phenom: can boot up Qemu64: fail (Error code: 0x005D) [root@jay-linux ~]# qemu-system-x86_64 -cpu ? x86 [n270] x86 [athlon] x86 [pentium3] x86 [pentium2] x86[pentium] x86[486] x86[coreduo] x86 [kvm32] x86 [qemu32] x86 [kvm64] x86 [core2duo] x86 [phenom] x86 [qemu64] -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1007269 Title: Can’t install or boot up 32bit win8 guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- 0x005D code means UNSUPPORTED_PROCESSOR in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1007269/+subscriptions
[Qemu-devel] [Bug 1007269] [NEW] Can’t install or boot up 32bit win8 guest.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- 0x005D code means UNSUPPORTED_PROCESSOR in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1007269 Title: Can’t install or boot up 32bit win8 guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- 0x005D code means UNSUPPORTED_PROCESSOR in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1007269/+subscriptions
[Qemu-devel] [Bug 1002121] [NEW] disk error when guest boot up via qcow2 image
Public bug reported: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: New Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 1002121] Re: disk error when guest boot up via qcow2 image
Latest commit 3fd9fedb in qemu-kvm master tree still has this issue. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1002121 Title: disk error when guest boot up via qcow2 image Status in QEMU: New Bug description: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel6u1) kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc Host Kernel Version:3.4.0-rc7 Hardware: WSM-EP, Romley-EP Bug detailed description: -- If I boot up a guest using qcow2 image, the guest show “disk read error”. If you press some key to continue, after being automatically repaired, the guest can boot up. This should be a qemu-kvm regression. kvm + qemu-kvm = result 51bfd299 + e54f008e= bad 51bfd299 + b320b8b7 = good Note: 1. guest rhel6u1, guest show “disk error” guest rhel6u2, guest show black screen this phenomenon occurs at the first time to create guest 2. create guest with raw image, this phenomenon doesn’t appear. Reproduce steps: 1.start up a host with kvm (commit: 51bfd299) and use qemu-kvm (commit:e54f008e) 2.qemu-img create –b /share/ia32e_rhel6u1.img –f qcow2 /root/rhel6u1.qcow 3.qemu-system-x86_64 -mem 1024 –hda /root/rhel6u1.qcow Current result: Guest console shows: error 25:Disk read error Prss any key to continue... Expected result: Guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1002121/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
It was fixed in latest qemu-kvm tree. verified it against kvm + qemu-kvm: 331b646d..+ e54f008e.. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, but the guest can only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igbvf driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 994378] [NEW] Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/994378 Title: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature i64 not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/994378/+subscriptions
[Qemu-devel] [Bug 979714] Re: The pit interrupt still exists even with tickless guest
verified. this bug should have been fixed by the following commit. commit 80019541e9c13fab476bee35edcef3e11646222c Author: Jan Kiszka jan.kis...@siemens.com Date: Mon Apr 23 10:47:14 2012 +0200 qemu-kvm: Switch to upstream in-kernel KVM PIT The upstream version provides the same feature plus proper support for the PC speaker port while the in-kernel PIT is enabled. ** Changed in: qemu Status: New = Fix Committed ** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/979714 Title: The pit interrupt still exists even with tickless guest Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:4f324a1b qemu-kvm Commit: b5ed4b6f Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Start a guest and check into /proc/interrupts, the timer interrupt will constantly increase while local timer interrups are already increasing. qemu-kvm commit: 9d636ae7 doesn't have this issue. The dmesg of the guest shows: APIC calibration not consistent with PM-Timer: 191ms instead of 100ms This should be a qemu-kvm bug. kvm + qemu-kvm = result 4f324a1b + b5ed4b6f = bad 4f324a1b + 9d636ae7 = good Reproduce steps: 1. start up a host with kvm kernel 2. qemu-system-x86_64 –m 1024 –smp 2 –net none –hda /root/rhel6u1.img 3. cat /proc/interrupts Current result: interrupt 0 keeps increasing Expected result: interrupt 0 stops at some value and doesn't increase To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/979714/+subscriptions
[Qemu-devel] [Bug 877155] Re: VT-D NIC doesn't work in windows guest
From my test, this bug is fixed in the latest kvm.git. I tried 82572 NIC for device assignment in WinXP, Win7 and Win2k8. The VT-d NIC works fine in Windows guest. kvm.git+qemu-kvm.git = result f4d1f417 +df44afac = bad eb9ede96 +df44afac = good But I don't know which exact patch fixed this bug. ** Changed in: qemu Status: New = Fix Committed ** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/877155 Title: VT-D NIC doesn't work in windows guest Status in QEMU: Fix Released Bug description: [This should be a kvm kernel bug. I met this issue with quemu and kvm for virtualization. For https://bugzilla.kernel.org is not available yet, I just file this bug here just for tracking. ] Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Using qemu and kvm upstream, VT-D NIC and SR-IOV VF don't work in Windows guest. I tried Windows XP, Vista, Win7, Win2k8 as a guest. And I used 82572 NIC and 82576 Virtual Function to assign to windows guest, and got the same result. Reproduce steps: 1.start a Windows guest with a NIC assigned: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=08:00.0 -net none -hda Windows.img 2.check network in the Windows guest. (You'll find the assigned NIC doesn't work in guest.) Current result: NIC doesn't work in Windows guest Expected result: NIC will work. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/877155/+subscriptions
[Qemu-devel] [Bug 953754] [NEW] one of the two assigned NICs doesn’t work in SMP guest.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: guest dmesg log https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861052/+files/dmesg-guest.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: lspci -vvv 82576 NIC in guest https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861057/+files/lspci-guest-82576.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Description changed: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP - Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: - 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. - 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. - 3. UP guest can get two IP. - 4. smp guest, and assign two VFs with igb driver, the guest can get two IP + 1. when assign two NICs, both of the drivers are igb, but the guest can only get one IP. + 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. + 3. UP guest can get two IP. + 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result - 18619592 + 81bdec90 = bad + 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img - 5. ifconfig - + 5. ifconfig Current result: Only one can work Expected result: Both NICs can work ** Description changed: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, but the guest can only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. - 4. smp guest, and assign two VFs with igb driver, the guest can get two IP - addresses. + 4. smp guest, and assign two VFs with igbvf driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, but the guest can only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igbvf driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result:
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: lspci -vvv 82576 NIC in host https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861055/+files/lspci-host-82576.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: lspci -vvv I350 NIC in host https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861054/+files/lspci-host-I350.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: host dmesg log https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861051/+files/dmesg-host.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
And if you try with smp=4, you may see some error info from qemu.
assigned_dev_update_msix_mmio: No such device or address
fail to set MSI-X entry number for MSIX! Invalid argument
The message is generated from the funtion assigned_dev_update_msix_mmio in
hw/device-assignment.c
1035 r = kvm_assign_set_msix_entry(kvm_state, msix_entry);
1036 if (r) {
1037 fprintf(stderr, fail to set MSI-X entry! %s\n,
strerror(-r));
1038 break;
1039 }
Some logs:
[root@vt-nhm9 jay]# qemu-system-x86_64 -m 512 -smp 4 -device
pci-assign,host=11:00.0,id=nic1 -net none -device
pci-assign,host=11:00.1,id=nic2 -net none -hda rhel6u1.qcow
Could not open option rom 'kvmvapic.bin': No such file or directory
Could not open option rom 'vapic.bin': No such file or directory
VNC server running on `::1:5900'
assigned_dev_update_msix_mmio: No such device or address
fail to set MSI-X entry number for MSIX! Invalid argument
assigned_dev_update_msix_mmio: Invalid argument
fail to set MSI-X entry number for MSIX! Invalid argument
assigned_dev_update_msix_mmio: Invalid argument
fail to set MSI-X entry number for MSIX! Invalid argument
assigned_dev_update_msix_mmio: Invalid argument
fail to set MSI-X entry number for MSIX! Invalid argument
assigned_dev_update_msix_mmio: Invalid argument
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
Title:
one of the two assigned NICs doesn’t work in SMP guest.
Status in QEMU:
New
Bug description:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows): Linux(RHEL6u1)
kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b
qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad
Host Kernel Version:3.3.0-rc5
Hardware: Romley-EP, WSM-EP
Bug detailed description:
--
SMP guest cannot get two IP addresses when assign two NICs with igb driver.
I tried with Intel I350 and 82576 Ethernet Adapter.
Note:
1. when assign two NICs, both of the drivers are igb, the guest get only
get one IP.
2. When assign two NICs, one driver is igb, another is ixgbe, the guest
can get two IP address.
3. UP guest can get two IP.
4. smp guest, and assign two VFs with igb driver, the guest can get two
IP
addresses.
This should be a qemu-kvm bug.
kvm + qemu-kvm = result
18619592 + 81bdec90 = bad
18619592 + b5ed4b6f = good
Reproduce steps:
1. start up a host with kvm kernel
2. /root/pcistub.sh –h 08:00.0
3. /root/pcistub.sh –h 0d:00.1
4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1
–net none –device pci-assign,host=08:00.0 –net none –hda
/root/rhel6u1.img
5. ifconfig
Current result:
Only one can work
Expected result:
Both NICs can work
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 953754] Re: one of the two assigned NICs doesn’t work in SMP guest.
** Attachment added: lspci -vvv I350 NIC in guest https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861056/+files/lspci-guest-I350.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/953754 Title: one of the two assigned NICs doesn’t work in SMP guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- SMP guest cannot get two IP addresses when assign two NICs with igb driver. I tried with Intel I350 and 82576 Ethernet Adapter. Note: 1. when assign two NICs, both of the drivers are igb, the guest get only get one IP. 2. When assign two NICs, one driver is igb, another is ixgbe, the guest can get two IP address. 3. UP guest can get two IP. 4. smp guest, and assign two VFs with igb driver, the guest can get two IP addresses. This should be a qemu-kvm bug. kvm + qemu-kvm = result 18619592 + 81bdec90 = bad 18619592 + b5ed4b6f = good Reproduce steps: 1. start up a host with kvm kernel 2. /root/pcistub.sh –h 08:00.0 3. /root/pcistub.sh –h 0d:00.1 4. qemu-system-x86_64 –m 512 –smp 2 –device pci-assign,host=0d:00.1 –net none –device pci-assign,host=08:00.0 –net none –hda /root/rhel6u1.img 5. ifconfig Current result: Only one can work Expected result: Both NICs can work To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/953754/+subscriptions
[Qemu-devel] [Bug 912612] Re: rhel5u5 guest panic when booting up
** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/912612 Title: rhel5u5 guest panic when booting up Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1 0800 80078e9a 0800 80411712 0009 0800 Call Trace: [8007efcf] lapic_watchdog_init+0x1b/0x3c [800795d1] setup_apic_nmi_watchdog+0x42/0x8a [80078e9a] setup_local_APIC+0x17b/0x187 [80411712] smp_prepare_cpus+0x34a/0x360 [804078c5] init+0x62/0x2f7 [8005efb1] child_rip+0xa/0x11 [801824cc] acpi_ds_init_one_object+0x0/0x80 [80407863] init+0x0/0x2f7 [8005efa7] child_rip+0x0/0x11 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/912612/+subscriptions
[Qemu-devel] [Bug 913774] Re: device can't be hot-removed from the guest
fixed by the following commit. commit 024a6fbdb9d8cbc4d7f833b23db51c9d1004bc47 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Jan 13 07:45:55 2012 -0600 qdev: fix device_del by refactoring reference counting Commit 8eb0283 broken device_del by having too overzealous reference counting checks. Move the reference count checks to qdev_free(), make sure to remove the parent link on free, and decrement the reference count on property removal. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 912612] Re: rhel5u5 guest panic when booting up
Already fixed. pls. track the following bug. https://bugzilla.kernel.org/show_bug.cgi?id=42563 ** Bug watch added: Linux Kernel Bug Tracker #42563 http://bugzilla.kernel.org/show_bug.cgi?id=42563 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/912612 Title: rhel5u5 guest panic when booting up Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1 0800 80078e9a 0800 80411712 0009 0800 Call Trace: [8007efcf] lapic_watchdog_init+0x1b/0x3c [800795d1] setup_apic_nmi_watchdog+0x42/0x8a [80078e9a] setup_local_APIC+0x17b/0x187 [80411712] smp_prepare_cpus+0x34a/0x360 [804078c5] init+0x62/0x2f7 [8005efb1] child_rip+0xa/0x11 [801824cc] acpi_ds_init_one_object+0x0/0x80 [80407863] init+0x0/0x2f7 [8005efa7] child_rip+0x0/0x11 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/912612/+subscriptions
[Qemu-devel] [Bug 913774] Re: device can't be hot-removed from the guest
** Attachment added: lspci -vvv in guest https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664205/+files/lspci-guest.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 913774] Re: device can't be hot-removed from the guest
** Attachment added: guest dmesg log https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664198/+files/dmesg-guest.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 913774] Re: device can't be hot-removed from the guest
** Attachment added: host dmesg log https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664196/+files/dmesg-host.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 913774] Re: device can't be hot-removed from the guest
** Attachment added: lspci -vvv in host https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664197/+files/lspci-host.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 913774] [NEW] device can't be hot-removed from the guest
Public bug reported: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/913774 Title: device can't be hot-removed from the guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19 Host Kernel Version: 3.2.0-rc7 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Using the latest qemu-kvm and kvm upstream, PCI device can't be hot-removed from the guest. I try to remove a VF, but the device can't be removed. The VF in guest still has IP, and its network is fine. A normal NIC will have the same issue. From my test, this should be a qemu-kvm bug. kvm + qemu-kvm= result ff92e9b5 + aad3b517 = bad ff92e9b5 + fcfeed4a = good some logs are attached. Reproduce steps: 1. start up a host with kvm(commit: ff92e9b5) and use qmeu-kvm(commit:aad3b517 ) 2. qemu-system-x86_64 -m 512 -smp 1 –hda /root/rhel6u1.img 3. ctrl+Alt+2 (switch to monitor) 4. device_add pci-assign,host=09:10.0,id=nic (hot-add a VF) 5. ctrl+Alt+1 6. check the device can get IP 7. ctrl+Alt+2 8. device_del nic (try to detach the VF) Current result: Cannot hot-remove the device. Expected result: The device can be hot-removed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/913774/+subscriptions
[Qemu-devel] [Bug 912612] Re: rhel5u5 guest panic when booting up
This should be a kvm kernel bug. As 'bugzilla.kernel.org' is down, I reported it here just for tracking. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/912612 Title: rhel5u5 guest panic when booting up Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1 0800 80078e9a 0800 80411712 0009 0800 Call Trace: [8007efcf] lapic_watchdog_init+0x1b/0x3c [800795d1] setup_apic_nmi_watchdog+0x42/0x8a [80078e9a] setup_local_APIC+0x17b/0x187 [80411712] smp_prepare_cpus+0x34a/0x360 [804078c5] init+0x62/0x2f7 [8005efb1] child_rip+0xa/0x11 [801824cc] acpi_ds_init_one_object+0x0/0x80 [80407863] init+0x0/0x2f7 [8005efa7] child_rip+0x0/0x11 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/912612/+subscriptions
[Qemu-devel] [Bug 912612] [NEW] rhel5u5 guest panic when booting up
Public bug reported: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1 0800 80078e9a 0800 80411712 0009 0800 Call Trace: [8007efcf] lapic_watchdog_init+0x1b/0x3c [800795d1] setup_apic_nmi_watchdog+0x42/0x8a [80078e9a] setup_local_APIC+0x17b/0x187 [80411712] smp_prepare_cpus+0x34a/0x360 [804078c5] init+0x62/0x2f7 [8005efb1] child_rip+0xa/0x11 [801824cc] acpi_ds_init_one_object+0x0/0x80 [80407863] init+0x0/0x2f7 [8005efa7] child_rip+0x0/0x11 ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/912612 Title: rhel5u5 guest panic when booting up Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1
[Qemu-devel] [Bug 912612] Re: rhel5u5 guest panic when booting up
** Attachment added: guest panic serial log https://bugs.launchpad.net/bugs/912612/+attachment/2659505/+files/guest-rhel5u5-panic.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/912612 Title: rhel5u5 guest panic when booting up Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): ia32e Guest OS (ia32/ia32e/IA64): ia32e Guest OS Type (Linux/Windows): Linux(rhel5u5) kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475 Host Kernel Version:3.2.0-rc7 Hardware: Westmere-EP Bug detailed description: -- rhel5u5 guest panic when booting up in the latest kvm upstream. When I tried rhel6u1 as a guest, I didn't met the guest panic issue. This should be a kvm kernel bug. kvm + qemu-kvm = result 781f3067 + 2850e9e3 = bad 08a95a51 + 2850e9e3 = good guest panic serial log is attached. Reproduce steps: 1.start up a host with kvm (commit:781f3067) 2.qemu-system-x86_64 -mem 512 -hda /root/rhel5u5.img Current result: guest panic Expected result: guest boot up correctly Basic root-causing log: -- SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed ACPI: Core revision 20060707 general protection fault: [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.18-194.el5 #1 RIP: 0010:[8007f1df] [8007f1df] setup_p6_watchdog+0x2f/0x7a RSP: :81000114be50 EFLAGS: 0246 RAX: 00130079 RBX: 0186 RCX: 0186 RDX: RSI: RDI: 03e8 RBP: 0009 R08: R09: R10: R11: R12: 8100010353e8 R13: 00c1 R14: R15: FS: () GS:803cb000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: CR3: 00201000 CR4: 06e0 Process swapper (pid: 1, threadinfo 81000114a000, task 81001fd3e7a0) Stack: 03e8 00ff 8007efcf 8043e288 800795d1 0800 80078e9a 0800 80411712 0009 0800 Call Trace: [8007efcf] lapic_watchdog_init+0x1b/0x3c [800795d1] setup_apic_nmi_watchdog+0x42/0x8a [80078e9a] setup_local_APIC+0x17b/0x187 [80411712] smp_prepare_cpus+0x34a/0x360 [804078c5] init+0x62/0x2f7 [8005efb1] child_rip+0xa/0x11 [801824cc] acpi_ds_init_one_object+0x0/0x80 [80407863] init+0x0/0x2f7 [8005efa7] child_rip+0x0/0x11 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/912612/+subscriptions
[Qemu-devel] [Bug 877155] Re: VT-D NIC doesn't work in windows guest
This is the dmesg in host in vtd assignment. Please look at the log from its tail. The device with BDF 08:00.0 is the assigned 82572EI NIC to a Win7 guest. ** Attachment added: dmesg in host in vtd assignment https://bugs.launchpad.net/qemu/+bug/877155/+attachment/2611274/+files/dmesg-host.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/877155 Title: VT-D NIC doesn't work in windows guest Status in QEMU: New Bug description: [This should be a kvm kernel bug. I met this issue with quemu and kvm for virtualization. For https://bugzilla.kernel.org is not available yet, I just file this bug here just for tracking. ] Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Using qemu and kvm upstream, VT-D NIC and SR-IOV VF don't work in Windows guest. I tried Windows XP, Vista, Win7, Win2k8 as a guest. And I used 82572 NIC and 82576 Virtual Function to assign to windows guest, and got the same result. Reproduce steps: 1.start a Windows guest with a NIC assigned: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=08:00.0 -net none -hda Windows.img 2.check network in the Windows guest. (You'll find the assigned NIC doesn't work in guest.) Current result: NIC doesn't work in Windows guest Expected result: NIC will work. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/877155/+subscriptions
[Qemu-devel] [Bug 877155] Re: VT-D NIC doesn't work in windows guest
You can try to follow the reproduce steps described in bug description to reproduce this bug with the given commit of kvm.git I think it's easy to reproduce. For Intel NIC drivers in windows, you can download the appropriate driver you need via searching Network Adapter Drivers for Windows keywords in the following link. http://downloadcenter.intel.com/SearchResult.aspx?lang=eng BTW, many Intel Ethernet Controllers use the same driver named PROWinx64.exe(64bit) or PROWin32.exe(32bit). My driver for the assigned 82572 NIC for windows guest is the latest driver downloaded from the above website. Its version is 16.7. I said it was a kernel bug because it doesn't work when using latest kvm with an older qemu-kvm (in July 2011) . The older qemu-kvm was proved to be a good version at that time with appropriate kvm. it's good with: kvm.git e62c2ef9 + qemu-kvm.git 525e3df7 it's bad with: kvm.git (latest) + qemu-kvm.git 525e3df7 The phenomenon with the latest kvm upstream has some difference now. Now VT-D/SR-IOV NIC in win2k8 guest works fine now, but VT-D/SR-IOV NIC in win7 or winXP guest doesn't work. However, when I reported that bug, VT-D/SR-IOV NIC didn't work in win2k8, win7 or winXP guest. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/877155 Title: VT-D NIC doesn't work in windows guest Status in QEMU: New Bug description: [This should be a kvm kernel bug. I met this issue with quemu and kvm for virtualization. For https://bugzilla.kernel.org is not available yet, I just file this bug here just for tracking. ] Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Using qemu and kvm upstream, VT-D NIC and SR-IOV VF don't work in Windows guest. I tried Windows XP, Vista, Win7, Win2k8 as a guest. And I used 82572 NIC and 82576 Virtual Function to assign to windows guest, and got the same result. Reproduce steps: 1.start a Windows guest with a NIC assigned: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=08:00.0 -net none -hda Windows.img 2.check network in the Windows guest. (You'll find the assigned NIC doesn't work in guest.) Current result: NIC doesn't work in Windows guest Expected result: NIC will work. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/877155/+subscriptions
[Qemu-devel] [Bug 875723] Re: guest aborts when detaching a SR-IOV VF
This bug is got fixed in qemu-kvm upstream. I verified it. The following is the commit info for the fix in qemu-kvm. commit c4cd183600aa6319b4a4a0b48cb41d63198e08c3 Author: Alex Williamson alex.william...@redhat.com Date: Wed Nov 16 13:45:32 2011 -0700 pci-assign: Fix device removal We're destroying the memory container before we remove the subregions it holds. This fixes: https://bugs.launchpad.net/qemu/+bug/875723 Signed-off-by: Alex Williamson alex.william...@redhat.com Signed-off-by: Avi Kivity a...@redhat.com ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/875723 Title: guest aborts when detaching a SR-IOV VF Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Guest will abort when detaching a SR-IOV VF. I'm using rhel6 and rhel6u1 as my guest. Firstly, I hot-plug a sr-iov VF to a guest. Then I detach the VF from the guest. At that time, guest aborts and qemu-kvm process aborts with the following message. qemu-system-x86_64: /workspace/qemu-kvm/memory.c:998: memory_region_destroy: Assertion `((mr-subregions)-tqh_first == ((void *)0))' failed. Aborted (core dumped) Reproduce steps: 1.start a rhel6 guest 2.attach a SR-IOV VF to the guest: device_add pci-assign,host=01:10.0,id=myNIC (I'm using 82576 Virtual Function.) 3.detach the VF from the guest: device_del myNIC (you'll find guest aborts) Current result: guest aborts and qemu process aborts Expected result: guest still alive To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/875723/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
This is because kvm is not enabled when starting guest by default even if I add KVM support when configuring qemu. Now it got fixed by the following commit. author Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) committer Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) commit 7879db7e9c09b92d9af1c143fbe2cc212ec89e4b Revert qemu-kvm: set default accelerator via target.conf This reverts commit a5c40eb1aa929a03157252db7337bc4ddd2435be. Jan says: Unless you fully install qemu, that conf is not picked up (or an older version is used). I'd still like to see this working with qemu started from a build directory... Signed-off-by: Marcelo Tosatti mtosa...@redhat.com ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: Fix Released Bug description: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu.git with commit edbb7c0, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. I found the following log in master tree. And that merger maybe introduced this issue in master tree. commit 36f490b176afab3096e9c2877b365354f67e269d Merge: ebffe2a 0d95952 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Oct 14 10:44:52 2011 -0500 Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into staging Reproduce steps: 1.with latest qemu.git master tree, to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 855664] Re: 64-bit windows guest cannot boot up
same reason as this bug: https://bugs.launchpad.net/qemu/+bug/882358 This is because kvm is not enabled when starting guest by default even if I add KVM support when configuring qemu. Now it got fixed by the following commit. author Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) committer Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) commit 7879db7e9c09b92d9af1c143fbe2cc212ec89e4b Revert qemu-kvm: set default accelerator via target.conf This reverts commit a5c40eb1aa929a03157252db7337bc4ddd2435be. Jan says: Unless you fully install qemu, that conf is not picked up (or an older version is used). I'd still like to see this working with qemu started from a build directory... Signed-off-by: Marcelo Tosatti mtosa...@redhat.com ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855664 Title: 64-bit windows guest cannot boot up Status in QEMU: Fix Released Bug description: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. I found the following git log in master tree. And that merger maybe introduced this issue in master tree. commit 36f490b176afab3096e9c2877b365354f67e269d Merge: ebffe2a 0d95952 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Oct 14 10:44:52 2011 -0500 Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into staging Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855664/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
It's the same reason as the following bug. https://bugs.launchpad.net/qemu/+bug/882358 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: Fix Released Bug description: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu.git with commit edbb7c0, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. I found the following log in master tree. And that merger maybe introduced this issue in master tree. commit 36f490b176afab3096e9c2877b365354f67e269d Merge: ebffe2a 0d95952 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Oct 14 10:44:52 2011 -0500 Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into staging Reproduce steps: 1.with latest qemu.git master tree, to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 875723] Re: guest aborts when detaching a SR-IOV VF
I also tried this issue with Intel 82576EI NIC, and this normal VT-D NIC doesn't have this detachment issue. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/875723 Title: guest aborts when detaching a SR-IOV VF Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Guest will abort when detaching a SR-IOV VF. I'm using rhel6 and rhel6u1 as my guest. Firstly, I hot-plug a sr-iov VF to a guest. Then I detach the VF from the guest. At that time, guest aborts and qemu-kvm process aborts with the following message. qemu-system-x86_64: /workspace/qemu-kvm/memory.c:998: memory_region_destroy: Assertion `((mr-subregions)-tqh_first == ((void *)0))' failed. Aborted (core dumped) Reproduce steps: 1.start a rhel6 guest 2.attach a SR-IOV VF to the guest: device_add pci-assign,host=01:10.0,id=myNIC (I'm using 82576 Virtual Function.) 3.detach the VF from the guest: device_del myNIC (you'll find guest aborts) Current result: guest aborts and qemu process aborts Expected result: guest still alive To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/875723/+subscriptions
[Qemu-devel] [Bug 882358] Re: device assignment doesn't work: error: requires KVM support
This is because kvm is not enabled by default even if I add KVM support when configuring qemu. Now it got fixed by the following commit. author Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) committer Marcelo Tosatti mtosa...@redhat.com Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200) commit 7879db7e9c09b92d9af1c143fbe2cc212ec89e4b Revert qemu-kvm: set default accelerator via target.conf This reverts commit a5c40eb1aa929a03157252db7337bc4ddd2435be. Jan says: Unless you fully install qemu, that conf is not picked up (or an older version is used). I'd still like to see this working with qemu started from a build directory... Signed-off-by: Marcelo Tosatti mtosa...@redhat.com -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/882358 Title: device assignment doesn't work: error: requires KVM support Status in QEMU: Fix Released Bug description: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/882358/+subscriptions
[Qemu-devel] [Bug 882358] Re: device assignment doesn't work: error: requires KVM support
It works now. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/882358 Title: device assignment doesn't work: error: requires KVM support Status in QEMU: Fix Released Bug description: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/882358/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. ** Description changed: - qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b + qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b + or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 - It will costs about 180 seconds to booting up a rhel6 guest. But when I - use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in - about 50 seconds. I did the comparative test in the same box and using - the same command line to create a guest BTW, I tested qemu-kvm.git not - qemu.git before kernel.org was down. + It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu.git with commit edbb7c0, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest. + I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. Reproduce steps: - 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img + 1.with latest qemu.git master tree, to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img (It maybe cost about 180 seconds to boot up.) ** Description changed: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu.git with commit edbb7c0, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. + I found the following log in master tree. And that merger maybe introduced this issue in master tree. + commit 36f490b176afab3096e9c2877b365354f67e269d + Merge: ebffe2a 0d95952 + Author: Anthony Liguori aligu...@us.ibm.com + Date: Fri Oct 14 10:44:52 2011 -0500 + + Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into + staging + + Reproduce steps: 1.with latest qemu.git master tree, to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img (It maybe cost about 180 seconds to boot up.) ** Changed in: qemu Status: Invalid = New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: New Bug description: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu.git with commit edbb7c0, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. I found the following log in master tree. And that merger maybe introduced this issue in master tree. commit 36f490b176afab3096e9c2877b365354f67e269d Merge: ebffe2a 0d95952 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Oct 14 10:44:52 2011 -0500 Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into staging Reproduce steps: 1.with latest qemu.git master tree, to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 855664] Re: 64-bit windows guest cannot boot up
I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. ** Description changed: - qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b + qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b + or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using - the same command line to create a guest. BTW, I tested qemu-kvm.git not - qemu.git before kernel.org was down. + the same command line to create a guest. + + I found this bug in memory/queue branch of qemu.git on September 21st. + As some codes in memory branch were merged into master branch, the + master tree of qemu.git also has this issue now. + + I found the following git log in master tree. And that merger maybe introduced this issue in master tree. + commit 36f490b176afab3096e9c2877b365354f67e269d + Merge: ebffe2a 0d95952 + Author: Anthony Liguori aligu...@us.ibm.com + Date: Fri Oct 14 10:44:52 2011 -0500 + + Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into + staging Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img ** Changed in: qemu Status: Invalid = New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855664 Title: 64-bit windows guest cannot boot up Status in QEMU: New Bug description: qemu.git (memory/queue branch) commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b or qemu.git (master branch) commit: 8843cf40c0f482949e6ae9d0119e45d6b96fe890 kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using the same command line to create a guest. I found this bug in memory/queue branch of qemu.git on September 21st. As some codes in memory branch were merged into master branch, the master tree of qemu.git also has this issue now. I found the following git log in master tree. And that merger maybe introduced this issue in master tree. commit 36f490b176afab3096e9c2877b365354f67e269d Merge: ebffe2a 0d95952 Author: Anthony Liguori aligu...@us.ibm.com Date: Fri Oct 14 10:44:52 2011 -0500 Merge remote-tracking branch 'qemu-kvm-tmp/memory/batch' into staging Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855664/+subscriptions
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
** Description changed: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: - qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img - qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img - 2.save the guest: - on qemu monitor: migrate exec:dd of=/root/test-save.img - 3.quit from qemu: - q command on qemu monitor + qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img + qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img + 2.save the guest: + on qemu monitor: migrate exec:dd of=/root/test-save.img + 3.quit from qemu: + q command on qemu monitor 4.restore from img just saved: - qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img + qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: Fix Released Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/739088/+subscriptions
[Qemu-devel] [Bug 882358] Re: device assignment doesn't work: error: requires KVM support
** Attachment added: qemu configuration log https://bugs.launchpad.net/bugs/882358/+attachment/2574718/+files/configure.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/882358 Title: device assignment doesn't work: error: requires KVM support Status in QEMU: New Bug description: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/882358/+subscriptions
[Qemu-devel] [Bug 882358] Re: device assignment doesn't work: error: requires KVM support
** Attachment added: qemu compiling log https://bugs.launchpad.net/qemu/+bug/882358/+attachment/2574719/+files/make.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/882358 Title: device assignment doesn't work: error: requires KVM support Status in QEMU: New Bug description: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/882358/+subscriptions
[Qemu-devel] [Bug 882358] [NEW] device assignment doesn't work: error: requires KVM support
Public bug reported: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/882358 Title: device assignment doesn't work: error: requires KVM support Status in QEMU: New Bug description: qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890 I met the following error when do device assignment with qemu in kvm host. ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized ./x86_64-softmmu/qemu-system-x86_64 -device ? 21 | grep -i pci-assign -name pci-assign, bus PCI, desc pass through host pci devices to the guest When configuring the qemu, it prints KVM support yes.My qemu configuration log and compiling log are attached. But commit edbb7c0d doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/882358/+subscriptions
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
using the following command line to restore guest, it works for me now. qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img -incoming=/roo/test-save.img ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: Fix Released Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/739088/+subscriptions
[Qemu-devel] [Bug 877155] [NEW] VT-D NIC doesn't work in windows guest
Public bug reported: [This should be a kvm kernel bug. I met this issue with quemu and kvm for virtualization. For https://bugzilla.kernel.org is not available yet, I just file this bug here just for tracking. ] Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Using qemu and kvm upstream, VT-D NIC and SR-IOV VF don't work in Windows guest. I tried Windows XP, Vista, Win7, Win2k8 as a guest. And I used 82572 NIC and 82576 Virtual Function to assign to windows guest, and got the same result. Reproduce steps: 1.start a Windows guest with a NIC assigned: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=08:00.0 -net none -hda Windows.img 2.check network in the Windows guest. (You'll find the assigned NIC doesn't work in guest.) Current result: NIC doesn't work in Windows guest Expected result: NIC will work. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/877155 Title: VT-D NIC doesn't work in windows guest Status in QEMU: New Bug description: [This should be a kvm kernel bug. I met this issue with quemu and kvm for virtualization. For https://bugzilla.kernel.org is not available yet, I just file this bug here just for tracking. ] Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Using qemu and kvm upstream, VT-D NIC and SR-IOV VF don't work in Windows guest. I tried Windows XP, Vista, Win7, Win2k8 as a guest. And I used 82572 NIC and 82576 Virtual Function to assign to windows guest, and got the same result. Reproduce steps: 1.start a Windows guest with a NIC assigned: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=08:00.0 -net none -hda Windows.img 2.check network in the Windows guest. (You'll find the assigned NIC doesn't work in guest.) Current result: NIC doesn't work in Windows guest Expected result: NIC will work. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/877155/+subscriptions
[Qemu-devel] [Bug 875723] [NEW] guest aborts when detaching a SR-IOV VF
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Guest will abort when detaching a SR-IOV VF. I'm using rhel6 and rhel6u1 as my guest. Firstly, I hot-plug a sr-iov VF to a guest. Then I detach the VF from the guest. At that time, guest aborts and qemu-kvm process aborts with the following message. qemu-system-x86_64: /workspace/qemu-kvm/memory.c:998: memory_region_destroy: Assertion `((mr-subregions)-tqh_first == ((void *)0))' failed. Aborted (core dumped) Reproduce steps: 1.start a rhel6 guest 2.attach a SR-IOV VF to the guest: device_add pci-assign,host=01:10.0,id=myNIC (I'm using 82576 Virtual Function.) 3.detach the VF from the guest: device_del myNIC (you'll find guest aborts) Current result: guest aborts and qemu process aborts Expected result: guest still alive ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/875723 Title: guest aborts when detaching a SR-IOV VF Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1 qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7 Host Kernel Version:3.1.0-rc9+ Hardware: Westmere-EP SandyBridge platform Bug detailed description: -- Guest will abort when detaching a SR-IOV VF. I'm using rhel6 and rhel6u1 as my guest. Firstly, I hot-plug a sr-iov VF to a guest. Then I detach the VF from the guest. At that time, guest aborts and qemu-kvm process aborts with the following message. qemu-system-x86_64: /workspace/qemu-kvm/memory.c:998: memory_region_destroy: Assertion `((mr-subregions)-tqh_first == ((void *)0))' failed. Aborted (core dumped) Reproduce steps: 1.start a rhel6 guest 2.attach a SR-IOV VF to the guest: device_add pci-assign,host=01:10.0,id=myNIC (I'm using 82576 Virtual Function.) 3.detach the VF from the guest: device_del myNIC (you'll find guest aborts) Current result: guest aborts and qemu process aborts Expected result: guest still alive To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/875723/+subscriptions
[Qemu-devel] [Bug 799036] Re: NIC assignment order in command line make some NIC can't work
Yes, this bug is got fixed. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/799036 Title: NIC assignment order in command line make some NIC can't work Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158 qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349 Host Kernel Version:3.0.0-rc2+ Hardware: Westmere-EP platform Bug detailed description: -- When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 82572EI NIC statically assigned, the two NIC's order in command line may make 82586 NIC can't work in guest. command1: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.1 -device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img command2: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img Using command1 to create a guest, both two NICs works well in guest. While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get IP in guest. BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC. The only difference of the two command lines is the order of NICs assignment. And only the 82576(kawela) NIC have this problem, the other one 82572EI always works well. And sriov VF doesn't have this issue. A VF and a 82576 PF assigned to a guest always work well. I don't know the order of NIC assignment in qemu-system-x86_64 will make this difference in guest. Maybe it's a qemu bug ? Reproduce steps: 1.pci-stub the two NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC). Current result: 82576 PF and the other NIC in guest will work well regardless of what the order of assignment is. Expected result: To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/799036/+subscriptions
[Qemu-devel] [Bug 830558] Re: VF doesn't work in guest when not pinned with addr=
this bug doesn't exist in the latest qemu tree. ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/830558 Title: VF doesn't work in guest when not pinned with addr= Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5) kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7 qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274 Host Kernel Version:3.0.0+ Hardware: Westmere-EP platform Bug detailed description: -- SR-IOV VF NIC doesn't work in guest when not pinned pci address with addr=x05. Guest's dmesg shows Failed to initialize MSI-X interrupts. If not pinned an address with addr=0x05, the VF will be pinned to :00:03.0 by default, and that doesn't work. Normal vtd NIC assignment doesn't have this issue. commit:fda19064e of qemu-kvm.git is good. commit:44755ea36 of qemu-kvm.git is bad with this issue. There maybe something wrong between the two commit. Here's some dmesg info in the guest. dmesg in guest-- Intel(R) Virtual Function Network Driver - version 1.0.0-k0 Copyright (c) 2009 Intel Corporation. igbvf :00:03.0: setting latency timer to 64 igbvf :00:03.0: Failed to initialize MSI-X interrupts. igbvf :00:03.0: Intel(R) 82576 Virtual Function igbvf :00:03.0: Address: da:66:bb:e6:1e:f4 igbvf :00:03.0: MAC: 1 igbvf :00:03.0: Unable to allocate interrupt, Error: -1 Reproduce steps: 1.pci-stub the a VF in 82576 NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow (if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work) 3.check network in guest Current result: VF doesn't work in guest. Expected result: VF works well in guest. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/830558/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
I used the default 'memory/queue' branch when I filed this bug. The master tree doesn't have these two bugs, and I'll mark the bugs as invalid. Mark as invalid. ** Changed in: qemu Status: New = Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: Invalid Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest BTW, I tested qemu- kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 855664] Re: 64-bit windows guest cannot boot up
I used the default 'memory/queue' branch when I filed this bug. The master tree doesn't have this bug. Mark as invalid. ** Changed in: qemu Status: New = Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855664 Title: 64-bit windows guest cannot boot up Status in QEMU: Invalid Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using the same command line to create a guest. BTW, I tested qemu-kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855664/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
Eh? I can reproduce very easily and it always has this issue in the qemu.git upstream in the past two weeks. I used rhel5u5, rhel6, rhel6u1 or any other images as guest, and met the same issue. And this is not a platform specific issue. It can be reproduced in Westmere-EP and Sandybrige-EP platforms (I often test kvm on the two platforms.) ‘info kvm' doesn't return 'enabled' in my box. When we didn't have many bugs and all of our test cases passed in the past, 'info kvm' din't return 'enabled' either. Seems that there's no info document for kvm in my box all the time. And for guest, there's no 'rhgb' or 'quiet' in the boot command line. From my eyes, I see the guest is not overall slowdown. I redirect the boot log to serial port. The boot serial log of rhel6u1 guest is attached. For the attached boot log, before this line scsi 1:0:0:0: CD-ROM, seems not so slow, and after that, boot slower. but after this line Starting udev: udev: starting version 147, it's very very slow and I can see it just print one line after another line with my eyes. BTW, shutting down guest is also much slower than before. ** Attachment added: rhel6u1-guest-slow.log https://bugs.launchpad.net/qemu/+bug/855633/+attachment/2446943/+files/guest-rhel6u1-slow.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: New Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest BTW, I tested qemu- kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 855633] [NEW] guest boots up too slowly
Public bug reported: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest BTW, I tested qemu-kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img (It maybe cost about 180 seconds to boot up.) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: New Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest BTW, I tested qemu- kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 855664] [NEW] 64-bit windows guest cannot boot up
Public bug reported: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using the same command line to create a guest. BTW, I tested qemu-kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855664 Title: 64-bit windows guest cannot boot up Status in QEMU: New Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 64-bit Windows guest cannot boot up, but 32-bit windows guest can boot up successfully. For Win7, it will show blue scream of death when booting up. For Windows XP, the guest hangs without blue screen when booting up. But when I use qemu-kvm.git with commit a040d28b, I won't meet this issue. I did the comparative test in the same box and using the same command line to create a guest. BTW, I tested qemu-kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 -hda /root/win7-64bit.img To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855664/+subscriptions
[Qemu-devel] [Bug 855633] Re: guest boots up too slowly
sorry, the right command to reproduce is 'qemu-system-x86_64 -m 1024 -smp 2 -hda /root/rhel6.img'. I missed the '-hda' in the bug description. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/855633 Title: guest boots up too slowly Status in QEMU: New Bug description: qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34 It will costs about 180 seconds to booting up a rhel6 guest. But when I use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in about 50 seconds. I did the comparative test in the same box and using the same command line to create a guest BTW, I tested qemu- kvm.git not qemu.git before kernel.org was down. Reproduce steps: 1. to create a guest: qemu-system-x86_64 -m 1024 -smp 2 /root/rhel6.img (It maybe cost about 180 seconds to boot up.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/855633/+subscriptions
[Qemu-devel] [Bug 830558] Re: VF doesn't work in guest when not pinned with addr=
** Project changed: qemu-kvm = qemu -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/830558 Title: VF doesn't work in guest when not pinned with addr= Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5) kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7 qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274 Host Kernel Version:3.0.0+ Hardware: Westmere-EP platform Bug detailed description: -- SR-IOV VF NIC doesn't work in guest when not pinned pci address with addr=x05. Guest's dmesg shows Failed to initialize MSI-X interrupts. If not pinned an address with addr=0x05, the VF will be pinned to :00:03.0 by default, and that doesn't work. Normal vtd NIC assignment doesn't have this issue. commit:fda19064e of qemu-kvm.git is good. commit:44755ea36 of qemu-kvm.git is bad with this issue. There maybe something wrong between the two commit. Here's some dmesg info in the guest. dmesg in guest-- Intel(R) Virtual Function Network Driver - version 1.0.0-k0 Copyright (c) 2009 Intel Corporation. igbvf :00:03.0: setting latency timer to 64 igbvf :00:03.0: Failed to initialize MSI-X interrupts. igbvf :00:03.0: Intel(R) 82576 Virtual Function igbvf :00:03.0: Address: da:66:bb:e6:1e:f4 igbvf :00:03.0: MAC: 1 igbvf :00:03.0: Unable to allocate interrupt, Error: -1 Reproduce steps: 1.pci-stub the a VF in 82576 NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow (if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work) 3.check network in guest Current result: VF doesn't work in guest. Expected result: VF works well in guest. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/830558/+subscriptions
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
** Project changed: qemu-kvm = qemu -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: New Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/739088/+subscriptions
[Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with addr=
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5) kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7 qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274 Host Kernel Version:3.0.0+ Hardware: Westmere-EP platform Bug detailed description: -- SR-IOV VF NIC doesn't work in guest when not pinned pci address with addr=x05. Guest's dmesg shows Failed to initialize MSI-X interrupts. If not pinned an address with addr=0x05, the VF will be pinned to :00:03.0 by default, and that doesn't work. Normal vtd NIC assignment doesn't have this issue. commit:fda19064e of qemu-kvm.git is good. commit:44755ea36 of qemu-kvm.git is bad with this issue. There maybe something wrong between the two commit. Here's some dmesg info in the guest. dmesg in guest-- Intel(R) Virtual Function Network Driver - version 1.0.0-k0 Copyright (c) 2009 Intel Corporation. igbvf :00:03.0: setting latency timer to 64 igbvf :00:03.0: Failed to initialize MSI-X interrupts. igbvf :00:03.0: Intel(R) 82576 Virtual Function igbvf :00:03.0: Address: da:66:bb:e6:1e:f4 igbvf :00:03.0: MAC: 1 igbvf :00:03.0: Unable to allocate interrupt, Error: -1 Reproduce steps: 1.pci-stub the a VF in 82576 NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow (if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work) 3.check network in guest Current result: VF doesn't work in guest. Expected result: VF works well in guest. ** Affects: qemu-kvm Importance: Undecided Status: New ** Project changed: qemu = qemu-kvm -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/830558 Title: VF doesn't work in guest when not pinned with addr= Status in qemu-kvm: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5) kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7 qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274 Host Kernel Version:3.0.0+ Hardware: Westmere-EP platform Bug detailed description: -- SR-IOV VF NIC doesn't work in guest when not pinned pci address with addr=x05. Guest's dmesg shows Failed to initialize MSI-X interrupts. If not pinned an address with addr=0x05, the VF will be pinned to :00:03.0 by default, and that doesn't work. Normal vtd NIC assignment doesn't have this issue. commit:fda19064e of qemu-kvm.git is good. commit:44755ea36 of qemu-kvm.git is bad with this issue. There maybe something wrong between the two commit. Here's some dmesg info in the guest. dmesg in guest-- Intel(R) Virtual Function Network Driver - version 1.0.0-k0 Copyright (c) 2009 Intel Corporation. igbvf :00:03.0: setting latency timer to 64 igbvf :00:03.0: Failed to initialize MSI-X interrupts. igbvf :00:03.0: Intel(R) 82576 Virtual Function igbvf :00:03.0: Address: da:66:bb:e6:1e:f4 igbvf :00:03.0: MAC: 1 igbvf :00:03.0: Unable to allocate interrupt, Error: -1 Reproduce steps: 1.pci-stub the a VF in 82576 NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow (if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work) 3.check network in guest Current result: VF doesn't work in guest. Expected result: VF works well in guest. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-kvm/+bug/830558/+subscriptions
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
this issue occurred again. So reopen this bug.
I use upstream kvm.git ef7c782ea and qemu-kvm.git 44755ea36.
The host is rhel6.1 with lastest kvm and qemu-kvm installed, and its file
system type is ext4.
here's the dmesg info in rhel5u5 guest after being restored.
-log--
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: master: error (0x00?)
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x00 { }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: master: error (0x00?)
end_request: I/O error, dev hda, sector 32991
end_request: I/O error, dev hda, sector 32999
end_request: I/O error, dev hda, sector 33007
end_request: I/O error, dev hda, sector 4465351
Buffer I/O error on device hda1, logical block 558161
Aborting journal on device hda1.
lost page write due to I/O error on hda1
end_request: I/O error, dev hda, sector 4465359
Buffer I/O error on device hda1, logical block 558162
lost page write due to I/O error on hda1
end_request: I/O error, dev hda, sector 13447
Buffer I/O error on device hda1, logical block 1673
lost page write due to I/O error on hda1
__journal_remove_journal_head: freeing b_committed_data
journal commit I/O error
ext3_abort called.
EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
** Project changed: qemu = qemu-kvm
** Changed in: qemu-kvm
Status: Fix Released = New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
Title:
I/O errors after Save/Restore
Status in qemu-kvm:
New
Bug description:
qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516
( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16
17:04:16 2011 -0300)
kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f
After restoring from saved img, some I/O errors appear in dmesg and
file system is read-only. I'm sure that the guest runs normally
before saving. See the pictures attached in detail.
Reproduce steps:
1.create a guest:
qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2
/root/test0320.img
qemu-system-x86_64 -m 256 -net
nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup
-hda /root/test0320.img
2.save the guest:
on qemu monitor: migrate exec:dd of=/root/test-save.img
3.quit from qemu:
q command on qemu monitor
4.restore from img just saved:
qemu-system-x86_64 -m 256 -net
nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup
-incoming=/roo/test-save.img
5.see dmesg in restored guest, you'll find some I/O errors. And run some
commands such as ps, touch,reboot and so on. Then some I/O errors
appear.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu-kvm/+bug/739088/+subscriptions
[Qemu-devel] [Bug 802588] Re: Latest GIT version fails to compile on Linux - setjmp.h problem
this issue got fixed. It doesn't exist in qemu-kvm.git fda19064e889d4419dd3dc69ca8e6e7a1535fdf5 ** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/802588 Title: Latest GIT version fails to compile on Linux - setjmp.h problem Status in QEMU: Fix Released Bug description: Git version: f26e428da505709ec03b2ed2c9eb3db82b30bd7b Gcc: 4.6.1 Host: Debinan/x86_64 Fails to compile at In file included from /usr/include/png.h:518:0, from ui/vnc-enc-tight.c:37: /usr/include/pngconf.h: At top level: /usr/include/pngconf.h:371:21: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘.’ token /usr/include/pngconf.h:372:12: error: unknown type name ‘__dont__’ /usr/include/pngconf.h:372:29: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘it’ /usr/include/pngconf.h:372:29: error: unknown type name ‘it’ Looking at pngconf.h around line 370 gives the reason for the compilation failure: # ifdef _SETJMP_H /* If you encounter a compiler error here, see the explanation * near the end of INSTALL. */ __pngconf.h__ in libpng already includes setjmp.h; __dont__ include it again.; # endif To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/802588/+subscriptions
[Qemu-devel] [Bug 802588] Re: Latest GIT version fails to compile on Linux - setjmp.h problem
I found this issue is also exist in latest qemu-kvm.git commit d58931037dbb4fbc2fbb33858629d3fabfd1b0d4 Merge: bcd4f22... f8121c4... Author: Avi Kivity a...@redhat.com Date: Tue Jun 28 15:11:13 2011 +0300 Git log shows it has merged commit 2fb0c09f4f*, but the bug is not fixed. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/802588 Title: Latest GIT version fails to compile on Linux - setjmp.h problem Status in QEMU: New Bug description: Git version: f26e428da505709ec03b2ed2c9eb3db82b30bd7b Gcc: 4.6.1 Host: Debinan/x86_64 Fails to compile at In file included from /usr/include/png.h:518:0, from ui/vnc-enc-tight.c:37: /usr/include/pngconf.h: At top level: /usr/include/pngconf.h:371:21: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘.’ token /usr/include/pngconf.h:372:12: error: unknown type name ‘__dont__’ /usr/include/pngconf.h:372:29: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘it’ /usr/include/pngconf.h:372:29: error: unknown type name ‘it’ Looking at pngconf.h around line 370 gives the reason for the compilation failure: # ifdef _SETJMP_H /* If you encounter a compiler error here, see the explanation * near the end of INSTALL. */ __pngconf.h__ in libpng already includes setjmp.h; __dont__ include it again.; # endif To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/802588/+subscriptions
[Qemu-devel] [Bug 799036] Re: NIC assignment order in command line make some NIC can't work
dmesg and lspci logs are attached as a tar package. There are many logs in it, please read README.txt first, which will tell you which log is in which case. ** Attachment added: vtd-NIC-assignment-order-issue.tar https://bugs.launchpad.net/qemu/+bug/799036/+attachment/2182799/+files/vtd-NIC-assignment-order-issue.tar -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/799036 Title: NIC assignment order in command line make some NIC can't work Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158 qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349 Host Kernel Version:3.0.0-rc2+ Hardware: Westmere-EP platform Bug detailed description: -- When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 82572EI NIC statically assigned, the two NIC's order in command line may make 82586 NIC can't work in guest. command1: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.1 -device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img command2: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img Using command1 to create a guest, both two NICs works well in guest. While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get IP in guest. BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC. The only difference of the two command lines is the order of NICs assignment. And only the 82576(kawela) NIC have this problem, the other one 82572EI always works well. And sriov VF doesn't have this issue. A VF and a 82576 PF assigned to a guest always work well. I don't know the order of NIC assignment in qemu-system-x86_64 will make this difference in guest. Maybe it's a qemu bug ? Reproduce steps: 1.pci-stub the two NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC). Current result: 82576 PF and the other NIC in guest will work well regardless of what the order of assignment is. Expected result: To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/799036/+subscriptions
[Qemu-devel] [Bug 799036] Re: NIC assignment order in command line make some NIC can't work
Without fixing address of the device, the first device will get 00:03.0 in my guest, and the second get 00:04.0. And when NIC 82576 is in the first order, it will get 00:03.0 in my guest, and it will not working. If I fix 82576 NIC using addr=0x3 and other using addr=0x4, 82576 NIC in guest will get 00:03.0 and the other will get 04:00.0. If fixing address, the assignment order doestn't matter the result. With addr=0x3, NIC 82576 always works well in guest; but with addr=0x4, 82580 or some other NIC will work well in my guest. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/799036 Title: NIC assignment order in command line make some NIC can't work Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158 qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349 Host Kernel Version:3.0.0-rc2+ Hardware: Westmere-EP platform Bug detailed description: -- When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 82572EI NIC statically assigned, the two NIC's order in command line may make 82586 NIC can't work in guest. command1: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.1 -device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img command2: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img Using command1 to create a guest, both two NICs works well in guest. While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get IP in guest. BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC. The only difference of the two command lines is the order of NICs assignment. And only the 82576(kawela) NIC have this problem, the other one 82572EI always works well. And sriov VF doesn't have this issue. A VF and a 82576 PF assigned to a guest always work well. I don't know the order of NIC assignment in qemu-system-x86_64 will make this difference in guest. Maybe it's a qemu bug ? Reproduce steps: 1.pci-stub the two NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC). Current result: 82576 PF and the other NIC in guest will work well regardless of what the order of assignment is. Expected result: To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/799036/+subscriptions
[Qemu-devel] [Bug 754591] Re: NIC doesn't work when it had been used before
It was fixed in kvm.git. This bug is fixed in the kvm upstream. It was fixed in kvm.git f8fcfd7 by alex.william...@redhat.com. commit f8fcfd775523347afe460dc3a0f45d0479e784a2 Author: Alex Williamson alex.william...@redhat.com Date: Tue May 10 10:02:39 2011 -0600 KVM: Use pci_store/load_saved_state() around VM device usage Store the device saved state so that we can reload the device back to the original state when it's unassigned. This has the benefit that the state survives across pci_reset_function() calls via the PCI sysfs reset interface while the VM is using the device. Signed-off-by: Alex Williamson alex.william...@redhat.com Acked-by: Avi Kivity a...@redhat.com Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org ** Changed in: qemu Status: New = Fix Committed ** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/754591/+subscriptions
[Qemu-devel] [Bug 799036] [NEW] NIC assignment order in command line make some NIC can't work
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158 qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349 Host Kernel Version:3.0.0-rc2+ Hardware: Westmere-EP platform Bug detailed description: -- When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 82572EI NIC statically assigned, the two NIC's order in command line may make 82586 NIC can't work in guest. command1: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.1 -device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img command2: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img Using command1 to create a guest, both two NICs works well in guest. While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get IP in guest. BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC. The only difference of the two command lines is the order of NICs assignment. And only the 82576(kawela) NIC have this problem, the other one 82572EI always works well. And sriov VF doesn't have this issue. A VF and a 82576 PF assigned to a guest always work well. I don't know the order of NIC assignment in qemu-system-x86_64 will make this difference in guest. Maybe it's a qemu bug ? Reproduce steps: 1.pci-stub the two NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC). Current result: 82576 PF and the other NIC in guest will work well regardless of what the order of assignment is. Expected result: ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/799036 Title: NIC assignment order in command line make some NIC can't work Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158 qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349 Host Kernel Version:3.0.0-rc2+ Hardware: Westmere-EP platform Bug detailed description: -- When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 82572EI NIC statically assigned, the two NIC's order in command line may make 82586 NIC can't work in guest. command1: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0e:00.1 -device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img command2: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img Using command1 to create a guest, both two NICs works well in guest. While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get IP in guest. BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC. The only difference of the two command lines is the order of NICs assignment. And only the 82576(kawela) NIC have this problem, the other one 82572EI always works well. And sriov VF doesn't have this issue. A VF and a 82576 PF assigned to a guest always work well. I don't know the order of NIC assignment in qemu-system-x86_64 will make this difference in guest. Maybe it's a qemu bug ? Reproduce steps: 1.pci-stub the two NIC 2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC). Current result: 82576 PF and the other NIC in guest will work well regardless of what the order of assignment is. Expected result: To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/799036/+subscriptions
[Qemu-devel] [Bug 754591] Re: NIC doesn't work when it had been used before
I can reproduce it stably. I use igb driver for my NIC. And Alex Williamson is on the way to fix it. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now).
[Qemu-devel] [Bug 754591] Re: NIC doesn't work when it had been used before
hot-plug NIC doesn't have this issue. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now).
[Qemu-devel] [Bug 730441] Re: NIC doesn't work with pci=nomsi in grub.conf
** Changed in: qemu Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/730441 Title: NIC doesn't work with pci=nomsi in grub.conf Status in QEMU: Fix Released Bug description: qemu-kvm Commit:27f368604a3d27ca4ddac0f62a6928bb93cdacd5 NIC doesn't work with pci=nomsi in grub.conf. Neither static assignment nor hot-plug assignment works. And when using qemu-kvm's commit 08bb9f6b1a5d8f4f5dd5bafad2876067797cb8b4， qemu doesn't have this problem. Reproduce steps: 1.build and install qemu-kvm 2.plug off a NIC device from host (BDF of NIC: 13:00.0) 3.start a guest (grub.conf has a configuration pci=nomsi) : qemu-system-x86_64 -m 512 -smp 2 -device pci_assign,host=13:00.0 -hda /share/ia32e-rhel5u5.img 4.[Guest] dhclient The NIC assigned before cannot get an IP address. It doesn't work.
[Qemu-devel] [Bug 730441] Re: NIC doesn't work with pci=nomsi in grub.conf
this bug is fixed in latest commit. kvm.git Commit:b35049715d619c9badaea07dec766787b433facf qemu-kvm Commit:27f368604a3d27ca4ddac0f62a6928bb93cdacd5 ** Changed in: qemu Status: New = Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/730441 Title: NIC doesn't work with pci=nomsi in grub.conf Status in QEMU: Fix Committed Bug description: qemu-kvm Commit:27f368604a3d27ca4ddac0f62a6928bb93cdacd5 NIC doesn't work with pci=nomsi in grub.conf. Neither static assignment nor hot-plug assignment works. And when using qemu-kvm's commit 08bb9f6b1a5d8f4f5dd5bafad2876067797cb8b4， qemu doesn't have this problem. Reproduce steps: 1.build and install qemu-kvm 2.plug off a NIC device from host (BDF of NIC: 13:00.0) 3.start a guest (grub.conf has a configuration pci=nomsi) : qemu-system-x86_64 -m 512 -smp 2 -device pci_assign,host=13:00.0 -hda /share/ia32e-rhel5u5.img 4.[Guest] dhclient The NIC assigned before cannot get an IP address. It doesn't work.
[Qemu-devel] [Bug 754591] [NEW] NIC doesn't work when it had been used before
Public bug reported: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now). ** Affects: qemu Importance: Undecided Status: New ** Tags: vt-d -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now).
[Qemu-devel] [Bug 754591] Re: NIC doesn't work when it had been used before
** Attachment added: dmesg_guest_NIC https://bugs.launchpad.net/bugs/754591/+attachment/125/+files/dmesg.txt -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now).
[Qemu-devel] [Bug 754591] Re: NIC doesn't work when it had been used before
qemu-kvm.git bad:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 and 9488459ff2ab113293586c1c36b1679bb15deee good:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/754591 Title: NIC doesn't work when it had been used before Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64): All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows):All kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- NIC doesn't work when it had been used before. Statically assign a NIC to guest, it works well. Then shutdown the guest, and assign the same NIC to a guest again. The NIC doesn't work. The dmesg of the guest is as following. -- Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2 Copyright (c) 2007-2009 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 igb :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 igb :00:03.0: setting latency timer to 64 alloc irq_desc for 24 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 24 for MSI/MSI-X alloc irq_desc for 25 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 25 for MSI/MSI-X alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 igb :00:03.0: irq 26 for MSI/MSI-X igb :00:03.0: PHY reset is blocked due to SOL/IDER session. igb :00:03.0: The NVM Checksum Is Not Valid igb :00:03.0: PCI INT A disabled igb: probe of :00:03.0 failed with error -5 Reproduce steps: 1.statically assign a NIC to a guest, check if it works well 2.shutdown the guest. 3.statically assign the same NIC to a guest (NIC doesn't work now).
[Qemu-devel] [Bug 744195] Re: guest cannot boot with 8 VFs or more
a related issues was reported and fiexed before, but the two is not the same problem. http://sourceforge.net/tracker/?func=detailaid=2847560group_id=180599atid=893831 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/744195 Title: guest cannot boot with 8 VFs or more Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows): Linux kvm.git Commit:a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f qemu-kvm Commit:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- Guest cannot boot with 8 VFs or more VFs, but guest can boot with 7 VFs. If you assign hot-plug VFs, after you assigning the 8th VF, you may get the following message in host. kvm_alloc_slot: no free slot available. And the guest aborts. Reproduce steps: 1.try to create a guest with 8 VFs:(the guest cannot boot) qemu-system-x86_64 -smp 2 -m 1024 -net none -hda /root/rhel6.1-beta1.img -device pci-assign,host=04:10.0 -device pci-assign,host=04:10.1 -device pci-assign,host=04:10.2 -device pci-assign,host=04:10.3 -device pci-assign,host=04:10.4 -device pci-assign,host=04:10.5 -device pci-assign,host=04:10.6 -device pci-assign,host=04:10.7 2.If you want to assign 8 hot-plug VFs, you may use following command in qemu monitor after you start a guest. device_add pci-assign,host=00:19.0,id=my_nic
[Qemu-devel] [Bug 744195] [NEW] guest cannot boot with 8 VFs or more
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows): Linux kvm.git Commit:a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f qemu-kvm Commit:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- Guest cannot boot with 8 VFs or more VFs, but guest can boot with 7 VFs. If you assign hot-plug VFs, after you assigning the 8th VF, you may get the following message in host. kvm_alloc_slot: no free slot available. And the guest aborts. Reproduce steps: 1.try to create a guest with 8 VFs:(the guest cannot boot) qemu-system-x86_64 -smp 2 -m 1024 -net none -hda /root/rhel6.1-beta1.img -device pci-assign,host=04:10.0 -device pci-assign,host=04:10.1 -device pci-assign,host=04:10.2 -device pci-assign,host=04:10.3 -device pci-assign,host=04:10.4 -device pci-assign,host=04:10.5 -device pci-assign,host=04:10.6 -device pci-assign,host=04:10.7 2.If you want to assign 8 hot-plug VFs, you may use following command in qemu monitor after you start a guest. device_add pci-assign,host=00:19.0,id=my_nic ** Affects: qemu Importance: Undecided Status: New ** Bug watch added: SourceForge.net Tracker #2847560 http://sourceforge.net/support/tracker.php?aid=2847560 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/744195 Title: guest cannot boot with 8 VFs or more Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):All Guest OS (ia32/ia32e/IA64): All Guest OS Type (Linux/Windows): Linux kvm.git Commit:a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f qemu-kvm Commit:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a Host Kernel Version:2.6.38+ Hardware:Westmere-EP / Sandy Bridge Bug detailed description: -- Guest cannot boot with 8 VFs or more VFs, but guest can boot with 7 VFs. If you assign hot-plug VFs, after you assigning the 8th VF, you may get the following message in host. kvm_alloc_slot: no free slot available. And the guest aborts. Reproduce steps: 1.try to create a guest with 8 VFs:(the guest cannot boot) qemu-system-x86_64 -smp 2 -m 1024 -net none -hda /root/rhel6.1-beta1.img -device pci-assign,host=04:10.0 -device pci-assign,host=04:10.1 -device pci-assign,host=04:10.2 -device pci-assign,host=04:10.3 -device pci-assign,host=04:10.4 -device pci-assign,host=04:10.5 -device pci-assign,host=04:10.6 -device pci-assign,host=04:10.7 2.If you want to assign 8 hot-plug VFs, you may use following command in qemu monitor after you start a guest. device_add pci-assign,host=00:19.0,id=my_nic
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
this bug is fixed in the latest qemu-kvm.git: 2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: Fix Released Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear.
[Qemu-devel] [Bug 739092] Re: guest hangs when using network after live migration
this bug is fixed in the latest qemu-kvm.git: 2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a ** Changed in: qemu Status: New = Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739092 Title: guest hangs when using network after live migration Status in QEMU: Fix Released Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.com Date: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f Guest hangs when I run command ssh/netstat using network after live migration. ssh or netstat hangs even if I press Ctrl+C to interrupt. And I cannnot connect the guest using ssh GustIP from the host, though the sshd is still running in the guest. Reproduce steps: 1.start a tcp daemon for migration: qemu-system-x86_64 -m 256 -smp 4 -incoming tcp:localhost: -no-acpi -net nic,macaddr=00:16:3e:63:d5:90,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/lv.img 2.create a guest: qemu-system-x86_64 -m 256 -smp 4 -no-acpi -net nic,macaddr=00:16:3e:63:d5:90,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/lv.img 3.migration: migrate tcp:localhost: 4.run command in guest: ssh root@192.168.1.177
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
** Attachment added: dmesg after restoring https://bugs.launchpad.net/qemu/+bug/739088/+attachment/1925364/+files/restore1.jpg -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: New Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear.
[Qemu-devel] [Bug 739088] Re: I/O errors after Save/Restore
** Attachment added: running commands after restoring https://bugs.launchpad.net/qemu/+bug/739088/+attachment/1925365/+files/restore2.jpg -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/739088 Title: I/O errors after Save/Restore Status in QEMU: New Bug description: qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516 ( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16 17:04:16 2011 -0300) kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f After restoring from saved img, some I/O errors appear in dmesg and file system is read-only. I'm sure that the guest runs normally before saving. See the pictures attached in detail. Reproduce steps: 1.create a guest: qemu-img create -b /share/xvs/img/app/ia32e_SMP.img -f qcow2 /root/test0320.img qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img 2.save the guest: on qemu monitor: migrate exec:dd of=/root/test-save.img 3.quit from qemu: q command on qemu monitor 4.restore from img just saved: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -incoming=/roo/test-save.img 5.see dmesg in restored guest, you'll find some I/O errors. And run some commands such as ps, touch,reboot and so on. Then some I/O errors appear.
