Hi all,
I installed 2009.06, xVM and happily installed a domU with no issues. I just
did this through the virt-manager GUI, and kept it as simple as possible.
Later I installed and booted a zone with very simple and standard configuration.
My existing xVM virtual machine did not immediately stop working, or have any
interruption at all. But, I can no longer create new virtual machines, or even
boot existing machines.
The virt-manager gui freezes at the connection dialogue, but command line tools
get me further, only giving up upon boot of the virtual machine.
The problem seems to be related to allocating a virtual network device to the
xvm domU. The eventual error in xend.log is:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in
perform
File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line
77, in op_start
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 1011, in
domain_start
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 595,
in waitForDevices
File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 152, in waitForDevices
File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 165, in waitForDevice
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.
The "vif" makes me think it's related to network devices, but I don't know how.
This all changes when I detach all my existing zones: everything in xVM goes
back to normal working condition.
I have repeated these symptoms on another server as well, however in this case
I set up the zones first and then installed xVM.
My zone configuration is pretty simple:
create -b
set zonepath=/zones/adriatic
set brand=ipkg
set autoboot=false
set ip-type=shared
add net
set address=192.168.31.29
set physical=bge0
end
Output of ifconfig shows the zone device alias, although it seems to have
multiple loopback devices. Is this normal?
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
zone adriatic
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.31.16 netmask ff000000 broadcast 192.255.255.255
bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
zone adriatic
inet 192.168.31.29 netmask ff000000 broadcast 192.255.255.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
lo0:1: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
zone adriatic
inet6 ::1/128
and output of "dladm show-link", showing a vnic created for xvm:
LINK CLASS MTU STATE OVER
nge0 phys 1500 unknown --
nge1 phys 1500 unknown --
bge0 phys 1500 up --
bge1 phys 1500 unknown --
xvm1_0 vnic 1500 up bge0
Thanks in advance,
L.
--
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
