You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
When running runltp-ng on openSUSE Tumbleweed (comes with QEMU 5.0.0) I notice that the guest VM created does not get a network interface card (NIC) by default, where as VM guests created openSUSE Leap 15.1 (QEMU 3.1.1.1) does get one.
Right now I just work around this by passing -nic user,model=virtio-net-pci inside the backend option opts.
Maybe its worth always passing a NIC option to QEMU explicitly? (Since backends needs to be able to reach internet after a successfull login/boot is one of the requirements of runltp-ng)
The text was updated successfully, but these errors were encountered:
Maybe we should use virtio NIC by default? All cloud providers should be using virtio nics, so using virtio will make testing more relevant to real world usage of VMs.
Maybe we should use virtio NIC by default? All cloud providers should be using virtio nics, so using virtio will make testing more relevant to real world usage of VMs.
I second that.
It would certainly help in my use case as well.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When running runltp-ng on openSUSE Tumbleweed (comes with QEMU 5.0.0) I notice that the guest VM created does not get a network interface card (NIC) by default, where as VM guests created openSUSE Leap 15.1 (QEMU 3.1.1.1) does get one.
Right now I just work around this by passing
-nic user,model=virtio-net-pci
inside the backend optionopts
.Maybe its worth always passing a NIC option to QEMU explicitly? (Since backends needs to be able to reach internet after a successfull login/boot is one of the requirements of runltp-ng)
The text was updated successfully, but these errors were encountered: