[Bug 1204162] Win10 in all versions have no network
https://bugzilla.suse.com/show_bug.cgi?id=1204162 https://bugzilla.suse.com/show_bug.cgi?id=1204162#c20 --- Comment #20 from ulfbart <ub22@gmx.net> --- (In reply to Lin Ma from comment #13)
Let's record some general information first: * Do not use PCI nic(E.g. rtl8139) in a PCIe capable of VM. Your VM's machine type is pc-q35-{6,7}.x, It offers PCIe support. (According to comment#7, VM win10_21H2x64's nic model is rtl8139)
* No matter how this issue is handled, Using paravirtualized devices(E.g. virtio-net) rather than emulated devices(E.g. E1000e or rtl8139) is recommended, Paravirtualized devices can provide better performance. (According to comment#5 and #7, VM win10 is using e1000e, VM win10_21H2x64 is using rtl8139). But we know that using paravirtualized devices in windows VM requires additional paravirtualized device drivers. If you'd like to do so, SUSE offers paravirtualized device drivers for windows at: https://www.suse.com/download/suse-vmdp/ You can download .exe or .iso
OK, Now let's take a look at this issue. * VM's firmware type has nothing to do with this issue. * The combination of VM's machine type + E1000e + Windows version triggers this issue.
Please refer to this table: ---------------------------------------------------------------- | pc-q35-6.0 | pc-q35-6.1 or newer ---------------------------------------------------------------- Win11 with e1000e | Pass | Pass ---------------------------------------------------------------- Win10_1909 with e1000e | Pass | Failed ---------------------------------------------------------------- Win10_1909 with virtio-net | Pass | Pass ---------------------------------------------------------------- (I didn't test other win10 revision)
Meanwhile, This table can explain the information in comment#1: why the network doesn't work with new XML and why network works with old XML.
Qemu commit 211afe5c(v6.2.0-rc1~6^2~11, hw/i386/acpi-build: Deny control on PCIe Native Hot-plug in _OSC) introduces this "issue". I won't call it's a qemu bug because I'm not familiar with windows device drivers at all, can't dig into it.
Workaround, Any of below options is fine:
* Manually edit VM config to use pc-q35-6.0 rather than pc-q35-7.1 through virsh or virt-manager's XML Editor.
* Using virtio-net instead of e1000e/rtl8139.(vmdp-win driver is required) E.g. <interface type="network"> <mac address="xx:xx:xx:xx:xx:xx"/> <source network="default"/> <model type="virtio"/> </interface>
* Keep pc-q35-7.1, Deal with yellow bang devices: "Uninstall device" -> "Scan for hardware changes" through "Device Manager". (According to comment#10, The VM has lots of yellow bang devices, They're not working correctly)
BTW, Comment#4 shows the VM has been configured spice-channel virtual device. When you installs vmdp-win driver in your windows VM, You can install virtio drivers and spice vdagent together by: setup.exe /vd_agent
The combination of spice channel + spice vdagent provide ability of copy/paste between host/guest.
After longer time (config not touched since them) I started the Win10 again, but seams that this workaround don't work anymore :-( -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com