massive failure on domain creation for 7353:29db5bded574

massive failure on domain creation for 7353:29db5bded574

[Sean Dague]

[-- Attachment #1.1: Type: text/plain, Size: 1419 bytes --]

I have a 5 DomU raw disk partition environment (5 different distros).  When
using changeset 7353:29db5bded574 I get massive failures when starting with
/etc/init.d/xendomains.

After about 60 seconds, I get an error from the script, then xend appears
dead.  A restart of xend provides me with the following from xm list:

Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       123    0      1  r-----    191.8
Mandrake2006      12       128    0      1  --p---      0.0
Suse9.2           27       100    0      1  --p---      0.0

So in that 60 seconds, there were 25 domain deaths from attempted starts. 
I've got about 1 MB of xend logs generated from this as well (which contain
vast numbers of "DEBUG (XendDomainInfo:805) XendDomainInfo.update").

Are we still in fallout from weekend changes, or are these new issues I
should be digging into and getting into bugzilla?

	-Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: massive failure on domain creation for 7353:29db5bded574

[Sean Dague]

[-- Attachment #1.1: Type: text/plain, Size: 1996 bytes --]

On Wed, Oct 12, 2005 at 08:45:41PM -0400, Sean Dague wrote:
> I have a 5 DomU raw disk partition environment (5 different distros).  When
> using changeset 7353:29db5bded574 I get massive failures when starting with
> /etc/init.d/xendomains.
> 
> After about 60 seconds, I get an error from the script, then xend appears
> dead.  A restart of xend provides me with the following from xm list:
> 
> Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> Domain-0           0       123    0      1  r-----    191.8
> Mandrake2006      12       128    0      1  --p---      0.0
> Suse9.2           27       100    0      1  --p---      0.0
> 
> So in that 60 seconds, there were 25 domain deaths from attempted starts. 
> I've got about 1 MB of xend logs generated from this as well (which contain
> vast numbers of "DEBUG (XendDomainInfo:805) XendDomainInfo.update").
> 
> Are we still in fallout from weekend changes, or are these new issues I
> should be digging into and getting into bugzilla?

Further update, when I try to create Suse9.2 domain by hand, about 1/3 of
the time it succeeds, the other 2/3 I get the following error on the
console:

VFS: Cannot open root device "hda1" or unknown-block(2,0)
Please append a correct "root=" boot option              
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)

All the configuration is the same, I'm just running xm create -c
/etc/xen/auto/Suse9.2 over again each time it fails.

	-Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Re: massive failure on domain creation for 7353:29db5bded574

[Anthony Liguori]

Hi Sean,

Can you post your configs?

Have you updated for the new event parameters?

Ewan/Dan: what do you guys think about checking the global parameters 
after reading the configuration file in xm and issuing warnings for 
unknown globals?  This might help avoid people using invalid parameters 
(I know I've been burned in the past from using disks instead of disk).

Regards,

Anthony Liguori

Sean Dague wrote:

>On Wed, Oct 12, 2005 at 08:45:41PM -0400, Sean Dague wrote:
>  
>
>>I have a 5 DomU raw disk partition environment (5 different distros).  When
>>using changeset 7353:29db5bded574 I get massive failures when starting with
>>/etc/init.d/xendomains.
>>
>>After about 60 seconds, I get an error from the script, then xend appears
>>dead.  A restart of xend provides me with the following from xm list:
>>
>>Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
>>Domain-0           0       123    0      1  r-----    191.8
>>Mandrake2006      12       128    0      1  --p---      0.0
>>Suse9.2           27       100    0      1  --p---      0.0
>>
>>So in that 60 seconds, there were 25 domain deaths from attempted starts. 
>>I've got about 1 MB of xend logs generated from this as well (which contain
>>vast numbers of "DEBUG (XendDomainInfo:805) XendDomainInfo.update").
>>
>>Are we still in fallout from weekend changes, or are these new issues I
>>should be digging into and getting into bugzilla?
>>    
>>
>
>Further update, when I try to create Suse9.2 domain by hand, about 1/3 of
>the time it succeeds, the other 2/3 I get the following error on the
>console:
>
>VFS: Cannot open root device "hda1" or unknown-block(2,0)
>Please append a correct "root=" boot option              
>Kernel panic - not syncing: VFS: Unable to mount root fs on
>unknown-block(2,0)
>
>All the configuration is the same, I'm just running xm create -c
>/etc/xen/auto/Suse9.2 over again each time it fails.
>
>	-Sean
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>  
>