On 27 March 2017 at 21:11, Stefan Weil wrote:
> This check had several problems which are fixed here:
>
> * Calling "configure --help" was no longer possible on Cygwin.
> Fix this by introducing a third state for supported_os and
> by moving the error handling code.
> Move the error handlin
From: Tejaswini Poluri
Start QEMU with
"qemu-system-x86_64 -nographic -M isapc -serial none-monitor stdio"
and enter "info lapic" at the monitor prompt ⇒
Segmentation fault
Signed-off-by: Tejaswini Poluri
---
target/i386/helper.c | 4
1 file changed, 4 insertions(+)
diff --git a/target/i
From: Vinzenz Feenstra
A command that will list all currenctly logged in users having running
processes.
Examples:
virsh # qemu-agent-command F25 '{ "execute": "guest-get-users" }'
{"return":[{"user":"root"}]}
virsh # qemu-agent-command Win2k12r2 '{ "execute": "guest-get-users" }'
{"return":[{
On 27/03/17 21:19, Stefan Weil wrote:
> Am 27.03.2017 um 07:48 schrieb Mark Cave-Ayland:
>> Right, I see cygwin has a much newer version of glib available which
>> explains how the builds are produced.
>>
>> What was the exact issue with global symbols which prevents the
>> pre-built Win64 binarie
Jeff Cody writes:
> On Mon, Mar 27, 2017 at 03:26:26PM +0200, Markus Armbruster wrote:
>> qemu_rbd_open() neglects to check pool and image are present.
>> Reproducer:
>>
>> $ qemu-system-x86_64 -nodefaults -drive if=none,driver=rbd,pool=p
>> Segmentation fault (core dumped)
>
> This repr
Today, the ICPState array of the sPAPR machine is indexed with
'cpu_index' of the CPUState. This numbering of CPUs is internal to
QEMU and the guest only knows about what is exposed in the device
tree, that is the 'cpu_dt_id'. This is why sPAPR uses the helper
xics_get_cpu_index_by_dt_id() to do th
Hello,
Here is a series adding support for the interrupt controller as found
on a POWER8 system. POWER9 uses a different interrupt controller
called XIVE, still to be worked on.
The initial patches are more cleanups of the XICS layer which move the
IRQ 'server' number mapping under the machine ha
Some controllers (ICP, PSI) have a base register address which is
calculated using the chip id.
Signed-off-by: Cédric Le Goater
Reviewed-by: David Gibson
---
include/hw/ppc/pnv.h | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/include/hw/ppc/pnv.h b/include/hw/p
This is the second step to abstract the IRQ 'server' number of the
XICS layer. Now that the prereq cleanups have been done in the
previous patch, we can move down the 'cpu_dt_id' to 'cpu_index'
mapping in the sPAPR machine handler.
Signed-off-by: Cédric Le Goater
Reviewed-by: David Gibson
---
h
It will be used by derived classes in PowerNV for customization.
Signed-off-by: Cédric Le Goater
Reviewed-by: David Gibson
---
hw/intc/xics.c| 5 +
include/hw/ppc/xics.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/hw/intc/xics.c b/hw/intc/xics.c
index bb485cc5b078..bf0fa22
This provides a new ICPState object for the PowerNV machine (POWER8).
Access to the Interrupt Management area is done though a memory
region. It contains the registers of the Interrupt Control Presenters
of each thread which are used to accept, return, forward interrupts in
the system.
Signed-off-
On Mon, 27 Mar 2017 21:20:56 +0300
"Michael S. Tsirkin" wrote:
> On Mon, Mar 27, 2017 at 07:46:03PM +0200, Greg Kurz wrote:
> > This introduces an Error object based implementation of virtio_error(). It
> > allows to implement virtio_error() wrappers in device-specific code.
> >
> > Signed-off-b
Like this is done for the sPAPR machine, we use a simple array under
the PowerNV machine to store the Interrupt Control Presenters (ICP)
objects, one for each vCPU. This array is indexed by 'cpu_index' of
the CPUState but the users will provide a core PIR number. The mapping
is done in the icp_get(
This provides to a PowerNV chip (POWER8) access to the Interrupt
Management area, which contains the registers of the Interrupt Control
Presenters of each thread. These are used to accept, return, forward
interrupts in the system.
This area is modeled with a per-chip container memory region holdin
This assigns the ICPState object to the CPU using the PIR number for
lookups before calling the XICS layer to finish the job.
Signed-off-by: Cédric Le Goater
Reviewed-by: David Gibson
---
hw/ppc/pnv.c | 2 ++
hw/ppc/pnv_core.c | 20
2 files changed, 18 insertions(+),
Jeff Cody writes:
> On Mon, Mar 27, 2017 at 08:58:28PM +0200, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>> > Max Reitz writes:
>> >
>> >> On 27.03.2017 18:10, Max Reitz wrote:
>> >>> On 27.03.2017 15:26, Markus Armbruster wrote:
>> qemu_rbd_open() neglects to check pool and
On 27/03/2017 18:50, Stefan Hajnoczi wrote:
> The IscsiAIOCB.qiov field has been unused since commit
> 063c3378a9e3c25cc0afac3c72e4823d0621e352 ("block/iscsi: introduce
> bdrv_co_{readv, writev, flush_to_disk}") back in 2013.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> block/iscsi.c | 1 -
> 1
On 27/03/2017 20:21, Xu, Anthony wrote:
>>> ./trace.o, ./qapi/trace.o and ./util/trace.o are added into
>>> libqemuutil.a to avoid recursive dependencies between
>>> libqemuutil.a and libqemutrace.a.
>> Why would libqemutrace.a depend on libqemuutil.a?
> Each trace.c calls trace_event_register_g
Jeff Cody writes:
> On Mon, Mar 27, 2017 at 10:32:40PM -0400, Jeff Cody wrote:
>> On Mon, Mar 27, 2017 at 03:26:33PM +0200, Markus Armbruster wrote:
>> > This reverts a part of commit 8a47e8e. We're having second thoughts
>> > on the QAPI schema (and thus the external interface), and haven't
>>
On 27/03/2017 22:11, Stefan Weil wrote:
> * Support cross compilation with the most common cross prefixes
> for Mingw-w64. Other cross builds are still broken!
Can you explain how it's broken? Why does check_define not work at this
point, for cross builds?
"../configure --cross-prefix=x86_64
On 28/03/2017 09:19, Tejaswini wrote:
> From: Tejaswini Poluri
>
> Start QEMU with
> "qemu-system-x86_64 -nographic -M isapc -serial none-monitor stdio"
> and enter "info lapic" at the monitor prompt ⇒
> Segmentation fault
>
> Signed-off-by: Tejaswini Poluri
> ---
> target/i386/helper.c | 4
On 28/03/2017 03:08, Herongguang (Stephen) wrote:
> From 8f5b9d2c2944ea7cd8149e9d3b4088f487217d20 Mon Sep 17 00:00:00 2001
> From: herongguang
> Date: Mon, 27 Mar 2017 15:08:59 +0800
> Subject: [PATCH] KVM: pci-assign: do not map smm memory slot pages in vt-d
> page table
>
> or VM memory are
On Mon, 27 Mar 2017 21:20:56 +0300
"Michael S. Tsirkin" wrote:
> On Mon, Mar 27, 2017 at 07:46:03PM +0200, Greg Kurz wrote:
> > This introduces an Error object based implementation of virtio_error(). It
> > allows to implement virtio_error() wrappers in device-specific code.
> >
> > Signed-off-b
Jeff Cody writes:
> On Mon, Mar 27, 2017 at 03:26:27PM +0200, Markus Armbruster wrote:
>> We laboriously enforce parameter values are between one and some
>
> s/are/that are/
>
> or maybe just s/are//
What about:
We laboriously enforce that parameter values are between one and some
>> arbit
If a page size used by QEMU is not enabled in the PHB IOMMU page mask,
in-kernel acceleration of TCE handling won't be enabled and performance
might be slower than expected.
This prints a warning if system page size is not enabled. This should
print a warning if huge pages are enabled but sphb.pgs
On Wed, 22 Mar 2017 10:34:22 +0800
Dong Jia Shi wrote:
> * Alex Williamson [2017-03-21 12:47:16 -0600]:
>
> [...]
>
> > > +vfio-ccw I/O region
> > > +---
> > > +
> > > +An I/O region is used to accept channel program request from user
> > > +space and store I/O interrupt result
* Thomas Huth (th...@redhat.com) wrote:
> On 27.03.2017 16:24, Dr. David Alan Gilbert wrote:
> > * Thomas Huth (th...@redhat.com) wrote:
> >> Some tests need to run single tests for every available machine of the
> >> current QEMU binary. To avoid code duplication, let's extract this
> >> code that
On Fri, 17 Mar 2017 04:17:27 +0100
Dong Jia Shi wrote:
> Dong Jia Shi (16):
> s390: cio: introduce cio_cancel_halt_clear
> s390: cio: export more interfaces
> vfio: ccw: define device_api strings
> vfio: ccw: basic implementation for vfio_ccw driver
> vfio: ccw: introduce channel progra
Eric Blake writes:
> On 03/27/2017 08:26 AM, Markus Armbruster wrote:
>> This reverts half of commit 0a55679. We're having second thoughts on
>> the QAPI schema (and thus the external interface), and haven't reached
>> consensus, yet. Issues include:
>>
>
>> Let's avoid painting ourselves into
On Tue, 28 Mar 2017 10:14:09 +0200
Greg Kurz wrote:
> On Mon, 27 Mar 2017 21:20:56 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Mar 27, 2017 at 07:46:03PM +0200, Greg Kurz wrote:
> > > This introduces an Error object based implementation of virtio_error(). It
> > > allows to implement virt
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 27 March 2017 18:46
> To: Paul Durrant
> Cc: 'Stefano Stabellini' ; qemu-devel@nongnu.org;
> xen-de...@lists.xenproject.org; Anthony Perard
>
> Subject: RE: [PATCH] xen: additionally restrict xenforeig
I missed the fact that when an exclusive work item runs it drops the
BQL to ensure all no vCPUs are stuck waiting for it, hence causing a
deadlock. However the actual helper needs to take the BQL especially
as we'll be messing with device emulation bits during the update which
all assume BQL is hel
When "tcg: enable thread-per-vCPU" (commit 3725794) was merged the
lifetime of current_cpu was changed. Previously a broken linux-user
call might abort() which can eventually escalate into a SIGSEGV which
would then crash qemu as it attempted to deref a NULL current_cpu.
After commit 3725794 it wou
A previous commit (3d4d16f4) added support for audio record/playback.
However this breaks the logfile ABI due to the re-ordering of the
ReplayEvents enum. The REPLAY_VERSION check is meant to prevent you
from using old log files in newer QEMUs but this is currently broken.
Signed-off-by: Alex Benn
Hi,
Here is the current batch of fixes for MTTCG regressions for the next
release candidate. I've dropped the speculative atomic cputlb patch
and included 2 fixes to the console code. The first fixes the taking
of the BQL (which I missed) and the second uses the exclusive
mechanism directly in the
The previous commit (8bb93c6f99) using async_safe_run_on_cpu() doesn't
work on graphics sub-system which restrict which threads can do GUI
updates. Rather the special casing MacOS we just directly call the
helper and move all the exclusive handling into do_dafe_dpy_refresh().
The unfortunate bounc
On 03/28/2017 10:20 AM, Cornelia Huck wrote:
> On Fri, 17 Mar 2017 04:17:27 +0100
> Dong Jia Shi wrote:
>
>> Dong Jia Shi (16):
>> s390: cio: introduce cio_cancel_halt_clear
>> s390: cio: export more interfaces
>> vfio: ccw: define device_api strings
>> vfio: ccw: basic implementation for
From: Pranith Kumar
Signed-off-by: Pranith Kumar
Signed-off-by: Alex Bennée
---
cpus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpus.c b/cpus.c
index 167d9615e1..68fdbc40b9 100644
--- a/cpus.c
+++ b/cpus.c
@@ -209,7 +209,7 @@ void qemu_tcg_configure(QemuOpts *opts, E
The introduction of stricter mmap_lock checking in translate-all broke
the BSD user build. The working mmap_lock functions were hidden behind
CONFIG_USE_NPTL which is never defined. This patch brings them inline
with linux-user.
Despite the disapearence of the comment "We aren't threadsafe to star
On Tue, Mar 28, 2017 at 3:15 AM, Liu, Changpeng wrote:
>> -Original Message-
>> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
>> Sent: Tuesday, March 28, 2017 4:20 AM
>> To: Liu, Changpeng
>> Cc: virtio-...@lists.oasis-open.org;
>> virtualizat...@lists.linux-foundation.org; linux-
>>
From: Peter Maydell
For a packed struct like 'P9Hdr' the fields within it may not be
aligned as much as the natural alignment for their types. This means
it is not valid to pass the address of such a field to a function
like le32_to_cpus() which operate on uint32_t* and assume alignment.
Doing t
The following changes since commit eb06c9e2d3c8f026a206e8402b0ffa201060ec8e:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging
(2017-03-27 17:34:50 +0100)
are available in the git repository at:
https://github.com/gkurz/qemu.git tags/for-upstream
for you to fetc
From: Li Qiang
The v9fs_create() and v9fs_lcreate() functions are used to create a file
on the backend and to associate it to a fid. The fid shouldn't be already
in-use, otherwise both functions may silently leak a file descriptor or
allocated memory. The current code doesn't check that.
This pa
On 27 March 2017 at 17:16, Paolo Bonzini wrote:
> The following changes since commit 08329701199449bde497570dcfdb9c86062baf20:
>
> qom: Fix regression with 'qom-type' (2017-03-23 17:59:40 +)
>
> are available in the git repository at:
>
> git://github.com/bonzini/qemu.git tags/for-upstream
* Cornelia Huck [2017-03-28 10:16:23 +0200]:
[...]
> >
> > @Conny, please correct me if my understanding is not right.
>
> No, it's fine.
Thanks!
>
> FWIW:
> https://virtualpenguins.blogspot.com/2017/02/channel-io-demystified.html
>
> (I plan to write more in the future.)
That's a very good
The conversion from QDict to QemuOpts is pointless. Simply get the
stuff straight from the QDict.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
Reviewed-by: Kevin Wolf
---
block/rbd.c | 20 +---
1 file changed, 5 insertions(+), 15 deletions(-)
diff --git a/block/rb
We laboriously enforce that parameter values are between one and some
arbitrary limit in length. Only RBD_MAX_IMAGE_NAME_SIZE comes from
librbd.h, and I'm not sure it applies. Where the other limits come
from is unclear.
Drop the length checking. The limits librbd actually imposes must be
check
The way we communicate extra key-value pairs from
qemu_rbd_parse_filename() to qemu_rbd_open() exposes option parameter
"keyvalue-pairs" on the command line. It's not wanted there. Hack:
rename the parameter to "=keyvalue-pairs" to make it inaccessible.
Signed-off-by: Markus Armbruster
Reviewed
This code in qemu_rbd_parse_filename()
found_str = qemu_rbd_next_tok(p, '\0', &p);
p = found_str;
has no effect. Drop it, and simplify qemu_rbd_next_tok().
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
Reviewed-by: Max Reitz
Reviewed-by: Jeff Cody
---
block/rbd.c | 24 ++
qemu_rbd_open() takes option parameters as a flattened QDict, with
keys of the form server.%d.host, server.%d.port, where %d counts up
from zero.
qemu_rbd_array_opts() extracts these values as follows. First, it
calls qdict_array_entries() to find the list's length. For each list
element, it for
I really, really want to correct a few issues in external interfaces
before while I can. Bonus: several minor bug fixes.
Thanks to Jeff Cody for testing this series.
v4:
* PATCH 01,04-06 unchanged
* PATCH 02 commit message fixed up [Jeff]
* PATCH 03 commit message tweak [Jeff]
* PATCH 07 fixed t
runtime_opts is used for three different purposes:
* qemu_rbd_open() uses it to accept options it recognizes, such as
"pool" and "image". Other .bdrv_open() methods do it similarly.
* qemu_rbd_open() accepts additional list-valued options
auth-supported and server, with the help of qemu_rbd_
We use InetSocketAddress in the QAPI schema. However, the code
doesn't use inet_connect_saddr(), but formats "host" and "port" into a
configuration string for rados_conf_set(). Thus, members "numeric",
"to", "ipv4" and "ipv6" are silently ignored. Not nice. Example:
-blockdev
rbd,node-nam
qemu_rbd_open() neglects to check pool and image are present. Missing
image is caught by rbd_open(), but missing pool crashes. Reproducer:
$ qemu-system-x86_64 -nodefaults -drive driver=rbd,id=rbd,image=i,...
terminate called after throwing an instance of 'std::logic_error'
what():
This reverts a part of commit 8a47e8e. We're having second thoughts
on the QAPI schema (and thus the external interface), and haven't
reached consensus, yet. Issues include:
* BlockdevOptionsRbd member @password-secret isn't actually a
password, it's a key generated by Ceph.
* We're not sure
This reverts half of commit 0a55679. We're having second thoughts on
the QAPI schema (and thus the external interface), and haven't reached
consensus, yet. Issues include:
* The implementation uses deprecated rados_conf_set() key
"auth_supported". No biggie.
* The implementation makes -drive
At the moment VFIO PCI device initialization works as follows:
vfio_realize
vfio_get_group
vfio_connect_container
register memory listeners (1)
update QEMU groups lists
vfio_kvm_device_add_group
Then (example f
This is my current working tree to support kernel's
"powerpc/kvm/vfio: Enable in-kernel acceleration".
Please comment. Thanks.
Alexey Kardashevskiy (3):
memory: Add get_fd() hook for IOMMU MR
vfio-pci: Reorder group-to-container attaching
vfio: Enable in-kernel acceleration via VFIO KVM d
Signed-off-by: Alexey Kardashevskiy
---
include/exec/memory.h | 2 ++
hw/ppc/spapr_iommu.c | 8
2 files changed, 10 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index e39256ad03..925c10b35b 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -1
This enables in-kernel acceleration of TCE update requests via
VFIO KVM device.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/vfio/vfio-common.h | 1 +
target/ppc/kvm_ppc.h | 6 ++
hw/ppc/spapr_iommu.c | 4
hw/vfio/common.c | 13 +
hw/v
On 28/03/2017 10:36, Alex Bennée wrote:
>
> Here is the current batch of fixes for MTTCG regressions for the next
> release candidate. I've dropped the speculative atomic cputlb patch
> and included 2 fixes to the console code. The first fixes the taking
> of the BQL (which I missed) and the sec
Hi
On Tue, Mar 28, 2017 at 7:15 AM Vinzenz Feenstra
wrote:
> Eric, what you think of this below way, instead?
>
> >
> > OK So how about something like this:
> >
> > {‘struct’: ‘GuestWindowsVersionInfo’,
> > ‘data’: {
> > ‘version’: ‘str’,
> > ‘name’: ‘str’,
> > } }
> >
> > {‘struc
when migration with quick speed, mig_save_device_bulk invoke
bdrv_is_allocated too frequently, and cause vnc reponse slowly.
this patch limit the time used for bdrv_is_allocated.
Signed-off-by: Lidong Chen
---
migration/block.c | 39 +++
1 file changed, 31 ins
when migrate the vm with quick speed, i find vnc response slowly.
the bug can be reproduce by this command:
virsh migrate-setspeed 165cf436-312f-47e7-90f2-f8aa63f34893 900
virsh migrate --live 165cf436-312f-47e7-90f2-f8aa63f34893
--copy-storage-inc qemu+ssh://10.59.163.38/system
and --copy-storag
On Tue, 28 Mar 2017 10:24:21 +0200
Cornelia Huck wrote:
> On Tue, 28 Mar 2017 10:14:09 +0200
> Greg Kurz wrote:
>
> > On Mon, 27 Mar 2017 21:20:56 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Mar 27, 2017 at 07:46:03PM +0200, Greg Kurz wrote:
> > > > This introduces an Error ob
Hi
On Tue, Mar 28, 2017 at 9:22 AM Vinzenz 'evilissimo' Feenstra <
vfeen...@redhat.com> wrote:
> From: Vinzenz Feenstra
>
> A command that will list all currenctly logged in users having running
> processes.
>
> Examples:
>
> virsh # qemu-agent-command F25 '{ "execute": "guest-get-users" }'
> {"
Passing the address of a field in a packed struct to a function
that expects a pointer to normally aligned data will result in
a SEGBUS on architectures like SPARC that have strict alignment
requirements.
Pass addresses of local variables rather than addresses of packed
structure fields to glib fu
On 28 March 2017 at 09:46, Greg Kurz wrote:
> The following changes since commit eb06c9e2d3c8f026a206e8402b0ffa201060ec8e:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
> staging (2017-03-27 17:34:50 +0100)
>
> are available in the git repository at:
>
> https://gi
On Sat, Mar 25, 2017 at 04:56:41PM +0300, Joannah Nanjekye wrote:
> From: nanjekyejoannah
>
> The patch provides python 3 support for one of the scripts in scripts/qmp
> that is to say qmp.py. This is not a port to python 3 but rather the patch
> ensures that the script runs fine for both pyth
Hi,
> Gerd,
>
> Do you want to take the console patches via your tree or have me
> include it in a pull request?
Just include them in your pull req.
Reviewed-by: Gerd Hoffmann
cheers,
Gerd
Lidong Chen wrote:
> when migration with quick speed, mig_save_device_bulk invoke
> bdrv_is_allocated too frequently, and cause vnc reponse slowly.
> this patch limit the time used for bdrv_is_allocated.
>
> Signed-off-by: Lidong Chen
> ---
> migration/block.c | 39 ++
On Wed, Mar 22, 2017 at 02:32:45PM +0100, Igor Mammedov wrote:
> and remove corresponding part in numa.c that uses
> node_cpu bitmaps.
>
> Signed-off-by: Igor Mammedov
Reviewed-by: David Gibson
> ---
> It's one more less user of node_cpu bitmpas, following
> commit will remove the last user al
On Wed, Mar 22, 2017 at 02:32:46PM +0100, Igor Mammedov wrote:
> Postfactum "CPU(s) present in multiple NUMA nodes" check
> was the last user of node_cpu bitmaps, but it's not need
> as machine_set_cpu_numa_node() does the similar check at
> the time mapping is set for cpus (i.e. when -numa cpus=
>
On Wed, Mar 22, 2017 at 02:32:47PM +0100, Igor Mammedov wrote:
> legacy cpu to node mapping is using cpu index values to map
> VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
> option. However cpu index is internal concept and QEMU users
> have to guess /reimplement qemu's logic/ to m
On Mon, Mar 27, 2017 at 11:09:23PM -0400, Pranith Kumar wrote:
> On Mon, Mar 27, 2017 at 11:03 PM, Pranith Kumar wrote:
>
> >
> > If you think the project makes sense, I will add it to the GSoC wiki
> > so that others can also apply for it. Please let me know if you are
> > interested in mentorin
The following changes since commit eb06c9e2d3c8f026a206e8402b0ffa201060ec8e:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging
(2017-03-27 17:34:50 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/block-pull-request
for you
On Mon, Mar 27, 2017 at 05:38:08PM +0300, Denis V. Lunev wrote:
> Parallels driver should not call bdrv_truncate if the image was opened
> in the read-only mode. Without the patch
> qemu-img check harddisk.hds
> asserts with
> bdrv_truncate: Assertion `child->perm & BLK_PERM_RESIZE' failed.
From: "Denis V. Lunev"
Parallels driver should not call bdrv_truncate if the image was opened
in the read-only mode. Without the patch
qemu-img check harddisk.hds
asserts with
bdrv_truncate: Assertion `child->perm & BLK_PERM_RESIZE' failed.
Parameters used on the write path are not neede
On Mon, Mar 27, 2017 at 02:17:18PM +0100, Stefan Hajnoczi wrote:
> Commit 0ab8ed18a6fe98bfc82705b0f041fbf2a8ca5b60 ("trace: switch to
> modular code generation for sub-directories") forgot to convert "tcg"
> trace events to the modular code generation approach where each
> sub-directory has its own
On Tue, 28 Mar 2017 11:34:15 +0200
Greg Kurz wrote:
> On Tue, 28 Mar 2017 10:24:21 +0200
> Cornelia Huck wrote:
>
> > On Tue, 28 Mar 2017 10:14:09 +0200
> > Greg Kurz wrote:
> >
> > > On Mon, 27 Mar 2017 21:20:56 +0300
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Mon, Mar 27, 2017 a
On 03/27/2017 07:34 PM, Peter Maydell wrote:
> That all makes sense in isolation, but shouldn't something have
> at least warned that "&h.size" isn't actually a uint32_t* in
> the sense of being something you can validly pass to a
> function that takes a uint32_t* ?
It turns out that clang actuall
On 28 March 2017 at 11:19, John Paul Adrian Glaubitz
wrote:
> On 03/27/2017 07:34 PM, Peter Maydell wrote:
>> That all makes sense in isolation, but shouldn't something have
>> at least warned that "&h.size" isn't actually a uint32_t* in
>> the sense of being something you can validly pass to a
>>
On Mon, 27 Mar 2017 11:48:14 -0300
Eduardo Habkost wrote:
> Instead of passing a pointer to the feature property getter and
> setter functions, pass a FeatureWord enum so they can perform
> other actions related to the feature flag.
>
> This will be used to add a new "user_features" field to kee
On Mon, 27 Mar 2017 11:48:15 -0300
Eduardo Habkost wrote:
> The existing code for "host" and "max" CPU models overrides every
> single feature in the CPU object at realize time, even the ones
> that were explicitly enabled or disabled by the user using
> "feat=on" or "feat=off", while features se
On 28 March 2017 at 11:07, Stefan Hajnoczi wrote:
> The following changes since commit eb06c9e2d3c8f026a206e8402b0ffa201060ec8e:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
> staging (2017-03-27 17:34:50 +0100)
>
> are available in the git repository at:
>
> git:
Yes, I can still reproduce this with 2.8.0, and it gives exactly the
same output.
** Changed in: qemu
Status: Expired => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1258626
Title:
Cur
Igor Mammedov wrote:
> On Thu, 23 Mar 2017 21:50:24 +0100
> Juan Quintela wrote:
>
>> Until we have reviewed what can/can't be hotplug during migration,
>> disable it. We can enable it later for the things that we know that
>> work. For instance, memory hotplug during postcopy don't work
>> cur
Eric Blake wrote:
> On 03/23/2017 03:44 PM, Juan Quintela wrote:
>> So all places are consisten on the nambing of a block name parameter.
>
> s/consisten/consistent/
> s/nambing/naming/
Done, thanks.
On Tue, 28 Mar 2017 15:19:20 +1100
David Gibson wrote:
> On Wed, Mar 22, 2017 at 02:32:30PM +0100, Igor Mammedov wrote:
> > Originally CPU threads were by default assigned in
> > round-robin fashion. However it was causing issues in
> > guest since CPU threads from the same socket/core could
> >
* Kevin Wolf (kw...@redhat.com) wrote:
> Am 25.02.2017 um 20:31 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > After migration all drives are inactive and savevm will fail with
> >
> > qemu-kvm: block/io.c:1406: bdrv_co_do_pwritev:
> >Assertion `!(bs->open_flags & 0x0800)' failed.
> >
> >
Peter Xu wrote:
> On Thu, Mar 23, 2017 at 09:44:58PM +0100, Juan Quintela wrote:
>> Signed-off-by: Juan Quintela
>> Reviewed-by: Dr. David Alan Gilbert
>
> Reviewed-by: Peter Xu
>
> (I see that we have MigrationStats.dirty_pages_rate which looks
> similar to this one. Maybe one day we can merg
Thanks to John Paul Adrian Glaubitz
and the Debian Project, we now have access to a SPARC Linux
system we can use for build testing. Move SPARC back into
the "supported" list.
Signed-off-by: Peter Maydell
---
We should also at least apply the TCG fixes:
http://patchwork.ozlabs.org/patch/743890/
Peter Xu wrote:
> On Thu, Mar 23, 2017 at 09:44:59PM +0100, Juan Quintela wrote:
>> Signed-off-by: Juan Quintela
>> Reviewed-by: Dr. David Alan Gilbert
>> ---
>> migration/ram.c | 20 +++-
>> 1 file changed, 11 insertions(+), 9 deletions(-)
>>
>> diff --git a/migration/ram.c b/
Am 28.03.2017 um 12:55 hat Dr. David Alan Gilbert geschrieben:
> * Kevin Wolf (kw...@redhat.com) wrote:
> > Am 25.02.2017 um 20:31 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > > After migration all drives are inactive and savevm will fail with
> > >
> > > qemu-kvm: block/io.c:1406: bdrv_co_do
On Tue, 28 Mar 2017 16:16:02 +1100
David Gibson wrote:
> On Wed, Mar 22, 2017 at 02:32:47PM +0100, Igor Mammedov wrote:
> > legacy cpu to node mapping is using cpu index values to map
> > VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
> > option. However cpu index is internal conce
I missed the fact that when an exclusive work item runs it drops the
BQL to ensure all no vCPUs are stuck waiting for it, hence causing a
deadlock. However the actual helper needs to take the BQL especially
as we'll be messing with device emulation bits during the update which
all assume BQL is hel
The introduction of stricter mmap_lock checking in translate-all broke
the BSD user build. The working mmap_lock functions were hidden behind
CONFIG_USE_NPTL which is never defined. This patch brings them inline
with linux-user.
Despite the disapearence of the comment "We aren't threadsafe to star
When "tcg: enable thread-per-vCPU" (commit 3725794) was merged the
lifetime of current_cpu was changed. Previously a broken linux-user
call might abort() which can eventually escalate into a SIGSEGV which
would then crash qemu as it attempted to deref a NULL current_cpu.
After commit 3725794 it wou
The following changes since commit ea2afcf5b6727a577cf561fd8fe0d8c397ecc927:
Merge remote-tracking branch 'remotes/stefanha/tags/tracing-pull-request'
into staging (2017-03-24 14:14:18 +)
are available in the git repository at:
https://github.com/stsquad/qemu.git tags/pull-mttcg-fixups-
A previous commit (3d4d16f4) added support for audio record/playback.
However this breaks the logfile ABI due to the re-ordering of the
ReplayEvents enum. The REPLAY_VERSION check is meant to prevent you
from using old log files in newer QEMUs but this is currently broken.
Signed-off-by: Alex Benn
1 - 100 of 337 matches
Mail list logo
