On 2017年01月04日 11:26, Jason Wang wrote:
On 2017年01月04日 00:27, Michael S. Tsirkin wrote:
On Tue, Jan 03, 2017 at 06:28:18PM +0800, Jason Wang wrote:
On 2017年01月03日 11:09, Jason Wang wrote:
On 2016年12月30日 20:41, Flavio Leitner wrote:
Hi,
While I was testing vhost-user using OVS 2.5 and D
In order to reduce the execution time, this patch optimize
the qmp_query_blockstats():
Remove the next_query_bds function.
Remove the bdrv_query_stats function.
Remove some judgement sentence.
The original qmp_query_blockstats calls next_query_bds to get
the next objects in each loops. In the next
the bdrv_query_stats and bdrv_query_bds_stats functions need to call
each other, that increases the coupling. it also makes the program
complicated and makes some unnecessary judgements.
remove the call from bdrv_query_bds_stats to bdrv_query_stats, just
take some recursion to make it clearly.
av
Change log v2 -> v3:
1. Remove the unnecessary code for the bdrv_next_node().
2. Remove the change of the locking rules.
Even if this change can improve the performance, but it may
effect the consistency.
For the multi-disks guest, we can use the dataplane feature to
hold performance doe
On 03.01.2017 18:11, Sean Bruno wrote:
>
>
> On 01/03/17 09:18, Sean Bruno wrote:
>>
>> I'm pondering where to start with getting FreeBSD's bsd-user code into
>> shape so it could actually be reviewed and accepted now that its sort of
>> working again (signal handling fixed finally).
>>
>> I almo
On Fri, Dec 16, 2016 at 4:07 PM, Greg Kurz wrote:
> On Fri, 16 Dec 2016 15:23:43 +0530
> Ashijeet Acharya wrote:
>
>> If a migration is already in progress and somebody attempts
>> to add a migration blocker, this should rightly fail.
>>
>> Add an errp parameter and a retcode return value to migr
On Thu, 2016-12-15 at 16:48 +1100, Alastair D'Silva wrote:
> > From: Alastair D'Silva
>
> Connect an RX8900 RTC to i2c12 of the AST2500 SOC at address 0x32
>
> > Signed-off-by: Alastair D'Silva
> Signed-off-by: Chris Smart
Reviewed-by: Andrew Jeffery
> ---
> hw/arm/aspeed.c | 29 ++
Hi Alastair,
Again, small comments below.
On Thu, 2016-12-15 at 16:48 +1100, Alastair D'Silva wrote:
> > From: Alastair D'Silva
>
> > Signed-off-by: Alastair D'Silva
> ---
> tests/Makefile.include | 2 +
> tests/rx8900-test.c| 882
> +
>
On Wed, 2017-01-04 at 15:29 +1030, Andrew Jeffery wrote:
> Hi Alastair,
>
> I have some mostly minor comments below.
Ok, I'm removing Chris from the CC list since he's left the team.
>
> On Thu, 2016-12-15 at 16:48 +1100, Alastair D'Silva wrote:
> > > From: Alastair D'Silva
> >
> > This patc
Hi Alastair,
I have some mostly minor comments below.
On Thu, 2016-12-15 at 16:48 +1100, Alastair D'Silva wrote:
> > From: Alastair D'Silva
>
> This patch adds support for the Epson RX8900 I2C RTC.
>
> The following chip features are implemented:
> - RTC (wallclock based, ptimer 10x oversampl
From: Li Qiang
On error path, the 'salt' doesn't been freed thus leading
a memory leak. This patch avoid this.
Signed-off-by: Li Qiang
---
crypto/ivgen-essiv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/crypto/ivgen-essiv.c b/crypto/ivgen-essiv.c
index 634de63..cba20bd 100644
--- a/cr
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1317603
Ti
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1119686
Title:
Incorrect h
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/322602
Title:
Snapshot usa
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/809912
Title:
qemu-kvm -m
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/441672
Title:
Windos XP BS
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/612297
Title:
qemu-kvm fai
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/590552
Title:
New default
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1102027
Title:
QED Time tr
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1639225
Title:
qcow2 - fil
On Tue, Jan 03, 2017 at 10:02:21PM +0800, 赵小强 wrote:
> Hi，david：
>
>To my understanding，what must be put in the realize function is
>code which depends on property values. What's the benefit of
>moving memory region initialization into realize function? I can
>not figure out, can
On Wed, Dec 21, 2016 at 03:07:07PM +0100, Paolo Bonzini wrote:
>
>
> On 29/11/2016 12:32, Paolo Bonzini wrote:
> > Cleaning up the code and removing duplication makes it simpler to
> > later adapt it for the multiqueue work.
> >
> > Tested against sheepdog 1.0. I also tested taking snapshots an
On 2017年01月04日 00:27, Michael S. Tsirkin wrote:
On Tue, Jan 03, 2017 at 06:28:18PM +0800, Jason Wang wrote:
On 2017年01月03日 11:09, Jason Wang wrote:
On 2016年12月30日 20:41, Flavio Leitner wrote:
Hi,
While I was testing vhost-user using OVS 2.5 and DPDK 2.2.0 in the
host and testpmd dpdk 2.2.
From: Caoxinhua
QEMU will crash with the follow backtrace if the new created thread exited
before
we call qemu_thread_set_name() for it.
(gdb) bt
#0 0x7f9a68b095d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7f9a68b0acc8 in __GI_abort () at
Oops, I deleted the original title carelessly, will send V2. Thanks.
On 2017/1/4 0:06, Stefan Hajnoczi wrote:
Please follow the conventions for commit messages. QEMU commit messages
start with a prefix that identifies the affected component.
(Use git-log(1) to check what prefix other people h
Hi Stefan,
>
> Subject: Re: [Qemu-devel] [PATCH v14 0/2] virtio-crypto: virtio crypto device
> specification
>
> On Mon, Dec 26, 2016 at 02:38:29AM +, Gonglei (Arei) wrote:
> > Both Alex and Stefan mentioned that the process of create/close a session
> > makes we have a least one full round-t
On Tue, 27 Dec 2016, Zhang Chen wrote:
> We can call this qmp command to start/stop replication outside of qemu.
> Like Xen colo need this function.
>
> Signed-off-by: Zhang Chen
> Signed-off-by: Wen Congyang
> Reviewed-by: Eric Blake
Reviewed-by: Stefano Stabellini
> ---
> docs/qmp-comman
On Tue, Jan 03, 2017 at 11:37:20PM +0100, Hervé Poussineau wrote:
> Le 03/01/2017 à 00:02, David Gibson a écrit :
> > On Thu, Dec 29, 2016 at 11:12:12PM +0100, Hervé Poussineau wrote:
> > > VGA device registers vram as BAR 0. If this BAR is activated as a very
> > > low address which
> > > crosses
On Tue, Jan 03, 2017 at 11:51:27PM +0100, Hervé Poussineau wrote:
> Le 03/01/2017 à 00:03, David Gibson a écrit :
> > On Thu, Dec 29, 2016 at 11:12:14PM +0100, Hervé Poussineau wrote:
> > > Part of the functionality is copied from hw/ppc/prep.c.
> > > Also add support for board identification/equip
On Tue, Jan 03, 2017 at 11:55:10PM +0100, Hervé Poussineau wrote:
> Le 03/01/2017 à 05:57, David Gibson a écrit :
> > On Thu, Dec 29, 2016 at 11:12:15PM +0100, Hervé Poussineau wrote:
> > > Signed-off-by: Hervé Poussineau
> > > ---
> > > default-configs/ppc-softmmu.mak | 1 +
> > > hw/ppc/Makef
Le 03/01/2017 à 05:57, David Gibson a écrit :
On Thu, Dec 29, 2016 at 11:12:15PM +0100, Hervé Poussineau wrote:
Signed-off-by: Hervé Poussineau
---
default-configs/ppc-softmmu.mak | 1 +
hw/ppc/Makefile.objs| 1 +
hw/ppc/rs6000_mc.c | 232 ++
Le 03/01/2017 à 00:03, David Gibson a écrit :
On Thu, Dec 29, 2016 at 11:12:14PM +0100, Hervé Poussineau wrote:
Part of the functionality is copied from hw/ppc/prep.c.
Also add support for board identification/equipment registers.
Needs more detail in the commit message. What is system I/O?
Le 03/01/2017 à 00:02, David Gibson a écrit :
On Thu, Dec 29, 2016 at 11:12:12PM +0100, Hervé Poussineau wrote:
VGA device registers vram as BAR 0. If this BAR is activated as a very low
address which
crosses 0xa-0xb, low memory region is not accessible anymore.
This fixes display on P
On Tue, Jan 03, 2017 at 03:33:12PM -0200, Flavio Leitner wrote:
> On Tue, 3 Jan 2017 18:28:18 +0800
> Jason Wang wrote:
>
> > On 2017年01月03日 11:09, Jason Wang wrote:
> > >
> > >
> > > On 2016年12月30日 20:41, Flavio Leitner wrote:
> > >> Hi,
> > >>
> > >> While I was testing vhost-user using OVS 2
On Mon, 26 Dec 2016 10:45:55 +0800
Jason Wang wrote:
> On 2016年12月23日 11:26, Peter Xu wrote:
> > On Thu, Dec 22, 2016 at 07:34:10PM +0800, Jason Wang wrote:
> >>
> >> On 2016年12月22日 19:04, Peter Xu wrote:
> >>> On Thu, Dec 22, 2016 at 05:52:58PM +0800, Jason Wang wrote:
> On 2016年12月22
Signed-off-by: Jean-Christophe Dubois
---
hw/block/m25p80.c | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c
index d29ff4c..6c374cf 100644
--- a/hw/block/m25p80.c
+++ b/hw/block/m25p80.c
@@ -28,6 +28,7 @@
#include "hw/
The i.MX SPI device was not de-asserting the CS line at the end of
memory access.
This triggered a SIGSEGV in Qemu when the sabrelite emulator was acessing
a SPI flash memory.
Whit this path the CS signal is correctly asserted and deasserted arround
memory access.
Assertion level is now based on
Le 03/01/2017 à 18:08, mar.krzeminski a écrit :
You may still want to harden the m25p80 code to make sure it doesn't
overrun its internal buffer.
Yeap, for me it is a bug.
I understand you will not finish this patch, won't you ?:)
I could give it a shot.
JC
On 01/03/2017 12:27 PM, Daniel P. Berrange wrote:
> The block/crypto.c defines a set of QemuOpts that provide
> parameters for encryption. This will also be needed by
> the qcow/qcow2 integration, so expose the relevant pieces
> in a new block/crypto.h header.
>
> Signed-off-by: Daniel P. Berrange
On 01/03/17 20:19, Marc-André Lureau wrote:
A fix has been committed in upstream glib commit
210a9796f78eb90f76f1bd6a304e9fea05e97617.
(See also related bug https://bugzilla.gnome.org/show_bug.cgi?id=764415)
It is desirable to use the glib version instead of qemu copy, since it
provides more deb
* Dmitry Fleytman (dmi...@daynix.com) wrote:
> >
> > On 16 Dec 2016, at 14:19 PM, Dr. David Alan Gilbert
> > wrote:
> >
> > * Dr. David Alan Gilbert (git) (dgilb...@redhat.com) wrote:
> >> From: "Dr. David Alan Gilbert"
> >>
> >> Fairly simple mechanical conversion of all fields.
> >>
> >> T
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> On some distros, whenever you close a block device file
> descriptor there is a udev rule that resets the file
> permissions. This can race with the test script when
> we run qemu-io multiple times against the same block
> device. Occassionally th
A fix has been committed in upstream glib commit
210a9796f78eb90f76f1bd6a304e9fea05e97617.
(See also related bug https://bugzilla.gnome.org/show_bug.cgi?id=764415)
It is desirable to use the glib version instead of qemu copy, since it
provides more debugging facilities (G_MAIN_POLL_DEBUG etc), and
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> Add tests for sha224, sha512, sha384 and ripemd160 hash
> algorithms.
>
> Signed-off-by: Daniel P. Berrange
> ---
> tests/qemu-iotests/149 | 10 +-
> tests/qemu-iotests/149.out | 482
> -
> 2 fi
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> By default the PBKDF algorithm used with LUKS is tuned
> based on the number of iterations to produce 1 second
> of running time. This makes running the I/O test with
> the LUKS format orders of magnitude slower than with
> qcow2/raw formats.
>
>
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> By default the PBKDF algorithm used with LUKS is tuned
> based on the number of iterations to produce 1 second
> of running time. This makes running the I/O test with
> the LUKS format orders of magnitude slower than with
> qcow2/raw formats.
>
>
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> The tests 033, 120, 140, 145 and 157 were all broken
> when run with LUKS, since they did not correctly use
> the required image opts args syntax to specify the
> decryption secret.
>
> Signed-off-by: Daniel P. Berrange
> ---
> +++ b/tests/qemu
Hi
On Tue, Jun 14, 2016 at 6:34 PM Daniel P. Berrange
wrote:
> The g_test_trap_subprocess() method does not work on the
> Mingw32 platform, causing the test-qdev-global-props
> test case to abort
>
> (test-logging.exe:230): GLib-ERROR **: g_test_trap_subprocess()
> failed: Failed to execute help
The 138 and 158 iotests exercise the legacy qcow2 aes encryption
code path. With a few simple tweaks they can exercise the same
feature in qcow (v1).
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/134 | 10 +-
tests/qemu-iotests/158 | 2 +-
2 files changed, 6 insertions(+), 6
The previous commit:
commit a3e1505daec31ef56f0489f8c8fff1b8e4ca92bd
Author: Eric Blake
Date: Mon Dec 5 09:49:34 2016 -0600
qcow2: Don't strand clusters near 2G intervals during commit
extended the 097 test case so that it did two passes, once
with an internal snapshot, once without
Now that all encryption keys must be provided upfront via
the QCryptoSecret API and associated block driver properties
there is no need for any explicit encryption handling APIs
in the block layer. Encryption can be handled transparently
within the block driver. We only retain an API for querying
w
Test 048 is designed to verify data preservation during an
image resize. The qcow (v1) format impl has never supported
resize so always fails.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/048 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/048 b
Instead of requiring separate input/output buffers for
encrypting data, change encrypt_sectors() to assume
use of a single buffer, encrypting in place. One current
caller all uses the same buffer for input/output already
and the other two callers are easily converted todo so.
Signed-off-by: Daniel
Now that qcow & qcow2 are wired up to get encryption keys
via the QCryptoSecret object, nothing is relying on the
interactive prompting for passwords. All the code related
to password prompting can thus be ripped out.
Signed-off-by: Daniel P. Berrange
---
hmp.c | 31 -
This adds support for using LUKS as an encryption format
with the qcow2 file. The use of the existing 'encryption=on'
parameter is replaced by a new parameter 'encryption-format'
which takes the values 'aes' or 'luks'. e.g.
# qemu-img create --object secret,data=123456,id=sec0 \
-f qcow2
Instead of requiring separate input/output buffers for
encrypting data, change qcow2_encrypt_sectors() to assume
use of a single buffer, encrypting in place. The current
callers all used the same buffer for input/output already.
Reviewed-by: Eric Blake
Reviewed-by: Fam Zheng
Signed-off-by: Danie
This converts the qcow2 driver to make use of the QCryptoBlock
APIs for encrypting image content, using the legacyy QCow2 AES
scheme.
With this change it is now required to use the QCryptoSecret
object for providing passwords, instead of the current block
password APIs / interactive prompting.
This converts the qcow2 driver to make use of the QCryptoBlock
APIs for encrypting image content. This is only wired up to
permit use of the legacy QCow encryption format. Users who wish
to have the strong LUKS format should switch to qcow2 instead.
With this change it is now required to use the Q
Test 042 is designed to verify operation with zero sized images.
Such images are not supported with qcow (v1), so this test has
always failed.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/042 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/042 b
Document that use of guest virtual sector numbers as the basis for
the initialization vectors is a potential weakness, when combined
with internal snapshots or multiple images using the same passphrase.
Signed-off-by: Daniel P. Berrange
---
qemu-img.texi | 9 +
1 file changed, 9 insertio
The qcow driver refuses to open images which are less than
2 bytes in size, but will happily create such images. Add
a check in the create path to avoid this discrepancy.
Signed-off-by: Daniel P. Berrange
---
block/qcow.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/block/qcow.c b/b
This series is a continuation of previous work to support LUKS in
QEMU. The existing merged code supports LUKS as a standalone
driver which can be layered over/under any other QEMU block device
driver. This works well when using LUKS over protocol drivers (file,
rbd, iscsi, etc, etc), but has some
When integrating the crypto support with qcow/qcow2, we don't
want to use the bare LUKS option names "hash-alg", "key-secret",
etc. We want to namespace them "luks-hash-alg", "luks-key-secret"
so that they don't clash with any general qcow options at a later
date.
Signed-off-by: Daniel P. Berrange
The block/crypto.c defines a set of QemuOpts that provide
parameters for encryption. This will also be needed by
the qcow/qcow2 integration, so expose the relevant pieces
in a new block/crypto.h header.
Signed-off-by: Daniel P. Berrange
---
block/crypto.c | 61 +++
This allows running big endian and little endian guest side by side using
cut & paste between them.
There is a general design idea that swapping should come as close to
virtio_read/virtio_write as possible. In particular, the protocol
between vdagent and vdagentd is guest-specific and in native en
Signed-off-by: Michal Suchanek
---
src/vdagentd/vdagentd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/vdagentd/vdagentd.c b/src/vdagentd/vdagentd.c
index 991514e..60a866e 100644
--- a/src/vdagentd/vdagentd.c
+++ b/src/vdagentd/vdagentd.c
@@ -334,6 +334,7 @@ static void do_client_file
On 01/03/17 09:18, Sean Bruno wrote:
>
> I'm pondering where to start with getting FreeBSD's bsd-user code into
> shape so it could actually be reviewed and accepted now that its sort of
> working again (signal handling fixed finally).
>
> I almost feel like the existing code should be purged,
On Tue, 3 Jan 2017 18:28:18 +0800
Jason Wang wrote:
> On 2017年01月03日 11:09, Jason Wang wrote:
> >
> >
> > On 2016年12月30日 20:41, Flavio Leitner wrote:
> >> Hi,
> >>
> >> While I was testing vhost-user using OVS 2.5 and DPDK 2.2.0 in the
> >> host and testpmd dpdk 2.2.0 in the guest, I found that
On 01/03/2017 11:04 AM, Daniel P. Berrange wrote:
> While the qemu-img dd command does accept --image-opts
> this is not sufficient to make it work with the LUKS
> image yet. This is because bdrv_create() still always
> requires the non-image-opts syntax.
>
> Thus we must skip 159/170 with luks fo
On 01/03/2017 10:05 AM, Daniel P. Berrange wrote:
> The 'check' program records timings for each test that
> is run. These timings are only valid, however, for a
> particular format/protocol combination. So if frequently
> running 'check' with a variety of different formats or
> protocols, the time
By default the PBKDF algorithm used with LUKS is tuned
based on the number of iterations to produce 1 second
of running time. This makes running the I/O test with
the LUKS format orders of magnitude slower than with
qcow2/raw formats.
When creating LUKS images, set the iteration time to
a 10ms to
On Tue, 3 Jan 2017 09:34:40 -0600
Eric Blake wrote:
> On 01/02/2017 09:44 AM, Igor Mammedov wrote:
>
> s/repporting/reporting/ in the subject
>
> > Do it by adding 'id' property to hostmem backends and fetch it
> > in query-memdev from object directly.
> >
> > Signed-off-by: Igor Mammedov
> >
The direction is wrong; scsi_block_is_passthrough returns
false for commands that *can* use sglists.
Reported-by: Zhang Qian
Fixes: 8fdc7839e40f43a426bc7e858cf1dbfe315a3804
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-disk.c | 2 +-
1 file changed, 1 insertion(+), 1
Add tests for sha224, sha512, sha384 and ripemd160 hash
algorithms.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/149 | 10 +-
tests/qemu-iotests/149.out | 482 -
2 files changed, 484 insertions(+), 8 deletions(-)
diff --git a/tests/qe
Hello JC,
W dniu 02.01.2017 o 22:11, Jean-Christophe Dubois pisze:
The i.MX SPI device was not de-asserting the CS line at the end of
memory access.
This triggered a SIGSEGV in Qemu when the sabrelite emulator was acessing
a SPI flash memory.
Whit this path the CS signal is correctly asserted
On 03/01/2017 10:58, Zhang Qian wrote:
>
> At 2017-01-03 17:38:49, Paolo Bonzini wrote:
>>
>>
>>On 03/01/2017 09:12, Zhang Qian wrote:
>>> yes, you are right.
>>> The scenarios of problem is
>>> a scsi-disk object receives VERIFY command with BYTCHK bit being zero,
>>> scsi_block_is_passthrough
W dniu 02.01.2017 o 22:24, Jean-Christophe DUBOIS pisze:
Le 30/12/2016 à 19:09, mar.krzeminski a écrit :
Can you check spi controller model code?
I'll double check.
But why is the SPI memory/device even responding if CS is not set ?
Looking at ssi code it should not.
Flash (so the m25p80)
The tests 033, 120, 140, 145 and 157 were all broken
when run with LUKS, since they did not correctly use
the required image opts args syntax to specify the
decryption secret.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/033 | 16
tests/qemu-iotests/120 | 25
(CCing libvir-list and Laine)
On Tue, Jan 03, 2017 at 05:53:27PM +0100, Igor Mammedov wrote:
> On Tue, 3 Jan 2017 17:10:15 +0100
> Paolo Bonzini wrote:
>
> >
> >
> > On 03/01/2017 15:22, Eduardo Habkost wrote:
> > >> I didn't know that. Is this documented somewhere?
> > >> Is it actually used
The main goal of this series is to get the I/O tests passing
100% with LUKS when run with './check -luks'. It also adds a
few more combinations to the LUKS/dmcrypt interoperability
test.
To make LUKS testing not quite as slow, we drop the PBKDF
iteration count down to a very small value. This does
On 01/03/2017 11:00 AM, Daniel P. Berrange wrote:
> The qemu-img dd command added --image-opts support, but missed
> the corresponding --object support. This prevented passing
> secrets (eg auth passwords) needed by certain disk images.
>
> Signed-off-by: Daniel P. Berrange
> ---
> qemu-img.c |
Hi Stefan,
Thanks for your reply.
On Tue, Jan 3, 2017 at 10:50 AM, Stefan Hajnoczi wrote:
> On Thu, Dec 22, 2016 at 01:34:47AM -0500, Weiwei Jia wrote:
>> With QEMU x-data-plane, I find the performance has not been improved
>> very much. Please see following two settings.
>
> Using IOThreads imp
On some distros, whenever you close a block device file
descriptor there is a udev rule that resets the file
permissions. This can race with the test script when
we run qemu-io multiple times against the same block
device. Occassionally the second qemu-io invokation
will find udev has reset the per
While the qemu-img dd command does accept --image-opts
this is not sufficient to make it work with the LUKS
image yet. This is because bdrv_create() still always
requires the non-image-opts syntax.
Thus we must skip 159/170 with luks for now
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iote
The qemu-img dd command added --image-opts support, but missed
the corresponding --object support. This prevented passing
secrets (eg auth passwords) needed by certain disk images.
Signed-off-by: Daniel P. Berrange
---
qemu-img.c | 16
1 file changed, 16 insertions(+)
diff --gi
On Tue, 3 Jan 2017 17:10:15 +0100
Paolo Bonzini wrote:
>
>
> On 03/01/2017 15:22, Eduardo Habkost wrote:
> >> I didn't know that. Is this documented somewhere?
> >> Is it actually used by any existing software?
> > not that I know of. But users should be fixed if they are not using it.
> >
> >
On Tue, 3 Jan 2017 16:26:16 +0100
Andreas Färber wrote:
> Am 03.01.2017 um 16:25 schrieb Eric Blake:
> > On 01/02/2017 09:44 AM, Igor Mammedov wrote:
> >
> > perhaps s/not used/unused/ in the subject
>
> ... and qom: instead of cleanup: if this gets re-spun.
sure
>
> Andreas
>
> >
> > Revie
On 12/29/2016 08:41 PM, Junkang Fu wrote:
>>From 74e913fc41ea98d1dde692175f1e3fb6729342aa Mon Sep 17 00:00:00 2001
> From: "junkang.fjk"
> Date: Wed, 24 Aug 2016 19:36:53 +0800
> Subject: [PATCH] virtio-blk: add disk-name device property
>
> Current virtio-blk disk name(ex. /dev/vdb) has nothing
On Mon, Jan 02, 2017 at 09:03:55PM +0900, morgenlette madeBy wrote:
> I got problem using QEMU.
>
> when i turn on virtual machine,
>
> this message was shown,
>
>
> virsh: error while loading shared libraries: libapparmor.so.1: cannot open
> shared object file: No such file or directory
>
> I
On Jan 3, 2017, at 3:59 AM, Gerd Hoffmann wrote:
> On So, 2017-01-01 at 13:15 -0500, Programmingkid wrote:
>> Hello, I was wondering if you would accept a patch that added a Speed
>> menu to the GTK interface. This would allow the user to change how
>> much CPU time the emulated CPU would see.
>
On Sun, Jan 01, 2017 at 10:39:45AM +0100, Hervé Poussineau wrote:
> This patch fixes a segfault at QEMU startup, introduced in
> a08156321ab9a7d2fed9ee77dbfeea2a61ffd153.
> gd_vc_find_current() return NULL, which is dereferenced without checking it.
>
> While at it, disable the whole 'View' menu
On Fri, Dec 30, 2016 at 10:41:35AM +0800, Junkang Fu wrote:
> From 74e913fc41ea98d1dde692175f1e3fb6729342aa Mon Sep 17 00:00:00 2001
> From: "junkang.fjk"
> Date: Wed, 24 Aug 2016 19:36:53 +0800
> Subject: [PATCH] virtio-blk: add disk-name device property
>
> Current virtio-blk disk name(ex. /dev
On Tue, Jan 03, 2017 at 06:28:18PM +0800, Jason Wang wrote:
>
>
> On 2017年01月03日 11:09, Jason Wang wrote:
> >
> >
> > On 2016年12月30日 20:41, Flavio Leitner wrote:
> > > Hi,
> > >
> > > While I was testing vhost-user using OVS 2.5 and DPDK 2.2.0 in the
> > > host and testpmd dpdk 2.2.0 in the gu
I'm pondering where to start with getting FreeBSD's bsd-user code into
shape so it could actually be reviewed and accepted now that its sort of
working again (signal handling fixed finally).
I almost feel like the existing code should be purged, except that it
gives a good history (and this seems
On 03/01/2017 15:22, Eduardo Habkost wrote:
>> I didn't know that. Is this documented somewhere?
>> Is it actually used by any existing software?
> not that I know of. But users should be fixed if they are not using it.
>
> I see. The problem is that the mechanism is undocumented,
> untested, an
Please follow the conventions for commit messages. QEMU commit messages
start with a prefix that identifies the affected component.
(Use git-log(1) to check what prefix other people have used for the
file(s) you touched.)
The commit message should be brief and doesn't need to be a full
sentence.
The 'check' program records timings for each test that
is run. These timings are only valid, however, for a
particular format/protocol combination. So if frequently
running 'check' with a variety of different formats or
protocols, the times printed can be very misleading.
Instead of having a singl
On 03/01/2017 16:53, Stefan Hajnoczi wrote:
> On Fri, Dec 23, 2016 at 03:15:58PM +0100, Paolo Bonzini wrote:
>> Considering that Easter is on April 16th, we'd probably want to have the
>> release before that date even in case of a slip.
>>
>> On the other hand, the Christmas / New Year break here
On Mon, Dec 26, 2016 at 01:59:13PM +0530, Gadre Nayan wrote:
> I am trying to test SPDK on a Virtual Machine with NVME support. I do not
> have NVME cards on the Host hence wanted to simulate the Hardware, I have
> install nvmeqemu (https://github.com/nvmeqemu/nvmeqemu) for that purpose.
That repo
On Fri, Dec 23, 2016 at 03:15:58PM +0100, Paolo Bonzini wrote:
> Considering that Easter is on April 16th, we'd probably want to have the
> release before that date even in case of a slip.
>
> On the other hand, the Christmas / New Year break here means that we'll
> have to make the development ti
1 - 100 of 146 matches
Mail list logo
