|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Gentoo Xen Control Daemon not starting - problem & resol
>-----Original Message-----
>From: Stefan de Konink [mailto:skinkie@xxxxxxxxx]
>Sent: Thursday, 17 January 2008 17:05
>To: Joris Dobbelsteen
>Cc: xen-users@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-users] Gentoo Xen Control Daemon not
>starting - problem & resolution
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>Joris Dobbelsteen schreef:
>> Dear,
>>
>> Since power went down here a few hours ago (rare event in the
>> Netherlands), I noticed that the Xen Control Daemon (xend) did not
>> start using the init script provided with Gentoo 2007.0 and
>Xen 3.1.2
>> (from portage). The issue seems that xend is hanging on the
>network script.
>>
>> The network script was customed to make multiple calls to the
>> "network-bridge", but for different interfaces.
>> One of the calls was to create the bridge "xenbr2" for non-existing
>> interface "eth2". When doing this by hard it worked. However it did
>> cause xend to fail to start.
>>
>> My network script is:
>> ===
>> #!/bin/sh
>> dir=$(dirname "$0")
>> "$dir/network-bridge" "$@" vifnum=0
>> "$dir/network-bridge" "$@" vifnum=1
>> "$dir/network-bridge" "$@" vifnum=2
>> ===
>>
>> The interfaces eth0 and eth1 exist, while eth2 does not exist.
>
>
>Do you have IPv6 on the interface?
No, I don't use IPv6. But this doesn't matter at all.
The issue is that eth0 and eth1 exists, while eth2 does NOT exist. The
box only has two network cards.
Utilizing such configuration as I did causes xend to hang while
starting. It might be that developers are interested (since issues could
arise when changing network cards or simply moving to a new computer).
For me the problem is currently solved, but points out that you should
not modify the physical/dom0 config without testing carefully, including
a complete system reboot.
- Joris
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|