Re: [Xen-users] Arch linux PV guest won't boot

[H C <hbc1024@xxxxxxxxx>]

Hi Ian,


>If you run "pygrub /path/to/disk.img" I expect it will report
>the same, but can you please confirm.

You are correct.  pygrub /vm/arch1/arch1.img returns the same error
message found in bootloader.XX.log

[root@earth ~]# pygrub /vm/arch1/arch1.img
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 886, in <module>
    raise RuntimeError, "Unable to find partition containing kernel"
RuntimeError: Unable to find partition containing kernel



>What does the partition table of your disk image look like?

[root@earth ~]# parted /vm/arch1/arch1.img
GNU Parted 3.2
Using /vm/arch1/arch1.img
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model:  (file)
Disk /vm/arch1/arch1.img: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name       Flags
 1      1049kB  21.5GB  21.5GB               Linux LVM  lvm

Ok, now that I'm looking at this here, i'm guessing you are going to say
either pygrub doesn't work with lvm or at the least has no idea how to find
the arch-root vg which contains  /boot/grub/grub.cfg.  I tired to google to see
how pygrub would be do that but didn't turn up anything.

If what I suspect is correct, could you give me a pointer on how I
would properly
setup  /boot/grub/grub.cfg so it is reachable by pygrub?




[root@earth ~]# xl -vvv create /vm/arch1/arch1.conf
Parsing config from /vm/arch1/arch1.conf
libxl: debug: libxl_create.c:1342:do_domain_create: ao 0xbe1a90:
create: how=(nil) callback=(nil) poller=0xbec9b0
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=xvda,
backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:286:libxl__device_disk_set_backend: Disk
vdev=xvda, using backend qdisk
libxl: debug: libxl_create.c:797:initiate_domain_create: running bootloader
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk
vdev=(null) spec.backend=qdisk
libxl: debug: libxl.c:2671:libxl__device_disk_local_initiate_attach:
locally attaching qdisk /vm/arch1/arch1.img
libxl: debug: libxl_bootloader.c:409:bootloader_disk_attached_cb:
Config bootloader value: pygrub
libxl: debug: libxl_bootloader.c:425:bootloader_disk_attached_cb:
Checking for bootloader in libexec path: /usr/lib/xen/bin/pygrub
libxl: debug: libxl_create.c:1356:do_domain_create: ao 0xbe1a90:
inprogress: poller=0xbec9b0, flags=i
libxl: debug: libxl_event.c:570:libxl__ev_xswatch_register: watch
w=0xbe2198 wpath=/local/domain/22 token=3/0: register slotnum=3
libxl: debug: libxl_event.c:1761:libxl__ao_progress_report: ao
0xbe1a90: progress report: ignored
libxl: debug: libxl_bootloader.c:535:bootloader_gotptys: executing
bootloader: /usr/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader
arg: /usr/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader
arg: --output=/run/xen/bootloader.22.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=/run/xen/bootloader.22.d
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys:   bootloader
arg: /vm/arch1/arch1.img
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0xbe2198
wpath=/local/domain/22 token=3/0: event epath=/local/domain/22
libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader
failed - consult logfile /var/log/xen/bootloader.22.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
bootloader [-1] exited with error status 1
libxl: debug: libxl_event.c:606:libxl__ev_xswatch_deregister: watch
w=0xbe2198 wpath=/local/domain/22 token=3/0: deregister slotnum=3
libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot
(re-)build domain: -3
libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0xbe1a90:
complete, rc=-3
libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0xbe1a90: destroy
xc: debug: hypercall buffer: total allocations:28 total releases:28
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:24 misses:2 toobig:2



 By the way, I located GrubConf but it keeps giving me
 Permission denied error. Though, I don't know how to use it.
 I tried to google but turned up nothing helpful.
 (grub.cfg.vm is the grub file from my vm)

 [root@earth grub]# ./GrubConf.py
-bash: ./GrubConf.py: Permission denied
[root@earth grub]# ./GrubConf.py grub2 grub.cfg.vm
-bash: ./GrubConf.py: Permission denied

On Wed, Oct 15, 2014 at 3:54 PM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote:
> On Wed, 2014-10-15 at 02:20 +0800, H C wrote:
>> >Which version of Xen are you using?
>>
>> 4.4
>>
>> I've made a bit of progress.  I'm not 100% sure why the log files were
>> zero bytes previously, though I just increased the memory for dom0
>> since dmesg showed it was running out and killing processes.  In
>> anycase, here is what I'm getting in /var/log/xen/bootloader.XX.log:
>>
>> Traceback (most recent call last):
>>   File "/usr/lib/xen/bin/pygrub", line 886, in <module>
>>     raise RuntimeError, "Unable to find partition containing kernel"
>> RuntimeError: Unable to find partition containing kernel
>>
>>
>> Now I tried editing the vm conf file to use xvda.  But no matter xvda
>> or hda I get the same error message above.
>>
>> When during the loading/booting process is that error thrown?
>
> It comes from pygrub itself which is being run early on in the domain
> construction process.
>
>>   Is Xen
>> even finding my grub file?
>
> No, it appears it isn't even finding the partition which should contain
> it.
>
> If you run "pygrub /path/to/disk.img" I expect it will report the same,
> but can you please confirm.
>
> It would also be useful to see the full logs from "xl -vvv
> create /vm/arch1/arch1.conf".
>
>> If it is finding the grub file is there a chance I'm not using the
>> right UUID?  Below is grub.cfg and what I have in my /etc/fstab file.
>
> These are in the guest? I don't think it is getting near to consulting
> these.
>
> What does the partition table of your disk image look like? (You
> provided a bunch of gdisk runes earlier, but I've no idea what they
> would result in.
>
> Ian.
>

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