[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] cannot boot guest VM

Fdisk -l gives:

You must set cylinders.
You can do this from the extra functions menu.

Disk debian-blktap2.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d818e

             Device Boot      Start         End      Blocks   Id  System
debian-blktap2.img1   *           1         996     7993344   83  Linux
Partition 1 does not end on cylinder boundary.
debian-blktap2.img2             996        1045      392193    5  Extended
Partition 2 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(1044, 52, 32)
debian-blktap2.img5             996        1045      392192   82  Linux swap / 

The " You must set cylinders." And "0 MB, 0 bytes" are a bit worrisome, no?

/usr/local/bin/pygrub and /usr/bin/pygrub are the same file.

Am I using any non-standard configuration option? Is there a more reliable way 
to deploy a PV VM in xen-unstable?


-----Original Message-----
From: Ian Campbell 
Sent: 12 June 2012 10:14
To: Thanos Makatos
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] cannot boot guest VM

On Fri, 2012-06-08 at 14:32 +0100, Thanos Makatos wrote:
> When I try to see what goes wrong with pygrub (pygrub <image-file>), I 
> get the following error:
> Traceback (most recent call last):
>   File "/usr/local/bin/pygrub", line 822, in <module>
>     raise RuntimeError, "Unable to find partition containing kernel"
> RuntimeError: Unable to find partition containing kernel

> Does this mean that something went terribly wrong during the 
> installation?

I'd be more inclined to suspect something is wrong with pygrub.

BTW, you have /usr/local/bin/pygrub which is a bit odd, I'd expect either 
/usr/bin/pygrub or /usr/lib/xen.../bin/pygrub depending on howup to date your 
xen-unstable is. Do you have multiple copies of pygrub on your system?

What does fdisk say about your partitions? Is one of them marked bootable? I 
think "fdisk -l /path/to/img" will tell you...

BTW -- you can drop the "extra" line when using pygrub.
> Begin: Running /scripts/init-bottom ... mount: mounting /dev on 
> /root/dev failed: No such file or directory
> done.
> mount: mounting /sys on /root/sys failed: No such file or directory
> mount: mounting /proc on /root/proc failed: No such file or directory
> Target filesystem doesn't have requested /sbin/init.
> No init found. Try passing init= bootarg.

This is because when replicating pygrub manually as well as extracting the 
kernel + initrd you need to pull the command line out of the guest's grub cfg 
and include it as the "extra" line in your cfg.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.