openstack team mailing list archive

[Rogério Vinhal Nunes <rogervn@xxxxxxxxxxx>]

Yes, I've tried the ttylinux right now, it starts the instance, but it
booted up a busybox, probably a recover from initrd (see output in the end
of this e-maill). I can access the instance by doing a xl console in the
host, describe-instances shows the status "running test".

I've successfully booted a separated vm with an old image I used with Xen
with Xen + libvirt just changing the openstack's libvirt.xml. It just works
fine.

The instance dir in /var/lib/nova/instances files look like this:

   0 -rw-r----- 1 nova nogroup    0 2011-09-28 15:43 console.log
 15M -rw-r--r-- 1 nova nogroup  18M 2011-09-28 15:43 disk
4,3M -rw-r--r-- 1 nova nogroup 4,3M 2011-09-28 15:43 kernel
4,0K -rw-r--r-- 1 nova nogroup 1,3K 2011-09-28 15:43 libvirt.xml
5,7M -rw-r--r-- 1 nova nogroup 5,7M 2011-09-28 15:43 ramdisk

this is the last output I get when I get into the instance console:

[    0.078066] blkfront: sda: barriers enabled
[    0.078394]  sda: unknown partition table
[    0.170040] XENBUS: Device with no driver: device/vkbd/0
[    0.170051] XENBUS: Device with no driver: device/vfb/0
[    0.170056] XENBUS: Device with no driver: device/console/0
[    0.170074]   Magic number: 1:252:3141
[    0.170114] /build/buildd/linux-2.6.35/drivers/rtc/hctosys.c: unable to
open rtc device (rtc0)
[    0.170122] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.170127] EDD information not available.
[    0.170259] Freeing unused kernel memory: 828k freed
[    0.170460] Write protecting the kernel read-only data: 10240k
[    0.173975] Freeing unused kernel memory: 308k freed
[    0.174481] Freeing unused kernel memory: 1620k freed
badness occurred in ramdisk


BusyBox v1.15.3 (Ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
/ #
/ #


Em 28 de setembro de 2011 14:06, Joshua Harlow <harlowja@xxxxxxxxxxxxx>escreveu:

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