Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 2022 and Red Hat VirtIO Ethernet Adapter #998

Closed
Quembar opened this issue Nov 16, 2023 · 3 comments
Closed

Windows 2022 and Red Hat VirtIO Ethernet Adapter #998

Quembar opened this issue Nov 16, 2023 · 3 comments
Assignees
Labels
Bug Bug

Comments

@Quembar
Copy link

Quembar commented Nov 16, 2023

Describe the bug
The installation of virtio-win-0.1.240 ends up without the installed NIC-Drv: 'Red Hat VirtIO Ethernet Adapter'
In Network setting I does not see a NIC

To Reproduce
Install a fresh Windows Server 2022 Standard Evalution ans install the libvirt-tools 0.1.240 afterwards.

Expected behavior
I expect a visible NIC to configure the LAN-Access

Screenshots
231116_110348-001
231116_110524-001

Host:

  • Disto: [openSUSE]
  • Kernel
    Linux jupiter 5.14.21-150400.24.97-default Big problems with tcp offload #1 SMP PREEMPT_DYNAMIC Fri Oct 27 10:29:06 UTC 2023 (8546fda) x86_64 x86_64 x86_64 GNU/Linux
  • QEMU version
    6.2.0
  • QEMU command line
  • libvirt version
    8.0.0
  • libvirt XML file

VM:

  • Windows version
    Windows Server 2022 Standard Evalution
  • Which driver has a problem
    Red Hat VirtIO Ethernet Adapter

Additional context
The same issue occurs if I use the RTL8139 NIC as device in the config of the VM
There are other VM (Windows Server 2019 Standard Evalution) in this hypervisor running w/o problems. Even if I update a Win 2019 Srv VM with the new virtio-tools 0.1.240 the NIC remain visible.

@sb-ntnx
Copy link
Contributor

sb-ntnx commented Nov 16, 2023

Duplicate of #750, not specific to virtio-win drivers suite and affects only (so far) German localization.

@zalnaRs
Copy link

zalnaRs commented Jul 21, 2024

Duplicate of #750, not specific to virtio-win drivers suite and affects only (so far) German localization.

and hungarian

@YanVugenfirer
Copy link
Collaborator

@zalnaRs Thanks a lot for the update! We are currently discussing this issues with MS. While they are going to fix it in the upcoming Windows releases, we definitely need to know more in the impact in the currently released Windows versions in order to convince them to fix.
Can you please tell what Windows version(s) are affected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug
Projects
None yet
Development

No branches or pull requests

4 participants