主题: [Qemu-devel] [PATCH v8 00/30] modify boot order of guest, and take
effect after rebooting
From: Gonglei arei.gong...@huawei.com
Sometimes, we want to modify boot order of a guest, but no need to
shutdown
it. We can call dynamic changing bootindex of a guest, which can be assured
On 2014-09-11 07:06, Zhang Haoyu wrote:
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy between
the EOI writing and irq delivery (system bus latency?). So we need to emulate
this behavior.
Reviewed-by: Benoît Canet benoit.ca...@nodalink.com
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi/block-core.json | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index bf0cb23..35191b4 100644
--- a/qapi/block-core.json
This is an analogue to Linux null_blk. It can be used for testing or
benchmarking block device emulation and general block layer
functionalities such as coroutines and throttling, where disk IO is not
necessary or wanted.
Use null-aio:// for AIO version, and null-co:// for coroutine version.
v7: Add Benoît's rev-by line in patch 2.
Improved help text in patch 1. (Benoît)
v6: Don't inherit from BlockdevOptionsFile. (Stefan)
Use .bdrv_co_readv instead of .bdrv_read. (Kevin)
Sort items in qapi schema definitions in patch 2 3.
Fam Zheng (3):
block: Introduce null drivers
On (Sun) 07 Sep 2014 [17:46:26], Zhang Haoyu wrote:
Hi, Paolo, Amit,
any ideas?
I'll check this, thanks for testing with Linux guests.
Amit
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi/block-core.json | 38 +++---
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 35191b4..5adef27 100644
--- a/qapi/block-core.json
+++
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
Why does hotplugging use a different name?
This also affects RDMA live migration - we are explicitly looking up
pc.ram ram blocks and pinning them for memory registration with Linux.
Are we? I cannot see any code that special cases pc.ram
On 09/11/2014 02:22 PM, Paolo Bonzini wrote:
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
Why does hotplugging use a different name?
This also affects RDMA live migration - we are explicitly looking up
pc.ram ram blocks and pinning them for memory registration with Linux.
Are we? I
On 2014/9/11 14:27, Michael R. Hines wrote:
On 09/11/2014 02:22 PM, Paolo Bonzini wrote:
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
Why does hotplugging use a different name?
This also affects RDMA live migration - we are explicitly looking up
pc.ram ram blocks and pinning them for
On Wed, 09/10 10:13, Markus Armbruster wrote:
Creating an anonymous BDS can't fail. Make that obvious.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
block.c | 26 +++---
block/iscsi.c | 2 +-
block/vvfat.c | 2 +-
blockdev.c
+static void del_original_boot_device(DeviceState *dev, const char *suffix)
Hmm, now we have two simliar delete functions. One which deletes all
entries belonging to a device, and one deleting only in case the suffix
matches (the later being needed to handle the floppy case I guess?).
Can't we
When the guest performs kexec() (for example, as a part of kdump),
new kernel does PCI probing. As a part of it, PCI_COMMAND_MASTER
gets disabled which disables bus master memory region.
Since ohci_frame_boundary() timer is not stopped at this point
as OHCI device was not reset, the device tries
On Do, 2014-09-11 at 17:11 +1000, Alexey Kardashevskiy wrote:
When the guest performs kexec() (for example, as a part of kdump),
new kernel does PCI probing. As a part of it, PCI_COMMAND_MASTER
gets disabled which disables bus master memory region.
Since ohci_frame_boundary() timer is not
Il 10/09/2014 17:43, Walid Nouri ha scritto:
The drive-mirror (and live migration) does not rely on shared storage
and allow live block device copy and incremental syncing.
I think your analysis is right. However, just for completeness I'll
note that quorum doesn't need shared storage.
To do
Hi,
Subject: Re: [PATCH v9 05/30] bootindex: rework add_boot_device_path
function
+static void del_original_boot_device(DeviceState *dev, const char *suffix)
Hmm, now we have two simliar delete functions. One which deletes all
entries belonging to a device, and one deleting only in
Zhu Guihua zhugh.f...@cn.fujitsu.com writes:
This patch provides HMP equivalent of QMP query-memory-devices command. By
this command info memory-devices, user can know all information about
hotpluggable memmory device such as id. With id of devices, hot removing
hotpluggable memory devices
Il 11/09/2014 07:41, Fam Zheng ha scritto:
v6: Drop bdrv_em_aiocb_info.cancel in patch 5. (Paolo)
v5: Fix IDE callback. (Paolo)
Fix blkdebug. (Paolo)
Drop the DMA fix which is independent of this series. (Paolo)
Incorperate Yuan's patch on quorum_aio_cancel. (Benoît)
Commit
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy
between
the EOI writing and irq delivery (system bus latency?). So we need to emulate
this behavior. Otherwise, for a guest who haven't
主题: RE: [Qemu-devel] [PATCH v8 00/30] modify boot order of guest, and
take
effect after rebooting
主题: [Qemu-devel] [PATCH v8 00/30] modify boot order of guest, and
take effect after rebooting
From: Gonglei arei.gong...@huawei.com
Sometimes, we want to modify boot
From: Gonglei arei.gong...@huawei.com
qerror_report() is a transitional interface to help with converting
existing HMP commands to QMP. It should not be used elsewhere.
Replace by error_report().
Signed-off-by: Gonglei arei.gong...@huawei.com
---
hw/usb/redirect.c | 6 +++---
1 file changed, 3
From: Gonglei arei.gong...@huawei.com
qerror_report() is a transitional interface to help with converting
existing HMP commands to QMP. It should not be used elsewhere.
Gonglei (2):
redirect.c: Don't use qerror_report()
dev-network: Don't use qerror_report_err()
hw/usb/dev-network.c | 2
From: Gonglei arei.gong...@huawei.com
qerror_report_err() is a transitional interface to help with
converting existing HMP commands to QMP. It should not be used
elsewhere.
Signed-off-by: Gonglei arei.gong...@huawei.com
---
hw/usb/dev-network.c | 2 +-
1 file changed, 1 insertion(+), 1
On 09/11/2014 05:22 PM, Gerd Hoffmann wrote:
On Do, 2014-09-11 at 17:11 +1000, Alexey Kardashevskiy wrote:
When the guest performs kexec() (for example, as a part of kdump),
new kernel does PCI probing. As a part of it, PCI_COMMAND_MASTER
gets disabled which disables bus master memory region.
Eric Blake ebl...@redhat.com writes:
On 09/10/2014 05:03 AM, Benoît Canet wrote:
The Wednesday 10 Sep 2014 à 10:13:30 (+0200), Markus Armbruster wrote :
Creating an anonymous BDS can't fail. Make that obvious.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
/* create a new block
Il 10/09/2014 16:34, Pavel Dovgalyuk ha scritto:
This patch initializes monitor for gdbstub with the qemu_chr_alloc function
instead of just allocating the memory. Initialization function call
is required, because it also creates chr_write_lock mutex, which is used
when writing to this
Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 10 Sep 2014 à 10:13:30 (+0200), Markus Armbruster wrote :
Creating an anonymous BDS can't fail. Make that obvious.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
block.c | 26 +++---
On 11.09.14 04:55, Alexey Kardashevskiy wrote:
On 09/11/2014 07:17 AM, Alexander Graf wrote:
On 10.09.14 17:00, Alexey Kardashevskiy wrote:
On 09/10/2014 11:03 PM, Alexander Graf wrote:
On 29.08.14 12:12, Alexey Kardashevskiy wrote:
This implements DDW for VFIO. Host kernel support is
Hi Stefan,
Sorry for delay in response as I was sick. Actually I have below two very
important queries. Answer to both queries are valuable to me. We are planning
to add block driver with the new protocol after proper testing.
1. With my new network based disk protocol, if I use 'raw' format,
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy between
the EOI writing and irq delivery (system bus latency?). So we need to emulate
this behavior. Otherwise, for a guest who haven't register a
On Tue, Sep 09, 2014 at 11:25:38AM +0200, Marc Marí wrote:
Signed-off-by: Marc Marí marc.mari.barc...@gmail.com
---
tests/libqos/virtio.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Missing a commit description. Please justify this patch. Why do you
need to bump the clock
Subject: [Qemu-devel] [PATCH] kvm: ioapic: conditionally delay irq delivery
duringeoi broadcast
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy between
the EOI writing and irq delivery
On Thu, Aug 28, 2014 at 9:06 AM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
After ACPI get a signal to eject a vCPU, the vCPU must be
removed from CPU list，before the vCPU really removed, then
release the all related vCPU objects.
But we do not close KVM vcpu fd, just record it into a list, in
Increase the clock step to avoid Travis failure in some builds due to
overagressive timeout.
Signed-off-by: Marc Marí marc.mari.barc...@gmail.com
---
tests/libqos/virtio.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/libqos/virtio.c b/tests/libqos/virtio.c
Il 08/09/2014 15:28, Chris Webb ha scritto:
divide error: [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 743 Comm: syslogd Not tainted 3.16.2-guest #2
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014
On 09/11/2014 05:35 PM, Bharata B Rao wrote:
On Thu, Aug 28, 2014 at 9:06 AM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
After ACPI get a signal to eject a vCPU, the vCPU must be
removed from CPU list，before the vCPU really removed, then
release the all related vCPU objects.
But we do not
Bharata, this not expected. info cpus should indicate report proper number
of cpus after deletion.
Anshul Makkar
On Thu, Sep 11, 2014 at 11:35 AM, Bharata B Rao bharata@gmail.com
wrote:
from
Kevin Wolf kw...@redhat.com writes:
Am 10.09.2014 um 10:13 hat Markus Armbruster geschrieben:
A block device consists of a frontend device model and a backend.
A block backend has a tree of block drivers doing the actual work.
The tree is managed by the block layer.
We currently use a
On 09/11/2014 05:35 PM, Bharata B Rao wrote:
On Thu, Aug 28, 2014 at 9:06 AM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
After ACPI get a signal to eject a vCPU, the vCPU must be
removed from CPU list，before the vCPU really removed, then
release the all related vCPU objects.
But we do not
Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 10 Sep 2014 10:13:31 (+0200), Markus Armbruster wrote :
A block device consists of a frontend device model and a backend.
A block backend has a tree of block drivers doing the actual work.
The tree is managed by the block layer.
On Thu, 11 Sep 2014 11:04:10 +0800
Gu Zheng guz.f...@cn.fujitsu.com wrote:
Hi Igor,
On 09/10/2014 09:28 PM, Igor Mammedov wrote:
On Wed, 3 Sep 2014 17:06:13 +0800
Gu Zheng guz.f...@cn.fujitsu.com wrote:
Signed-off-by: Gu Zheng guz.f...@cn.fujitsu.com
---
hw/acpi/cpu_hotplug.c
Hi,
To be precise, it is kdump.
Ok, kdump is a different story, radically turn off all DMA is reasonable
in that case, normal driver shutdown might be unreliable after panic and
it also changes system state too much for a useful dump.
ohci (and probably others too, but without spamming the
Zeroing is relatively expensive since we have big request structures.
VirtQueueElement ( 4k) and sense_buf (256 bytes) are two points to look at.
This visibly reduces overhead of request handling when testing with the
unmerged null driver and virtio-scsi dataplane. Before, the issue is very
Zeroing sense buffer for each scsi request is not efficient, we can just
leave it uninitialized because sense_len is set to 0.
Move the implicitly zeroes fields to the end of the structure and use a
partial memset.
Also change g_malloc0 to g_slice_alloc.
Signed-off-by: Fam Zheng f...@redhat.com
The VirtQueueElement is a very big structure ( 4k), since it will be
initialzed by virtqueue_pop, we can save the expensive zeroing here.
This saves a few nanoseconds per request in my test:
[fio-test] rw bs iodepthjobs bw iops
latency
On Wed, 10 Sep 2014 16:38:09 +0800
Zhu Guihua zhugh.f...@cn.fujitsu.com wrote:
This patch provides HMP equivalent of QMP query-memory-devices command. By
this command info memory-devices, user can know all information about
hotpluggable memmory device such as id. With id of devices, hot
Seems that we get a crash when we live-migrate a VMs using virtio-net-pci
(vhost=on).
This worked in 2.1.0. Any ideas?
I am pleased to announce that the QEMU v2.1.1 stable release is now available
at:
I found a new trace - using the ipipe patch that I have, there seems to be an
issue in the 3.4 kernels, but as it looks also in the 3.10 kernels.
http://www.xenomai.org/pipermail/xenomai/2013-March/027865.html
Is there an update on that already existing? It was not completely clear
if this issue
Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 10 Sep 2014 à 10:13:31 (+0200), Markus Armbruster wrote :
A block device consists of a frontend device model and a backend.
A block backend has a tree of block drivers doing the actual work.
The tree is managed by the block layer.
Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 10 Sep 2014 à 14:40:42 (+0200), Benoît Canet wrote :
The Wednesday 10 Sep 2014 à 10:13:31 (+0200), Markus Armbruster wrote :
[...]
diff --git a/qemu-img.c b/qemu-img.c
index 4490a22..bad3f64 100644
--- a/qemu-img.c
+++
The Wednesday 10 Sep 2014 à 10:13:35 (+0200), Markus Armbruster wrote :
Signed-off-by: Markus Armbruster arm...@redhat.com
---
block.c | 43 +++
block/block-backend.c | 4
include/block/block_int.h | 2 --
3 files changed,
The in-kernel OpenPIC emulation only supports a single map. However, we
map the OpenPIC at 2 locations: The CPU visible one and the PCI visible
one. For KVM acceleration, we only care about the first one.
To make sure that we only map that first mapping and not the PCI map that
happens
On 11.09.14 12:14, bogdan.purcare...@freescale.com wrote:
-Original Message-
From: Alexander Graf [mailto:ag...@suse.de]
Sent: Wednesday, September 10, 2014 4:56 PM
To: Purcareata Bogdan-B43198; Wood Scott-B07421
Cc: Caraman Mihai Claudiu-B02008; qemu-...@nongnu.org;
On 09/11/2014 08:15 PM, Gerd Hoffmann wrote:
Hi,
To be precise, it is kdump.
Ok, kdump is a different story, radically turn off all DMA is reasonable
in that case, normal driver shutdown might be unreliable after panic and
it also changes system state too much for a useful dump.
ohci
Hi,
Another question - I noticed that XHCI migration is broken in quite recent
upstream QEMU, smells like memory corruption. Is it just me or just PPC or
is it known issue?
2.0 - 2.1 migration being broken is a known issue (patch for that one
was on the list earlier this week, unfortunately
On 10 September 2014 06:55, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
Qemu 2.1.1 release is delayed a bit, so I have the chance to squeeze
in a last-minute fix for a migration compatibility bug in xhci.
please pull,
Gerd
The following changes since commit
The Wednesday 10 Sep 2014 à 10:13:36 (+0200), Markus Armbruster wrote :
Signed-off-by: Markus Armbruster arm...@redhat.com
---
block-migration.c | 30 +++---
block.c | 9 -
blockdev.c| 31 +--
-Original Message-
From: Alexander Graf [mailto:ag...@suse.de]
Sent: Wednesday, September 10, 2014 4:56 PM
To: Purcareata Bogdan-B43198; Wood Scott-B07421
Cc: Caraman Mihai Claudiu-B02008; qemu-...@nongnu.org; qemu-devel@nongnu.org
Subject: Re: [Qemu-ppc] [PATCH 2/2] PPC:
Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 10 Sep 2014 à 10:13:32 (+0200), Markus Armbruster wrote :
The pointer from BlockBackend to BlockDriverState is a strong
reference, managed with bdrv_ref() / bdrv_unref(), the back-pointer is
a weak one.
Convenience function
Just a few nits...
Il 11/09/2014 12:16, Fam Zheng ha scritto:
+uint32_t sense_len;
sense_len is initialized to zero, might as well do that via memset.
+uint8_t sense[SCSI_SENSE_BUF_SIZE];
+bool enqueued;
+bool io_canceled;
+
On 29 August 2014 17:49, Richard Henderson r...@twiddle.net wrote:
On 08/29/2014 04:21 AM, Peter Maydell wrote:
Peter Maydell (10):
exec.c: Relax restrictions on watchpoint length and alignment
exec.c: Provide full set of dummy wp remove functions in user-mode
exec.c: Record watchpoint
On 09/11/2014 08:38 PM, Gerd Hoffmann wrote:
Hi,
Another question - I noticed that XHCI migration is broken in quite recent
upstream QEMU, smells like memory corruption. Is it just me or just PPC or
is it known issue?
2.0 - 2.1 migration being broken is a known issue (patch for that one
On 10 September 2014 11:59, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
Add an address limit input parameter to load_dtb() so that we can
tell it how much memory the dtb is allowed to consume. If the dtb
doesn't fit, return 0, otherwise return the actual size of the
loaded dtb, or -1 on
Similar nits to patch 1, but a good patch nevertheless!
Il 11/09/2014 12:16, Fam Zheng ha scritto:
The VirtQueueElement is a very big structure ( 4k), since it will be
initialzed by virtqueue_pop, we can save the expensive zeroing here.
This saves a few nanoseconds per request in my test:
Am 10.09.2014 um 17:49 hat Benoît Canet geschrieben:
On Wed, Sep 10, 2014 at 09:14:35AM -0600, Eric Blake wrote:
On 09/10/2014 02:54 AM, Fam Zheng wrote:
Let's think of a situation that recursive blockers protect but
backing_blocker does not:
a - b - c - d
c is the backing
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: 11 September 2014 01:33
To: Owen Smith
Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org; Stefano Stabellini
Subject: Re: [PATCH 1/3] xenfb: Unregister keyboard event handler correctly
On
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: 11 September 2014 02:01
To: Owen Smith
Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org; Stefano Stabellini
Subject: Re: [PATCH 2/3] xenfb: Add option to use grant ref for shared page.
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: 11 September 2014 02:23
To: Owen Smith
Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org; Stefano Stabellini
Subject: Re: [PATCH 3/3] xenfb: Add feature-no-abs-rescale for Windows
PV
The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
device_name[] is can become non-empty only in bdrv_new_named() and
bdrv_move_feature_fields(). The latter is used only to undo damage
done by bdrv_swap(). The former is called only by blk_new_with_bs().
Therefore, when a
On 10 September 2014 11:56, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
This patch series makes the console code use pixman format codes
internally. It also adds some helper functions for gfx emulation
code. I have some wip patches for pl110 using them, but they are
not ready yet so they
The Thursday 11 Sep 2014 à 13:34:33 (+0200), Benoît Canet wrote :
The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
device_name[] is can become non-empty only in bdrv_new_named() and
bdrv_move_feature_fields(). The latter is used only to undo damage
done by
Markus Armbruster arm...@redhat.com writes:
Kevin Wolf kw...@redhat.com writes:
[...]
diff --git a/qemu-img.c b/qemu-img.c
index 4490a22..bad3f64 100644
--- a/qemu-img.c
+++ b/qemu-img.c
Won't comment on each hunk in qemu-img, but in many cases, on
bdrv_new_open() failure, blk is leaked.
Public bug reported:
A fresh installation of Windows Millennium Edition (Windows ME, WinME)
as guest OS on qemu interprets qemu's videocards as Number Nine Imagine
128 with the consequence, that
1. It is impossible to change color depth.
2. WinME uses the i128.drv Driver that is shipped with
Here's a screenshot of the driver problem, that WinME shows up.
It says error code 23, whatever that means.
** Attachment added: qemu_windme_number_nine_core_23.png
https://bugs.launchpad.net/qemu/+bug/1368178/+attachment/4201320/+files/qemu_windme_number_nine_core_23.png
--
You received
Here's a picture of the allowed color depth.
As long as the videocard isn't detected properly, using another driver won't
help and without another driver the color depth stays at 16 colors.
** Attachment added: qemu_windme_color_depth_problem.png
In console mode, info pci gives the following information (see attachted
screenshot)
** Attachment added: qemu_windme_monitor_mode_info_pci.png
https://bugs.launchpad.net/qemu/+bug/1368178/+attachment/4201333/+files/qemu_windme_monitor_mode_info_pci.png
--
You received this bug
Could you please provide backtrace and give more details to reproduce
the issue?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1361912
Title:
qemu-mips64 Segmentation fault
Status in QEMU:
New
The Wednesday 10 Sep 2014 à 10:13:39 (+0200), Markus Armbruster wrote :
Signed-off-by: Markus Armbruster arm...@redhat.com
---
blockdev.c | 3 +--
hw/arm/collie.c | 9 +
hw/arm/gumstix.c | 5 +++--
On 09/10/2014 03:09 PM, Alexander Graf wrote:
On 09.09.14 09:31, Eric Auger wrote:
A new common module is created. It implements all functions
that have no device specificity (PCI, Platform).
This patch only consists in move (no functional changes)
Signed-off-by: Kim Phillips
On 11.09.14 14:11, Eric Auger wrote:
On 09/10/2014 03:09 PM, Alexander Graf wrote:
On 09.09.14 09:31, Eric Auger wrote:
A new common module is created. It implements all functions
that have no device specificity (PCI, Platform).
This patch only consists in move (no functional changes)
On Tue, 9 Sep 2014 21:34:46 +1000
Alexey Kardashevskiy a...@ozlabs.ru wrote:
This reverts commit c40708176a6b52b73bec14796b7c71b882ceb102.
The idea not to swap bytes at all did not work out as MMIO interface
is defined as target host endian and it is always big-endian for PPC64
s/target
The Wednesday 10 Sep 2014 à 10:13:40 (+0200), Markus Armbruster wrote :
I'll use BlockDriverAIOCB with block backends shortly, and the name is
going to fit badly there. It's a block layer thing anyway, not just a
block driver thing.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
On 04/09/14 18:38, Stefan Hajnoczi wrote:
From: Michael S. Tsirkin m...@redhat.com
On vm stop, virtio changes vm_running state
too soon, so callbacks can get envoked with
vm_running = false;
Cc: qemu-sta...@nongnu.org
Cc: Jason Wang jasow...@redhat.com
Signed-off-by: Michael S. Tsirkin
On 9/10/2014 5:43 PM, Pierre Mallard wrote:
On Wed, Sep 10, 2014 at 7:15 PM, Tom Musta tommu...@gmail.com
mailto:tommu...@gmail.com wrote:
(1) Eliminate the TARGET_PPC64 checks for all six FP Doubleword Integer
Conversion instructions.
There is also fcfids and fcfidus which
Public bug reported:
On a fresh installation of Windows Millennium (WinME) in qemu, Windows
Me isn't able to find the CD-ROM drive or additional hard drives other
than -hda at first place.
Only if i add manually an IDE controller driver in Windows ME's device manager,
the CD-ROM inserted in
On Thu, Sep 11, 2014 at 02:19:42PM +0200, Christian Borntraeger wrote:
On 04/09/14 18:38, Stefan Hajnoczi wrote:
From: Michael S. Tsirkin m...@redhat.com
On vm stop, virtio changes vm_running state
too soon, so callbacks can get envoked with
vm_running = false;
Cc:
On Thu, Sep 11, 2014 at 3:23 PM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
On 09/11/2014 05:35 PM, Bharata B Rao wrote:
On Thu, Aug 28, 2014 at 9:06 AM, Gu Zheng guz.f...@cn.fujitsu.com wrote:
After ACPI get a signal to eject a vCPU, the vCPU must be
removed from CPU list，before the vCPU really
On 11/09/14 14:38, Michael S. Tsirkin wrote:
This broke managedsave on s390x:
qemu-system-s390x: hw/net/virtio-net.c:1348: virtio_net_save: Assertion
`!n-vhost_started' failed.
reverting that commit makes it working again.
Any ideas?
Christian
Does it help if you apply
[PULL
Am 11.09.2014 um 07:58 schrieb Gonglei (Arei):
./qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -name redhat6.2 -drive \
file=/home/win7_32_2U,if=none,id=drive-ide0-0-0 -device ide-hd,bus=ide.0,\
unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive \
Commit 3718d8ab65f68de2acccbe6a315907805f54e3cc (block: Replace in_use
with operation blocker) broke the error path because it consumed
local_err instead of propagating it.
The caller has no way to know that the function failed. This caused
virtio-blk to start successfully even though there was
Subject: [Qemu-devel] [PATCH] kvm: ioapic: conditionally delay irq delivery
duringeoi broadcast
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy
between
the EOI writing and irq delivery
On 09/11/2014 05:34 AM, Benoît Canet wrote:
The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
device_name[] is can become non-empty only in bdrv_new_named() and
bdrv_move_feature_fields(). The latter is used only to undo damage
done by bdrv_swap(). The former is called
On 09/11/2014 06:49 AM, Stefan Hajnoczi wrote:
Commit 3718d8ab65f68de2acccbe6a315907805f54e3cc (block: Replace in_use
with operation blocker) broke the error path because it consumed
local_err instead of propagating it.
The caller has no way to know that the function failed. This caused
On 05/09/14 09:33, Jens Freimann wrote:
Cornelia, Christian, Alex,
here are two css patches and a small sclp cleanup.
Patch 1 remove duplicate defines in SCLP code
Patch 2 adds support for format-0 ccws
Patch 3 a css bugfix adding a limit of 255 to ccws chains without data
transfer
Currently, we call ioapic_service() immediately when we find the irq is still
active during eoi broadcast. But for real hardware, there's some dealy between
the EOI writing and irq delivery (system bus latency?). So we need to emulate
this behavior. Otherwise, for a guest who haven't register a
The Thursday 11 Sep 2014 à 07:00:41 (-0600), Eric Blake wrote :
On 09/11/2014 05:34 AM, Benoît Canet wrote:
The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
device_name[] is can become non-empty only in bdrv_new_named() and
bdrv_move_feature_fields(). The latter is
attached the trace.dat (tar-gzipped) as recommended. Hope this helps finding
the issue. The file should capture the following:
- windows 8 with screen that shows that the last boot attempts failed
- issued system_reset on qemu commandline
- startup of windows 8 that stalls
** Attachment added:
Quoting Dietmar Maurer (2014-09-11 04:55:05)
Seems that we get a crash when we live-migrate a VMs using virtio-net-pci
(vhost=on).
This worked in 2.1.0. Any ideas?
Is this what you're seeing on the source side?
qemu-system-x86_64: /home/mdroth/w/qemu3.git/hw/net/virtio-net.c:1348:
On Thu, Sep 11, 2014 at 09:11:40AM -0500, Michael Roth wrote:
Quoting Dietmar Maurer (2014-09-11 04:55:05)
Seems that we get a crash when we live-migrate a VMs using virtio-net-pci
(vhost=on).
This worked in 2.1.0. Any ideas?
Is this what you're seeing on the source side?
1 - 100 of 217 matches
Mail list logo
