This is no longer a problem with 2.6.37-8.21-generic 2.6.37-rc4.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs
** Tags added: kernel-series-unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/685991
Title:
cannot kill kvm process that uses 'tap'
--
Ubuntu-server-bugs mailing list
Ubunt
Ah, there you go - 2.6.37.7.9 (still default with natty) fails, 2.6.38.8
succeeds.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/685991
Title:
cannot kill kvm process that uses 't
Actually, compiling my own kernel from
git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
that kernel also works?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/685991
Title:
cannot
No, I think that's in the natty kernel already, so guess not...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/685991
Title:
cannot kill kvm process that uses 'tap'
--
Ubuntu-ser
I'd guess that upstream commit 853dc2e03ddd0c49885ed55c48755d2b1073122a
was involved in fixing it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/685991
Title:
cannot kill kvm proc
This bug does NOT happen with the latest kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undeci
Yeah this really sounds like a kernel refcount bug. However, I'll
try to reproduce with upstream kvm, and then upstream latest kernel.
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => High
**
