Add following routines to esx_interface_driver:
esxNumOfInterfaces,
esxNumOfDefinedInterfaces,
esxListInterfaces,
esxListDefinedInterfaces,
esxInterfaceLookupByMACString,
esxInterfaceGetXMLDesc,
esxInterfaceUndefine,
esxInterfaceCreate,
esxInterfaceDestroy
Signe
Use ATTRIBUTE_UNUSED for unused variable.
Signed-off-by: Ata E Husain Bohra
---
src/esx/esx_interface_driver.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/src/esx/esx_interface_driver.c b/src/esx/esx_interface_driver.c
index 1c1aaf2..0b07259 100644
--- a
Updated the variable names to match vSphere terminology.
Signed-off-by: Ata E Husain Bohra
---
src/esx/esx_interface_driver.c | 179
src/esx/esx_vi.c | 30 +++
src/esx/esx_vi.h |6 +-
3 files changed, 107 insertions(
Updated the patch against review comments from Laine and Matthias.
Ata E Husain Bohra (3):
ESX: Add routines to interface driver
ESX: Add routines to interface driver
ESX: Add routines to interface driver
src/esx/esx_interface_driver.c | 499 +++-
src/e
---
libvirt-gobject/libvirt-gobject-connection.c | 160 ++
libvirt-gobject/libvirt-gobject-connection.h | 20
libvirt-gobject/libvirt-gobject.sym |3 +
3 files changed, 183 insertions(+)
diff --git a/libvirt-gobject/libvirt-gobject-connection.c
b/libv
Hi everyone!
I ran into a rather annoying bug this evening. It appears that having
a special function to connect to libvirt (in a class), like:
hostname.':16514/system',
false);
}
?>
..causes any calls to get a domain resource to be corrupted somehow, like:
libvirtConnect();
return libvirt_
On Sat, Jul 28, 2012 at 6:50 AM, Peter Maydell wrote:
> On 27 July 2012 16:31, Anthony Liguori wrote:
>> Peter Maydell writes:
>>> My approach to this is to avoid non-standard things
>>
>> http://en.wikipedia.org/wiki/C99#Implementations
>>
>> So unless you plan on compiling QEMU with xlc, pgi,
On 27 July 2012 16:31, Anthony Liguori wrote:
> Peter Maydell writes:
>> My approach to this is to avoid non-standard things
>
> http://en.wikipedia.org/wiki/C99#Implementations
>
> So unless you plan on compiling QEMU with xlc, pgi, or icc, I don't
> think relying on "standard things" really hel
