KVM - Bridged networking in Windows guest

G

gezley

New Member
Jan 23, 2009
3
0
1
Hi
I have just started using Proxmox, which seems to be a really excellent product.
I have set up Windows 2003 Server in KVM, but I can't get bridging to work, perhaps because I have come from VirtualBox where it is done differently.

On the host vmbr0 is active, and address is 192.168.0.40. It is attached to eth1. I can't ping an address on the internet from the host. Is there a firewall active on Proxmox?

In the Windows guest I have set a static address on the network adapter (e1000) - 192.168.0.41. How do I join this to the bridge vmbr0? I thought I had done this when I created the Virtual Machine and indeed e1000 is joined to vmbr0 when I look in the web interface but I can't ping another address on the LAN from the VM and I can't even ping the host.
 
gezley said:
Hi
I have just started using Proxmox, which seems to be a really excellent product.
I have set up Windows 2003 Server in KVM, but I can't get bridging to work, perhaps because I have come from VirtualBox where it is done differently.

On the host vmbr0 is active, and address is 192.168.0.40. It is attached to eth1. I can't ping an address on the internet from the host. Is there a firewall active on Proxmox?
Click to expand...

no. (I mean yes, Proxmox VE is really excellent, and no, there is no firewall on a standard Proxmox VE installation).

gezley said:
In the Windows guest I have set a static address on the network adapter (e1000) - 192.168.0.41. How do I join this to the bridge vmbr0? I thought I had done this when I created the Virtual Machine and indeed e1000 is joined to vmbr0 when I look in the web interface but I can't ping another address on the LAN from the VM and I can't even ping the host.
Click to expand...

you need to setup the windows in the same way you setup a physical host. so it looks like you did it the right way - pls review the IP settings in your guest. If you have a DHCP server in your network, the windows guest would get everything automatically, can you test this?

do you use the latest version of Proxmox VE? run apt-get update/upgrade.
and post the output of

Code: 
pveversion -v
or do you have a custom Proxmox VE installation (e.g. from OVH)?
 
tom said:
you need to setup the windows in the same way you setup a physical host. so it looks like you did it the right way - pls review the IP settings in your guest. If you have a DHCP server in your network, the windows guest would get everything automatically, can you test this?
Click to expand...

Thanks for your help Tom; I really did think I had set it up correctly. I won't be back at that machine till later this evening. I downloaded the Proxmox VE from the website only yesterday, so it should be the latest, no? I have made no changes whatsoever to the default install.
While I was here at home it occurred to me Proxmox might have configured the two physical network adapters in reverse! Usually if I install Linux on that computer the Marvell adapter becomes eth0 and the D-Link becomes eth1, but I completely overlooked the possibility it is the other way around under Proxmox! But of course if that was the case I wouldn't be able to access the web interface. hmmmm ... very confusing.
 
gezley said:
Thanks for your help Tom; I really did think I had set it up correctly. I won't be back at that machine till later this evening. I downloaded the Proxmox VE from the website only yesterday, so it should be the latest, no? I have made no changes whatsoever to the default install.
Click to expand...

Update:
Well it turned out your advice was spot on Tom. Once I did apt-get update and then apt-get upgrade everything went fine. I just assumed I had the latest version when I downloaded Proxmox VE yesterday. Live and learn!
The network performance isn't great, although I suspect a cheap 8-port Netgear 1 GB switch might be the problem. I bought a 24-port 1 GB D-Link for the network myself; this one cost 380 euro so I don't think this one is the problem.
I'm going to give the virtio drivers a go next instead of the e1000, just to see if it improves things, but it's still pretty good. I need to load Service Pack 2 for the Windows 2003 Server guest as well.
Thanks for your help; I think this Proxmox has the makings of a killer virtualization package.
:)
 
Fix for the Intel e1000

The built in driver for the Intel 1000 in Windows is the problem. Switch to the rtl NIC to get online, then download the latest driver from Intel. Your looking for the 1000/PRO MT Server driver for Windows. The latest version is currently 13.5. After you download it to your guest, switch back to the e1000 and install the driver. It should work great.
 
This post might be 18 months old but the info is still pertinent.

I have a few VMs working away well together Windows KVM and OpenVZ. A W2008R2 happily serving physical workstations, but when I tried to join another Virtual Windows server to the domain from the same host, I found that the Windows VMs IPs could not be accesssed by any of the other VMs.

Searching for "1000/PRO MT Server driver for Windows" brought me straight to the Intel download page. (Up to about v15.x now)

Fixed my problem. Thanks bitbud.
 
Last edited:
You must log in or register to reply here.
Top Bottom