On Tue, Jul 17, 2012 at 05:02:49PM -0500, Michael Roth wrote:
> On Tue, Jul 17, 2012 at 02:34:53PM -0700, desi babu wrote:
> > On Mon, Jul 16, 2012 at 01:49:19PM -0700, desi babu wrote:
> > > Any pointers for debugging ?.
> >
> > >> What version of the virtio-win drivers are you using? More specifically,
> > >> what's the name of the ISO/package you used? I'm not sure how
> > >> "Driver Date" maps to actual virto-win releases.
> >
> > I tested with both virtio-win-0.1-22.iso and virtio-win-0.1-30.iso.
> >
> > >>There is a test utility on the virtio-win ISO called "vioser-test.exe".
> > >>I'd recommend running that to confirm whether or not it's a qemu-ga
> > >>issue.
> >
> > Running vioser-test.exe reports error 5.
> > "Running in non-blocking mode.
> > Cannot find vioserial device
> > \\?\{6FDE7547-1B65-48AE-B628-80BE62016026}#VIOSERIALPORT#4&263E99FC&0&01#{6FDE7547-1B65-48AE-B628-80BE62016026},
> > error = 5
> >
>
> This implies the driver isn't installed/working properly and the virtio-serial
> device isn't present.
>
> Vadim: any suggestions for debugging?
>
> > Before you run it, attach something to the host-side socket to
> >
> > >>confirm you get the expected output from the test utility, such as
> > >>`nc -U /tmp/qemu-ga.w2008.0.sock`
> >
> > echo "{'execute':'guest-ping'}" | socat stdio
> > unix-connect:/tmp/qemu-ga.w2008.0
> > -- no response.. I tried this with another linux server which has guest
> > agent loaded and get the same no response.
>
> A linux guest with qemu-ga installed? If that scenario isn't working for you
> it's a different issue, but I'd be interested in the output you see when
> running qemu-ga in the linux guest as `./qemu-ga -v` (as root) and then
> sending
> the guest-ping command.
>
Actually I think what's happening here is socat is getting an EOF from
your echo process and closing the stream before qemu-ga has a chance to
respond. Retry with:
echo "{'execute':'guest-ping'}" | socat stdio,ignoreeof
unix-connect:/tmp/qemu-ga.w2008.0
> >
> > >> Also, any logs/output from the QEMU process may provide some clues as
> > >> well.
> >
> > Checked the logs and found nothing abnormal which is reported, following is
> > the process list.
> >
> > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> > QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
> > 2,sockets=2,cores=1,threads=1 -name w2008 -uuid
> > ef25aa07-8ff6-10c1-ad3d-d8b0c7455ee0 -nodefconfig -nodefaults -chardev
> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/w2008.monitor,server,nowait
> > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot
> > -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
> > file=/opt/nfs2/windows2008r2.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw
> > -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> > file=/opt/nfs2/virtio-win-0.1-30.iso,if=none,id=drive-ide0-1-1,readonly=on,format=raw
> > -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -drive
> > file=/opt/nfs2/vm/w2008.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native
> > -device
> >
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> > -netdev tap,fd=18,id=hostnet0 -device
> > virtio-net-pci,netdev=hostnet0,id=net0,mac=42:52:01:52:fa:3f,bus=pci.0,addr=0x3
> > -chardev pty,id=charserial0 -device
> > isa-serial,chardev=charserial0,id=serial0 -chardev
> > socket,id=charchannel0,path=/tmp/qemu-ga.w2008.0.sock,server,nowait -device
> > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
> > -vnc 0.0.0.0:0 -vga cirrus -device
> > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
> >
> >
> > Version info :
> > libvirt : 0.9.12-0ubuntu3
> > qemu-kvm : 1.0+noroms-0ubuntu1
> > linux kernel : 3.2.0-26-generic
> >
> > Thanks, appreciate your help.
> > >
> > > Thanks..
> > >
> > > ----- Forwarded Message -----
> > > From: desi babu <vdesib...@yahoo.com>
> > > To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
> > > Sent: Monday, July 16, 2012 3:24 PM
> > > Subject: Qemu-ga : Guest Agent : Win 2008-64bit not working
> > >
> > >
> > >
> > > ________________________________
> > >
> > > Qemu Guest Agent on Windows 2008 is not able to connect to virtio-serial
> > > socket.
> > >
> > > Windows Version : 2008 64 Bit
> > >
> > > VIRT-IO Serial Driver installed in windows.
> > > Driver Provider : Redhat Inc.
> > > Driver Date : 61.63.103.2200
> > >
> > > Libvirt Settings.
> > >
> > >
> > > <channel type='unix'>
> > > <source mode='bind' path='/tmp/qemu-ga.w2008.0.sock'/>
> > > <target type='virtio' name='org.qemu.guest_agent.0'/>
> > > <address type='virtio-serial' controller='0' bus='0' port='1'/>
> > > </channel>
> > >
> > >
> > > Version : qemu-ga -V
> > > QEMU Guest Agent 1.1.0
> > >
> > > qemu-ga.exe
> > > critical : error opening path
> > > critical : error opening channel
> > > critical : failed to create guest agent channel
> > > critical : failed to initialize guest agent channel.
> > >
> > > Any recommendations or debugging methods to verify vertio-serial ?
> > >
> > > Thanks in advance.
