Problem when you run a SLES10 in QEMU/KVM

[Z37A]

I found a problem with QEMU/KVM when i run a SuSe Linux Enterprise Server 10 with any SP in KVM. The virtual machine don't started and remains in pause when started the GRUB stage.

For lucky i found a temporary solution, you need to start the virtual machine with a live CD and edit the /boot/grub/menu.lst to start with the /dev/hda* and not with de /dev/uid....

This problem started in Ubuntu Server 12.04, never had this problem in 10.04.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-kvm (not installed)
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: x86_64
Date: Wed May 9 17:04:05 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release x86_64
SourcePackage: qemu-kvm
UpgradeStatus: Upgraded to precise on 2012-05-08 (1 days ago)

[Z37A (juanzele)]

I needed to add that this problem did not occur in the pc where reported, occurred in another computer installed with 10.04 and 12.04 with x86_64 updated

[Serge Hallyn (serge-hallyn)]

Does SLES12 work successfully for you? (I ask because I have that available to test with)

[Z37A (juanzele)]

I think the problem may be in the way that identifies the virtual drives, since the problem happens when you try to default SuSe grub device by id.

PD: In this cases SuSe use GRUB 1.5

[Serge Hallyn (serge-hallyn)]

Could you post the xml file for the guest? Are you using virtio? Does switching to IDE help?

[Serge Hallyn (serge-hallyn)]

Ah, presumably you are using ide since you say you are using /dev/hda*. Sorry, i thought you had been talking about the hd(...) line in grub.

Can you post your grub.conf file (in addition to the xml file)?

Still waiting for a suse (12) guest to install so I can reproduce...

[Serge Hallyn (serge-hallyn)]

Could not reproduce with suse 12 - which makes sense if the problem is with grub 1.5. Will find 10 to try it.

[Z37A (juanzele)]

Serge, SLES12 not exist. You need to use SLES10 SuSe Linux Enterprise Server 10, no OpenSuSe! With SLES11 this problems don't exist.

Wait a minute, i'm downloading from server the xml and the functional menu.lst from GRUB

[Z37A (juanzele)]

Mi menu.lst from the virtual SuSe, I made two changes, disable the gfxmenu and change the id from device for hda1:

# Modified by YaST2. Last modification on Thu May 10 10:57:33 ART 2012
default 0
timeout 8
##YaST - generic_mbr
#gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 10 SP4
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.16.60-0.85.1-default root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts
    initrd /boot/initrd-2.6.16.60-0.85.1-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 10 SP4
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.16.60-0.85.1-default root=/dev/hda2 vga=0x314 showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /boot/initrd-2.6.16.60-0.85.1-default

[Z37A (juanzele)]

Mi XML:

<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
  virsh edit iPrint
or other application using the libvirt API.
-->

<domain type='kvm'>
  <name>iPrint</name>
  <uuid>562f1567-d9a8-12d4-1b34-4d893e92e1e0</uuid>
  <memory>1048576</memory>
  <currentMemory>1048576</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-1.0'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/vms-r0/Imagenes/iPrint.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/vms/ISOS/oes2sp3-x86_64-CD1.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' unit='1'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/vms/ISOS/SLES-10-SP4-DVD-x86_64-GM-DVD1.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='scsi' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:d1:e2:ee'/>
      <source bridge='br0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes'/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
</domain>

[Serge Hallyn (serge-hallyn)]

Quoting Z37A (<email address hidden>):
> Mi menu.lst from the virtual SuSe, I made two changes, disable the
> gfxmenu and change the id from device for hda1:
>
> # Modified by YaST2. Last modification on Thu May 10 10:57:33 ART 2012
> default 0
> timeout 8
> ##YaST - generic_mbr
> #gfxmenu (hd0,1)/boot/message
> ##YaST - activate
>
>
> ###Don't change this comment - YaST2 identifier: Original name: linux###
> title SUSE Linux Enterprise Server 10 SP4
> root (hd0,1)
> kernel /boot/vmlinuz-2.6.16.60-0.85.1-default root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts

What exactly did it look like before your changes? Was it root=UUID=... ?

[Z37A (juanzele)]

I replaced: gfxmenu (hd0,1)/boot/message
for: #gfxmenu (hd0,1)/boot/message

And, I replaced: kernel /boot/vmlinuz-2.6.16.60-0.85.1-default root=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part2 vga=0x314 resume=/dev/hda1 splash=silent showopts
for: kernel /boot/vmlinuz-2.6.16.60-0.85.1-default root=/dev/hda2 vga=0x314 resume=/dev/hda1 splash=silent showopts

PD: I confirm that SLES11 runs fine.

PD2: You can download ISOs from SLES10 in http://download.novell.com/ with a free account!

[Serge Hallyn (serge-hallyn)]

Reproduced in precise.

[Serge Hallyn (serge-hallyn)]

I was not able to reproduce this in a 12.10 system. However, the 12.10 system was intel, the 12.04 system was amd.

[Serge Hallyn (serge-hallyn)]

Yup, precise on intel is fine. This appears to be an AMD specific bug.

[Serge Hallyn (serge-hallyn)]

It's still present in 12.10 on AMD.

Marking this as also affecting the kernel as it's hard to believe that something affecting amd and not intel would not have its root in the different kernel module.

[Serge Hallyn (serge-hallyn)]

Hi kernel team,

this bug appears to only happen when using grub1 (sles10sp4 is an example). It occurs in precise and quantal, but only on AMD. It manifests in userspace as a 'kvm internal error: suberror 1' (see above for the precise error).

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 997311

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.