Anno domini 2009 Daniel Veillard scripsit:
Hi!
> > Fix compile errors in 'safezero()' functions in util.c
> > Commit 70e7672184ff639856d5f2f3bf7849464031dff9 introduced some
> > compile errors because of the unsued 'flags' parameter in all three
> > version of the 'safezero()' function.
>
On Fri, Mar 20, 2009 at 05:31:32PM +0100, Maximilian Wilhelm wrote:
>
> Hi!
>
> Fix compile errors in 'safezero()' functions in util.c
>
> Commit 70e7672184ff639856d5f2f3bf7849464031dff9 introduced some
> compile errors because of the unsued 'flags' parameter in all three
> version of the
Hi!
Fix compile errors in 'safezero()' functions in util.c
Commit 70e7672184ff639856d5f2f3bf7849464031dff9 introduced some
compile errors because of the unsued 'flags' parameter in all three
version of the 'safezero()' function.
Signed-Off-By: Maximilian Wilhelm
The attached patch fix
Sorry all about my last email, the subject should be "[RFC] Power
Hypervisor
Libvirt support". There should be an error here.
Thanks again,
Em Sex, 2009-03-20 às 13:58 -0300, Eduardo Otubo escreveu:
> Hello all,
>
> I've been working on a libvirt extension to manage IBM's Power VMs
> (LPARs). T
Hello all,
I've been working on a libvirt extension to manage IBM's Power VMs
(LPARs). The Power systems are managed through management console
referred to as the HMC or using a management partition (IVM). Both HMC
and IVM runs an SSH, then you can reach it via command line, and an HTTP
server, th
Is there any authorization mechanism in libvirt? I've got TLS going so
that only those with a cert signed by my CA are allowed in, but there
appears to be no way for me to only allow them access to certain VMs.
Can I limit folks to specific VMs or VNC ports? Ideally I can allow
access only to those
In libvirt 0.6.1, if you create a domain description of type 'kvm'
without an arch set on an x86-64 host, you would get an i686 qemu guest
rather than the expected x86-64 kvm guest.
This is because virCapabilitiesDefaultGuestArch doesn't take the domain
type into consideration, so it just returned
On Fri, Mar 20, 2009 at 02:43:40PM +0100, Chris Lalancette wrote:
> Daniel Veillard wrote:
> > On Mon, Mar 16, 2009 at 04:26:58PM +0100, Chris Lalancette wrote:
> >> All,
> >> Attached is a *very* rough first draft of the secure migration code
> >> I'm
> >> working on. This is in no way read
Daniel Veillard wrote:
> On Mon, Mar 16, 2009 at 04:26:58PM +0100, Chris Lalancette wrote:
>> All,
>> Attached is a *very* rough first draft of the secure migration code I'm
>> working on. This is in no way ready for merge. That being said, this
>> demonstrates the basic idea that I'm pursui
2009/3/16 Anton Protopopov
> Hi all.
>
> When libvirt creates an OpenVZ machine, it does smth like
> # vzctl create $ctid --ostemplate `ostemplate`
> And we can't specify an --config `config` argument. In this case vzctl
> chooses
> a default config file (a value of CONFIG variable from /etc/vz
On Fri, Mar 20, 2009 at 11:18:57AM +, Daniel P. Berrange wrote:
> To address this I think we'd need to completely change the logic to
> do something like
>
> - For each directory in $PATH
> For each emulator name in (qemu, qemu-system-x864, etc)
> If emulator exists
>
On Fri, Mar 20, 2009 at 12:06:25PM +0100, Daniel Veillard wrote:
> On Thu, Mar 19, 2009 at 08:17:52PM +0530, Amit Shah wrote:
> > This patchset makes use of the posix_fallocate() call to allocate
> > chunks of files whenever needed if it's available.
> >
> > We fallback to using safewrite() if it'
On Fri, Mar 20, 2009 at 11:57:24AM +0100, Daniel Veillard wrote:
> On Mon, Mar 16, 2009 at 06:03:59PM +, Daniel P. Berrange wrote:
> > Currently we are pretty strict about what emulator binary we allow for
> > QEMU guests on x86 arches. In particular, for arch+domain type combos:
> >
> > - i6
On Thu, Mar 19, 2009 at 09:47:12PM +0530, Amit Shah wrote:
> On (Thu) Mar 19 2009 [20:17:52], Amit Shah wrote:
> > This patchset makes use of the posix_fallocate() call to allocate
> > chunks of files whenever needed if it's available.
> >
> > We fallback to using safewrite() if it's not available
On Thu, Mar 19, 2009 at 08:17:54PM +0530, Amit Shah wrote:
> Make use of the safezero() function to allocate disk space instead
> of safewrite() to write zeros. The safezero() function will use
> posix_fallocate() on supported systems.
>
> If progress activity is not requested (current behaviour),
On Thu, Mar 19, 2009 at 08:17:53PM +0530, Amit Shah wrote:
> Using posix_fallocate() to allocate disk space and fill it with zeros is
> faster
> than writing the zeros block-by-block.
>
> Also, for backing file systems that support extents and the fallocate()
> syscall,
> this operation will giv
On Fri, Mar 20, 2009 at 11:45:06AM +0100, Daniel Veillard wrote:
>
> Okay I have tried to think again about this, from the code fragment
> before and discussions on IRC while performances are tolerable, there
> is a lot of costs related to the 64KB chunking imposed by the XML-RPC.
This isn't XM
On Thu, Mar 19, 2009 at 08:17:52PM +0530, Amit Shah wrote:
> This patchset makes use of the posix_fallocate() call to allocate
> chunks of files whenever needed if it's available.
>
> We fallback to using safewrite() if it's not available.
>
> mmap() could be used instead of safewrite too; I have
On Mon, Mar 16, 2009 at 06:03:59PM +, Daniel P. Berrange wrote:
> Currently we are pretty strict about what emulator binary we allow for
> QEMU guests on x86 arches. In particular, for arch+domain type combos:
>
> - i686+qemu must use 'qemu' binary
> - x86_64+qemu must use 'qemu-system-x86_6
On Mon, Mar 16, 2009 at 04:26:58PM +0100, Chris Lalancette wrote:
> All,
> Attached is a *very* rough first draft of the secure migration code I'm
> working on. This is in no way ready for merge. That being said, this
> demonstrates the basic idea that I'm pursuing, and I've actually been ab
On Fri, Mar 20, 2009 at 08:23:46AM +0100, Nikola Ciprich wrote:
> Hi Dan,
> I'd like to ask about qemu-0.10.0: it already contains KVM support,
> BUT in contrary to std kvm userspace package, KVM support needs to be enabled
> by switch (while in kvm shipped userspace it's enabled by default and can
Zvi Dubitzky wrote:
> After generating TLS certificates for Libvirt remote access , I test the
> certificates
> by running pki_check.sh and get the following message :
> The CA certificate and the client certificate do not match
>
> What can cause this message ?
>
> I guess this is a problem
Hi Dan,
I'd like to ask about qemu-0.10.0: it already contains KVM support,
BUT in contrary to std kvm userspace package, KVM support needs to be enabled
by switch (while in kvm shipped userspace it's enabled by default and can by
disabled by switch).
How can I enable it when I want to use new qem
23 matches
Mail list logo
