Thank you, but I have to ask last question. My qemu is 2.6.0, and there is
no -qmp option :
[root@yf-mos-test-net09 ~]# ps aux | grep qemu
> root 5714 0.0 0.0 1669388 77736 ? Sl Sep01 0:09
> /usr/local/bin/qemu-system-x86_64_2.6.0 -enable-kvm -cpu
> qemu64,+vmx,+ssse3,+sse4.1,+sse4.2,+x2apic,+aes,+avx,+vme,+pat,+ss,+pclmulqdq,+xsave,level=13
> -machine pc,accel=kvm -chardev
> socket,id=hmqmondev,port=55919,host=127.0.0.1,nodelay,server,nowait -mon
> chardev=hmqmondev,id=hmqmon,mode=readline -rtc
> base=utc,clock=host,driftfix=none -usb -device usb-tablet -daemonize
> -nodefaults -nodefconfig -no-kvm-pit-reinjection -global
> kvm-pit.lost_tick_policy=discard -vga std -k en-us -smp 1 -name
> mvs5-huanghuai -m 1024 -boot order=cdn -vnc :19,password -drive
> file=/opt/cloud/workspace/disks/4a5148da-e34e-4c81-aada-12a247c0337e,if=none,id=drive_0,format=qcow2,cache=none,aio=native
> -device virtio-blk-pci,id=dev_drive_0,drive=drive_0,bus=pci.0,addr=0x5
> -drive
> file=/opt/cloud/workspace/disks/08eb3f72-07ba-44e9-8ee9-4ab662dbbd1f,if=none,id=drive_1,format=qcow2,cache=none,aio=native
> -device virtio-blk-pci,id=dev_drive_1,drive=drive_1,bus=pci.0,addr=0x6
> -device ide-cd,drive=ide0-cd0,bus=ide.1,unit=1 -drive
> id=ide0-cd0,media=cdrom,if=none -chardev
> socket,id=char-n-f879ac2f,path=/usr/local/var/run/openvswitch/n-f879ac2f,server
> -netdev type=vhost-user,id=n-f879ac2f,chardev=char-n-f879ac2f,vhostforce=on
> -device
> virtio-net-pci,netdev=n-f879ac2f,mac=00:22:f8:79:ac:2f,id=netdev-n-f879ac2f,addr=0xf
> -object
> memory-backend-file,id=mem,size=1024M,mem-path=/dev/hugepages,share=on
> -numa node,memdev=mem -mem-prealloc -pidfile
> /opt/cloud/workspace/servers/63ef2ec4-556f-47ea-93e0-23089bb59be5/pid
> -chardev
> socket,path=/opt/cloud/workspace/servers/63ef2ec4-556f-47ea-93e0-23089bb59be5/qga.sock,server,nowait,id=qga0
> -device virtio-serial -device
> virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -incoming tcp:0:8081
After I use telnet like this `telnet localhost 55919`, then enter this cmd
line:
[root@yf-mos-test-net09 ~]# telnet localhost 55919
> Trying ::1...
> telnet: connect to address ::1: Connection refused
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> QEMU 2.6.0 monitor - type 'help' for more information
> (qemu) help
> help
> acl_add aclname match allow|deny [index] -- add a match rule to the access
> control list
> ...
> xp /fmt addr -- physical memory dump starting at 'addr'
> (qemu)
> (qemu)
(qemu) {"execute":"query-status"}
> {"execute":"query-status"}
> unknown command: '{"execute":"query-status"}'
And I send QMP json format command, it report error as above. So where is
the monitor socket? Why I got error while using QMP command?
2017-09-04 18:16 GMT+08:00 Daniel P. Berrange <berra...@redhat.com>:
> On Mon, Sep 04, 2017 at 06:11:44PM +0800, Sam wrote:
> > Actually I use qga socket first(send json format command like {'execute':
> > 'chardev-add', 'arguments': {'id': id, 'type': type}, 'params': params}
> by
> > qga socket, which is
> > /opt/cloud/workspace/servers/1925a92d-f003-4d77-871c-
> bce8f85229aa/qga.sock,
> > using the same script as first mail), but it response me "netdev_add is
> not
> > valid command"(it's reasonable, as guest OS could not operate
> 'netdev_add'
> > command), so I thought qga could not do this work, then I change to
> monitor.
>
> You're mixing up two different things. 'QGA' is the QEMU guest agent
> which is a service than runs in the guest OS. 'QMP' is the QEMU monitor
> socket which runs in the host OS. Both of these use the same JSON based
> protocol, but take completely different commands.
>
> You need to use 'QMP' for 'netdev_add', not 'QGA'.
>
> Regards,
> Daniel
> --
> |: https://berrange.com -o- https://www.flickr.com/photos/
> dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o- https://www.instagram.com/
> dberrange :|
>
