v2: add usb_mouse_properties
use macros for bmAttributes
Signed-off-by: Jan Vesely
---
hw/usb/dev-hid.c | 73 +---
1 file changed, 65 insertions(+), 8 deletions(-)
diff --git a/hw/usb/dev-hid.c b/hw/usb/dev-hid.c
index f36e617..70c2c5f 100
v2: add usb_keyboard_properties
use macros for bmAttributes
Signed-off-by: Jan Vesely
---
hw/usb/dev-hid.c | 73 +---
1 file changed, 65 insertions(+), 8 deletions(-)
diff --git a/hw/usb/dev-hid.c b/hw/usb/dev-hid.c
index 70c2c5f..6ead61c
On Fri, Feb 21, 2014 at 01:00:57PM +0800, Jason Wang wrote:
> Currently, the default msix vectors for virtio-net-pci is 3 which is
> obvious not suitable for multiqueue guest, so we depends on the user
> or management tools to pass a correct vectors parameter. In fact, we
> can simplifying this by
On Sat, Feb 22, 2014 at 04:28:26PM -0700, Alex Williamson wrote:
> On Thu, 2014-02-20 at 10:12 +0200, Michael S. Tsirkin wrote:
> > On Wed, Feb 19, 2014 at 03:20:54PM -0500, Bandan Das wrote:
> > > The following patch depends on the value of rom_bar to
> > > determine rom blacklist behavior. Existi
During the test, I found that if the path is long, the performance is
very very slow under 9pfs (whether apply this patch or not, the results
are the same).
So after this patch passes checking, I will/should analyse this
performance issue, next.
Thanks.
On 02/23/2014 12:48 PM, Chen Gang wrote:
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory allocation).
Also find/fix several another related issues when failure occurs.
- check 'fh' in handle_na
Hi Community,
I am new to qemu, I am trying to familiarize myself with aarch64
timer/interrupt support (maybe someone already did this, but not merged
into mainline yet).
As shown in include/qemu/timer.h, there are 6 categories of APIs:
- QEMUClockType
- QEMUTimerList
- QEMUTimerListGroup
- Q
This makes use of op_blocker and blocks all the operations except for
commit target, on each BlockDriverState->backing_hd.
The asserts for op_blocker in bdrv_swap are removed because with this
change, the target of block commit has at least the backing blocker of
its child, so the assertion is not
Hello,
I've been tring to use QEMU-1.5.0 and Libvirt-1.1.0 to run a VM with a nbd
network disk, the VM is created by Libvirt as follow(Please attention to the
red words):
root@xxx-11:~# ps -ef | grep kvm
root 1647 2 0 Feb05 ?00:00:00 [kvm-irqfd-clean]
root 8304 1 37 1
This applies cases on drive-backup on blockdev-backup, except cases with
target format and mode.
Also add a case to check source == target.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/055 | 275 ++---
tests/qemu-iotests/055.out | 4 +-
2 files c
Drive backup is a read only operation on source bs. We want to allow
this specific case to enable image-fleecing. Note that when
image-fleecing job starts, the job still add its blocker to source bs,
and any other operation on it will be blocked by that.
Signed-off-by: Fam Zheng
---
block.c | 2
Signed-off-by: Fam Zheng
---
blockdev.c | 48
qapi-schema.json | 1 +
2 files changed, 49 insertions(+)
diff --git a/blockdev.c b/blockdev.c
index 5ffae90..5db5bbb 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -1409,6 +1409,49 @@ static void
Similar to drive-backup, but this command uses a device id as target
instead of creating/opening an image file.
Also add blocker on target bs, since the target is also a named device
now.
Add check and report error for bs == target which became possible but is
an illegal case with introduction of
Dropping intermediate could be useful both for commit and stream, and
BDS refcnt plus bdrv_swap could do most of the job nicely. It also needs
to work with op blockers.
Signed-off-by: Fam Zheng
---
block.c| 137 +++--
block/commit.c |
This tests the workflow of creating a lightweight point-in-time snapshot
with blockdev-backup command and export it with built-in NBD server.
It's tested that after the snapshot it created, writing to the original
device doesn't change data that can be read from target with NBD.
Signed-off-by: Fa
Now it's safe to allow reference for backing_hd in the interface.
Signed-off-by: Fam Zheng
---
block.c | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/block.c b/block.c
index edfbe59..a8d1012 100644
--- a/block.c
+++ b/block.c
@@ -1405,12 +1405,34
This reuses the new bdrv_drop_intermediate.
Signed-off-by: Fam Zheng
---
block/stream.c | 30 +-
1 file changed, 1 insertion(+), 29 deletions(-)
diff --git a/block/stream.c b/block/stream.c
index dd0b4ac..9cdcf0e 100644
--- a/block/stream.c
+++ b/block/stream.c
@@ -5
This is the common but non-trivial steps to assign or change the
backing_hd of BDS.
Signed-off-by: Fam Zheng
---
block.c | 46 ++
include/block/block.h | 1 +
2 files changed, 39 insertions(+), 8 deletions(-)
diff --git a/block.c b/bloc
It makes no sense to check for "any" blocker on bs, we are here only
because of the mechanical conversion from in_use to op_blockers. Remove
it now, and let the callers check specific operation types. Backup and
mirror already have it, add checker to stream and commit.
Signed-off-by: Fam Zheng
Re
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
export it through built in NBD server. The steps are as below:
1. (SHELL) qemu-i
This drops BlockDriverState.in_use with op_blockers:
- Call bdrv_op_block_all in place of bdrv_set_in_use(bs, 1).
- Call bdrv_op_unblock_all in place of bdrv_set_in_use(bs, 0).
- Check bdrv_op_is_blocked() in place of bdrv_in_use(bs).
The specific types are used, e.g. in place of startin
BlockDriverState.op_blockers is an array of lists with BLOCK_OP_TYPE_MAX
elements. Each list is a list of blockers of an operation type
(BlockOpType), that marks this BDS as currently blocked for a certain
type of operation with reason errors stored in the list. The rule of
usage is:
* BDS user w
This adds the enum of all the operations that can be taken on a block
device.
Signed-off-by: Fam Zheng
Reviewed-by: Benoit Canet
---
include/block/block.h | 19 +++
1 file changed, 19 insertions(+)
diff --git a/include/block/block.h b/include/block/block.h
index 780f48b..882073
On Fri, 02/21 23:12, Kevin Wolf wrote:
> From: Max Reitz
>
> Allow bdrv_open() to handle references to existing block devices just as
> bdrv_file_open() is already capable of.
>
> Signed-off-by: Max Reitz
> Signed-off-by: Kevin Wolf
> ---
> block.c | 44 +
On Thu, 2014-02-20 at 10:12 +0200, Michael S. Tsirkin wrote:
> On Wed, Feb 19, 2014 at 03:20:54PM -0500, Bandan Das wrote:
> > The following patch depends on the value of rom_bar to
> > determine rom blacklist behavior. Existing code shouldn't
> > be affected by changing the default value of rom_ba
** Bug watch added: Debian Bug tracker #739800
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739800
** Also affects: qemu (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739800
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Changed in: qemu (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1256546
Title:
qemu-s390x-static: segmentation fault entering chroot
Status in QEMU:
Conf
Public bug reported:
When using ppc-linux-user/qemu-ppc on a ppc ELF executable, I see that
QEMU wrongly recognizes the vrfim, vrfin and vrfiz instructions:
If the binary contains vrfim QEMU sees vrfiz
If the binary contains vrfin QEMU sees vrfim
If the binary contains vrfiz QEMU sees vrfin
The v
Quorum is not compiled by default: make the quorum 081 test aware of this.
Signed-off-by: Benoit Canet
---
tests/qemu-iotests/081 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/qemu-iotests/081 b/tests/qemu-iotests/081
index f053f11..b512d00 100755
--- a/tests/qemu-iotests/081
+++
Insert quorum QMP events documentation alphabetically.
Also change the "ret" errno value by an optional "error" being an strerror(-ret)
in the QUORUM_REPORT_BAD qmp event.
Signed-off-by: Benoit Canet
Reviewed-by: Eric Blake
---
block/quorum.c | 9 --
docs/qmp/qmp-events.txt
Fix some nits before QEMU 2.0 freeze.
Signed-off-by: Benoit Canet
Reviewed-by: Eric Blake
---
qapi-schema.json | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index fcb22800..ab5cdde 100644
--- a/qapi-schema.json
+++ b/qapi-schema.jso
in v3:
use $QEMU_IMG (Fam)
apply Eric reviewed by
in v2:
make error optional and return strerror(-ret) [Eric]
better documentation of the error string [Eric]
apply Eric reviewed by
Benoît Canet (3):
qmp: Fix BlockdevOptionQuorum.
qmp: Make Quorum error events more palata
On Sat, 02/22 14:00, Peter Lieven wrote:
> this patch tries to optimize zero write requests
> by automatically using bdrv_write_zeroes if it is
> supported by the format.
>
> i know that there is a lot of potential for discussion, but i would
> like to know what the others think.
>
> this should
On Sat, 02/22 12:58, Benoît Canet wrote:
> The Saturday 22 Feb 2014 à 15:38:15 (+0800), Fam Zheng wrote :
> > On Sat, 02/22 02:20, Benoît Canet wrote:
> > > Quorum is not compiled by default: make the quorum 081 test aware of this.
> > >
> > > Signed-off-by: Benoit Canet
> > > ---
> > > tests/qe
Il 22/02/2014 13:17, Peter Lieven ha scritto:
commit fa6252b0 introduced a segfault because it tries
to read iTask.task->sense after iTask.task has been
freed.
CC: qemu-sta...@nongnu.org
Not needed, it's not in the 1.7.1 pending release. Applied to
scsi-next, thanks.
Paolo
Signed-off-by:
Il 21/02/2014 18:36, Liu, Jinsong ha scritto:
From 0750e335eb5860b0b483e217e8a08bd743cbba16 Mon Sep 17 00:00:00 2001
From: Liu Jinsong
Date: Thu, 20 Feb 2014 17:39:32 +0800
Subject: [PATCH] KVM: x86: expose ADX feature to guest
ADCX and ADOX instructions perform an unsigned addition with Carry
Il 21/02/2014 18:39, Liu, Jinsong ha scritto:
From 00c920c96127d20d4c3bb790082700ae375c39a0 Mon Sep 17 00:00:00 2001
From: Liu Jinsong
Date: Fri, 21 Feb 2014 23:47:18 +0800
Subject: [PATCH] KVM: x86: Fix xsave cpuid exposing bug
EBX of cpuid(0xD, 0) is dynamic per XCR0 features enable/disable.
Il 21/02/2014 18:33, Liu, Jinsong ha scritto:
From 24ffdce9efebf13c6ed4882f714b2b57ef1141eb Mon Sep 17 00:00:00 2001
From: Liu Jinsong
Date: Thu, 20 Feb 2014 17:38:26 +0800
Subject: [PATCH] KVM: x86: expose new instruction RDSEED to guest
RDSEED instruction return a random number, which supplie
Il 22/02/2014 13:25, Alex Bligh ha scritto:
Paolo,
On 22 Feb 2014, at 10:55, Paolo Bonzini wrote:
Il 22/02/2014 10:03, Alex Bligh ha scritto:
I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
condition should be changed too:
} else if (deactivating_bit(ol
On Wed, Feb 19, 2014 at 10:02:36AM +0800, Li Guang wrote:
> Beniamino Galvani wrote:
> >On Tue, Feb 18, 2014 at 11:49:51AM +0800, Li Guang wrote:
> >>Beniamino Galvani wrote:
> >>>According to this mail thread [1], writing to pending register seems
> >>>to have no effect on actual pending status of
Hi Mark,
the strace is from qemu-system-sparc64 host process. Inside the running system
(Linux 3.13.3, glib 2.19, busybox) I get:
[pid 273] umask(0)= 022
[pid 273] umask(022) = 0
[pid 273] mkdir("perl-5.18.1/", 0777) = -1 EEXIST (File exists)
[pid 273
this patch tries to optimize zero write requests
by automatically using bdrv_write_zeroes if it is
supported by the format.
i know that there is a lot of potential for discussion, but i would
like to know what the others think.
this should significantly speed up file system initialization and
sho
Paolo,
On 22 Feb 2014, at 10:55, Paolo Bonzini wrote:
> Il 22/02/2014 10:03, Alex Bligh ha scritto:
>> I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
>> condition should be changed too:
>>
>>} else if (deactivating_bit(old_val, new_val, HPET_TN_ENABLE) ||
commit fa6252b0 introduced a segfault because it tries
to read iTask.task->sense after iTask.task has been
freed.
CC: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven
---
block/iscsi.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/block/iscsi.c b/block
19.02.2014 09:11, Stefan Weil wrote:
> These modifications avoid type conversions for non optimized code.
>
> ld* function prototypes will follow later.
>
> [PATCH 1/2] bswap: Modify prototype of stb_p (avoid type
> [PATCH 2/2] bswap: Modify prototypes of st[wl]_{le,be}_p (avoid type
Thanks, app
Thanks, applied to the trivial patches queue.
/mjt
The Saturday 22 Feb 2014 à 15:38:15 (+0800), Fam Zheng wrote :
> On Sat, 02/22 02:20, Benoît Canet wrote:
> > Quorum is not compiled by default: make the quorum 081 test aware of this.
> >
> > Signed-off-by: Benoit Canet
> > ---
> > tests/qemu-iotests/081 | 3 +++
> > 1 file changed, 3 insertion
Il 22/02/2014 10:03, Alex Bligh ha scritto:
> I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
> condition should be changed too:
>
> } else if (deactivating_bit(old_val, new_val, HPET_TN_ENABLE) ||
>!hpet_enabled(s)) {
>
On 02/22/2014 01:51 PM, Benjamin Herrenschmidt wrote:
> On Sat, 2014-02-22 at 13:20 +1100, Alexey Kardashevskiy wrote:
>
>> Sorry for bothering again. This is quite simple patchset, it does not touch
>> a lot and just a small rework. This is v7, v1 was 31/10/2013 (~4 months), I
>> sent "ping" to v
On 22 Feb 2014, at 04:37, Matt Lupfer wrote:
> A HPET timer can be started when HPET is not yet
> enabled. This will not generate an interrupt
> to the guest, but causes problems when HPET is later
> enabled.
>
> A timer that is created and expires at least once before
> HPET is enabled will hav
Il 22/02/2014 05:37, Matt Lupfer ha scritto:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least once before
HPET is enabled will have an initializ
Il 22/02/2014 01:57, Matt Lupfer ha scritto:
Thanks for the response. The hpet_timer() callback calls timer_mod()
every 1 ms. That timerlist has no notify callback so it in turn calls
qemu_notify_event().
The guest kernel is only enabling the HPET timer and looking for
timer interrupts.
FWIW
On 22 Feb 2014, at 00:57, Matt Lupfer wrote:
> I did some more debugging and found the problem was elsewhere. This
> different timer behavior is exposing a bug in the HPET implementation.
>
> It's possible for the QEMU timer underlying the HPET to call the hpet_timer()
> callback between when t
Resizing the xbzrle cache during migration causes qemu-crash,
because the main-thread and migration-thread modify the xbzrle
cache size concurrently without lock-protection.
Signed-off-by: ChenLiang
Signed-off-by: Gonglei
Reviewed-by: Dr. David Alan Gilbert
---
Changes against the previous vers
54 matches
Mail list logo
