Hi,<br><br>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. <br><br>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):<br><br>-> eth3<br>DEVICE=eth3<br>BOOTPROTO=static<br>HWADDR=D4:85:64:4B:76:AB<br>ONBOOT=yes<br>#HOTPLUG=no<br>#DHCP_HOSTNAME=kdr-3k-4r-3o-07<br>BRIDGE=br0<br>
TYPE=Ethernet<br><br>-> br0<br>DEVICE=br0<br>TYPE=Bridge<br>BOOTPROTO=none<br>ONBOOT=yes<br><br>Then I configured new virt. ifaces on VM's (using virsh edit, config is listed below):<br><br> <interface type='bridge'><br>
<mac address='00:16:36:17:62:5d'/><br> <source bridge='xenbr0'/><br> <script path='vif-bridge'/><br> <target dev='vif5.0'/><br> </interface><br>
<interface type='bridge'><br> <mac address='00:16:3e:ca:63:39'/><br> <source bridge='br0'/><br> <script path='vif-bridge'/><br> <target dev='vif5.1'/><br>
</interface><br><br>You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0 connected to vif5.1.<br><br>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 :/<br><br><br>Furthermore, I noticed this in the Xen log:<br><br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices vif.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558) hotplugStatusCallback 1.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544) hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558) hotplugStatusCallback 1.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices usb.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices vbd.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.<br>[2011-11-18
09:27:16 xend 8213] DEBUG (DevController:544) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558) hotplugStatusCallback 1.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.<br>[2011-11-18
09:27:16 xend 8213] DEBUG (DevController:544) hotplugStatusCallback
/local/domain/0/backend/vbd/1/5632/hotplug-status.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558) hotplugStatusCallback 1.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices irq.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices vkbd.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices vfb.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices pci.<br>
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices ioports.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices tap.<br>[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for devices vtpm.<br>
<br>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) ...<br><br>Does anybody have a clue why is this happening?<br><br>Thanks in advance ..<br>