On Tue, Nov 06, 2018 at 09:36:44AM -0500, Michael S. Tsirkin wrote:
> On Tue, Nov 06, 2018 at 11:23:33AM +0100, Gerd Hoffmann wrote:
> > Print a warning for deprecated and obsolete devices.
> > Also add support state to device listing.
> >
> > Signed-off-by: Gerd Hoffmann
>
> Should we also add
On Mon, Nov 05, 2018 at 09:58:56AM -0600, Eric Blake wrote:
> On 11/5/18 6:45 AM, Yuval Shaia wrote:
> > pvrdma requires that the same GID attached to it will be attached to the
> > backend device in the host.
> >
> > A new QMP messages is defined so pvrdma device can broadcast any change
> > made
Hi,
> >> +# @experimental: in development, can be unstable or incomplete.
> >
> > People reading this document would ask: what would appear on
> > MAINTAINERS if SupportState is `experimental`?
>
> Probably Maintained. It's something that is on its way towards becoming
> "supported", but stil
Hi Eric,
On Tue, Nov 6, 2018 at 7:42 PM Eric Auger wrote:
> Commit af7d64ede0b9 (hw/arm/sysbus-fdt: Allow device matching with DT
> compatible value) introduced a match_fn callback which gets called
> for each registered combo to check whether a sysbus device can be
> dynamically instantiated. Ho
Hi, everybody.
I want to compile QEMU statically. But when I make the soure files, I get the
error messages. Please help me to resolve them.
Now I will tell you the steps what I do.
(1)$ cd qemu-3.0.0
(2)$ ./configure --prefix=/usr --static
(3)$ make
When I input the "make" command, and run it, t
On Mon, Nov 05, 2018 at 12:20:05PM +0100, Thomas Huth wrote:
> On 2018-10-30 13:35, Kashyap Chamarthy wrote:
> > Since we're deprecating the QMP `cpu-add`, let's deprecate its HMP
> > equivalent, too.
> >
> > Suggested-by: Thomas Huth
> > Signed-off-by: Kashyap Chamarthy
[...]
> > diff --git a
On 07.11.18 00:10, David Gibson wrote:
> On Mon, Nov 05, 2018 at 11:20:38AM +0100, David Hildenbrand wrote:
>> We better stop right away. While at it, properly move the check
>> to the pre_plug handler.
>>
>> Reviewed-by: Igor Mammedov
>> Signed-off-by: David Hildenbrand
>
> Reviewed-by: David G
Hi,
> > Signed-off-by: Gerd Hoffmann
>
> Thanks for taking the latest version. If this works out well, would it be
> possible to use this version of Seabios also for QEMU 3.0 stable? I am
> asking primarily due to the TPM patches and the fact that QEMU 3.0 is
> packaged in F29, with the CRB po
On 2018-11-07 09:49, Kashyap Chamarthy wrote:
> On Mon, Nov 05, 2018 at 12:20:05PM +0100, Thomas Huth wrote:
>> On 2018-10-30 13:35, Kashyap Chamarthy wrote:
>>> Since we're deprecating the QMP `cpu-add`, let's deprecate its HMP
>>> equivalent, too.
>>>
>>> Suggested-by: Thomas Huth
>>> Signed-off
Hi,
On 7/11/18 9:43, wj193102 wrote:
Hi, everybody.
I want to compile QEMU statically. But when I make the soure files, I get the
error messages. Please help me to resolve them.
Now I will tell you the steps what I do.
(1)$ cd qemu-3.0.0
(2)$ ./configure --prefix=/usr --static
Can you share t
On 6/11/18 11:23, Gerd Hoffmann wrote:
Signed-off-by: Gerd Hoffmann
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
---
include/qemu/typedefs.h | 1 +
include/qom/object.h| 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/qemu/typedefs
Am 29.10.2018 um 07:29 hat Li Qiang geschrieben:
> The first corrent the refcount and second fix a memory leak.
Thanks, applied to the block branch.
Kevin
Hi Berg,
thanks for the tip, a fix has also been commited already :)
Cheers,
Bastian
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1794939
T
06.11.2018 20:57, Kevin Wolf wrote:
> Am 15.10.2018 um 18:06 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> Otherwise, if we have serialized read-part in copy_range from backing
>> file to its parent if CoW take place, this CoW's sub-reads will
>> intersect with firstly created serialized read re
07.11.2018 01:35, John Snow wrote:
>
> On 11/06/2018 12:21 PM, Kevin Wolf wrote:
>> Am 02.11.2018 um 17:41 hat Vladimir Sementsov-Ogievskiy geschrieben:
>>> ping
>>>
>>> 15.10.2018 19:06, Vladimir Sementsov-Ogievskiy wrote:
Hi all!
These series introduce backup-top driver. It's a fil
Hello,
another version of the proposed API for monitor identification
information. Still not for merge yet, the plan is to merge when it's
complete.
Changes since v2:
* Merged the two API functions into one:
spice_qxl_set_device_info(QXLInstance *instance,
const char
Replace it by spice_qxl_set_device_info. Note we can't use
monitors_count for what's stored in max_monitors, because monitors_count
denotes the length of the device_display_ids array, which
spice_qxl_set_max_monitors doesn't touch.
Signed-off-by: Lukáš Hrázký
---
server/red-qxl.c | 1 +
server
Adds a function to let QEMU provide information to identify graphics
devices and their monitors in the guest. The function
(spice_qxl_set_device_info) sets the device address (e.g. a PCI path)
and monitor ID -> device display ID mapping of displays exposed by given
QXL interface.
Signed-off-by: Lu
Calls the new SPICE QXL interface function spice_qxl_set_device_info to
set the hardware address of the graphics device represented by the QXL
interface (e.g. a PCI path) and the device display IDs (the IDs of the
device's monitors that belong to this QXL interface).
Also stops using the deprecate
On 7 November 2018 at 02:56, Peter Xu wrote:
> Strange, "make check -j8" failed on my hosts (I tried two) with either
> Markus's pull tree or qemu master:
>
> hw/core/ptimer.o: In function `timer_new_tl':
> /home/xz/git/qemu/include/qemu/timer.h:536: undefined reference to
> `timer_init_tl'
> col
On 7 November 2018 at 06:05, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
>> The $(SHELLSTATUS) variable requires GNU make >= 4.2, but Travis
>> seems to provide an older version. Change the existing rules to
>> use command output instead of exit code, to make it compatible
>> with older
On 7 November 2018 at 08:43, wj193102 wrote:
> Hi, everybody.
> I want to compile QEMU statically. But when I make the soure files, I get the
> error messages. Please help me to resolve them.
> Now I will tell you the steps what I do.
> (1)$ cd qemu-3.0.0
> (2)$ ./configure --prefix=/usr --static
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20181029173437.32559-1-pbonz...@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] scsi-generic: fixes for Block Limits emulation
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n
(I'm not going to claim this is a bug, but it causes a large, easily
measurable performance regression in virt-v2v).
In qemu 2.10, when you do ‘qemu-img convert’ to an NBD target, qemu
interleaves write and zero requests. We can observe this as follows:
$ virt-builder fedora-28
$ nbdkit --fi
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Tuesday, November 6, 2018 4:18 AM
> To: Wang, Xiao W ; m...@redhat.com;
> alex.william...@redhat.com
> Cc: qemu-devel@nongnu.org; Bie, Tiwei ; Liang, Cunming
> ; Ye, Xiaolong ; Wang, Zhihong
> ; Daly, Dan
> Subj
Hi,
This series failed docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20181029173437.32559-1-pbonz...@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] scsi-generic
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20181102152257.20637-1-mark.cave-ayl...@ilande.co.uk
Subject: [Qemu-devel] [PATCH v6 00/10] hw/m68k: add Apple Machintosh Quadra 800
machine
=== TEST SCRIPT BEGIN ===
#!/bin
Hi,
During "[PATCH v2 05/10] qom/globals: generalize
object_property_set_globals()" review, Eduardo suggested to rework the
GlobalProperty handling, so that -global is limited to QDev only and
we avoid mixing the machine compats and the user-provided -global
properties (instead of generalizing -gl
Instead, it returns 1 if an error was detected, which is the case for:
/qdev/properties/dynamic/global/subprocess:
warning: global dynamic-prop-type-bad.prop3 has invalid class name
warning: global nohotplug-type.prop5=105 not used
warning: global nondevice-type.prop6 has invalid class name
Clari
Interfaces don't have instance, let's make the interface type really
abstract to avoid confusion.
Signed-off-by: Marc-André Lureau
---
include/hw/acpi/acpi_dev_interface.h | 6 +-
include/hw/arm/linux-boot-if.h | 5 +
include/hw/fw-path-provider.h| 4 +---
include/hw/hotplu
The function is only used by a test, move it there.
Signed-off-by: Marc-André Lureau
Reviewed-by: Eduardo Habkost
---
include/hw/qdev-properties.h | 1 -
hw/core/qdev-properties.c | 9 -
tests/test-qdev-global-props.c | 18 ++
3 files changed, 14 insertions(+),
global_props is only used for Xen xen_compat_props. It's a static
array of GlobalProperty, like machine globals in SET_MACHINE_COMPAT().
Let's register the globals the same way, without extra copy allocation.
Signed-off-by: Marc-André Lureau
Reviewed-by: Igor Mammedov
---
include/hw/qdev-proper
Instead of accepting any Object*, change user_creatable_complete() to
require a UserCreatable*. Modify the callers to pass the appropriate
argument, removing redundant dynamic cast checks in object creation.
Signed-off-by: Marc-André Lureau
Reviewed-by: Igor Mammedov
---
include/qom/object_inte
All qdev_prop_register_global() set &error_fatal for errp, except
'-rtc driftfix=slew', which arguably should also use &error_fatal, as
otherwise failing to apply the property would only report a warning.
Signed-off-by: Marc-André Lureau
---
include/hw/qdev-core.h| 6 --
hw/core/qdev-pro
hostmem-file and hostmem-memfd use the whole object path for the
memory region name, and hostname-ram uses only the path component (the
object id, or canonical path basename):
qemu -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/tmp/foo -numa
node,memdev=mem -monitor stdio
(qemu) inf
Considering that CPU features are provided via command line, the
global_props are now all user-provided globals. No need to track this
anymore for qdev_prop_check_globals().
Signed-off-by: Marc-André Lureau
---
include/hw/qdev-core.h | 3 --
hw/core/qdev-properties.c | 4 ---
test
Machine & Accel props are not provided by user. Let's not mix them
with the global properties.
Call a new helper function object_apply_global_props() during
device_post_init().
Add a stub for current_machine, so qemu-user and tests can find a
fallback symbol when linking with QDev.
The following
On Fri, 2 Nov 2018 11:30:20 +0100
Pierre Morel wrote:
> From: Pierre Morel
Meta: you may want to rewrite your authorship to the shorter address.
>
> We intercept the PQAP(AQIC) instruction.
>
> Until we implement AQIC we return a PGM_OPERATION.
>
> Signed-off-by: Pierre Morel
> ---
> hw/
The following patches are going to implement post_init callbacks for
settings properties. The interface post_init are called before the
instance post_init, so the default interface behaviour can be
overriden if necessary.
Signed-off-by: Marc-André Lureau
---
qom/object.c| 8
A step towards being able to call object_apply_global_props().
Signed-off-by: Marc-André Lureau
---
hw/core/qdev-properties.c | 29 -
1 file changed, 20 insertions(+), 9 deletions(-)
diff --git a/hw/core/qdev-properties.c b/hw/core/qdev-properties.c
index 43c30a57f4.
The following patch is going to add compatiblity parameters for
qemu <= 3.1.
Signed-off-by: Marc-André Lureau
---
include/hw/compat.h | 3 +++
include/hw/i386/pc.h | 3 +++
hw/i386/pc_piix.c| 21 ++---
hw/i386/pc_q35.c | 19 +--
4 files changed, 41 inse
It's now possible to use the common function.
Teach object_apply_global_props() to warn if Error argument is NULL.
Signed-off-by: Marc-André Lureau
---
hw/core/qdev-properties.c | 24 ++--
qom/object.c | 6 +-
2 files changed, 7 insertions(+), 23 deletions(
On Wed, Nov 07, 2018 at 07:05:03AM +0100, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > The $(SHELLSTATUS) variable requires GNU make >= 4.2, but Travis
> > seems to provide an older version. Change the existing rules to
> > use command output instead of exit code, to make it compatib
Let's make compatiblity properties an interface, so that objects other
than QDev can benefit from having machine compatiblity properties.
Signed-off-by: Marc-André Lureau
---
include/hw/boards.h| 2 ++
hw/core/compat-props.c | 43 ++
hw/core/qdev.c
The 'block-commit' QMP command is implemented internally using two
different drivers. If the source image is the active layer then the
mirror driver is used (commit_active_start()), otherwise the commit
driver is used (commit_start()).
In both cases the destination image must be put temporarily in
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block/commit.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/block/commit
No one is using this function anymore, so we can safely remove it.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block.c | 21 -
include/block/block.h | 1 -
2 files changed, 22 deletions(-)
diff --git a/block.c b/block.c
index cfa53f7114..31de7b22
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block/commit.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/b
Hi all,
when reopening a BlockDriverState using bdrv_reopen() and friends the
new options can be specified either with a QDict or with flags. Both
methods overlap and that makes the semantics and the implementation
unnecessarily complicated.
This series removes the 'flags' parameter from these fu
Towards the end of bdrv_reopen_queue_child(), before starting to
process the children, the update_flags_from_options() function is
called in order to have BDRVReopenState.flags in sync with the options
from the QDict.
This is necessary because during the reopen process flags must be
updated for al
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/block.c b/block
Most callers of bdrv_reopen() only use it to switch a BlockDriverState
between read-only and read-write, so this patch adds a new function
that does just that.
We also want to get rid of the flags parameter in the bdrv_reopen()
API, so this function sets the "read-only" option and passes the
origi
When reopen_f() puts a block device in the reopen queue, some of the
new options are passed using a QDict, but others ("read-only" and the
cache options) are passed as flags.
This patch puts those flags in the QDict. This way the flags parameter
becomes redundant and we'll be able to get rid of it
Now that all callers are passing the new options using the QDict we no
longer need the 'flags' parameter.
This patch makes the following changes:
1) The update_options_from_flags() call is no longer necessary
so it can be removed.
2) The update_flags_from_options() call is now used i
Now that all callers are passing all flag changes as QDict options,
the flags parameter is no longer necessary, so we can get rid of it.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block.c | 5 +++--
block/replication.c | 6 ++
include/block/block.h | 3 +--
qem
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
blockdev.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/blockdev.c b/bl
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
block/stream.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --gi
In qcow2_snapshot_create there is the following code block:
/* Generate an ID */
find_new_snapshot_id(bs, sn_info->id_str, sizeof(sn_info->id_str));
/* Check that the ID is unique */
if (find_snapshot_by_id_and_name(bs, sn_info->id_str, NULL) >= 0) {
return -EEXIST;
}
This function is used to put the hidden and secondary disks in
read-write mode before launching the backup job, and back in read-only
mode afterwards.
This patch does the following changes:
- Use an options QDict with the "read-only" option instead of
passing the changes as flags only.
-
At this moment, QEMU attempts to create/load/delete snapshots
by using either an ID (id_str) or a name. The problem is that the code
isn't consistent of whether the entered argument is an ID or a name,
causing unexpected behaviors.
For example, when creating snapshots via savevm , what happens is
This patch replaces the bdrv_reopen() call that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
Reviewed-by: Max Reitz
---
blockdev.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/blockdev.c b/blockdev.
After the previous patch, the only instance of this function left
is inside qemu-img.c.
qemu-img is using it inside the 'img_snapshot' function to delete
snapshots in the SNAPSHOT_DELETE case, based on a "snapshot_name"
string that refers to the tag, not ID, of the QEMUSnapshotInfo struct.
This ca
This function takes three options (cache.direct, cache.no-flush and
read-only) from a QemuOpts object and updates the flags accordingly.
If any of those options is not set (because it was missing from the
original QDict or because it had an invalid value) then the function
aborts with a failed ass
changes in v3:
- rebased to v3.1.0-rc0 tag
- hmp-commands.hx documentation now mentions the change of semantics
starting version 3.2.
- previous version link:
http://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg00629.html
It is not uncommon to see bugs being opened by testers that attempt
noload kernels are loaded with the u-boot image header and as a result
the header size needs adding to the entry point. Fake up a hdr so the
kernel image is loaded at the right address and the entry point is
adjusted appropriately
Signed-off-by: Nick Hudson
---
hw/arm/boot.c | 8 +
Hi Bastian,
I got past this error by installing libvte-dev instead of
libvte-2.91-dev.
I'm not sure if it actually works however.
Cheers,
Berg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1794939
On 07.11.18 07:36, Markus Armbruster wrote:
> From: Jeff Cody
>
> This adds configure options to control the following block drivers:
>
> * Bochs
> * Cloop
> * Dmg
> * Qcow (V1)
> * Vdi
> * Vvfat
> * qed
> * parallels
> * sheepdog
>
> Each of these defaults to being enabled.
>
> Signed-off-by:
On Fri, 2 Nov 2018 11:30:21 +0100
Pierre Morel wrote:
> We intercept the PQAP(AQIC) instruction and transform
> the guest's AQIC command parameters for the host AQIC
> parameters.
>
> Doing this we use the standard adapter interface to provide
> the adapter NIB, indicator and ISC.
>
> We defin
On 7 November 2018 at 12:49, Eduardo Habkost wrote:
> Now, why do we need --with-python, and why do we need to use
> $(PYTHON) when running tests? If somebody wants to use a
> different Python binary when running tests, they can already use
> $PATH for that.
>
> (That's the same argument I used f
On 01.11.18 13:17, Vladimir Sementsov-Ogievskiy wrote:
> 27.09.2018 20:35, Max Reitz wrote:
>> On 07.08.18 19:43, Vladimir Sementsov-Ogievskiy wrote:
>>> Memory allocation may become less efficient for encrypted case. It's a
>>> payment for further asynchronous scheme.
>>>
>>> Signed-off-by: Vladim
I saw this thread, but from a NetBSD maintainer point of view, I will
defer review to ARM people.
On 07.11.2018 14:19, Nick Hudson wrote:
> noload kernels are loaded with the u-boot image header and as a result
> the header size needs adding to the entry point. Fake up a hdr so the
> kernel image
Another thing I tried was to change the NBD server (nbdkit) so that it
doesn't advertise zero support to the client:
$ nbdkit --filter=log --filter=nozero memory size=6G logfile=/tmp/log \
--run './qemu-img convert ./fedora-28.img -n $nbd'
$ grep '\.\.\.$' /tmp/log | sed 's/.*\([A-Z][a-z
On 2018/11/7 下午8:26, Liang, Cunming wrote:
-Original Message-
From: Jason Wang [mailto:jasow...@redhat.com]
Sent: Tuesday, November 6, 2018 4:18 AM
To: Wang, Xiao W ; m...@redhat.com;
alex.william...@redhat.com
Cc: qemu-devel@nongnu.org; Bie, Tiwei ; Liang, Cunming
; Ye, Xiaolong ; Wa
Wed, Nov 7, 2018 at 4:36 PM Richard W.M. Jones wrote:
> Another thing I tried was to change the NBD server (nbdkit) so that it
> doesn't advertise zero support to the client:
>
> $ nbdkit --filter=log --filter=nozero memory size=6G logfile=/tmp/log \
> --run './qemu-img convert ./fedora-2
On Wed, Nov 07, 2018 at 04:56:48PM +0200, Nir Soffer wrote:
> Wed, Nov 7, 2018 at 4:36 PM Richard W.M. Jones wrote:
>
> > Another thing I tried was to change the NBD server (nbdkit) so that it
> > doesn't advertise zero support to the client:
> >
> > $ nbdkit --filter=log --filter=nozero memory
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Wednesday, November 7, 2018 2:38 PM
> To: Liang, Cunming ; Wang, Xiao W
> ; m...@redhat.com; alex.william...@redhat.com
> Cc: qemu-devel@nongnu.org; Bie, Tiwei ; Ye, Xiaolong
> ; Wang, Zhihong ; Daly, Dan
>
> Su
As discussed during "[PATCH v4 00/29] vhost-user for input & GPU"
review, let's define a common set of backend conventions to help with
management layer implementation, and interoperability.
v2:
- use a vhost-user.json schema to discover backends and describe
capability format
- drop --pidfil
On 7/11/18 0:06, Peter Maydell wrote:
On 6 November 2018 at 19:16, Philippe Mathieu-Daudé wrote:
On 6/11/18 19:43, Peter Maydell wrote:
I had an idea for how to get a rough list of source files
containing devices that haven't been QOMified. The theory
is that a pre-QOM device generally has an
From: Corey Minyard
This makes their function more clear and prevents conflicts when adding
the actual devices to the machine state, if necessary.
Signed-off-by: Corey Minyard
Cc: Paolo Bonzini
Cc: Richard Henderson
Cc: Eduardo Habkost
---
hw/i386/pc.c | 18 +-
hw/i3
David Hildenbrand writes:
> On 05.11.18 21:43, Markus Armbruster wrote:
>> David Hildenbrand writes:
>>
>>> On 05.11.18 16:37, Markus Armbruster wrote:
David Hildenbrand writes:
> On 31.10.18 18:55, Markus Armbruster wrote:
>> David Hildenbrand writes:
>>
>>> On 31.1
On Wed, Nov 07, 2018 at 01:45:35PM +, Peter Maydell wrote:
> On 7 November 2018 at 12:49, Eduardo Habkost wrote:
> > Now, why do we need --with-python, and why do we need to use
> > $(PYTHON) when running tests? If somebody wants to use a
> > different Python binary when running tests, they c
Hi Paolo,
On Thu, Sep 27, 2018 at 10:55:59AM +0200, Paolo Bonzini wrote:
> > What is the syntactic thing in this example which distinguishes
> > "user can toggle this" (ESP_PCI, ARM_VIRT, SUN4M) from "user
> > can't toggle this, it's just an internal thing selected by
> > other nodes" (the rest) ?
Hi
On Wed, Nov 7, 2018 at 4:49 PM Marc-André Lureau
wrote:
>
> The following patch is going to add compatiblity parameters for
> qemu <= 3.1.
>
I realize this may be good enough for x86 i440/q35 machines, but what
about other machines & architectures?
What do we officially support, for migratio
On 7/11/18 16:24, miny...@acm.org wrote:
From: Corey Minyard
This makes their function more clear and prevents conflicts when adding
the actual devices to the machine state, if necessary.
Signed-off-by: Corey Minyard
Cc: Paolo Bonzini
Cc: Richard Henderson
Cc: Eduardo Habkost
Reviewed-by
These changes allow SMBus access while doing a state transfer.
Seems like a good idea to me in general.
I have these queued for the SMBus IPMI driver work, of course.
From: Corey Minyard
Transfer the state information for the SMBus registers and
internal data so it will work on a VM transfer.
Signed-off-by: Corey Minyard
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Dr. David Alan Gilbert
---
hw/acpi/piix4.c | 3 ++-
hw/i2c/pm_smbus.c |
From: Corey Minyard
This was if the eeprom is accessed during a state transfer, the
transfer will be reliable.
Signed-off-by: Corey Minyard
Cc: Paolo Bonzini
Cc: Michael S. Tsirkin
Cc: Dr. David Alan Gilbert
---
hw/i2c/smbus_eeprom.c | 16 +++-
1 file changed, 15 insertions(+),
From: Corey Minyard
There is no vmstate handling for SMBus, so no device sitting on SMBus
can have a state transfer that works reliable. So add it.
Signed-off-by: Corey Minyard
Cc: Paolo Bonzini
Cc: Michael S. Tsirkin
Cc: Dr. David Alan Gilbert
---
hw/i2c/smbus.c | 14 +
Peter Maydell writes:
> On 6 November 2018 at 18:52, Thomas Huth wrote:
>> On 2018-11-06 19:49, Philippe Mathieu-Daudé wrote:
>>> On 6/11/18 19:17, Thomas Huth wrote:
There is no active maintainer, but since Peter is picking up
patches via qemu-...@nongnu.org, I think we could at least
On 11/5/18 6:19 AM, Cornelia Huck wrote:
> On Mon, 5 Nov 2018 12:03:10 +0100
> David Hildenbrand wrote:
>
>> I fail to see why this is useful as we require MSIX always and
>> completely fail adding a device.
>>
>> Signed-off-by: David Hildenbrand
>> ---
>> hw/s390x/s390-pci-bus.c | 2 --
>> hw
Under heavy IO (e.g. fio) the queue is not checked frequently enough for
pending commands. As a result some pending commands are timed out by the
linux sym53c8xx driver, which sends SCSI Abort messages for the timed out
commands. The SCSI Abort messages result in linux errors, which show up
on the
On Tue, 6 Nov 2018 19:42:12 +0100
Eric Auger wrote:
> Commit af7d64ede0b9 (hw/arm/sysbus-fdt: Allow device matching with DT
> compatible value) introduced a match_fn callback which gets called
> for each registered combo to check whether a sysbus device can be
> dynamically instantiated. However
Eduardo Habkost writes:
> On Wed, Nov 07, 2018 at 01:45:35PM +, Peter Maydell wrote:
>> On 7 November 2018 at 12:49, Eduardo Habkost wrote:
>> > Now, why do we need --with-python, and why do we need to use
>> > $(PYTHON) when running tests? If somebody wants to use a
>> > different Python b
On 11/7/18 6:13 AM, Richard W.M. Jones wrote:
(I'm not going to claim this is a bug, but it causes a large, easily
measurable performance regression in virt-v2v).
I haven't closely looked at at this email thread yet, but a quick first
impression:
In qemu 2.12 this behaviour changed:
$
On 11/7/18 5:21 AM, Peter Maydell wrote:
On 7 November 2018 at 02:56, Peter Xu wrote:
Strange, "make check -j8" failed on my hosts (I tried two) with either
Markus's pull tree or qemu master:
hw/core/ptimer.o: In function `timer_new_tl':
/home/xz/git/qemu/include/qemu/timer.h:536: undefined re
Hi,
I was wrong... Described problem with vhost-user is not possible.
It cannot enter tcp_chr_disconnect twice because of qemu global mutex (BQL).
Thus chardev event handler (main loop) and vhost_user_blk_set_status (VCPU) are
working under BQL.
30.10.2018, 20:12, "Marc-André Lureau" :
> Hi
>
> O
When I try to build qga-vss.dll I get the following link error:
LINKqga/vss-win32/qga-vss.dll
/usr/lib64/gcc/i686-w64-mingw32/8.2.0/../../../../i686-w64-mingw32/bin/ld:
qga/vss-win32/requester.o: in function `requester_freeze':
/src/qemu/qga/vss-win32/requester.cpp:284: undefined reference to
Am 07.11.2018 um 15:56 hat Nir Soffer geschrieben:
> Wed, Nov 7, 2018 at 4:36 PM Richard W.M. Jones wrote:
>
> > Another thing I tried was to change the NBD server (nbdkit) so that it
> > doesn't advertise zero support to the client:
> >
> > $ nbdkit --filter=log --filter=nozero memory size=6G
I am also able to reproduce this bug. The problem is that when hvf is
enabled, qemu will attempt to execute the xgetbv instruction, which
isn't supported on my processor (Intel Xeon X5670).
Here is a stack trace from lldb; the behavior is 100% reproducible for
me.
nathan@Nathans-Mac-Pro:~/src/qem
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20181106110548.4209-1-luc.mic...@greensocs.com
Subject: [Qemu-devel] [PATCH v4 00/16] gdbstub: support for the multiprocess
extension
=== TEST SCRIPT BEGIN ===
#!/bin/bash
1 - 100 of 172 matches
Mail list logo
