Red Hat Bugzilla – Bug 906940
Hypervisor default (i.e.rtl8139)
Last modified: 2013-02-07 16:21:45 EST
Description of problem:
Doing a file transfer between Fedora host running samba and Windows2008R2 guest using a hypervisor default network card results in large file transfers failing. (8Gig file transfer)
The guest displays connection lost message during the file copy. Requires reboot of the guest to fix.
Version-Release number of selected component (if applicable):
qemu-kvm (Latest Fedora 18) QEMU emulator version 1.2.2 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard
Setup a Windows2008R2 server with default hypervisor card model on a routed network. Copy a file from the hosts smb file share to the guests local drive of 8Gigs or more.
Steps to Reproduce:
1. Use explorer and connect smb share (i.e. \\10.10.5.236\gcarter for example)
2. Drag a large folder onto the desktop of the guest from the smb share
3. Watch the network die on the guest side, requires reboot to fix.
Guest complains network or smb has lost connection after a while. Doesn't seem consistent either, sometimes it dies at 4GB, others at 7Gig. It is random in the amount of data that is copied before the network card fails on the guest, which is listed as a rtl8139
Should copy the file.
This can be fixed if you instead choose or replace the network card on the w2008r2 host with instead of a hypervisor default, you pick the e1000. Then things work fine.
Fedora won't change the default card. You can use virt-manager or GNOME Boxes to create a guest with the "right" card for your OS.
Exactly what is the "right" card for your OS?
During setup, when I installed the Windows 2008R2 on the Fedora host, the virt-manager selected Hypervisor default as the card for the guest.
I am not sure I understand what you mean by "right" card?
Are you saying virt-manager has a bug and selected the wrong card for the guest selection I made? (i.e. Windows 2008 Server)
If so what is the correct card selection for the qemu-kvm guest of Windows 2008, and why doesn't the virt-manager select it at creation time?
If you selected Windows 2008 R2 during virt-manager installation,
then virt-manager should probably have selected a better
card. Looking in the current libosinfo database[*] unfortunately
it doesn't seem to have a suitable entry for a virtio-net card
and driver for any Windows. So it's probably selecting the
In any case, *if* you used virt-manager and selected Windows 2008 R2,
then it may be a bug in virt-manager, so reopening this bug and
assigning it to virt-manager would be appropriate in that case.
[*] Also virt-manager doesn't use libosinfo yet, but that's
going to be fixed.