Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] vhost-user-blk: prevent using uninitialized vqs

g > the following logs: > > qemu-system-x86_64: Unable to map available ring for ring 0 > qemu-system-x86_64: Verify ring failure on region 0 > > This has already been fixed for vhost scsi devices and was > recently vhost-user scsi devices. This commit fixes it for >

[Qemu-devel] [Bug 1824744] [NEW] ivshmem device PCI device exposes wrong endianness on ppc64le

Public bug reported: On a ppc64le host with a ppc64le guest running on QEMU 3.1.0 when an ivshmem device is used, the ivshmem device appears to expose the wrong endianness for the values in BAR 0. For example, when the guest is assigned an ivshmem device ID of 1, the IVPosition register (u32

[Qemu-devel] [Bug 1824744] Re: ivshmem PCI device exposes wrong endianness on ppc64le

** Summary changed: - ivshmem device PCI device exposes wrong endianness on ppc64le + ivshmem PCI device exposes wrong endianness on ppc64le -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1824744

[Qemu-devel] How can i run different router or switch on qemu

Hello, I'm sorry to waste your time. Now I have a question and i can't find answer by google. I need to use qemu to run different router,switch,and different type(example:cisco,netgear,forti and more) and use openstack vm to connect these equipment. I found these equipment with diff

[Qemu-devel] [PATCH] vmdk: false positive of compat6 with hwversion not set

reproduced by: $ qemu-img convert -O vmdk -o subformat=streamOptimized,compat6 /home/yuchenlin/syno.qcow2 /home/yuchenlin/syno.vmdk qemu-img: /home/yuchenlin/syno.vmdk: error while converting vmdk: compat6 cannot be enabled with hwversion set Signed-off-by: yuchenlin --- block/vmdk.c | 2 +- 1

[Qemu-devel] [Bug 1759338] Re: qemu-system-sparc w/ SS-20 ROM does not add processors

As of QEMU 4 OpenBIOS can boot Solaris again, and it does properly allocate multiple CPUs. Of course, it's a whole lot slower on multiple CPUs which I wasn't really anticipating, but it does work. (And single CPU is so fast anyway compared to the actual hardware it's emulating!) So

Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] vmdk: Fix comment regarding max l1_size coverage

rmat which is not implemented yet in qemu. Reviewed-by: Karl Heubaum Reviewed-by: Eyal Moscovici Reviewed-by: Liran Alon Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- block/vmdk.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/block/vmdk.c b/block/vm

Re: [Qemu-devel] [PATCH] e1000: Delay flush queue when receive RCTL

evel;/* Tracks interrupt pin level. */ uint32_t mit_ide; /* Tracks E1000_TXD_CMD_IDE bit. */ +QEMUTimer *flush_queue_timer; + /* Compatibility flags for migration to/from qemu 1.3.0 and older */ #define E1000_FLAG_AUTONEG_BIT 0 #define E1000_FLAG_MIT_BIT 1 @@ -366,6 +368,7 @@ s

Re: [Qemu-devel] [PATCH] e1000: Delay flush queue when receive RCTL

b/hw/net/e1000.c @@ -120,6 +120,8 @@ typedef struct E1000State_st { bool mit_irq_level;    /* Tracks interrupt pin level. */ uint32_t mit_ide;  /* Tracks E1000_TXD_CMD_IDE bit. */ +    QEMUTimer *flush_queue_timer; +  /* Compatibility flags for migration to/from qemu

[Qemu-devel] [PATCH] vmstate: Add VMSTATE_OPAQUE to save/load complex data structures

From: Roman Kiryanov VMSTATE_OPAQUE allows passing user defined functions to save and load vmstate for cases when data structures do not fit into int/struct/array terms. Signed-off-by: Roman Kiryanov --- include/migration/vmstate.h | 13 + 1 file changed, 13 insertions(+) diff --g

[Qemu-devel] [PATCH v2 0/4] 9p: Fix file ID collisions

Hi! This is v2 of a proposed patch set for fixing file ID collisions with 9pfs. Patch 1 to 3 are identical to the previous version. New in this v2 is patch 4 which introduces variable length suffixes for inode mapping instead of fixed length prefixes. Also: patch 4 disables file ID persistency a

[Qemu-devel] [PATCH v2 1/4] 9p: mitigates most QID path collisions

This first patch here is an updated version of Antonios Motakis' original 4-patch set, merged to one patch: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg02283.html * Updated to latest git master, specifically to new qht interface. * Merged the original 4 patches to this single

[Qemu-devel] [PATCH v2 2/4] 9P: trivial cleanup of QID path collision mitigation

Addresses trivial changes regarding the previous patch as requested on the mailing list a while ago. * Removed unneccessary parantheses: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg02661.html * Removed unneccessary g_malloc() result checks: https://lists.gnu.org/archive/html

[Qemu-devel] [PATCH v2 3/4] 9p: persistency of QID path beyond reboots / suspensions

, since in practice the qpf_table is really just tiny. Since there is currently no callback in qemu yet that would reliably be called on guest shutdowns, the table is stored on every new insertion for now. Signed-off-by: Christian Schoenebeck --- hw/9pfs/9p.c | 315

[Qemu-devel] [PATCH v2 4/4] 9p: use variable length suffixes for inode mapping

This patch introduces variable length suffixes for being used for inode mapping instead of the fixed 16 bit size prefixes of patch 1. With this patch the inode numbers on guest will typically be much smaller (e.g. around >2^1 .. >2^7 instead of >2^48 with patch 1). I preserved both solutions in th

[Qemu-devel] [PATCH v3 5/5] 9p: adds virtfs 'vii' device parameter

This patch adds an optional qemu device parameter "vii" (very important inode[s]), which accepts a colon separated list of pathes relative below the 9p export root, which shall be given the smallest inode suffix (and hence largest possible inode namespace on guest) according to the g

[Qemu-devel] [PATCH v3 2/5] 9P: trivial cleanup of QID path collision mitigation

Addresses trivial changes regarding the previous patch as requested on the mailing list a while ago. * Removed unneccessary parantheses: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg02661.html * Removed unneccessary g_malloc() result checks: https://lists.gnu.org/archive/html

[Qemu-devel] [PATCH v3 4/5] 9p: use variable length suffixes for inode mapping

This patch introduces variable length suffixes for being used for inode mapping instead of the fixed 16 bit size prefixes of patch 1. With this patch the inode numbers on guest will typically be much smaller (e.g. around >2^1 .. >2^7 instead of >2^48 with patch 1). I preserved both solutions in th

[Qemu-devel] [PATCH v3 1/5] 9p: mitigates most QID path collisions

This first patch here is an updated version of Antonios Motakis' original 4-patch set (using fixed length 16 bit prefixes), merged to one patch: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg02283.html * Updated to latest git master, specifically to new qht interface. * Merge

[Qemu-devel] [PATCH v3 3/5] 9p: persistency of QID path beyond reboots / suspensions

, since in practice the qpf_table is really just tiny. Since there is currently no callback in qemu yet that would reliably be called on guest shutdowns, the table is stored on every new insertion for now. Signed-off-by: Christian Schoenebeck --- hw/9pfs/9p.c | 315

[Qemu-devel] [PATCH v3 0/5] 9p: Fix file ID collisions

ional qemu virtfs device parameter "vii" (very important inode[s]) , which allows host admins to configure which fs device(s) should get the largest inode namespaces on guest. I will also send a (6th) patch against libvirt which allows to configure the "vii" feature of patch 5

[Qemu-devel] [libvirt patch] qemu: adds support for virtfs 9p argument 'vii'

might then look like this: ... ... Like with the vii qemu virtfs command line argument, the order of the "important" tag defines which one gets the highest inode namespace (smallest generated suffix) on guest s

Re: [Qemu-devel] [libvirt patch] qemu: adds support for virtfs 9p argument 'vii'

commenting mostly on v2 of the patch set, where my email client replaced the message IDs and hence screwed threading. This is v3 that I sent yesterday and which has correct threading: https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg01143.html Please just have a glimpse on that v3 thread,

Re: [Qemu-devel] [PATCH v3 1/5] 9p: mitigates most QID path collisions

On Dienstag, 7. Mai 2019 13:42:47 CEST Daniel P. Berrangé wrote: > > This first patch here is an updated version of Antonios Motakis' > > original 4-patch set (using fixed length 16 bit prefixes), merged to one > > patch: > > > > https://lists.gnu.org/archive/ht

Re: [Qemu-devel] [libvirt patch] qemu: adds support for virtfs 9p argument 'vii'

On Dienstag, 7. Mai 2019 13:57:56 CEST Daniel P. Berrangé wrote: > > ... > > > > > > > > > > > > > > > > > > > > > > > >

Re: [Qemu-devel] [libvirt patch] qemu: adds support for virtfs 9p argument 'vii'

hat I sent yesterday and which has correct threading: > > https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg01143.html > > For a reason yet to be investigated, I haven't received it yet... Here are the archive links for latest v3 patch set [5(+1) patches total]: [

Re: [Qemu-devel] [PATCH v7 4/6] dax: check synchronous mapping is supported

From: Pankaj Gupta Date: Thu, Apr 25, 2019 at 10:00 PM > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma, > + struct dax_device *dax_dev) > +{ > + return !(vma->flags & VM_SYNC); > +} Shouldn't it be rather `return !(vma->vm_flags & VM_

Re: [Qemu-devel] [PATCH v7 2/6] virtio-pmem: Add virtio pmem driver

On 4/25/19 10:00 PM, Pankaj Gupta wrote: > +void host_ack(struct virtqueue *vq) > +{ > + unsigned int len; > + unsigned long flags; > + struct virtio_pmem_request *req, *req_buf; > + struct virtio_pmem *vpmem = vq->vdev->priv; > + > + spin_lock_irqsave(&vpmem->pmem_lock, flags)

[Qemu-devel] [Bug 1828207] [NEW] Request to add something like "Auth failed from IP" log report for built-in VNC server

and in combination with weak built-in VNC-auth scheme can be a security vulnerability. Adding a simple log record like "QEMU VNC Authentication failed 192.168.0.5:5902 - 123.45.67.89:7898" will permit to quickly integrate it to fail2ban system. ** Affects: qemu Importance:

Re: [Qemu-devel] [PATCH v7 2/6] virtio-pmem: Add virtio pmem driver

On 5/8/19 4:12 AM, Pankaj Gupta wrote: > >> >> On 4/25/19 10:00 PM, Pankaj Gupta wrote: >> >>> +void host_ack(struct virtqueue *vq) >>> +{ >>> + unsigned int len; >>> + unsigned long flags; >>> + struct virtio_pmem_request *req, *req_buf; >>> + struct virtio_pmem *vpmem = vq->vdev->priv; >

Re: [Qemu-devel] [PATCH 0/2] ui/cocoa: Fix input device issues on Mojave

Thank you and best regards. > On Jun 12, 2019, at 6:39 PM, Peter Maydell wrote: > > On Tue, 4 Jun 2019 at 10:34, Chen Zhang wrote: >> >> The following patches fixed issues of absolute and relative input devices >> on macOS Mojave. >> >> Chen Zhang (2): >> ui/cocoa: Fix absolute input device

[Qemu-devel] [PATCH] ui/cocoa: Adding cursor support

coordinates of the QEMU screen, not the NSScreen or the NSView, for convenience of blending. Signed-off-by: Chen Zhang --- ui/cocoa.m | 79 ++ 1 file changed, 79 insertions(+) diff --git a/ui/cocoa.m b/ui/cocoa.m index 420b2411c1..8beed6e514 100644

Re: [Qemu-devel] [PATCH] ui/cocoa: Adding cursor support

Hi, I did try to utilize NSCursor and CGWarpMouseCursorPosition API before this compromise. In cocoa_mouse_set, the position of cursor should to be modified, but the bottom half that called it was not scheduled on main thread. UI operations have to be queued on main thread asynchronously therea

Re: [Qemu-devel] [PATCH] ui/cocoa: Adding cursor support

Hi, I sympathize with your situation, but the things on macOS seems a little different. The QEMU Cocoa UI starts in the `main` thread and detach a `qemu_main` thread which runs stuff in vl.c etc. On the contrary, QEMU with gtk and other UIs just scheduled its event loop in the qemu_main

Re: [Qemu-devel] [PATCH] ui/cocoa: Adding cursor support

> On Mar 14, 2019, at 1:35 AM, BALATON Zoltan wrote: > > On Wed, 13 Mar 2019, Chen Zhang wrote: >> I sympathize with your situation, but the things on macOS seems a little >> different. >> >> The QEMU Cocoa UI starts in the `main` thread and detach a `qemu_

Re: [Qemu-devel] [PATCH 5/5] aspeed/timer: Use signed muldiv for timer resets

Thanks for the feedback, On Thu, Mar 14, 2019, 11:57 Peter Maydell wrote: > But overall I'm a little sceptical that the aspeed timer is > really a special case that needs a signed version of this > when no other timer in the system does... I agree, and the v2 of the patch doesn't require it. H

Re: [Qemu-devel] [PATCH 0/5] aspeed/timer: Fix slowdowns in recent Linux

9 9:59 AM, no-re...@patchew.org wrote: > > Patchew URL: > https://patchew.org/QEMU/20190314084235.9887-1-...@kaod.org/ > > > > > > > > Hi, > > > > This series failed the docker-mingw@fedora build test. Please find the > testing commands and > > th

Re: [Qemu-devel] [PATCH 5/5] aspeed/timer: Use signed muldiv for timer resets

Hi all, I have a new patch but I'm not sure how you want me to post it. Should I do a "PATCH v2" with a single patch and this thread as the thread ID? Thanks, - Chris On Thu, Mar 14, 2019 at 10:05 AM Cédric Le Goater wrote: > Christian, > > Could you please provide a fix for this patch ? patc

[Qemu-devel] [PATCH 0/2] ui/cocoa: Fix absolute input device grabbing issue on Mojave

On Mojave, absolute input device, i.e. tablet, had trouble re-grabbing the cursor in re-entry into the virtual screen area. In some cases, the `window` property of NSEvent object is nil, after exit of cursor, meaning that the `-locationInWindow` method would return value in screen coordinates. T

[Qemu-devel] [PATCH 1/2] Fix absolute input device grabbing issues on Mojave

Signed-off-by: Chen Zhang --- ui/cocoa.m | 29 + 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/ui/cocoa.m b/ui/cocoa.m index 420b2411c1..5d0a6599d9 100644 --- a/ui/cocoa.m +++ b/ui/cocoa.m @@ -405,6 +405,24 @@ QemuCocoaView *cocoaView; return (p

[Qemu-devel] [PATCH 2/2] ui/cocoa: fix grabbing issue in fullscreen mode

Signed-off-by: Chen Zhang --- ui/cocoa.m | 35 +++ 1 file changed, 27 insertions(+), 8 deletions(-) diff --git a/ui/cocoa.m b/ui/cocoa.m index 5d0a6599d9..8e74f6e283 100644 --- a/ui/cocoa.m +++ b/ui/cocoa.m @@ -410,11 +410,31 @@ QemuCocoaView *cocoaView; { N

[Qemu-devel] [PATCH] linux-user: Support gdb 'qOffsets' query for ELF

This is needed to support debugging PIE ELF binaries running under QEMU user mode. Currently, `code_offset` and `data_offset` remain unset for all ELF binaries, so GDB is unable to correctly locate the position of the binary's text and data. The fields `code_offset`, and `data_offset`

Re: [Qemu-devel] [PATCH] linux-user: Support gdb 'qOffsets' query for ELF

+cc: riku.voi...@iki.fi, I typoed the email on the first go. On Fri, Aug 16, 2019 at 4:34 PM Josh Kunz wrote: > This is needed to support debugging PIE ELF binaries running under QEMU > user mode. Currently, `code_offset` and `data_offset` remain unset for > all ELF binaries, so GDB

[Qemu-devel] [Bug 1772165] Re: arm raspi2/raspi3 emulation has no USB support

m/content/dam/www/programmable/us/en/pdfs/literature/hb/arria-10/a10_54018.pdf Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1772165 Title: arm raspi2/raspi3 emulation has no USB support Sta

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

is a link to the original thread this message is in reply to in-case my mail-client doesn't set up the reply properly: https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg01303.html Thanks, Josh Kunz

Re: [Qemu-devel] RFC raspberry pi sd-card reset

From: Damien Hedde Sent: Wednesday, July 31, 2019 7:21:02 AM To: QEMU Developers Cc: Peter Maydell ; Andrew Baumann ; f4...@amsat.org ; qemu-arm Subject: RFC raspberry pi sd-card reset Hi, Concerning the reset on the raspi2/3 machine, I ran into an issue with the sd-card

[Qemu-devel] [Bug 1838569] [NEW] virtio-balloon change breaks post 4.0 upgrade

Public bug reported: We upgraded the libvirt UCA packages from 3.6 to 4.0 as part of a queens upgrade and noticed that virtio-ballon is broken when instances live migrate (started with a prior 3.6 version) with: 2019-07-24T06:46:49.487109Z qemu-system-x86_64: warning: Unknown firmware file

[Qemu-devel] [Bug 1838569] Re: virtio-balloon change breaks post 4.0 upgrade

** Description changed: - We upgraded the libvirt UCA packages from 3.6 to 4.0 as part of a queens upgrade and noticed that + We upgraded the libvirt UCA packages from 3.6 to 4.0 and qemu 2.10 to 2.11 as part of a queens upgrade and noticed that virtio-ballon is broken when instances live

Re: [Qemu-devel] [PATCH v9 04/17] block/io_uring: implements interfaces for io_uring

/* > + * Linux io_uring support. > + * > + * Copyright (C) 2009 IBM, Corp. > + * Copyright (C) 2009 Red Hat, Inc. > + * Copyright (C) 2019 Aarushi Mehta > + * > + * This work is licensed under the terms of the GNU GPL, version 2 or later. > + * See the COPYING file in the t

Re: [Qemu-devel] [PATCH v9 07/17] blockdev: adds bdrv_parse_aio to use io_uring

On Fri, Aug 2, 2019 at 1:41 AM Aarushi Mehta wrote: > +int bdrv_parse_aio(const char *mode, int *flags) > +{ > +if (!strcmp(mode, "threads")) { > +/* do nothing, default */ > +} else if (!strcmp(mode, "native")) { > +*flags |= BDRV_O_NATIVE_AIO; This 'if' should be covered

Re: [Qemu-devel] [PATCH v9 07/17] blockdev: adds bdrv_parse_aio to use io_uring

On Wed, Aug 7, 2019 at 2:06 PM Aarushi Mehta wrote: > > > > On Wed, 7 Aug, 2019, 17:15 Julia Suvorova, wrote: >> >> On Fri, Aug 2, 2019 at 1:41 AM Aarushi Mehta wrote: >> > +int bdrv_parse_aio(const char *mode, int *flags) >> > +{ >> > +if (!strcmp(mode, "threads")) { >> > +/* do not

Re: [Qemu-devel] [PATCH] raspi: Add Raspberry Pi 1 support

Hi Omar, > From: Omar Rizwan [mailto:omar.riz...@gmail.com] > Sent: Friday, 7 April 2017 22:43 Did you do any testing of this? One of the reasons I never got around to upstreaming this was that I couldn't get Raspbian working reliably (there was some problem with stalled DMA reads from the MMC

[Qemu-devel] [Bug 1681439] [NEW] qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

Public bug reported: Since upgrading to QEMU 2.8.0, my Windows 7 64-bit virtual machines started crashing due to the assertion quoted in the summary failing. The assertion in question was added by commit 9972354856 ("block: add BDS field to count in-flight requests"). My tests show th

[Qemu-devel] [Bug 1681439] Re: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

8 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1681439 Title: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed. Status in QEMU

Re: [Qemu-devel] [PATCH] raspi: Add Raspberry Pi 1 support

> From: Omar Rizwan [mailto:omar.riz...@gmail.com] > Sent: Friday, 7 April 2017 23:13 > On Fri, Apr 7, 2017 at 10:57 PM Andrew Baumann > wrote: > > > From: Omar Rizwan [mailto:omar.riz...@gmail.com] > > > Sent: Friday, 7 April 2017 22:43 > > Did you do any testing of this? One of the reasons I ne

Re: [Qemu-devel] [PATCH] raspi: Add Raspberry Pi 1 support

; with the 0x4000 address. The code in my tree for bcm2835.c is: > > /* Peripheral base address seen by the CPU */ > #define BCM2835_PERI_BASE 0x2000 > ... > sysbus_mmio_map_overlap(SYS_BUS_DEVICE(&s->peripherals), 0, > BCM2835_PERI_BASE, 1)

[Qemu-devel] [Bug 1681439] Re: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

> I don't think the assert you are talking about in the subject is added > by 9972354856. That assertion was added by 86698a12f and has been > present since QEMU 2.6. I don't see the relation immediately to > AioContext patches. You are right, of course. Sorry for mis

Re: [Qemu-devel] [PATCH v6] kvm: better MWAIT emulation for guests

This might be more useful if it could be dynamically toggled on and off, depending on system load. On Tue, Apr 11, 2017 at 4:45 AM, Alexander Graf wrote: > From: "Michael S. Tsirkin" > > Guests that are heavy on futexes end up IPI'ing each other a lot. That > can lead to significant slowdowns an

[Qemu-devel] [Bug 1681439] Re: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

> > ide_cancel_dma_sync() is also invoked from bmdma_cmd_writeb() and this > > is in fact the code path taken when the assertion fails. > > > > Yep, I wonder why your guest is trying to cancel DMA, though? Something > else is probably going wrong first. Beats me. &g

Re: [Qemu-devel] [PATCH v6] kvm: better MWAIT emulation for guests

Actually, we have rejected commit 87c00572ba05aa8c ("kvm: x86: emulate monitor and mwait instructions as nop"), so when we intercept MONITOR/MWAIT, we synthesize #UD. Perhaps it is this difference from vanilla kvm that motivates the following idea... Since we're still not going to report MONITOR s

Re: [Qemu-devel] [PATCH v6] kvm: better MWAIT emulation for guests

On Wed, Apr 12, 2017 at 7:54 AM, Alexander Graf wrote: > > > On 12.04.17 16:34, Jim Mattson wrote: >> >> Actually, we have rejected commit 87c00572ba05aa8c ("kvm: x86: emulate >> monitor and mwait instructions as nop"), so when we intercept >> MONITOR/MWAIT, we synthesize #UD. Perhaps it is this d

Re: [Qemu-devel] [PULL 02/15] docs: VM Generation ID device description

that could be mapped > with > + caching disabled. (In other words, regardless of whether the generation > ID > + lives in RAM, ROM or MMIO, it shall only be mapped as cacheable.) > + > +R2 to R5. [These AML requirements are isolated well enough in the Microsoft

Re: [Qemu-devel] [PULL 02/15] docs: VM Generation ID device description

gmail.com>> wrote: >> >> +Device Usage: >> +- >> + >> +The device has one property, which may be only be set using the command >> line: >> + >> + guid - sets the value of the GUID. A special value "auto" instructs >> + QEMU t

Re: [Qemu-devel] [PULL 02/15] docs: VM Generation ID device description

vice Usage: >>> +- >>> + >>> +The device has one property, which may be only be set using the command >>> line: >>> + >>> + guid - sets the value of the GUID. A special value "auto" instructs >>> + QEMU to

[Qemu-devel] [Bug 1681439] Re: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

> Let's try and see if this doesn't fix your problem: > https://github.com/jnsnow/qemu/commit/57bf2ccdfe8dd35838c1e6642bf9bd76dc9ad1a9 Sadly, no, it still crashes. Same assertion, same canceled command, same time to reproduce. -- You received this bug notification because you

[Qemu-devel] [Bug 986318] Re: [sdl] Mouse grab breaks GNOME 3 screensaver unlock screen

On current versions (QEMU 2.8, GNOME-Shell 3.22.3 on Wayland), the screensaver will activate. Cursor control is given to the lock screen, everything works properly. After the screen is unlocked, the cursor is given back to QEMU and is still in "mouse grab" mode. ** Changed in: qemu

Re: [Qemu-devel] [PATCH v8 7/8] tests: Add unit tests for the VM Generation ID feature

Hi, > On Apr 21, 2017, at 3:14 AM, Marc-André Lureau > wrote: > > Hi, > > Was this patch intentionally dropped from the series? > Good question. I thought the whole patch series was pulled in, but it looks like this one was not. I guess we’ll see what Michael has to say. —Ben > > > --

Re: [Qemu-devel] [PATCH] tests: Add unit tests for the VM Generation ID feature

> On Jun 1, 2017, at 7:21 AM, Michael S. Tsirkin wrote: > > On Thu, Jun 01, 2017 at 08:10:27AM +, Marc-André Lureau wrote: >> Hi >> >> On Mon, May 29, 2017 at 7:18 PM Ben Warren via Qemu-devel < >> qemu-devel@nongnu.org> wrote: >> >>

Re: [Qemu-devel] [PATCH] tests: Add unit tests for the VM Generation ID feature

u wrote: >>>> Hi >>>> >>>> On Mon, May 29, 2017 at 7:18 PM Ben Warren via Qemu-devel < >>>> qemu-devel@nongnu.org> wrote: >>>> >>>> From: Ben Warren >>>> >>>> The following tests are implemen

Re: [Qemu-devel] Dummy Panel.

| | | | || | | | || demo may 4 QEMU Emulating a Raspberry PI 2 running the QEMU IO demo from Circle low level system. Using GDummyPanel to inte... | | | |  John BradleyTel: 07896 839635Skype: flypie125 125B Grove StreetEdge Hill Liverpool L7 7AF On

[Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling

I had two problems with QEMU on macOS: 1) Sometimes when alt-tabbing to QEMU it would act as if the 'a' key was pressed so I'd get 'a'. 2) Using Sikuli to programatically send keys to the QEMU window text like "foo_bar" would come out as &

[Qemu-devel] Error Msg on list.

Is this just me. I got the following message from 2 different SMTP servers. Google & Yahoo when sending via GIT mail. Mail to myself worked. Your message wasn't delivered to qemu-devel@nongnu.org because the address couldn't be found. Check for typos or unnecessary spaces and t

[Qemu-devel] Changes to Broadcom(BCM) files and Raspberry Pi files. Addition of PanelEmu

/hw/timer/bcm2835_timer.h | 32 + include/hw/usb/bcm2835_usb.h | 78 +++ include/qemu/PanelEmu.h | 53 ++ util/Makefile.objs |1 + util/PanelEmu.c | 293 ++ 30 files changed, 3547 insertions(+), 149 deletions(-) create m

Re: [Qemu-devel] Changes to Broadcom(BCM) files and Raspberry Pi files. Addition of PanelEmu

, 2017 at 5:42 PM, John Bradley via Qemu-devel wrote: > From 7f74f048f135d9c9c230a9e90f72451c841c6d35 Mon Sep 17 00:00:00 2001 > From: John Bradley > Date: Sat, 13 May 2017 23:07:47 +0100 > Subject: [PATCH] Changes to Broadcom(BCM) files and Raspberry Pi files. > Addition of PanelEm

Re: [Qemu-devel] [Qemu-arm] Changes to Broadcom(BCM) files and Raspberry Pi files. Addition of PanelEmu

w files. I rebased your branch on latest qemu/master here: https://github.com/philmd/qemu/tree/flypie-GDummyPanel-rebased It is much easier to follow now, the big XML files you added/removed also disappeared (gitk was crashing 'Out Of Memory' trying to look at your tree). I ho

Re: [Qemu-devel] Changes to Broadcom(BCM) files and Raspberry Pi files. Addition of PanelEmu

"I think that should be #ifdef _WIN32. Maybe in the far future QEMU could also be compiled with Visual Studio or any other windows compiler" The reason for doing it this way is that MINGW64, which is the dev platform I uses on Windows10, does not include a port of the GNU Socket li

Re: [Qemu-devel] [Qemu-arm] Changes to Broadcom(BCM) files and Raspberry Pi files. Addition of PanelEmu

 John BradleyTel: 07896 839635Skype: flypie125 125B Grove StreetEdge Hill Liverpool L7 7AF On Tuesday, 16 May 2017, 9:56, Geert Martin Ijewski wrote: Am 16.05.2017 um 02:01 schrieb John Bradley via Qemu-devel: > Hi, > The XML files in the base are not in the patch. They where net bea

Re: [Qemu-devel] [PULL 19/21] tests: Add unit tests for the VM Generation ID feature

t; Hi -- this test seems to intermittently fail: > > TEST: tests/vmgenid-test... (pid=15466) > /i386/vmgenid/vmgenid/set-guid: ** > ERROR:/home/peter.maydell/qemu/tests/vmgenid-test.c:65:acpi_find_vgia: > assertion failed (ACPI_ASSERT_CMP > _str == &quo

Re: [Qemu-devel] [PULL 19/21] tests: Add unit tests for the VM Generation ID feature

7;s not aarch64-specific. I just hit this on >>>> a build on x86_64 host, gcc, debug build: >>>> >>>> GTESTER check-qtest-x86_64 >>>> ** >>>> ERROR:/home/petmay01/linaro/qemu-for-merges/tests/vmgenid-test.c:65:acpi_find_vgia:

Re: [Qemu-devel] [PULL 19/21] tests: Add unit tests for the VM Generation ID feature

Hi, > On Jul 13, 2017, at 4:51 AM, Marc-André Lureau > wrote: > > Hi > > On Thu, Jul 13, 2017 at 1:32 PM Laszlo Ersek > wrote: > On 07/13/17 12:47, Peter Maydell wrote: > > On 12 July 2017 at 00:43, Ben Warren > > wrote: > >> Yes, it’s

Re: [Qemu-devel] [PATCH v2] vmgenid-test: use boot-sector infrastructure

..a49de92 100644 > --- a/tests/vmgenid-test.c > +++ b/tests/vmgenid-test.c > @@ -15,6 +15,7 @@ > #include "qemu/bitmap.h" > #include "qemu/uuid.h" > #include "hw/acpi/acpi-defs.h" > +#include "boot-sector.h&qu

[Qemu-devel] Disable image locking for snapshot drive?

Hi all, I'm running a recent Linux build of qemu on Windows Subsystem for Linux (WSL) which doesn't appear to implement file locking: $ qemu-system-aarch64 ... -drive file=test.vhdx,if=none,id=hd0 -device virtio-blk-pci,drive=hd0 qemu-system-aarch64: -drive file=test.vhdx,if=n

Re: [Qemu-devel] Disable image locking for snapshot drive?

> From: John Snow [mailto:js...@redhat.com] > Sent: Monday, 17 July 2017 17:34 > On 07/17/2017 07:30 PM, Andrew Baumann via Qemu-devel wrote: > > Hi all, > > > > I'm running a recent Linux build of qemu on Windows Subsystem for Linux > (WSL) which doesn

Re: [Qemu-devel] [PATCH 1/7] vmgenid: replace x-write-pointer-available hack

he additional benefit of handling other cases properly, like: > > $ qemu-system-x86_64 -device vmgenid -machine none > qemu-system-x86_64: -device vmgenid: vmgenid requires DMA write support in > fw_cfg, which this machine type does not provide > $ qemu-system-x86_64 -device

[Qemu-devel] [PATCH v2] tests: Add unit tests for the VM Generation ID feature

2017 Skyport Systems + * + * This work is licensed under the terms of the GNU GPL, version 2 or later. + * See the COPYING file in the top-level directory. + */ + +#include +#include +#include +#include "qemu/osdep.h" +#include "qemu/bitmap.h" +#include "qemu/uuid.h&q

[Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.

the GNU GPLv2 and later. + */ + +#include "qemu/osdep.h" +#include "cpu.h" +#include "hw/arm/bcm2835.h" +#include "hw/arm/raspi_platform.h" +#include "hw/sysbus.h" +#include "exec/address-spaces.h" + + +/* Peripheral base address seen by t

Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.

StreetEdge Hill Liverpool L7 7AF On Wednesday, 17 May 2017, 19:27, Eric Blake wrote: On 05/17/2017 01:09 PM, John Bradley via Qemu-devel wrote: > Also available at > > https://www.dropbox.com/s/gwuquw0kirstw7a/0001-Add-Markus-Armbrusters-code-for-Broadcom-Perhiperals.patch?dl=0 Thi

Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.

Andrew Baumann has and others have release the code under GNU General Public License version 2 (GPLv2), the same as QEMU that allows me to added it to QEMU as it is under the same license, by signing it off this is what I am certifying.  John BradleyTel: 07896 839635Skype: flypie125 125B Grove

[Qemu-devel] [PATCH] Add BCM2835 devices to Arm hardware.

(c) 2013 Jan Petrous + * + * Rasperry Pi 2 emulation and refactoring Copyright (c) 2015, Microsoft + * Written by Andrew Baumann + * + * This code is licensed under the GNU GPLv2 and later. + */ + +#include "qemu/osdep.h" +#include "cpu.h" +#include "hw/arm/bcm2835.h" +

Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.

Public > License version 2 (GPLv2), the same as QEMU that allows me to added it to > QEMU as it is under the same license, by signing it off this is what I am > certifying. See this document linked from the SubmitAPatch link (it describes the kernel meaning of S-o-b tags, although

Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.

cceed, as far as I >> can tell , in matching you standards, to such an extent that I am happy that > > You are correct that the GPL gives us legal rights to use Andrew's code > without his permission.  And yes, YOU can fork qemu, and take whatever > GPL patches you want witho

[Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling

I had two problems with QEMU on macOS: 1) Sometimes when alt-tabbing to QEMU it would act as if the 'a' key was pressed so I'd get 'a'. 2) Using Sikuli to programatically send keys to the QEMU window text like "foo_bar" would come out as &

[Qemu-devel] [PATCH] [PATCH V2] GDummyPanel Fix formatingissues.

nel The code uses GNU Sockets & Windows sockets as on MINGW GNU no available. This is inteded as a Demo for RFC. Signed-off-by: John Bradley --- hw/gpio/bcm2835_gpio.c | 316 ++- include/hw/gpio/bcm2835_gpio.h | 4 + include/qemu/PanelEmu.h

[Qemu-devel] [PATCH] Add code to connect to external panel, for ARM

| 104 + hw/gpio/bcm2835_gpio.c | 136 +++-- include/hw/gpio/bcm2835_gpio.h | 4 + include/qemu/PanelEmu.h| 53 +++ util/PanelEmu.c| 326 + 6 files changed, 583 insertions(+), 42 deletions(-) crea

[Qemu-devel] [PATCH V2] Add code to connect to external panel, for ARM

hw/gpio/bcm2835_gpio.h | 4 + include/qemu/PanelEmu.h| 53 +++ util/Makefile.objs | 1 + util/PanelEmu.c| 326 + 5 files changed, 479 insertions(+), 41 deletions(-) create mode 100644 include/qemu/PanelEmu.h create mode

Re: [Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling

On Tue, May 23, 2017 at 3:03 AM Gerd Hoffmann wrote: > Sounds like this happens in case there is a modifier state change > without linked key event, such as state change while qemu did not have > the keyboard focus. Nice that macos sends notifications in that case. > Yeah, I gu

Re: [Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling

On Tue, May 23, 2017 at 8:52 AM Ian McKellar wrote: > On Tue, May 23, 2017 at 3:03 AM Gerd Hoffmann wrote: > >> >> I'm wondering whenever we should just use modifierFlags all the time. >> > > Probably. My initial patch tried to be minimally intrusive but I can try > reworking the NSEventTypeFlag

Re: [Qemu-devel] ssi_auto_connect_slave

+qemu-dev Show original message On Monday, May 22, 2017 6:34 PM, boddu pavan wrote: Hi, I see that ssi_auto_connect_slave helper of ssi.c (https://github.com/qemu/qemu/blob/master/hw/ssi/ssi.c#L166) is used to connect SSISlave children of spi controller to its respective spi bus

[Qemu-devel] [PATCH] Improve Cocoa modifier key handling

I had two problems with QEMU on macOS: 1) Sometimes when alt-tabbing to QEMU it would act as if the 'a' key was pressed so I'd get 'a'. 2) Using Sikuli to programatically send keys to the QEMU window text like "foo_bar" would come out as &

Re: [Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling

Sent another patch that does a better job of toggling caps-lock. I couldn't make it fail with the old patch but I think the new patch is somewhat better. Ian On Tue, May 23, 2017 at 11:17 PM Gerd Hoffmann wrote: > Hi, > > > After a little more experimentation I think that the approach in this

<    2   3   4   5   6   7   8   9   10   11   >