Mailinglist Archive: opensuse-bugs (6630 mails)

< Previous Next >
[Bug 530200] kiwi: xenboot failed when using xen virtual block devices /dev/xvda
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 12 Aug 2009 01:28:26 -0600
  • Message-id: <20090812072826.B44C3245514@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=530200

User ms@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=530200#c1


Marcus Schaefer <ms@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Summary|Kiwi cannot create xen |kiwi: xenboot failed when
|images which use xen |using xen virtual block
|virtual block devices |devices /dev/xvda
|(/dev/xvda) instead of |
|/dev/sda |




--- Comment #1 from Marcus Schaefer <ms@xxxxxxxxxx> 2009-08-12 01:28:25 MDT ---
an alternative solution would be to use the vmx image type instead
of the xen type. If you add the following line into your system image
config.xml

<type
filesystem="ext3"
bootprofile="xen" bootkernel="nex"
boot="vmxboot/suse-..."
>vmx</type>

and call kiwi --create ... --type vmx the result is a virtual disk
including the xen kernel and the xenconfig file uses the xen virtual block
device layer along with a tap device and the pygrub loader system.
the initrd code just detects a disk by using hwinfo which is a more
generic approach

Anyway you are right the domUloader system with the xenboot initrd must
be more flexible.

Thanks for the patch I'll check if we can make it more flexible and if
not I will check your version in

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References