On Sat, Aug 08, 2009 at 11:57:25PM +0200, Matthias Bolte wrote:
> esxUtil_ParseQuery() warns if a known query parameter should be
> ignored due to the corresponding char/int pointer being NULL, instead
> of silently ignoring it.
>
> The attached patch changes the if/else structure to fix this.
On Sat, Aug 08, 2009 at 11:56:10PM +0200, Matthias Bolte wrote:
> The VMX entry ethernet0.addressType may be set to 'vpx' beside
> 'static' and 'generated'. 'vpx' indicates that the MAC address was
> generated by a vCenter.
>
> The attached patch adds 'vpx' to the valid values for ethernet0.addres
On Sat, Aug 08, 2009 at 11:57:25PM +0200, Matthias Bolte wrote:
> esxUtil_ParseQuery() warns if a known query parameter should be
> ignored due to the corresponding char/int pointer being NULL, instead
> of silently ignoring it.
>
> The attached patch changes the if/else structure to fix this.
>
On Sat, Aug 08, 2009 at 11:56:10PM +0200, Matthias Bolte wrote:
> The VMX entry ethernet0.addressType may be set to 'vpx' beside
> 'static' and 'generated'. 'vpx' indicates that the MAC address was
> generated by a vCenter.
>
> The attached patch adds 'vpx' to the valid values for ethernet0.addres
2009/8/10 Itamar Heim :
>> From: Matthias Bolte [mailto:matthias.bo...@googlemail.com]
> ...
>>
>> The ESX driver parses the VMX file of a virtual machine to gather the
>> information needed for the dump XML function. The VMX entry
>> ethernet0.addressType maybe set to vpx if the generated MAC addr
> From: Matthias Bolte [mailto:matthias.bo...@googlemail.com]
...
>
> The ESX driver parses the VMX file of a virtual machine to gather the
> information needed for the dump XML function. The VMX entry
> ethernet0.addressType maybe set to vpx if the generated MAC address
> was generated by a vCent
2009/8/10 Itamar Heim :
>> From: libvir-list-boun...@redhat.com [mailto:libvir-list-
>> boun...@redhat.com] On Behalf Of Matthias Bolte
>
>>
>> The VMX entry ethernet0.addressType may be set to 'vpx' beside
>> 'static' and 'generated'. 'vpx' indicates that the MAC address was
>> generated by a vCen
> From: libvir-list-boun...@redhat.com [mailto:libvir-list-
> boun...@redhat.com] On Behalf Of Matthias Bolte
>
> The VMX entry ethernet0.addressType may be set to 'vpx' beside
> 'static' and 'generated'. 'vpx' indicates that the MAC address was
> generated by a vCenter.
>
> The attached patch ad
esxUtil_ParseQuery() warns if a known query parameter should be
ignored due to the corresponding char/int pointer being NULL, instead
of silently ignoring it.
The attached patch changes the if/else structure to fix this.
Matthias
diff --git a/src/esx/esx_util.c b/src/esx/esx_util.c
index 5e7c62a.
The VMX entry ethernet0.addressType may be set to 'vpx' beside
'static' and 'generated'. 'vpx' indicates that the MAC address was
generated by a vCenter.
The attached patch adds 'vpx' to the valid values for ethernet0.addressType.
Matthias
diff --git a/src/esx/esx_vmx.c b/src/esx/esx_vmx.c
index
On Wed, Aug 05, 2009 at 03:23:28PM +0200, Matthias Bolte wrote:
> Subject says it all. No functional change included.
>
Okay, applied along with the 2 previous fixes,
thanks !
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
dan...@veillard.com | Rpmfi
On Wed, Aug 05, 2009 at 03:23:28PM +0200, Matthias Bolte wrote:
> Subject says it all. No functional change included.
> diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
> index 49fdf00..0225e9a 100644
> --- a/src/esx/esx_driver.c
> +++ b/src/esx/esx_driver.c
> @@ -56,11 +56,11 @@ static in
On Wed, Aug 05, 2009 at 03:23:14PM +0200, Matthias Bolte wrote:
> Subject says it all.
>
> Matthias
> diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
> index 8b8575c..49fdf00 100644
> --- a/src/esx/esx_driver.c
> +++ b/src/esx/esx_driver.c
> @@ -298,6 +298,7 @@ esxOpen(virConnectPtr conn
On Wed, Aug 05, 2009 at 03:22:51PM +0200, Matthias Bolte wrote:
> Subject says it all.
>
> Matthias
5B> diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
> index dba6305..8b8575c 100644
> --- a/src/esx/esx_driver.c
> +++ b/src/esx/esx_driver.c
> @@ -1395,9 +1395,16 @@ esxDomainDestroy(virD
Subject says it all. No functional change included.
Matthias
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 49fdf00..0225e9a 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -56,11 +56,11 @@ static int esxDomainGetMaxVcpus(virDomainPtr domain);
typedef struct _esx
Subject says it all.
Matthias
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 8b8575c..49fdf00 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -298,6 +298,7 @@ esxOpen(virConnectPtr conn, virConnectAuthPtr auth, int flags ATTRIBUTE_UNUSED)
esxVI_Context_Free
Subject says it all.
Matthias
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index dba6305..8b8575c 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -1395,9 +1395,16 @@ esxDomainDestroy(virDomainPtr domain)
static char *
-esxDomainGetOSType(virDomainPtr dom ATTRIBUTE_
On Thu, Jul 30, 2009 at 01:28:47PM +0200, Matthias Bolte wrote:
> Add some documentation about the CPU scheduler parameters and remove
> some old, unnecessary compensation code, since virsh uses the proposed
> parameter types now.
Okay, looks logical, more comment and less code is good too :-)
Add some documentation about the CPU scheduler parameters and remove
some old, unnecessary compensation code, since virsh uses the proposed
parameter types now.
Documentation in HTML form will be added soon.
Matthias
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 1aa6c4b..eb3e09e
On Mon, Jul 27, 2009 at 01:15:16PM +0200, Matthias Bolte wrote:
> Adds a no_verify query parameter to stop libcurl from verifying the
> server certificate for the https transport.
>
> Idea from Tom Hughes.
ACK, this matches the same no_verify parameter supported for the generic
'remote' driver, w
On Mon, Jul 27, 2009 at 01:44:44PM +0100, Tom Hughes wrote:
> On 27/07/09 13:28, Matthias Bolte wrote:
>
>> It seems that I should setup an ESXi 4 just in case there are more
>> differences between version 3.5 and 4.0.
>>
>> See the other patch regarding VI API 4.0, that one should fix the
>> virtu
On 27/07/09 13:28, Matthias Bolte wrote:
It seems that I should setup an ESXi 4 just in case there are more
differences between version 3.5 and 4.0.
See the other patch regarding VI API 4.0, that one should fix the
virtualHW.version problem and make the version checking more robust.
Latest gi
2009/7/27 Tom Hughes :
> On 27/07/09 12:25, Matthias Bolte wrote:
>
>> '.encoding = "UTF-8"' is a valid VMX config entry, so the
>> virConfParser must accept it in VMX mode. This patch lets the parser
>> accept those names with leading dots.
>
> With that patch ESX4i gets a bit further but barfs on
On Mon, Jul 27, 2009 at 01:25:01PM +0200, Matthias Bolte wrote:
> Hi,
>
> '.encoding = "UTF-8"' is a valid VMX config entry, so the
> virConfParser must accept it in VMX mode. This patch lets the parser
> accept those names with leading dots.
Okay, simple, applied !
thanks,
Daniel
--
Dan
On Mon, Jul 27, 2009 at 01:15:16PM +0200, Matthias Bolte wrote:
> Adds a no_verify query parameter to stop libcurl from verifying the
> server certificate for the https transport.
>
> Idea from Tom Hughes.
Good idea to keep it as secure as prossible by default
Daniel
--
Daniel Veillard
On Mon, Jul 27, 2009 at 01:08:51PM +0200, Matthias Bolte wrote:
> Subject says it all.
Okay. applied though esxDomainXMLFromNative() change are more a
simplified exit it could not leak or break
thanks !
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
da
On 27/07/09 12:25, Matthias Bolte wrote:
'.encoding = "UTF-8"' is a valid VMX config entry, so the
virConfParser must accept it in VMX mode. This patch lets the parser
accept those names with leading dots.
With that patch ESX4i gets a bit further but barfs on a version check:
error: internal
Hi,
This patch extends the VI API version checks to accept version 4.0 too.
Regards,
Matthias
diff --git a/src/esx/esx_vi.c b/src/esx/esx_vi.c
index 18e11e7..aa4f840 100644
--- a/src/esx/esx_vi.c
+++ b/src/esx/esx_vi.c
@@ -268,17 +268,20 @@ esxVI_Context_Connect(virConnectPtr conn, esxVI_Contex
Hi,
'.encoding = "UTF-8"' is a valid VMX config entry, so the
virConfParser must accept it in VMX mode. This patch lets the parser
accept those names with leading dots.
Regards,
Matthias
diff --git a/src/conf.c b/src/conf.c
index c51531e..2aa4a55 100644
--- a/src/conf.c
+++ b/src/conf.c
@@ -534
Adds a no_verify query parameter to stop libcurl from verifying the
server certificate for the https transport.
Idea from Tom Hughes.
Regards,
Matthias
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index aa73e46..8f1ebfb 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@
Subject says it all.
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 11b727b..d460f76 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -2023,10 +2023,13 @@ esxDomainDumpXML(virDomainPtr domain, int flags)
}
cleanup:
+esxVI_String_Free(&propertyNameList);
2009/7/23 Daniel Veillard :
> On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
>> Hi,
>>
>> the development was hindered by our testing cluster being offline
>> since 2 weeks due to server room cooling system maintenance. But I
>> finally got a basic version of dump-XML done, that fi
2009/7/23 Daniel Veillard :
> On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
>>
>
> Now reviewing the main code,
>
> [...]
>> +typedef struct _esxPrivate {
>> + esxVI_Context *host;
>> + esxVI_Context *vcenter;
>> + int phantom; // boolean
>
> Do we really need phantom ?
On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
> Hi,
>
> the development was hindered by our testing cluster being offline
> since 2 weeks due to server room cooling system maintenance. But I
> finally got a basic version of dump-XML done, that fills all fields of
> the virDomainD
On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
>
Now reviewing the main code,
[...]
> +typedef struct _esxPrivate {
> +esxVI_Context *host;
> +esxVI_Context *vcenter;
> +int phantom; // boolean
Do we really need phantom ? this is basically a debug mode with no rea
2009/7/22 Daniel Veillard :
> On Wed, Jul 22, 2009 at 05:24:09PM +0100, Daniel P. Berrange wrote:
>> On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
>> > Hi,
>> >
>> > the development was hindered by our testing cluster being offline
>> > since 2 weeks due to server room cooling sys
On Wed, Jul 22, 2009 at 05:24:09PM +0100, Daniel P. Berrange wrote:
> On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
> > Hi,
> >
> > the development was hindered by our testing cluster being offline
> > since 2 weeks due to server room cooling system maintenance. But I
> > finally
On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
> Hi,
>
> the development was hindered by our testing cluster being offline
> since 2 weeks due to server room cooling system maintenance. But I
> finally got a basic version of dump-XML done, that fills all fields of
> the virDomainD
On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
> Hi,
I checked the diff patch, i.e. change to the current infrastructure,
it all look clean and uncontroversial. I think it just misses adequate
changes to the spec file including libcurl BuidDeps but I will handle
this one :-)
Sti
On Tue, Jul 21, 2009 at 04:58:50PM +0200, Matthias Bolte wrote:
> Hi,
>
> the development was hindered by our testing cluster being offline
> since 2 weeks due to server room cooling system maintenance. But I
> finally got a basic version of dump-XML done, that fills all fields of
> the virDomainD
On Thu, Jun 25, 2009 at 05:26:45PM +0200, Daniel Veillard wrote:
> > One problem here is the essential guestOS field of the VMX config, see
> > http://sanbarrow.com/vmx/vmx-guestos.html . For a first try I would
> > set it to 'other' by default, because there is currently no field
> > available in
On Thu, Jun 25, 2009 at 12:11:26PM +0200, Matthias Bolte wrote:
> I claimed before that I would need to read most information needed for
> dump XML from the VMX config file. That's not true. Possibly all
> information can be retrieved via VI API, but the information is
> scattered in various places
2009/6/25 Daniel Veillard :
>> So I won't be able to complete the dump/create XML implementation
>> until tomorrow (freeze for the 0.6.5 release) that was requested in
>> order to get the driver merged into the official repository. But well,
>> with the short release cycle of libvirt not much is lo
On Thu, Jun 25, 2009 at 05:26:45PM +0200, Daniel Veillard wrote:
> On Thu, Jun 25, 2009 at 12:11:26PM +0200, Matthias Bolte wrote:
>
> > One problem here is the essential guestOS field of the VMX config, see
> > http://sanbarrow.com/vmx/vmx-guestos.html . For a first try I would
> > set it to 'oth
On Thu, Jun 25, 2009 at 12:11:26PM +0200, Matthias Bolte wrote:
> Hi,
>
> I'm still working on the VMX config to domain XML mapping for
> dump/create XML, but it's not complete yet. I got distracted by other
> urgent, Uni related work that had to be done first.
Okay :-)
> So I won't be able to
Hi,
I'm still working on the VMX config to domain XML mapping for
dump/create XML, but it's not complete yet. I got distracted by other
urgent, Uni related work that had to be done first.
So I won't be able to complete the dump/create XML implementation
until tomorrow (freeze for the 0.6.5 releas
On Mon, May 25, 2009 at 07:39:21PM +0200, Stefan de Konink wrote:
> Daniel Veillard wrote:
> >>> The other possibility was to use the libraries they provide to
> >>>interconnect, but there was a licencing problem, plus you can't expect
> >>>to have thing installed on the server, so this was a dead
Daniel Veillard wrote:
The other possibility was to use the libraries they provide to
interconnect, but there was a licencing problem, plus you can't expect
to have thing installed on the server, so this was a dead end too.
We looked at this closed source communication library provided by
VMwar
On Thu, May 21, 2009 at 02:54:46AM +0200, Matthias Bolte wrote:
> 2009/5/19 Daniel Veillard :
> >> The driver uses the SOAP based VMware VI API. We've tried to generate
> >> SOAP client code with gSOAP and looked at other SOAP libraries, but
> >> the VI API uses inheritance in a way that gSOAP fail
On Thu, May 21, 2009 at 02:54:46AM +0200, Matthias Bolte wrote:
> 2009/5/19 Daniel Veillard :
> >> diff --git a/src/esx_driver.c b/src/esx_driver.c
> >> new file mode 100644
> >> index 000..28500b8
> >> --- /dev/null
> >> +++ b/src/esx_driver.c
> >> @@ -0,0 +1,1385 @@
> > [...]
> >> +#define ES
2009/5/19 Daniel Veillard :
>> The driver uses the SOAP based VMware VI API. We've tried to generate
>> SOAP client code with gSOAP and looked at other SOAP libraries, but
>> the VI API uses inheritance in a way that gSOAP fails to generate C
>
> Yes, I have tried that before, and it looked nasty,
On Tue, May 19, 2009 at 04:52:04PM +0200, Matthias Bolte wrote:
> Hello,
>
> I'm participate in a project of the Paderborn Center for Parallel
> Computing, an institute of the University of Paderborn:
> http://pc2.uni-paderborn.de
>
> The project's goal is to use virtualization in a supercomputer
On Tue, May 19, 2009 at 04:52:04PM +0200, Matthias Bolte wrote:
> Hello,
Hello Matthias,
> I'm participate in a project of the Paderborn Center for Parallel
> Computing, an institute of the University of Paderborn:
> http://pc2.uni-paderborn.de
>
> The project's goal is to use virtualization i
On Tue, 20 May 2008, Pau Garcia i Quiles wrote:
> > I read about VIX again, but is this already working for ESX? On their site
> > and fora they mention Workstatation/Server only.
>
> According to http://communities.vmware.com/thread/115071 the VIX API
> will be supported in ESX in the future.
Th
Quoting Stefan de Konink <[EMAIL PROTECTED]>:
On Tue, 20 May 2008, Daniel Veillard wrote:
On Mon, May 19, 2008 at 02:28:10PM -0600, drew einhorn wrote:
> Hi,
Hi,
> I have some code that can probably be hacked into a libvirt driver for
> VMware ESX.
interesting, how did you go? I did som
On Tue, 20 May 2008, Daniel Veillard wrote:
> On Mon, May 19, 2008 at 02:28:10PM -0600, drew einhorn wrote:
> > Hi,
>
> Hi,
>
> > I have some code that can probably be hacked into a libvirt driver for
> > VMware ESX.
>
> interesting, how did you go? I did some experimentation using SOAP and
>
On Mon, May 19, 2008 at 02:28:10PM -0600, drew einhorn wrote:
> Hi,
Hi,
> I have some code that can probably be hacked into a libvirt driver for
> VMware ESX.
interesting, how did you go? I did some experimentation using SOAP and
gsoap2 a few weeks ago that i need to restart. Did you use VIX
drew einhorn schreef:
I have some code that can probably be hacked into a libvirt driver for
VMware ESX.
This shoulds cool :) I'm happy you will start this before I have to do
it :) What approach will you take? Soap?
Is there a template with stubs for all the necessary routines for the
API
Hi,
I have some code that can probably be hacked into a libvirt driver for
VMware ESX.
Is there a template with stubs for all the necessary routines for the API
that I can use
as a starting point?
--
Drew Einhorn
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/
59 matches
Mail list logo
