Cam Macdonell wrote:

Dor Laor wrote:
>>> 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
>> I tried having a program listening on the unix domain socket.
>> Actually, the VM won't even start until a program connects to the
>> socket.  I didn't get the message with my listening program, but I'll
>> try the telnet method as I haven't programmed a socket in a while so
>> I may have missed a step.
>
> Go for it, its 1 minute effort.

Hi Dor,

It didn't work.  I used the following option: -vmchannel
di:2258,tcp:0:4444,server (the // confused kvm) and when the VM booted,
I connected with "telnet localhost 4444" which allowed the boot to
proceed.  But, I didn't get the hello host message when I loaded the
hypercall module.  dmesg did show that the module loaded successfully.
I'll dig around with it and see what else I can figure ou

I just tried it and it worked. I used fc7 2.6.21 kernel, 64 bits for the guest.
Can you send the relevant dmesg?
-------------------------------------------------------------------------
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/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to