On 11 June 2015 at 03:21, Gonglei arei.gong...@huawei.com wrote:
Failed to build on SUSE11.3:
That's because g_malloc0_n() introduced since glib-2.24,
but QEMU just require glib-2.22.
Thanks for the catch -- I do have a glib-2.22 system in my
pre-pull build tests, but it's not x86/Linux, so
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Daniel P. Berrange berra...@redhat.com
---
ui/gtk.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/ui/gtk.c b/ui/gtk.c
index 126326a..df2a79e 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -1917,12 +1917,19 @@
repository at:
git://git.kraxel.org/qemu tags/pull-gtk-20150611-1
for you to fetch changes up to 060ab76356fff6a420bc881a574c40a5dda086af:
gtk: don't exit early in case gtk init fails (2015-06-11 11:37:56 +0200)
gtk: don't exit early
On 11.06.2015 01:33, John Snow wrote:
On 06/09/2015 12:01 PM, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:22PM +0300, Vladimir Sementsov-Ogievskiy wrote:
+BdrvDirtyBitmap *bdrv_load_dirty_bitmap(BlockDriverState *bs,
+BlockDriverState *file,
+
Hi Paolo,
On Tue, May 5, 2015 at 9:18 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Patches 1 and 2 enable support from more than 8 MMU modes in TCG (patch
1 is in the targets, patch 2 is in cpu-defs.h). The TLB size is reduced
proportionally on targets where that is necessary.
This is a very
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The sysbus_get_fw_dev_path() function formats OpenFirmware device path
nodes (driver-name@unit-address) for sysbus devices. The first choice
for unit-address is the base address of the device's first MMIO region.
The second choice is its first IO port.
On 06/11/15 12:29, Marcel Apfelbaum wrote:
On 06/11/2015 01:26 PM, Laszlo Ersek wrote:
On 06/11/15 12:21, Marcel Apfelbaum wrote:
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens
The properties reg/assigned-resources need to encode 64-bit memory
address space as part of phys.hi dword.
00 if configuration space
01 if IO region,
10 if 32-bit MEM region
11 if 64-bit MEM region
Signed-off-by: Nikunj A Dadhania nik...@linux.vnet.ibm.com
Reviewed-by: Thomas Huth
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens because the
sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have
enough information to format a unique identifier for the PXB
Hi,
I've just bisected a virt-test breakage down to:
97edf3bd5 'gtk: add opengl support, using egl'
I think the problem is that it's trying to start X up early
on, even in the cases when qemu would just print some help and
exit. I'm running virt-test on a remote machine via ssh and
don't have
Eric Auger eric.au...@linaro.org writes:
g_malloc0_n() is introduced since glib-2.24 while QEMU currently
requires glib-2.22. This may cause a link error on some distributions.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
hw/vfio/platform.c | 3 +--
1 file changed, 1 insertion(+),
' into
staging (2015-06-10 18:13:58 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-gtk-20150611-1
for you to fetch changes up to 060ab76356fff6a420bc881a574c40a5dda086af:
gtk: don't exit early in case gtk init fails (2015-06-11 11:37:56 +0200
All the PCI enumeration and device node creation was off-loaded to
SLOF. With PCI hotplug support, code needed to be added to add device
node. This creates multiple copy of the code one in SLOF and other in
hotplug code. To unify this, the patch adds the pci device node
creation in Qemu. For
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens because the
sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have
enough information to format a unique identifier for the PXB
On 06/11/2015 01:26 PM, Laszlo Ersek wrote:
On 06/11/15 12:21, Marcel Apfelbaum wrote:
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens because the
sysbus_get_fw_dev_path() function in
On Fri, 05/22 13:35, Fam Zheng wrote:
Ping :)
Fam
Fam Zheng (2):
Makefile: Fix make cscope TAGS
Makefile: Add make ctags
Makefile | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
--
2.4.1
The patch series creates PCI device tree(DT) nodes in QEMU. The new
hotplug code needs the device node creation in QEMU. While during
boot, nodes were created in SLOF. It makes more sense to consolidate
the code to one place for better maintainability.
Based on David's spapr-next
Each hardware instance has a platform unique location code. The OF
device tree that describes a part of a hardware entity must include
the “ibm,loc-code” property with a value that represents the location
code for that hardware entity.
Populate ibm,loc-code.
1) PCI passthru devices need to
On Thu, Jun 11, 2015 at 01:54:22PM +0800, Jason Wang wrote:
On 06/11/2015 01:49 PM, Thibaut Collet wrote:
Yes, but still need a mechanism to notify the backend of migration
completion from qemu side if GUEST_ANNOUNCE is not negotiated.
backend is aware of a connection with the guest
On 06/11/2015 01:45 PM, Laszlo Ersek wrote:
On 06/11/15 12:29, Marcel Apfelbaum wrote:
On 06/11/2015 01:26 PM, Laszlo Ersek wrote:
On 06/11/15 12:21, Marcel Apfelbaum wrote:
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
This isn't used by any of the code. In fact it looks like it was never
used as it came in with ARMv7 support.
Signed-off-by: Alex Bennée alex.ben...@linaro.org
---
target-arm/cpu.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/target-arm/cpu.h b/target-arm/cpu.h
index 21b5b8e..7c1d95c
Device node names should encode the unit address as hex, while the
code was encodind it as integers.
Also, use FDT_NAME_MAX macro for allocating and composing the name.
Signed-off-by: Nikunj A Dadhania nik...@linux.vnet.ibm.com
Reviewed-by: Thomas Huth th...@redhat.com
---
hw/ppc/spapr_pci.c |
Hi Gonglei,
On 06/11/2015 09:55 AM, Gonglei wrote:
On 2015/6/11 15:14, Eric Auger wrote:
g_malloc0_n() is introduced since glib-2.24 while QEMU currently
requires glib-2.22. This may cause a link error on some distributions.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
g_malloc0_n() is introduced since glib-2.24 while QEMU currently
requires glib-2.22. This may cause a link error on some distributions.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
v1 - v2:
- replace g_malloc0 by g_new0
---
hw/vfio/platform.c | 3 +--
1 file changed, 1 insertion(+), 2
On 10.06.2015 16:00, Eric Blake wrote:
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
+
On Thu, Jun 11, 2015 at 10:26:12AM +0200, Gerd Hoffmann wrote:
Hi,
Here's an incomplete todo for spec compliance: note that it does not
have to block this patchset:
- complete other devices besides net, balloon
need to disable a bunch of features
that 1.0
On 11.06.2015 02:42, John Snow wrote:
On 06/08/2015 11:21 AM, Vladimir Sementsov-Ogievskiy wrote:
From: Vladimir Sementsov-Ogievskiy vsement...@parallels.com
Signed-off-by: Vladimir Sementsov-Ogievskiy vsement...@virtuozzo.com
---
block/qcow2-dirty-bitmap.c | 5 +
block/qcow2.c
On 06/05/2015 10:32 PM, Pankaj Gupta wrote:
We use vhostforce to enable vhost even if Guests don't have MSI-X
support
and we fall back to QEMU virtio-net. This patch will enable vhost
unconditionally
whenever we have vhostforce='ON' or vhost='ON'.
Initially, I wanted to
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
Cc: Markus Armbruster arm...@redhat.com
Cc: Marcel Apfelbaum mar...@redhat.com
Cc: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
Notes:
v3:
- new in v3
hw/core/sysbus.c | 16 ++--
1 file
On 06/11/15 11:15, Marcel Apfelbaum wrote:
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens because the
sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have
enough
On Do, 2015-06-11 at 10:38 +0100, Frediano Ziglio wrote:
libvirt has this as a video card parameter (actually set to 1 but not
used). This parameter will allow to limit setting a use can do (which
could be confusing).
Hmm. So heads is '1' by default but ignored today. When this starts to
be
Current code missed the Prog IF register. All Class Code, Subclass,
and Prog IF registers are needed to identify the accurate device type.
For example: USB controllers use the PROG IF for denoting: USB
FullSpeed, HighSpeed or SuperSpeed.
Signed-off-by: Nikunj A Dadhania nik...@linux.vnet.ibm.com
On 10.06.2015 18:27, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:18PM +0300, Vladimir Sementsov-Ogievskiy wrote:
QCow2 header is extended by fields 'nb_dirty_bitmaps' and
'dirty_bitmaps_offset' like with snapshots.
Proposed command line syntax is the following:
-dirty-bitmap
From: Alberto Garcia be...@igalia.com
The Ctrl-Alt-u keyboard shortcut restores the screen to its original
size. In the SDL2 UI this is done by destroying the window and
creating a new one. The old window emits SDL_WINDOWEVENT_HIDDEN when
it's destroyed, but trying to call SDL_GetWindowFromID()
://git.kraxel.org/qemu tags/pull-sdl-20150611-1
for you to fetch changes up to 08d49df0dbaacc220a099dbfb644e1dc0eda57be:
sdl2: fix crash in handle_windowevent() when restoring the screen size
(2015-06-09 10:25:21 +0200)
sdl2: fix
On 11 June 2015 at 08:46, Pavel Fedin p.fe...@samsung.com wrote:
Hi Peter!
Hi. I think this patch largely makes sense, but I have some comments
below. If you want to fix these and resend as a standalone patch
I'm happy to apply that.
How are things going? I have resent v4 of this on the
On 10.06.2015 16:24, Stefan Hajnoczi wrote:
On Wed, Jun 10, 2015 at 11:19:30AM +0300, 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:
@@ -166,6 +167,19 @@ the header extension data.
On 06/11/15 12:21, Marcel Apfelbaum wrote:
On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
off devices behind the PXB. This happens because the
sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have
enough
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
Hi,
I've just bisected a virt-test breakage down to:
This is fixed by the just posted 'gtk: don't exit early in case gtk init fails'
Dave
97edf3bd5 'gtk: add opengl support, using egl'
I think the problem is that it's trying to
On 10.06.2015 18:34, Kevin Wolf wrote:
Am 08.06.2015 um 17:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
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) or as
* phb_index is not being used and if required can be obtained from sphb
* use helper to get drc_index in this function
Suggested-by: Alexey Kardashevskiy a...@ozlabs.ru
Signed-off-by: Nikunj A Dadhania nik...@linux.vnet.ibm.com
---
hw/ppc/spapr_pci.c | 12 +---
1 file changed, 5
Is there something I need to install (kernel module or something like
that) so that the virtio guest receives signals from vhost?
The communication from and to qemu works (I can send a message from
guest to qemu, and I can send a message from qemu to guest), and I can
send a message from guest to
On 06/11/15 15:58, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw path
Signed-off-by: Frediano Ziglio fzig...@redhat.com
---
hw/display/qxl-logger.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/hw/display/qxl-logger.c b/hw/display/qxl-logger.c
index c900c2c..d944d3f 100644
--- a/hw/display/qxl-logger.c
+++
On 11 June 2015 at 09:44, Eric Auger eric.au...@linaro.org wrote:
g_malloc0_n() is introduced since glib-2.24 while QEMU currently
requires glib-2.22. This may cause a link error on some distributions.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
v1 - v2:
- replace g_malloc0 by
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path:
On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new
On 06/11/15 16:36, Marcel Apfelbaum wrote:
On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the
It seems that the problem is from the code itself.
If I call vhost_dev_start() in set_status() (in qemu), when the status
changes to VIRTIO_CONFIG_S_DRIVER_OK, only the communication path from
guest to vhost works.
In another scenario I send a message from guest to qemu, and the vq
handler in
On 11 May 2015 at 07:53, Gerd Hoffmann kra...@redhat.com wrote:
On So, 2015-05-10 at 23:51 +0100, Peter Maydell wrote:
So looking at the code in ui/console.c that implements our
virtual consoles, the scrolling is hooked up to the keycodes
QEMU_KEY_CTRL_{UP,DOWN,PAGEUP,PAGEDOWN}. These only
-06-08 15:57:41 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-sdl-20150611-1
for you to fetch changes up to 08d49df0dbaacc220a099dbfb644e1dc0eda57be:
sdl2: fix crash in handle_windowevent() when restoring the screen size
(2015-06-09 10:25:21 +0200
add modern header
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
include/hw/virtio/virtio-balloon.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/hw/virtio/virtio-balloon.h
b/include/hw/virtio/virtio-balloon.h
index
From: Cornelia Huck cornelia.h...@de.ibm.com
For virtio-1 devices, we allow a more complex queue layout that doesn't
require descriptor table and rings on a physically-contigous memory area:
add virtio_queue_set_rings() to allow transports to set this up.
Signed-off-by: Cornelia Huck
From: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/hw/pci/pci_ids.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/hw/pci/pci_ids.h
From: Shannon Zhao shannon.z...@linaro.org
As only one place in virtio-net.c uses DEFINE_VIRTIO_NET_FEATURES,
there is no need to expose it. Inline it into virtio-net.c to avoid
wrongly use.
Signed-off-by: Shannon Zhao zhaoshengl...@huawei.com
Signed-off-by: Shannon Zhao shannon.z...@linaro.org
I am not sure to understand your remark:
It needs to be sent when backend is activated by guest kick
(in case of virtio 1, it's possible to use DRIVER_OK for this).
This does not happen when VM still runs on source.
Could you confirm rarp can be sent by backend when the
-tracking branch 'remotes/kraxel/tags/pull-vga-20150610-1' into
staging (2015-06-10 18:13:58 +0100)
are available in the git repository at:
git://anongit.freedesktop.org/spice/qemu tags/pull-spice-20150611-1
for you to fetch changes up to 5a9259a0b5d6f9424f94539cd9c715b1d166d90c:
spice
From: Gerd Hoffmann kra...@redhat.com
This patch adds variables for the pci bars (to get rid of the magic
numbers in the code) and moves the modern virtio bar to region 4 so
regions 2+3 are kept free. virtio-vga wants use them.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael
From: Gerd Hoffmann kra...@redhat.com
Add function to map modern virtio regions.
Add offset to VirtIOPCIRegion.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.h | 1 +
From: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.c | 4 +++-
1 file changed, 3
On Tue, Jun 09, 2015 at 02:07:47PM +0300, Igor Yakovlev wrote:
Would you so kind to help me with my problem concerning libgfapi.
My host operating system is Ubuntu 14.04 LTS, version of glusterfs is
3.6.2, and version of qemu is 2.0.0. We use libfgapi library to connect to
glusterfs.
In
The following changes since commit 309750fad51f17d1ec6195c5d8ad7d741596ddb6:
vhost: logs sharing (2015-06-04 12:44:49 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
for you to fetch changes up to
On Thu, Jun 11, 2015 at 02:10:48PM +0200, Thibaut Collet wrote:
I am not sure to understand your remark:
It needs to be sent when backend is activated by guest kick
(in case of virtio 1, it's possible to use DRIVER_OK for this).
This does not happen when VM still runs on source.
Could
From: Shannon Zhao shannon.z...@linaro.org
As only one place in virtio-rng.c uses DEFINE_VIRTIO_RNG_PROPERTIES,
there is no need to expose it. Inline it into virtio-rng.c to avoid
wrongly use.
Signed-off-by: Shannon Zhao zhaoshengl...@huawei.com
Signed-off-by: Shannon Zhao
The old one still works for now, but will not work indefinitely.
Signed-off-by: Josh Durgin jdur...@redhat.com
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4ed8215..34eeb88 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw path was wrongly computed:
From: Cornelia Huck cornelia.h...@de.ibm.com
Handle endianness conversion for virtio-1 virtqueues correctly.
Note that dataplane now needs to be built per-target.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
include/hw/virtio/virtio.h | 1 +
hw/virtio/virtio-pci.c | 2 +-
hw/virtio/virtio.c | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/hw/virtio/virtio.h
From: Cornelia Huck cornelia.h...@de.ibm.com
virtio-net (non-vhost) now should have everything in place to support
virtio 1.0: let's enable the feature bit for it.
Note that VIRTIO_F_VERSION_1 is technically a transport feature; once
every device is ready for virtio 1.0, we can move setting this
From: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.h | 1 +
hw/virtio/virtio-pci.c | 9 +
2 files changed, 6 insertions(+), 4
From: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Acked-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.c | 2 +-
1 file changed, 1 insertion(+), 1
Ok.
backend is able to know when the eventfd is kick the first time and then
can send a rarp for legacy guest.
With this backend modification the issue point by Jason is no more a QEMU
problem.
Full support of live migration for vhost user:
- Need my first patch.
- For legacy guest the backend
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw path was wrongly computed:
/pci-root@1/pci@i0cf8/...
Fix the above issues: Correct the bus number and remove the
extra host bridge description.
Apply the ceph settings from a config file before any ceph settings
from the command line. Since the ceph config file location may be
specified on the command line, parse it once to read the config file,
and do a second pass to apply the rest of the command line ceph
options.
Signed-off-by: Josh
To be safe, when cache=none is used ceph settings should not be able
to override it to turn on caching. This was previously possible with
rbd_cache=true in the rbd device configuration or a ceph configuration
file. Similarly, rbd settings could have turned off caching when qemu
requested it,
On 06/11/15 14:51, Marcel Apfelbaum wrote:
On 06/11/2015 03:45 PM, Michael S. Tsirkin wrote:
On Thu, Jun 11, 2015 at 03:41:35PM +0300, Marcel Apfelbaum wrote:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch
This is somewhat functional. With this, and linux driver from my tree,
I was able to use virtio net as virtio 1.0 device for light browsing.
At the moment, dataplane and vhost code is
still missing.
Based on Cornelia's virtio 1.0 patchset:
Date: Thu, 11 Dec 2014 14:25:02 +0100
From:
From: Cornelia Huck cornelia.h...@de.ibm.com
Devices operating as virtio 1.0 may not allow writes to the mac
address in config space.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
virtio 1.0 config space is in LE format for all
devices, use modern wrappers when accessed through
the 1.0 BAR.
Reported-by: Rusty Russell ru...@rustcorp.com.au
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.c | 12
From: Gerd Hoffmann kra...@redhat.com
This patch adds virtio-pci support for the emulated virtio-input
devices. Using them is as simple as adding -device virtio-tablet-pci
to your command line. If you want add multiple devices but don't want
waste a pci slot for each you can compose a
From: Shannon Zhao shannon.z...@linaro.org
Remove unsed DEFINE_VIRTIO_NET_PROPERTIES in virtio-net.h and delete a
space typo.
Signed-off-by: Shannon Zhao zhaoshengl...@huawei.com
Signed-off-by: Shannon Zhao shannon.z...@linaro.org
Reviewed-by: Paolo Bonzini pbonz...@redhat.com
Acked-by: Cornelia
From: Jason Wang jasow...@redhat.com
Currently, during host notifier set. We only add eventfd for legacy
bar, this is not correct since:
- Non-transitional device does not have legacy bar, so qemu will crash
since proxy-bar was not initialized.
- Modern device uses modern bar and notify cap to
On Thu, Jun 11, 2015 at 05:07:45AM +0900, IdleTime wrote:
I have released the Chrome version of QEMU.
https://chrome.google.com/webstore/detail/pnacl-qemu/mogglnfmfhjnjmeehdjppldblehpniom
Sorry, my english is very poor.
I would like if possible to link the URL above
Replace g_malloc0 occurences by g_new0 where that makes obvious sense.
This looks to be the best practice bringing extra compile-time checking
and integer overflow protection.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
hw/vfio/common.c | 8
hw/vfio/pci.c | 24
On Thu, Jun 11, 2015 at 02:22:35PM +0300, Vladimir Sementsov-Ogievskiy wrote:
On 10.06.2015 18:27, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:18PM +0300, Vladimir Sementsov-Ogievskiy wrote:
QCow2 header is extended by fields 'nb_dirty_bitmaps' and
'dirty_bitmaps_offset' like with
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw path was wrongly computed:
/pci-root@1/pci@i0cf8/...
Fix the above issues: Correct the bus number and remove the
On Thu, Jun 11, 2015 at 01:19:24PM +0300, Vladimir Sementsov-Ogievskiy wrote:
On 10.06.2015 16:24, Stefan Hajnoczi wrote:
On Wed, Jun 10, 2015 at 11:19:30AM +0300, Vladimir Sementsov-Ogievskiy wrote:
On 09.06.2015 20:03, Stefan Hajnoczi wrote:
On Mon, Jun 08, 2015 at 06:21:19PM +0300, Vladimir
Add VERSION_1 to list of features that we should
test at the backend.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
hw/net/vhost_net.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/net/vhost_net.c b/hw/net/vhost_net.c
index
From: Cornelia Huck cornelia.h...@de.ibm.com
For virtio-1 devices, the driver must not attempt to set feature bits
after it set FEATURES_OK in the device status. Simply reject it in
that case.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
From: Cornelia Huck cornelia.h...@de.ibm.com
Make sure that all vhost interfaces use 64 bit features, as the virtio
core does, and make sure to use ULL everywhere possible to be on the
safe side.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Reviewed-by: Michael S. Tsirkin
From: Gerd Hoffmann kra...@redhat.com
Now the three struct virtio_pci_caps are identical,
lets drop two of them ;)
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/virtio/virtio-pci.c | 18
From: Laszlo Ersek ler...@redhat.com
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 address
From: Laszlo Ersek ler...@redhat.com
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, said patch
Patches 1 and 2 are simple cleanups. 3 and 4 fix the precedence of
cache options and ceph settings. The cache option precedence in
particular is important due to the potential for misconfigurations
(ceph.conf setting rbd_cache=true, qemu setting cache=none) to
accidentally put data at risk.
Josh
In qxl_v2n check that value is not negative.
Signed-off-by: Frediano Ziglio fzig...@redhat.com
---
hw/display/qxl-logger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/display/qxl-logger.c b/hw/display/qxl-logger.c
index d944d3f..faed869 100644
---
On Thu, 2015-06-11 at 14:00 +0100, Peter Maydell wrote:
On 11 June 2015 at 09:44, Eric Auger eric.au...@linaro.org wrote:
g_malloc0_n() is introduced since glib-2.24 while QEMU currently
requires glib-2.22. This may cause a link error on some distributions.
Signed-off-by: Eric Auger
Easier than duplicating code.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
---
linux-headers/linux/virtio_pci.h | 192 +++
hw/virtio/virtio-pci.c | 2 +
2 files changed, 194 insertions(+)
create
From: Cornelia Huck cornelia.h...@de.ibm.com
virtio-1 devices always use num_buffers in the header, even if
mergeable rx buffers have not been negotiated.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin
From: Gerd Hoffmann kra...@redhat.com
Add VIRTIO_PCI_FLAG_DISABLE_LEGACY and VIRTIO_PCI_FLAG_DISABLE_MODERN
for VirtIOPCIProxy-flags. Also add properties for them. They can be
used to disable modern (virtio 1.0) or legacy (virtio 0.9) modes.
By default only legacy is advertized, modern will be
1 - 100 of 232 matches
Mail list logo
