|
|
|
|
|
|
|
|
|
|
xen-community
[Xen-community] XEN Debian 3.0 HVM routed networking no-carrier
Running:
linux-image-2.6-xen-amd64 2.6.18+6etch3
linux-image-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch6
linux-modules-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch6
xen-docs-3.0 3.0.3-0-4
xen-hypervisor-3.0.3-1-amd64 3.0.3-0-4
xen-ioemu-3.0.3-1 3.0.3-0-4
xen-tools 2.8-2
xen-utils-3.0.3-1 3.0.3-0-4
xen-utils-common 3.0.3-0-2
Because of provider I had to change XEN setup from bridged to routing:
#(network-script network-bridge)
#(vif-script vif-bridge)
(network-script network-route)
(vif-script vif-route)
Now all domains work except HVMs. For first they refused to start.
Commenting out line with brctl in /etc/xen/scripts/qemu-ifup helped to
resolve this:
#brctl addif $2 $1
Now the problem is that HVM domUs has no connectivity. I've found this
problem:
9: vif7.0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet xx.xx.xx.xx/32 brd xx.255.255.255 scope global vif7.0
The vif for HVM domain has NO-CARRIER but all other non-HVM domains are OK.
Any ideas?
Thanks in advance.
_______________________________________________
Xen-community mailing list
Xen-community@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-community
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-community] XEN Debian 3.0 HVM routed networking no-carrier,
Bc. Slavomir Danas <=
|
|
|
|
|