All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Sean Dague <sean@dague.net>
Cc: Dan Smith <danms@us.ibm.com>,
	xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>
Subject: Re: Re: massive failure on domain creation for	7353:29db5bded574
Date: Wed, 12 Oct 2005 20:55:08 -0500	[thread overview]
Message-ID: <434DBE7C.9070204@us.ibm.com> (raw)
In-Reply-To: <20051013012533.GC30182@underhill.no-ip.org>

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
>  
>

      reply	other threads:[~2005-10-13  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13  0:45 massive failure on domain creation for 7353:29db5bded574 Sean Dague
2005-10-13  1:25 ` Sean Dague
2005-10-13  1:55   ` Anthony Liguori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=434DBE7C.9070204@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=danms@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=sean@dague.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.