Install virtio drivers in Windows Server 2008 R2 Core Install

[VegasMac]

I'm sorry if this is a repost for I have searched google and this forum for this topic and have not fond anything relating to Windows Server Core install.
I have Windows Server 2008 R2 Server Core installed and and Now I need to install the virtIO network drivers. Is there already a How-To written for this?
If not, I can stumble through it myself, I just need to know which exact INF file to use for the virtIO network driver for X64 Windows Server 2008 R2. I tried the Win7 and WHL drivers but it failed.
Also, along the same lines, I would like to take advantage of the Ballon memory driver and virtio disk driver if possible.

 

[macday]

virtIO network is not stable on Windows 2008 R2...don´t put too much sweat on it

 

[tom]

virtio works here without problems.

 

[adis]

We've also had problems with VirtIO drivers (downloaded from Fedora site), network stops responding at least once in 24h.
"Disable/Enble" cycle would fix problems temporarily.

The final solution was to disable "Offload Tx LSO" in Device manager for VirtIO NICs.

 

[macday]

We've also had problems with VirtIO drivers (downloaded from Fedora site), network stops responding at least once in 24h.
"Disable/Enble" cycle would fix problems temporarily.

The final solution was to disable "Offload Tx LSO" in Device manager for VirtIO NICs.

Thank you I´ll try that.

 

[macday]

Thank you I´ll try that.

Hello again,

I tried again my Windows 2003 Machines with virtio from the Fedora-page an also disabled "Offload Tx LSO" but I still lost connection last night. What can I do else?

I saw at dmesg screen this error: e1000e 0000:0a:00.0: eth0: Detected Hardware Unit Hang:
This NIC is an a bond with 2bnx and 2e1000 nics. Perhaps this helps.

Thank you

Update: I took the "defect" e1000e NIC´s out of the bond, now I have to wait until Monday (traffic). How can I fix this error? New Kernel perhaps?

Is my NIC defect ?

 

[macday]

Hello again,

I tried again my Windows 2003 Machines with virtio from the Fedora-page an also disabled "Offload Tx LSO" but I still lost connection last night. What can I do else?

I saw at dmesg screen this error: e1000e 0000:0a:00.0: eth0: Detected Hardware Unit Hang:
This NIC is an a bond with 2bnx and 2e1000 nics. Perhaps this helps.

Thank you

Update: I took the "defect" e1000e NIC´s out of the bond, now I have to wait until Monday (traffic). How can I fix this error? New Kernel perhaps?

Is my NIC defect ?

Please help...I still have disconnections on our virtual Exchange-Web-Access Server nearly every night...Do I have to go back to e1000?

 

[linum]

Do I have to go back to e1000?

I think virtio support is somewhat broken. I also had to go back to e1000 driver to get a stable system. Just search for virtio and windows. Or look here:

http://forum.proxmox.com/threads/7318-WinXP-virtio-proxmox-1-9-gt-crash


http://forum.proxmox.com/threads/61...virtio-drivers-for-Windows-and-latest-PVE-1-8

 

[macday]

Would this help? http://forum.proxmox.com/threads/8102-Kernel-panic-with-e1000-under-high-network-load

 

[linum]

To use KSM and since I didn't use openvz is run kernel 2.6.35.