On Wed, 2 Nov 2011, Gaurav Gupta wrote: > On Tue, Nov 1, 2011 at 3:51 PM, Scott Moser <smo...@ubuntu.com> wrote: > > > On Tue, 1 Nov 2011, Vishvananda Ishaya wrote: > > > > > Sounds like we can work around this pretty easily by sorting the disks > > before we pass them into the xml template. > > > > The long term solution here is not to load the kernel and the ramdisk > > outside the image, but rather let grub load it with root=LABEL=xxxx > > or root=UUID=xxxx . > > > > If you boot one of the full disk Ubuntu image (-disk1.img) files at > > https://cloud-images.ubuntu.com/releases/oneiric/release/ or > > https://cloud-images.ubuntu.com/server/natty/current/ , then you wont have > > the problem. You'll also be able to 'apt-get update && apt-get > > dist-upgrade && reboot' and get a new kernel. That is not possible with > > the hypervisor doing the kernel and ramdisk loading. > > > > Actually you can create a bootable image where the kernel and ramdisk are > picked from the root file system. AFAIU you can't do this with volumes > thought, you have to create an image and boot from it.
I'll try to take a look at this next week, and if it isn't functioning correctly try to get it addressed in essex. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp