On 05/17/2011 04:31 PM, Chip Vincent wrote:
The reason your not seeing a vnc instance is because libvirt-cim expects the 'listen' parameter. Please add 'listen=127.0.0.1' to the graphics element, update the VM, and re-run the wbemcli and you should see an instance for vnc.
You are right, thanks for the clarification. Results follow: [etrunko@eblima libcmpiutil.orig]$ wbemcli -nl ein http://root@localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingDa... localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f14-vmtest/serial:0" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f14-vmtest/serial:1" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f14-vmtest/console:0" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f14-vmtest/vnc" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f15-test/serial:0" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f15-test/console:0" localhost:5988/root/virt:KVM_GraphicsResourceAllocationSettingData.InstanceID="f15-test/vnc" So I think this patch has finally got the ACK. :D Cheers, -- Eduardo de Barros Lima Software Engineer, Open Virtualization Linux Technology Center - IBM/Brazil eblima@br.ibm.com