10:24 a.m.
2010/4/7 Aaron Lippold <lippold(a)gmail.com>:
Hi Matthias,
Sorry for the late reply. I was on travel with limited network access last week.
That sounds great, if you need any help or someone to test stuff,
please let me know since I am highly interested in helping in any way
I can.
More testing is always good to have.
First question, when I am testing can I use VMWare Workstation on my
laptop as a replacement for a full fledged for just testing API and
libVirt access? If so I can set that up on my F12 box and start
running some tests with libvirt and cobbler.
Sorry, but VMware Workstation will not work. The libvirt VMware
support is based on the VMware vSphere API. This API is supported by
VMware ESX/ESXi 3.5 and newer and VMware Server 2.0 and newer
(formally known as VMware GSX). So if you don't have ans ESX/ESXi
server at hand to test, you could use VMware Server 2.0, that can be
downloaded and used for free.
Any new updates on the storage and network efforts? What are the
basic
requirements that you are going to try to initially hit. I assume
there is alway more you could do but what's your 1.0 'good to go' set?
I think a 'good to go' set for the storage and network support should
allow to create a new virtual machine using virt-manager. Currently
this is hindered by missing storage support.
Matthias
Thanks,
Aaron
On Sun, Mar 21, 2010 at 1:26 PM, Matthias Bolte
<matthias.bolte(a)googlemail.com> wrote:
> You can manage the power state of a domain (start, stop, suspend, and
> resume), you can also define a new domain, undefine existing domains,
> migrate domains between hosts and configure CPU and RAM limits of a
> domain.
>
> Two major missing features are currently storage and network
> management. This means that you currently cannot use the libvirt
> storage and network API to manage the storage and network of an ESX
> server. I'm going to address this soon.
>
> A minor missing feature is editing the virtual hardware configuration
> of an existing domain. I'm currently working on this.
>
> The problem reported by Jonathan Kelley affects ESX 4.0 only. It's not
> fixed yet, but I think I can get it fixed for libvirt 0.7.8. I've
> withdrawn the first patch fix this issue. A better patch is more
> involved, because I need to rework the controller handling internally.
>
> Documentation about the ESX support can be found at:
> http://www.libvirt.org/drvesx.html
>
> If you have any questions about the ESX support feel free to ask.
>
> Matthias
>
> 2010/3/19 Aaron Lippold <lippold(a)gmail.com>:
>> Hi,
>>
>> So google and the mailing list didn't clearly state if we could or
>> couldn't create a new vm in a domain on ESX or just turn it on, off,
>> restart etc.
>>
>> Has the XML generation issue been addressed in 0.7.6+? If the docs
>> exist, please point me to them and I will be glad to RT*M :).
>>
>> Thanks,
>>
>> A
>>
>> On Fri, Mar 12, 2010 at 4:21 PM, Matthias Bolte
>> <matthias.bolte(a)googlemail.com> wrote:
>>> 2010/3/9 Jonathan Kelley <jkelley(a)vm-labs.com>:
>>>> Just curious but how long has ESX support been in libvirt?
>>>
>>> Since version 0.7.0 (August 2009).
>>>
>>>> Also I noticed this error when accessing one of my windows vms:
>>>>
>>>> error: internal error Expecting VMX entry 'scsi0.virtualDev' to
be
>>>> 'buslogic' or 'lsilogic' but found 'lsisas1068'
>>>
>>> I've just posted a patch to add lsisas1068 to the list of known SCSI
>>> controller types.
>>>
>>> Thanks for reporting.
>>>
>>> Matthias
>>>
>>
>