public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Using VMChannel to communicate with the host.
Date: Tue, 11 Sep 2007 10:09:58 +0300	[thread overview]
Message-ID: <46E63F46.2040707@qumranet.com> (raw)
In-Reply-To: <46E56A71.50102-edFDblaTWIyXbbII50Afww@public.gmane.org>

Cam Macdonell wrote:
>
> Dor Laor wrote:
> > I just tested it, it got a little deprecated over time since it call
> > pci_module_init instead of pci_register_* and some more irq function
> > deprecation.The sysfs interface in not complete and you can't read/write
> > from the device.
> > The qemu parameters are -vmchannel di:2258,unix:/tmp/file,server
> > 2258 is the vendor id for the device, you can use unix sockets ot even
> > tcp for the host end.
> >
>
> Hi Dor,
>
> Thanks, that got it up and running.  But in the hypercall.c code (from
> the git repo) there is a "hello host" message that looks like it should
> be written to the host.  How do I trigger that to be sent so my very
> simple "listening" program can read it?
>
> Thanks,
> Cam
>
You need to open the unix socket you passed to the vmchannel parameter.
An easier alternative is to use -vmchannel di:2258,tcp://0:4444,server.
Before the guest loads you'll need to telnet the 4444 port and then you 
should receive the
hello world output once the driver is up.
-Dor

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-11  7:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 22:44 Using VMChannel to communicate with the host Cam Macdonell
     [not found] ` <46E1D44E.90509-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-08  0:51   ` Troy Benjegerdes
     [not found]     ` <20070908005122.GB6764-na1kE3HDu0idQnJuSAr7PQ@public.gmane.org>
2007-09-09  8:38       ` Dor Laor
2007-09-09  9:56   ` Dor Laor
     [not found]     ` <46E3C345.9090305-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-10 16:01       ` Cam Macdonell
     [not found]         ` <46E56A71.50102-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-11  7:09           ` Dor Laor [this message]
     [not found]             ` <46E63F46.2040707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-11 14:36               ` Cameron Macdonell
     [not found]                 ` <FFFA58AC-4040-4E6D-A28F-BBBDD78F8722-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-11 20:21                   ` Dor Laor
     [not found]                     ` <64F9B87B6B770947A9F8391472E032160D95E340-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-11 22:57                       ` Cam Macdonell
     [not found]                         ` <46E71D72.7000901-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-15 22:47                           ` Dor Laor
     [not found]                             ` <46EC60FF.60209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 16:00                               ` Cameron Macdonell
     [not found]                                 ` <07D7C2A1-A29D-4CED-9B97-5C0071C75AF8-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-17 22:42                                   ` Dor Laor
     [not found]                                     ` <46EF02C7.1000904-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-18 22:27                                       ` Cam Macdonell
     [not found]                                         ` <46F050BB.9040801-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-19 10:31                                           ` Dor Laor

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=46E63F46.2040707@qumranet.com \
    --to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=cam-edFDblaTWIyXbbII50Afww@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox