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

[Aastha Mehta <aasthakm@xxxxxxxxx>]

On 1 October 2013 11:07, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Tue, 2013-10-01 at 09:55 +0100, Wei Liu wrote:
>> On Mon, Sep 30, 2013 at 09:39:31PM +0200, Aastha Mehta wrote:
>> > On 30 September 2013 14:50, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
>> > > On Fri, Sep 27, 2013 at 07:19:25PM +0200, Aastha Mehta wrote:
>> > > [...]
>> > >>
>> > >> Sorry, I am going around in circles :(
>> > >> As you suggested to first try with stock kernel, I was trying to create 
>> > >> a
>> > >> baseline VM. And I am missing something somewhere.
>> > >>
>> > >
>> > > OK, does your baseline VM boot? Make sure it boots before using your
>> > > kernel.
>> > >
>> > >> I added path to modified kernel and initrd in the config file, and then
>> > >> this is what happens:
>> > >>
>> > >
>> > > Looks like there's something wrong with hotplug scripts.
>> > >
>> > > This page contains useful info on how to collect necessary info.
>> > >
>> > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen
>> > >
>> > > Wei.
>> >
>> > No, I am not even able to boot my baseline VM (specifying only the
>> > mirror and no modified kernel). This is the error I get:
>> > Parsing config from /etc/xen/precise-guest.cfg
>> > libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader
>> > failed - consult logfile /var/log/xen/bootloader.3.log
>> > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
>> > bootloader [19273] exited with error status 1
>> > libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot
>> > (re-)build domain: -3
>> >
>> > And /var/log/xen/bootloader.3.log contains:
>> > File "/usr/lib/xen-default/bin/pygrub", line 763 in <module>
>> >    raise RuntimeError, "Unable to find partition containing kernel"
>> >
>>
>> I don't think xen-create-image adds pygrub, does it?
>
> It seems to depend on the distro, from xen-create-image:
>     #  Lucid and probably all later Ubuntus, too, don't work without pygrub
>     #
>     if ( $CONFIG{ 'dist' } =~ /lucid|maverick|natty|oneiric|precise|quantal/ )
>     {
>         $CONFIG{ 'pygrub' } = 1;
>     }
>
> xl -vvv create should give us the bootloader command line used, which
> will be helpful.
>
> Ian.
>

Yes, specifying either the bootloader or kernel image is mandatory. I
get the same behaviour even with a debian distro mirror image. 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

Thanks


-- 
Aastha Mehta
MPI-SWS, Germany
E-mail: aasthakm@xxxxxxxxxxx

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