ntial htop vim curl git vcsh
tig quilt tmux
and xen-hypervisor-4.4-amd64
How your /etc/network/interfaces looks like? Anything in it that would setup
network interface named vif*?
Thanks,
--
Anthony PERARD
___
Mailing list: http://lists.opens
# that interface (e.g. another running domU) because it's likely a
# configuration error
if ip link show "$vifname" >&/dev/null
then
fatal "Cannot rename interface $dev. An interface with name $vifname
already exists."
fi
ip link set &
ript to set down
the interface before trying to rename it:
In /etc/xen/scripts/vif-common.sh, search the function rename_vif() and add
in the begining this:
ip link set "$dev" down
And don't forget to remove the "exit 0" in /etc/xen/scripts/vif-bridge that
we've added
console of the VM
// to quit, ctr+]
> Do you have any other ideas? That is interesting that the master doesn't
> have the issue. Just to verify, are you running this all on one node?
Yes, all in one. I've enable those neutron services via devs
7;t know much of what Neutron is doing with the network interface but
we can maybe try to work arround this issue.
Could you add "exit 0" at the begin of the /etc/xen/scripts/vif-bridge
script? Then check if you've got network access to the guest.
Thanks,
--
Anthony PERARD
