This bug was fixed in the package kvm - 1:84+dfsg-0ubuntu3
---
kvm (1:84+dfsg-0ubuntu3) jaunty; urgency=low
[ Reviewed Ubuntu patches with KVM/QEMU upstream, Anthony Liguori ]
* debian/patches/03_bios_no_ssp.patch: DROPPED, included upstream
* debian/patches/06_no_system_linux_k
Okay, the fix for this bug will be to update the kvm-ifup script.
It's determination of the bridge device is quite simply broken.
For now, let's hardcode and require the bridge device to be "br0" for
this script to operate properly. That should be the case in most
reasonable setups. We can cons
Hello Soren!
My concern was neither the non-existance or _your_ interest to write a
better solution, nor the fact that you inherit the bug from upstream.
Not even that it exists, bugs are perfectly fine.
My disappointment that I was interested in writing a better solution,
offered so, but lacked
Our kvm packages are based on Debian's, so you'll find the same script
there, I'm afraid.
Indeed, KVM is Ubuntu's recommended hypervisor, and the recommended way
to use it is through libvirt. libvirt handles all the networking setup
you should need for kvm.
It's quite hard to provide a qemu style
Hello Matt,
just for the record, I retract my year old offer "willing to provide a
patch", because in the mean time I switched back to Debian.
Should anybody make a statement that Ubuntu is not responsive to bugs, I
may consider to mention this bug. The help offers in this bug were
ignored all th
