On 11/11/18 10:59 PM, Han Han wrote:
> qemuDomainHubIsBusy is to check whether a usb device are attached to the hub
> device. It will be used for hotunplugging and live device update of hub
> device.
>
> Signed-off-by: Han Han
> ---
> src/qemu/qemu_hotplug.c | 64
On 11/15/2018 12:55 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Add a new memoryBacking source type "memfd", supported by QEMU (when
> the capability is available).
>
> A memfd is a specialized anonymous memory kind. As such, an anonymous
> source type could be
On 11/15/2018 12:55 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> QEMU 3.1 should only expose the property if the host is actually
> capable of creating hugetable-backed memfd. However, it may fail
> at runtime depending on requested "hugetlbsize".
>
> Reviewed-by: John
在 2018/11/15 下午8:12, Andrea Bolognani 写道:
On Thu, 2018-11-15 at 10:17 +, Daniel P. Berrangé wrote:
On Tue, Nov 13, 2018 at 03:35:43PM +0100, Andrea Bolognani wrote:
Dan, do you have any remaining concerns about the XML syntax, or can
I go ahead and push?
Honestly, I still don't much
On 11/11/18 10:59 PM, Han Han wrote:
> Signed-off-by: Han Han
> ---
> docs/news.xml | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/docs/news.xml b/docs/news.xml
> index 88774c55ae..b677f52efc 100644
> --- a/docs/news.xml
> +++ b/docs/news.xml
> @@ -35,6 +35,16 @@
>
>
On 11/15/2018 12:55 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Hi,
>
> This is an alternative series from "[PATCH 0/5] Use memfd if
> possible". Instead of automatically using memfd for anonymous memory
> when available (as suggested by Daniel), it introduces the
On 11/15/2018 12:55 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Check availability of "-object memory-backend-memfd".
>
> Reviewed-by: John Ferlan
> Signed-off-by: Marc-André Lureau
> Signed-off-by: John Ferlan
> ---
> src/qemu/qemu_capabilities.c
On 11/11/18 10:59 PM, Han Han wrote:
> Add this function to check if the a usb address is attached to a hub device.
>
> Signed-off-by: Han Han
> ---
> src/conf/domain_addr.c | 22 ++
> src/conf/domain_addr.h | 5 +
> src/libvirt_private.syms | 1 +
> 3 files
We were mistakenly skipping virZPCIDeviceAddressIsEmpty() and
virZPCIDeviceAddressIsValid() when compiling on non-Linux,
which unsurprisingly ended up causing linking failures later
in the build process.
Clue-stick-by: Peter Krempa
Signed-off-by: Andrea Bolognani
---
Pushed as build fix.
On Thu, 15 Nov 2018 12:21:55 +0100
Cornelia Huck wrote:
> After a quick look, this seems fine; have not actually tried to run it
> yet.
Played a bit with it (with zpci devices for a s390x machine), seems to
work as expected.
--
libvir-list mailing list
libvir-list@redhat.com
On Wed, 2018-11-14 at 21:38 -0200, Eduardo Habkost wrote:
> Many of the current virtio-*-pci device types actually represent
> 3 different types of devices:
> * virtio 1.0 non-transitional devices
> * virtio 1.0 transitional devices
> * virtio 0.9 ("legacy device" in virtio 1.0 terminology)
>
>
On 11/11/18 10:59 PM, Han Han wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1375423
>
> Signed-off-by: Han Han
> ---
> src/qemu/qemu_driver.c | 5 ++-
> src/qemu/qemu_hotplug.c | 81 -
> src/qemu/qemu_hotplug.h | 4 ++
> 3 files changed, 88
On 11/14/18 7:44 AM, Michal Privoznik wrote:
> For metadata locking we might need an extra fork() which given
> latest attempts to do fewer fork()-s is suboptimal. Therefore,
> there will be a qemu.conf knob to enable or this feature. But
or disable or just use "{en|dis}able" if you don't
On 11/14/18 7:44 AM, Michal Privoznik wrote:
> v4 of:
>
> https://www.redhat.com/archives/libvir-list/2018-October/msg00861.html
>
> diff to v3:
> - Introduced a config knob to enable/disable metadata locking (except
> not really). We want to have a knob that enables/disables remembering
>
On 11/15/18 4:55 AM, Michal Privoznik wrote:
> On 11/05/2018 01:58 PM, John Ferlan wrote:
>> Create a new API that will allow an adjustment of IOThread
>> polling parameters for the specified IOThread. These parameters
>> will not be saved in the guest XML. Currently the only parameters
>>
On 11/15/18 4:55 AM, Michal Privoznik wrote:
> On 11/05/2018 01:58 PM, John Ferlan wrote:
>> Separate out the fetch of the IOThread monitor call into a separate
>> helper so that a subsequent domain statistics change can fetch the raw
>> IOThread data and parse it as it sees fit.
>>
>>
On 11/14/18 7:44 AM, Michal Privoznik wrote:
> Trying to use virlockd to lock metadata turns out to be too big
> gun. Since we will always spawn a separate process for relabeling
> we are safe to use thread unsafe POSIX locks and take out
> virtlockd completely out of the picture.
>
NB: This
I would say here that we're going to "convert" the rememberOwner
configuration knob into a security driver "lock" knob that will
effectively enable or disable the usage of metadata locking for the object.
When metadata locking is enabled that means the security commit
processing will be run in
On 11/14/18 7:44 AM, Michal Privoznik wrote:
> The TPM code currently accepts pointer to a domain definition.
> This is okay for now, but in near future the security driver APIs
> it calls will require domain object. Therefore, change the TPM
> code to accept the domain object pointer.
>
>
On 10/11/18 10:19 PM, Wang Yechao wrote:
> The commit 89563efc0209b854d2b2e554423423d7602acdbd fix the
> monitor error when closing the QEMU monitor. The QEMU agent
> has a problem similar to QEMU monitor. So fix the QEMU agent
> with the same method.
>
> Signed-off-by: Wang Yechao
> ---
>
On Thu, Nov 15, 2018 at 5:55 PM Michal Privoznik wrote:
>
> On 11/15/2018 12:55 PM, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > Check availability of "-object memory-backend-memfd".
> >
> > Reviewed-by: John Ferlan
> > Signed-off-by: Marc-André Lureau
> >
On 11/15/18 7:38 PM, John Ferlan wrote:
On 11/14/18 2:52 PM, Daniel Henrique Barboza wrote:
Adding maxCpu validation in qemuDomainDefValidate allows the user to
spot over the board maxCpus counts at editing time, instead of
facing a runtime error when starting the domain. This check is also
On 11/15/18 7:40 PM, John Ferlan wrote:
On 11/14/18 2:52 PM, Daniel Henrique Barboza wrote:
v2:
- original patch was split in 3 patches as John Ferlan requested;
- patches 4 and 5 are cleanups;
- first patch link:
https://www.redhat.com/archives/libvir-list/2018-October/msg00251.html
On 11/14/18 2:52 PM, Daniel Henrique Barboza wrote:
> Adding maxCpu validation in qemuDomainDefValidate allows the user to
> spot over the board maxCpus counts at editing time, instead of
> facing a runtime error when starting the domain. This check is also
> arch independent.
>
> This leaves
On 11/14/18 2:52 PM, Daniel Henrique Barboza wrote:
> v2:
> - original patch was split in 3 patches as John Ferlan requested;
> - patches 4 and 5 are cleanups;
> - first patch link:
> https://www.redhat.com/archives/libvir-list/2018-October/msg00251.html
>
>
>
> Daniel Henrique Barboza (5):
On Thu, Nov 15, 2018 at 05:29:24PM +0100, Andrea Bolognani wrote:
> On Wed, 2018-11-14 at 21:38 -0200, Eduardo Habkost wrote:
> > Many of the current virtio-*-pci device types actually represent
> > 3 different types of devices:
> > * virtio 1.0 non-transitional devices
> > * virtio 1.0
Add the support to work with libvirt commit 66a85cb13.
Signed-off-by: Philipp Hahn
---
examples/event-test.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/event-test.py b/examples/event-test.py
index 709277b..81ebfc1 100755
--- a/examples/event-test.py
+++
On Thu, Nov 15, 2018 at 12:36 AM Andrea Bolognani
wrote:
> On Wed, 2018-11-14 at 15:19 +0800, Han Han wrote:
> > When listing snapshot with VIR_DOMAIN_SNAPSHOT_LIST_NO_METADATA, it
> > always returns 0 or no snapshot. Because we never implement funtions
> > to list no-metadata snapshot in
On Wed, 2018-11-14 at 23:46 +0100, Vitaly Kuznetsov wrote:
> The upcoming QEMU 3.1 release will bring us two new Hyper-V enlightenments:
> hv_ipi and hv_evmcs. Support these in libvirt.
>
> Changes since v2:
> - Separate docs/news.xml hunks in their own PATCH6, squash both
> changes together
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20181114233831.10374-1-ehabk...@redhat.com
Type: series
Subject: [Qemu-devel] [PATCH for-4.0 v2] virtio: Provide version-specific
variants of virtio PCI devices
=== TEST SCRIPT BEGIN
On Wed, Nov 14, 2018 at 02:22:12PM -0500, John Ferlan wrote:
>
>
> On 11/14/18 4:25 AM, Daniel P. Berrangé wrote:
> > On Tue, Nov 13, 2018 at 03:21:03PM -0500, John Ferlan wrote:
> >> Sending as an RFC primarily because I'm looking for whether either
> >> or both mechanisms in the series is more
On 11/14/2018 05:45 PM, John Ferlan wrote:
> Add the support to work with libvirt commit 66a85cb13.
>
> Signed-off-by: John Ferlan
> ---
> Although it's a build breaker and this does fix the problem - I'll wait
> to push just to make sure the text used for the message passes muster.
>
>
On Wed, Nov 14, 2018 at 09:38:31PM -0200, Eduardo Habkost wrote:
> Many of the current virtio-*-pci device types actually represent
> 3 different types of devices:
> * virtio 1.0 non-transitional devices
> * virtio 1.0 transitional devices
> * virtio 0.9 ("legacy device" in virtio 1.0 terminology)
On Mon, Nov 05, 2018 at 04:41:09PM -0600, Eric Blake wrote:
> On 10/9/18 8:23 AM, Daniel P. Berrangé wrote:
> > From: "Daniel P. Berrange"
> >
> > Currently any client which can complete the TLS handshake is able to use
> > the NBD server. The server admin can turn on the 'verify-peer' option
>
On 11/14/2018 07:17 PM, Chris Venteicher wrote:
> Quoting Michal Privoznik (2018-11-14 09:45:06)
>> On 11/11/2018 08:59 PM, Chris Venteicher wrote:
>>> Make process code usable outside qemu_capabilities by moving code
>>> from qemu_capabilities to qemu_process and exposing public functions.
>>>
On Mon, Nov 05, 2018 at 04:41:09PM -0600, Eric Blake wrote:
> On 10/9/18 8:23 AM, Daniel P. Berrangé wrote:
> > From: "Daniel P. Berrange"
> >
> > Currently any client which can complete the TLS handshake is able to use
> > the NBD server. The server admin can turn on the 'verify-peer' option
>
On Thu, Nov 15, 2018 at 11:50:56AM +0100, Cornelia Huck wrote:
> On Thu, 15 Nov 2018 10:05:59 +
> Daniel P. Berrangé wrote:
>
> > On Wed, Nov 14, 2018 at 09:38:31PM -0200, Eduardo Habkost wrote:
> > > Many of the current virtio-*-pci device types actually represent
> > > 3 different types of
On Thu, 15 Nov 2018 10:05:59 +
Daniel P. Berrangé wrote:
> On Wed, Nov 14, 2018 at 09:38:31PM -0200, Eduardo Habkost wrote:
> > Many of the current virtio-*-pci device types actually represent
> > 3 different types of devices:
> > * virtio 1.0 non-transitional devices
> > * virtio 1.0
On 11/05/2018 01:58 PM, John Ferlan wrote:
> Create a new API that will allow an adjustment of IOThread
> polling parameters for the specified IOThread. These parameters
> will not be saved in the guest XML. Currently the only parameters
> supported will allow the hypervisor to adjust the
On Thu, Nov 15, 2018 at 08:28:57AM +0100, Erik Skultety wrote:
> Commit 20ab0c4d added a new constant to reflect recent libvirt upstream
> changes. However, it also introduced a tiny typo which caused the build
> to fail.
Urgh thanks, I had it locally but forgot to commit the typo fix
before
On 11/05/2018 01:58 PM, John Ferlan wrote:
> Separate out the fetch of the IOThread monitor call into a separate
> helper so that a subsequent domain statistics change can fetch the raw
> IOThread data and parse it as it sees fit.
>
> Signed-off-by: John Ferlan
> ---
> src/qemu/qemu_driver.c |
On 11/05/2018 01:58 PM, John Ferlan wrote:
> v2: https://www.redhat.com/archives/libvir-list/2018-October/msg01065.html
>
> NB: Minor mods for this are change using 4.10.0 instead of 4.9.0, merge of
> qemu_capabilities conflict, and updated news.xml
>
> .. v2 Cover Letter:
>
> v1:
On Tue, Nov 13, 2018 at 03:35:43PM +0100, Andrea Bolognani wrote:
> On Thu, 2018-11-08 at 19:00 +0800, Yi Min Zhao wrote:
> > Abstract
> >
> > The PCI representation in QEMU has been extended for S390
> > allowing configuration of zPCI attributes like uid (user-defined
> > identifier) and
On Wed, 14 Nov 2018 21:38:31 -0200
Eduardo Habkost wrote:
> diff --git a/hw/virtio/virtio-pci.h b/hw/virtio/virtio-pci.h
> index 813082b0d7..1d2a11504f 100644
> --- a/hw/virtio/virtio-pci.h
> +++ b/hw/virtio/virtio-pci.h
(...)
> +/**
> + * VirtioPCIDeviceTypeInfo:
> + *
> + * Template for
On 11/10/2018 01:56 PM, Radoslaw Biernacki wrote:
> The device xml parser code does not set "model" while parsing
>
>
> function='0x2'/>
>
>
> virDomainDefPtr def->nets[i]->model can be NULL while latter compares strings
> with
> STREQ instead of STREQ_NULLABLE.
>
> Fixes:
From: Marc-André Lureau
QEMU 3.1 should only expose the property if the host is actually
capable of creating hugetable-backed memfd. However, it may fail
at runtime depending on requested "hugetlbsize".
Reviewed-by: John Ferlan
Signed-off-by: Marc-André Lureau
Signed-off-by: John Ferlan
---
On 11/10/2018 01:56 PM, Radoslaw Biernacki wrote:
> libvirt wrongly assumes that VF netdev has to have the
> netdev assigned to PF. There is no such requirement in SRIOV standard.
> This patch change the virNetDevSwitchdevFeature() function to deal
> with SRIOV devices which does not have netdev
On 11/10/2018 01:56 PM, Radoslaw Biernacki wrote:
> Removing redundant sections of the code
>
> Signed-off-by: Radoslaw Biernacki
> ---
> src/util/virnetdev.c | 40 +++-
> 1 file changed, 5 insertions(+), 35 deletions(-)
ACK
Michal
--
libvir-list mailing list
On 11/10/2018 01:56 PM, Radoslaw Biernacki wrote:
> linkdev is In/Out function parameter as second order reference pointer
> so requires first order dereference for checking NULLs which can be a
> result from virPCIGetNetName()
>
> Fixes: d6ee56d7237 (util: change virPCIGetNetName() to not return
From: Marc-André Lureau
Add a new memoryBacking source type "memfd", supported by QEMU (when
the capability is available).
A memfd is a specialized anonymous memory kind. As such, an anonymous
source type could be automatically using a memfd. However, there are
some complications when migrating
From: Marc-André Lureau
Hi,
This is an alternative series from "[PATCH 0/5] Use memfd if
possible". Instead of automatically using memfd for anonymous memory
when available (as suggested by Daniel), it introduces the "memfd"
memory backing type.
Although using memfd transparently when possible
From: Marc-André Lureau
Check availability of "-object memory-backend-memfd".
Reviewed-by: John Ferlan
Signed-off-by: Marc-André Lureau
Signed-off-by: John Ferlan
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
> -Original Message-
> From: John Ferlan [mailto:jfer...@redhat.com]
> Sent: Thursday, November 15, 2018 12:18 AM
> To: Wang, Huaqiang ; libvir-list@redhat.com
> Cc: Feng, Shaohe ; Ding, Jian-feng feng.d...@intel.com>; Zang, Rui
> Subject: Re: [PATCHv8 16/17] qemu: Report cache
> -Original Message-
> From: John Ferlan [mailto:jfer...@redhat.com]
> Sent: Thursday, November 15, 2018 12:19 AM
> To: Wang, Huaqiang ; libvir-list@redhat.com
> Cc: Feng, Shaohe ; Ding, Jian-feng feng.d...@intel.com>; Zang, Rui
> Subject: Re: [PATCHv8 17/17] docs: Updated news.xml
> -Original Message-
> From: John Ferlan [mailto:jfer...@redhat.com]
> Sent: Thursday, November 15, 2018 12:19 AM
> To: Wang, Huaqiang ; libvir-list@redhat.com
> Cc: Feng, Shaohe ; Ding, Jian-feng feng.d...@intel.com>; Zang, Rui
> Subject: Re: [PATCHv8 2/2] tools: Add help docs
On Thu, 2018-11-15 at 10:17 +, Daniel P. Berrangé wrote:
> On Tue, Nov 13, 2018 at 03:35:43PM +0100, Andrea Bolognani wrote:
> > Dan, do you have any remaining concerns about the XML syntax, or can
> > I go ahead and push?
>
> Honestly, I still don't much like it & would prefer zpci as a top
On 11/15/18 1:12 PM, Andrea Bolognani wrote:
On Thu, 2018-11-15 at 10:17 +, Daniel P. Berrangé wrote:
On Tue, Nov 13, 2018 at 03:35:43PM +0100, Andrea Bolognani wrote:
Dan, do you have any remaining concerns about the XML syntax, or can
I go ahead and push?
Honestly, I still don't much
57 matches
Mail list logo
