This patch provides downtime calculation per vCPU,
as a summary and as a overlapped value for all vCPUs.
This approach was suggested by Peter Xu, as an improvements of
previous approch where QEMU kept tree with faulted page address and cpus bitmask
in it. Now QEMU is keeping array with faulted pag
This modification is necessary for userfault fd features which are
required to be requested from userspace.
UFFD_FEATURE_THREAD_ID is a one of such "on demand" feature, which will
be introduced in the next patch.
QEMU need to use separate userfault file descriptor, due to
userfault context has int
This patch add request to kernel space for UFFD_FEATURE_THREAD_ID,
in case when this feature is provided by kernel.
DowntimeContext is incapsulated inside migration.c.
Signed-off-by: Alexey Perevalov
---
include/migration/migration.h | 12
migration/migration.c | 33 +++
This is third version of patch set.
First version was tagged as RFC, second was without version tag.
Difference since previous version (V3 -> V2)
- Downtime calculation approach was changed, thanks to Peter Xu
- Due to previous point no more need to keep GTree as well as bitmap of
cpus.
S
On 2017年04月26日 18:06, Liu, Yi L wrote:
> With vIOMMU exposed to guest, vIOMMU emulator needs to do translation
> between host and guest. e.g. a device-selective TLB flush, vIOMMU
> emulator needs to replace guest SID with host SID so that to limit
> the invalidation. This patch introduces a new cal
we can get the network interface statistics inside a virtual machine by
guest-network-get-interfaces command. it is very useful for us to monitor
and analyze network traffic.
Signed-off-by: ZhiPeng Lu
Signed-off-by: Daniel P. Berrange
---
qga/commands-posix.c | 80 ++
On 2017年04月27日 18:32, Peter Xu wrote:
> On Wed, Apr 26, 2017 at 06:06:32PM +0800, Liu, Yi L wrote:
>> VT-d implementations reporting PASID or PRS fields as "Set", must also
>> report ecap.ECS as "Set". Extended-Context is required for SVM.
>>
>> When ECS is reported, intel iommu driver would initia
On 28.04.2017 04:23, Eric Blake wrote:
> Commit 78f86a2b7 added a new test, but forgot to exclude the built
> binary from version control.
>
> Signed-off-by: Eric Blake
> ---
> tests/.gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/.gitignore b/tests/.gitignore
> index
Commit 78f86a2b7 added a new test, but forgot to exclude the built
binary from version control.
Signed-off-by: Eric Blake
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index 5ab00a9..40c2e3e 100644
--- a/tests/.gitignore
+++ b/tests/
Since all reset/shutdown requests have been associated with a
reason, we can expose the full reason rather than a simple bool
to the guest. Document that any future additions to the enum
type will still use a 'host-' or 'guest-' prefix.
Signed-off-by: Eric Blake
---
v4: s/ShutdownType/ShutdownCa
Libvirt would like to be able to distinguish between a SHUTDOWN
event triggered solely by guest request and one triggered by a
SIGTERM or other action on the host. While qemu_kill_report() is
already able to tell whether a shutdown was triggered by a host
signal (but NOT by a host UI event, such a
v2 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03185.html
v3 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05515.html
v4 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05539.html
Since then:
- fix braindead mistake of mine for using '
We want to track why a guest was shutdown; in particular, being able
to tell the difference between a guest request (such as ACPI request)
and host request (such as SIGINT) will prove useful to libvirt.
Since all requests eventually end up changing shutdown_requested in
vl.c, the logical change is
There is no signal 0 (kill(pid, 0) has special semantics to probe whether
a process is alive), rather than actually sending a signal 0). So we
can use the simpler 0, instead of -1, for our sentinel of whether a
shutdown request due to a signal has happened.
Suggested-by: Markus Armbruster
Signed
On Do, 2017-04-27 at 14:30 +0800, yuan.zh...@zte.com.cn wrote:＞ ＞ Mr.
Hoffmann,＞＞ ＞ ＞ ＞ Thank you for your time.＞ ＞ ＞ ＞ ＞ ＞ This email will describe
a new module that I'd like to commit to the＞ ＞ qemu code source.＞ ＞ ＞ ＞ We call
it as remote usb, and this is features:＞ ＞ ＞ ＞ 1. real usb device
On 03/30/2017 02:50 AM, Thomas Huth wrote:
> HMP commands do not get any automatic testing yet, so on certain
> QEMU machines, some HMP commands were causing crashes in the past.
> Thus we should test HMP commands in our test suite, too, to avoid
> that such problems creep in again in the future.
>
On 04/27/2017 04:13 PM, Peter Maydell wrote:
> On 27 April 2017 at 18:38, Wei Huang wrote:
>> CONFIG_ARM_V7M is used to control the compilation of NVIC and SysTick
>> Timer in QEMU. These two devices are not available when CONFIG_ARM_V7M
>> is un-defined. This can cause problems with ARMv7M code
On Thu, Apr 27, 2017 at 13:59:56 +0200, Richard Henderson wrote:
(snip)
> Signed-off-by: Emilio G. Cota
> Message-Id: <1493263764-18657-8-git-send-email-c...@braap.org>
> [rth: Replace gen_jr global variable with DISAS_EXIT state.]
> Signed-off-by: Richard Henderson
Just want to confirm that thi
On 04/27/2017 04:31 PM, Eric Blake wrote:
> v2 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03185.html
> v3 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05515.html
>
> Since then:
> - s/ShutdownType/ShutdownCause/ to avoid conflict with mingw header
Use the existing readline history function we are utilizing
to provide persistent command history across instances of qmp-shell.
This assists entering debug commands across sessions that may be
interrupted by QEMU sessions terminating, where the qmp-shell has
to be relaunched.
Signed-off-by: John
On Thu, 27 Apr 2017, Bruce Rogers wrote:
> >>> On 4/27/2017 at 03:09 PM, Stefano Stabellini
> >>> wrote:
> > On Thu, 27 Apr 2017, Bruce Rogers wrote:
> >> Commit f0c9d64a exposed the issue that with a xenfv machine using
> >> pci passthrough, acpi cpi hotplug code was being executed by mistake.
On Thu, Apr 27, 2017 at 14:00:04 +0200, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> tcg/aarch64/tcg-target.h | 2 +-
> tcg/aarch64/tcg-target.inc.c | 22 --
> 2 files changed, 21 insertions(+), 3 deletions(-)
Tested-by: Emilio G. Cota
Would be n
We now have macros in place to make it less verbose to add a scalar
to QDict and QList, so use them. To make this patch smaller to
review, a couple of subdirectories were done in earlier patches.
Patch created mechanically via:
spatch --sp-file scripts/coccinelle/qobject.cocci \
--macro-fil
Commit 62c39b3 introduced test-qga, and at face value, appears
to be testing the 'guest-sync' behavior that is recommended for
guests in sending 0xff to QGA to force the parser to reset. But
this aspect of the test has never actually done anything: the
qmp_fd() call chain converts its string argum
Noticed while checking Coccinelle results. Naming a label 'out:'
when it is only used on error paths is weird. Also, we had some
dead stores to 'ret'. Meanwhile we know that snapshot_options
is NULL on success and that QDECREF(NULL) is safe. So merge the
two exit paths into one by careful contro
Use the preferred blockdev-change-medium command instead.
Also, use of 'device' is deprecated; adding an explicit id on
the command line lets us use 'id' for both blockdev-change-medium
and eject.
Signed-off-by: Eric Blake
Reviewed-by: John Snow
Reviewed-by: Markus Armbruster
---
v5: add R-b
We have macros in place to make it less verbose to add a subtype
of QObject to both QDict and QList. While we have made cleanups
like this in the past (see commit fcfcd8ffc, for example), having
it be automated by Coccinelle makes it easier to maintain.
Patch created mechanically via:
spatch --s
Rather than making lots of callers wrap a scalar in a QInt, QString,
or QBool, provide helper macros that do the wrapping automatically.
Update the Coccinelle script to make mass conversions easy, although
the conversion itself will be done as a separate patches to ease
review and backport efforts
We have macros in place to make it less verbose to add a subtype
of QObject to both QDict and QList. While we have made cleanups
like this in the past (see commit fcfcd8ffc, for example), having
it be automated by Coccinelle makes it easier to maintain.
The script is separate from the cleanups, fo
No one outside of pcie_aer.h was using error injection; mark them
static for internal use.
Signed-off-by: Eric Blake
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Michael S. Tsirkin
Reviewed-by: Marcel Apfelbaum
Reviewed-by: Markus Armbruster
---
v5: add R-b
v4: no change
v3: new patch, s
Noticed while investigating Coccinelle cleanups. There is no need
for a temporary variable when we can use the new macro to do the
same thing with less typing.
Signed-off-by: Eric Blake
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Markus Armbruster
---
v5: add R-b
v4: new patch
---
util/q
This is a subset of my earlier post "Rip out dynamic JSON parsing"[1],
and then a rebase of that work onto master. It is available here:
git fetch git://repo.or.cz/qemu/ericb.git qapi-dynamic-json-v5
the tag name is a bit of a misnomer for the current series, but is
historically accurate.
Since
It's simpler to just use a C struct than it is to bundle things
into a QDict in one function just to pull them back out in the
caller. Plus, doing this gets rid of one more user of dynamic
JSON through qobject_from_jsonf(), as well as a memory leak of
the QDict.
While cleaning the code, fix thing
Hello,
Thomas Huth, on lun. 24 avril 2017 11:15:56 +0200, wrote:
> On 20.04.2017 22:43, Tao Wu wrote:
> > The current code looks buggy, we zero ti_i while we access
> > ti_dst/ti_src later.
Indeed.
> > Signed-off-by: Tao Wu
> > *mtod(m, struct tcpiphdr *) = *ti;
> > ti
>>> On 4/27/2017 at 03:09 PM, Stefano Stabellini
>>> wrote:
> On Thu, 27 Apr 2017, Bruce Rogers wrote:
>> Commit f0c9d64a exposed the issue that with a xenfv machine using
>> pci passthrough, acpi cpi hotplug code was being executed by mistake.
>> Guard calls to acpi_pcihp_device_plug_cb (and
We want to track why a guest was shutdown; in particular, being able
to tell the difference between a guest request (such as ACPI request)
and host request (such as SIGINT) will prove useful to libvirt.
Since all requests eventually end up changing shutdown_requested in
vl.c, the logical change is
Since all reset/shutdown requests have been associated with a
reason, we can expose the full reason rather than a simple bool
to the guest. Document that any future additions to the enum
type will still use a 'host-' or 'guest-' prefix.
Signed-off-by: Eric Blake
---
v4: s/ShutdownType/ShutdownCa
There is no signal 0 (kill(pid, 0) has special semantics to probe whether
a process is alive), rather than actually sending a signal 0). So we
can use the simpler 0, instead of -1, for our sentinel of whether a
shutdown request due to a signal has happened.
Suggested-by: Markus Armbruster
Signed
v2 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03185.html
v3 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05515.html
Since then:
- s/ShutdownType/ShutdownCause/ to avoid conflict with mingw header pollution
- fix long line
Eric Blake (4):
shutdown: S
On 04/27/2017 03:50 PM, John Snow wrote:
> Excised from an old patchset from 2015, just a couple of touchups.
>
> John Snow (2):
> iotests: clarify help text
> iotests: fix exclusion option
Reviewed-by: Eric Blake
[eww - we were really using 'ls' instead of 'echo' to expand a glob?
Your pat
On 04/26/2017 10:16 AM, Kamil Rytarowski wrote:
The default NetBSD package manager is pkgsrc and it installs Perl
along other third party programs under custom and configurable prefix.
The default prefix for binary prebuilt packages is /usr/pkg, and the
Perl executable lands in /usr/pkg/bin/perl.
On Thu, Apr 27, 2017 at 10:55:28AM +1000, Tim Ansell wrote:
> I'm about to add support for disabling the inbuilt or1k timer peripheral
> (as our SoC does not have it enabled). That isn't really a CPU feature so I
> think it still makes sense to have some type of feature field? Maybe CPU
> features
On 27 April 2017 at 18:38, Wei Huang wrote:
> CONFIG_ARM_V7M is used to control the compilation of NVIC and SysTick
> Timer in QEMU. These two devices are not available when CONFIG_ARM_V7M
> is un-defined. This can cause problems with ARMv7M code as it is tightly
> integrated with NVIC for process
On Thu, 27 Apr 2017, Bruce Rogers wrote:
> Commit f0c9d64a exposed the issue that with a xenfv machine using
> pci passthrough, acpi cpi hotplug code was being executed by mistake.
> Guard calls to acpi_pcihp_device_plug_cb (and corresponding
> acpi_pcihp_device_unplug_cb) with a check for xen_enab
On Thu, Apr 27, 2017 at 1:36 PM, Ashijeet Acharya
wrote:
> Previously posted series patches:
> v1: http://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg04641.html
>
> This series helps to provide chunk size independence for DMG driver to prevent
> denial-of-service in cases where untrusted f
If you are running out-of-tree, the -x option to exclude
a certain iotest is broken.
Replace porcelain usage of ls with a sturdier awk command.
Reviewed-by: Fam Zheng
Signed-off-by: John Snow
---
tests/qemu-iotests/common | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/te
Excised from an old patchset from 2015, just a couple of touchups.
John Snow (2):
iotests: clarify help text
iotests: fix exclusion option
tests/qemu-iotests/common | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
--
2.9.3
Split the help text to highlight the groups of options
a little better, carving out a clear "format" and
"protocols" section.
Signed-off-by: John Snow
---
tests/qemu-iotests/common | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tests/qemu-iotests/common b/tests/qemu-
On Thu, Apr 27, 2017 at 12:12:58PM +0200, Laurent Vivier wrote:
> We need to change the way we distribute the memory across
> the nodes. To keep compatibility between machine type version
> introduce a machine type dependent function.
>
> Signed-off-by: Laurent Vivier
> ---
> include/hw/boards.
On Thu, Apr 27, 2017 at 04:46:26PM +0200, Igor Mammedov wrote:
> On Thu, 27 Apr 2017 16:05:42 +0200
> Markus Armbruster wrote:
> > Igor Mammedov writes:
> > > On Thu, 27 Apr 2017 07:54:31 -0500
> > > Eric Blake wrote:
[...]
> > >>
> > >> Markus has asked that all new QMP commands have some test
On 04/27/2017 02:49 PM, no-re...@patchew.org wrote:
> Hi,
>
> This series failed automatic build test. Please find the testing commands and
> their output below. If you have docker installed, you can probably reproduce
> it
> locally.
>
> CC util/buffer.o
> In file included from
> /usr/
Commit f0c9d64a exposed the issue that with a xenfv machine using
pci passthrough, acpi cpi hotplug code was being executed by mistake.
Guard calls to acpi_pcihp_device_plug_cb (and corresponding
acpi_pcihp_device_unplug_cb) with a check for xen_enabled(). Without
this check I am seeing an error th
>>> On 4/27/2017 at 12:08 PM, Stefano Stabellini
>>> wrote:
> On Thu, 27 Apr 2017, Igor Mammedov wrote:
>> On Thu, 27 Apr 2017 10:51:23 -0600
>> "Bruce Rogers" wrote:
>>
>> >
>> >
>> > >>> On 4/27/2017 at 10:08 AM, Igor Mammedov wrote:
>> > > On Thu, 27 Apr 2017 09:44:31 -0600
>> > > "Br
Quoting David Gibson (2017-04-27 02:28:43)
> Migrating between different CPU versions is a bit complicated for ppc.
> A long time ago, we ensured identical CPU versions at either end by
> checking the PVR had the same value. However, this breaks under KVM
> HV, because we always have to use the ho
Quoting David Gibson (2017-04-27 02:28:42)
> Currently, the CPU compatibility mode is set when the cpu is initialized,
> then again when the guest negotiates features. This means if a guest
> negotiates a compatibility mode, then reboots, that compatibility mode
> will be retained across the reset
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v3 0/4] event: Add source information to SHUTDOWN
Message-id: 20170427192211.30640-1-ebl...@redhat.com
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
t
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH v3 0/4] event: Add source information to SHUTDOWN
Message-id: 20170427192211.30640-1-ebl...@redha
Since all reset/shutdown requests have been associated with a
reason, we can expose the full reason rather than a simple bool
to the guest. Document that any future additions to the enum
type will still use a 'host-' or 'guest-' prefix.
Signed-off-by: Eric Blake
---
v3: new patch. If we like thi
We want to track why a guest was shutdown; in particular, being able
to tell the difference between a guest request (such as ACPI request)
and host request (such as SIGINT) will prove useful to libvirt.
Since all requests eventually end up changing shutdown_requested in
vl.c, the logical change is
Libvirt would like to be able to distinguish between a SHUTDOWN
event triggered solely by guest request and one triggered by a
SIGTERM or other action on the host. While qemu_kill_report() is
already able to tell whether a shutdown was triggered by a host
signal (but NOT by a host UI event, such a
v2 was here:
https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03185.html
Since then:
- turn it from one patch into a series
- update iotests to pass (the combination of -qcow2, -file, and -nbd
is sufficient to cover all the changed tests)
- add cleanup patch to shutdown_signal initial valu
There is no signal 0 (kill(pid, 0) has special semantics to probe whether
a process is alive), rather than actually sending a signal 0). So we
can use the simpler 0, instead of -1, for our sentinel of whether a
shutdown request due to a signal has happened.
Suggested-by: Markus Armbruster
Signed
> Am 26.04.2017 um 10:33 schrieb Anton Nefedov :
>
> On error path (like i/o error in one of the coroutines), it's required to
> - wait for coroutines completion before cleaning the common structures
> - reenter dependent coroutines so they ever finish
>
> Introduced in 2d9187bc65.
>
> Signed
On Tue, Apr 25, 2017 at 3:36 AM, sundeep subbaraya
wrote:
> Hi Alistair,
>
> On Mon, Apr 24, 2017 at 11:14 PM, Alistair Francis
> wrote:
> +
> +isr = !!(st->regs[R_RIS] & TIMER_RIS_ACK);
> +ier = !!(st->regs[R_CTRL] & TIMER_CTRL_INTR);
> +
> +qemu_set_irq(st->irq,
On Thu, 27 Apr 2017, Greg Kurz wrote:
> The 9p protocol is transport agnostic: if an error occurs when copying data
> to/from the client, this should be handled by the transport layer [1] and
> the 9p server should simply stop processing requests [2].
>
> [1] can be implemented in the transport ma
On Thu, 27 Apr 2017, Greg Kurz wrote:
> Only pdu_complete() needs to notify the client that a request has completed.
>
> Signed-off-by: Greg Kurz
> ---
> hw/9pfs/9p.c |7 +--
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index c80ba67389
On 03/13/2017 01:18 AM, Markus Armbruster wrote:
> I'm proposing this is 2.9 because it fixes a documentation regression.
> It affects only documentation; generated C code is unchanged except
> for the removal of trailing space in PATCH 46.
>
> Additionally, my series fixes a number of bugs and c
On Thu, 27 Apr 2017, Greg Kurz wrote:
> The code only uses well known format strings. An unknown format token is a
> bug.
>
> Signed-off-by: Greg Kurz
Reviewed-by: Stefano Stabellini
> ---
> fsdev/9p-iov-marshal.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Thu, 27 Apr 2017, Greg Kurz wrote:
> These bits aren't related to the transport so let's move them to the core
> code.
>
> Signed-off-by: Greg Kurz
Reviewed-by: Stefano Stabellini
> ---
> hw/9pfs/9p.c |8 +++-
> hw/9pfs/9p.h |2 +-
> hw/9pfs/virtio-
On Thu, 27 Apr 2017, Igor Mammedov wrote:
> On Thu, 27 Apr 2017 10:51:23 -0600
> "Bruce Rogers" wrote:
>
> >
> >
> > >>> On 4/27/2017 at 10:08 AM, Igor Mammedov wrote:
> > > On Thu, 27 Apr 2017 09:44:31 -0600
> > > "Bruce Rogers" wrote:
> > >
> > >> >>> On 4/27/2017 at 03:11 AM, Igor Mammed
CONFIG_ARM_V7M is used to control the compilation of NVIC and SysTick
Timer in QEMU. These two devices are not available when CONFIG_ARM_V7M
is un-defined. This can cause problems with ARMv7M code as it is tightly
integrated with NVIC for processing IRQ and exception.
This patchset addresses the p
In current QEMU, when CONFIG_ARM_V7M is not configured, armv7m_nvic.c
and armv7m_systick.c won't be compiled. This causes dependency issues
for armv7m SoC because armv7m uses the device "armv7m_nvic". This patch
makes the compilation of armv7m.c and other v7m SoC dependent on
CONFIG_ARM_V7M.
Signe
M-profile CPUs relies on NVIC controller which won't be compiled if
CONFIG_ARM_V7M is not defined. To solve the problem, this patch
defines four NVIC stub functions. These functions are called when
CONFIG_ARM_V7M is not defined.
Signed-off-by: Wei Huang
---
target/arm/Makefile.objs | 1 +
targe
On Thu, 27 Apr 2017 10:51:23 -0600
"Bruce Rogers" wrote:
>
>
> >>> On 4/27/2017 at 10:08 AM, Igor Mammedov wrote:
> > On Thu, 27 Apr 2017 09:44:31 -0600
> > "Bruce Rogers" wrote:
> >
> >> >>> On 4/27/2017 at 03:11 AM, Igor Mammedov wrote:
> >> > On Wed, 26 Apr 2017 13:07:02 -0600
> >> > B
On Thu, Apr 27, 2017 at 07:25:23PM +0200, Igor Mammedov wrote:
[...]
> > > #
> > > # A discriminated record of NUMA options. (for OptsVisitor)
> > > #
> > > +# For 'cpu' type as arguments use a set of cpu properties returned
> > > +# by query-hotpluggable-cpus[].props, where node-id could be use
On Thu, 27 Apr 2017 13:32:25 -0300
Eduardo Habkost wrote:
> On Thu, Apr 27, 2017 at 03:14:06PM +0200, Igor Mammedov wrote:
> > On Wed, 26 Apr 2017 09:21:38 -0300
> > Eduardo Habkost wrote:
> >
> > adding Peter to CC list
> >
> > [...]
> >
> > > On Wed, Apr 19, 2017 at 01:14:58PM +0200, Igor M
Quoting David Gibson (2017-04-27 02:28:41)
> Server class POWER CPUs have a "compat" property, which is used to set the
> backwards compatibility mode for the processor. However, this only makes
> sense for machine types which don't give the guest access to hypervisor
> privilege - otherwise the c
From: "Dr. David Alan Gilbert"
Glib commit a6a875068779 (from 2013) made many of the glib assert
macros non-fatal if a flag is set.
This causes two problems:
a) Compilers moan that your code is unsafe even though you've
put an assert in before the point of use.
b) Someone evil could, in
>>> On 4/27/2017 at 10:08 AM, Igor Mammedov wrote:
> On Thu, 27 Apr 2017 09:44:31 -0600
> "Bruce Rogers" wrote:
>
>> >>> On 4/27/2017 at 03:11 AM, Igor Mammedov wrote:
>> > On Wed, 26 Apr 2017 13:07:02 -0600
>> > Bruce Rogers wrote:
>> >
>> >> Commit f0c9d64a exposed an issue with the cod
On 04/26/2017 07:30 AM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> There is a new update of qcow2-bitmap series - v17.
>
> web:
> https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=qcow2-bitmap-v17
> git: https://src.openvz.org/scm/~vsementsov/qemu.git (tag qcow2-bitmap-v17)
>
On Thu, Apr 27, 2017 at 03:14:06PM +0200, Igor Mammedov wrote:
> On Wed, 26 Apr 2017 09:21:38 -0300
> Eduardo Habkost wrote:
>
> adding Peter to CC list
>
> [...]
>
> > On Wed, Apr 19, 2017 at 01:14:58PM +0200, Igor Mammedov wrote:
> > > On Wed, 12 Apr 2017 18:02:39 -0300
> > > Eduardo Habkost
On Thu, Apr 27, 2017 at 06:24:17PM +0200, Markus Armbruster wrote:
> No review, just an observation.
>
> Mao Zhongyi writes:
>
> > Currently, net_socket_mcast_create(), net_socket_fd_init_dgram() and
> > net_socket_fd_init() use the function such as fprintf(), perror() to
> > report an error mes
>>> On 4/27/2017 at 10:08 AM, Igor Mammedov wrote:
> On Thu, 27 Apr 2017 09:44:31 -0600
> "Bruce Rogers" wrote:
>
>> >>> On 4/27/2017 at 03:11 AM, Igor Mammedov wrote:
>> > On Wed, 26 Apr 2017 13:07:02 -0600
>> > Bruce Rogers wrote:
>> >
>> >> Commit f0c9d64a exposed an issue with the cod
Mao Zhongyi writes:
> v2:
> * PATCH 02 reworking of patch 2 following Markus's suggestion that convert
> error_report()
> in the function called by net_socket_*_init() to Error. Also add many error
> handling
> information.
> * PATCH 03 net_socket_mcast_create(), net_socket_fd_init_dgram()
No review, just an observation.
Mao Zhongyi writes:
> Currently, net_socket_mcast_create(), net_socket_fd_init_dgram() and
> net_socket_fd_init() use the function such as fprintf(), perror() to
> report an error message.
>
> Now, convert these functions to Error.
>
> CC: jasow...@redhat.com, arm
On Thu, Apr 27, 2017 at 06:19:50PM +0200, Markus Armbruster wrote:
> Markus Armbruster writes:
>
> > Mao Zhongyi writes:
> >
> >> Currently, socket connection in net is realized by an old
> >> mechanism which is non-blocking.
> >>
> >> That old mechanism may cause net blocks on DNS lookups and
>
On Wed, Apr 26, 2017 at 04:04:15PM +0800, Mao Zhongyi wrote:
> Currently, socket connection in net is realized by an old
> mechanism which is non-blocking.
>
> That old mechanism may cause net blocks on DNS lookups and
> QEmu has already replaced it with QIOchannel in many features,
> such as migr
On Thu, Apr 27, 2017 at 11:59:26AM -0300, jos...@linux.vnet.ibm.com wrote:
> On Thu, Apr 27, 2017 at 10:55:04AM +0200, Paolo Bonzini wrote:
> >
> >
> > On 24/04/2017 19:19, Jose Ricardo Ziviani wrote:
> > > These trace events were very useful to help me to understand and find a
> > > reordering i
mouse works better with debug & fix patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1592351
Title:
mouse pointer offset with gtk,gl=on
Status in QEMU:
Confirmed
Bug description:
When I tu
Markus Armbruster writes:
> Mao Zhongyi writes:
>
>> Currently, socket connection in net is realized by an old
>> mechanism which is non-blocking.
>>
>> That old mechanism may cause net blocks on DNS lookups and
>> QEmu has already replaced it with QIOchannel in many features,
>> such as migrati
Mao Zhongyi writes:
> When -net socket fails, it first reports a specific error, then
> a generic one, like this:
>
> $ qemu-system-x86_64 -net socket,
> qemu-system-x86_64: -net socket: exactly one of fd=, listen=, connect=,
> mcast= or udp= is required
> qemu-system-x86_64: -net so
Richard Henderson writes:
> From: "Emilio G. Cota"
>
> Signed-off-by: Emilio G. Cota
> Message-Id: <1493263764-18657-2-git-send-email-c...@braap.org>
> Signed-off-by: Richard Henderson
Reviewed-by: Alex Bennée
> ---
> cpu-exec.c | 6 ++
> include/exec/exec-all.h | 2 ++
>
On Thu, Apr 27, 2017 at 05:09:26PM +0200, Laurent Vivier wrote:
> On 27/04/2017 16:09, Eduardo Habkost wrote:
> > On Thu, Apr 27, 2017 at 12:12:58PM +0200, Laurent Vivier wrote:
> >> We need to change the way we distribute the memory across
> >> the nodes. To keep compatibility between machine type
Richard Henderson writes:
> We need to coordinate with the TCG_OVERSIZED_GUEST test in cputlb.c,
> and allow 64-bit atomics even though sizeof(void *) == 4.
Hmm you say this here but we never actually do it. But the other changes
seem fine.
>
> Signed-off-by: Richard Henderson
> ---
> includ
On Thu, 27 Apr 2017 09:44:31 -0600
"Bruce Rogers" wrote:
> >>> On 4/27/2017 at 03:11 AM, Igor Mammedov wrote:
> > On Wed, 26 Apr 2017 13:07:02 -0600
> > Bruce Rogers wrote:
> >
> >> Commit f0c9d64a exposed an issue with the code order in acpi_setup.
> >> As of that commit, a xenfv machine typ
Mouse still doesn't work properly with 2.9.0 and Ubuntu 17.04 guest
-smp 2 -enable-kvm -vga virtio -display gtk,gl=on -m 2048 -cdrom
ubuntu-17.04-desktop-amd64.iso
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
Richard Henderson writes:
> We have required a v9 cpu since 9b9c37c36439ee0452632253dac7a31897f27f70.
> However, the flags we were using did not reliably enable v8plus, which
> meant that the compiler didn't know it could inline 64-bit atomics.
>
> Signed-off-by: Richard Henderson
Reviewed-by:
Richard Henderson writes:
> Avoid a "cast from pointer to integer of different size" warning
> by using the proper host type.
>
> Signed-off-by: Richard Henderson
Reviewed-by: Alex Bennée
> ---
> target/nios2/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
This support was introduced in QEMU 2.6 last year. Some info here:
https://www.berrange.com/posts/2016/08/16/improving-qemu-security-part-6
-tls-support-for-character-devices/
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member o
Mao Zhongyi writes:
> Currently, socket connection in net is realized by an old
> mechanism which is non-blocking.
>
> That old mechanism may cause net blocks on DNS lookups and
> QEmu has already replaced it with QIOchannel in many features,
> such as migration.
>
> Convert it to QIOchannel for
1 - 100 of 271 matches
Mail list logo
