All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-1958725 ] openSUSE 11.0 became broken with newer KVM
Date: Sun, 03 Aug 2008 08:34:16 +0000	[thread overview]
Message-ID: <E1KPZ2e-0002CG-Sl@565xhf1.ch3.sourceforge.com> (raw)

Bugs item #1958725, was opened at 2008-05-06 16:21
Message generated for change (Comment added) 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: Open
Resolution: None
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

             reply	other threads:[~2008-08-03  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03  8:34 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-03  8:34 [ kvm-Bugs-1958725 ] openSUSE 11.0 became broken with newer KVM SourceForge.net
2008-05-06 13:21 SourceForge.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1KPZ2e-0002CG-Sl@565xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.