Indeed, with qemu 1.5 we did not observed this issue at all.
Sorry, but I don't have the resources at the moment to do the bisecting.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1353947
Title:
Hy
Hello Serge,
I agree that there is probably some missing feature in the guest kernel.
However, I don't believe it is acceptable for the hyper-visor kernel to be
affected from this.
Actually, this is a security issue if a VM user can crash i't Host kernel and
probably some other VMs as well.
--
Can't run apport-collect after the kernel hang
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1353947
Title:
Hypervisor with QEM
Hi Serge,
1. Please see the table below
2. We also observed this issue with Intel NICs
===
GuestOS | Guestkernel | HostOS | Hostkernel
Public bug reported:
The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
The VM network interface is attached to a PCI virtual function (SR-IOV).
When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor
hang shortly after the VM is loaded
We observed t
