But as mentioned before, for security reasons pvgrub (aka grub.xen) should be used anyhow.
So my approach to add that line to the code in driver.py is not that bad, is it? :-) Wouldn't that be a reason to consider adding this as a real patch as described in the previous mails? Regards, Eugen Zitat von Jim Fehlig <jfehlig@suse.com>:
On 06/02/2016 02:48 AM, Eugen Block wrote:
Hi,
Is your xen compute node running latest xen and libvirt, including the fix for bug#981094?
Yes it does:
---cut here--- compute1:~ # rpm -qi libvirt-1.3.4-573.1.x86_64 Name : libvirt Version : 1.3.4 Release : 573.1 Architecture: x86_64 Install Date: Do 26 Mai 2016 14:55:31 CEST Group : Development/Libraries/C and C++ Size : 106 License : LGPL-2.1+ Signature : RSA/SHA256, Mi 25 Mai 2016 19:31:20 CEST, Key ID a193fbb572174fc2 Source RPM : libvirt-1.3.4-573.1.src.rpm Build Date : Mi 25 Mai 2016 19:30:03 CEST Build Host : build78 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/Virtualization URL : http://libvirt.org/
##############################################
compute1:~ # rpm -qi xen-libs Name : xen-libs Version : 4.7.0_03 Release : 440.1 Architecture: x86_64 Install Date: Di 10 Mai 2016 13:59:52 CEST Group : System/Kernel Size : 1560640 License : GPL-2.0 Signature : RSA/SHA256, Fr 06 Mai 2016 16:33:12 CEST, Key ID a193fbb572174fc2 Source RPM : xen-4.7.0_03-440.1.src.rpm Build Date : Fr 06 Mai 2016 16:31:47 CEST Build Host : build74 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/Virtualization ---cut here---
Here are the logs from /var/log/libvirt/libxl/libxl-driver.log and /var/log/xen/bootloader.26.log
---cut here--- compute1:~ # tail /var/log/libvirt/libxl/libxl-driver.log 2016-06-02 10:32:59 CEST libxl: error: libxl_bootloader.c:635:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.26.log 2016-06-02 10:32:59 CEST libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [28303] exited with error status 1 2016-06-02 10:32:59 CEST libxl: error: libxl_create.c:1222:domcreate_rebuild_done: cannot (re-)build domain: -3
##############################################
compute1:~ # tail /var/log/xen/bootloader.26.log Traceback (most recent call last): File "/usr/lib/xen/bin/pygrub", line 923, in <module> part_offs = get_partition_offsets(file) File "/usr/lib/xen/bin/pygrub", line 114, in get_partition_offsets image_type = identify_disk_image(file) File "/usr/lib/xen/bin/pygrub", line 57, in identify_disk_image fd = os.open(file, os.O_RDONLY) OSError: [Errno 2] No such file or directory: 'rbd:images/551a1dd6-ce9b-44c9-87f4-c2058efd94f6_disk:id=openstack:key=<KEY>:auth_supported=cephx\\;none:mon_host=<HOST1>\\:6789\\;<HOST2>\\:6789\\;<HOST3>\\:6789'
Heh, I'd expect open(2) to fail on such a filename :-). I was thinking the dom0 bootloader code would 'block-attach' the rbd device to dom0, allowing pygrub to access it. I guess I was wrong about pygrub working with network-based block devices.
But as mentioned before, for security reasons pvgrub (aka grub.xen) should be used anyhow. Note also that pygrub doesn't know how to grok btrfs, so it wouldn't work for images on the local fs that contain btrfs either.
Regards, Jim
-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
-- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock@nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org