Public bug reported:
Booting an image that uses linux-kvm from the Ubuntu archive fails to
find a network when using a minimal qemu commandline:
kvm -m 256 -net nic -net user,id=user.0,hostfwd=tcp::5555-:22 -drive
file=boot-disk.img,if=virtio -drive file=seed.iso,if=virtio,media=cdrom
This fails because:
-net nic[,vlan=n][,macaddr=mac][,model=type]
[,name=name][,addr=addr][,vectors=v]
[...] The NIC is an e1000 by default on the PC target.
e1000 is a sensible least-common-denominator driver for use on a generic
hypervisor, because it's old and simple and has maximum compatibility
with a range of possible guest OSes.
But it's clearly inferior to virtio in every other way, and I don't
think we want to enable the e1000 in the linux-kvm build - I think we
want people to configure their VMs to use virtio instead of e1000, which
is the default in various frontends to qemu. I think anyone who is
configuring a kvm instance for running Linux as a guest, and uses e1000
instead of virtio, has it misconfigured.
Would it therefore make sense at this point in time to change the
default NIC driver for qemu from e1000 to virtio?
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776696
Title:
sensible default NIC for x86? (virtio, not e1000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776696/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
