On 11/04/2013 06:47 PM, Alexander Graf wrote:
On 04.11.2013, at 04:36, Alexey Kardashevskiy a...@ozlabs.ru wrote:
If QEMU is started with KVM enabled and -cpu specified, and the CPU is not
from the family which the host is running on, an error should be displayed
so this the patch does.
On 04.11.2013, at 09:58, Alexey Kardashevskiy a...@ozlabs.ru wrote:
On 11/04/2013 06:47 PM, Alexander Graf wrote:
On 04.11.2013, at 04:36, Alexey Kardashevskiy a...@ozlabs.ru wrote:
If QEMU is started with KVM enabled and -cpu specified, and the CPU is not
from the family which the host
On 11/04/2013 08:05 PM, Alexander Graf wrote:
On 04.11.2013, at 09:58, Alexey Kardashevskiy a...@ozlabs.ru wrote:
On 11/04/2013 06:47 PM, Alexander Graf wrote:
On 04.11.2013, at 04:36, Alexey Kardashevskiy a...@ozlabs.ru wrote:
If QEMU is started with KVM enabled and -cpu specified, and
On 31/10/13 15:30, Michael S. Tsirkin wrote:
On Thu, Oct 24, 2013 at 10:39:03AM +0800, Hu Tao wrote:
Hi All,
I know it's been a long time since this thread. But qemu 1.7 is
releasing, do you have any consensus on this?
Thanks.
I think the biggest issue is the new PANICKED state.
I
On 04.11.2013, at 10:24, Alexey Kardashevskiy a...@ozlabs.ru wrote:
On 11/04/2013 08:05 PM, Alexander Graf wrote:
On 04.11.2013, at 09:58, Alexey Kardashevskiy a...@ozlabs.ru wrote:
On 11/04/2013 06:47 PM, Alexander Graf wrote:
On 04.11.2013, at 04:36, Alexey Kardashevskiy
On 24.10.2013 12:07, Juan Quintela wrote:
Peter Lieven p...@kamp.de wrote:
The madvise for zeroed out pages was introduced when every transferred
zero page was memset to zero and thus allocated. Since commit
211ea740 we check for zeroness of a target page before we memset
it to zero.
Previously a BlockDriverState has only one dirty bitmap, so only one
caller (e.g. a block job) can keep track of writing. This changes the
dirty bitmap to a list and creates a BdrvDirtyBitmap for each caller, the
lifecycle is managed with these new functions:
bdrv_create_dirty_bitmap
On Wed, Oct 30, 2013 at 02:49:32PM +0100, Markus Armbruster wrote:
The first proposal is to add another parameter, say id. Users can
then refer either to an arbitrary BDS by id, or (for backward
compatibility) to the root BDS by device. When the code sees
device, it'll look up the BB, then
On Mon, 2013-11-04 at 08:18 +0200, Michael S. Tsirkin wrote:
On Sun, Nov 03, 2013 at 09:26:06PM +, Peter Maydell wrote:
On 3 November 2013 20:48, Marcel Apfelbaum marce...@redhat.com wrote:
The problem appears when a root memory region within an
address space with size UINT64_MAX has
On 04.11.2013, at 02:10, Alexey Kardashevskiy a...@ozlabs.ru wrote:
Normally CPUState::cpu_index is used to pick the right CPU for various
operations. However default consecutive numbering does not always work
for POWERPC.
For example, on POWER7 (which supports 4 threads per core),
-smp
On 11/04/2013 05:31 PM, Stefan Hajnoczi wrote:
On Wed, Oct 30, 2013 at 02:49:32PM +0100, Markus Armbruster wrote:
The first proposal is to add another parameter, say id. Users can
then refer either to an arbitrary BDS by id, or (for backward
compatibility) to the root BDS by device. When the
On So, 2013-11-03 at 08:45 -0800, Anthony Liguori wrote:
Modern Linux's no longer support /dev/dsp so enabling it by
default causes audio failures on newer Linux distros.
That will break sound on BSD.
I think we should do something like this instead:
--- a/configure
+++ b/configure
@@ -554,7
On Mon, 2013-11-04 at 08:06 +0200, Michael S. Tsirkin wrote:
The page table logic in exec.c assumes
that memory addresses are at most TARGET_PHYS_ADDR_SPACE_BITS.
But pci addresses are full 64 bit so if we try to render them ignoring
the extra bits, we get strange effects with sections
On Mon, Nov 04, 2013 at 11:33:56AM +0200, Marcel Apfelbaum wrote:
On Mon, 2013-11-04 at 08:18 +0200, Michael S. Tsirkin wrote:
On Sun, Nov 03, 2013 at 09:26:06PM +, Peter Maydell wrote:
On 3 November 2013 20:48, Marcel Apfelbaum marce...@redhat.com wrote:
The problem appears when a
On 11/04/2013 08:41 PM, Alexander Graf wrote:
On 04.11.2013, at 02:10, Alexey Kardashevskiy a...@ozlabs.ru wrote:
Normally CPUState::cpu_index is used to pick the right CPU for various
operations. However default consecutive numbering does not always work
for POWERPC.
For example, on
On Mon, Nov 04, 2013 at 11:50:05AM +0200, Marcel Apfelbaum wrote:
On Mon, 2013-11-04 at 08:06 +0200, Michael S. Tsirkin wrote:
The page table logic in exec.c assumes
that memory addresses are at most TARGET_PHYS_ADDR_SPACE_BITS.
But pci addresses are full 64 bit so if we try to render
On 04.11.2013, at 10:58, Alexey Kardashevskiy a...@ozlabs.ru wrote:
On 11/04/2013 08:41 PM, Alexander Graf wrote:
On 04.11.2013, at 02:10, Alexey Kardashevskiy a...@ozlabs.ru wrote:
Normally CPUState::cpu_index is used to pick the right CPU for various
operations. However default
Il 02/11/2013 13:07, Markus Armbruster ha scritto:
Why do you even need a new category? Just take everything in the
network category and put it in the help.
You *can't* currently construct -net nic,model=help output from
registered qdev NICs, because:
* -net nic generally doesn't accept
v2:
- fix issues found by checkpatch.pl
- change the descritpion of patch 3
This patch series makes the thread pool implementation modular.
This allows each drive to use a special implementation.
The patch series prepares qemu to be able to include thread pools different to
the one actually
This patch allows to choose at the command line level which thread pool
implementation will be used by every block device.
Signed-off-by: Matthias Brugger matthias@gmail.com
---
blockdev.c | 13 +
qemu-options.hx | 2 +-
2 files changed, 14 insertions(+), 1 deletion(-)
This patch introduces function pointers for the thread pool, so that
it's implementation can be set at run-time.
Signed-off-by: Matthias Brugger matthias@gmail.com
---
include/block/thread-pool.h | 11 +++
thread-pool.c | 33 +
2 files
With this patch, the calls to the thread pool functions pass through the
new modular thread pool implementation.
Signed-off-by: Matthias Brugger matthias@gmail.com
---
async.c | 4 ++--
block/raw-posix.c | 15 +++
block/raw-win32.c | 9 +++--
Il 04/11/2013 07:59, Fam Zheng ha scritto:
I think callers outside block.c should only call
hbitmap_set/hbitmap_reset; resetting is typically done before processing
sectors and setting after an error (both of which happen privately to
each task).
Thus you probably should add a fourth patch
Il 01/11/2013 04:21, Alexey Kardashevskiy ha scritto:
Normally CPUState::cpu_index is used to pick the right CPU for various
operations. However default consecutive numbering does not always work
for POWERPC.
For example, on POWER7 (which supports 4 threads per core),
-smp 8,threads=4
Il 04/11/2013 10:30, Fam Zheng ha scritto:
diff --git a/include/block/block.h b/include/block/block.h
index 3560deb..06f424c 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -388,12 +388,15 @@ void *qemu_blockalign(BlockDriverState *bs, size_t
size);
bool
Disable acpi build for isapc and no_kvmclock machine
types (used by xen), since acpi build currently expects pci.
Reported-by: Andreas Färber afaer...@suse.de
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/i386/pc_piix.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 01.11.2013, at 11:21, Alexey Kardashevskiy a...@ozlabs.ru wrote:
SLOF gets really confused if RTAS/device-tree and everything else
what SLOF can use is not in the very first block of the very first
memory node.
This makes sure that the RMA area is where SLOF expects it to be.
Cc:
On 11/04/2013 06:37 PM, Paolo Bonzini wrote:
Il 04/11/2013 10:30, Fam Zheng ha scritto:
diff --git a/include/block/block.h b/include/block/block.h
index 3560deb..06f424c 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -388,12 +388,15 @@ void *qemu_blockalign(BlockDriverState
From: Kirill A. Shutemov kirill.shute...@linux.intel.com
Currently we have few issues with P9_STATS_GEN:
- We don't try to read st_gen anything except files or directories, but
still set P9_STATS_GEN bit in st_result_mask. It may mislead client:
we present garbage as valid st_gen.
- If
Il 04/11/2013 11:07, Michael S. Tsirkin ha scritto:
On Mon, Nov 04, 2013 at 11:50:05AM +0200, Marcel Apfelbaum wrote:
On Mon, 2013-11-04 at 08:06 +0200, Michael S. Tsirkin wrote:
The page table logic in exec.c assumes
that memory addresses are at most TARGET_PHYS_ADDR_SPACE_BITS.
But pci
On Mon, 2013-11-04 at 11:44 +0100, Alexander Graf wrote:
On 01.11.2013, at 11:21, Alexey Kardashevskiy a...@ozlabs.ru wrote:
SLOF gets really confused if RTAS/device-tree and everything else
what SLOF can use is not in the very first block of the very first
memory node.
This makes
Il 04/11/2013 11:47, Fam Zheng ha scritto:
-void bdrv_set_dirty_tracking(BlockDriverState *bs, int granularity);
-int bdrv_get_dirty(BlockDriverState *bs, int64_t sector);
+typedef struct BdrvDirtyBitmap BdrvDirtyBitmap;
+BdrvDirtyBitmap *bdrv_create_dirty_bitmap(BlockDriverState *bs, int
Am 31.10.2013 um 21:50 hat Anthony Liguori geschrieben:
On Thu, Oct 31, 2013 at 4:48 PM, Kevin Wolf kw...@redhat.com wrote:
The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging
(2013-10-18 10:03:24
On 3 November 2013 16:45, Anthony Liguori anth...@codemonkey.ws wrote:
Modern Linux's no longer support /dev/dsp so enabling it by
default causes audio failures on newer Linux distros.
Signed-off-by: Anthony Liguori aligu...@amazon.com
---
audio/ossaudio.c | 2 +-
1 file changed, 1
Am 04.11.2013 um 10:48 hat Fam Zheng geschrieben:
On 11/04/2013 05:31 PM, Stefan Hajnoczi wrote:
On Wed, Oct 30, 2013 at 02:49:32PM +0100, Markus Armbruster wrote:
The first proposal is to add another parameter, say id. Users can
then refer either to an arbitrary BDS by id, or (for backward
On Mon, Nov 04, 2013 at 11:54:34AM +0100, Paolo Bonzini wrote:
Il 04/11/2013 11:07, Michael S. Tsirkin ha scritto:
On Mon, Nov 04, 2013 at 11:50:05AM +0200, Marcel Apfelbaum wrote:
On Mon, 2013-11-04 at 08:06 +0200, Michael S. Tsirkin wrote:
The page table logic in exec.c assumes
that
Am 01.11.2013 um 16:12 hat Luiz Capitulino geschrieben:
On Fri, 01 Nov 2013 08:59:20 -0600
Eric Blake ebl...@redhat.com wrote:
On 11/01/2013 08:51 AM, Luiz Capitulino wrote:
On Wed, 30 Oct 2013 13:25:35 -0600
Eric Blake ebl...@redhat.com wrote:
On 10/30/2013 07:49 AM, Markus
Am 04.11.2013 um 08:24 hat Fam Zheng geschrieben:
On Tue 29 Oct 2013 08:12:38 PM CST, Kevin Wolf wrote:
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an image cached in
bs-total_sectors so that
On 11/04/2013 09:00 PM, Paolo Bonzini wrote:
Il 01/11/2013 04:21, Alexey Kardashevskiy ha scritto:
Normally CPUState::cpu_index is used to pick the right CPU for various
operations. However default consecutive numbering does not always work
for POWERPC.
For example, on POWER7 (which supports
Il 04/11/2013 12:14, Michael S. Tsirkin ha scritto:
This patch looks good; however, on top of it can you test
kvm-unit-tests with TARGET_PHYS_ADDR_SPACE_BITS=64 and see whether
there is a measurable slowdown (in the inl_from_qemu tests)? If not,
we can just get rid of
On 11/04/2013 07:18 PM, Kevin Wolf wrote:
Am 04.11.2013 um 08:24 hat Fam Zheng geschrieben:
On Tue 29 Oct 2013 08:12:38 PM CST, Kevin Wolf wrote:
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an
Am 04.11.2013 um 08:01 hat Amos Kong geschrieben:
Currently we have three QemuOptsList (qemu_common_drive_opts,
qemu_legacy_drive_opts, and qemu_drive_opts), only qemu_drive_opts
is added to vm_config_groups[].
We query commandline options by checking information in
vm_config_groups[], so
Avoid starting a new migration task while the previous one still exist.
Signed-off-by: Zeng Junliang zengjunli...@huawei.com
---
migration.c | 34 ++
1 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/migration.c b/migration.c
index
On 04.11.2013, at 11:55, Benjamin Herrenschmidt b...@kernel.crashing.org
wrote:
On Mon, 2013-11-04 at 11:44 +0100, Alexander Graf wrote:
On 01.11.2013, at 11:21, Alexey Kardashevskiy a...@ozlabs.ru wrote:
SLOF gets really confused if RTAS/device-tree and everything else
what SLOF can use
Il 04/11/2013 12:26, Zhanghaoyu (A) ha scritto:
Avoid starting a new migration task while the previous one still exist.
Can you explain how to reproduce the problem?
Also please use pbonz...@redhat.com instead. My Gmail address is an
implementation detail. :)
Signed-off-by: Zeng Junliang
On 11/04/2013 07:06 PM, Kevin Wolf wrote:
Am 04.11.2013 um 10:48 hat Fam Zheng geschrieben:
On 11/04/2013 05:31 PM, Stefan Hajnoczi wrote:
On Wed, Oct 30, 2013 at 02:49:32PM +0100, Markus Armbruster wrote:
The first proposal is to add another parameter, say id. Users can
then refer either
Am 01.11.2013 um 16:32 hat Jeff Cody geschrieben:
On Thu, Oct 31, 2013 at 02:10:48PM +0100, Stefan Hajnoczi wrote:
On Wed, Oct 30, 2013 at 10:44:37AM -0400, Jeff Cody wrote:
This patch series contains the initial VHDX log parsing, replay,
write support, and image creation.
=== v8
On 11/04/2013 08:34 AM, Amos Kong wrote:
(I'm curious where your original query was sent - I didn't see it in my
libvir-list nor my qemu-devel folders...)
currently, all the RedHat mailing lists seem to gobble up emails
from the linux.vnet.ibm.com domain, I have tried to report that
via the
On Mon, 4 Nov 2013 12:28:12 +0100
Alexander Graf ag...@suse.de wrote:
On 04.11.2013, at 11:55, Benjamin Herrenschmidt b...@kernel.crashing.org
wrote:
On Mon, 2013-11-04 at 11:44 +0100, Alexander Graf wrote:
On 01.11.2013, at 11:21, Alexey Kardashevskiy a...@ozlabs.ru wrote:
SLOF
On Mon, Nov 04, 2013 at 12:22:35PM +0100, Paolo Bonzini wrote:
Il 04/11/2013 12:14, Michael S. Tsirkin ha scritto:
This patch looks good; however, on top of it can you test
kvm-unit-tests with TARGET_PHYS_ADDR_SPACE_BITS=64 and see whether
there is a measurable slowdown (in the
Il 04/11/2013 13:04, Michael S. Tsirkin ha scritto:
Also, I'm not sure what will this test tell
us: inl reads io space, not memory, right?
The number of levels in the dispatch radix tree is independent of the
size of the AddressSpace; it is P_L2_LEVELS for both the 64K io space
Unlike the existing FW_CFG_E820_TABLE entry which carries reservations
only the new etc/e820 file also has entries for RAM.
Format is simliar to the FW_CFG_E820_TABLE, it is a simple list of
e820_entry structs. Unlike FW_CFG_E820_TABLE it has no count though
as the number of entries can be
Il 04/11/2013 11:46, Michael S. Tsirkin ha scritto:
Disable acpi build for isapc and no_kvmclock machine
types (used by xen), since acpi build currently expects pci.
Xen is now using -M pc, so it's okay to remove it from the legacy -M
xenfv.
Reported-by: Andreas Färber afaer...@suse.de
Il 04/11/2013 07:06, Michael S. Tsirkin ha scritto:
The page table logic in exec.c assumes
that memory addresses are at most TARGET_PHYS_ADDR_SPACE_BITS.
But pci addresses are full 64 bit so if we try to render them ignoring
the extra bits, we get strange effects with sections overlapping
Hi,
After some discussion with Andrea Arcangeli the initial
approach of extending the FW_CFG_E820_TABLE was scratched.
Unfortunaly that patch wasn't formally NACK'ed and became
commit 0624c7f916b4d97f17726d9b295d6a6b0dc5076d, so we
need to fixup the mess now, before 1.7.
The new approach is to
On 07.10.2013, at 18:53, Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Targets like ppc64 support different typed of KVM, one which use
hypervisor mode and the other which doesn't. Add a new machine
property kvm_type that
On Do, 2013-10-31 at 10:35 +0100, Hans de Goede wrote:
This patch mirrors a patch to the Linux uas kernel driver which I've just
submitted. It looks like the qemu uas struct definitions were taken from
the Linux kernel driver, and have inherited the same mistake.
Besides fixing the response
So RAM shows up in the new etc/e820 fw_cfg file.
Cc: Andrea Arcangeli aarca...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/i386/pc.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index a653ae4..12c436e 100644
---
Hi,
So maybe design that with memory hotplug in mind? Such as adding a new
qemu-specific type QEMU_RAM_HOTPLUG? Which seabios could use to reserve
the memory (but not add it to the e820 table for the guest)?
It will do job too. But extending semantics of standard table would be
On Fri, Nov 01, 2013 at 05:35:29PM +0800, Fam Zheng wrote:
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
On Mo, 2013-10-28 at 08:47 +, Gonglei (Arei) wrote:
-Original Message-
From: Gerd Hoffmann [mailto:kra...@redhat.com]
Sent: Monday, October 28, 2013 3:53 PM
To: Gonglei (Arei)
Cc: qemu-devel@nongnu.org; Stefan Hajnoczi; Yanqiangjun; Luonengjun;
Huangweidong (Hardware)
Tested with latest qemu git repos. Got the same kernel panic.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1247122
Title:
kernel guest 3.10.6 boot failure at sha_transform
Status in QEMU:
New
On 11/04/2013 10:50 PM, Thomas Huth wrote:
On Mon, 4 Nov 2013 12:28:12 +0100
Alexander Graf ag...@suse.de wrote:
On 04.11.2013, at 11:55, Benjamin Herrenschmidt b...@kernel.crashing.org
wrote:
On Mon, 2013-11-04 at 11:44 +0100, Alexander Graf wrote:
On 01.11.2013, at 11:21, Alexey
On 4 November 2013 13:11, Alexey Kardashevskiy a...@ozlabs.ru wrote:
PAPR says in Hypervisor Call Functions:
Logical addresses start at zero. When control is initially passed to the
OS from the platform, the first region is the
single RMA. The first region has logical region identifier of
On 2013-10-07 18:53, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Targets like ppc64 support different typed of KVM, one which use
hypervisor mode and the other which doesn't. Add a new machine
property kvm_type that helps in selecting the respective ones
On 2013-08-14 13:29, Jan Kiszka wrote:
This was once introduced by commit 100d9891d6 but was never used in-tree
and then got broken by commit 32e0c8260d. Time to clean up.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/timer/mc146818rtc.c |9 +
1 files changed, 1
On 04.11.2013, at 14:28, Jan Kiszka jan.kis...@siemens.com wrote:
On 2013-10-07 18:53, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Targets like ppc64 support different typed of KVM, one which use
hypervisor mode and the other which doesn't. Add a new
After reporting the GUEST_PANICKED monitor event, QEMU stops the VM.
The reason for this is that events are edge-triggered, and can be lost if
management dies at the wrong time. Stopping a panicked VM lets management
know of a panic even if it has crashed; management can learn about the
panic
This causes two slight backwards-incompatibilities between -M pc-1.5
and 1.5's -M pc:
(1) a fw_cfg file is removed with this patch. This is only a problem
if migration stops the virtual machine exactly during fw_cfg enumeration.
(2) after migration, a VM created without an explicit -device
On 2013-11-04 14:30, Alexander Graf wrote:
On 04.11.2013, at 14:28, Jan Kiszka jan.kis...@siemens.com wrote:
On 2013-10-07 18:53, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Targets like ppc64 support different typed of KVM, one which use
hypervisor
On Mon, 04 Nov 2013 09:59:50 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013/11/1 22:02, Luiz Capitulino 写道:
On Mon, 21 Oct 2013 10:16:01 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c
On 11/05/2013 12:19 AM, Peter Maydell wrote:
On 4 November 2013 13:11, Alexey Kardashevskiy a...@ozlabs.ru wrote:
PAPR says in Hypervisor Call Functions:
Logical addresses start at zero. When control is initially passed to the
OS from the platform, the first region is the
single RMA. The
On Wed, Oct 30, 2013 at 01:56:38PM +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Currently, we get SeaBIOS defaults: manufacturer Bochs, product Bochs,
no version. Best SeaBIOS can do, but we can provide better defaults:
manufacturer QEMU, product version taken
This feature was already deprecated back then in qemu-kvm, ie. before
pci-assign went upstream. assigned_dev_ioport_rw will never be invoked
with resource_fd 0.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/i386/kvm/pci-assign.c | 56 +---
1
Please pull the following for 1.7.
The following changes since commit a126050a103c924b03388a9a64ce9af8c96b0969:
Merge remote-tracking branch 'kwolf/tags/for-anthony' into staging
(2013-10-31 17:02:26 +0100)
are available in the git repository at:
The page table logic in exec.c assumes
that memory addresses are at most TARGET_PHYS_ADDR_SPACE_BITS.
But pci addresses are full 64 bit so if we try to render them ignoring
the extra bits, we get strange effects with sections overlapping each
other.
To fix, simply limit the system memory size to
On 11/03/2013 07:41 AM, 宫文超 wrote:
Top-posted replies to an untrimmed digest message and with an irrelevant
subject line are considered poor netiquette.
When i use the savevm command to create a online snapshot i found it's very
very slow,i found the online snapshot save four device
Disable acpi build for isapc and no_kvmclock machine
types (used by xen), since acpi build currently expects pci.
Reported-by: Andreas Färber afaer...@suse.de
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Paolo Bonzini pbonz...@redhat.com
---
hw/i386/pc_piix.c | 2 ++
1 file
From: Paolo Bonzini pbonz...@redhat.com
After reporting the GUEST_PANICKED monitor event, QEMU stops the VM.
The reason for this is that events are edge-triggered, and can be lost if
management dies at the wrong time. Stopping a panicked VM lets management
know of a panic even if it has crashed;
On Mon, 4 Nov 2013 12:13:59 +0100
Kevin Wolf kw...@redhat.com wrote:
Am 01.11.2013 um 16:12 hat Luiz Capitulino geschrieben:
On Fri, 01 Nov 2013 08:59:20 -0600
Eric Blake ebl...@redhat.com wrote:
On 11/01/2013 08:51 AM, Luiz Capitulino wrote:
On Wed, 30 Oct 2013 13:25:35 -0600
On 04.11.2013, at 14:32, Jan Kiszka jan.kis...@siemens.com wrote:
On 2013-11-04 14:30, Alexander Graf wrote:
On 04.11.2013, at 14:28, Jan Kiszka jan.kis...@siemens.com wrote:
On 2013-10-07 18:53, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Targets
04.11.2013 00:06, Jan Kiszka wrote:
On 2013-11-01 11:10, Michael Tokarev wrote:
[]
If Jan picks it up, that's fine. If not, I think it can go
to the trivial patches queue.
Works fine, applied to queues/slirp.
Okay, thank you Jan.
But this is not a trivial patch as the fix is not obvious
On 11/04/2013 04:26 AM, Zhanghaoyu (A) wrote:
Avoid starting a new migration task while the previous one still exist.
Signed-off-by: Zeng Junliang zengjunli...@huawei.com
---
It's best to put comments here...
migration.c | 34 ++
1 files changed, 22
Public bug reported:
USB Passthrough from host to guest is not working for a 32-bit Windows 7
guest.
The device appears in the device manager of Windows 7, but with Error
code 10: device cannot start. I have tried this with numerous USB
thumbdrives and a USB wireless NIC, all with the same
On 2013-11-04 14:55, Michael Tokarev wrote:
04.11.2013 00:06, Jan Kiszka wrote:
On 2013-11-01 11:10, Michael Tokarev wrote:
[]
If Jan picks it up, that's fine. If not, I think it can go
to the trivial patches queue.
Works fine, applied to queues/slirp.
Okay, thank you Jan.
But this
From: Dinar Valeev dval...@suse.de
This patch enables pie for PowerPC and ARM architectures
Signed-off-by: Dinar Valeev dval...@suse.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 91372f9..0130e7e 100755
--- a/configure
+++
On Sat, Nov 02, 2013 at 02:52:11PM +0100, Max Reitz wrote:
The actual size of the image file may differ depending on the Linux
kernel currently running on the host. Filtering out this value makes
this test pass in such cases.
Signed-off-by: Max Reitz mre...@redhat.com
---
Il 04/11/2013 11:46, Michael S. Tsirkin ha scritto:
Disable acpi build for isapc and no_kvmclock machine
types (used by xen), since acpi build currently expects pci.
Reported-by: Andreas Färber afaer...@suse.de
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Wait, Xen is not using
The bug occured on Ubuntu 13.04
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1247796
Title:
USB Passthrough not working for Windows 7 Embedded guest
Status in QEMU:
New
Bug description:
USB
On Mon, Nov 04, 2013 at 03:13:50PM +0100, Paolo Bonzini wrote:
Il 04/11/2013 11:46, Michael S. Tsirkin ha scritto:
Disable acpi build for isapc and no_kvmclock machine
types (used by xen), since acpi build currently expects pci.
Reported-by: Andreas Färber afaer...@suse.de
On Mon, 04 Nov 2013 13:48:03 +0100
Gerd Hoffmann kra...@redhat.com wrote:
Hi,
So maybe design that with memory hotplug in mind? Such as adding a new
qemu-specific type QEMU_RAM_HOTPLUG? Which seabios could use to reserve
the memory (but not add it to the e820 table for the guest)?
Le Monday 04 Nov 2013 à 17:30:10 (+0800), Fam Zheng a écrit :
Previously a BlockDriverState has only one dirty bitmap, so only one
caller (e.g. a block job) can keep track of writing. This changes the
dirty bitmap to a list and creates a BdrvDirtyBitmap for each caller, the
lifecycle is
On Mo, 2013-11-04 at 15:35 +0100, Igor Mammedov wrote:
On Mon, 04 Nov 2013 13:48:03 +0100
Gerd Hoffmann kra...@redhat.com wrote:
Hi,
So maybe design that with memory hotplug in mind? Such as adding a new
qemu-specific type QEMU_RAM_HOTPLUG? Which seabios could use to reserve
*** This bug is a duplicate of bug 685096 ***
https://bugs.launchpad.net/bugs/685096
duplicate: 685096
** This bug has been marked a duplicate of bug 685096
USB Passthrough not working for Windows 7 guest
** This bug has been marked a duplicate of bug 685096
USB Passthrough not
Il 17/10/2013 16:47, Paolo Bonzini ha scritto:
Only the first item of the array was ever looked at. No
practical effect, but still worth fixing.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
target-i386/kvm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, Oct 29, 2013 at 11:12:25AM +0100, Vincenzo Maffione wrote:
Looks pretty good, I think we can merge the next revision.
This patch only contains the simplest netmap backend for QEMU.
In particular, this backend implementation is still not
able to make use of batching on the TX side
mohamad.ge...@gmail.com writes:
Version 5
* Use pkg-config for lttng-ust and urcu-bp libraries in configure (hard-coded
libraries as a fallback)
* s/Qemu/QEMU in docs/tracing.txt
* Better dependencies for ust-generated files in trace/Makefile.obj
snip
Ping Stefan.
Any more need doing
petar.jovano...@rt-rk.com writes:
From: Petar Jovanovic petar.jovano...@imgtec.com
Creating target_structs header in linux-user/$arch/ and making
target_ipc_perm and target_shmid_ds its first inhabitants.
The struct defintions may/should be further fine-tuned by arch maintainers.
On Thu, Oct 31, 2013 at 10:41:46PM +0100, Andreas Tobler wrote:
Hi all,
the below patch is needed to compile qemu trunk on FreeBSD with gcc48,
clang will fail ;). Host x84_64-freebsd.
Installation will fail due to hardcoded /usr/bin/python in
scripts/acpi_extract.py
Thanks,
Hi,
Am 04.11.2013 07:41, schrieb 赵小强:
于 09/27/2013 01:30 PM, xiaoqiang zhao 写道:
From: xiaoqiang.zhao zxq_yx_...@163.com
Change apic and kvm/apic to use QOM interface.
Includes:
1. APICCommonState now use QOM realizefn
2. Remove DO_UPCAST() for APICCommonState
3. Use type constant
4.
1 - 100 of 175 matches
Mail list logo
