On Mon, May 17, 2010 at 7:01 PM, Miles Fidelman
<mfidelman@xxxxxxxxxxxxxxxx> wrote:
> Fajar A. Nugraha wrote:
>>
>> On Sat, May 15, 2010 at 7:51 AM, Miles Fidelman
>> <mfidelman@xxxxxxxxxxxxxxxx> wrote:
>>
>>>
>>> Configuration this applies to:
>>> Debian Lenny
>>> xendomains was trying to bring up VMs, before drbd devices were
>>> initialized
>>> - leading to all kinds of weirdness. The domains would try to come up,
>>> get
>>> through the boot stages, and then hang as soon as they tried to mount
>>> root
>>> and swap.
>>>
>>
>> That, by itself, is strange. Whether you use phy:/dev/drbd*, or
>> block-drbd scripts, the drbd resource should not be accessible if drbd
>> has not been started yet. Not accessible means the domU should not be
>> able to start at all.
>>
>
> That's exactly the point - xen tries to access a non-existent boot device,
> and hangs in the middle of the boot process.
... and that's why I said it's strange. It should've refused to start.
Not loading kernel and hang in the middle.
>>
>> Since you use debian packages, your best bet is to contact their
>> package maintainer, or use their bug report mechanism.
>> http://packages.debian.org/lenny/xen-linux-system-2.6.26-2-xen-686
>>
>
> Good point. Thanks.
Good luck. If you have some time it might be better to test squid/sid
first. Just in case they've fixed it there.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home