Re: [Xen-users] Domain-U failed to start when Domain-0 reboot

["Grant McWilliams" <grantmasterflash@xxxxxxxxx>]

On Wed, Dec 17, 2008 at 11:19 AM, Muzammel Asghar <muzammel.asghar@xxxxxxxxxxxxxx> wrote:

Hi guys i am facing some strange problem in xen. I used xen version 3
in fedora core 8 in routed mode. I create 5 vm's, the problem is when i
reboot mother
domain-0 first two vms boot and shutdown and rest other 3 vm's
are boot properly. But after that i manually start 1st and 2nd vm they
start fine, i don't understand why they not start automatically when
domain-0 boot but manuall start of these vm's are fine

here below the logs of /var/log/messages

Dec 13 10:28:27 khunj logger: /etc/xen/scripts/vif-route:
Dec 13 10:28:27 khunj logger: /etc/xen/scripts/vif-route:
/etc/xen/scripts/vif-route failed; error detected.
Dec 13 10:28:27 khunj logger: /etc/xen/scripts/vif-route:
Dec 13 10:28:27 khunj logger: /etc/xen/scripts/vif-route:
/etc/xen/scripts/vif-route failed; error detected.
Dec 13 10:28:28 khunj logger: /etc/xen/scripts/vif-route:
Dec 13 10:28:28 khunj logger: /etc/xen/scripts/vif-route:
/etc/xen/scripts/vif-route failed; error detected.

and in xend.log it shows this

[2008-12-13 10:28:27 2136] DEBUG (XendDomainInfo:1040)
XendDomainInfo.handleShutdownWatch
[2008-12-13 10:28:27 2136] DEBUG (DevController:150) Waiting for devices
vif.
[2008-12-13 10:28:27 2136] DEBUG (DevController:155) Waiting for 0.
[2008-12-13 10:28:27 2136] DEBUG (DevController:594)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2008-12-13 10:28:27 2136] DEBUG (DevController:594)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2008-12-13 10:28:27 2136] DEBUG (DevController:608)
hotplugStatusCallback 2.
[2008-12-13 10:28:27 2136] DEBUG (XendDomainInfo:1802)
XendDomainInfo.destroy: domid=1
[2008-12-13 10:28:27 2136] DEBUG (XendDomainInfo:1821)
XendDomainInfo.destroyDomain(1)

kindly help me regarding this matter.

--
Regards,
Muzammel Asghar

There are people who believe the most reliable way of ensuring your DomUs start is to create your own init script and not leave it to the xend service to do it. I'm not quite there but after seeing this happen multiple times I'm considering it. There doesn't seem to be any reason why a DomU doesn't start because they start just fine manually. I have noticed that for whatever reason having having a link to the domU config file in auto worked better than having the domU config file itself in auto. Maybe it was just a coincidence, I didn't follow up. Just my 2 cents.


Grant McWilliams

Some people, when confronted with a problem, think "I know, I'll use Windows."
Now they have two problems.
 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users