<html><head><style type="text/css"></style></head><body><div style="font-family:'times new roman', 'new york', times, serif;font-size:12pt"><div>Let me rephrase my question : )</div><div><br></div><div>In the current libvirt infrastructure I can do a lot of things with libvirt and a remote <span class="Apple-style-span" style="text-decoration: underline;">ESX </span>node</div><div>I can list all the guests</div><div>I can suspend a guest</div><div>I can get a lot of node info</div><div>and much more....</div><div><br></div><div>can I (for example)</div><div>1. add NIC to a guest domain</div><div>2. list all the physical interfaces on a node</div><div><br></div><div>If not - what do I need to develop</div><div>should I expand the current driver</div><div>or</div><div>should I need to develop a new interface driver(like netcf) </div><div>or</div><div>maybe I can assign the current esx driver as the interface driver and expand it to handle the relvant requests</div><div><br></div><div>10x again</div><div><br></div><div>Shahar</div><div><br></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> Tuesday, September 8, 2009 5:55:42 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [libvirt] Interface driver and ESX support<br></font><br>Shahar Klein wrote:<br>> mmm<br>> <br>> I would like to get host(i.e. node) interface info<br>> as well as domain(guest) network/interface info<br>> <br>> I will probably would like to set/manipulate the node and domains as well<br>> but it is simpler to start with the get functions - isn't it?<br>> <br>> Did I totally misunderstood the architecture?<br><br>More or less, yes (at least for the ESX driver). The ESX driver is a bit<br>special, and different from some of the other drivers in that you don't run a<br>libvirtd on the target machine. It accesses the ESX API's via SOAP on the<br>remote machine. So what the libvirt driver can do is limited by what the ESX<br>API's can do. If the ESX API's can do the sort of enumeration you are talking<br>about, then I think it would be possible to implement it, although it would<br>require an entirely new interface driver.<br><br>-- <br>Chris Lalancette<br></div></div><div style="position:fixed"></div></div><br> </body></html>