Also, try as I might, I have not been able to reproduce this problem
using kvm alone on the command line (without libvirt).
I see that libvirt was merged twice, from 0.4.6-5ubuntu2 to
0.5.1-4ubuntu1, and then to 0.6.0-1ubuntu1 shortly before Jamie's
report. I'm thinking that there may have been a regression somewhere in
there.
I have posted a message to the kvm upstream mailing list, asking if
anyone there is familiar with the problem.
Finally, I'm marking this 'Incomplete' against kvm (but leaving it open
against libvirt) until someone can show me how to reproduce this problem
using KVM alone.
:-Dustin
** Changed in: kvm (Ubuntu Jaunty)
Status: Triaged => Incomplete
** Changed in: kvm
Importance: Unknown => Undecided
** Changed in: kvm
Status: Unknown => New
** Changed in: kvm
Bugwatch: SourceForge.net Tracker #2067179 => None
--
virtio on hardy guest and jaunty host (kvm 84) is broken
https://bugs.launchpad.net/bugs/331128
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
