All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Ning <yu.ning@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
	Thomas Huth <huth@tuxfamily.org>,
	qemu-devel <qemu-devel@nongnu.org>, Stefan Weil <sw@weilnetz.de>
Cc: Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] HAXM is now open source
Date: Fri, 17 Nov 2017 16:17:13 +0800	[thread overview]
Message-ID: <a1648b4d-946f-49c4-93c5-5990baa0bce8@linux.intel.com> (raw)
In-Reply-To: <cdd6e0a4-93cd-66ca-5e69-7a834f0b10d0@redhat.com>



On 11/15/2017 22:18, Paolo Bonzini wrote:
> On 15/11/2017 09:25, Yu Ning wrote:
>>
>> On 11/15/2017 3:13, John Snow wrote:
>>> On 11/14/2017 06:09 AM, Thomas Huth wrote:
>>>> That's great news! I hope this all will help to promote QEMU on Windows
>>>> and macOS quite a bit!
>>>>
>>>> However, during the past months, I noticed a couple of times that users
>>>> ask on IRC or the qemu-discuss mailing list how they could accelerate
>>>> their QEMU on Windows - and they are running only in TCG mode when you
>>>> ask how they start QEMU. So it seems like there is not much knowledge
>>>> about "--accel hax" in the public yet. Maybe you could write a nice blog
>>>> post for the QEMU blog or something similar that explains how to use
>>>> HAXM with QEMU on Windows for the normal users? Or maybe make it more
>>>> prominent in the QEMU wiki? (e.g. the main page only mentions KVM and
>>>> Xen, but not HAXM)
>>> A blog post advertising this new development would be an absolute
>>> miracle for linking to people who are just getting started with QEMU on
>>> Windows.
>>>
>>> (It would also be really good for idiots like me, who do not use Windows
>>> for anything other than playing video games and sometimes forget that it
>>> is capable of doing other things.)
>> Thanks for the encouragement.
>>
>> I think I can start by writing a small section that can be added to an
>> existing document, and later expanded to a blog article. But I haven't
>> found a suitable place for it on the QEMU wiki.
>>
>> Does it make sense to add the proposed piece to the QEMU user manual
>> (qemu-doc.texi), under the Quick Start section (2.2)? The user manual is
>> published on Stefan's website and referred to by qemu.org:
>>
>> https://qemu.weilnetz.de/doc/qemu-doc.html
> Unfortunately the "Quick Start" section is quite out of date (it doesn't
> even mention KVM!) and is basically a huge list of options.  We are in
> the process of improving QEMU documentation, so I think a blog post is
> preferrable at this stage.
>
>
I see. I'll take the advice.

Is there a preferred document format for the QEMU blog, e.g. Markdown? 
I'll get the content ready by early next week, and then I'll need 
someone to help me post it.

  reply	other threads:[~2017-11-17  8:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14  8:54 [Qemu-devel] HAXM is now open source Yu Ning
2017-11-14 11:09 ` Thomas Huth
2017-11-14 19:13   ` John Snow
2017-11-15  8:25     ` Yu Ning
2017-11-15 14:18       ` Paolo Bonzini
2017-11-17  8:17         ` Yu Ning [this message]
2017-11-17  8:30           ` Thomas Huth
2017-11-17  8:34             ` Yu Ning
2017-11-17  8:53 ` Kamil Rytarowski
2017-11-17 10:30   ` Yu Ning
2017-11-17 11:09     ` Kamil Rytarowski

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=a1648b4d-946f-49c4-93c5-5990baa0bce8@linux.intel.com \
    --to=yu.ning@linux.intel.com \
    --cc=huth@tuxfamily.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    --cc=vpalatin@chromium.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.