Bugs item #1958725, was opened at 2008-05-06 16:21
Message generated for change (Settings changed) made by technologov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1958725&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: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Technologov (technologov)
Assigned to: Nobody/Anonymous (nobody)
Summary: openSUSE 11.0 became broken with newer KVM

Initial Comment:

Host OS: Fedora7/x64, kernel 2.6.21
Guest OS: openSUSE 11.0 BETA2, 32-bit x86 DVD ISO, kernel 2.6.25
CPU: Intel Core 2
KVM: KVM-67 (bug also valid for KVM-68)

KVM-67 broke openSUSE 11.0 on newer KVMs-67/68 on intel.

command:
./qemu-kvm -cdrom openSUSE-11.0-BETA2-32-bit.iso -m 512 -hda myharddisk.qcow2 
-boot d

Symptoms:
Red error message is displayed in the guest monitor, during setup stage2 (Yast) 
load.

I have bisected it.
qemu-merge for KVM-67 userspace is responsible for this bug, commit:
c33833a3f98b1bb9d8208b0ed115009bc20e6e87

Works fully on KVM-66. On KVM-67/68 it works only with "-no-kvm" parameter. 

FAILS with default parameters, fails with -no-kvm-acpi, -no-kvm-pit, 
-no-kvm-irqchip, and fails when guest is loaded with normal or FAILSAFE kernel 
boot parameters.
That is: fails in all cases.

-Alexey "Technologov", 6.May.2008.

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

Comment By: Technologov (technologov)
Date: 2008-08-03 11:34

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

Fixed.

openSUSE 11.0 Verified to work on KVM-71.

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

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

Reply via email to