[ kvm-Bugs-1902416 ] After upgrade to kvm 60 release 2.fc8 problem with XP image

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bugs item #1902416, was opened at 2008-02-26 19:40
Message generated for change (Comment added) made by jessorensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1902416&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jeff Nessen (jnessen)
Assigned to: Nobody/Anonymous (nobody)
Summary: After upgrade to kvm 60 release 2.fc8 problem with XP image

Initial Comment:
I am running the latest update from the Fedora 8 updates repository (as of this morning).  I was able to boot my XP image using qemu-kvm -m 512 -hda kvm-xp.qcow2

The system booted the first time, but crashed at some point when it was running.  Sorry I had another window up in front of it, so I could not see exactly what happened.  When I returned to the qemu window, it was at the POST/BIOS screen and the last message said

Disk Read Error
Press ctrl+alt+delete to restart

I tried to restart qemu-kvm but got the same error at the same place.  The windows system was not doing anything in the background, just sleeping with a blank screen when the crash occurred.

----------------------------------------------------------------------

>Comment By: Jes Sorensen (jessorensen)
Date: 2010-06-18 16:07

Message:
Hi,

This was fixed in an update to Fedora 8 per the bugzilla listed below, so
closing this bug.

If you see this problem in a more recent version, please open a new bug
against that in launchpad.

Thanks,
Jes


----------------------------------------------------------------------

Comment By: Jeff Nessen (jnessen)
Date: 2008-02-26 22:34

Message:
Logged In: YES 
user_id=16852
Originator: YES

So does this mean it is a Fedora specific (package) problem or does it
apply at the KVM level?

----------------------------------------------------------------------

Comment By: Daniel Berrange (danpb)
Date: 2008-02-26 22:14

Message:
Logged In: YES 
user_id=73606
Originator: NO

FYI This problem is being tracked in the Fedora bugzilla for the KVM rpm

https://bugzilla.redhat.com/show_bug.cgi?id=434978

It was caused by the recent patch to fix the block device range checking
security flaw.
It will impact any grow-on-demand disk format such as QCow and result in
serious data loss/corruption

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1902416&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux