unable to boot linux vm's that are not Debian derived.

Bug #220463 reported by Jayson Rowe on 2008-04-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
kvm (Ubuntu)
Declined for Intrepid by Dustin Kirkland 
libvirt (Ubuntu)
Declined for Intrepid by Dustin Kirkland 

Bug Description

Binary package hint: virt-manager

I am unable to start any Linux Virtual Machine that is not of Debian decent. I have tried Ubuntu, Debian Etch, Debian Lenny, Parsix, Elive, Mepis and Fluxbuntu. All these distros of Debian heritage run fine. Anything else gives the error: "Attempted DOS System Call" on boot-up. The Fedora Live-CD will not boot - gives that error from the start. I can install Foresight Linux, however I get the boot after installation has completed and the virtual machine is rebooted. I have attached screenshots. Please let me know any additional information you might need. I'm reporting this as a virt-manager error rather than a kvm error because I can start the virtual machines from the command line w/ kvm...the problem only exists when using virt-manager.

jayson@jlr:~$ uname -a
Linux jlr 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

jayson@jlr:~$ apt-cache policy virt-manager
  Installed: 0.5.3-0ubuntu8
  Candidate: 0.5.3-0ubuntu8
  Version table:
 *** 0.5.3-0ubuntu8 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Jayson Rowe (jayson.rowe) wrote :
Jayson Rowe (jayson.rowe) wrote :
Soren Hansen (soren) wrote :


I think this is an extboot problem. I can run those CD's just fine with -cdrom path/to/the/iso, but with -drive file=/path/to/the/iso,if=ide,media=cdrom,boot=on it fails.

ivom (ivo-maljevic) wrote :

Among so many other problems with this tool I ran into this same problem. The workaround that worked for me:

- close virt-manager and instead run the kvm on the .img file from the command line untill you install your OS (eg., live CD, ISO, etc. )
- One you do this, your HD will be bootable and virt-manager will work.

Of course, it would be better if there was a real fix.

Dustin Kirkland  (kirkland) wrote :

Changing to virt-manager, as this works for me from the command line, per Soren's instructions, not so much from virt-manager GUI.


Changed in kvm:
importance: Undecided → Wishlist
status: New → Confirmed
Dustin Kirkland  (kirkland) wrote :

I'm actually getting this same error message when trying to boot Debian mini.iso's for Lenny and Sid, both i386 and amd64.


Dustin Kirkland  (kirkland) wrote :

I'm elevating the importance from Wishlist to Medium. This is a rather annoying issue, and significantly limits virt-manager's usage on Ubuntu.


Changed in virt-manager:
importance: Wishlist → Medium
Soren Hansen (soren) wrote :

It's a kvm (extboot, actually) problem.

Jason Gerard DeRose (jderose) wrote :

This also might be a bug in the vgabios package. See this bug in the Redhat bugzilla:


Jason Gerard DeRose (jderose) wrote :

After more investigation, it seems the bug is in neither with kvm nor vgabios. The problem seems to be with the way libvirt is invoking kvm/qemu.

Trying to install Fedora 9 onto a VM using virt-install results in the "Attempted DOS System Call" error, but I can manually create the VM without virt-install and the installer works fine.

Manual Steps:

1. I created the disk image:

  qemu-img create fedora.img 2G

2. I booted the ISO using kvm directly:

  kvm -cdrom Fedora-9-i386-disc1.iso -boot d fedora.img

In case the problem was with virt-install and not libvirt, I tried modifying the XML defining my fedora VM manually so it booting from the ISO... and again, same "Attempted DOS System Call" error, which again suggest the bug is in libvirt.

The sf bug #1977971 regarding kvm makes it clear that this is not really a bug but an issue of incorrect invocation. Perhaps a workaround will be added to kvm, but libvirt should be fixed to invoke it correctly.

Anders Kaseorg (andersk) wrote :

Here’s a debdiff that adds a patch extracted from the libvirt-0.4.4-2.fc9 RPM <ftp://download.fedora.redhat.com/pub/fedora/linux/updates/testing/9/SRPMS/libvirt-0.4.4-2.fc9.src.rpm>. I just tested it and it indeed fixes this problem.

Kai Blin (kai.blin) wrote :

Any news on this one?

Dustin Kirkland  (kirkland) wrote :

I'm marking this as Fix Released.

Previously, I could not boot Fedora or Debian install media, or virtual machines. I'm now able to boot and run both.

Please re-open with details, if this is still a problem for you.


Changed in kvm:
status: Confirmed → Fix Released
Changed in libvirt:
status: New → Fix Released
Dustin Kirkland  (kirkland) wrote :

This was actually a bug in libvirt, not kvm. Marking the kvm task 'Invalid'.


Changed in kvm:
status: Fix Released → Invalid
laksdjfaasdf (laksdjfaasdf) wrote :

Is there any chance, that this patch will be backported to Ubuntu Hardy, too?

freakalad (freakalad) wrote :

Issue is still present, even after numerous updates & releases (discrepancies between KVM, libvirt & virt-manager seem to be getting more pronounced)
Hardy 64.

Dustin Kirkland  (kirkland) wrote :

Declining for intrepid and hardy.

These issues should be fixed in the kvm-84 package that's available in hardy-backports and intrepid-backports. If this issue is still critical to you, please try those packages.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.