With Linux kernel version 3.3 or later, qemu fails with the following message:
sh_serial: unsupported read from 0x18
Aborted
Reported-and-analyzed-by: Rob Landley r...@landley.net
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
See
On 8 September 2013 08:39, Guenter Roeck li...@roeck-us.net wrote:
With Linux kernel version 3.3 or later, qemu fails with the following message:
sh_serial: unsupported read from 0x18
Aborted
Reported-and-analyzed-by: Rob Landley r...@landley.net
Signed-off-by: Guenter Roeck
I started writing a blog post yesterday about virtualized smartcards here:
https://blogs.gnome.org/halfline/2013/09/08/another-smartcard-post/
and while testing what I was writing I noticed an invalid PIN worked when
it shouldn't have. It turns out that typing a valid PIN once in one
This is being looked at in an upstream thread at
http://lists.gnu.org/archive/html/qemu-devel/2013-07/msg01850.html
Cheers,
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1100843
Title:
Live
On Sat, Sep 07, 2013 at 09:49:24AM +0100, Peter Maydell wrote:
On 6 September 2013 19:01, Richard W.M. Jones rjo...@redhat.com wrote:
Have you tried virtio-serial on ARM at all? The port never shows up.
I don't think I've tested the serial-device part of it, but I've
used it to provide
On Thu, Sep 05, 2013 at 03:06:21PM +0200, Paolo Bonzini wrote:
On KVM, the KVM_SET_XSAVE would be executed with a 0 xstate_bv,
and not restore anything.
XRSTOR restores FP/SSE state to reset state if no bits are set in
xstate_bv. This is what should happen on reset, no?
Since FP and SSE data
On Thu, Sep 05, 2013 at 03:06:22PM +0200, Paolo Bonzini wrote:
QEMU moves state from CPUArchState to struct kvm_xsave and back when it
invokes the KVM_*_XSAVE ioctls. Because it doesn't treat the XSAVE
region as an opaque blob, it might be impossible to set some state on
the destination if
On 09/08/2013 12:51 AM, Peter Maydell wrote:
On 8 September 2013 08:39, Guenter Roeck li...@roeck-us.net wrote:
With Linux kernel version 3.3 or later, qemu fails with the following message:
sh_serial: unsupported read from 0x18
Aborted
Reported-and-analyzed-by: Rob Landley
On Fri, 09/06 20:19, Lluís Vilanova wrote:
Fam Zheng writes:
[...]
Because $(obj) here is './block', instead of '../block'. This doesn't
hurt compiling because we basically build all .o from top Makefile,
before entering Makefile.target, but it will affact arriving per-object
libs
the other question: when I change the buffer size #define IO_BUF_SIZE 32768
to #define IO_BUF_SIZE (1 * 1024 * 1024), the savevm is more quickly.
Is this for cache=unsafe as well?
Juan, any specific reason for using 32k? I think it would be better to
have a multiple of the qcow2 cluster
On Fri, 09/06 14:11, Paolo Bonzini wrote:
Il 06/09/2013 13:47, Fam Zheng ha scritto:
On Fri, 09/06 12:09, Paolo Bonzini wrote:
Il 06/09/2013 09:28, Fam Zheng ha scritto:
Add necessary rules and flags for shared object generation.
$(common-obj-m) will include $(block-obj-m), like
On 09/06/2013 01:11 AM, Alexander Graf wrote:
On 05.09.2013, at 16:26, Benjamin Herrenschmidt wrote:
On Thu, 2013-09-05 at 16:14 +0200, Andreas Färber wrote:
Are you thinking of POWER8 having a different frequency than POWER8 in
compat mode? Because migration from one -cpu to another is
If it is not restored after qcow2_write_snapshots() fail, a core
dump will happen in bdrv_close() since access of invalid pointer.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qcow2-snapshot.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git
For those error paths which can't be triggered by other debug event,
use snapshot debug events.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qcow2-snapshot.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/block/qcow2-snapshot.c
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qcow2-snapshot.c | 20
1 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/block/qcow2-snapshot.c b/block/qcow2-snapshot.c
index 9e2d695..e0b7a5a 100644
--- a/block/qcow2-snapshot.c
+++
V2:
1: all fail case will goto fail section.
2: add the goto code.
v3:
Address Stefan's comments:
2: don't goto fail after allocation failure.
3: use sn-l1size correctly in qcow2_free_cluster().
4-7: add test case to verify the error paths.
Other:
1: new patch fix a existing bug,
The message will be print out with a macro enabled, which can
be used to check which error path is taken.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qcow2-snapshot.c | 46 ++
1 files changed, 46 insertions(+), 0 deletions(-)
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block/qcow2-snapshot.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/block/qcow2-snapshot.c b/block/qcow2-snapshot.c
index 40393b2..9e2d695 100644
--- a/block/qcow2-snapshot.c
+++ b/block/qcow2-snapshot.c
Some code in qcow2-snapshot.c directly access bs-file, so in those
points error can't be injected by other events. Since the code in
qcow2-snapshot.c is qcow2's internal detail similar as L1 table,
so add some debug events.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
This test will focus on the low level procedure of qcow2 snapshot
operations, now it covers only the create operation. Overlap error
paths are not checked since no good way to trigger those errors.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
tests/qemu-iotests/063 | 229
Paolo Bonzini wrote:
Il 29/08/2013 10:25, Liu, Jinsong ha scritto:
Currently HVM S3 has a bug coming from the difference between
qemu-traditioanl and qemu-xen. For qemu-traditional, the way
to resume from hvm s3 is via 'xl trigger' command. However,
for qemu-xen, the way to resume from hvm s3
From 6f40a66521e012170493964a2135fb3b4ae7c9b2 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sun, 8 Sep 2013 00:33:19 +0800
Subject: [PATCH V3 1/2] qemu: Adjust qemu wakeup
Currently Xen hvm s3 has a bug coming from the difference between
qemu-traditioanl and qemu-xen. For
From 63668de43b6512c1db06405b0d2d1e0a0c68244b Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sun, 8 Sep 2013 00:39:45 +0800
Subject: [PATCH V3 2/2] qemu: Add qemu xen logic for Xen HVM S3 resume
This patch is qemu patch 2 to fix Xen HVM S3 bug, adding qemu
xen logic. When
From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Fri, 23 Aug 2013 23:30:23 +0800
Subject: [PATCH V3] xl: HVM domain S3 bugfix
Currently Xen hvm s3 has a bug coming from the difference between
qemu-traditioanl and qemu-xen. For
On 09/07/2013 03:21 AM, Eduardo Otubo wrote:
Adding a system call blacklist right before the vcpus starts. This filter is
composed by the system calls that can't be executed after the guests are up.
This list should be refined as the whitelist is, with as much testing as we can
do using
Hi all,
1. I create a raw image named as win8.img, using the following command:
/usr/local/kvm/bin/qemu-img create -f raw win8.img 20G
2. I try to install win8 with the following command, but I failed several times.
sudo /usr/local/kvm/bin/qemu-system-x86_64 -enable-kvm -drive
This will help you:
http://www.linux-kvm.org/page/Boot_from_virtio_block_device
xuanmao_001
From: Yaodong Yang
Date: 2013-09-09 13:02
To: qemu-devel@nongnu.org; qemu-disc...@nongnu.org
Subject: [Qemu-discuss] virtio with Windows 8.
Hi all,
1. I create a raw image named as win8.img, using the
Am 09.09.2013 um 04:40 schrieb Alexey Kardashevskiy a...@ozlabs.ru:
On 09/06/2013 01:11 AM, Alexander Graf wrote:
On 05.09.2013, at 16:26, Benjamin Herrenschmidt wrote:
On Thu, 2013-09-05 at 16:14 +0200, Andreas Färber wrote:
Are you thinking of POWER8 having a different frequency
28 matches
Mail list logo
