http://bugzilla.novell.com/show_bug.cgi?id=530200 Summary: Kiwi cannot create xen images which use xen virtual block devices (/dev/xvda) instead of /dev/sda Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms@novell.com ReportedBy: jwilkins@appriss.com QAContact: adrian@novell.com Found By: --- Created an attachment (id=312084) --> (http://bugzilla.novell.com/attachment.cgi?id=312084) Fix to allow kiwi to create images which use /dev/xvda1 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 GTB5 If <xendisk device="/dev/xvda" /> is used in config.xml, a non-bootable image is generated. The image builds correctly, and the xenconfig file is correct, but booting fails in the initrd. The file "/usr/share/kiwi/image/xenboot/suse-linuxrc" is used to generate the initrd. It contains a function called VMFindSystem which is hard coded to use /dev/sda1 or /dev/hda1. Reproducible: Always Steps to Reproduce: 1. Change the example xen config.xml to include <xendisk device="/dev/xvda" /> 2. Prepare, create, and boot the image. 3. Watch it fall down, go boom. I've attached a patch which has solved the problem for me. I simplified some of the if/else structure in the function, but the implementation still seems inflexible. Is there really no deterministic way to set the device for the root filesystem? The linuxrc from mkinitrd uses: get_param() { echo $(eval echo \${cmd_${1/-/_}}) 2>/dev/null } Would that work for a xen guest? -- 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.