Commit 7c2d65d dropped setting default mode.
Update zfs tests accordingly.
---
tests/storagepoolxml2xmlout/pool-zfs-sourcedev.xml | 3 ---
tests/storagepoolxml2xmlout/pool-zfs.xml | 3 ---
2 files changed, 6 deletions(-)
diff --git a/tests/storagepoolxml2xmlout/pool-zfs-sourcedev.xml
On 2015/5/26 10:48, Eric Blake wrote:
> On 05/25/2015 08:43 PM, Eric Blake wrote:
>> On 05/25/2015 08:28 PM, zhang bo wrote:
>>> IME-Version: 1.0
>>> Content-Type: text/plain; charset=UTF-8
>>> Content-Transfer-Encoding: 8bit
>>>
>>> caller should be translated to "璋冪敤绋嬪簭" rather than "璋冨害绋嬪簭", wh
On 05/25/2015 08:43 PM, Eric Blake wrote:
> On 05/25/2015 08:28 PM, zhang bo wrote:
>> IME-Version: 1.0
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 8bit
>>
>> caller should be translated to "璋冪敤绋嬪簭" rather than "璋冨害绋嬪簭", which in fact
>> refers to "scheduler" in English
On 05/25/2015 08:28 PM, zhang bo wrote:
> IME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> caller should be translated to "璋冪敤绋嬪簭" rather than "璋冨害绋嬪簭", which in fact
> refers to "scheduler" in English.
> ---
> po/zh_CN.po | 8
> 1 file cha
I don't know why the codes in chinese become messy-code in this patch for me.
I'm using thunderBird on *Windows*.
The patch looked fine on my *Linux* machine.
How does it appear at your side?
If there's more work to do to make it look normal, please let me know.
BTW: shall I change the headers
IME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
caller should be translated to "璋冪敤绋嬪簭" rather than "璋冨害绋嬪簭", which in fact
refers to "scheduler" in English.
---
po/zh_CN.po | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/po/zh_
On 05/24/2015 07:37 AM, John Ferlan wrote:
>
>
> On 05/21/2015 04:03 PM, Cole Robinson wrote:
>> The XML parser sets a default if none is explicitly passed in.
>> This is then used at pool/vol creation time, and unconditionally reported
>> in the XML.
>>
>> The problem with this approach is that
On 05/24/2015 07:38 AM, John Ferlan wrote:
>
>
> On 05/21/2015 04:03 PM, Cole Robinson wrote:
>> ---
>> v3:
>> New patch
>>
>> src/conf/storage_conf.c| 42
>> +-
>> tests/storagepoolxml2xmlout/pool-netfs-gluster.xml | 2 --
>> tests/storagevo
On 05/24/2015 07:20 AM, John Ferlan wrote:
>
>
> On 05/21/2015 04:03 PM, Cole Robinson wrote:
>> - Don't redocument the permissions fields for backingstore, just point to
>> the volume docs.
>> - Clarify that owner/group are inherited from the parent directory at
>> volume create/pool build t
On 05/24/2015 09:38 AM, Pavel Fedin wrote:
> Virt machine in qemu has PCI generic host controller, and can use PCI
> devices. This
> provides performance improvement as well as vhost-net with irqfd support for
> virtio-net.
> However libvirt still insists on virtio devices attached to Virt mach
Thank you.
I will go through your comments just in case I'm going to push any other
changes.
Sorry for the inconvenience from my patches :-/.
Pavel
On Mon, May 25, 2015 at 5:58 PM, Michal Privoznik
wrote:
> On 21.05.2015 13:07, Pavel Boldin wrote:
> > The patchset represented in the mail thre
On 05/22/2015 09:18 PM, Maxim Nestratov wrote:
This new driver 'vz' will be used as a substitution for parallels driver.
New domains will be created with 'vz' domain type. Old 'parallels' domains
remain supported. Connection to the driver can be made either way:
vz:///system or parallels:///sys
On 05/21/2015 04:49 PM, Maxim Nestratov wrote:
Cleanup code in prlsdkLoadDomain doesn't take into account the fact
if private domain structure along with freeing function is assigned
or not. In case it is, we shouldn't call it manually because
virDomainObjListRemove calls it and frees pdom.
Als
On 05/21/2015 04:49 PM, Maxim Nestratov wrote:
It is better to get all necessary parameters and check them on newly
created configuration before actually creating a domain with them or
applying them to an existing domain.
Signed-off-by: Maxim Nestratov
Thanks, ACKED and pushed.
---
src/
On 25.05.2015 17:47, Peter Krempa wrote:
> On Mon, May 25, 2015 at 17:35:19 +0200, Michal Privoznik wrote:
>> On 25.05.2015 17:18, Peter Krempa wrote:
>>> Since commit bcd9a564b631aa virDomainNumatuneGetMode returns the value
>>> via a pointer rather than in the return value. The change triggered
>
On Mon, May 25, 2015 at 05:35:19PM +0200, Michal Privoznik wrote:
On 25.05.2015 17:18, Peter Krempa wrote:
Since commit bcd9a564b631aa virDomainNumatuneGetMode returns the value
via a pointer rather than in the return value. The change triggered
problems with platforms where the compiler decides
On Mon, May 25, 2015 at 17:35:19 +0200, Michal Privoznik wrote:
> On 25.05.2015 17:18, Peter Krempa wrote:
> > Since commit bcd9a564b631aa virDomainNumatuneGetMode returns the value
> > via a pointer rather than in the return value. The change triggered
> > problems with platforms where the compile
On Mon, May 25, 2015 at 05:26:01PM +0200, Peter Krempa wrote:
On Mon, May 25, 2015 at 16:59:08 +0200, Andrea Bolognani wrote:
The command is only defined in QEMU for TARGET_I386, so issuing it on
any other architecture can't possibly work.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1
On 25.05.2015 17:18, Peter Krempa wrote:
> Since commit bcd9a564b631aa virDomainNumatuneGetMode returns the value
> via a pointer rather than in the return value. The change triggered
> problems with platforms where the compiler decides to use a data type of
> size different than integer at the poi
On Mon, May 25, 2015 at 16:59:08 +0200, Andrea Bolognani wrote:
> The command is only defined in QEMU for TARGET_I386, so issuing it on
> any other architecture can't possibly work.
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1211938
> ---
> src/qemu/qemu_driver.c | 20 +
Since commit bcd9a564b631aa virDomainNumatuneGetMode returns the value
via a pointer rather than in the return value. The change triggered
problems with platforms where the compiler decides to use a data type of
size different than integer at the point where we typecast it.
Work around the issue b
On Fri, May 22, 2015 at 01:36:14PM +0100, Daniel P. Berrange wrote:
The virNetServer class has the ability to serialize its state
to a JSON file, and then re-load that data after an in-place
execve() call to re-connect to active file handles. This data
format is critical ABI that must have compat
On 21.05.2015 13:07, Pavel Boldin wrote:
> The `virTypedParamsValidate' function now can be instructed to allow
> multiple entries for some of the keys. For this flag the type with
> the `VIR_TYPED_PARAM_MULTIPLE' flag.
>
> Add unit tests for this new behaviour.
>
> Signed-off-by: Pavel Boldin
>
On 21.05.2015 13:07, Pavel Boldin wrote:
> The `virTypedParamsAddStringList' function provides interface to add a
> NULL-terminated array of string values as a multi-value to the params.
>
> Signed-off-by: Pavel Boldin
> ---
> include/libvirt/libvirt-host.h | 6 ++
> src/libvirt_public.syms
The command is only defined in QEMU for TARGET_I386, so issuing it on
any other architecture can't possibly work.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1211938
---
src/qemu/qemu_driver.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/src/
On 21.05.2015 13:07, Pavel Boldin wrote:
> Add multikey API:
>
> * virTypedParamsFilter that returns all the parameters with specified name.
> * virTypedParamsPickStrings that returns a NULL-terminated `const char**'
>list with all the values for specified name and string type.
>
> Signed-o
On 21.05.2015 13:07, Pavel Boldin wrote:
> The patchset represented in the mail thread implements the selective block
> device migration for the QEMU driver. This closes the referenced bug [1].
>
> First the supplementary API implemented allowing for multiple key-values pair
> in the virTypedParam
On 21.05.2015 13:07, Pavel Boldin wrote:
> Allow multi-value parameters to be build using virTypedParamsAdd*
> functions by removing check for duplicates.
>
> Signed-off-by: Pavel Boldin
> ---
> src/util/virtypedparam.c | 16
> 1 file changed, 16 deletions(-)
ACK
Michal
--
li
On 21.05.2015 13:07, Pavel Boldin wrote:
> Implement a `migrate_disks' parameters for the QEMU driver. This multi-
> value parameter can be used to explicitly specify what block devices
> are to be migrated using the NBD server. Tunnelled migration using NBD
> is to be done.
>
> Signed-off-by: Pav
On 21.05.2015 13:07, Pavel Boldin wrote:
> Add `virsh migrate' option `--migratedisks' that allows CLI user to
> explicitly specify block devices to migrate.
>
> Signed-off-by: Pavel Boldin
> ---
> tools/virsh-domain.c | 23 +++
> tools/virsh.pod | 5 -
> 2 files ch
On Fri, May 22, 2015 at 14:28:05 +0200, Jiri Denemark wrote:
> On Fri, May 22, 2015 at 13:09:17 +0100, Daniel P. Berrange wrote:
> > On Fri, May 22, 2015 at 12:42:34AM +0200, Jiri Denemark wrote:
> > > Our usage of pthread conditions does not allow a single thread to wait
> > > for several events f
On 05/18/2015 09:21 AM, John Ferlan wrote:
> Commit id '73eda710' added virDomainKeyWrapDefParseXML which uses
> virXPathNodeSet, but does not handle a -1 return thus causing a possible
> loop condition exit problem later when the return value is used.
>
> Change the logic to return the value from
On 05/18/2015 09:21 AM, John Ferlan wrote:
> Recent changes to the -M/--machine processing code in qemuParseCommandLine
> caused Coverity to determine there was a possible resource leak with how
> the 'list' is managed. Rather than try to add virStringFreeList calls
> everywhere - just promote list
On Sat, May 23, 2015 at 21:45:56 -0600, Eric Blake wrote:
> qemu 2.3 added a new QMP command block-set-write-threshold,
> which allows callers to get an interrupt when a file hits a
> write threshold, rather than the current approach of repeatedly
> polling for file allocation. This patch prepares
On Fri, May 22, 2015 at 13:48:16 -0400, John Ferlan wrote:
>
>
> On 05/22/2015 10:31 AM, Jiri Denemark wrote:
> > On Fri, May 22, 2015 at 10:16:26 -0400, John Ferlan wrote:
> >>
> >>
> >> On 05/21/2015 06:42 PM, Jiri Denemark wrote:
> >>> Our usage of pthread conditions does not allow a single th
On Fri, May 22, 2015 at 01:07:31PM -0600, Eric Blake wrote:
> On 05/22/2015 08:01 AM, Pavel Hrdina wrote:
> > Some virsh commands have a size parameter, which is handled as scaled
> > integer. We don't have any *feature* that would allow to use '-1' as
> > maximum size, so it's safe to reject any
On Fri, 2015-05-15 at 11:35 +0200, Andrea Bolognani wrote:
> The guest firmware provides the same functionality as the pvpanic
> device, which is not available in QEMU on pSeries: make sure the
> XML reflects this fact by automatically adding a element
> when not already present.
>
> On the other
37 matches
Mail list logo
