Re: [Qemu-discuss] [libvirt] Facing problems in running QEMU guest agents in Windows 2008 guest machine.

[Puneet Bakshi]

Can somebody in qemu user list let me know what is wrong I am doing and point me to the working way of installing qemu guest agents in Windows 8 guest machine.

Regards,

~Puneet

On Tue, Jul 1, 2014 at 6:21 PM, Claudio Bley <address@hidden> wrote:

At Tue, 1 Jul 2014 15:57:07 +0530,

Puneet Bakshi wrote:
>
> Hi,
>
> I have a CenOS host machine running KVM and a Windows 2008 guest machine. I
> am able to run "qemu-monitor-command" but not "qemu-agent-command".
>
>
> address@hidden Windows_ISO]# virsh qemu-monitor-command --hmp vm_win_05
> 'info network'
> Devices not on any VLAN:
>   hostnet0: fd=23 peer=net0
>   net0: model=virtio-net-pci,macaddr=52:54:00:7f:4a:5b peer=hostnet0
>
> address@hidden Windows_ISO]# virsh qemu-agent-command vm_win_05
> '{"execute":"guest-ping"}'
>
> address@hidden Windows_ISO]#
>
>
> [QEMU guest installation]
> To install QEMU guest agent, I followed steps mentioned at following URL
> http://wiki.qemu.org/Features/QAPI/GuestAgent#Example_usage
>
>
> [Problem-1]
> "qemu-ga.exe -s install" runs silently, "net start qemu-ga" gave error.
>
> Following is the snippet from Windows shell.
>
>     PS C:\puneet> .\qemu-ga.exe -s install
>
>     PS C:\puneet> net start qemu-ga
>     The service name is invalid.
>
>     More help is available by typing NET HELPMSG 2185.
>
>     PS C:\puneet>address@hidden Windows_ISO]#
>
>
> [Problem-2]
> When I double click the "qemu-ga.exe", it gives the following error.
>
> "The application was unable to start correctly (0xc000007b). Click Ok to
> close the application."

The libvirt list is not quite the right mailing list for your
question. This list is for discussion about libvirt
development. Better ask at the qemu *user* list when you have problems
with the qemu guest agent.

BTW, 0xc000007b means STATUS_INVALID_IMAGE_FORMAT, which indicates
that either your file is not a valid PE executable or that it's a 32
bit app and tried to load a 64 bit DLL, but that's just a wild guess.

You could use Dependency Walker to track this down.

Claudio