Re: [Xen-users] question regarding booting custom guest kernel

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2013-10-01 at 22:26 +0200, Aastha Mehta wrote:
> Here is the output of # xl -vvv create /etc/xen/precise-guest.cfg
> 
> Parsing config from /etc/xen/precise-guest.cfg
> libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x665600: create: 
> how=(nil) callback=(nil) poller=0x664db0
> libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk 
> vdev=xvda2 spec.backend=unknown
> libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=xvda2, backend 
> phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:212:disk_try_backend: Disk vdev=xvda2, backend 
> tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk 
> vdev=xvda2, using backend qdisk
> libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk 
> vdev=xvda1 spec.backend=unknown
> libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=xvda1, backend 
> phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:212:disk_try_backend: Disk vdev=xvda1, backend 
> tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk 
> vdev=xvda1, using backend qdisk
> libxl: debug: libxl_create.c:675:initiate_domain_create: running bootloader
> libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk 
> vdev=(null) spec.backend=qdisk
> libxl: debug: libxl.c:2641:libxl__device_disk_local_initiate_attach: locally 
> attaching qdisk /home/domains/precise-guest/disk.img
> libxl: debug: libxl_bootloader.c:409:bootloader_disk_attached_cb: Config 
> bootloader value: /usr/lib/xen-default/bin/pygrub
> libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x665600: inprogress: 
> poller=0x664db0, flags=i
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0x663d58 
> wpath=/local/domain/9 token=3/0: register slotnum=3
> libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao 0x665600: 
> progress report: ignored
> libxl: debug: libxl_bootloader.c:535:bootloader_gotptys: executing 
> bootloader: /usr/lib/xen-default/bin/pygrub
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> /usr/lib/xen-default/bin/pygrub
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> --args=root=/dev/xvda2 ro
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> --output=/var/run/xen/bootloader.9.out
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> --output-format=simple0
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> --output-directory=/var/run/xen/bootloader.9.d
> libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader arg: 
> /home/domains/precise-guest/disk.img
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x663d58 
> wpath=/local/domain/9 token=3/0: event epath=/local/domain/9
> libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - 
> consult logfile /var/log/xen/bootloader.9.log
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader 
> [31916] exited with error status 1
> libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch 
> w=0x663d58 wpath=/local/domain/9 token=3/0: deregister slotnum=3
> libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build 
> domain: -3
> libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x665600: complete, 
> rc=-3
> libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x665600: destroy
> xc: debug: hypercall buffer: total allocations:31 total releases:31
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:27 misses:2 toobig:2

What is the output of:
        /usr/lib/xen-default/bin/pygrub --entry=0 
/home/domains/precise-guest/disk.img
?

And what about:
        fdisk -l /home/domains/precise-guest/disk.img
?

If it has no partition table are you able to
        mount -o loop /home/domains/precise-guest/disk.img /mnt
?

If it has a partition table are you able to
        kpartx -a /home/domains/precise-guest/disk.img
        mount /dev/mapper/.....
for any/all of the partitions?
(I forget how kpartx names things, it should be obvious in ls)

What are the filesystems used? Are you able to locate one with a
grub.cfg and/or a kernel on it?

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users