xen-users
Re: [Xen-users] pygrub error booting iso
Just in case :- http://lists.xensource.com/archives/html/xen-users/2010-05/msg00303.html I can't remind version Ubuntu Server 8.04 and higher installable via ISO image.
Boris
--- On Mon, 6/14/10, Gerry Reno <greno@xxxxxxxxxxx> wrote:
From: Gerry Reno <greno@xxxxxxxxxxx> Subject: Re: [Xen-users] pygrub error booting iso To: greno@xxxxxxxxxxx Cc: xen-users@xxxxxxxxxxxxxxxxxxx Date: Monday, June 14, 2010, 1:33 AM
Ok, a little progress. I copied the kernel and ramdisk from the lucid iso to /boot and then used these when creating. That gave me an installer screen. But I got no disk devices of any kind. No hdX, no xvdX, no cdrom, nothing. -Gerry Jun 13, 2010 10:17:12 PM, greno@xxxxxxxxxxx wrote:
Here is the pertinent part of the boot: [ 0.466857] blkfront: xvde: barriers enabled [ 0.470319] xvde: unknown partition table [ 0.473183] Setting capacity to 6909376 [ 0.473197] xvde: detected capacity change from 0 to 3537600512 [ 0.473521] blkfront: xvda: barriers enabled [ 0.474962] xvda: xvda1 xvda2 < xvda5 > [ 0.476335] Setting capacity to 251658240 [ 0.476344] xvda: detected capacity change from 0 to 128849018880
Jun 13, 2010 09:46:15 PM, greno@xxxxxxxxxxx wrote:
The furtherest I have gotten with this is to get an initramfs prompt using this config:
name = "RESCUE" memory = 1024 vcpus = 4 kernel = "/boot/vmlinuz-2.6.32.13" ramdisk = "/boot/initrd.img-2.6.32.13" disk = [ 'file:/tmp/iso/ubuntu/10.04/ubuntu-10.04-server-amd64.iso,hdd:cdrom,r',
"tap:aio:/var/lib/xen/images/CLOUD-CC-1.img,xvda,w" ]
vfb = [ 'type=vnc,vncunused=1' ]
In initramfs I can see the devices: xvda1,xvda2,xvda5, xvde
And if I mount xvde as iso9660 then I can see the files in the iso.
I don't understand why it cannot perform the boot. It seems like everythng is there. This is using pv_ops kernel 2.6.32.13 and Xen 4.0.0-rc8
-Gerry
Jun 13, 2010 07:34:45 PM, greno@xxxxxxxxxxx wrote:
ok, some other things that are weird: hdc ends up on xvda hdd ends up on xvde Huh?
I don't know whether this is pygrub or Xen that's causing the problems.
-Gerry
Jun 13, 2010 06:54:02 PM, greno@xxxxxxxxxxx wrote:
You mean like this?: disk = [ 'file:/tmp/ubuntu/10.04/ubuntu-10.04-server-amd64.iso,hdc:cdrom,r', "tap:aio:/var/lib/xen/images/CLOUD-CC-1.img,xvda,w" ]
Gives me the exact same result: Error: Boot loader didn't return any data!
I've verified the paths to the kernel and ramdisk. It's weird because I did this some time ago without any problem. But now it doesn't work. Maybe because I updated to Xen 4.0.0-rc8? Pygrub says version 0.6 inside it.
-Gerry
Jun 13, 2010 06:19:46 PM, tknchris@xxxxxxxxx wrote:
Why not just use file: and iso path? I don't see any benefit to another layer of abstraction
Sent from my iPhone
On Jun 13, 2010, at 5:49 PM, greno@xxxxxxxxxxx wrote:
> I mounted an iso file like so: >
------------------------------------------- > # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt > #ls /tmp/mnt > cdromupgrade dists doc install isolinux md5sum.txt pics pool > preseed README.diskdefines ubuntu > ------------------------------------------- > > I used the following file to try to have pygrub boot the mounted iso: > ------------------------------------------- > name = "RESCUE" > memory = 1024 > vcpus = 4 > bootloader = '/usr/local/bin/pygrub' > kernel = "/boot/vmlinuz-2.6.32.13" > ramdisk = "/boot/initrd.img-2.6.32.13" > disk = [ > 'phy:/dev/loop0,hdc:cdrom,r', > "tap:aio:/var/lib/xen/images/CLOUD-CC-1.img,xvda,w" > ] > > > > > vfb = [ 'type=vnc,vncunused=1' ] >
------------------------------------------- > > Then I tried to create: > ------------------------------------------- > # xm create test.py > Using config file "./test.py". > Error: Boot loader didn't return any data! > ------------------------------------------- > > Is there something else I need to get pygrub to boot an iso? > > -Gerry > > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|