PDA

View Full Version : SLES 11 SP3 Opensuse 42.1 Leap doesn't start as a virtual host



pfsas
29-Mar-2016, 22:10
I run SLES 11 SP3 with several xen-based virtual machines (SLES11, Win and opensuse 13). I want to install new Opensuse Leap virtual host. Installation went OK, but VM refused to start telling me that the kernel was not found. I tried it again, checking if there was any issue during the installation, but couldn't see any.

Peter

jmozdzen
30-Mar-2016, 08:45
Hi Peter,

I run SLES 11 SP3 with several xen-based virtual machines (SLES11, Win and opensuse 13). I want to install new Opensuse Leap virtual host. Installation went OK, but VM refused to start telling me that the kernel was not found. I tried it again, checking if there was any issue during the installation, but couldn't see any.

what root fs are you using in your VM and have you set up a separate /boot partition? And am I assuming correctly that you're running the guest in paravirtualized mode?

How's the boot loader setup in the Xen configuration of this guest?

Regards,
Jens

pfsas
30-Mar-2016, 13:38
Hi Peter,


what root fs are you using in your VM and have you set up a separate /boot partition? And am I assuming correctly that you're running the guest in paravirtualized mode?

How's the boot loader setup in the Xen configuration of this guest?

Regards,
Jens

Hi Jens,
I kept all the proposed settings untouched, which means BtrFS for root partition, no separate /boot partition. And yes you are correct, I run it in paravirtualized mode.
During the installation the Boot options of VM says Kernel path: /tmp/kernel.something, Initrd path: /tmp/install-initrd.something and Kernel argumets: install=hd:/dev/xvdb - is this what you asked for?
After the installation VM restarts, then says No kernel was found and the disk image (which was created during the installation) disappears completely as well as the VM itself.

Peter

jmozdzen
31-Mar-2016, 09:30
Hi Peter,

I kept all the proposed settings untouched, which means BtrFS for root partition, no separate /boot partition. And yes you are correct, I run it in paravirtualized mode.

we've had our share of problems booting DomUs with BtrFS for root. We decided to generally use Ext4, but there may be a work-around, depending on the patch level of your Dom0 installation.


During the installation the Boot options of VM says Kernel path: /tmp/kernel.something, Initrd path: /tmp/install-initrd.something and Kernel argumets: install=hd:/dev/xvdb - is this what you asked for?
After the installation VM restarts, then says No kernel was found and the disk image (which was created during the installation) disappears completely as well as the VM itself.

No that wasn't what I was after - it's the configuration that's set up *after* the install phase.

During DomU installation, the boot loader grabs the kernel and initrd from the installation media, copies it to Dom0's /tmp and boots that - this is what you see and quoted above. Once the installation is "complete", IOW the first restart of the DomU is scheduled, those temporary files are deleted and the configuration updated to boot from the DomU's virtual disk.

If I got that right, we typically used the following boot loader config for BtrFS-based images (i.e. SLES12 or Leap, when configured all default):


builder="linux" # PVM
# bootloader="pygrub" # non-BtrFS
kernel="/usr/lib/grub2/x86_64-xen/grub.xen" # BtrFS

please note that this is from a SLES11SP*4* Dom0 (provided by grub2-x86_64-xen-2.00-0.57.1 in our case) - so please check first that this loader file is available on SP3...

If not and you cannot upgrade to SP4, install you VMs using Ext4 or at least put /boot on a separate, non-BtrFS partition.

Regards,
Jens

pfsas
07-Apr-2016, 10:02
Hi Jens,




No that wasn't what I was after - it's the configuration that's set up *after* the install phase.



As just after the installation my virtual machine disappeared together with the disk, I couldn't see the configuration, there was no file to read it from.

Nevertheless, the problem is now sold. First of all, I gave you bad version information. We are on SP4, not SP3. And it was not fully up-to-date. After latest update the installation went OK and virtual machine is running now. Anyway, thanks for your advice.

Peter

jmozdzen
07-Apr-2016, 11:02
Hi Peter,

thank you for reporting back.

> [SLES11SP4] After latest update the installation went OK and virtual machine is running now

yes that sounds reasonable - we had experienced that issue and worked with engineering to get it resolved :)

Glad you got your environment back to operational state!

Regards,
Jens