Re: [libvirt] Using ESX domain XML for V2V
2010/1/15 Matthias Bolte matthias.bo...@googlemail.com: 2010/1/14 Matthew Booth mbo...@redhat.com: I'm trying to use the ESX driver to extract metadata from ESX in an easily digestible form for driving V2V. I've noticed the domain XML seems to be missing a few bits: features/ This is currently not implemented, but could be by parsing the CPUIDs. This is on my todo list. graphics/ VMware seems to use a certain type of VNC for this, but they use a custom authentication mechanism. There is a Firefox plugin for that (vmware-mks.xpi), but IIRC its Windows only. I think this could be implemented but there is more research necessary what to expose as graphics element. Okay, I should have looked at this in more detail before answering... ESX (at least 4.0) supports normal VNC as well. It can be enabled by adding RemoteDisplay.vnc.enabled = true RemoteDisplay.vnc.port = port RemoteDisplay.vnc.password = password to the VMX config. I tested it and it works, but I had to manually open the VNC port range in the ESX firewall using the VI client GUI. I think this can be done using the VI API, but I'm not sure whether the ESX driver should do this automatically or if proper firewall configuration should stay a responsibility of the user. Matthias -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Using ESX domain XML for V2V
On Fri, Jan 15, 2010 at 12:04:50PM +0100, Matthias Bolte wrote: 2010/1/15 Matthias Bolte matthias.bo...@googlemail.com: 2010/1/14 Matthew Booth mbo...@redhat.com: I'm trying to use the ESX driver to extract metadata from ESX in an easily digestible form for driving V2V. I've noticed the domain XML seems to be missing a few bits: features/ This is currently not implemented, but could be by parsing the CPUIDs. This is on my todo list. graphics/ VMware seems to use a certain type of VNC for this, but they use a custom authentication mechanism. There is a Firefox plugin for that (vmware-mks.xpi), but IIRC its Windows only. I think this could be implemented but there is more research necessary what to expose as graphics element. Interesting - if there is any docs or source code illustrating this auth mechanism we could try and hook it into GTK-VNC and see if it really does have normalish VNC Okay, I should have looked at this in more detail before answering... ESX (at least 4.0) supports normal VNC as well. It can be enabled by adding RemoteDisplay.vnc.enabled = true RemoteDisplay.vnc.port = port RemoteDisplay.vnc.password = password to the VMX config. I tested it and it works, but I had to manually open the VNC port range in the ESX firewall using the VI client GUI. I think this can be done using the VI API, but I'm not sure whether the ESX driver should do this automatically or if proper firewall configuration should stay a responsibility of the user. That's the responsibility of hte ESX admin, in same way the Linux host admin has to open the firewall for VNC when using KVM/Xen Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Using ESX domain XML for V2V
2010/1/15 Daniel P. Berrange berra...@redhat.com: On Fri, Jan 15, 2010 at 12:04:50PM +0100, Matthias Bolte wrote: 2010/1/15 Matthias Bolte matthias.bo...@googlemail.com: 2010/1/14 Matthew Booth mbo...@redhat.com: I'm trying to use the ESX driver to extract metadata from ESX in an easily digestible form for driving V2V. I've noticed the domain XML seems to be missing a few bits: features/ This is currently not implemented, but could be by parsing the CPUIDs. This is on my todo list. graphics/ VMware seems to use a certain type of VNC for this, but they use a custom authentication mechanism. There is a Firefox plugin for that (vmware-mks.xpi), but IIRC its Windows only. I think this could be implemented but there is more research necessary what to expose as graphics element. Interesting - if there is any docs or source code illustrating this auth mechanism we could try and hook it into GTK-VNC and see if it really does have normalish VNC Well that's the VMware MKS stuff. The VI API contains a AcquireMksTicket method [1] that returns a VirtualMachineMksTicket [2] containing some information to establish a connection. But IIRC the port return is 902 and thats the port of the vmware-authd-mks service. I'm not sure if there is any public documentation available about the auth mechanism for this service. But there is no need for the VMware MKS stuff as I just discovered. The VMX RemoteDisplay.vnc.* config options allow to enable normal VNC. I edited the config of a virtual machine by hand and used the default vncviewer of my Ubuntu box here to connect. On connect it asks for the password and then it works as expected. I'll have a patch for that shortly. Okay, I should have looked at this in more detail before answering... ESX (at least 4.0) supports normal VNC as well. It can be enabled by adding RemoteDisplay.vnc.enabled = true RemoteDisplay.vnc.port = port RemoteDisplay.vnc.password = password to the VMX config. I tested it and it works, but I had to manually open the VNC port range in the ESX firewall using the VI client GUI. I think this can be done using the VI API, but I'm not sure whether the ESX driver should do this automatically or if proper firewall configuration should stay a responsibility of the user. That's the responsibility of hte ESX admin, in same way the Linux host admin has to open the firewall for VNC when using KVM/Xen Daniel Okay. [1] http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.VirtualMachine.html#acquireMksTicket [2] http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.VirtualMachine.MksTicket.html Matthias -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Using ESX domain XML for V2V
2010/1/15 Matthew Booth mbo...@redhat.com: On 15/01/10 10:37, Matthias Bolte wrote: 2010/1/14 Matthew Booth mbo...@redhat.com: I'm trying to use the ESX driver to extract metadata from ESX in an easily digestible form for driving V2V. I've noticed the domain XML seems to be missing a few bits: features/ This is currently not implemented, but could be by parsing the CPUIDs. This is on my todo list. This would be extremely useful. graphics/ VMware seems to use a certain type of VNC for this, but they use a custom authentication mechanism. There is a Firefox plugin for that (vmware-mks.xpi), but IIRC its Windows only. I think this could be implemented but there is more research necessary what to expose as graphics element. input/ A ESX virtual machine has a PS2 mouse and keyboard by default and AFAIK that's not changeable. So the ESX driver could output input elements for them, but the user won't be able to change it when defining a new virtual machine. Currently input elements are ignored by the ESX driver. To explain my use case, I'm using the domain XML provided by the ESX driver to form the basis of domain XML for the QEMU driver. I don't need to be able to modify or even access the underlying guest, I just need to know that the devices exist and what drivers they are using. I believe there is more than 1 available graphics device in ESX, so that would be most important. I assume you mixed up video and graphics devices. The graphics device will be VNC. I just looked up If the video device type can be configured but I can't find anything about that, there is only a single type. But VRAM size can be configured and 3D acceleration support can be enabled with ESX 4.0. Matthias -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Using ESX domain XML for V2V
I'm trying to use the ESX driver to extract metadata from ESX in an easily digestible form for driving V2V. I've noticed the domain XML seems to be missing a few bits: features/ graphics/ input/ serial/ and console/ are also missing, but that could well be because they aren't present. Is this intentional? Should I be assuming some of the above because it's ESX, or is this an omission? Thanks, Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team M: +44 (0)7977 267231 GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
