Hi all,
this patch series introduces a new command line option to restrict the
privilege of the xenstore connection. Used together with -runas, can
help secure the execution of QEMU in Dom0.
Changes in v3:
- introduce emulator_id and use in the xenstore path
- move qemu_xen_opts to xen-common.c
Introduce a new command line option xenopts with two suboptions:
xsrestrict (boolean) and emulator_id (numeric). When xsrestrict=on is
passed, QEMU will restrict the xenstore connection calling xs_restrict.
Also it won't initialize the pv backends as they require higher
privileges. The emulator_id
On Wed, Jun 10, 2015 at 08:00:55AM +0100, Jan Beulich wrote:
On 08.06.15 at 13:28, m...@redhat.com wrote:
On Mon, Jun 08, 2015 at 11:55:22AM +0100, Jan Beulich wrote:
while function 0 has
0x10: Base Address Register 0 = 0xca23000c (Memory space, 64-bit access,
prefetchable)
0x18:
On 29 May 2015, at 22:16, Martin Galvan
martin.gal...@tallertechnologies.com wrote:
... I think Peter M is the maintainer for Target-ARM.
Peter, is this OK to commit?
was this patch accepted? if so, where can I get it from?
regards,
Liviu
On 06/10/15 11:09, Marcel Apfelbaum wrote:
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
(7) At least one issue remains to be solved (designed) in QEMU, for both
SeaBIOS's and OVMF's sake: booting off devices that are located on
the PXB. The problem is with the bootorder fw_cfg file.
This patch introduces the blk_drain() function which allows to replace
blk_drain_all() when only one BlockDriverState needs to be drained.
Cc: Christian Borntraeger borntrae...@de.ibm.com
Cc: Cornelia Huck cornelia.h...@de.ibm.com
Cc: Kevin Wolf kw...@redhat.com
Cc: Paolo Bonzini
Each call of the virtio_blk_reset() function calls blk_drain_all(),
which works for all existing BlockDriverStates, while draining only
one is needed.
This patch replaces blk_drain_all() by blk_drain() in virtio_blk_reset().
Cc: Christian Borntraeger borntrae...@de.ibm.com
Cc: Cornelia Huck
Changes in v2:
- Patch block-backend: Introduce blk_drain() and replace blk_drain_all()
splitted to two.
- blk_drain() moved to above virtio_blk_data_plane_stop().
During reset the aio_poll() function is called at least amount_of_disks^2 times:
for_each disk
virtio_blk_reset()
The following patch will introduce a new option to restrict the
privilege of the xenstore connection. In that case, we do not want to
use multiple xenstore connections, but just the one, with lower
privileges.
For this reason, split the xenstore_record_dm_state calls for pv and hvm
machines, so
Am 10.06.2015 um 11:34 schrieb Fam Zheng:
On Wed, 06/10 11:18, Christian Borntraeger wrote:
Am 10.06.2015 um 04:12 schrieb Fam Zheng:
On Tue, 06/09 11:01, Christian Borntraeger wrote:
Am 09.06.2015 um 04:28 schrieb Fam Zheng:
On Tue, 06/02 16:36, Christian Borntraeger wrote:
Paolo,
I
On 10/06/15 10:54, Igor Mammedov wrote:
On Tue, 09 Jun 2015 15:35:21 +0100
Marc Zyngier marc.zyng...@arm.com wrote:
On 09/06/15 15:01, Peter Maydell wrote:
On 9 June 2015 at 15:00, Marc Zyngier marc.zyng...@arm.com wrote:
Yeah, what I had in mind was something along the lines of:
- kernel
On 10 June 2015 at 10:58, Liviu Ionescu i...@livius.net wrote:
On 29 May 2015, at 22:16, Martin Galvan
martin.gal...@tallertechnologies.com wrote:
... I think Peter M is the maintainer for Target-ARM.
Peter, is this OK to commit?
was this patch accepted?
No; as Peter C suggested,
On 10 June 2015 at 11:49, Daniel Gutson
daniel.gut...@tallertechnologies.com wrote:
El 10/6/2015 7:45, Peter Maydell peter.mayd...@linaro.org escribió:
No; as Peter C suggested, Martin split it into two patches.
Those patches then got code review, but I don't think Martin
has sent out a
On 06/10/15 12:06, Marcel Apfelbaum wrote:
On 06/09/2015 11:34 PM, Laszlo Ersek wrote:
On 06/07/15 11:23, Michael S. Tsirkin wrote:
On Sat, Jun 06, 2015 at 01:46:29AM +0200, Laszlo Ersek wrote:
OVMF downloads the ACPI linker/loader script from QEMU when the edk2
PCI
Bus driver globally
The problem was that my device started having activity before the
backend was finished to be set up.
On Wed, Jun 10, 2015 at 12:26 PM, Catalin Vasile
catalinvasil...@gmail.com wrote:
When is VIRTIO_CONFIG_S_DRIVER_OK set?
I've seen in vhost-scsi from qemu, that it sets it's own set_status()
2015-06-10 11:31+0100, Marc Zyngier:
On 10/06/15 10:54, Igor Mammedov wrote:
On Tue, 09 Jun 2015 15:35:21 +0100
Marc Zyngier marc.zyng...@arm.com wrote:
Indeed. I also missed the step that says kernel is able to convert
arbitrary MPIDR to vcpu_id in an efficient manner GICv3 is
definitely
After the commit 9b536adc (block: acquire AioContext in
bdrv_drain_all()) the aio_poll() function got called for every
BlockDriverState, in assumption that every device may have its own
AioContext. If we have thousands of disks attached, there are a lot of
BlockDriverStates but only a few
On 06/09/2015 11:34 PM, Laszlo Ersek wrote:
On 06/07/15 11:23, Michael S. Tsirkin wrote:
On Sat, Jun 06, 2015 at 01:46:29AM +0200, Laszlo Ersek wrote:
OVMF downloads the ACPI linker/loader script from QEMU when the edk2 PCI
Bus driver globally signals the firmware that PCI enumeration and
On Wed, 06/03 16:46, Alexander Yarygin wrote:
Each call of the virtio_blk_reset() function calls blk_drain_all(),
which works for all existing BlockDriverStates, while only one
BlockDriverState needs to be drained.
This patch introduces the blk_drain() function and replaces
blk_drain_all()
On Mon 08 Jun 2015 03:21:19 PM CEST, Stefan Hajnoczi stefa...@redhat.com
wrote:
Please structure the patches so that each statistic or group of
statistics has its own patch.
Yes, that's the plan.
uint64_t queue_depth[BLOCK_MAX_IOTYPE];
Average number of requests. Similar to the
On Wed, Jun 10, 2015 at 08:08:37AM +0100, Jan Beulich wrote:
On 08.06.15 at 11:30, m...@redhat.com wrote:
What happens if you disable SERR# in the command register
of 83:00.1?
We've just been told that with SERR not enabled in any of the
sibling endpoints the NMI still occurs. Not really
This change is a replicate of the previous two, just the calculation of polled
events is more delicate, and both read and write are polled.
Signed-off-by: Fam Zheng f...@redhat.com
---
slirp/slirp.c | 310 ++
1 file changed, 140
Signed-off-by: Fam Zheng f...@redhat.com
---
main-loop.c | 4 ++--
slirp/libslirp.h | 4 ++--
slirp/slirp.c| 4 ++--
stubs/slirp.c| 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/main-loop.c b/main-loop.c
index 18b7508..b3808ae 100644
--- a/main-loop.c
+++
repository at:
git://git.kraxel.org/qemu tags/pull-vga-20150610-1
for you to fetch changes up to 62232bf48456bda4058ceae05851bc58c1032338:
virtio-gpu/2d: add virtio gpu core code (2015-06-10 11:02:00 +0200)
stdvga: factor out
On 09.06.2015 20:03, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:19PM +0300, Vladimir Sementsov-Ogievskiy wrote:
From: Vladimir Sementsov-Ogievskiy vsement...@parallels.com
Persistent dirty bitmaps will be saved into qcow2 files. It may be used
as 'internal' bitmaps (for qcow2 drives)
Currently iohandler.c and asyn.c has a lot in common, except that iohandler is
hooked into main_loop_wait(), with qemu_iohandler_fill(). Likewise for slirp.
It is much cleaner to drive slirp fds with iohandler, and implement
iohandler with an AioContext. This series does these two things. It
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/display/vga-pci.c | 59 ++--
1 file changed, 30 insertions(+), 29 deletions(-)
diff --git a/hw/display/vga-pci.c b/hw/display/vga-pci.c
index fcbdde5..0ed44c7 100644
--- a/hw/display/vga-pci.c
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/display/vga-pci.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/hw/display/vga-pci.c b/hw/display/vga-pci.c
index 93c8b5d..fcbdde5 100644
--- a/hw/display/vga-pci.c
+++
Use the new dpy_ui_info_supported function.
Clarifies the control flow.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/spice-display.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/ui/spice-display.c b/ui/spice-display.c
index 4e6356a..cc4a6ce
On 09/06/15 13:37, Christian Borntraeger wrote:
Am 09.06.2015 um 12:19 schrieb Denis V. Lunev:
Excessive virtio_balloon inflation can cause invocation of OOM-killer,
when Linux is under severe memory pressure. Various mechanisms are
responsible for correct virtio_balloon memory management.
On 06/10/2015 04:45 AM, Dr. David Alan Gilbert wrote:
* Jason J. Herne (jjhe...@linux.vnet.ibm.com) wrote:
On 06/09/2015 04:06 AM, Dr. David Alan Gilbert wrote:
* Jason J. Herne (jjhe...@linux.vnet.ibm.com) wrote:
On 06/03/2015 02:11 PM, Jason J. Herne wrote:
On 06/03/2015 02:03 PM, Dr.
2.3.0 running RHEL7,1 little-endian version no problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463812
Title:
qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
Status in QEMU:
New
On 06/10/2015 02:19 AM, Vladimir Sementsov-Ogievskiy wrote:
+Dirty bitmaps is an optional header extension. It provides a
possibility of
+storing dirty bitmaps in qcow2 image. The fields are:
+
+ 0 - 3: nb_dirty_bitmaps
+ Number of dirty bitmaps contained in the
Ping?
Have these patches been missed?
On 2015/4/29 23:24, Shannon Zhao wrote:
The private qdev properties of virtio devices are only used by
themselves. As Peter suggested and like what virtio-blk has done, we
should move the private qdev properties into devices and don't expose
them to avoid
On Mon, June 1, 2015 8:48 pm, Paulo Alcantara wrote:
This interface provides some registers within a 32-byte range and can be
acessed through PCI-to-LPC bridge interface (PMBASE + 0x60).
It's commonly used as a watchdog timer to detect system lockups through
SMIs that are generated -- if
This patch adds virtio-gpu-pci, which is the pci proxy for the virtio
gpu device. With this patch in place virtio-gpu is functional. You
need a linux guest with a virtio-gpu driver though, and output will
appear pretty late in boot, once the kernel initialized drm and fbcon.
Written by Dave
This patch adds a virtio-vga device. It is simliar to virtio-gpu-pci,
but it also adds in vga compatibility, so guests without native
virtio-gpu support can drive the device in vga mode. It is compatible
with stdvga.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie
Public bug reported:
copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0,
corrupted; copied again, run, corrupted again.
Run the image on qemu 1.5.3, no problem.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification
On Thu, Jun 04, 2015 at 12:34:09PM +0200, Gerd Hoffmann wrote:
Hi,
Here comes the virtio 1.0 patch series, rebased to latest master.
Patches 1-23 are based on the old branch by cornelia mst.
Patches 24-30 are virtio-pci bits on top of that.
Patches 31-33 add virtio-pci support for the
On 06/10/15 13:55, Marcel Apfelbaum wrote:
On 06/10/2015 02:04 PM, Laszlo Ersek wrote:
On 06/10/15 11:09, Marcel Apfelbaum wrote:
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
(7) At least one issue remains to be solved (designed) in QEMU, for
both
SeaBIOS's and OVMF's sake: booting off
Hi,
Here is the code to add virtio-pci support for the virtio-gpu.
This series depends on the vga pull request sent earlier today
the the virtio-1.0 patch series sent last week.
vgabios support is not included yet as this depends on not-yet
merged changes in seabios.
This series with
Am 11.05.2015 um 17:45 hat Max Reitz geschrieben:
On 08.05.2015 19:21, Kevin Wolf wrote:
This allows iterating over all children of a given BDS, not only
including bs-file and bs-backing_hd, but also driver-specific
ones like VMDK extents or Quorum children.
Signed-off-by: Kevin Wolf
Oh and:
5) What's your disk image stored on - local disk or network?
6) WHat's the command line you're using for your guest
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463812
Title:
Hi,
Can you add some details about your host and guest please:
1) What's your host system? (ppc64 or x86? which os?)
2) What's the guest disk image format - raw or qcow2?
3) could you try some of the versions in between 2.3.0 and 1.5.3 ?
4) Is it just the 5.9 image that has
On Wed, Jun 10, 2015 at 11:43:19AM +0200, Igor Mammedov wrote:
On Tue, 9 Jun 2015 09:40:54 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On Tue, Jun 09, 2015 at 11:23:19AM +0200, Igor Mammedov wrote:
On Mon, 8 Jun 2015 12:51:39 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On 06/10/2015 02:04 PM, Laszlo Ersek wrote:
On 06/10/15 11:09, Marcel Apfelbaum wrote:
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
(7) At least one issue remains to be solved (designed) in QEMU, for both
SeaBIOS's and OVMF's sake: booting off devices that are located on
the PXB.
Hi Hervé,
On 03/06/2015 21:45, Hervé Poussineau wrote:
This fixes Windows NT 4.0/MIPS, which was always bugchecking with
IRQL_NOT_LESS_OR_EQUAL.
Signed-off-by: Hervé Poussineau hpous...@reactos.org
---
hw/dma/rc4030.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
Some convinience fluff: Add support for '-vga virtio', also add
virtio-vga to the list of vga cards so '-device virtio-vga' will
turn off the default vga.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie airl...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
On 10.06.15 at 13:43, m...@redhat.com wrote:
On Wed, Jun 10, 2015 at 08:00:55AM +0100, Jan Beulich wrote:
On 08.06.15 at 13:28, m...@redhat.com wrote:
On Mon, Jun 08, 2015 at 11:55:22AM +0100, Jan Beulich wrote:
while function 0 has
0x10: Base Address Register 0 = 0xca23000c (Memory
On 10.06.15 at 13:46, m...@redhat.com wrote:
I don't really know. The idea would be that device
is not designed for memory to be disabled when it's
active, and starts behaving in broken ways.
But you recall that we know the origin of the offending write is in
the hypervisor, and we also know
On Wed, Jun 10, 2015 at 11:43:19AM +0200, Igor Mammedov wrote:
On Tue, 9 Jun 2015 09:40:54 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On Tue, Jun 09, 2015 at 11:23:19AM +0200, Igor Mammedov wrote:
On Mon, 8 Jun 2015 12:51:39 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
El 10/6/2015 7:45, Peter Maydell peter.mayd...@linaro.org escribió:
On 10 June 2015 at 10:58, Liviu Ionescu i...@livius.net wrote:
On 29 May 2015, at 22:16, Martin Galvan
martin.gal...@tallertechnologies.com wrote:
... I think Peter M is the maintainer for Target-ARM.
Peter, is
On 06/10/2015 01:57 AM, Kevin Wolf wrote:
The statistic I'm interested in is the allocation of the block device
(the host offset, aka wr_highest_offset 72482304 above), and NOT the
usage pattern of the guest (the qcow2 protocol, wr_highest_offset
9129332224). But bdrv_lookup_bs() finds the
On Wed, Jun 10, 2015 at 03:02:21PM +0300, Denis V. Lunev wrote:
On 09/06/15 13:37, Christian Borntraeger wrote:
Am 09.06.2015 um 12:19 schrieb Denis V. Lunev:
Excessive virtio_balloon inflation can cause invocation of OOM-killer,
when Linux is under severe memory pressure. Various mechanisms
I'm running qemu 2.3.0 on a RHEL5.3/x86 box, 1.5.3 on a CentOS6.6/x86
box.
Date: Wed, 10 Jun 2015 12:25:22 +
From: dgilb...@redhat.com
To: w...@hotmail.com
Subject: [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk
corruption
Hi,
Can you add some details about your host
I'm using: qemu-system-ppc64 -hda ppcrhel5.img -cpu POWER7 -machine
type=pseries,usb=off -m 768 -nographic -net nic -net tap,ifname=tap0,script=no
It's on local disk.
same as on qemu 1.5.3.
Date: Wed, 10 Jun 2015 12:29:56 +
From: dgilb...@redhat.com
To: w...@hotmail.com
Subject: [Bug
On Wed, Jun 10, 2015 at 09:18:27PM +0800, Shannon Zhao wrote:
Ping?
Have these patches been missed?
I see them upstream. See e.g. da3e8a23492dbc13c4b70d90b6ae42970624e63a.
What's missing?
On 10.06.2015 11:19, Vladimir Sementsov-Ogievskiy wrote:
On 09.06.2015 20:03, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:19PM +0300, Vladimir
Sementsov-Ogievskiy wrote:
From: Vladimir Sementsov-Ogievskiy vsement...@parallels.com
Persistent dirty bitmaps will be saved into qcow2
Where the fd was added, compare the events with so-poll_events and call
qemu_set_fd_handler() to update if it's changed. Where the fd was not added,
call qemu_set_fd_handler() to remove it. Update slirp-do_slowtimo with a
return value. For simplicity, G_IO_HUP and G_IO_ERR are unnecessary to be
G_IO_PRI event is watched by slirp, add support of that to make future
refactoring possible.
Signed-off-by: Fam Zheng f...@redhat.com
---
aio-posix.c | 19 +++
aio-win32.c | 10 ++
include/block/aio.h | 8
3 files changed, 37 insertions(+)
diff
Signed-off-by: Fam Zheng f...@redhat.com
---
main-loop.c | 1 -
slirp/libslirp.h | 1 +
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/main-loop.c b/main-loop.c
index 631caa0..18b7508 100644
--- a/main-loop.c
+++ b/main-loop.c
@@ -24,7 +24,6 @@
#include qemu-common.h
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
Following up on this cross-posted message, I will send two patch sets,
one for QEMU (to qemu-devel) and another for OVMF (to edk2-devel). With
both in place, OVMF supports multiple PCI root buses.
Hi Laszlo,
Thank you for the patches.
Below I'm
This patch adds the core code for virtio gpu emulation,
covering 2d support.
Written by Dave Airlie and Gerd Hoffmann.
Signed-off-by: Dave Airlie airl...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/display/Makefile.objs | 2 +
hw/display/virtio-gpu.c| 918
Simliar to pci_vga_ioport_write.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/display/vga-pci.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/display/vga-pci.c b/hw/display/vga-pci.c
index ff5dfb2..93c8b5d 100644
--- a/hw/display/vga-pci.c
+++
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/standard-headers/linux/virtio_gpu.h | 204
include/standard-headers/linux/virtio_ids.h | 1 +
2 files changed, 205 insertions(+)
create mode 100644 include/standard-headers/linux/virtio_gpu.h
diff --git
Am 09.06.2015 um 17:46 hat John Snow geschrieben:
On 06/09/2015 05:24 AM, Kevin Wolf wrote:
Am 08.06.2015 um 22:49 hat John Snow geschrieben:
ce1ffea8 neglected to update the BdrvDirtyBitmap structure
itself for internal consistency. It's currently not an issue,
but for migration and
* Jason J. Herne (jjhe...@linux.vnet.ibm.com) wrote:
On 06/09/2015 04:06 AM, Dr. David Alan Gilbert wrote:
* Jason J. Herne (jjhe...@linux.vnet.ibm.com) wrote:
On 06/03/2015 02:11 PM, Jason J. Herne wrote:
On 06/03/2015 02:03 PM, Dr. David Alan Gilbert wrote:
* Jason J. Herne
This change is a replicate of the previous one.
Signed-off-by: Fam Zheng f...@redhat.com
---
slirp/slirp.c | 95 ---
1 file changed, 39 insertions(+), 56 deletions(-)
diff --git a/slirp/slirp.c b/slirp/slirp.c
index f648e6c..a031240 100644
On Mon, 06/08 16:53, Paolo Bonzini wrote:
On 08/06/2015 16:17, Eric Blake wrote:
+
+if (detect_zeroes == BLOCKDEV_DETECT_ZEROES_OPTIONS_UNMAP
+!(bdrv_flags BDRV_O_UNMAP)) {
+error_setg(errp, setting detect-zeroes to unmap is not allowed
+
Am 10.06.2015 um 00:35 hat Eric Blake geschrieben:
On 06/06/2015 07:38 PM, Eric Blake wrote:
Commit e2462113 allowed the ability to fire an event if a BDS
node exceeds a threshold during a write, but limited the option
to only work on node names. For convenience, expand this to
allow a
Am 09.06.2015 um 17:21 hat Eric Blake geschrieben:
On 06/09/2015 08:48 AM, Stefan Hajnoczi wrote:
I guess my @redhat.com email was received directly from Max because I
was in CC list. It didn't pass through Mailman. I saw the original,
unmodified list of CCs with Kevin included.
The
The field stores the current interesting events.
Signed-off-by: Fam Zheng f...@redhat.com
---
slirp/socket.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/slirp/socket.h b/slirp/socket.h
index 57e0407..0c49770 100644
--- a/slirp/socket.h
+++ b/slirp/socket.h
@@ -53,6 +53,7 @@ struct socket
On 06/06/2015 02:46 AM, Laszlo Ersek wrote:
The patch
apci: fix PXB behaviour if used with unsupported BIOS
uses the following condition to see if a PXB mem/IO chunk has *not* been
configured by the BIOS:
(!range_base || range_base range_limit)
When this condition evaluates to true,
On 06/06/2015 02:46 AM, Laszlo Ersek wrote:
The ACPI specification permits the _HID and _UID objects to evaluate to
strings. (See 6.1.5 _HID (Hardware ID) and 6.1.12 _UID (Unique ID) in
the ACPI v6.0 spec.)
With regard to related standards, the UEFI specification can also express
a device
On Wed, 06/10 11:18, Christian Borntraeger wrote:
Am 10.06.2015 um 04:12 schrieb Fam Zheng:
On Tue, 06/09 11:01, Christian Borntraeger wrote:
Am 09.06.2015 um 04:28 schrieb Fam Zheng:
On Tue, 06/02 16:36, Christian Borntraeger wrote:
Paolo,
I bisected
commit
On Tue, 09 Jun 2015 15:35:21 +0100
Marc Zyngier marc.zyng...@arm.com wrote:
On 09/06/15 15:01, Peter Maydell wrote:
On 9 June 2015 at 15:00, Marc Zyngier marc.zyng...@arm.com wrote:
Yeah, what I had in mind was something along the lines of:
- kernel computes its default MPDIR
- kernel
On Jun 8, 2015, at 11:12 AM, Peter Lieven p...@kamp.de wrote:
Am 28.05.2015 um 16:24 schrieb Vadim Rozenfeld:
On Thu, 2015-05-28 at 16:07 +0200, Peter Lieven wrote:
Hi,
we observed problems with Windows Update Services and Uploading Files from
a Windows System to other systems.
We
On 09/06/2015 15:55, Alex Bennée wrote:
Alex Bennée alex.ben...@linaro.org writes:
fred.kon...@greensocs.com writes:
From: KONRAD Frederic fred.kon...@greensocs.com
This mechanism replaces the existing load/store exclusive mechanism which seems
to be broken for multithread.
It follows the
Although it is pretty unusual the stride for the guest image and the
mirror image maintained by spice-display can be different. So use
separate variables for them.
Cc: qemu-sta...@nongnu.org
Reported-by: perrier vincent clow...@clownix.net
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
When is VIRTIO_CONFIG_S_DRIVER_OK set?
I've seen in vhost-scsi from qemu, that it sets it's own set_status()
member function for a virtio object, which checks for
VIRTIO_CONFIG_S_DRIVER_OK (from a status variable received as a
parameter) so it knows if it has to call vhost_scsi_start(),
On Tue, 9 Jun 2015 09:40:54 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On Tue, Jun 09, 2015 at 11:23:19AM +0200, Igor Mammedov wrote:
On Mon, 8 Jun 2015 12:51:39 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On Mon, Jun 08, 2015 at 11:51:03AM +0200, Igor Mammedov wrote:
On
SPCR is the Serial Port Console Redirection Table. See the document
linked from http://uefi.org/acpi. For serial port types, Interface
Type, see the documentation for the Debug Port Table 2 (DBG2).
Signed-off-by: Andrew Jones drjo...@redhat.com
Tested-by: Shannon Zhao shannon.z...@linaro.org
---
Signed-off-by: Andrew Jones drjo...@redhat.com
Tested-by: Shannon Zhao shannon.z...@linaro.org
---
hw/arm/virt-acpi-build.c | 43 ++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index
Adding this table allows the guest to boot without the console=
parameter added to the kernel command line. And anyway, kernel doc
Documentation/arm64/acpi_object_usage.txt says it's a required
table for arm64.
v3:
- no enums, document struct and value in build_spcr [mst]
- document earliest spec
The function originally behaves very badly when adding properties with [*]
suffix. Normally these are used for numbering IRQ pins. In order to find the
correct starting number the function started from zero and checked for
duplicates. This takes incredibly long time with large number of CPUs
Hi,
is there a way to query the current cursor position of the QEMU tablet or
QEMU Mouse? Or is there a way to see that the mouse was moved e.g. since
the last query?
There are input_* tracepoints. Also info mice monitor command tells
which is the active pointer device.
I currently have
This patch fixes exception handling in MIPS.
MIPS instructions generate several types of exceptions.
When exception is generated, it breaks the execution of the current translation
block. Implementation of the exceptions handling in MIPS does not correctly
restore icount for the instruction which
On 10/06/2015 10:03, Frederic Konrad wrote:
On 09/06/2015 15:55, Alex Bennée wrote:
Alex Bennée alex.ben...@linaro.org writes:
fred.kon...@greensocs.com writes:
From: KONRAD Frederic fred.kon...@greensocs.com
This mechanism replaces the existing load/store exclusive mechanism
which seems
On (Tue) 14 Apr 2015 [18:03:37], Dr. David Alan Gilbert (git) wrote:
From: Dr. David Alan Gilbert dgilb...@redhat.com
Postcopy needs a method to send messages from the destination back to
the source, this is the 'return path'.
Wire it up for 'socket' QEMUFile's using a dup'd fd.
I'm not
Create a global AioContext instance and let its GSource to handle the
events.
Signed-off-by: Fam Zheng f...@redhat.com
---
include/qemu/main-loop.h | 10 +++-
iohandler.c | 124 ++-
main-loop.c | 5 +-
3 files changed, 37
It has always been compiled out. Remove it before we refactor the rest
part of slirp poll.
Signed-off-by: Fam Zheng f...@redhat.com
---
slirp/slirp.c| 40
slirp/slirp_config.h | 4
2 files changed, 44 deletions(-)
diff --git a/slirp/slirp.c
Am 10.06.2015 um 04:12 schrieb Fam Zheng:
On Tue, 06/09 11:01, Christian Borntraeger wrote:
Am 09.06.2015 um 04:28 schrieb Fam Zheng:
On Tue, 06/02 16:36, Christian Borntraeger wrote:
Paolo,
I bisected
commit a0710f7995f914e3044e5899bd8ff6c43c62f916
Author: Paolo Bonzini
On Wed, 06/10 17:11, Fam Zheng wrote:
On Mon, 06/08 16:53, Paolo Bonzini wrote:
On 08/06/2015 16:17, Eric Blake wrote:
+
+if (detect_zeroes == BLOCKDEV_DETECT_ZEROES_OPTIONS_UNMAP
+!(bdrv_flags BDRV_O_UNMAP)) {
+error_setg(errp, setting detect-zeroes
On 10/06/15 16:13, Michael S. Tsirkin wrote:
On Wed, Jun 10, 2015 at 03:02:21PM +0300, Denis V. Lunev wrote:
On 09/06/15 13:37, Christian Borntraeger wrote:
Am 09.06.2015 um 12:19 schrieb Denis V. Lunev:
Excessive virtio_balloon inflation can cause invocation of OOM-killer,
when Linux is
In case of live migration with legacy guest (without
VIRTIO_NET_F_GUEST_ANNOUNCE)
a message is added between QEMU and the vhost client/backend.
This message provides the RARP content, prepared by QEMU, to the vhost
client/backend.
The vhost client/backend is responsible to send the RARP.
Some vhost client/backend are able to support live migration.
To provide this service the following features must be added:
1. GARP from guest after live migration:
the VIRTIO_NET_F_GUEST_ANNOUNCE capability is added to vhost-net when netdev
backend is vhost-user to let virtio-net NIC
In the block layer functions that determine options for a child block
device, it's a common pattern to either copy options from the parent's
options or to set a default string if the option isn't explicitly set
yet for the child. Provide convenience functions so that it becomes a
one-liner for
When reopening an image, the block layer already takes care to reopen
bs-file as well with recalculated inherited flags. The same must happen
for any other child (most notably missing before this patch: backing
files).
If bs-file (or any other child) didn't originally inherit from bs, e.g.
Besides standardising on a single interface for opening child nodes,
this simplifies the .bdrv_open() implementation of the quorum block
driver by using block layer functionality for handling BlockdevRefs.
Signed-off-by: Kevin Wolf kw...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
bdrv_swap() requires that there are no requests in flight on either of
the two devices. The request coroutine would work on the wrong
BlockDriverState object (with bs-opaque even being interpreted as a
different type potentially) and all sorts of bad things would result
from this.
The currently
1 - 100 of 243 matches
Mail list logo
