public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gregory Haskins" <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Success!
Date: Mon, 12 Mar 2007 19:46:28 -0400	[thread overview]
Message-ID: <45F5AE1B.BA47.005A.0@novell.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]


Im pleased to report that with the addition of the PIIX3 fix I posted earlier coupled with the reversion of 4423, we can now put SUSE Linux Enterprise Desktop on the list of booting guests.  This is verified with 64 bit on 64 bit on Intel only.  The GRUB segfault that I was seeing in 12/13 is fixed also once moving to the KVM-16 codebase, so the whole thing is working appropriately now.  Thanks for all the help guys!  

Attached, please find a tarball and a quilt series on the patches we are using to run this on SLEx (I excluded the patches obtained from the tree).  I dont expect most of them to be adopted into the tree.  I am just sharing them in case someone else wants to run on SUSE or has similar problems.   One of the patches adds a rudimentary trace facility that printks VMEXIT activity (mostly only supporting Intel, however).  It also has an optional mode that allows you to turn on single-step breakpoints so that you can watch the RIP for each op-code.  Note however that turning single-step on seems to change the behavior (takes unexpected triplefaults) so its not fully baked.  The non-singlestep mode was quite helpful in tracking down the real-mode problems I was having with the 4423 BIOS.

We will have to figure out what the problem in the BIOS is w.r.t. 4423 before this will work with the code in /trunk, however.

-Greg

[-- Attachment #2: patches.tar.bz2 --]
[-- Type: application/octet-stream, Size: 51200 bytes --]

[-- Attachment #3: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

             reply	other threads:[~2007-03-12 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 23:46 Gregory Haskins [this message]
     [not found] ` <45F5AE1B.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-13  9:46   ` Success! Avi Kivity
     [not found]     ` <45F67312.4090105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-13 12:44       ` Success! Avi Kivity
     [not found]         ` <45F69C98.1020209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-13 13:22           ` Success! Avi Kivity

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=45F5AE1B.BA47.005A.0@novell.com \
    --to=ghaskins-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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