openstack team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Here is also the libvirt.xml section that might be useful:

$ more instance-00000033/libvirt.xml
<domain type='xen'>
    <name>instance-00000033</name>
    <memory>524288</memory>
    <os>
            <type>linux</type>
            <root>/dev/xvda</root>
            <kernel>/home/ctoteam/nova/nova/..//instances/instance-00000033/kernel</kernel>
                <cmdline>ro</cmdline>
    </os>
    <features>
        <acpi/>
    </features>
    <vcpu>1</vcpu>
    <devices>
        <disk type='file'>
            <driver type='raw'/>
            <source file='/home/ctoteam/nova/nova/..//instances/instance-00000033/disk'/>
            <target dev='sda' bus='scsi'/>
        </disk>



On 8/22/11 11:28 AM, "Joshua Harlow" <harlowja@xxxxxxxxxxxxx> wrote:

Attempting to follow your notes.

I have the following ubuntu kernel.

Linux version 2.6.35-24-virtual

This is just a standard ubuntu UEC image.

With command line options.

Command line: root=/dev/xvda ro

I've got a dom0 running with the following.

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {

Which seems to be right.

The following error still occurs.

[    0.190303] md: Waiting for all devices to be available before autodetect
[    0.190315] md: If you don't use raid, use raid=noautodetect
[    0.190508] md: Autodetecting RAID arrays.
[    0.190520] md: Scanned 0 and added 0 devices.
[    0.190528] md: autorun ...
[    0.190534] md: ... autorun DONE.
[    0.190629] VFS: Cannot open root device "xvda" or unknown-block(0,0)
[    0.190641] Please append a correct "root=" boot option; here are the available partitions:
[    0.190658] ca00         1441792 sda driver: vbd
[    0.190671] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.190683] Pid: 1, comm: swapper Not tainted 2.6.35-24-virtual #42-Ubuntu
[    0.190693] Call Trace:

When switching it to sda it works though. Following your notes it seems like the dom0 kernel version shouldn't be having this issue?

http://lists.debian.org/debian-l10n-english/2010/12/msg00059.html

On 8/20/11 6:53 AM, "Thomas Goirand" <thomas@xxxxxxxxxx> wrote:

On 08/20/2011 05:40 AM, Joshua Harlow wrote:
> So what I've figured out is the following seems to work with xen4.

The naming of sda vs xvda has nothing to do with the hypervisor, and a
lot to do with your kernel.

Thomas