qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jiahuan Zhang <jiahuanzhang90@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU pipe implementation for Windows(host) Linux(guest) interaction
Date: Thu, 23 Feb 2017 09:19:43 +0000	[thread overview]
Message-ID: <20170223091943.GA10047@redhat.com> (raw)
In-Reply-To: <CAJy91Cav17O8N++OzmOJUUeZKa7_tZyRNgQ-KZkwR-wcv1oX=Q@mail.gmail.com>

On Thu, Feb 23, 2017 at 08:45:17AM +0100, Jiahuan Zhang wrote:
> Dear QEMU developers,
> 
> I am a student working on the host-guest interaction for a Windows Host and
> Linux Quest. Actually, I aim to make a universal pipe implementation for
> any host-guest interaction.

FWIW, there's already two general purpose host<->guest communication
channels for QEMU - virtio-serial (like a traditional serial port
but giving them names & allowing many to be create) and virtio-vsock
(like UNIX domain sockets, but across host/guest - alternatively like
TCP/IP sockets, but without network devices involved)

> I am now using a serial port to redirect to a pipe. This is working with
> LInux host and Linux guest by using "mkfifo" to create the pipe. However, I
> don't know how to create a pipe in Windows for QEMU usage.

IIUC, you don't need to pre-create the pipe on Windows with QEMU chardevs.
It looks like the code takes the filename you set, appends ".pipe" and
then calls CreateNamedPipe to create it pipe.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

      reply	other threads:[~2017-02-23  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  7:45 [Qemu-devel] QEMU pipe implementation for Windows(host) Linux(guest) interaction Jiahuan Zhang
2017-02-23  9:19 ` Daniel P. Berrange [this message]

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=20170223091943.GA10047@redhat.com \
    --to=berrange@redhat.com \
    --cc=jiahuanzhang90@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 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).