[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt-users] F20 Virt-Manager with MacVTap not working

(Please put your responses inline rather than top-posting)

On 02/12/2014 10:07 AM, John Obaterspok wrote:
I've setup a VM with default networking (NAT) and this works fine but hosts on my LAN can't get to the VM since it uses NAT.

When I try to set network to use MacVTap with either default or bridged I get no networking for the VM. 
Any hints around this? I would like to have the VM's on the same LAN as my host and other machines. I don't care if the VM host can't reach the guests.

It did work find in F19 but there I believe I had more MacVtap devices to choose from.

2014-02-12 11:41 GMT+01:00 Laine Stump <laine laine org>:

I am using macvtap on F20 with no problems. Which device are you selecting to connect the macvtap device to? You should use the physical device that your host uses for network communication. Please send the <interface> section of the output of "virsh $guestname dumpxml" (where $guestname is, of course, the name of the guest with non-working networking).

On 02/12/2014 03:16 PM, John Obaterspok wrote:
The guest was setup through virt-manager. The machine is not configured much after a F20 install (I believe I didn't change any network things)

 Here is the network part:

   <interface type='direct'>
      <mac address='52:54:00:fe:b0:66'/>
      <source dev='em1' mode='bridge'/>
      <target dev='macvtap0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

It seems you are not alone. Here's a new BZ filed just last night:


It's unclear whether the reporter ran wireshark to turn on promiscuous mode on the host's macvtap interface, the host's physical device, or the guest's interface to make everything work, but you might try those (you could just run tcpdump instead of wireshark - same effect).

In the meantime, I notice that the reporter of that BZ is using qemu-1.6.1-3, while I'm running 1.7.0-4 (which is from the fedora-virt-preview repo). You might want to try enabling fedora-virt-preview in your yum setup, updating, then see if the problem is solved. Otherwise, I guess follow the BZ for progress reports.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]