Networking with Virtual Machines

[mpolo]

I have successfully used Virtual Machine Manager to create a KVM/QEMU virutal machine running Windows XP.

This has created a virtual bridge (virbr0) with the IPv4 configuration:

Network: 192.168.122.0/24
DHCP start: 192.168.122.2
DHCP end: 192.168.122.254
Forwarding: NAT

In Windows ipconfig gives me

IP-Adress: 192.168.122.115
Subnet mask: 255.255.255.0
Standard gateway: 192.168.122.1

So far, so good, but the bridge does not seem to be forwarding properly. If I ping the server in the physical network, I get nothing. I can't find the Internet, I can't find the local network.

What do I need to do to get this to work?

[scott32746]

Hello,
I am using VirtualBox I had to change NAT to BRIDGE to make my network to work

[smr54]

Did you set up the bridge using virt-manager or manually?

If I remember correctly (haven't used it in awhile), one first has to set up the bridged interface, probably manually. Then, virt-manager will enable you to use it..

I have a very dated page dealing with CentOS' older version of KVM--that is, older than the current version of CentOS' KVM, where it explains setting up a bridge manually. You might scan through the section on bridging and see if there's anything obvious you left out, such as an iptables entry.

DISCLAIMER--haven't done bridged networking in Fedora, and the older article may be completely irrelevant--Fedora might do all the firewall adjustments, etc., for you.

I remember stevea mentioning that the latest virt-manager does most of it--the one time I tried it (probably in F13), however it wouldn't automagically set up a bridge---the bridged option was greyed out, probably because I hadn't set one up in advance.

http://home.roadrunner.com/~computer...centoskvm.html

[mpolo]

As it stands, it creates a bridge device: virbr0. The Forwarding options are NAT and Routed. Each of these can be to all devices or to a specific device (in my case, eth0).

None of those options work. I guess I have a couple more experiments to try…