Unable to start WinXP using virt-manager

Bug #241786 reported by Michael Monreal
8
Affects Status Importance Assigned to Milestone
virt-manager (Fedora)
Won't Fix
Medium
virt-manager (Ubuntu)
Invalid
Undecided
Michael Monreal

Bug Description

After installation of WinXP in virt-manager (using KVM) I get this while trying to boot: Disk read error

Revision history for this message
In , Mihai (mihai-redhat-bugs) wrote :

Description of problem:

When try to install winXp in a qemu VM with virt-manager I see that:

Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed internal error QEMU quit during console startup
qemu: could not open disk image /home/mihai/xp.img

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 651, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 845, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 866, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 833, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: virDomainCreateLinux() failed internal error QEMU quit during
console startup
qemu: could not open disk image /home/mihai/xp.img

'

Version-Release number of selected component (if applicable):

Fedora Rawhide update 17.04.2008
virt-manager-0.5.4-3.fc9.i386
qemu-0.9.1-5.fc9.i386
libvirt-0.4.2-1.fc9.i386

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
Michael Monreal (mimox) wrote :
Revision history for this message
Michael Monreal (mimox) wrote :

I have now installed the Intrepid Alpha release on another partition and I got the same problem there. WinXP installs just fine from CD but at the first boot it says the HDD is corrupted. The installation is completed at this point though (seems to be successful, see screenshot)

Revision history for this message
Michael Monreal (mimox) wrote :
Revision history for this message
Michael Monreal (mimox) wrote :

Also I was able to install WinXP using kvm command line just fine... and virt-manager was able to boot WinXP after installing it using qemu. What's wrong with ubuntu's virt-manager setup?

Changed in virt-manager:
status: Unknown → Confirmed
Revision history for this message
Cédric Belin (cedx) wrote :

I'm using Ubuntu Desktop 8.10 Intrepid 64 bits with virt-manager 0.5.4-2ubuntu1, kvm 72+dfsg-1ubuntu6 and libvirt 0.4.4-3ubuntu3.

If I install AND run a Windows XP system with kvm command line, everything works fine.
If I install OR run the Windows XP system with virt-manager, I obtain disk errors and the system reboots all the time.

With my previous Ubuntu system (8.04 Hardy 64 bits), virt-manager worked fine. It seems that the virt-manager version shipped with Intrepid has introduced regression(s). It's a critical error since the current virt-manager is useless for some guest OS.

Revision history for this message
Alvin (alvind) wrote :

There is a workaround for this problem posted in bug 105195, but the report of that bug may be inaccurate. Can someone confirm if this is a duplicate?

Revision history for this message
Kunio Murasawa (m92o) wrote :

I think, this is not a duplicate.

I tested Kubuntu 9.04 alpha 3 with virt-manager 0.6.0-6ubuntu1.
It works. (Windows XP install OK)

As CedX said, It might be virt-manager problem.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Changed in virt-manager (Fedora):
status: Confirmed → Won't Fix
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for reporting this issue. Do you still have this issue with recent versions of Ubuntu, such as Karmic or Lucid?

Changed in virt-manager (Ubuntu):
assignee: nobody → Michael Monreal (mimox)
status: New → Incomplete
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!

Changed in virt-manager (Ubuntu):
status: Incomplete → Invalid
Changed in virt-manager (Fedora):
status: Won't Fix → Invalid
Changed in virt-manager (Fedora):
importance: Unknown → Medium
status: Invalid → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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