qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dan Sandberg <dan.sandberg@medsci.uu.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu - bug with -m 256 <-please disregard
Date: Mon, 24 Apr 2006 15:28:23 +0200	[thread overview]
Message-ID: <444CD277.5090900@medsci.uu.se> (raw)
In-Reply-To: <444C8EA0.8020402@medsci.uu.se>

Dan Sandberg wrote:

> Brad Campbell wrote:
>
>> Troy Benjegerdes wrote:
>>
>>> On Thu, Feb 09, 2006 at 04:01:34PM -0600, Anthony Liguori wrote:
>>>
>>>> Jim C. Brown wrote:
>>>>
>>>>> -kernel-kqemu virtualizes ring 0 code.
>>>>>
>>>>> So it basically makes qemu do what VMware does.
>>>>>
>>>>> IIRC someone reported a 33% speedup with the new option.
>>>>>  
>>>>
>>>>
>>>> That was me.  That was a 33% speedup on win2k startup time.  kqemu 
>>>> (user only) has a negligible impact on win2k startup time which 
>>>> suggests this is mostly ring 0 code running which would make it a 
>>>> good benchmark for kernel-kqemu performance.
>>>>
>>>> This was a terribly unscientific benchmarking so don't read too 
>>>> much into it.
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>>
>>>
>>>
>>> My win2k guest (with SP4, but not any updates) seemed to hang on 
>>> startup
>>> with -kernel-kqemu.
>>
>>
>>
>> Are you using -m 256 by any chance? I get this result with around 
>> that much ram allocated to the guest. -m 160 (or less) or -m 384 (or 
>> more) works perfectly here..
>>
>>
>>
> Great tip -thank you!
>
> I have been having the same headache as others: Linux and RectOS 
> guests constantly crashing in the very same spot when -kernel-kqemu is 
> enabled.
> I just made a quick test adding -m 384 and ReactOS suddenly boots all 
> the way with -kernel-kqemu enabled!
> My test line was:
> qemu.exe -kernel-kqemu -m 384 -L ./bios -boot c -hda c.img
>
> Best regards,
> Dan Sandberg
>
Sorry!
Monday morning, coffee machine broken and my test far TOO quick since I 
forgot to start the kqemu service first and used a double-click script 
with the result that I missed the warning message that kqemu actually 
wasn´t running.
With -kernel-kqemu enabled I now get the same nasty bug as before 
regardless of -m 160, 256, 384 or 512..
Best regards,
Dan Sandberg

>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

  reply	other threads:[~2006-04-24 13:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 23:04 [Qemu-devel] -kernel-kqemu Jim C. Brown
2006-02-09  1:27 ` Jim C. Brown
2006-02-09  8:46   ` Hetz Ben Hamo
2006-02-09 18:05     ` Jim C. Brown
2006-02-09 22:01       ` Anthony Liguori
2006-02-09 23:32         ` Phil Krylov
2006-02-10 14:24           ` G Portokalidis
2006-04-19 17:31         ` Troy Benjegerdes
2006-04-21 21:09           ` Brad Campbell
2006-04-24  8:38             ` [Qemu-devel] -kernel-kqemu - bug with -m 256 Dan Sandberg
2006-04-24 13:28               ` Dan Sandberg [this message]
2006-04-24 22:31             ` [Qemu-devel] -kernel-kqemu Fabrice Bellard
2006-02-09 18:35     ` Anthony Liguori
2006-02-09 22:01       ` Fabrice Bellard
2006-02-11  3:02         ` Kazu
2006-02-09 16:27 ` Brad Campbell
2006-02-10 13:29 ` Christian MICHON
2006-02-10 16:18   ` Jim C. Brown

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=444CD277.5090900@medsci.uu.se \
    --to=dan.sandberg@medsci.uu.se \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).