public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply-pyega4qmqnRoyOMFzWx49A@public.gmane.org>
To: noreply-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: [ kvm-Bugs-1629495 ] QEMU / KVM incompatibility
Date: Sat, 06 Jan 2007 09:59:59 -0800	[thread overview]
Message-ID: <E1H3Fpn-0005OT-Fd@sc8-sf-web2.sourceforge.net> (raw)

Bugs item #1629495, was opened at 2007-01-06 18:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1629495&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: shutdown2k (shutdown2k)
Assigned to: Nobody/Anonymous (nobody)
Summary: QEMU / KVM incompatibility

Initial Comment:
System:
Debian Etch RC3, Kernel 2.6.20-rc3
AMD Athlon X2
External KVM Modules (up2date svn version)

Problem:
qemu-system-x86_64 -m 384 -no-acpi -L ./bios -std-vga -soundhw es1370 -localtime -hda ./vdisk_xp.img -boot c

QEMU window shows up very for a very short time and terminates within less than a second.
The only message I get is: "vga_bios_size 0"

I am using the VGA BIOS from http://www.nongnu.org/vgabios/ version 0.6a.

There are 2 workarounds that work for me:
1. Disable KVM:
qemu-system-x86_64 -m 384 -no-acpi -L ./bios -std-vga -soundhw es1370 -localtime -hda ./vdisk_xp.img -boot c -no-kvm
Don't like it because this virtual machine 's gonna be really sloooooow and actually renders the Pacifica instructions of my CPU useless.
"vga_bios_size 0" is also reported when starting it that way.

2. Disable VESA graphics:
qemu-system-x86_64 -m 384 -no-acpi -L ./bios -soundhw es1370 -localtime -hda ./vdisk_xp.img -boot c
Don't like this because graphics will be somewhat limited in the virtual machine...
This solution doesn't report "vga_bios_size 0", so I guess this message is related to -std-vga and is not responsible for my problem at all.

So it would be great if you could figure out what's wrong and fix it.

You guys are doing a really great job, I enjoy using the Pacifica instructions of my CPU a lot :)

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1629495&group_id=180599

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

                 reply	other threads:[~2007-01-06 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1H3Fpn-0005OT-Fd@sc8-sf-web2.sourceforge.net \
    --to=noreply-pyega4qmqnroyomfzwx49a@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox