> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> On Tue, Jun 05, 2018 at 02:56:29PM +0300, Pavel Dovgalyuk wrote:
> > > From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> > >
> > > This series doesn't seem to add anything to Documentation/ that
> > > describes the API we make available
This makes test-block work.
Signed-off-by: Fam Zheng
---
tests/docker/dockerfiles/centos7.docker | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/docker/dockerfiles/centos7.docker
b/tests/docker/dockerfiles/centos7.docker
index 575de29a0a..83462b7205 100644
---
On 10.07.2018 08:50, Peter Maydell wrote:
> On 9 July 2018 at 23:03, Thomas Huth wrote:
>> On 09.07.2018 23:42, Peter Maydell wrote:
>>> On 9 July 2018 at 22:03, Thomas Huth wrote:
When trying to "device_add bcm2837" on a machine that is not suitable for
this device, you can quickly
This step was left behind my mistake. As suggested by the echoed text,
the intention was to test two devices with the same image, with
different options. The behavior should be the same as two QEMU
processes. Complete it.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/153 | 2 ++
On Wed, 11 Jul 2018 08:53:20 +0200
Thomas Huth wrote:
> On 10.07.2018 17:24, Peter Krempa wrote:
> > On Tue, Jul 10, 2018 at 17:01:22 +0200, Cornelia Huck wrote:
> >> So, from that I gather that a hard failure would be the easiest for
> >> libvirt to detect (and everything else would become
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU and Windows? Or could we close this
ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Looking through old bug tickets... can you still reproduce this bug
with the latest version of QEMU? At least for vvfat, the warning message
does not seem to occur anymore.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of
On 10.07.2018 17:24, Peter Krempa wrote:
> On Tue, Jul 10, 2018 at 17:01:22 +0200, Cornelia Huck wrote:
>> On Tue, 10 Jul 2018 16:39:31 +0200
>> Peter Krempa wrote:
>>> On Tue, Jul 10, 2018 at 16:22:08 +0200, Cornelia Huck wrote:
On Tue, 10 Jul 2018 07:59:15 +0200
Markus Armbruster
On Tue, Jul 10, 2018 at 05:14:53PM +1000, Alexey Kardashevskiy wrote:
> On Tue, 10 Jul 2018 16:42:48 +1000
> David Gibson wrote:
>
> > On Tue, Jul 10, 2018 at 12:22:44PM +1000, Alexey Kardashevskiy wrote:
> > > On Mon, 2 Jul 2018 16:26:44 +1000
> > > Alexey Kardashevskiy wrote:
> > >
> > >
197 is one example where _make_test_img is used twice without stopping
the NBD server in between. An error will occur like this:
@@ -26,9 +26,13 @@
=== Partial final cluster ===
+qemu-img: TEST_DIR/t.IMGFMT: Failed to get "resize" lock
+Is another process using the image?
Looking through old bug tickets... which version of QEMU did you use
here? Can you still reproduce this issue with the latest version of
QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a
On Tue, 07/03 12:35, Philippe Mathieu-Daudé wrote:
> This silents the following warning:
>
> Cloning into './debootstrap.git'...
> warning: redirecting to
> https://salsa.debian.org/installer-team/debootstrap.git/
>
> See https://lists.debian.org/debian-devel-announce/2018/01/msg4.html
On 10/07/18 18:03, Dave Martin wrote:
On Tue, Jul 10, 2018 at 05:38:39PM +0100, Suzuki K Poulose wrote:
On 09/07/18 14:37, Dave Martin wrote:
On Mon, Jul 09, 2018 at 01:29:42PM +0100, Marc Zyngier wrote:
On 09/07/18 12:23, Dave Martin wrote:
[...]
Wedging arguments into a few bits in the
On Wed, 11 Jul 2018 11:28:02 +1000
David Gibson wrote:
> On Tue, Jul 10, 2018 at 05:55:14PM +0200, Greg Kurz wrote:
> > Recent cleanup in commit a028dd423ee6 causes QEMU to crash during CPU
> > hotplug:
> >
> > (qemu) device_add host-spapr-cpu-core,id=core1,core-id=1
> > Segmentation fault
Am 11.07.2018 um 08:40 hat Fam Zheng geschrieben:
> 197 is one example where _make_test_img is used twice without stopping
> the NBD server in between. An error will occur like this:
>
> @@ -26,9 +26,13 @@
>
> === Partial final cluster ===
>
> +qemu-img: TEST_DIR/t.IMGFMT: Failed
Am 11.07.2018 um 03:22 hat Fam Zheng geschrieben:
> Explicitly enabling zero detection or compression suppresses copy
> offloading during convert. Document it.
>
> Suggested-by: Kevin Wolf
> Signed-off-by: Fam Zheng
Thanks, applied to the block branch.
Kevin
Am 10.07.2018 um 19:00 hat John Snow geschrieben:
> Tighten which types of files we'll allow you to specify for the various
> file drivers (file, host_device, host_cdrom).
Thanks, applied to the block branch.
Kevin
To reach gdb_set_stop_cpu() with gdbserver_state == NULL, you previously
> entered gdb_vm_state_change() with and use CPUState *cpu =
> gdbserver_state->c_cpu = NULL deref, which shouldn't happen.
> Also in gdb_set_stop_cpu() you finally call cpu_single_step(cpu=crap)
> which then deref
On Thu, Jun 28, 2018 at 05:33:58PM +0800, Xiao Guangrong wrote:
>
>
> On 06/19/2018 03:36 PM, Peter Xu wrote:
> > On Mon, Jun 04, 2018 at 05:55:15PM +0800, guangrong.x...@gmail.com wrote:
> > > From: Xiao Guangrong
> > >
> > > Try to hold src_page_req_mutex only if the queue is not
> > > empty
Gentle ping. CCing Paolo Bonzini.
Regards, Dima.
On Tue, Jun 19, 2018 at 05:12:16PM +0300, Dima Stepanov wrote:
> Ping.
>
> Regards, Dima.
>
> On Wed, Jun 13, 2018 at 11:19:55AM +0300, Dima Stepanov wrote:
> > In the memory_region_do_invalidate_mmio_ptr() routine the section
> > variable is
On Wed, Jul 11, 2018 at 10:05:50AM +0100, Suzuki K Poulose wrote:
> On 10/07/18 18:03, Dave Martin wrote:
> >On Tue, Jul 10, 2018 at 05:38:39PM +0100, Suzuki K Poulose wrote:
> >>On 09/07/18 14:37, Dave Martin wrote:
> >>>On Mon, Jul 09, 2018 at 01:29:42PM +0100, Marc Zyngier wrote:
> On
On 10/07/2018 17:50, Stefan Hajnoczi wrote:
> The ->pre_plug() callback is invoked before the device is realized. The
> ->plug() callback is invoked when the device is being realized but
> before it is reset.
>
> This patch adds a ->post_plug() callback which is invoked after the
> device has
Am 11.07.2018 um 09:05 hat Fam Zheng geschrieben:
> This step was left behind my mistake. As suggested by the echoed text,
> the intention was to test two devices with the same image, with
> different options. The behavior should be the same as two QEMU
> processes. Complete it.
>
>
On 05.07.2018 19:25, Jason J. Herne wrote:
> From: "Jason J. Herne"
You might want to do a --reset-author of this patch to get rid of this
"From:" line...
> Add bootindex property and iplb data for vfio-ccw devices. This allows us to
> forward boot information into the bios for vfio-ccw
Am 10.07.2018 um 22:16 hat Peter Lieven geschrieben:
>
>
> > Am 10.07.2018 um 17:31 schrieb Kevin Wolf :
> >
> > Am 10.07.2018 um 17:05 hat Peter Lieven geschrieben:
> >> We currently don't enforce that the sparse segments we detect during
> >> convert are
> >> aligned. This leads to
'I' was being double-incremented; correctly within the inner loop
and incorrectly within the outer loop.
Signed-off-by: Richard Henderson
---
Fixes a SIGSEGV within one of these generated helpers,
exposed by an armclang vectorized code sample.
r~
---
target/arm/sve_helper.c | 4 ++--
1 file
Hello,
On Wed, Jul 11, 2018 at 12:39 PM, Richard Henderson
wrote:
> 'I' was being double-incremented; correctly within the inner loop
> and incorrectly within the outer loop.
>
> Signed-off-by: Richard Henderson
I didn't try to apply the patch but line numbers look wrong.
I guess this should
On Tue, 10 Jul 2018 17:07:37 -0700
Siwei Liu wrote:
> On Mon, Jul 9, 2018 at 6:54 PM, Michael S. Tsirkin wrote:
> > On Mon, Jul 09, 2018 at 06:11:53PM -0700, si-wei liu wrote:
> >> The plan is to enable group ID based matching in the first place rather
> >> than
> >> match by MAC, the latter
Qemu includes the glibc headers for the host defines and target headers are
part of the qemu source themselves. The glibc has the F_GETLK64, F_SETLK64
and F_SETLKW64 defined to 12, 13 and 14 for all archs(generic) in
sysdeps/unix/sysv/linux/bits/fcntl-linux.h. The linux kernel generic
definition
Am 10.07.2018 um 16:02 hat Marc-André Lureau geschrieben:
> Hi
>
> On Tue, Jul 10, 2018 at 3:20 PM, Kevin Wolf wrote:
> > Am 03.07.2018 um 23:35 hat Markus Armbruster geschrieben:
> >> handle_qmp_command() reports JSON syntax errors right away. This is
> >> wrong when OOB is enabled, because
On 05.07.2018 19:25, Jason J. Herne wrote:
> From: "Jason J. Herne"
git commit --amend --reset-author ?
> Create a boot_setup function to handle getting boot information from
> the machine/hypervisor. This decouples common boot logic from the
> virtio code path and allows us to make use of it
On Wed, 11 Jul 2018 16:26:19 +1000
David Gibson wrote:
> On Tue, Jul 10, 2018 at 05:14:53PM +1000, Alexey Kardashevskiy wrote:
> > On Tue, 10 Jul 2018 16:42:48 +1000
> > David Gibson wrote:
> >
> > > On Tue, Jul 10, 2018 at 12:22:44PM +1000, Alexey Kardashevskiy wrote:
> > > > On Mon, 2
Our Makefile has:
vm-build-%: tests/vm/%.img
$(call quiet-command, \
$(SRC_PATH)/tests/vm/$* \
$(if $(V)$(DEBUG), --debug) \
$(if $(DEBUG), --interactive) \
the intention of which is to let the make command in VM have V=1 if
V=1 is set. We
On Wed, 07/11 14:58, Fam Zheng wrote:
> This makes test-block work.
>
> Signed-off-by: Fam Zheng
Queued, thanks.
On Mon, Jul 09, 2018 at 11:11:31AM +0200, Emanuele Giuseppe Esposito wrote:
> -QPCIBus *qpci_init_pc(QTestState *qts, QGuestAllocator *alloc)
> +static void *qpci_get_driver(void *obj, const char *interface)
> {
> -QPCIBusPC *ret = g_new0(QPCIBusPC, 1);
> +QPCIBusPC *qpci = obj;
> +if
On 11/07/2018 16:28, Stefan Hajnoczi wrote:
>> + * build_driver_cmd_line(): builds the command line for the driver
>> + * @node. The node name must be a valid qemu identifier, since it
>> + * will be used to build the command line.
>> + *
>> + * It is also possible to pass an optional @args that
On Mon, Jul 09, 2018 at 11:11:35AM +0200, Emanuele Giuseppe Esposito wrote:
> Add main executable that takes care of starting the framework, create the
> nodes, set the available drivers/machines, discover the path and run tests.
This is elegant, I like it.
> Signed-off-by: Emanuele Giuseppe
On 07/10/2018 01:00 PM, Peter Maydell wrote:
> Now that we have full support for small regions, including execution,
> we can remove the workarounds where we marked all small regions as
> non-executable for the M-profile MPU and SAU.
>
> Signed-off-by: Peter Maydell
Reviewed-by: Philippe
On Mon, Jul 09, 2018 at 11:11:36AM +0200, Emanuele Giuseppe Esposito wrote:
> +/**
> + * Old sdhci_t structure:
Do you intend to delete this comment before this series is merged? It
seems like a TODO that doesn't need to be kept around.
> +qos_add_test("sdhci-test", "sdhci", test_machine);
On 07/11/2018 11:18 AM, Fam Zheng wrote:
> Our Makefile has:
>
> vm-build-%: tests/vm/%.img
> $(call quiet-command, \
> $(SRC_PATH)/tests/vm/$* \
> $(if $(V)$(DEBUG), --debug) \
> $(if $(DEBUG), --interactive) \
>
> the intention of which is to let
In order not to upload a big image I can say that you can generate the image
with this tool
https://github.com/M0Rf30/simonpi
the initrd used is in the arch linux arm boot partition generated by the
previous referenced tool.
--
You received this bug notification because you are a member of
On 11/07/2018 16:59, Stefan Hajnoczi wrote:
>> +machine->obj.get_device = raspi2_get_device;
>> +machine->obj.destructor = raspi2_destroy;
>> +qos_create_sdhci_mm(>sdhci, 0x3f30, &(QSDHCIProperties) {
>> +.version = 3,
>> +.baseclock = 52,
>> +.capab.sdma =
On Wed, 11 Jul 2018 15:32:12 +0200
Paolo Bonzini wrote:
> On 11/07/2018 15:29, Stefan Hajnoczi wrote:
> >> if (dev->hotplugged) {
> >> device_reset(dev);
> >> +
> >> +if (hotplug_ctrl) {
> > In the final patch I will move this out of if (dev->hotplugged) since
v2: Drop archive-source.sh changes.
The new test depends on the iotests nbd fix I posted today to pass.
Docker testing on patchew has long suffered from 'make check' hangings. The
cleanness of VM testing is the cure. Now let's add a CentOS 7 image to run the
tests. It's purely ad-hoc, but
In VM based tests, the source archive is created in host, we don't have
to run archive-source.sh again, as it complicates the Makefile and
scripts.
Signed-off-by: Fam Zheng
---
tests/docker/Makefile.include | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
Not using snapshot has the benefit of automatically persisting useful
test harnesses, such as docker images and ccache database. Although it
will lose some cleanness, it is imaginably useful for patchew.
Signed-off-by: Fam Zheng
---
tests/vm/basevm.py | 7 ++-
1 file changed, 6
On 07/10/2018 01:00 PM, Peter Maydell wrote:
> Now that all the callers can handle get_page_addr_code() returning -1,
> remove all the code which tries to handle execution from MMIO regions
> or small-MMU-region RAM areas. This will mean that we can correctly
> execute from these areas, rather
On 10/07/2018 - 16:55:57, Marc-André Lureau wrote:
> Current and upcoming mesa releases rely on a shader disk cash. It uses
> a thread job queue with low priority, set with
> sched_setscheduler(SCHED_IDLE). However, that syscall is rejected by
> the "resourcecontrol" seccomp qemu filter.
>
>
On 11/07/2018 16:49, Stefan Hajnoczi wrote:
> On Mon, Jul 09, 2018 at 11:11:31AM +0200, Emanuele Giuseppe Esposito wrote:
>> -QPCIBus *qpci_init_pc(QTestState *qts, QGuestAllocator *alloc)
>> +static void *qpci_get_driver(void *obj, const char *interface)
>> {
>> -QPCIBusPC *ret =
Hi Fam,
On 07/11/2018 11:18 AM, Fam Zheng wrote:
> This one does docker testing in the VM. It is intended to replace the
> native docker testing on patchew testers.
>
> Signed-off-by: Fam Zheng
> ---
> tests/vm/Makefile.include | 2 +-
> tests/vm/centos | 84
On Tue, Jul 10, 2018 at 10:07:31AM +0100, Daniel P. Berrangé wrote:
> On Mon, Jul 09, 2018 at 05:37:31PM -0300, Eduardo Habkost wrote:
> > Every time we create new PC machine-types in QEMU, the defaults
> > for SMBIOS fields change unnecessarily because the version field
> > defaults to
Le 11/07/2018 à 15:04, Laurent Vivier a écrit :
> Le 11/07/2018 à 12:55, Shivaprasad G Bhat a écrit :
>> Qemu includes the glibc headers for the host defines and target headers are
>> part of the qemu source themselves. The glibc has the F_GETLK64, F_SETLK64
>> and F_SETLKW64 defined to 12, 13 and
According to KVM API Documentation, we should only
run vcpu ioctls from the same thread that was used
to create the vcpu. This patch makes KVM_KVMCLOCK_CTRL
ioctl consistent with the Documentation.
No functional change.
Signed-off-by: Yongji Xie
Signed-off-by: Chai Wen
---
hw/i386/kvm/clock.c
On 07/05/2018 04:54 AM, Greg Kurz wrote:
> It is unsafe to rely on *_enabled() helpers before the accelerator has
> been initialized, ie, accel_init_machine() has succeeded, because they
> always return false. But it is still possible to end up calling them
> indirectly by inadvertance, and cause
On 07/11/2018 09:36 AM, Stefan Hajnoczi wrote:
> On Wed, Jul 04, 2018 at 03:35:18PM +, Aleksandar Markovic wrote:
>> If checkpatch.pl is applied (using switch "-f") on file
>> target/mips/msa_helper.c, it will hang.
>>
>> There is a workaround for this particular file:
>>
>> These lines in
Hi Stephane,
On 07/11/2018 04:52 AM, stephane duverger wrote:
> To reach gdb_set_stop_cpu() with gdbserver_state == NULL, you previously
>> entered gdb_vm_state_change() with and use CPUState *cpu =
>> gdbserver_state->c_cpu = NULL deref, which shouldn't happen.
>> Also in gdb_set_stop_cpu() you
** Tags added: canonical-is
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1719339
Title:
serial8250: too much work for irq3
Status in QEMU:
New
Bug description:
It's know issue and sometimes
On 07/11/2018 04:00 PM, Stefan Hajnoczi wrote:
On Mon, Jul 09, 2018 at 11:11:29AM +0200, Emanuele Giuseppe Esposito wrote:
Basic framework steps are the following:
- All nodes and edges are created in their respective machine/driver/test files
- The framework starts QEMU and asks for a list of
This one does docker testing in the VM. It is intended to replace the
native docker testing on patchew testers.
Signed-off-by: Fam Zheng
---
tests/vm/Makefile.include | 2 +-
tests/vm/centos | 84 +++
2 files changed, 85 insertions(+), 1
On Mon, Jul 09, 2018 at 11:11:30AM +0200, Emanuele Giuseppe Esposito wrote:
> +/* Graph Edge.*/
> +struct QOSGraphEdge {
> +QOSEdgeType type;
> +char *dest;
> +char *arg; /* just for CONTAIS and CONSUMED_BY */
CONTAINS?
> +/**
> + * remove_node(): removes a node @val from the nodes
On Mon, Jul 09, 2018 at 11:11:33AM +0200, Emanuele Giuseppe Esposito wrote:
> Add arm/raspi2 machine to the graph. This machine contains a generic-sdhci, so
> its constructor must take care of setting it properly when called.
>
> Signed-off-by: Emanuele Giuseppe Esposito
> ---
>
On Tue, 10 Jul 2018 16:50:36 +0100
Stefan Hajnoczi wrote:
> The ->pre_plug() callback is invoked before the device is realized. The
> ->plug() callback is invoked when the device is being realized but
> before it is reset.
>
> This patch adds a ->post_plug() callback which is invoked after
On Mon, Jul 09, 2018 at 11:11:29AM +0200, Emanuele Giuseppe Esposito wrote:
> This work is being done as Google Summer of Code 2018 project for QEMU,
> my mentors are Paolo Bonzini and Laurent Vivier.
> Additional infos on the project can be found at:
>
On 07/11/2018 04:49 PM, Stefan Hajnoczi wrote:
On Mon, Jul 09, 2018 at 11:11:31AM +0200, Emanuele Giuseppe Esposito wrote:
-QPCIBus *qpci_init_pc(QTestState *qts, QGuestAllocator *alloc)
+static void *qpci_get_driver(void *obj, const char *interface)
{
-QPCIBusPC *ret = g_new0(QPCIBusPC,
Am 2018-07-11 17:48, schrieb Eduardo Habkost:
"none" looked like a false positive when I first looked, but now
I think it's not. Shouldn't it set default_display="none"?
I think that there is some other logic burried that these machine
doesn't get a graphics display. But overall it is indeed
On 11 July 2018 at 17:12, Eduardo Habkost wrote:
> On Wed, Jul 11, 2018 at 09:21:48AM +0200, Thomas Huth wrote:
>> On 10.07.2018 08:50, Peter Maydell wrote:
>> > On 9 July 2018 at 23:03, Thomas Huth wrote:
>> >> On 09.07.2018 23:42, Peter Maydell wrote:
>> >>> On 9 July 2018 at 22:03, Thomas
On 09/07/2018 23:03, Thomas Huth wrote:
>
> The problem is that qdev_set_parent_bus() from instance_init adds a link
> to the child devices which is not valid anymore after the device init
> failed. Thus the qdev_set_parent_bus() must rather be done in the realize
> function instead.
The
On 10/07/2018 08:50, Peter Maydell wrote:
>>> Yuck. The real problem here is that we're still requiring the
>>> code that creates these QOM devices to manually set the parent
>>> in the first place. It's not surprising that we don't get it right
>>> (either parenting in the wrong place or not at
On 07/11/2018 05:15 PM, Stefan Hajnoczi wrote:
On Mon, Jul 09, 2018 at 11:11:36AM +0200, Emanuele Giuseppe Esposito wrote:
+/**
+ * Old sdhci_t structure:
Do you intend to delete this comment before this series is merged? It
seems like a TODO that doesn't need to be kept around.
Paolo
Le 11/07/2018 à 18:40, Laurent Vivier a écrit :
> The value given by mmap_find_vma_reserved() is used with mmap(),
> so it is needed to be aligned with the host page size.
>
> Since commit 18e80c55bb, reserved_va is only aligned to TARGET_PAGE_SIZE,
> and it works well if this size is greater or
On Wed, Jul 11, 2018 at 07:20:42PM +0200, Paolo Bonzini wrote:
> On 09/07/2018 23:03, Thomas Huth wrote:
> >
> > The problem is that qdev_set_parent_bus() from instance_init adds a link
> > to the child devices which is not valid anymore after the device init
> > failed. Thus the
On Wed, Jul 11, 2018 at 07:00:54PM +0200, Sebastian Bauer wrote:
> Am 2018-07-11 17:48, schrieb Eduardo Habkost:
> > "none" looked like a false positive when I first looked, but now
> > I think it's not. Shouldn't it set default_display="none"?
>
> I think that there is some other logic burried
On 11.07.2018 19:20, Paolo Bonzini wrote:
> On 09/07/2018 23:03, Thomas Huth wrote:
>>
>> The problem is that qdev_set_parent_bus() from instance_init adds a link
>> to the child devices which is not valid anymore after the device init
>> failed. Thus the qdev_set_parent_bus() must rather be done
On 11.07.2018 19:21, Paolo Bonzini wrote:
> On 10/07/2018 08:50, Peter Maydell wrote:
Yuck. The real problem here is that we're still requiring the
code that creates these QOM devices to manually set the parent
in the first place. It's not surprising that we don't get it right
From: Marc-André Lureau
qmp_error_response() will free the given error. Fix double-free in
later qmp_request_free().
Signed-off-by: Marc-André Lureau
Message-Id: <20180705164201.9853-1-marcandre.lur...@redhat.com>
Reviewed-by: Markus Armbruster
Fixes: 1cc37471525d03f963bc71d724f0dc9eab888fc1
The following changes since commit c447afd5783b9237fa51b7a85777007d8d568bfc:
Update version for v3.0.0-rc0 release (2018-07-10 18:19:50 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-monitor-2018-07-11
for you to fetch changes up to
On Wed, Jul 11, 2018 at 06:19:33PM +0200, Paolo Bonzini wrote:
> On 11/07/2018 18:00, Eduardo Habkost wrote:
> >> @@ -237,7 +237,7 @@ int x86_cpu_write_elf32_note(WriteCoreDumpFunction f,
> >> CPUState *cs,
> >> * please count up QEMUCPUSTATE_VERSION if you have changed definition of
> >> *
On Wed, Jul 04, 2018 at 03:35:18PM +, Aleksandar Markovic wrote:
> If checkpatch.pl is applied (using switch "-f") on file
> target/mips/msa_helper.c, it will hang.
>
> There is a workaround for this particular file:
>
> These lines in msa_helper.c:
>
> uint## BITS ##_t S = _S, T
On Thu, Jul 05, 2018 at 03:16:44PM +0800, Dongli Zhang wrote:
>
>
> On 07/05/2018 12:12 PM, Probir Roy wrote:
> >> Does 'per CPU basis' indicates irq per cpu, or irq per device queue?
> >
> > IRQ per CPU core, meaning that IRQ will be raised at and served by
> > that CPU. Does IRQ per queue
On Fri, Jul 06, 2018 at 03:55:14PM +0100, Peter Maydell wrote:
> On 5 July 2018 at 23:21, Julia Suvorova wrote:
> > Check that reserved SCS registers return 0 at read,
> > and writes are ignored.
> >
> > Based-on: <20180627143815.1829-1-j...@jms.id.au>
> > Based-on:
On Mon, Jul 09, 2018 at 03:45:49PM +0200, Cornelia Huck wrote:
> Hi,
>
> I recently noticed that iotest 147 was hanging on my laptop, but worked
> fine on my s390x LPAR. Turned out that the architecture was a red
> herring; on both platforms, things fail with the 'simple' trace backend
> and work
On Tue, Jul 10, 2018 at 06:33:35PM +0300, Julia Suvorova via Qemu-devel wrote:
> The differences from ARMv7-M NVIC are:
> * ARMv6-M only supports up to 32 external interrupts
>(configurable feature already). The ICTR is reserved.
> * Active Bit Register is reserved.
> * ARMv6-M supports
On 11 July 2018 at 14:25, Stefan Hajnoczi wrote:
> On Tue, Jul 10, 2018 at 06:33:35PM +0300, Julia Suvorova via Qemu-devel wrote:
>> The differences from ARMv7-M NVIC are:
>> * ARMv6-M only supports up to 32 external interrupts
>>(configurable feature already). The ICTR is reserved.
>> *
On Tue, Jul 10, 2018 at 05:01:22PM +0200, Cornelia Huck wrote:
[...]
> Who is, in general, testing which libvirt version? I can think of:
> - libvirt developers, which will probably run libvirt current git, but
> more likely a released QEMU?
> - QEMU (and other related tools) developers, who
On 11 July 2018 at 14:47, Philippe Mathieu-Daudé wrote:
> Hi Dima,
>
> On 07/11/2018 05:34 AM, Dima Stepanov wrote:
>> Gentle ping. CCing Paolo Bonzini.
>>
>> Regards, Dima.
>>
>> On Tue, Jun 19, 2018 at 05:12:16PM +0300, Dima Stepanov wrote:
>>> Ping.
>>>
>>> Regards, Dima.
>>>
>>> On Wed, Jun
Yes, it does appear, you just need to make vvfat rw:
$ qemu-system-x86_64 -drive file.driver=vvfat,file.dir=foo,file.rw=on
vvfat foo chs 1024,16,63
WARNING: Image format was not specified for 'json:{"dir": "foo", "driver":
"vvfat", "rw": "on"}' and probing guessed raw.
Automatically
On Thu, Jul 05, 2018 at 09:54:30AM +0200, Greg Kurz wrote:
> It is unsafe to rely on *_enabled() helpers before the accelerator has
> been initialized, ie, accel_init_machine() has succeeded, because they
> always return false. But it is still possible to end up calling them
> indirectly by
On Wed, Jul 04, 2018 at 02:49:22PM +0200, Andrew Jones wrote:
> The ACPI PPTT table supports topology descriptions for ACPI
> guests. Note, while a DT boot Linux guest with a non-flat CPU
> topology will see socket and core IDs being sequential integers
> starting from zero, e.g. with -smp
On Thu, Jul 05, 2018 at 04:49:22PM +0100, Peter Maydell wrote:
> On 5 July 2018 at 16:45, Peter Maydell wrote:
> > On 30 June 2018 at 10:13, Stefan Hajnoczi wrote:
> >> The ARMv7-M code is largely similar to what other M Profile CPUs need.
> >> Extract the common M Profile aspects into the
On Wed, 11 Jul 2018 14:06:17 +0100
Stefan Hajnoczi wrote:
> On Mon, Jul 09, 2018 at 03:45:49PM +0200, Cornelia Huck wrote:
> > Hi,
> >
> > I recently noticed that iotest 147 was hanging on my laptop, but worked
> > fine on my s390x LPAR. Turned out that the architecture was a red
> > herring;
Kevin Wolf writes:
> Am 10.07.2018 um 16:02 hat Marc-André Lureau geschrieben:
>> Hi
>>
>> On Tue, Jul 10, 2018 at 3:20 PM, Kevin Wolf wrote:
>> > Am 03.07.2018 um 23:35 hat Markus Armbruster geschrieben:
>> >> handle_qmp_command() reports JSON syntax errors right away. This is
>> >> wrong
On Wed, Jul 04, 2018 at 03:54:10PM +0100, Stefan Hajnoczi wrote:
Sorry you weren't CCed originally, Berto. This one is for you! :)
> Throttle groups consist of members sharing one throttling state
> (including bps/iops limits). Round-robin scheduling is used to ensure
> fairness. If a group
Le 11/07/2018 à 12:55, Shivaprasad G Bhat a écrit :
> Qemu includes the glibc headers for the host defines and target headers are
> part of the qemu source themselves. The glibc has the F_GETLK64, F_SETLK64
> and F_SETLKW64 defined to 12, 13 and 14 for all archs(generic) in
>
On Thu, 5 Jul 2018 16:27:05 +0200
Auger Eric wrote:
> Hi Shameer,
>
> On 07/05/2018 03:19 PM, Shameerali Kolothum Thodi wrote:
> >
> >> -Original Message-
> >> From: Auger Eric [mailto:eric.au...@redhat.com]
> >> Sent: 05 July 2018 13:18
> >> To: David Hildenbrand ;
According to KVM API Documentation, we should only
run vcpu ioctls from the same thread that was used
to create the vcpu. This patch makes KVM_KVMCLOCK_CTRL
ioctl consistent with the Documentation.
No functional change.
Signed-off-by: Yongji Xie
Signed-off-by: Chai Wen
---
hw/i386/kvm/clock.c
On Tue, Jul 10, 2018 at 04:50:36PM +0100, Stefan Hajnoczi wrote:
> The ->pre_plug() callback is invoked before the device is realized. The
> ->plug() callback is invoked when the device is being realized but
> before it is reset.
>
> This patch adds a ->post_plug() callback which is invoked
On Wed, Jul 11, 2018 at 09:22:27AM +0800, Fam Zheng wrote:
> Explicitly enabling zero detection or compression suppresses copy
> offloading during convert. Document it.
>
> Suggested-by: Kevin Wolf
> Signed-off-by: Fam Zheng
> ---
> qemu-img.texi | 6 --
> 1 file changed, 4 insertions(+),
On Wed, 11 Jul 2018 15:15:45 +0200
Cornelia Huck wrote:
> On Wed, 11 Jul 2018 14:06:17 +0100
> Stefan Hajnoczi wrote:
>
> > On Mon, Jul 09, 2018 at 03:45:49PM +0200, Cornelia Huck wrote:
> > > Hi,
> > >
> > > I recently noticed that iotest 147 was hanging on my laptop, but worked
> > > fine
Public bug reported:
I have qemu windows build 2.12.90, haxm 7.2.0. Ubuntu, nor arch linux does not
works when i turn on hax acceleration. Permanent kernel panics, black screen
freezing and other crashes happens when i run qemu.
Qemu crashed with hax - when i ran it from iso. It crashed on
On 07/11/2018 03:58 AM, Fam Zheng wrote:
> This makes test-block work.
>
> Signed-off-by: Fam Zheng
Reviewed-by: Philippe Mathieu-Daudé
> ---
> tests/docker/dockerfiles/centos7.docker | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/docker/dockerfiles/centos7.docker
>
1 - 100 of 159 matches
Mail list logo
