4:07 p.m.
Hello,
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.
-- john
6:41 p.m.
On 02/12/2014 10:07 AM, John Obaterspok wrote:
Hello,
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.
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).
9:16 p.m.
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'/>
</interface>
and the complete dump:
<domain type='kvm' id='3'>
<name>winpc</name>
<uuid>3d333333-3333-3333-3333-333333333333</uuid>
<memory unit='KiB'>2097152</memory>
<currentMemory unit='KiB'>2097152</currentMemory>
<vcpu placement='static'>1</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-1.6'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='vmdk'/>
<source file='/vm/storage/win8pc.img'/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x07'
function='0x0'/>
</disk>
<controller type='usb' index='0' model='ich9-ehci1'>
<alias name='usb0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<alias name='usb0'/>
<master startport='0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x0' multifunction='on'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci2'>
<alias name='usb0'/>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<alias name='usb0'/>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x06'
function='0x0'/>
</controller>
<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'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/2'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/2'>
<source path='/dev/pts/2'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0'
port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
</input>
<input type='mouse' bus='ps2'/>
<graphics type='spice' port='5900' autoport='yes'
listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<sound model='ich6'>
<alias name='sound0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x0'/>
</sound>
<video>
<model type='qxl' ram='65536' vram='65536'
heads='1'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x08'
function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c296,c829</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c296,c829</imagelabel>
</seclabel>
</domain>
2014-02-12 11:41 GMT+01:00 Laine Stump <laine(a)laine.org>:
On 02/12/2014 10:07 AM, John Obaterspok wrote:
Hello,
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.
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).
5:16 p.m.
(Please put your responses inline rather than top-posting)
On 02/12/2014 10:07 AM, John Obaterspok wrote:
Hello,
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(a)laine.org
<mailto: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'/>
</interface>
It seems you are not alone. Here's a new BZ filed just last night:
https://bugzilla.redhat.com/show_bug.cgi?id=1064516
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.
http://fedorapeople.org/groups/virt/virt-preview/fedora-virt-preview.repo
7:37 p.m.
2014-02-13 10:16 GMT+01:00 Laine Stump <laine(a)laine.org>:
It seems you are not alone. Here's a new BZ filed just last night:
https://bugzilla.redhat.com/show_bug.cgi?id=1064516
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.
http://fedorapeople.org/groups/virt/virt-preview/fedora-virt-preview.repo
Thanks a lot. I'm away right now but I'm pretty sure I'm using e1000e
(Intel® 82579V Gigabit Ethernet Controller).
I'll keep an eye on the BZ.
-- john
3859
days inactive
3860
days old
4 comments
2 participants
participants (2)
-
John Obaterspok -
Laine Stump