Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

Eric Blake writes: > On 03/16/2017 04:46 AM, Janne Huttunen wrote: >> On Wed, 2017-03-15 at 08:24 +0100, Gerd Hoffmann wrote: The short answer: emulating real hardware. >>> >>> Ok, that is reason enough. >>> >>> Adding bootonceindex everywhere doesn't look like the

Re: [Qemu-devel] [PATCH 2/2] configure: use pkg-config for obtaining xen version

On 21/03/17 19:54, Stefano Stabellini wrote: > On Tue, 21 Mar 2017, Juergen Gross wrote: >> On 17/03/17 19:33, Stefano Stabellini wrote: >>> On Fri, 17 Mar 2017, Juergen Gross wrote: On 16/03/17 21:20, Stefano Stabellini wrote: > On Thu, 16 Mar 2017, Juergen Gross wrote: >> Instead of

[Qemu-devel] [Bug 889827] Re: Qemu hangs on loadvm

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/889827 Title: Qemu hangs

Re: [Qemu-devel] [PATCH 0/3] Add COLO-proxy virtio-net support

On 03/22/2017 11:13 AM, Jason Wang wrote: On 2017年03月22日 09:50, Zhang Chen wrote: On 03/21/2017 05:15 PM, Jason Wang wrote: On 2017年03月21日 15:08, Zhang Chen wrote: On 03/21/2017 02:30 PM, Jason Wang wrote: On 2017年03月21日 14:16, Zhang Chen wrote: On 03/21/2017 02:10 PM, Jason

Re: [Qemu-devel] [PATCH 0/3] Add COLO-proxy virtio-net support

On 2017年03月22日 09:50, Zhang Chen wrote: On 03/21/2017 05:15 PM, Jason Wang wrote: On 2017年03月21日 15:08, Zhang Chen wrote: On 03/21/2017 02:30 PM, Jason Wang wrote: On 2017年03月21日 14:16, Zhang Chen wrote: On 03/21/2017 02:10 PM, Jason Wang wrote: On 2017年03月21日 13:47, Zhang

[Qemu-devel] [PATCH] e1000: disable debug by default

Disable debug output by default, the information were not needed for release. Cc: Peter Maydell Cc: Stefan Hajnoczi Cc: Leonid Bloch Cc: Dmitry Fleytman Cc:

[Qemu-devel] [PATCH v2 3/3] qapi: Fix QemuOpts visitor regression on unvisited input

An off-by-one in commit 15c2f669e meant that we were failing to check for unparsed input in all QemuOpts visitors. Recent testsuite additions show that fixing the obvious bug with bogus fields will also fix the case of an incomplete list visit; update the tests to match the new behavior. Simple

[Qemu-devel] [PATCH v2 2/3] qom: Avoid unvisited 'id'/'qom-type' in user_creatable_add_opts

A regression in commit 15c2f669e caused us to silently ignore excess input to the QemuOpts visitor. Later, commit ea4641 accidentally abused that situation, by removing "qom-type" and "id" from the corresponding QDict but leaving them defined in the QemuOpts, when using the pair of containers to

[Qemu-devel] [PATCH v2 1/3] tests: Expose regression in QemuOpts visitor

Commit 15c2f669e broke the ability of the QemuOpts visitor to flag extra input parameters, but the regression went unnoticed because of missing testsuite coverage. Add a test to cover this; take the approach already used in 9cb8ef3 of adding a test that passes (to avoid breaking bisection) but

[Qemu-devel] [PATCH v2 for-2.9 0/3] Fix QemuOpts regression on bogus keys

Reported to me off-list by Laurent Vivier, who found the problem while working on https://bugzilla.redhat.com/1433193 Broken since 2.7, but the fix is a one-liner (pointing out my embarrassing mistake of mis-converting a pre-decrement operator); as a bug fix, it still qualifies for 2.9 in spite of

Re: [Qemu-devel] [PATCH v4 14/16] docs: add documentation for vfio-ccw

* 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 for user space to retrieve. The > >

Re: [Qemu-devel] [PATCH v4 11/16] vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls

* Alex Williamson [2017-03-21 12:47:24 -0600]: [...] > > @@ -458,6 +459,11 @@ enum { > > VFIO_CCW_NUM_REGIONS > > }; > > > > +enum { > > + VFIO_CCW_IO_IRQ_INDEX, > > + VFIO_CCW_NUM_IRQS > > +}; > > + > > /** > > * VFIO_DEVICE_GET_PCI_HOT_RESET_INFO -

[Qemu-devel] [PATCH] only link current target arch traces to qemu-system

When building target x86_64-softmmu, all other architectures' trace.o are linked into x86_64-softmmu/qemu-system-x86_64, like hw/arm/trace.o, hw/mips/trace.o etc., that is not necessary. Same thing happens when building other targets. Only current target arch traces should be linked into

Re: [Qemu-devel] [PATCH 0/3] Add COLO-proxy virtio-net support

On 03/21/2017 05:15 PM, Jason Wang wrote: On 2017年03月21日 15:08, Zhang Chen wrote: On 03/21/2017 02:30 PM, Jason Wang wrote: On 2017年03月21日 14:16, Zhang Chen wrote: On 03/21/2017 02:10 PM, Jason Wang wrote: On 2017年03月21日 13:47, Zhang Chen wrote: On 03/21/2017 11:39 AM, Jason

[Qemu-devel] 答复: Re: 答复: Re: 答复: Re: [BUG]COLO failover hang

diff --git a/migration/socket.c b/migration/socket.c index 13966f1..d65a0ea 100644 --- a/migration/socket.c +++ b/migration/socket.c @@ -147,8 +147,9 @@ static gboolean socket_accept_incoming_migration(QIOChannel *ioc, } trace_migration_socket_incoming_accepted()

Re: [Qemu-devel] 答复: Re: 答复: Re: [BUG]COLO failover hang

On 2017/3/21 19:56, Dr. David Alan Gilbert wrote: * Hailiang Zhang (zhang.zhanghaili...@huawei.com) wrote: Hi, Thanks for reporting this, and i confirmed it in my test, and it is a bug. Though we tried to call qemu_file_shutdown() to shutdown the related fd, in case COLO thread/incoming

Re: [Qemu-devel] [PATCH v2 1/2] hw/acpi/vmgenid: prevent device realization on pre-2.5 machine types

> On Mar 20, 2017, at 10:05 AM, Laszlo Ersek wrote: > > The WRITE_POINTER linker/loader command that underlies VMGENID depends on > commit baf2d5bfbac0 ("fw-cfg: support writeable blobs", 2017-01-12), which > in turn depends on fw_cfg DMA. > > DMA for fw_cfg is enabled in

Re: [Qemu-devel] [PATCH] virtio: fix vring_align() on 64-bit win32 platforms

> From: Eric Blake [mailto:ebl...@redhat.com] > Sent: Tuesday, 21 March 2017 15:52 > > On 03/21/2017 05:31 PM, Andrew Baumann wrote: > > "long" is 32-bits on win32, but we need to promote it to a 64-bit hwaddr > > before negating, or else the top half of the address is truncated > > > >

Re: [Qemu-devel] [PATCH] virtio: fix vring_align() on 64-bit win32 platforms

On 03/21/2017 05:31 PM, Andrew Baumann wrote: > "long" is 32-bits on win32, but we need to promote it to a 64-bit hwaddr > before negating, or else the top half of the address is truncated > > Signed-off-by: Andrew Baumann > --- > include/hw/virtio/virtio.h | 2 +-

[Qemu-devel] [PATCH] virtio: fix vring_align() on 64-bit win32 platforms

"long" is 32-bits on win32, but we need to promote it to a 64-bit hwaddr before negating, or else the top half of the address is truncated Signed-off-by: Andrew Baumann --- include/hw/virtio/virtio.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [Qemu-devel] [Qemu-block] [PATCH v2 3/3] qemu-img: print short help on getopt failure

On Fri, Mar 17, 2017 at 06:45:41PM +0800, Stefan Hajnoczi wrote: > Printing the full help output obscures the error message for an invalid > command-line option or missing argument. > > Before this patch: > > $ ./qemu-img --foo > ...pages of output... That gives me: $ qemu-img --foo

Re: [Qemu-devel] [PATCH v3] qemu/thread: Add support for error reporting in qemu_thread_create

Hi, This series failed build test on s390x host. Please find the details below. Subject: [Qemu-devel] [PATCH v3] qemu/thread: Add support for error reporting in qemu_thread_create Message-id: 74f647b8-a890-6635-278a-ce55fbbb5...@gmail.com Type: series === TEST SCRIPT BEGIN === #!/bin/bash #

[Qemu-devel] [PATCH] add xen-9p-backend to MAINTAINERS under Xen

Signed-off-by: Stefano Stabellini Signed-off-by: Stefano Stabellini CC: gr...@kaod.org CC: anthony.per...@citrix.com --- This patch is meant to be on top of http://marc.info/?l=xen-devel=149003409510264=2 --- MAINTAINERS | 1 + 1 file changed, 1

[Qemu-devel] [PATCH v3] qemu/thread: Add support for error reporting in qemu_thread_create

Failure during thread creation in qemu_thread_create does not force the program to exit anymore, since that isn't always the desired behaviour. The caller of qemu_thread_create is responsible for the error handling. Signed-off-by: Achilles Benetopoulos --- cpus.c

[Qemu-devel] [PATCH 55/81] s390x/kvm: fix cmma reset for KVM

From: Christian Borntraeger We must reset the CMMA states for normal memory (when not on mem path), but the current code does the opposite. This was unnoticed for some time as the kernel since 4.6 also had a bug which mostly disabled the paging optimizations. Fixes:

Re: [Qemu-devel] [PATCH v2] qemu/thread: Add support for error reporting in qemu_thread_create

Hi, This series failed build test on s390x host. Please find the details below. Subject: [Qemu-devel] [PATCH v2] qemu/thread: Add support for error reporting in qemu_thread_create Message-id: 0bfb9ff9-b205-42ea-8f8b-936ec51bf...@gmail.com Type: series === TEST SCRIPT BEGIN === #!/bin/bash #

[Qemu-devel] [PATCH v2] qemu/thread: Add support for error reporting in qemu_thread_create

Failure during thread creation in qemu_thread_create does not force the program to exit anymore, since that isn't always the desired behaviour. The caller of qemu_thread_create is responsible for the error handling. Signed-off-by: Achilles Benetopoulos --- cpus.c

Re: [Qemu-devel] [PATCH v4 0/8] xen/9pfs: introduce the Xen 9pfs backend

On Tue, 21 Mar 2017, Greg Kurz wrote: > On Mon, 20 Mar 2017 11:18:46 -0700 (PDT) > Stefano Stabellini wrote: > > > Hi all, > > > > This patch series implements a new transport for 9pfs, aimed at Xen > > systems. > > > > The transport is based on a traditional Xen

[Qemu-devel] [ANNOUNCE] QEMU 2.9.0-rc1 is now available

Hello, On behalf of the QEMU Team, I'd like to announce the availability of the second release candidate for the QEMU 2.9 release. This release is meant for testing purposes and should not be used in a production environment. http://download.qemu-project.org/qemu-2.9.0-rc1.tar.xz

Re: [Qemu-devel] [PATCH for-2.9] blockjob: avoid recursive AioContext locking

On 03/21/2017 12:48 PM, Paolo Bonzini wrote: > Streaming or any other block job hangs when performed on a block device > that has a non-default iothread. This happens because the AioContext > is acquired twice by block_job_defer_to_main_loop_bh and then released > only once by BDRV_POLL_WHILE.

Re: [Qemu-devel] [PATCH v3] xen: use libxendevice model to restrict operations

On Tue, 21 Mar 2017, Paul Durrant wrote: > This patch adds a command-line option (-xen-domid-restrict) which will > use the new libxendevicemodel API to restrict devicemodel [1] operations > to the specified domid. (Such operations are not applicable to the xenpv > machine type). > > This patch

Re: [Qemu-devel] [PATCH 2/2] configure: use pkg-config for obtaining xen version

On Tue, 21 Mar 2017, Juergen Gross wrote: > On 17/03/17 19:33, Stefano Stabellini wrote: > > On Fri, 17 Mar 2017, Juergen Gross wrote: > >> On 16/03/17 21:20, Stefano Stabellini wrote: > >>> On Thu, 16 Mar 2017, Juergen Gross wrote: > Instead of trying to guess the Xen version to use by

Re: [Qemu-devel] [PATCH v4 11/16] vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls

On Fri, 17 Mar 2017 04:17:38 +0100 Dong Jia Shi wrote: > Realize VFIO_DEVICE_GET_IRQ_INFO ioctl to retrieve > VFIO_CCW_IO_IRQ information. > > Realize VFIO_DEVICE_SET_IRQS ioctl to set an eventfd fd for > VFIO_CCW_IO_IRQ. Once a write operation to the ccw_io_region

Re: [Qemu-devel] [PATCH v4 03/16] vfio: ccw: define device_api strings

On Fri, 17 Mar 2017 04:17:30 +0100 Dong Jia Shi wrote: > Define vfio-ccw device API strings. CCW vendor driver using mediated > device framework should use this string for device_api attribute. > > Reviewed-by: Pierre Morel >

Re: [Qemu-devel] [PATCH v4 14/16] docs: add documentation for vfio-ccw

On Fri, 17 Mar 2017 04:17:41 +0100 Dong Jia Shi wrote: > Add file Documentation/s390/vfio-ccw.txt that includes details > of vfio-ccw. > > Acked-by: Pierre Morel > Signed-off-by: Dong Jia Shi > --- >

Re: [Qemu-devel] [PATCH v4 09/16] vfio: ccw: realize VFIO_DEVICE_GET_REGION_INFO ioctl

On Fri, 17 Mar 2017 04:17:36 +0100 Dong Jia Shi wrote: > Introduce device information about vfio-ccw: VFIO_DEVICE_FLAGS_CCW. > Realize VFIO_DEVICE_GET_REGION_INFO ioctl for vfio-ccw. > > Reviewed-by: Pierre Morel > Signed-off-by: Dong Jia

Re: [Qemu-devel] Guest application reading from pl011 without device driver

Okay. Thank you very much. I'll take your advice and test. Let's see the chardev maintainers reply. Best, Huan 2017年3月21日 19:28，"Peter Maydell" 写道： > On 21 March 2017 at 18:11, Jiahuan Zhang wrote: > > What do you mean "RXFE will be cleared"?

[Qemu-devel] [PATCH v3] xen: use libxendevice model to restrict operations

This patch adds a command-line option (-xen-domid-restrict) which will use the new libxendevicemodel API to restrict devicemodel [1] operations to the specified domid. (Such operations are not applicable to the xenpv machine type). This patch also adds a tracepoint to allow successful enabling of

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 18:11, Jiahuan Zhang wrote: > What do you mean "RXFE will be cleared"? > Here RXFE is > #define PL011_RXFE 0x10 I mean that as soon as 1 byte of data is ready to read the RXFE bit will be cleared in the FR register. So you need: /* probably you

Re: [Qemu-devel] Guest application reading from pl011 without device driver

2017年3月21日 18:55，"Peter Maydell" 写道： On 21 March 2017 at 17:48, Jiahuan Zhang wrote: > The guest program is as follows. > > While (*UART_FR & PL011_RXFE); //wait until fifo not empty > for (i=0;i <16;i++){ >data [i] = (unsigned char)

Re: [Qemu-devel] [PATCH] test-qobject-input-visitor: Cover visit_type_uint64()

On 03/21/2017 12:44 PM, Markus Armbruster wrote: > The new test demonstrates known bugs: integers between INT64_MAX+1 and > UINT64_MAX rejected, and integers between INT64_MIN and -1 are > accepted modulo 2^64. > > Signed-off-by: Markus Armbruster > --- >

[Qemu-devel] [PATCH] configure: Fix cut-n-paste errors in OS deprecation warning

Fix some cut-and-paste errors in the OS deprecation warning pointed out by Thomas Huth. Reported-by: Thomas Huth Signed-off-by: Peter Maydell --- configure | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure b/configure

Re: [Qemu-devel] [PATCH v2] configure: Warn about deprecated hosts

On 21 March 2017 at 17:55, Thomas Huth wrote: > On 21.03.2017 15:31, Peter Maydell wrote: >> +if test "$supported_os" = "no"; then >> +echo >> +echo "WARNING: SUPPORT FOR THIS HOST OS WILL GO AWAY IN FUTURE >> RELEASES!" >> +echo >> +echo "CPU host OS $targetos

Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures

On 03/16/2017 10:46 AM, Daniel P. Berrange wrote: > >> Should "native CYGWIN" be in the drop list? I only test >> mingw cross compile, but configure has a separate section for >> CYGWIN in its $targetos case statement. > > Cygwin is different enough from mingw that I'd basically call > it a

Re: [Qemu-devel] [PATCH v2] configure: Warn about deprecated hosts

On 21.03.2017 15:31, Peter Maydell wrote: > We plan to drop support in a future QEMU release for host OSes > and host architectures for which we have no test machine where > we can build and run tests. For the 2.9 release, make configure > print a warning if it is run on such a host, so that the

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

On 15/03/2017 07:58, Janne Huttunen wrote: > > Since real HW has this capability, there exist certain > auxiliary systems that are built on it. Having similar > semantics available in QEMU allows me to build a virtual > machine that works with these systems without modifying > them in any way.

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 17:48, Jiahuan Zhang wrote: > The guest program is as follows. > > While (*UART_FR & PL011_RXFE); //wait until fifo not empty > for (i=0;i <16;i++){ >data [i] = (unsigned char) *UART_DR; //read from the data register. > } This is buggy. You must

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

On 03/16/2017 04:46 AM, Janne Huttunen wrote: > On Wed, 2017-03-15 at 08:24 +0100, Gerd Hoffmann wrote: >>> >>> The short answer: emulating real hardware. >> >> Ok, that is reason enough. >> >> Adding bootonceindex everywhere doesn't look like the best plan to me >> though. Possibly we can pimp

Re: [Qemu-devel] [PATCH] block: Make 'replication_state' an enum

On 03/16/2017 09:17 PM, Fam Zheng wrote: > BDRVReplicationState.replication_state is a name with a bit of > duplication, plus it could be an enum like BDRVReplicationState.mode, > which is be more readable and also more straightforward in a debuuger. With the followup commit message cleanups,

[Qemu-devel] [PATCH for-2.9] blockjob: avoid recursive AioContext locking

Streaming or any other block job hangs when performed on a block device that has a non-default iothread. This happens because the AioContext is acquired twice by block_job_defer_to_main_loop_bh and then released only once by BDRV_POLL_WHILE. (Insert rants on recursive mutexes, which

Re: [Qemu-devel] Guest application reading from pl011 without device driver

But what I met is that, when the receiving data is small, no data is knocking the door of the fifo by ReadFile (), then pl011_read can starts. When the data is large, after the fifo is full, there are still data requesting to get into the fifo. Then the device is busy with pl011_can_receive. The

Re: [Qemu-devel] [PATCH 04/21] qobject: add quint type

Hi On Tue, Mar 21, 2017 at 9:06 PM Eric Blake wrote: > On 03/21/2017 11:49 AM, Markus Armbruster wrote: > > > > > QMP clients that work around the "large positive integers are rejected" > > bugs by sending large negative ones instead may well exist. Fixing the > > interface

[Qemu-devel] [PATCH] test-qobject-input-visitor: Cover visit_type_uint64()

The new test demonstrates known bugs: integers between INT64_MAX+1 and UINT64_MAX rejected, and integers between INT64_MIN and -1 are accepted modulo 2^64. Signed-off-by: Markus Armbruster --- tests/test-qobject-input-visitor.c | 30 ++ 1 file

Re: [Qemu-devel] [PATCH] qemu/thread: Add support for error reporting in qemu_thread_create

Hi, This series failed build test on s390x host. Please find the details below. Subject: [Qemu-devel] [PATCH] qemu/thread: Add support for error reporting in qemu_thread_create Message-id: 8408e117-8ab1-150f-c7f9-254b6dd46...@gmail.com Type: series === TEST SCRIPT BEGIN === #!/bin/bash #

[Qemu-devel] [PATCH] qemu/thread: Add support for error reporting in qemu_thread_create

Failure during thread creation in qemu_thread_create does not force the program to exit anymore, since that isn't always the desired behaviour. The caller of qemu_thread_create is responsible for the error handling. Signed-off-by: Achilles Benetopoulos --- cpus.c

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 16:59, Jiahuan Zhang wrote: > > > On 21 March 2017 at 17:50, Peter Maydell wrote: >> >> On 21 March 2017 at 16:47, Jiahuan Zhang wrote: >> > The actual situation is, pl011_can_receive is returning

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 17:59, Jiahuan Zhang wrote: > > > On 21 March 2017 at 17:50, Peter Maydell wrote: > >> On 21 March 2017 at 16:47, Jiahuan Zhang >> wrote: >> > The actual situation is, pl011_can_receive is

Re: [Qemu-devel] [PATCH for-2.9] block: Declare blockdev-add and blockdev-del supported

On 03/21/2017 11:57 AM, Markus Armbruster wrote: > It's been a long journey, but here we are. > > x-blockdev-remove-medium, x-blockdev-insert-medium and > x-blockdev-change need a bit more work, so leave them alone for now. > > Signed-off-by: Markus Armbruster > --- >

Re: [Qemu-devel] [PATCH 04/21] qobject: add quint type

On 03/21/2017 11:49 AM, Markus Armbruster wrote: > > QMP clients that work around the "large positive integers are rejected" > bugs by sending large negative ones instead may well exist. Fixing the > interface would break them. Depressing. Eric, could you have a peek at > libvirt? Yes,

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 17:50, Peter Maydell wrote: > On 21 March 2017 at 16:47, Jiahuan Zhang wrote: > > The actual situation is, pl011_can_receive is returning false, the fifo > is > > full, pl011_read does't start. > > At this moment, only

[Qemu-devel] [PATCH for-2.9] block: Declare blockdev-add and blockdev-del supported

It's been a long journey, but here we are. x-blockdev-remove-medium, x-blockdev-insert-medium and x-blockdev-change need a bit more work, so leave them alone for now. Signed-off-by: Markus Armbruster --- blockdev.c | 4 ++-- qapi/block-core.json | 14

Re: [Qemu-devel] [PATCH v2] xen: use libxendevice model to restrict operations

On Tue, 21 Mar 2017, Paul Durrant wrote: > Fixing list address... > > > -Original Message- > > From: Stefano Stabellini [mailto:sstabell...@kernel.org] > > Sent: 20 March 2017 22:05 > > To: Paul Durrant > > Cc: qemu-de...@lists.xenproject.org; Stefano Stabellini

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 16:47, Jiahuan Zhang wrote: > The actual situation is, pl011_can_receive is returning false, the fifo is > full, pl011_read does't start. > At this moment, only pl011_can_recieve is keeping returning 0. OK, so the incoming data has filled up the

Re: [Qemu-devel] [PATCH v2] numa, spapr: align default numa node memory size to 256MB

On Tue, Mar 21, 2017 at 12:03:21PM +1100, David Gibson wrote: > On Mon, Mar 20, 2017 at 04:11:14PM -0300, Eduardo Habkost wrote: > > On Mon, Mar 20, 2017 at 03:12:44PM +0100, Laurent Vivier wrote: > > > Since commit 224245b ("spapr: Add LMB DR connectors"), NUMA node > > > memory size must be

Re: [Qemu-devel] [PATCH 04/21] qobject: add quint type

Marc-André Lureau writes: > Hi > > On Mon, Mar 13, 2017 at 5:29 PM Marc-André Lureau > wrote: > > Hi > > - Original Message - >> On 03/13/2017 02:15 AM, Markus Armbruster wrote: >> > Eric Blake writes: >> > >> >> On

Re: [Qemu-devel] Guest application reading from pl011 without device driver

many thanks for the rapid reply! On 21 March 2017 at 17:39, Peter Maydell wrote: > On 21 March 2017 at 16:32, Jiahuan Zhang wrote: > > I found the serial device is always trying to receive all the data when > > ReadFile() is running, then

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 21 March 2017 at 16:32, Jiahuan Zhang wrote: > I found the serial device is always trying to receive all the data when > ReadFile() is running, then start reading. Even if the fifo is full, the > _can_receive function still keeps polling if the data is larger than 16

Re: [Qemu-devel] NetBSD doesn't boot under KVM

On 21 March 2017 at 16:24, Paolo Bonzini wrote: > On 21/03/2017 17:14, Peter Maydell wrote: >> Any ideas? Does this sound like a KVM bug, or a guest bug? > > It sounds like a weird bug. :) I'm downloading the image. Thanks. (the freenode/#netbsd IRC channel seemed to have

[Qemu-devel] Guest application reading from pl011 without device driver

Dear QEMU developers, I am trying to read streaming data from a serial device by pointing to the data register. The input data for the serial device is a string, whose length is larger than the receiving fifo (I am using pl011). Ths input is done by ReadFile() since my host is Win 7; Now the

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

On Tue, 21 Mar 2017 10:13:08 +0100 Greg Kurz wrote: > On Mon, 20 Mar 2017 18:07:24 -0500 > Michael Roth wrote: > > > Hi everyone, > > > > The following new patches are queued for QEMU stable v2.8.1: > > > >

Re: [Qemu-devel] NetBSD doesn't boot under KVM

On 21/03/2017 17:14, Peter Maydell wrote: > So if you try to boot NetBSD inside KVM: > > > qemu-img create -f qcow2 disk.qcow2 15G > wget http://cdn.netbsd.org/pub/NetBSD/NetBSD-7.1/images/NetBSD-7.1-amd64.iso > qemu-system-x86_64 -m 2048 -enable-kvm \ >-drive

Re: [Qemu-devel] [PATCH qemu-ga] Start VSS Provider after install

Quoting Sameeh Jubran (2017-03-21 07:03:26) > Signed-off-by: Sameeh Jubran What happens without this patch? Fresh installs don't report the fsfreeze interface as available? > --- > qga/vss-win32/install.cpp | 1 + > 1 file changed, 1 insertion(+) > > diff --git

[Qemu-devel] NetBSD doesn't boot under KVM

So if you try to boot NetBSD inside KVM: qemu-img create -f qcow2 disk.qcow2 15G wget http://cdn.netbsd.org/pub/NetBSD/NetBSD-7.1/images/NetBSD-7.1-amd64.iso qemu-system-x86_64 -m 2048 -enable-kvm \ -drive if=virtio,file=disk.qcow2,format=qcow2 \ -netdev

Re: [Qemu-devel] [PATCH 1/2] tests: Expose regression in QemuOpts visitor

On 21/03/2017 17:01, Markus Armbruster wrote: > Eric Blake writes: > >> On 03/21/2017 08:33 AM, Laurent Vivier wrote: >>> On 21/03/2017 14:21, Eric Blake wrote: On 03/21/2017 04:01 AM, Laurent Vivier wrote: > On 21/03/2017 04:17, Eric Blake wrote: >> Commit

Re: [Qemu-devel] [PATCH] Fix Event Viewer errors caused by qemu-ga

Quoting Sameeh Jubran (2017-03-21 05:49:52) > When the command "guest-fsfreeze-freeze" is executed it causes > the VSS service to log the errors below in the Event Viewer. > > These errors are caused by two issues in the function "CommitSnapshots" in > provider.cpp: > > 1. When VSS_TIMEOUT_MSEC

Re: [Qemu-devel] [PATCH 1/2] tests: Expose regression in QemuOpts visitor

Eric Blake writes: > On 03/21/2017 08:33 AM, Laurent Vivier wrote: >> On 21/03/2017 14:21, Eric Blake wrote: >>> On 03/21/2017 04:01 AM, Laurent Vivier wrote: On 21/03/2017 04:17, Eric Blake wrote: > Commit 15c2f669e broke the ability of the QemuOpts visitor to >

Re: [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"

On 03/21/17 16:50, Paolo Bonzini wrote: > > > On 21/03/2017 16:45, Laszlo Ersek wrote: >>> +* [Testing SMM with QEMU, KVM and >>> + >>> libvirt](https://github.com/tianocore/tianocore.github.io/wiki/Testing-SMM-with-QEMU,-KVM-and-libvirt) >>> + by László Eršek >> >> NAK, Eršek <-> Érsek :) >

Re: [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"

On 21/03/2017 16:45, Laszlo Ersek wrote: >> +* [Testing SMM with QEMU, KVM and >> + >> libvirt](https://github.com/tianocore/tianocore.github.io/wiki/Testing-SMM-with-QEMU,-KVM-and-libvirt) >> + by László Eršek > > NAK, Eršek <-> Érsek :) Is it at least the first time that you get _that_

Re: [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"

On 03/19/17 10:46, Paolo Bonzini wrote: > Just an idea... If this is useful, we can do it every month. It only > takes ten minutes to skim planet.virt-tools.org and compile the list. > > Signed-off-by: Paolo Bonzini > --- > .../2017-03-19-qemu-in-the-blogs-february-2017.md

Re: [Qemu-devel] [PULL 0/2] 9pfs fixes 2017-03-21 for 2.9

On 21 March 2017 at 14:12, Greg Kurz wrote: > The following changes since commit 940a8ce075e3408742a4edcabfd6c2a15e2539eb: > > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into > staging (2017-03-20 16:34:26 +) > > are available in the git repository at:

Re: [Qemu-devel] [PATCH 1/2] tests: Expose regression in QemuOpts visitor

On 03/21/2017 08:33 AM, Laurent Vivier wrote: > On 21/03/2017 14:21, Eric Blake wrote: >> On 03/21/2017 04:01 AM, Laurent Vivier wrote: >>> On 21/03/2017 04:17, Eric Blake wrote: Commit 15c2f669e broke the ability of the QemuOpts visitor to flag extra input parameters, but the regression

Re: [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"

On Tue, Mar 21, 2017 at 01:35:02PM +0100, Paolo Bonzini wrote: > > > On 21/03/2017 13:30, Kashyap Chamarthy wrote: > > On Tue, Mar 21, 2017 at 01:09:19PM +0100, Thomas Huth wrote: > >> On 19.03.2017 10:46, Paolo Bonzini wrote: > >>> Just an idea... If this is useful, we can do it every month.

[Qemu-devel] [Bug 1670175] Re: qemu-system-sparc64 with tribblix-sparc-0m16.iso ends with "panic - kernel: no nucleus hblk8 to allocate"

QEMU 2.8.90 gets a bit further with Tribblix: $ qemu-system-sparc64 -m 2048 -cdrom ~/Downloads/tmp/tribblix-sparc-0m16.iso -boot d -M sun4u -nographic OpenBIOS for Sparc64 Configuration device id QEMU version 1 machine id 0 kernel cmdline CPUs: 1 x SUNW,UltraSPARC-IIi UUID:

Re: [Qemu-devel] [PATCH] 9pfs: don't try to flush self and avoid QEMU hang on reset

On 03/21/2017 09:42 AM, Greg Kurz wrote: >>> This insane behavior is likely to denote a bug in the client, and it would >>> deserve an Rerror message to be sent back. Unfortunately, the protocol >>> allows it and requires all flush requests to suceed (only a Tflush response >>> >> >>

Re: [Qemu-devel] [PATCH 03/21] object: fix potential leak in getters

On 03/11/2017 07:22 AM, Marc-André Lureau wrote: > If the property is not of the requested type, the getters will leak a > QObject. > > Signed-off-by: Marc-André Lureau > Cc: qemu-triv...@nongnu.org > --- > qom/object.c | 6 +++--- > 1 file changed, 3 insertions(+),

Re: [Qemu-devel] [PATCH] 9pfs: don't try to flush self and avoid QEMU hang on reset

On Tue, 21 Mar 2017 09:01:50 -0500 Eric Blake wrote: > On 03/16/2017 11:33 AM, Greg Kurz wrote: > > According to the 9P spec [*], when a client wants to cancel a pending I/O > > request identified by a given tag (uint16), it must send a Tflush message > > and wait for the

Re: [Qemu-devel] [PATCH v0] fsdev: QMP interface for throttling

On 03/21/2017 04:44 AM, Pradeep Jagadeesh wrote: >> >> You're introducing this struct in 2.10, so this member is not since 1.7. >> Either that, or you're copying-and-pasting when you should be sharing >> code and reusing an existing struct. > Hmm..copied the block devices code, I will correct

[Qemu-devel] [PATCH v2] configure: Warn about deprecated hosts

We plan to drop support in a future QEMU release for host OSes and host architectures for which we have no test machine where we can build and run tests. For the 2.9 release, make configure print a warning if it is run on such a host, so that the user has some warning of the plans and can

[Qemu-devel] [PULL 2/2] 9pfs: proxy: assert if unmarshal fails

Replies from the virtfs proxy are made up of a fixed-size header (8 bytes) and a payload of variable size (maximum 64kb). When receiving a reply, the proxy backend first reads the whole header and then unmarshals it. If the header is okay, it then does the same operation with the payload. Since

[Qemu-devel] [Bug 1670170] Re: `qemu-system-sparc64 -M Niagara` Aborted (core dumped)

Fixed in version 2.8.90. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1670170 Title: `qemu-system-sparc64 -M Niagara` Aborted (core

[Qemu-devel] [Bug 1670170] Re: `qemu-system-sparc64 -M Niagara` Aborted (core dumped)

Retested with QEMU 2.8.90: 15:03 $ qemu-system-sparc64 -M Niagara qemu-system-sparc64: -M Niagara: unsupported machine type Use -machine help to list supported machines 15:03 $ qemu-system-sparc64 -M help Supported machines are: niagara Sun4v platform, Niagara none

[Qemu-devel] [PATCH qemu-ga] qemu-ga: Don't display errors to the user on thaw command

Errors that are related to ur inner implementation for the thaw command shouldn't be displayed to the user. Signed-off-by: Sameeh Jubran --- qga/vss-win32/requester.cpp | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/qga/vss-win32/requester.cpp

[Qemu-devel] [PULL 1/2] 9pfs: don't try to flush self and avoid QEMU hang on reset

According to the 9P spec [*], when a client wants to cancel a pending I/O request identified by a given tag (uint16), it must send a Tflush message and wait for the server to respond with a Rflush message before reusing this tag for another I/O. The server may still send a completion message for

[Qemu-devel] [PULL 0/2] 9pfs fixes 2017-03-21 for 2.9

The following changes since commit 940a8ce075e3408742a4edcabfd6c2a15e2539eb: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-03-20 16:34:26 +) are available in the git repository at: https://github.com/gkurz/qemu.git tags/for-upstream for you to

Re: [Qemu-devel] [BUG] virtio-net linux driver fails to probe on MIPS Malta since 'hw/virtio-pci: fix virtio behaviour'

On 03/20/2017 05:43 PM, Michael S. Tsirkin wrote: On Mon, Mar 20, 2017 at 05:21:22PM +0200, Marcel Apfelbaum wrote: On 03/17/2017 11:57 PM, James Hogan wrote: Hi, I've bisected the following failure of the virtio_net linux v4.10 driver to probe in QEMU v2.9.0-rc1 emulating a MIPS Malta

Re: [Qemu-devel] [PATCH] qemu-ga: add guest-get-osinfo command

> On Mar 21, 2017, at 2:39 PM, Eric Blake wrote: > > On 03/16/2017 05:23 AM, Vinzenz 'evilissimo' Feenstra wrote: >> From: Vinzenz Feenstra >> >> Add a new 'guest-get-osinfo' command for reporting basic information of >> the guest operating system

Re: [Qemu-devel] [PATCH] 9pfs: don't try to flush self and avoid QEMU hang on reset

On 03/16/2017 11:33 AM, Greg Kurz wrote: > According to the 9P spec [*], when a client wants to cancel a pending I/O > request identified by a given tag (uint16), it must send a Tflush message > and wait for the server to respond with a Rflush message before reusing this > tag for another I/O. The

Re: [Qemu-devel] [PATCH v2] add opengl_cflags to QEMU_CFLAGS

On 21 March 2017 at 07:04, Gerd Hoffmann wrote: > ... and drop OPENGL_CFLAGS from Makefiles. > > Signed-off-by: Gerd Hoffmann > --- > configure| 2 +- > hw/display/Makefile.objs | 6 +- > ui/Makefile.objs | 7 ++- > 3 files

[Qemu-devel] [PATCH qemu-ga] Fix a bug where qemu-ga service is stuck during stop operation

After triggering a freeze command without any following thaw command, qemu-ga will not respond to stop operation. This behaviour is wanted on Linux as there is no time limit for a freeze command and we want to prevent quitting in the middle of freeze, on the other hand on Windows the time limit

Re: [Qemu-devel] [PATCH v2] x86: Allow to set NUMA distance for different NUMA nodes

On 03/16/2017 03:38 AM, He Chen wrote: > Current, QEMU does not provide a clear command to set vNUMA distance for > guest although we already have `-numa` command to set vNUMA nodes. Subject line: "Allow to $verb" is not idiomatic English. It is either "Allow $subject to $verb", or the shorter

  1   2   >