public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Mark Clarkson <mark.clarkson-Sphq+rzYrv710XsdtD+oqA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: White screen
Date: Mon, 18 Dec 2006 10:07:13 +0200	[thread overview]
Message-ID: <45864C31.8080907@qumranet.com> (raw)
In-Reply-To: <1166406561.3448.28.camel@localhost>

Mark Clarkson wrote:
> Hi,
> When using WinXP I get a completely white screen whenever I change the
> resolution and just before the Windows GUI comes up, which lasts for
> around 20 seconds. 

That is a known issue.  Windows is clearing the screen using mmio 
writes.  We have hacks to convert the mmio writes to regular RAM writes, 
but they aren't effective for the screen clearing.  It is likely 
fixable, just haven't gotten around to it.


> Also, as with Xen HVM, network performance is poor,
> although it seems to be faster than WinXP under Xen. Do you expect
> network performance to be good enough for server use in a guest in the
> future, maybe once the MMU has been improved, or will you go the same
> route as Xen and provide non-free guest network drivers?
>   

We intend, at first, to improve fully virtualized performance as far as 
we are able, without resorting to paravirtualized drivers.

Should performance not be satisfactory to our needs, we may write 
paravirtualized devices and drivers.  If we do so, I can't commit as to 
whether the paravirtualized Windows drivers will be open or not (I'm not 
saying the drivers will be closed -- just that no decision has been made).

However, if you (or anyone) is interested in writing paravirtulized 
drivers, we will work with you towards merging them into the kernel and 
into the kvm distribution.  We welcome such contributions and will 
cooperate fully.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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:[~2006-12-18  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  1:49 White screen Mark Clarkson
2006-12-18  8:07 ` Avi Kivity [this message]
     [not found]   ` <45864C31.8080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-18  8:16     ` Dor Laor
2006-12-19 10:53     ` Mark Clarkson
2006-12-19 11:08       ` 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=45864C31.8080907@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mark.clarkson-Sphq+rzYrv710XsdtD+oqA@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