Hi,
I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.
Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):
-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet
-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):
<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>
You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.
So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/
Furthermore, I noticed this in the Xen log:
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.
So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...
Does anybody have a clue why is this happening?
Thanks in advance ..
