Mailinglist Archive: opensuse-bugs (4669 mails)

< Previous Next >
[Bug 635361] try to create a VM in xen result every time in error
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 1 Sep 2010 14:59:21 +0000
  • Message-id: <20100901145921.EC7D824551D@xxxxxxxxxxxxxxxxxxxxxx>

https://bugzilla.novell.com/show_bug.cgi?id=635361

https://bugzilla.novell.com/show_bug.cgi?id=635361#c2


Charles Arnold <carnold@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |WONTFIX

--- Comment #2 from Charles Arnold <carnold@xxxxxxxxxx> 2010-09-01 14:59:21 UTC
---
The problem is with the opensuse 11.2 menu.lst file. Pygrub looks at this file
to determine which kernel to boot. In 11.2, the default in menu.lst for a
paravirtualized xen guest actually points to the native kernel instead of the
xen kernel. This is not a problem if domUloader is used because it just grabs
the kernel and initrd based on a hardcoded path (/boot/vmlinuz-xen and
/boot/initrd-xen) and ignores menu.lst. You have a couple options to fix the
problem.

1) As you already noticed, you can use the 11.2 configuration file from
/etc/xen/vm on 11.3 to boot the guest.
2) In 11.2, start the guest and edit the menu.lst file and change the 'default'
field to point at the entry containing the xen kernel (vmlinuz-xen). This
won't effect starting the guest on 11.2 because domUloader doesn't care about
menu.lst.

Because we can't change the already shipping media in 11.2 nor are we willing
to use domUloader in 11.3 for opensuse 11 guests, these are the only solutions
to the problem.

Thank you for entering the bug.

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

< Previous Next >