<html><head><style type="text/css"></style></head><body><div style="font-family:'times new roman', 'new york', times, serif;font-size:12pt"><div>thanks Chris</div><div><br></div><div>I'll try to write somthing</div><div>and see how it goes</div><div><br></div><div>shahar</div><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Chris Lalancette <clalance@redhat.com><br><b><span style="font-weight: bold;">To:</span></b> Shahar Klein <shaharklein@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> veillard@redhat.com; libvir-list@redhat.com<br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, September 9, 2009 10:18:39 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [libvirt] Interface driver and ESX support<br></font><br>Shahar Klein wrote:<br>> Let me rephrase my question : )<br>> <br>> In the current libvirt infrastructure I can do a lot of things with<br>> libvirt and a remote ESX node<br>> I can list all the guests<br>> I can suspend a guest<br>> I can get a lot of node info<br>> and much more....<br>> <br>> can I (for example)<br>> 1. add NIC to a guest domain<br><br>From looking at the current libvirt ESX driver (in src/esx/esx_driver.c), it<br>looks like no, this is not implemented yet.<br><br>> 2. list all the physical interfaces on a node<br><br>This is also not implemented yet.<br><br>> <br>> If not - what do I need to develop<br>> should I expand the current driver<br><br>For case 1) above, you should certainly expand the current driver (although<br>again, this all depends on whether the ESX SOAP API supports this operation,<br>which I can't answer).<br><br>For case 2) above, it's a lot more tricky. If you look at<br>src/interface_driver.c, that is one network interface driver that can enumerate<br>all of the physical devices on a host (using netcf as the backend). *If* the<br>ESX SOAP API's provide something similar, then you possibly could write a new<br>network interface driver for ESX that used the SOAP API's on the backend. This<br>would be a whole new interface driver, and may require new API's (although I'm<br>not sure about this, since I don't know the interface driver very well).<br><br>-- <br>Chris Lalancette<br></div></div><div style="position:fixed"></div></div><br> </body></html>