Random write IOPS will drop dramatically if qcow2 l2 cache could not
cover the whole disk. This patch gives libvirt user a chance to adjust
the qcow2 cache configuration.
Three new qcow2 driver parameters (l2-cache-size, refcount-cache-size
and cache-clean-interval) are added as attributes to a
Add qemu capabilities QEMU_CAPS_L2_CACHE_SIZE,
QEMU_CAPS_REFCOUNT_CACHE_SIZE, QEMU_CAPS_CACHE_CLEAN_INTERVAL.
Add testing for the above qemu capabilities.
Signed-off-by: Liu Qing
---
src/qemu/qemu_capabilities.c | 11
Qcow2 small IO random write performance will drop dramatically if the l2
cache table could not cover the whole disk. This will be a lot of l2
cache table RW operations if cache miss happens frequently.
This patch exports the qcow2 driver parameter
l2-cache-size/refcount-cache-size, first added
On Wed, Sep 13, 2017 at 01:20:03PM +0200, Peter Krempa wrote:
> On Wed, Sep 13, 2017 at 17:21:23 +0800, Liu Qing wrote:
> > Random write IOPS will drop dramatically if qcow2 l2 cache could not
> > cover the whole disk. This patch gives libvirt user a chance to adjust
> > the qcow2 cache
On Tue, Sep 12, 2017 at 05:21:53PM -0400, John Ferlan wrote:
>
>
> On 09/07/2017 02:09 AM, Liu Qing wrote:
> > Random write IOPS will drop dramatically if qcow2 l2 cache could not
> > cover the whole disk. This patch gives libvirt user a chance to adjust
> > the qcow2 cache configuration.
> >
>
On Wed, Sep 13, 2017 at 06:51:35AM -0400, John Ferlan wrote:
>
>
> On 09/13/2017 05:21 AM, Liu Qing wrote:
> > Qcow2 small IO random write performance will drop dramatically if the l2
> > cache table could not cover the whole disk. This will be a lot of l2
> > cache table RW operations if cache
On 09/13/17 17:28 +0200, Michal Privoznik wrote:
>
> BTW: I ran a migration from no nvdimm qemu to one that had -M nvdimm=on
> and guest migrated happily. So looks like guest ABI is stable (or at
> least stable enough not to crash). But since ACPI table is changed I
> doubt that.
One example
On 09/12/2017 01:56 PM, ashish mittal wrote:
> Hi,
>
> Updating the list with some test results of the base VxHS functionality
> (without TLS), and some changes resulting therefrom -
>
> (A) Qemu did not work with the
> changed file.server.0.host=127.0.0.1 syntax. Threw an error "Parameter
>
On 09/13/2017 06:47 AM, Michal Privoznik wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1075520
>
> Apart from generic checks, we need to constrain netmask/prefix
> lenght a bit. Thing is, with current implementation QEMU needs to
s/lenght/length/
> be able to 'assign' some IP addresses to
On 09/13/2017 06:47 AM, Michal Privoznik wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1075520
>
> Currently, all that users can specify for an interface type of
> 'user' is the common attributes: PCI address, NIC model (and
> that's basically it). However, some need to configure other
>
On 09/13/2017 06:46 AM, Michal Privoznik wrote:
> On 09/12/2017 09:16 PM, Laine Stump wrote:
>> On 09/12/2017 05:32 AM, Michal Privoznik wrote:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1075520
>>>
>>> +/* QEMU needs some space to have
>>> + * some other
On Wed, Sep 13, 2017 at 01:57:44PM +0100, Dean Smith wrote:
> *** BLURB HERE ***
> I have taken Anton Kryukovs fix from #13 on github and am submitting
> along with addition of 1.8 and 1.9 as travis go version targets
>
> Example of failing running on 1.9, which passes on 1.7 can be found
> at
>
On 09/13/2017 03:54 PM, Stefan Hajnoczi wrote:
> Hi Michal,
> You asked how NVDIMM hotplug should work if the domain was launched
> without -M nvdimm=on. I'm not very familiar with ACPI so this may be
> incorrect.
>
> Hotplug relies on the presence of ACPI tables (SSDT Device=NVDR
>
On 09/13/2017 08:52 AM, Peter Krempa wrote:
> Drop all the monitor code necessary to do the downstream block jobs.
> ---
> src/qemu/qemu_driver.c | 7 +++
> src/qemu/qemu_migration.c| 2 +-
> src/qemu/qemu_monitor.c | 24 ++--
> src/qemu/qemu_monitor.h
On 09/13/2017 08:52 AM, Peter Krempa wrote:
> Interrestingly, none of the qemus we have caps for supported it ...
s/Interrestingly/Interestingly/
> ---
> src/qemu/qemu_capabilities.c | 1 -
> src/qemu/qemu_capabilities.h | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
Reviewed-by:
On 09/13/2017 08:52 AM, Peter Krempa wrote:
> Block job QMP commands with underscores rather than dashes were never
> released in upstream qemu, (they were added, but modified in the same
> release [1]), but a certain distro managed to backport the version in the
> middle.
I find it fine that you
Block job QMP commands with underscores rather than dashes were never
released in upstream qemu, (they were added, but modified in the same
release [1]), but a certain distro managed to backport the version in the
middle.
The change also slightly modified semantics for the abort command, which
Hi Michal,
You asked how NVDIMM hotplug should work if the domain was launched
without -M nvdimm=on. I'm not very familiar with ACPI so this may be
incorrect.
Hotplug relies on the presence of ACPI tables (SSDT Device=NVDR
_HID=ACPI0012) added by -M nvdimm=on. The ACPI tables contain the
Drop all the monitor code necessary to do the downstream block jobs.
---
src/qemu/qemu_driver.c | 7 +++
src/qemu/qemu_migration.c| 2 +-
src/qemu/qemu_monitor.c | 24 ++--
src/qemu/qemu_monitor.h | 9 +++--
src/qemu/qemu_monitor_json.c | 17
See patch 1/3
Peter Krempa (3):
qemu: Remove support for legacy block jobs
qemu: monitor: Remove support for "legacy" block jobs
qemu: caps: Deprecate QEMU_CAPS_BLOCKJOB_SYNC
src/qemu/qemu_capabilities.c | 1 -
src/qemu/qemu_capabilities.h | 2 +-
src/qemu/qemu_domain.c | 13
On Wed, Sep 13, 2017 at 03:24:42PM +0200, Peter Krempa wrote:
> On Wed, Sep 13, 2017 at 09:05:43 -0400, John Ferlan wrote:
> >
> > I was thinking more about virstoragefile.c and virstoragetest.c. It's
> > easy enough to fetch the user/password-secret in
> > virStorageSourceParseBackingJSONiSCSI:
---
.travis.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 5e6be77..dd13140 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -6,6 +6,8 @@ go:
- 1.5
- 1.6
- 1.7
+ - 1.8
+ - 1.9
script:
go test -timeout 1m -v
--
1.8.3.1
--
libvir-list
Interrestingly, none of the qemus we have caps for supported it ...
---
src/qemu/qemu_capabilities.c | 1 -
src/qemu/qemu_capabilities.h | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c
index e7ea6f47c..c690cb349
*** BLURB HERE ***
I have taken Anton Kryukovs fix from #13 on github and am submitting
along with addition of 1.8 and 1.9 as travis go version targets
Example of failing running on 1.9, which passes on 1.7 can be found
at
g...@github.com:deasmi/libvirt-go-xml.git
branch parsefailtest
Anton
From: Anton Kryukov
Add support for hex values in DomainAddress struct
Tests fixed for HexUint
>From PR#13 https://github.com/libvirt/libvirt-go-xml/pull/13
on github by Emreu
@deasmi submitting via mail
---
domain.go | 27 ++-
domain_test.go |
On Wed, Sep 13, 2017 at 09:05:43 -0400, John Ferlan wrote:
>
>
> On 09/13/2017 03:08 AM, Peter Krempa wrote:
> > On Tue, Sep 12, 2017 at 11:55:29 -0400, John Ferlan wrote:
> >>
> >>
> >> On 09/12/2017 09:36 AM, Peter Krempa wrote:
> >>> On Tue, Sep 05, 2017 at 15:09:35 -0400, John Ferlan wrote:
On 09/13/2017 03:08 AM, Peter Krempa wrote:
> On Tue, Sep 12, 2017 at 11:55:29 -0400, John Ferlan wrote:
>>
>>
>> On 09/12/2017 09:36 AM, Peter Krempa wrote:
>>> On Tue, Sep 05, 2017 at 15:09:35 -0400, John Ferlan wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1425757
The
On Tue, 2017-09-12 at 12:37 -0400, Cole Robinson wrote:
> Signed-off-by: Cole Robinson
> ---
> docs/news.xml | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/docs/news.xml b/docs/news.xml
> index 483f9d6d1..17f00a25e 100644
> --- a/docs/news.xml
> +++
Available since QEMU 2.10.0 (specifically commit
v2.9.0-2233-g53f9a6f45f).
Signed-off-by: Jiri Denemark
---
src/cpu/cpu_map.xml| 75 ++
.../x86_64-cpuid-Xeon-Gold-6148-guest.xml | 9 +--
Signed-off-by: Jiri Denemark
---
tests/cputest.c| 1 +
.../x86_64-cpuid-Xeon-Gold-6148-disabled.xml | 7 +
.../x86_64-cpuid-Xeon-Gold-6148-enabled.xml| 9 +
.../x86_64-cpuid-Xeon-Gold-6148-guest.xml | 35 +++
The features were added to QEMU by commit v2.4.0-1690-gf7fda28094 as
Skylake Server features.
Signed-off-by: Jiri Denemark
---
src/cpu/cpu_map.xml | 6 ++
tests/cputestdata/x86_64-cpuid-Xeon-Gold-6148-guest.xml | 1 +
Jiri Denemark (3):
tests: Add CPUID data for Intel(R) Xeon(R) Gold 6148 CPU
cpu: Add clwb/pcommit CPU features
cpu: Add new Skylake-Server CPU model
src/cpu/cpu_map.xml| 81 +++
tests/cputest.c| 1 +
On Wed, Sep 13, 2017 at 17:21:23 +0800, Liu Qing wrote:
> Random write IOPS will drop dramatically if qcow2 l2 cache could not
> cover the whole disk. This patch gives libvirt user a chance to adjust
> the qcow2 cache configuration.
>
> Three new qcow2 driver parameters are added. They are
On 09/13/2017 05:21 AM, Liu Qing wrote:
> Qcow2 small IO random write performance will drop dramatically if the l2
> cache table could not cover the whole disk. This will be a lot of l2
> cache table RW operations if cache miss happens frequently.
>
> This patch exports the qcow2 driver
https://bugzilla.redhat.com/show_bug.cgi?id=1075520
Apart from generic checks, we need to constrain netmask/prefix
lenght a bit. Thing is, with current implementation QEMU needs to
be able to 'assign' some IP addresses to the virtual network. For
instance, the default gateway is at x.x.x.2, dns
https://bugzilla.redhat.com/show_bug.cgi?id=1075520
Currently, all that users can specify for an interface type of
'user' is the common attributes: PCI address, NIC model (and
that's basically it). However, some need to configure other
address range than the default one.
Signed-off-by: Michal
diff to v1:
- moved the directly under
- enhanced the test
- tuned some error messages
Michal Privoznik (2):
conf: Allow usernet to have an address
qemu: Implement usernet address
docs/formatdomain.html.in | 8 +++-
src/qemu/qemu_command.c
On 09/12/2017 09:16 PM, Laine Stump wrote:
> On 09/12/2017 05:32 AM, Michal Privoznik wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1075520
>>
>> Apart from generic checks, we need to constrain netmask/prefix
>> lenght a bit. Thing is, with current implementation QEMU needs to
>> be able
Add qemu capabilities QEMU_CAPS_L2_CACHE_SIZE,
QEMU_CAPS_REFCOUNT_CACHE_SIZE, QEMU_CAPS_CACHE_CLEAN_INTERVAL.
Add testing for the above qemu capabilities.
Signed-off-by: Liu Qing
---
src/qemu/qemu_capabilities.c | 9 +
src/qemu/qemu_capabilities.h
Qcow2 small IO random write performance will drop dramatically if the l2
cache table could not cover the whole disk. This will be a lot of l2
cache table RW operations if cache miss happens frequently.
This patch exports the qcow2 driver parameter
l2-cache-size/refcount-cache-size, first added
On 09/13/2017 09:52 AM, Peter Krempa wrote:
> On Wed, Sep 13, 2017 at 09:30:45 +0200, Michal Privoznik wrote:
>> The documentation mistakenly states that the unit for returned
>> values is kB (multiple of 1000), while in fact we are returning
>> KiB (multiple of 1024).
>>
>> Signed-off-by: Michal
Random write IOPS will drop dramatically if qcow2 l2 cache could not
cover the whole disk. This patch gives libvirt user a chance to adjust
the qcow2 cache configuration.
Three new qcow2 driver parameters are added. They are l2-cache-size,
refcount-cache-size and cache-clean-interval.
The
On 09/12/2017 07:35 PM, Laine Stump wrote:
> On 09/12/2017 05:53 AM, Martin Kletzander wrote:
>> On Tue, Sep 12, 2017 at 11:32:52AM +0200, Michal Privoznik wrote:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1075520
>>>
>>> Currently, all that users can specify for an interface type of
>>>
On Wed, Sep 13, 2017 at 09:30:45 +0200, Michal Privoznik wrote:
> The documentation mistakenly states that the unit for returned
> values is kB (multiple of 1000), while in fact we are returning
> KiB (multiple of 1024).
>
> Signed-off-by: Michal Privoznik
> ---
>
> Oops, I
On Wed, Aug 30, 2017 at 15:48:37 -0400, John Ferlan wrote:
> No need to pass a @driver parameter since all that's done is deref
> the @cfg especially since the only caller can just pass an already
> referenced @cfg.
>
> Also, looks like commit id '0298531b' at one time had a different
> name for
On Tue, Sep 12, 2017 at 20:49:12 +0300, Khasan Khafizov wrote:
> Suppose we have a disk with several external snapshots of it. This disk is
> attached to some domain. I found that after destroying and starting the
> domain the xml of attached disk doesn't contain all backingStore that it
> has to.
On Tue, Sep 12, 2017 at 01:35:08PM -0400, Laine Stump wrote:
On 09/12/2017 05:53 AM, Martin Kletzander wrote:
On Tue, Sep 12, 2017 at 11:32:52AM +0200, Michal Privoznik wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1075520
Currently, all that users can specify for an interface type of
The documentation mistakenly states that the unit for returned
values is kB (multiple of 1000), while in fact we are returning
KiB (multiple of 1024).
Signed-off-by: Michal Privoznik
---
Oops, I forgot to send this one,
tools/virsh.pod | 30 +++---
On Tue, Sep 12, 2017 at 11:55:29 -0400, John Ferlan wrote:
>
>
> On 09/12/2017 09:36 AM, Peter Krempa wrote:
> > On Tue, Sep 05, 2017 at 15:09:35 -0400, John Ferlan wrote:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1425757
> >>
> >> The blockdev-add code provides a mechanism to sanely
49 matches
Mail list logo