From: Avi Kivity <avi@redhat.com>
To: Neo Jia <neojia@gmail.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: Windows guest debugging on KVM/Qemu
Date: Tue, 25 May 2010 11:24:54 +0300 [thread overview]
Message-ID: <4BFB8956.8070308@redhat.com> (raw)
In-Reply-To: <AANLkTineP1tXGgL9iTFilk8F90OmUx8nESgq6rjPbb8w@mail.gmail.com>
On 05/24/2010 11:07 PM, Neo Jia wrote:
> hi,
>
> I am using KVM/Qemu to debug my Windows guest according to KVM wiki
> page (http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging).
> It works for me and also I can only use one Windows guest and bind its
> serial port to a TCP port and run "Virtual Serial Ports Emulator" on
> my Windows dev machine.
>
> The problem is that these kind of connection is really slow. Is there
> any known issue with KVM serial port driver? There is a good
> discussion about the same issue one year ago. Not sure if there is any
> improvement or not after that.
>
How slow? Can you measure it (without a debugger, just guest-to-guest
file transfer)?
slirp used to be ridiculously slow but some recent change made it fairly
fast. Probably a missing wakeup, perhaps serial has the same problem.
In any case I recommend testing with qemu-kvm.git master.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Neo Jia <neojia@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: Windows guest debugging on KVM/Qemu
Date: Tue, 25 May 2010 11:24:54 +0300 [thread overview]
Message-ID: <4BFB8956.8070308@redhat.com> (raw)
In-Reply-To: <AANLkTineP1tXGgL9iTFilk8F90OmUx8nESgq6rjPbb8w@mail.gmail.com>
On 05/24/2010 11:07 PM, Neo Jia wrote:
> hi,
>
> I am using KVM/Qemu to debug my Windows guest according to KVM wiki
> page (http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging).
> It works for me and also I can only use one Windows guest and bind its
> serial port to a TCP port and run "Virtual Serial Ports Emulator" on
> my Windows dev machine.
>
> The problem is that these kind of connection is really slow. Is there
> any known issue with KVM serial port driver? There is a good
> discussion about the same issue one year ago. Not sure if there is any
> improvement or not after that.
>
How slow? Can you measure it (without a debugger, just guest-to-guest
file transfer)?
slirp used to be ridiculously slow but some recent change made it fairly
fast. Probably a missing wakeup, perhaps serial has the same problem.
In any case I recommend testing with qemu-kvm.git master.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-25 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 20:07 Windows guest debugging on KVM/Qemu Neo Jia
2010-05-24 20:07 ` [Qemu-devel] " Neo Jia
2010-05-25 8:24 ` Avi Kivity [this message]
2010-05-25 8:24 ` [Qemu-devel] " 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=4BFB8956.8070308@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=neojia@gmail.com \
--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 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.