after test the qemu gluster V5 patch:http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg01023.html
I had write a patch in libvirt to support gluster protocol, but has qemuMonitorIO error:
2012-08-22 17:17:47.600+0000: 29121: error : qemuMonitorIORead:490 : Unable to read from monitor: Connection reset by peer
2012-08-22 17:17:47.600+0000: 29121: error : qemuMonitorIO:546 : 内部错误 event from unexpected fd -1!=27 / watch 15!=15
the vm libvirt config file like this:
<domain type='kvm'>
<name>gluster-vm</name>
<vcpu>1</vcpu>
<cpu>
<topology sockets='1' cores='1' threads='1'/>
</cpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<memory>524288</memory>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='network' device='disk'>
<source protocol='gluster' name='volname/windowsxp.img'>
<host name='10.1.0.1' port='24007'/>
</source>
<target dev='vda' bus='virtio'/>
<driver name='qemu' type='qcow2' io='native' cache='none'/>
</disk>
<controller type='virtio-serial' index='0'/>
</devices>
<features>
<pae/>
<acpi/>
<apic/>
</features>
</domain>
my questions:
1. what's the function of qemuMonitorIO?
2. why the qemu-gluster patch caused qemuMonitorIO error?
I could boot vm in qemu command without monitor, like this:
/usr/libexec/qemu-kvm -drive file=gluster://10.1.0.1/volname/windowsxp.img,format=qcow2
Best Regards,
Yin Yin
