From: David F Barrera <dfbp@us.ibm.com>
To: Robin van Leeuwen <rvl@ttg-edam.nl>
Cc: xen-devel@lists.xensource.com
Subject: Re: x86_64 - Unable to boot DomU
Date: Mon, 22 Aug 2005 16:22:49 -0500 [thread overview]
Message-ID: <430A4229.2010309@us.ibm.com> (raw)
In-Reply-To: <430A3C22.3040105@ttg-edam.nl>
So, I am not the only one, then. Thanks for your reply.
David
Robin van Leeuwen wrote:
> I have the same here after last pull
>
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
>
> only my hda1 maps to a ext3 on a lvm device...
>
> [Debian unstable/testing, last pull 22-08-05 18:00]
>
>
> David F Barrera wrote:
>
>> I've built Xen with the latest hg source pull, and I am not able to
>> boot domU on my x86_64 boxes using configurations and setups that
>> have previously worked. Has something changed since late last week
>> that would require a change in my domU configuration file?
>>
>> When creating DomU, I get the following error message:
>>
>> VFS: Cannot open root device "sdb2" or unknown-block(0,0)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>>
>> The file system for DomU is ext3, and I've made sure that it is built
>> in xenU kernel.
>>
>> This are the xm dmesg lines displayed when error occurs:
>>
>> (XEN) (file=grant_table.c, line=1071) Grant unref rd(5) ld(0)
>> frm(d485) flgs(0).
>> (XEN) (file=traps.c, line=878) Non-priv domain attempted
>> RDMSR(00000000c0000080,00020000,00020000).
>> (XEN) (file=traps.c, line=870) Non-priv domain attempted
>> WRMSR(00000000c0000100,00000000,00000000).
>> (XEN) (file=traps.c, line=870) Non-priv domain attempted
>> WRMSR(00000000c0000102,00000000,00000000).
>> (XEN) (file=traps.c, line=878) Non-priv domain attempted
>> RDMSR(00000000c0000080,00000000,00000000).
>> stop_this_cpu disable_local_apic
>>
>> This is the domU configuration file:
>>
>> # Kernel image file.
>> kernel = "/boot/vmlinuz-2.6-xenU"
>> # Optional ramdisk.
>> # ramdisk = "/boot/initrd-2.6.11.12-xenU"
>> # The domain build function. Default is 'linux'.
>> builder='linux'
>> # Initial memory allocation (in megabytes) for the new domain.
>> # memory = 256
>> memory = 512
>> # A name for your domain. All domains must have different names.
>> name = "vm1"
>> disk = [ 'phy:sdb1,0811,w','phy:sdb2,0812,w' ]
>> # Set if you want dhcp to allocate the IP address.
>> # vif = [ 'mac= AA:00:00:47:CB:34, bridge=xen-br0' ]
>> # Set if you want dhcp to allocate the IP address.
>> #dhcp="dhcp"
>> # Set netmask.
>> #netmask = '255.255.255.0'
>> # Set default gateway.
>> # gateway = '9.53.94.0'
>> # Set the hostname.
>> # hostname= "vm%d" % vmid
>>
>>
>> # Set root device.
>> root = "/dev/sdb2 ro"
>> # Sets runlevel 4.
>> # extra = "4"
>> #==============
>>
>> David F Barrera
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>
>
next prev parent reply other threads:[~2005-08-22 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 13:21 x86_64 - Unable to boot DomU David F Barrera
[not found] ` <430A3C22.3040105@ttg-edam.nl>
2005-08-22 21:22 ` David F Barrera [this message]
2005-08-22 22:17 ` Robin van Leeuwen
2005-08-23 13:40 ` David F Barrera
-- strict thread matches above, loose matches on Subject: below --
2005-08-22 21:23 Puthiyaparambil, Aravindh
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=430A4229.2010309@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=rvl@ttg-edam.nl \
--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.