|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Xen4.4 HVM domains and routed setups
Hi
I tried a lot of things, and I found something differences, that enabled me to
make the system WORK:
--- old system
--------------------------------------------------------------------------------
The old system creates 2 devices for each hvm domain:
vif32.0 and vm-test
The vm-test device is a tap device:
# ip tuntap show
vm-test: tap
# ip a
...
50: vif32.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
51: vm-test: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 500
link/ether 1e:1e:bf:79:39:0d brd ff:ff:ff:ff:ff:ff
inet 1.1.1.1/32 brd 1.255.255.255 scope global vm-test
# ifconfig vif32.0
vif32.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
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:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
# ifconfig vm-test
vm-test Link encap:Ethernet HWaddr 1e:1e:bf:79:39:0d
inet addr:1.1.1.1 Bcast:1.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:159023 errors:0 dropped:0 overruns:0 frame:0
TX packets:184838 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:28804291 (28.8 MB) TX bytes:70720586 (70.7 MB)
--- new system
--------------------------------------------------------------------------------
And the new system also creates 2 devices:
vm-test and vm-test-emu
Here vm-test-emu is the tap device:
# ip tuntap show
vm-test-emu: tap one_queue vnet_hdr
# ip a
...
31: vm-test-emu: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 500
link/ether 92:8f:40:6e:a1:10 brd ff:ff:ff:ff:ff:ff
32: vm-test: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet 1.1.1.1/32 brd 1.255.255.255 scope global vm-test
valid_lft forever preferred_lft forever
# ifconfig vm-test-emu
vm-test-emu Link encap:Ethernet HWaddr 92:8f:40:6e:a1:10
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:157 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:7090 (7.0 KB) TX bytes:0 (0.0 B)
# ifconfig vm-test
vm-test Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet addr: 1.1.1.1 Bcast:1.255.255.255 Mask:255.255.255.255
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:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
-----------------------------------------------------------------------------------
So, the devices seem to be somewhat swapped and on the new system both devices
seem to be down.
I can see arp requests from the VM if I manually bring the vm-test-emu device
online. But the host does not answer.
So I can run the following command to get it working:
echo 1 > /proc/sys/net/ipv4/conf/vm-test-emu/proxy_arp
ip llink set vm-test-emu up
ip route del 1.1.2.5 dev vm-test src 1.1.1.1
ip route add 1.1.2.5 dev vm-test-emu src 1.1.1.1
THEN IT WORKS.
However I would not like to run all these commands everytime I boot the system
but rather fix the vif-route scripts.
I would also want to contribute the results, as I am quite sure, the existing
scripts cannot work for anyone...
But I am not show how I would fix that....
Anyone any ideas?
Regards,
Steffen
Attachment:
smime.p7s _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |