Windows 2008 strange network issue

[tincboy]

I've create a Windows 2008 VM on my new server just like the many old ones,
But in this new server, If a Win2008 VM download a file with speed more than 25 mbps it's network become disconnected and it can't reach the gateway any more,
Anyone familiar with this situation?

 

[tincboy]

After it becomes inaccessible the only way to fix network is to power off and start the VM

 

[mmenaz]

I had in the past with Windows guests in general and virtio, never tried with 2008 though. Connectivity was working again disabling/enabling the nic, AFAIR, without rebooting.
Two workaround:
a) use Intel e1000 type of virtual nic, and use the latest related drivers from Intel site directly
b) try the latest stable drivers 0.1-49 recently made available here: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
Please report back

 

[tincboy]

Thanks for your tips,
Currently I've fixed the issue by simply changing the network card type to e1000

 

[tincboy]

My question now is why I didn't have this issue in older version of Proxmox with the same hardware?
Version with no issue:

pve-manager: 2.2-31 (pve-manager/2.2/e94e95e9)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-82
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-33
qemu-server: 2.0-69
pve-firmware: 1.0-21
libpve-common-perl: 1.0-39
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1

server with issue:

pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-40
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10

 

[tincboy]

I've this issue on all Windows Guests from pve 2.2-32 on another new server too
Anyone has the same experience?

 

[spirit]

I've this issue on all Windows Guests from pve 2.2-32 on another new server too
Anyone has the same experience?

Hi, what virtio driver version ? win2008 , 2008R2, 32/64 bit ?

If that happen, can you try in monitor: set_link net0 off|on.

 

[tincboy]

I'm not using virtio, simple configuration of a vm

bootdisk: ide0
cores: 1
ide0: local:7673/vm-7673-disk-1.raw,size=25G
memory: 256
name: stest
net1: rtl8139=F2:74:4A:37:8A:A4,bridge=vmbr1
onboot: 0
ostype: other

 

[tincboy]

Anyone else facing the same issue?

 

[mmenaz]

Why use a 100Mb/s nic type? I think that rtl8139 is there just as "kickstarter" for legacy os that don't support any newer hardware, and I think is not much tested either.
Try virtio with latest drivers or e1000.
Of course if previous Proxmox worked fine this could mean a bug in kvm 1.3, and you are right to ask, so this is not the right answer to your question, just a question/suggestion.

 

[webservio]

I have the same issue. Have not tried virtio driver. Before making an effort to do so any one got e1000 working? This happens to me when I try to copy a large directory.

 

[nz_monkey]

We too are experiencing this on Proxmox 2.2 with Windows guests running VirtIO 61.64.104.4900

 

[webservio]

This is getting very critical and we need to find a fix. A few mentioned here to update the driver for e1000 from Intel's site. Before trying to do so has it worked for any one?

 

[tincboy]

This is getting very critical and we need to find a fix. A few mentioned here to update the driver for e1000 from Intel's site. Before trying to do so has it worked for any one?

It worked for me, But it's necessary for Proxmox to fix such critical bug.

 

[webservio]

Thanks for your post tincboy. Where exactly did you download the e1000 driver for Windows 2008 R2? From Intel's site? Do you have the link?

 

[tincboy]

I've installed the e1000 driver on Windows 2003 VMs, the Windows 2008 has built in driver for e1000,
The link is:
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18719&lang=eng

 

[webservio]

Selecting e1000 as the bridge device is working without any drivers updates for now. I am copying a test 32GB directory through the network and see what happens. Just for the records I am posting my version for the Proxmox team info as well as people who have similar issues:

pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

 

[webservio]

Hi ticboy. Yes you are right and thanks so much for your reply. I posted my version to help Proxmox team to come up with fixes in the future.