Hello Eric,
On Thursday 19 January 2012 21:38:22 Eric Blake wrote:
> That's an unusual mix, where the syscall exists (since 2.6.27) but libc
> is too old to use the syscall.
The original kernel was 2.6.26, but which later was updated to 2.6.32 for
better support of newer hardware.
> Then how ab
On Sun, Jan 22, 2012 at 12:30:20PM +0100, Guido Günther wrote:
> On Fri, Jan 20, 2012 at 05:01:48PM +, Daniel P. Berrange wrote:
> > On Fri, Jan 20, 2012 at 05:57:34PM +0100, Guido Günther wrote:
> > > by dereferencing a NULL pointer in the call to
> > > virNodeSuspendGetTargetMask.
> > >
> >
On Fri, Jan 20, 2012 at 02:55:27PM -0700, Eric Blake wrote:
> On 01/20/2012 01:15 PM, Zeeshan Ali (Khattak) wrote:
> > From 6895c107970ea6daf3d0e7f8be9a1a4e97b2278b Mon Sep 17 00:00:00 2001
> > From: "Zeeshan Ali (Khattak)"
> > Date: Fri, 20 Jan 2012 21:50:35 +0200
> > Subject: [PATCH] Allow custo
On Fri, Jan 20, 2012 at 10:41:37PM +0100, Jiri Denemark wrote:
> On Fri, Jan 20, 2012 at 14:06:26 -0700, Eric Blake wrote:
> > Although this is a public API break, it only affects users that
> > were compiling against *_LAST values, and can be trivially
> > worked around without impacting compilati
On Mon, Jan 23, 2012 at 10:33:18 +, Daniel P. Berrange wrote:
> On Fri, Jan 20, 2012 at 02:55:27PM -0700, Eric Blake wrote:
> > 2. we probably need an API to allow the user to change this XML on the
> > fly for a running domain. Which means you ought to investigate whether
> > you can merge yo
On Fri, Jan 20, 2012 at 11:11:57PM +0200, Zeeshan Ali (Khattak) wrote:
> From: "Zeeshan Ali (Khattak)"
>
> ---
> libvirt-gconfig/libvirt-gconfig-domain.c | 115
> +
> libvirt-gconfig/libvirt-gconfig-domain.h |8 ++
> libvirt-gconfig/libvirt-gconfig-helpers.c |
On Thu, Jan 19, 2012 at 03:18:00PM -0700, Eric Blake wrote:
> On 01/17/2012 04:44 AM, Michal Privoznik wrote:
> > There is now a standard QEMU guest agent that can be installed
> > and given a virtio serial channel
> >
> >
> >
>
> Do we really want to be documenting a path in the libv
On Fri, Jan 20, 2012 at 07:16:22PM +0100, Michal Privoznik wrote:
> On 19.01.2012 23:18, Eric Blake wrote:
> > On 01/17/2012 04:44 AM, Michal Privoznik wrote:
> >> There is now a standard QEMU guest agent that can be installed
> >> and given a virtio serial channel
> >>
> >>
> >>
[snip
On Fri, Jan 20, 2012 at 02:55:27PM -0700, Eric Blake wrote:
> On 01/20/2012 01:15 PM, Zeeshan Ali (Khattak) wrote:
> > From 6895c107970ea6daf3d0e7f8be9a1a4e97b2278b Mon Sep 17 00:00:00 2001
> > From: "Zeeshan Ali (Khattak)"
> > Date: Fri, 20 Jan 2012 21:50:35 +0200
> > Subject: [PATCH] Allow custo
On Fri, Jan 20, 2012 at 11:11:57PM +0200, Zeeshan Ali (Khattak) wrote:
> From: "Zeeshan Ali (Khattak)"
>
> ---
> libvirt-gconfig/libvirt-gconfig-domain.c | 115
> +
> libvirt-gconfig/libvirt-gconfig-domain.h |8 ++
> libvirt-gconfig/libvirt-gconfig-helpers.c |
On Mon, Jan 23, 2012 at 10:22:35AM +, Daniel P. Berrange wrote:
> On Sun, Jan 22, 2012 at 12:30:20PM +0100, Guido Günther wrote:
> > On Fri, Jan 20, 2012 at 05:01:48PM +, Daniel P. Berrange wrote:
> > > On Fri, Jan 20, 2012 at 05:57:34PM +0100, Guido Günther wrote:
> > > > by dereferencing
QEMU supports a bunch of CPUID features that are tied to the kvm CPUID
nodes rather than the processor's. They are "kvmclock", "kvm_nopiodelay",
"kvm_mmu", "kvm_asyncpf". These are not known to libvirt and their
CPUID leaf might move if (for example) the Hyper-V extensions are enabled.
Hence thei
The qemu32 CPU model is chosen based on the name when
creating the QEMU command line. Reflect the kvm32/kvm64/qemu32/qemu64
CPU models in the element when doing the opposite transformation.
To do this, we need to not look at def->os.arch until after the
command-line has been parsed.
At the same
The qemu32/qemu64 models are weird in that the exact combination of
CPUID flags does not match any actual processor. kvm32 and kvm64 are
a better match when not using TCG. Use them when -cpu is only needed
to hardcode a 32-bit guest arch or for kvmclock.
Signed-off-by: Paolo Bonzini
---
src/qe
Add kvmclock timer to documentation, schema and parsers. Keep the
platform timer first since it is kind of special, and alphabetize
the others when possible (i.e. when it does not change the ABI).
Signed-off-by: Paolo Bonzini
---
docs/formatdomain.html.in |4 ++--
docs/schemas/domaincom
Creating part of the -cpu command-line from something other than the
XML element introduces some ugliness.
---
src/qemu/qemu_command.c| 72 ++--
tests/qemuargv2xmltest.c |4 +
.../qemuxml2argv-cpu-host-kvmclock.args
---
tools/virsh.c | 111 +++
tools/virsh.pod | 11 +
2 files changed, 122 insertions(+), 0 deletions(-)
diff --git a/tools/virsh.c b/tools/virsh.c
index d635b56..92029fd 100644
--- a/tools/virsh.c
+++ b/tools/virsh.c
@@ -15809,6 +15809,
---
src/qemu/qemu_conf.h |1 +
src/qemu/qemu_driver.c | 82 ++
src/qemu/qemu_monitor.c | 40
src/qemu/qemu_monitor.h |1 +
src/qemu/qemu_monitor_json.c |8
src/qemu/qemu_monitor_text.c | 15
We already provide ways to detect when a domain has been paused as a
result of I/O error, but there was no way of getting the exact error or
even the device that experienced it. This new API may be used for both.
Jiri Denemark (4):
virDomainIOError public API and remote protocol
virsh: Implem
We already provide ways to detect when a domain has been paused as a
result of I/O error, but there was no way of getting the exact error or
even the device that experienced it. This new API may be used for both.
---
include/libvirt/libvirt.h.in | 19 +++
src/driver.h
QEMU always sends details about all available block devices as an answer
for "info block"/"query-block" command. On the other hand, our
qemuMonitorGetBlockInfo was made for a single block devices queries
only. Thus, when asking for multiple devices, we asked qemu multiple
times to always get the sa
On 01/23/2012 02:48 AM, Philipp Hahn wrote:
>> Then how about this patch:
>>
>> From 330f666036943a0fc423a4b5db2ca294fb2a4298 Mon Sep 17 00:00:00 2001
>> From: Eric Blake
>> Date: Thu, 19 Jan 2012 13:35:39 -0700
>> Subject: [PATCH] build: skip lxc with too-old glibc
> ...
>
> Looks good: Now the
On 01/20/2012 10:50 PM, Laine Stump wrote:
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If those VFs
are then passed-through to a guest using
These patches are taken from here:
https://www.redhat.com/archives/libvir-list/2011-October/msg00135.html
I've just rebased and polished them.
The QEMU guest agent "/usr/bin/qemu-ga" has some handy functions
for controlling the guest, not least, shutdown/reboot and filesystem
freeze/tha
This makes use of the QEMU guest agent to implement the
virDomainShutdownFlags and virDomainReboot APIs. With
no flags specified, it will prefer to use the agent, but
fallback to ACPI. Explicit choice can be made by using
a suitable flag
* src/qemu/qemu_driver.c: Wire up use of agent
---
src/qemu
There is now a standard QEMU guest agent that can be installed
and given a virtio serial channel
The protocol that runs over the guest agent is JSON based and
very similar to the JSON monitor. We can't use exactly the same
code because there are some odd differences in the
Add a new API virDomainShutdownFlags and define:
VIR_DOMAIN_SHUTDOWN_DEFAULT= 0,
VIR_DOMAIN_SHUTDOWN_ACPI_POWER_BTN = (1 << 0),
VIR_DOMAIN_SHUTDOWN_GUEST_AGENT= (1 << 1),
Also define some flags for the reboot API
VIR_DOMAIN_REBOOT_DEFAULT= 0,
VIR_DOMAIN_RE
Extend the 'shutdown' and 'reboot' methods so that they both
accept a new argument
--mode acpi|agent
* tools/virsh.c: New args for shutdown/reboot
* tools/virsh.pod: Document new args
---
tools/virsh.c | 47 +--
tools/virsh.pod | 12 +
On Mon, Jan 23, 2012 at 1:01 PM, Christophe Fergeau wrote:
> On Fri, Jan 20, 2012 at 11:11:57PM +0200, Zeeshan Ali (Khattak) wrote:
>> From: "Zeeshan Ali (Khattak)"
>>
>> ---
>> libvirt-gconfig/libvirt-gconfig-domain.c | 115
>> +
>> libvirt-gconfig/libvirt-gconfig
Added RSS information gathering into qemuMemoryStats into qemu driver
and the reporting into virsh dommemstat.
---
include/libvirt/libvirt.h.in |7 ++-
src/qemu/qemu_driver.c | 21 +
tools/virsh.c|2 ++
3 files changed, 25 insertions(+), 5 de
One more parameter added into the function parsing /proc//stat
and the call of the function is fixed as well.
---
src/qemu/qemu_driver.c | 25 ++---
1 files changed, 18 insertions(+), 7 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 608e82a..
This patch enables reporting of Resident Set Size for qemu process. It
is available through qemudDomainMemoryStats and qemudGetProcessInfo. The
reporting is also added into "virsh dommemstat" command.
Martin Kletzander (2):
Added RSS information gathering into qemudGetProcessInfo
Added RSS rep
The 23/01/12, Michal Privoznik wrote:
> +By default the hypervisor will try to pick a suitable shutdown
> +method. To specify an alternative method, the I<--mode> parameter
> +can specify C or C.
> +
What's the "suitable shutdown method", BTW? If I don't give the --mode
option, it is not clear wh
On Mon, Jan 23, 2012 at 04:41:43PM +0100, Nicolas Sebrecht wrote:
> The 23/01/12, Michal Privoznik wrote:
>
> > +By default the hypervisor will try to pick a suitable shutdown
> > +method. To specify an alternative method, the I<--mode> parameter
> > +can specify C or C.
> > +
>
> What's the "sui
On 01/18/2012 03:23 PM, Peter Krempa wrote:
I've reworked this patches to use a separate element for storing the
short note. This v2 also contains som new patches, especially added
support for the LXC driver, and optionaly API to get the description.
(See patches marked as optional). These are no
On Mon, Jan 23, 2012 at 14:11:08 +0100, Paolo Bonzini wrote:
> The qemu32 CPU model is chosen based on the name when
> creating the QEMU command line. Reflect the kvm32/kvm64/qemu32/qemu64
> CPU models in the element when doing the opposite transformation.
> To do this, we need to not look at de
On Mon, Jan 23, 2012 at 14:11:11 +0100, Paolo Bonzini wrote:
> The qemu32/qemu64 models are weird in that the exact combination of
> CPUID flags does not match any actual processor. kvm32 and kvm64 are
> a better match when not using TCG. Use them when -cpu is only needed
> to hardcode a 32-bit g
On Mon, Jan 23, 2012 at 04:57:21PM +0100, Jiri Denemark wrote:
> On Mon, Jan 23, 2012 at 14:11:11 +0100, Paolo Bonzini wrote:
> > The qemu32/qemu64 models are weird in that the exact combination of
> > CPUID flags does not match any actual processor. kvm32 and kvm64 are
> > a better match when not
On Mon, Jan 23, 2012 at 14:11:09 +0100, Paolo Bonzini wrote:
> Add kvmclock timer to documentation, schema and parsers. Keep the
> platform timer first since it is kind of special, and alphabetize
> the others when possible (i.e. when it does not change the ABI).
Any chance the "clock" part in "k
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
On 01/20/2012 10:50 PM, Laine Stump wrote:
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If thos
On 01/23/2012 08:50 AM, Peter Krempa wrote:
> On 01/18/2012 03:23 PM, Peter Krempa wrote:
>> I've reworked this patches to use a separate element for storing the
>> short note. This v2 also contains som new patches, especially added
>> support for the LXC driver, and optionaly API to get the descri
On 01/23/2012 04:52 PM, Jiri Denemark wrote:
I think we could just set cpu->model even if the model used in qemu command
line was {qemu,kvm}{32,64}. That would probably mean we need to add some of
the models in cpu_map.xml, though.
Actually I was doing that on purpose, not just for laziness. :)
On Mon, Jan 23, 2012 at 09:17:51AM -0700, Eric Blake wrote:
> On 01/23/2012 08:50 AM, Peter Krempa wrote:
> > On 01/18/2012 03:23 PM, Peter Krempa wrote:
> >> I've reworked this patches to use a separate element for storing the
> >> short note. This v2 also contains som new patches, especially adde
On 01/23/2012 05:03 PM, Daniel P. Berrange wrote:
> > The qemu32/qemu64 models are weird in that the exact combination of
> > CPUID flags does not match any actual processor. kvm32 and kvm64 are
> > a better match when not using TCG. Use them when -cpu is only needed
> > to hardcode a 3
On 01/23/2012 05:05 PM, Jiri Denemark wrote:
> Add kvmclock timer to documentation, schema and parsers. Keep the
> platform timer first since it is kind of special, and alphabetize
> the others when possible (i.e. when it does not change the ABI).
Any chance the "clock" part in "kvmclock" i
On Mon, Jan 23, 2012 at 05:23:32PM +0100, Paolo Bonzini wrote:
> On 01/23/2012 05:03 PM, Daniel P. Berrange wrote:
> > The qemu32/qemu64 models are weird in that the exact combination of
> > CPUID flags does not match any actual processor. kvm32 and kvm64 are
> > a better matc
On 01/23/2012 09:23 AM, Daniel P. Berrange wrote:
>> Changing or of a transient domain is a
>> nice-to-have, but not the end of the world. Changing of a
>> transient domain is a must-have, so we need at least one new API.
>> Setting is important, while getting is only a shortcut (we can make th
On Mon, Jan 23, 2012 at 09:46:57AM -0700, Eric Blake wrote:
> On 01/23/2012 09:23 AM, Daniel P. Berrange wrote:
> >> Changing or of a transient domain is a
> >> nice-to-have, but not the end of the world. Changing of a
> >> transient domain is a must-have, so we need at least one new API.
> >>
On 01/23/2012 11:12 AM, Laine Stump wrote:
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an element:
BTW, another advantage of defining these in rather than
is that it makes it easie
On 01/23/2012 05:30 PM, Daniel P. Berrange wrote:
> On Mon, Jan 23, 2012 at 05:23:32PM +0100, Paolo Bonzini wrote:
>> On 01/23/2012 05:03 PM, Daniel P. Berrange wrote:
>> > The qemu32/qemu64 models are weird in that the exact combination of
>> > CPUID flags does not match any actual
On Mon, Jan 23, 2012 at 04:53:40PM +0200, Zeeshan Ali (Khattak) wrote:
> On Mon, Jan 23, 2012 at 1:01 PM, Christophe Fergeau
> wrote:
> > I wouldn't make this recursive, I'd just set the namespace on the root
> > node in case users of the API want to use different namespaces in the xml
> > they e
Based on a patch from Zeeshan Ali (Khattak)
---
libvirt-gconfig/libvirt-gconfig-domain.c | 60 +
libvirt-gconfig/libvirt-gconfig-domain.h |7 +++
libvirt-gconfig/libvirt-gconfig-helpers-private.h |1 +
libvirt-gconfig/libvirt-gconfig-helpers.c
From: "Daniel P. Berrange"
* src/util/threads-pthread.c, src/util/threads.h: Add virThreadCancel
---
src/util/threads-pthread.c |5 +
src/util/threads.h |1 +
2 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/src/util/threads-pthread.c b/src/util/threads-pthread.
This series of patch is the minimal required to get a working proof
of concept implementation of fine grained access control in libvirt.
This demonstrates
- Obtaining a client identity from a socket
- Ensuring RPC calls are executed with the correct identity sset
- A policykit access driver th
From: "Daniel P. Berrange"
Allow the logging APIs to be called with a va_list for format
args, instead of requiring var-args usage.
* src/util/logging.h, src/util/logging.c: Add virLogVMessage
---
src/util/logging.c | 29 -
src/util/logging.h |5 +
2 files
From: "Daniel P. Berrange"
---
include/libvirt/virterror.h |3 +
po/POTFILES.in|1 +
src/Makefile.am | 16 +
src/access/apis.txt | 577 +
src/access/viraccessdriver.h | 51
src/ac
From: "Daniel P. Berrange"
Add new APIs virNetServerClientGetTLSSession,
virNetServerClientIsLocal, virNetServerClientGetSecurityContext
virNetServerClientGetSASLSession, virNetSocketGetSecurityContext
and virNetTLSSessionGetX509DName
---
src/rpc/virnetserverclient.c | 48 +
From: "Daniel P. Berrange"
---
po/POTFILES.in |1 +
src/Makefile.am | 12 ++-
src/access/org.libvirt.domain.policy | 37
src/access/viraccessdriverpolkit.c | 163 ++
src/access/viraccessdriverpolkit.h
From: "Daniel P. Berrange"
---
include/libvirt/libvirt.h.in | 30 +++
include/libvirt/virterror.h |1 +
src/datatypes.h | 22 +-
src/libvirt.c| 176 ++
src/util/virterror.c |6 ++
5 files changed,
From: "Daniel P. Berrange"
Currently the server determines whether authentication of clients
is complete, by checking whether an identity is set. This patch
removes that lame hack and replaces it with an explicit method
for changing the client auth code
* daemon/remote.c: Update for new APis
* s
From: "Daniel P. Berrange"
Add APIs which allow storage of a real & effective identity on
all server clients. Also add an API which allows creation of an
initial identity based on the results of client authentication
processes like TLS, x509, SASL, SO_PEERCRED
---
src/rpc/virnetserverclient.c |
From: "Daniel P. Berrange"
When dispatching an RPC API call, setup the access manager to hold
the real & effective identities of the current server client whose
RPC is being dispatched. The setting is thread-local, so only
affects the API call in this thread
---
src/rpc/virnetserverclient.c |
From: "Daniel P. Berrange"
Introduce a new 'access_driver' configuration parameter which
specifies the name of the access control manager driver to
activate. By default the 'no op' driver is active
---
src/qemu/qemu.conf |5 +
src/qemu/qemu_conf.c | 10 ++
src/qemu/qemu_c
From: "Daniel P. Berrange"
---
po/POTFILES.in |1 +
src/Makefile.am |3 +-
src/access/viraccessdriverselinux.c | 388 +++
src/access/viraccessdriverselinux.h | 28 +++
src/access/viraccessmanager.c |2 +
From: "Daniel P. Berrange"
Inserts the minimal access control checks to the QEMU driver to
protect usage of virDomainObjPtr objects.
---
src/qemu/qemu_driver.c| 631 ++--
src/qemu/qemu_migration.c |5 +
2 files changed, 607 insertions(+), 29 delet
The domain schema enforced restrictions on the domain name string that
the code doesn't. This patch relaxes the check, leaving the restrictions
on the driver or hypervisor.
---
And maybe we should consider adding some restrictions on the qemu driver, as
the daemon
is competely fine with creating a
On 01/23/2012 05:12 PM, Laine Stump wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an element:
Nice! I should have thought of this in my original proposal - it's the
logical extension of having networks of type='hostdev'. I would
Hit send too soon... a couple more observations.
On 01/23/2012 05:12 PM, Laine Stump wrote:
(Note that even with *no new XML*, we already have a problem where just
scanning all the entries won't tell us about all host devices
that are currently assigned exclusively to guests - using a network
d
On Mon, Jan 23, 2012 at 06:53:17PM +0100, Peter Krempa wrote:
> The domain schema enforced restrictions on the domain name string that
> the code doesn't. This patch relaxes the check, leaving the restrictions
> on the driver or hypervisor.
> ---
> And maybe we should consider adding some restricti
On 01/23/2012 10:53 AM, Peter Krempa wrote:
> The domain schema enforced restrictions on the domain name string that
> the code doesn't. This patch relaxes the check, leaving the restrictions
> on the driver or hypervisor.
> ---
> And maybe we should consider adding some restrictions on the qemu dr
On Wed, Jan 11, 2012 at 04:33:29PM +, Daniel P. Berrange wrote:
> This patch series adds support for sVirt to the LXC driver. In this
> series, all LXC guests continue to run unconfined by default. The
> app has to explicitly request sVirt confinement for the guest. This
> is to ensure backward
On 01/23/2012 01:06 PM, Paolo Bonzini wrote:
On 01/23/2012 05:12 PM, Laine Stump wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an element:
Nice! I should have thought of this in my original proposal - it's the
logical extension
On 01/23/2012 07:48 AM, Michal Privoznik wrote:
> There is now a standard QEMU guest agent that can be installed
> and given a virtio serial channel
>
>
>
>
>
You also need to update docs/formatdomain.html.in to include this
specific example. May I propose that you squash
On 01/20/2012 07:16 PM, Eric Blake wrote:
On 01/18/2012 09:20 AM, Stefan Berger wrote:
Add a test case to test the virHashEqual function.
---
tests/hashtest.c | 78
+++
1 file changed, 78 insertions(+)
Even better - you test your new AP
On 01/23/2012 07:48 AM, Michal Privoznik wrote:
> Add a new API virDomainShutdownFlags and define:
>
> VIR_DOMAIN_SHUTDOWN_DEFAULT= 0,
> VIR_DOMAIN_SHUTDOWN_ACPI_POWER_BTN = (1 << 0),
> VIR_DOMAIN_SHUTDOWN_GUEST_AGENT= (1 << 1),
>
> Also define some flags for the reboot AP
On 01/23/2012 07:48 AM, Michal Privoznik wrote:
[for some reason, this one didn't get threaded properly - bug in git
send-email?]
> This makes use of the QEMU guest agent to implement the
> virDomainShutdownFlags and virDomainReboot APIs. With
> no flags specified, it will prefer to use the agent
On 01/23/2012 07:48 AM, Michal Privoznik wrote:
> Extend the 'shutdown' and 'reboot' methods so that they both
> accept a new argument
>
> --mode acpi|agent
>
> * tools/virsh.c: New args for shutdown/reboot
> * tools/virsh.pod: Document new args
> ---
> tools/virsh.c | 47 +++
On Mon, Jan 23, 2012 at 7:19 PM, Christophe Fergeau wrote:
> Based on a patch from Zeeshan Ali (Khattak)
Looks good! I'll test it later. Some minor issues:
> + gvir_config_object_set_namespace(custom_xml, ns, ns_uri, TRUE);
You meant to pass 'FALSE' in the last arg?
> + g_return_val_if_
On 01/18/2012 09:20 AM, Stefan Berger wrote:
> Compare two filter definitions for equality and only rebuild/instantiate
> the new filter if the two filters are found to be different. This improves
> performance during an update of a filter with no obvious change or the
> reloading
> of filters dur
On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Add a virFileTouch API which ensures that a file will always
> exist, even if zero length
>
> * src/lxc/lxc_container.c, src/util/virfile.h: virFileTouch
This line is not quite accurate,
> ---
> src/util/virfil
On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> The current setup code for LXC is bind mounting /dev/pts/ptmx
> ontop of a character device /dev/ptmx. This is denied by SELinux
s/ontop/on top/
> policy and is just wrong. The target of a bind mount should just
On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Revert parsing changes:
>
> commit 302fe95ffa1bc5f1c61c0beb31a1adfbc38c668e
> Author: Eric Blake
> Date: Wed Jan 4 16:01:24 2012 -0700
>
> seclabel: fix regression in libvirtd restart
>
> commit b
Hi,
I tried to update the fedora mingw package to follow the mingw64
packaging guideline and allow build for x86 and x64. But I got into
build warning and errors for x86_64. (using Fedora Cross project repo:
http://build1.openftd.org/fedora-cross/fedora-cross.repo,
x86_64-w64-mingw32-gcc (GCC) 4.6
On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> This re-introduces parsing & formatting for per device seclabels.
> There is a new virDomainDeviceSeclabelPtr struct and corresponding
> APIs for parsing/formatting.
> ---
> src/conf/domain_conf.c | 115
> ++
On 01/23/2012 03:38 PM, Eric Blake wrote:
> On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
>> From: "Daniel P. Berrange"
>>
>> This re-introduces parsing & formatting for per device seclabels.
>> There is a new virDomainDeviceSeclabelPtr struct and corresponding
>> APIs for parsing/formatting.
On 01/11/2012 09:33 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Curently security labels can be of type 'dynamic' or 'static'.
> If no security label is given, then 'dynamic' is assumed. The
> current code takes advantage of this default, and avoids even
> saving elements with
On 01/23/2012 03:29 PM, Marc-André Lureau wrote:
> Hi,
>
> I tried to update the fedora mingw package to follow the mingw64
> packaging guideline and allow build for x86 and x64. But I got into
> build warning and errors for x86_64. (using Fedora Cross project repo:
> http://build1.openftd.org/fed
From: "Zeeshan Ali (Khattak)"
Applications can now insert custom nodes and hierarchies into domain
cofiguration XML. Although currently not enforced, application are
required to use their own namespaces on every custom node they insert.
---
docs/formatdomain.html.in |
From: "Zeeshan Ali (Khattak)"
Applications can now insert custom nodes and hierarchies into domain
cofiguration XML. Although currently not enforced, application are
required to use their own namespaces on every custom node they insert.
---
docs/formatdomain.html.in |
89 matches
Mail list logo
