From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Daniel Paquet <resminator-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: get_dirty_pages returned -2
Date: Wed, 08 Aug 2007 02:56:20 +0300 [thread overview]
Message-ID: <46B906A4.5000100@qumranet.com> (raw)
In-Reply-To: <9a1a10a40708071112g6080bc3cxc779b13f52149f8d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Daniel Paquet wrote:
> Hello Devs!
>
> On my haste to try new patches and stuff I got this error message
> looping and using 100% cpu when starting vista as guest.
>
> My host is a linux 2.6.22.1-cfs-v19 #1 SMP
>
> So I have the cfs scheduler patchs in.
>
> I have build kvm-33 on this new kernel.
>
> I dont get this get_dirty_pages returned -2 when starting xp guest.
>
> I am starting vista with those params.
>
> kvm -cdrom /dev/cdrom -boot c -hda disks/vista.qcow2 -localtime -m 512
> -net nic,model=ne2k_pci,macaddr=00:00:00:00:00:01 -net tap,ifname=tap0
> -std-vga
>
> Vista was running within kvm-29 and kernel 2.6.21.3 <http://2.6.21.3>
> without the cfs patch.
>
-std-vga is known broken. Avoid this switch and all will be well.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-07 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 18:12 get_dirty_pages returned -2 Daniel Paquet
[not found] ` <9a1a10a40708071112g6080bc3cxc779b13f52149f8d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-07 23:56 ` Avi Kivity [this message]
[not found] ` <46B906A4.5000100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-13 13:01 ` Daniel Paquet
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=46B906A4.5000100@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=resminator-Re5JQEeQqe8AvxtiuMwx3w@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 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.