From: Tej <bewith.tej@gmail.com>
To: xen-devel@lists.xensource.com, xen-users <xen-users@lists.xensource.com>
Subject: [Xen-devel] Startup Issues with Latest Xen Unstable
Date: Tue, 4 May 2010 16:31:33 +0530 [thread overview]
Message-ID: <z2gf1c9d251005040401o34c3ed46t7af13c0979b06dd3@mail.gmail.com> (raw)
All,
Recently starting Xen Unstable with linux-2.6-xen0 kernel. It got
stuck up at boot with following log.
...snip.....
libudev: udev_monitor_new_from_netlink Error invalid argument
Segmentation fault
Give up waiting for root device. Common problem:
- Boot args (cat /proc/cmdline)
- Check rootdelays
ALERT: /dev/sda7 does not exist
---snip------
System Details:
Distribution: Ubuntu 10.04
Udev Version: 151
Intel ICH6 SATA
Ok I know that it may work with Ubuntu 9.04 or with Udevd <= 132.
But does anyone has any idea how to make it work with my current system details.
Thanks for any help
-Tej
next reply other threads:[~2010-05-04 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 11:01 Tej [this message]
2010-05-04 14:18 ` Startup Issues with Latest Xen Unstable Konrad Rzeszutek Wilk
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=z2gf1c9d251005040401o34c3ed46t7af13c0979b06dd3@mail.gmail.com \
--to=bewith.tej@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).