Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've created a VM image via vmbuilder. I've been trying to configure the VM to be able to network with the host machine as well as the outside router. I've been following the directions here and here since bridging to a wireless card is not supported by KVM/QEMU out of the box.

When doing virsh start mystique.ootbdev I get:

error: Failed to start domain mystique.ootbdev
error: Unable to add bridge tap0 port vnet0: Operation not supported

Trying to start with kvm leads to better results:

kvm -hda mystique.qcow2 -net nic -net tap,ifname=tap0,script=no -usb -display curses

The VM boots but there isn't any networking. How can I get these guys to talk to one another? I've been trying to read up to better understand how TAP 'should' work, but it's not clear to me what I should be trouble shooting next.

How do I configure my host/guest networking so that they can talk to one another and that external clients can access the VM?

Config data below


On the host, ifconfig looks like this:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2518 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2518 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:416757 (416.7 KB)  TX bytes:416757 (416.7 KB)

tap0      Link encap:Ethernet  HWaddr 46:1e:a0:a3:cf:3a  
          inet addr:192.168.100.200  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

virbr0    Link encap:Ethernet  HWaddr 96:df:02:00:43:dd  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 8c:21:0a:e1:0c:f9  
          inet addr:192.168.100.150  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::8e21:aff:fee1:cf9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:359338 errors:0 dropped:0 overruns:0 frame:0
          TX packets:176516 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:389033762 (389.0 MB)  TX bytes:19063805 (19.0 MB)

On the guest it looks like this:

eth0      Link encap:Ethernet  HWaddr 52:54:00:12:34:56                         
          inet addr:192.168.100.201  Bcast:0.0.0.0  Mask:255.255.255.255        
          inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link                     
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                    
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0                 
          collisions:0 txqueuelen:1000                                          
          RX bytes:0 (0.0 B)  TX bytes:2616 (2.6 KB)                            
          Interrupt:10 Base address:0x4000                                      

lo        Link encap:Local Loopback                                             
          inet addr:127.0.0.1  Mask:255.0.0.0                                   
          inet6 addr: ::1/128 Scope:Host                                        
          UP LOOPBACK RUNNING  MTU:16436  Metric:1                              
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0                   
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0                 
          collisions:0 txqueuelen:0                                             
          RX bytes:2432 (2.4 KB)  TX bytes:2432 (2.4 KB)     

Here is the interfaces file for the host and for the guest.

Thanks!

share|improve this question
    
Are you running virsh start as root or with sudo? –  mgorven Jun 28 '12 at 5:46
    
I do a 'sudo -s' to get root access. –  Avery Chan Jun 28 '12 at 8:04
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.