On 06/27/2014 04:47 PM, Nikunj A Dadhania wrote:
> PAPR compliant guest calls this in absence of kdump. This finally
> reaches the guest and can be handled according to the policies set by
> higher level tools(like taking dump) for further analysis by tools like
> crash.
>
> Linux kernel calls thi
PAPR compliant guest calls this in absence of kdump. This finally
reaches the guest and can be handled according to the policies set by
higher level tools(like taking dump) for further analysis by tools like
crash.
Linux kernel calls this only when the extended version of os,term is
implemented to
Useful for identifying the guest/host uniquely within the
guest. Adding following properties to the guest root node.
vm,uuid - uuid of the guest
host-model - Host model number
host-serial - Host machine serial number
hypervisor type - Tells its "kvm"
Signed-off-by: Nikunj A Dadhania
---
hw/ppc/
MAX_CPUS 256 is inconsistent with qemu supporting upto 255 cpus. This
MAX_CPUS number was percolated back to "virsh capabilities" with wrong
max_cpus.
Signed-off-by: Nikunj A Dadhania
---
hw/ppc/spapr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/ppc/spapr.c b/hw/ppc/s
Am 27.06.2014 um 06:59 hat Paolo Bonzini geschrieben:
> Il 27/06/2014 03:15, Ming Lei ha scritto:
> >On Thu, Jun 26, 2014 at 11:57 PM, Paolo Bonzini wrote:
> >>We can implement (advisory) calls like bdrv_plug/bdrv_unplug in order to
> >>restore the previous levels of performance.
> >
> >Yes, that
> -Original Message-
> From: peter.crosthwa...@petalogix.com
> [mailto:peter.crosthwa...@petalogix.com] On Behalf Of
> Peter Crosthwaite
> Sent: Friday, June 27, 2014 10:11 AM
> To: Pavel Dovgaluk; Fréderic Konrad
> Cc: qemu-devel@nongnu.org Developers; Paolo Bonzini
> Subject: Re: [Qemu-d
Hi Pavel,
On Fri, Jun 27, 2014 at 3:18 PM, Pavel Dovgaluk
wrote:
> Hello!
>
> We want to publish set of patches related to the reverse execution and
> deterministic replay of qemu.
> Our implementation of deterministic replay can be used for deterministic and
> reverse debugging of
> guest code
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Thursday, June 26, 2014 3:52 PM
> To: Bhushan Bharat-R65777
> Cc: qemu-...@nongnu.org; qemu-devel@nongnu.org; ma...@linux.vnet.ibm.com
> Subject: Re: [PATCH 5/5 v5] ppc: Add hw breakpoint watchpoint support
>
>
>
On 06/27/2014 06:26 AM, Richard Henderson wrote:
> With rt != r0 on loads, we use rt for scratch. If we need an index
> register different from base, we can't use rt, but r0 is usable.
That fixes the problem : a x86_64 fedora 20 TCG guest now runs under a
the latest qemu, (trusty ppc64le host)
2014-06-27 12:55 GMT+08:00 Paolo Bonzini :
> Il 27/06/2014 04:08, Le Tan ha scritto:
>
>> 1. In struct IOMMUTLBEntry, I think the addr_mask field should be the
>> mask of the page offset, right? But I see different usages of this
>> field. In spapr_tce_translate_iommu(), the addr_mask field is assi
Hello!
We want to publish set of patches related to the reverse execution and
deterministic replay of qemu.
Our implementation of deterministic replay can be used for deterministic and
reverse debugging of
guest code through gdb remote interface.
Execution recording writes non-deterministic eve
On Fri, Jun 27, 2014 at 12:01 AM, Damjan Marion wrote:
> Old code was affected by memory gaps which resulted in buffer pointers
> pointing to address outside of the mapped regions.
>
> Here we are introducing following changes:
> - new function qemu_get_ram_block_host_ptr() returns host pointer
Il 27/06/2014 03:15, Ming Lei ha scritto:
On Thu, Jun 26, 2014 at 11:57 PM, Paolo Bonzini wrote:
We can implement (advisory) calls like bdrv_plug/bdrv_unplug in order to
restore the previous levels of performance.
Yes, that is also what I am thinking, or interfaces like bdrv_queue_io()
and bd
Il 27/06/2014 04:08, Le Tan ha scritto:
1. In struct IOMMUTLBEntry, I think the addr_mask field should be the
mask of the page offset, right? But I see different usages of this
field. In spapr_tce_translate_iommu(), the addr_mask field is assigned
with the mask of the page offset. However, in pbm
On (Thu) 26 Jun 2014 [17:50:02], Laszlo Ersek wrote:
> Libvirt wants to know about the guest-side connection state of some
> virtio-serial ports (in particular the one(s) assigned to guest agent(s)).
> Report such states with a new monitor event.
>
> RHBZ: https://bugzilla.redhat.com/show_bug.cgi?
With rt != r0 on loads, we use rt for scratch. If we need an index
register different from base, we can't use rt, but r0 is usable.
Signed-off-by: Richard Henderson
---
This ought to fix the problem that Greg reported.
That we need to use --enable-debug-tcg to see the assert, and that I
didn't
On Thu, Jun 26, 2014 at 10:55:33AM -0600, Eric Blake wrote:
> On 06/26/2014 12:13 AM, Hu Tao wrote:
> > We already have ROUND_UP but there are similar macros and ROUND_UP-like
> > lines all around, replace them with ROUND_UP and clean up similar macros.
> >
> > Signed-off-by: Hu Tao
> > ---
>
>
On Thu, Jun 26, 2014 at 05:52:45AM -0600, Eric Blake wrote:
> On 06/26/2014 12:13 AM, Hu Tao wrote:
> > We already have ROUND_UP but there are similar macros and ROUND_UP-like
> > lines all around, replace them with ROUND_UP and clean up similar macros.
>
> Not a review (yet), but a question - how
Hi, Stefan & Kevin,
Could you help to have a look at this version? We've discussed about
this last November and now switch it to QemuOpts.
Thanks,
Chunyan
>>> On 6/23/2014 at 05:17 PM, in message
<1403515022-24802-1-git-send-email-cy...@suse.com>, Chunyan Liu
wrote:
> Add 'nocow' option so tha
On Thu, Jun 26, 2014 at 06:33:20PM -0300, Eduardo Habkost wrote:
> We don't support sparse NUMA node IDs yet, so this changes QEMU to
> reject configs where not all nodes are present.
>
> Signed-off-by: Eduardo Habkost
> ---
> numa.c | 17 -
> 1 file changed, 16 insertions(+), 1
On Thu, Jun 26, 2014 at 06:33:19PM -0300, Eduardo Habkost wrote:
> The same nodeid shouldn't appear multiple times in the command-line.
>
> In addition to detecting command-line mistakes, this will fix a bug
> where nb_numa_nodes may become larger than MAX_NODES (and cause
> out-of-bounds access o
http://wiki.qemu.org/Features/ResetAPI：
system reseta hardware mechanism for setting or returning all hardware
states to the initial conditions.* Use caseIn qemu, system_system_reset().
cold reset(power on reset)system reset following the application of power.
* Use caseIn qemu, system_reset()
On Thu, Jun 26, 2014 at 06:33:18PM -0300, Eduardo Habkost wrote:
> Based on "enable sparse node numbering" patch from Nishanth Aravamudan,
> but without the code to actually support sparse node IDs. This just adds
> the code to keep track of present/non-present nodes on the command-line,
> without
2014-06-26 22:05 GMT+08:00 Paolo Bonzini :
> Il 26/06/2014 16:01, Le Tan ha scritto:
>
>> Hi Paolo,
>> I am adding intel-iommu emulation to q35 for the GSoC project. I am
>> confused about AddressSpace and I believe that you can help me. :)
>> 1. For intel-iommu emulation, I have to read the transl
http://wiki.qemu.org/Features/PostCopyLiveMigration
in description：
“This is is yet” should be changed to "This is "Or "It is "
On Thu, Jun 26, 2014 at 11:57 PM, Paolo Bonzini wrote:
> This is indeed a difference between the ioq-based and block-based backends.
> ioq could submit more than one request with the same io_submit system call.
>
Yes, I have been thinking that is advantage of qemu virtio dataplane, but
it isn't a
On Thu, Jun 26, 2014 at 11:29 PM, Peter Maydell
wrote:
> On 24 June 2014 05:41, Peter Crosthwaite wrote:
>> Subject should read:
>>
>> "convert to Object::init()"
>>
>> On Tue, Jun 24, 2014 at 2:24 PM, Alistair Francis
>> wrote:
>>> SysBusDevice::init is deprecated. Convert to Object::init
>>> a
On Thu, Jun 26, 2014 at 9:38 PM, Peter Crosthwaite
wrote:
> On Thu, Jun 26, 2014 at 3:02 PM, Alistair Francis
> wrote:
>> Remove the old PMCCNTR code and replace it with calls to the new
>> pmccntr_sync() function and the CCNT_ENABLED macro
>
> arm_ccnt_enabled() function.
>
>>
>> Signed-off-by:
On Thu, Jun 26, 2014 at 9:42 PM, Peter Maydell wrote:
> This patchseries fixes some cases for pxa2xx and strongarm
> where we'd defined a vmstate struct but forgotten to actually
> register it (caught by new warnings in clang 3.4).
>
> As a prerequisite (suggested by Peter Crosthwaite) we clean
>
On Tue, Jun 24, 2014 at 4:06 PM, Alistair Francis
wrote:
> SysBusDevice::init is deprecated. Convert to Object::init and
> Device::realize as prescribed by QOM conventions.
>
> Signed-off-by: Alistair Francis
Reviewed-by: Peter Crosthwaite
CC Peter for target-arm.
Regards,
Peter
> ---
>
> h
Signed-off-by: Reza Jelveh
---
hw/ide/ahci.c | 11 ---
hw/ide/ahci.h | 2 ++
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
index 9bae22e..ee3613f 100644
--- a/hw/ide/ahci.c
+++ b/hw/ide/ahci.c
@@ -639,6 +639,11 @@ static void ahci_write_fis
On 06/26/2014 03:38 PM, Max Reitz wrote:
> For some protocol block drivers, the "filename" attribute in their BDSs
> is unset due to bdrv_file_open() removing it from the options QDict
> before bdrv_open_common() is able to copy it into the BDS. Fix this by
> not removing it until until bdrv_open_c
On 06/26/2014 03:33 PM, Eduardo Habkost wrote:
> This is just a cleanup to make sure QEMU validate the NUMA node IDs on the
Yay - this counts as a bug fix, so good for inclusion in 2.1.
> command-line. After that, we may eventually change the code to accept sparse
> node IDs under some circumstan
On 26.06.2014 23:46, Eric Blake wrote:
On 06/26/2014 03:17 PM, Max Reitz wrote:
On 25.06.2014 16:35, Kevin Wolf wrote:
This is the first part of an attempt for disentangling bdrv_open(). At
the end
of this series, bdrv_open() code is somewhat easier to read, but the real
changes (including some
On 06/26/2014 03:17 PM, Max Reitz wrote:
> On 25.06.2014 16:35, Kevin Wolf wrote:
>> This is the first part of an attempt for disentangling bdrv_open(). At
>> the end
>> of this series, bdrv_open() code is somewhat easier to read, but the real
>> changes (including some bug fixes and changes of beh
On 07.06.2014 23:21, Max Reitz wrote:
On 24.05.2014 23:24, Max Reitz wrote:
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr
Add a new test for qemu-iotests which checks whether the "filename" (and
consequently the "file") attribute is set for images which are opened
over NBD.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/097 | 72 ++
tests/qemu-iotests/097.out | 13 ++
If "filename" is removed from the options QDict before entering
bdrv_open_common(), it cannot be stored in the BDS. Therefore, wait
until it has been copied there and remove it from the options only
afterwards.
This fixes "filename" in the BDS being empty for block drivers which do
not need the f
For some protocol block drivers, the "filename" attribute in their BDSs
is unset due to bdrv_file_open() removing it from the options QDict
before bdrv_open_common() is able to copy it into the BDS. Fix this by
not removing it until until bdrv_open_common() has indeed copied it.
v3:
- Patch 1: R
The same nodeid shouldn't appear multiple times in the command-line.
In addition to detecting command-line mistakes, this will fix a bug
where nb_numa_nodes may become larger than MAX_NODES (and cause
out-of-bounds access on the numa_info array).
Signed-off-by: Eduardo Habkost
---
numa.c | 5 ++
This is just a cleanup to make sure QEMU validate the NUMA node IDs on the
command-line. After that, we may eventually change the code to accept sparse
node IDs under some circumstances (but I am not sure that would be material for
QEMU 2.1).
Cc: Nishanth Aravamudan
Cc: "Michael S. Tsirkin"
Cc:
Based on "enable sparse node numbering" patch from Nishanth Aravamudan,
but without the code to actually support sparse node IDs. This just adds
the code to keep track of present/non-present nodes on the command-line,
without changing any behavior.
Signed-off-by: Nishanth Aravamudan
[Rename max_n
We don't support sparse NUMA node IDs yet, so this changes QEMU to
reject configs where not all nodes are present.
Signed-off-by: Eduardo Habkost
---
numa.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/numa.c b/numa.c
index e93407a..96fe5dd 100644
--- a/n
Il 26/06/2014 22:19, Luiz Capitulino ha scritto:
Here goes a gdb backtrace:
#0 0x7f298ce31759 in syscall () from /lib64/libc.so.6
#1 0x7f29939b0b56 in futex_wait (ev=0x7f2994548f18, val=4294967295)
at
/home/lcapitulino/work/src/upstream/qmp-unstable/util/qemu-thread-posix.c:304
#2
On 25.06.2014 16:35, Kevin Wolf wrote:
This is the first part of an attempt for disentangling bdrv_open(). At the end
of this series, bdrv_open() code is somewhat easier to read, but the real
changes (including some bug fixes and changes of behaviour) haven't happened
yet.
Just sending out the f
Old code was affected by memory gaps which resulted in buffer pointers
pointing to address outside of the mapped regions.
Here we are introducing following changes:
- new function qemu_get_ram_block_host_ptr() returns host pointer
to the ram block, it is needed to calculate offset of specific
Hi Richard,
If setup qemu to use a watchdog with action pause, like this:
# qemu [...] -watchdog i6300esb -watchdog-action pause
qemu will completely hang when the watchdog fires. I started trying to
bisect, but I went as down as qemu v1.7.0 and the bug exists there.
Here goes a gdb backtrace:
On 26.06.2014 22:01, Max Reitz wrote:
On 26.06.2014 21:46, Eric Blake wrote:
On 06/26/2014 01:09 PM, Max Reitz wrote:
If "filename" is removed from the options QDict before entering
bdrv_open_common(), it cannot be stored in the BDS. Therefore, wait
until it has been copied there and remove it
On 06/26/14 22:16, Laszlo Ersek wrote:
> 2014-06-26 15:41:37.895+: 1637: debug :
> qemuMonitorJSONIOProcessLine:172 : QEMU_MONITOR_RECV_EVENT:
> mon=0x7f2e2400cfd0 event={"timestamp": {"seconds": 1403797297,
> "microseconds": 895242}, "event": "VSERPORT_CHANGE", "data": {"open":
> true, "id":
On 06/26/14 18:37, Eric Blake wrote:
> On 06/26/2014 09:50 AM, Laszlo Ersek wrote:
>> Changes in v3: patch 1 creates the event with a "bool" field called
>> "open" in the data portion, instead of introducing a two-valued enum.
>> Patch 2 is left intact. Retested.
>>
>> Laszlo Ersek (2):
>> virtio
Hello,
Just to add my two bits.
I will fully support getting all the necessary parts of ivshmem into tree
where appropriate, both qemu and a driver in Linux. I understand those
concerns.
I do not have the time to fully maintain ivshmem at the level needed, but I
will help as much as I can.
Sor
On 26.06.2014 21:46, Eric Blake wrote:
On 06/26/2014 01:09 PM, Max Reitz wrote:
If "filename" is removed from the options QDict before entering
bdrv_open_common(), it cannot be stored in the BDS. Therefore, wait
until it has been copied there and remove it from the options only
afterwards.
This
On 06/26/2014 06:51 AM, Andreas Färber wrote:
> I assume this pull broke ppc64 support on Mac OS X. It now says #error
> "Unsupported abi" (1734) plus errors about LINK_AREA_SIZE (1763) and
> LR_OFFSET (1775), all in tcg/ppc/tcg-target.c. It used to build and work
> okay before.
Yep, Peter's got a
On 06/26/2014 08:37 AM, Peter Maydell wrote:
> +++ b/tcg/ppc/tcg-target.c
> @@ -1716,6 +1716,9 @@ static void tcg_out_qemu_st(TCGContext *s, const TCGArg
> *args, bool is_64)
> # define LINK_AREA_SIZE(6 * SZR)
> # define LR_OFFSET (1 * SZR)
> # define TCG_TAR
On 06/26/2014 01:09 PM, Max Reitz wrote:
> If "filename" is removed from the options QDict before entering
> bdrv_open_common(), it cannot be stored in the BDS. Therefore, wait
> until it has been copied there and remove it from the options only
> afterwards.
>
> This fixes "filename" in the BDS b
On Tue, Jun 24, 2014 at 10:40:38AM -0700, Nishanth Aravamudan wrote:
> Sparse node numbering occurs on powerpc in practice under PowerVM. In
> order to emulate the same NUMA topology under qemu, the assumption that
> NUMA nodes are linearly ordered has to be removed. qemu actually already
> support
If "filename" is removed from the options QDict before entering
bdrv_open_common(), it cannot be stored in the BDS. Therefore, wait
until it has been copied there and remove it from the options only
afterwards.
This fixes "filename" in the BDS being empty for block drivers which do
not need the fi
Add a new test for qemu-iotests which checks whether the "filename" (and
consequently the "file") attribute is set for images which are opened
over NBD.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/097 | 72 ++
tests/qemu-iotests/097.out | 13 ++
For some protocol block drivers, the "filename" attribute in their BDSs
is unset due to bdrv_file_open() removing it from the options QDict
before bdrv_open_common() is able to copy it into the BDS. Fix this by
not removing it until until bdrv_open_common() has indeed copied it.
v2:
- Patch 1: O
On 23.06.2014 10:35, Stefan Hajnoczi wrote:
On Wed, Jun 18, 2014 at 12:14:08AM +0200, Max Reitz wrote:
For some protocol block drivers, the "filename" attribute in their BDSs
is unset due to bdrv_file_open() removing it from the options QDict
before bdrv_open_common() is able to copy it into the
On Thu, Jun 26, 2014 at 10:58:07AM -0700, Nishanth Aravamudan wrote:
> On 26.06.2014 [17:09:25 +0800], Hu Tao wrote:
> > On Wed, Jun 25, 2014 at 09:23:17PM +0300, Michael S. Tsirkin wrote:
> > > On Wed, Jun 25, 2014 at 01:52:56PM -0300, Eduardo Habkost wrote:
> > > > On Wed, Jun 25, 2014 at 09:13:5
On 26.06.2014 [17:09:25 +0800], Hu Tao wrote:
> On Wed, Jun 25, 2014 at 09:23:17PM +0300, Michael S. Tsirkin wrote:
> > On Wed, Jun 25, 2014 at 01:52:56PM -0300, Eduardo Habkost wrote:
> > > On Wed, Jun 25, 2014 at 09:13:59AM -0700, Nishanth Aravamudan wrote:
> > > > On 25.06.2014 [13:21:34 +0200],
Implement kvm_arm_vcpu_init() as a simple call to arm_arm_vcpu_init()
(which uses the KVM_ARM_VCPU_INIT vcpu ioctl to tell the kernel
to re-initialize the vCPU), rather than via the complicated code
which saves a copy of the register state on first init and then
writes it back to the kernel. This i
I went back and tried the 1.7 and 1.6 releases, and they both seem to
have been broken as well wrt cmos alarms waking from suspend.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1334397
Title:
cmos
On 06/26/14 04:23, Chen, Tiejun wrote:
On 2014/6/26 10:00, Chen, Tiejun wrote:
On 2014/6/26 7:04, Slutz, Donald Christopher wrote:
On 06/24/14 22:49, Chen, Tiejun wrote:
On 2014/5/19 19:22, Gerd Hoffmann wrote:
Hi,
Gerd,
Sorry I return this discussion again.
As we discussed here, we
On 06/26/2014 12:13 AM, Hu Tao wrote:
> We already have ROUND_UP but there are similar macros and ROUND_UP-like
> lines all around, replace them with ROUND_UP and clean up similar macros.
>
> Signed-off-by: Hu Tao
> ---
All of these conversions are correct, so:
Reviewed-by: Eric Blake
However,
Subject better have a component prefix "[PATCH] tests: Functions bus_foreach
and device_find from libqos virtio API".
See also "git log tests/".
Fam
On Thu, 06/26 16:34, Marc Marí wrote:
> Virtio header has been changed to compile and work with a real device.
> Functions bus_foreach and device_
On 06/26/2014 09:50 AM, Laszlo Ersek wrote:
> Changes in v3: patch 1 creates the event with a "bool" field called
> "open" in the data portion, instead of introducing a two-valued enum.
> Patch 2 is left intact. Retested.
>
> Laszlo Ersek (2):
> virtio-serial: report frontend connection state vi
On 06/26/2014 07:25 AM, Paolo Bonzini wrote:
> Il 26/06/2014 15:17, Luiz Capitulino ha scritto:
>>> > We're really close to hard freeze and by extension the release. Do
>>> > _not_ strive for perfection. Get something that is mostly okay and is
>>> > an obvious patch. We'll then have 3 weeks to
On 06/26/2014 07:43 AM, Luiz Capitulino wrote:
> Fair enough. Here goes the patch. As each commit dropped a section of the
> file, it was easier just to re-add it. ACKs wanted.
>
> Subject: [PATCH] qmp: add qmp-events.txt back
>
> The conversion of events to the QAPI, resulted in the removal of
Il 26/06/2014 18:25, Eric Blake ha scritto:
Actually, there is a second new event on queue right now:
https://lists.gnu.org/archive/html/qemu-devel/2014-06/msg06561.html
Ok. FWIW, I consider that series a bugfix so it can go in after hard
freeze. Same for the patch that lets management recon
If a fix has already been committed, is there a branch or tag in the
qemu git repo I should validate this with?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1334397
Title:
cmos RTC alarms no longe
Il 26/06/2014 16:53, Peter Maydell ha scritto:
>> This will break running BE32 binaries with "-cpu any"
>> (which sets all the features we know about, including
>> ARM_FEATURE_V7).
>
> Yes, this was on purpose.
I would expect that anybody running BE32 binaries is
probably running them with -cpu
This is indeed a difference between the ioq-based and block-based
backends. ioq could submit more than one request with the same
io_submit system call.
We can implement (advisory) calls like bdrv_plug/bdrv_unplug in order to
restore the previous levels of performance.
Note that some fallout
On Thu, Jun 26, 2014 at 09:06:03AM -0600, Eric Blake wrote:
> On 06/23/2014 06:32 AM, Chrysostomos Nanakos wrote:
> > VM Image on Archipelago volume is specified like this:
> >
> > file=archipelago:[/mport=[:vport=][:
> > segment=]]
> >
> > or
> >
> > file.driver=archipelago,file.volume=[,file.m
Hi Vince,
Yes, I did see the patches for the new server. I will review within the
week.
Cheers,
Cam
On Thu, Jun 26, 2014 at 9:37 AM, Vincent JARDIN
wrote:
> Hi Cam,
>
> FYI, David did implement a new server.
> http://lists.nongnu.org/archive/html/qemu-devel/2014-06/msg04978.html
>
> which
Changes in v3: patch 1 creates the event with a "bool" field called
"open" in the data portion, instead of introducing a two-valued enum.
Patch 2 is left intact. Retested.
Laszlo Ersek (2):
virtio-serial: report frontend connection state via monitor
char: report frontend open/closed state in '
In addition to the on-line reporting added in the previous patch, allow
libvirt to query frontend state independently of events.
Libvirt's path to identify the guest agent channel it cares about differs
between the event added in the previous patch and the QMP response field
added here. The event
Libvirt wants to know about the guest-side connection state of some
virtio-serial ports (in particular the one(s) assigned to guest agent(s)).
Report such states with a new monitor event.
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1080376
Signed-off-by: Laszlo Ersek
---
Notes:
v3:
Hello,
I'll be sending a new version (V3) of the patches on Monday. The patches add
QemuOpts
handling to the "-icount option". If you want I can only send the part of the
patch
that adds QemuOpts support.
Best regards,
Sebastian Tanase
- Mail original -
> De: "Paolo Bonzini"
> À: "Fr
On Thu, 26 Jun 2014 17:58:21 +0200
Markus Armbruster wrote:
> Paolo Bonzini writes:
>
> > Il 26/06/2014 17:37, Markus Armbruster ha scritto:
> >> Paolo Bonzini writes:
> >>
> >>> From: Wenchao Xia
> >>>
> >>> Signed-off-by: Wenchao Xia
> >>> Signed-off-by: Paolo Bonzini
> >>
> >> This bro
Paolo Bonzini writes:
> Il 26/06/2014 17:37, Markus Armbruster ha scritto:
>> Paolo Bonzini writes:
>>
>>> From: Wenchao Xia
>>>
>>> Signed-off-by: Wenchao Xia
>>> Signed-off-by: Paolo Bonzini
>>
>> This broke tests/qemu-iotests/041. Apparently, the BLOCK_JOB_ERROR
>> event changed from
>>
On Thu, 26 Jun 2014 17:50:08 +0200
Markus Armbruster wrote:
> Paolo Bonzini writes:
>
> > This includes:
> >
> > - Max's dependency fixes for QAPI scripts
> >
> > - Wenchao's QAPI event series
> >
> > - my thread-safety fixes, rebased onto QAPI events
>
> The QAPI event series messed up two ou
Paolo Bonzini writes:
> This includes:
>
> - Max's dependency fixes for QAPI scripts
>
> - Wenchao's QAPI event series
>
> - my thread-safety fixes, rebased onto QAPI events
The QAPI event series messed up two out of three event types tested in
qemu-iotests, if I count them correctly.
How can w
On Thu, Jun 26, 2014 at 11:43 PM, Paolo Bonzini wrote:
> Il 26/06/2014 17:37, Ming Lei ha scritto:
>
>> On Thu, Jun 26, 2014 at 11:29 PM, Paolo Bonzini
>> wrote:
>>>
>>> Il 26/06/2014 17:14, Ming Lei ha scritto:
>>>
Hi Stefan,
I found VM block I/O thoughput is decreased by more tha
Hi all,
while playing around with the vmware vga driver I noticed that there seems
to be a race condition when the resolution is changed. I was able to trigger
this also with std vga. Attached valgrind produces always an output similar to
this:
==3346== Thread 1:
==3346== Invalid read of size 8
On Thu, 26 Jun 2014 17:40:57 +0200
Paolo Bonzini wrote:
> Il 26/06/2014 17:37, Markus Armbruster ha scritto:
> > Paolo Bonzini writes:
> >
> >> From: Wenchao Xia
> >>
> >> Signed-off-by: Wenchao Xia
> >> Signed-off-by: Paolo Bonzini
> >
> > This broke tests/qemu-iotests/041. Apparently, th
Il 26/06/2014 17:37, Ming Lei ha scritto:
On Thu, Jun 26, 2014 at 11:29 PM, Paolo Bonzini wrote:
Il 26/06/2014 17:14, Ming Lei ha scritto:
Hi Stefan,
I found VM block I/O thoughput is decreased by more than 40%
on my laptop, and looks much worsen in my server environment,
and it is caused by
On 23 June 2014 16:55, Richard Henderson wrote:
> It's also
>
> Reviewed-by: Richard Henderson
Thanks; applied to master.
-- PMM
Hi Cam,
FYI, David did implement a new server.
http://lists.nongnu.org/archive/html/qemu-devel/2014-06/msg04978.html
which is easier to maintain.
Please, could you review his patch? He'll be back from holiday within 1
week.
Best regards,
Vincent
PS: thanks for your comments
Il 26/06/2014 17:37, Markus Armbruster ha scritto:
> Paolo Bonzini writes:
>
>> From: Wenchao Xia
>>
>> Signed-off-by: Wenchao Xia
>> Signed-off-by: Paolo Bonzini
>
> This broke tests/qemu-iotests/041. Apparently, the BLOCK_JOB_ERROR
> event changed from
>
> {'timestamp': {'seconds': 14
On Thu, Jun 26, 2014 at 03:30:11PM +0200, Paolo Bonzini wrote:
> Il 26/06/2014 13:36, Michael S. Tsirkin ha scritto:
> >>It should be this way in real hardware too
> >But it isn't.
>
> That's why I mentioned that this hack should become architecturally
> specified (since it can work on real hardwa
Il 26/06/2014 16:34, Marc Marí ha scritto:
+static void qvirtio_pci_foreach(uint16_t device_type,
+void (*func)(QVirtioDevice *d, void *data), void *data)
+{
+QVirtioPCIForeachData d = { .func = func,
+.device_type = device_type,
+
Paolo Bonzini writes:
> From: Wenchao Xia
>
> Signed-off-by: Wenchao Xia
> Signed-off-by: Paolo Bonzini
This broke tests/qemu-iotests/041. Apparently, the BLOCK_JOB_ERROR
event changed from
{'timestamp': {'seconds': 1403796871, 'microseconds': 446502},
'data': {'device': 'drive0',
On Thu, Jun 26, 2014 at 11:29 PM, Paolo Bonzini wrote:
> Il 26/06/2014 17:14, Ming Lei ha scritto:
>
>> Hi Stefan,
>>
>> I found VM block I/O thoughput is decreased by more than 40%
>> on my laptop, and looks much worsen in my server environment,
>> and it is caused by your commit 580b6b2aa2:
>>
>
Add back in the support for 64-bit PPC MacOSX hosts that was
broken in the recent merge of the 32-bit and 64-bit TCG backends.
Signed-off-by: Peter Maydell
---
As per subject, this is totally untested since I don't have any
PPC MacOSX hosts; numbers based on the documentation at
https://developer
Il 26/06/2014 17:27, Marc Marí ha scritto:
If these functions are just Virtio PCI specific, it makes sense to take
them out. If they are common to other transports, in my opinion is
better to leave them there. Of course, a good solution has to be found
to just having a global bus variable.
It is
Il 26/06/2014 17:11, Frederic Konrad ha scritto:
Are you talking of this patch on the list:
http://lists.gnu.org/archive/html/qemu-devel/2014-06/msg03039.html ?
It seems to includes the "align" options too. Is that possible to split
it up?
Sure, you can split it up and when the original auth
On 06/26/2014 09:14 AM, Christian Borntraeger wrote:
> On 25/06/14 16:27, Matthew Rosato wrote:
>> Add memory information to read SCP info and add handlers for
>> Read Storage Element Information, Attach Storage Element,
>> Assign Storage and Unassign Storage.
>>
>> Signed-off-by: Matthew Rosato
>
Il 26/06/2014 17:14, Ming Lei ha scritto:
Hi Stefan,
I found VM block I/O thoughput is decreased by more than 40%
on my laptop, and looks much worsen in my server environment,
and it is caused by your commit 580b6b2aa2:
dataplane: use the QEMU block layer for I/O
I run fio with below
1 - 100 of 277 matches
Mail list logo
