openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04409
Re: Xen image starts Kernel Panic in Diablo
-
To:
Todd Deshane <todd.deshane@xxxxxxx>, Rogério Vinhal Nunes <rogervn@xxxxxxxxxxx>
-
From:
Joshua Harlow <harlowja@xxxxxxxxxxxxx>
-
Date:
Wed, 28 Sep 2011 10:06:55 -0700
-
Accept-language:
en-US
-
Acceptlanguage:
en-US
-
Cc:
openstack <openstack@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAMrPLWJg-GomsEUko4mVHWgmupKo4og6N0HcYd2Tb88=WsDKeg@mail.gmail.com>
-
Thread-index:
Acx9h97fqTFRiOp8QIWGstfd7c1ujwAeSdGm
-
Thread-topic:
[Openstack] Xen image starts Kernel Panic in Diablo
Can u try with the ttylinux images and see if those work for you?
I know when I tried it I had to adjust the libvirt xml was creating (which may have not been the right solution) to get those to work.
I think the ttylinux ones might work better (from the last time I tried).
On 9/27/11 7:11 PM, "Todd Deshane" <todd.deshane@xxxxxxx> wrote:
2011/9/27 Rogério Vinhal Nunes <rogervn@xxxxxxxxxxx>:
> Hello, I've upgraded to Diablo to see if this issue was resolved, but
> apparently it isn't.
>
> There is already a thread talking about it, but it didn't come to a solution
> that I could use. After having Openstack configured with Xen and libvirt in
> Ubuntu 10.04 whenever I run an instance it is started, but it stops with a
> kernel panic trying to mount root by using xvda, but sda is the only
> available.
>
> I'm using Diablo's nova + glance and the
> ubuntu1010-UEC-localuser-image.tar.gz from the manual.
>
> The kernel panic is like this:
>
> [ 0.170563] VFS: Cannot open root device "xvda" or unknown-block(0,0)
> [ 0.170572] Please append a correct "root=" boot option; here are the
> available partitions:
> [ 0.170585] ca00 32768 sda driver: vbd
> [ 0.170594] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> [ 0.170604] Pid: 1, comm: swapper Not tainted 2.6.35-24-virtual
> #42-Ubuntu
>
> I've played with libvirt.xml.template, it changed a lot since Cactus, so I
> tried to replace xvda with sda, and the kernel panic didn't go away, just
> changed a little:
>
> [ 0.161237] List of all partitions:
> [ 0.161248] ca00 32768 sda driver: vbd
> [ 0.161257] No filesystem could mount root, tried: ext3 ext2 ext4
> fuseblk
> [ 0.161275] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(202,0)
> [ 0.161286] Pid: 1, comm: swapper Not tainted 2.6.35-24-virtual
> #42-Ubuntu
>
Are you able to start a guest manually with Xen + libvirt (without OpenStack)?
That's the first step to debugging this issue.
> I've tried using --xenapi_remap_vbd_dev=true, but it didn't work (it
> wouldn't also because I'm using libvirt, not xenapi).
>
Would XCP or XenServer work for you in general? (The XenAPI-based
hypervisors are more tested and even have more features compared with
libvirt - http://wiki.openstack.org/XenAPI)
Or even Project Kronos (also uses XCP/XenServer toolstack)
http://blog.xen.org/index.php/2011/07/22/project-kronos/
Thanks,
Todd
--
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Follow ups
References