Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 4/6] Categorize devices: i82374

On 27/03/2019 14.34, Ernest Esene wrote: > Set category and describe the i82374 device > > Signed-off-by: Ernest Esene > > --- > v2: > * split into separate patches > --- > hw/dma/i82374.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/hw/dma/i82374.c b/hw/dma/i82374.c > index 89

[Qemu-devel] [PATCH] Revert "audio: fix pc speaker init"

This reverts commit bd56d378842c238c8901536c06c20a4a51ee9761. Turned out it isn't that simple as the device needs the pit object link. So "-device isa-pcspk" isn't going wo work anyway. We are in freeze, so just reverting the thing is the best way to handle this for now, trying to come up with so

Re: [Qemu-devel] [PATCH] block/file-posix: ignore fail on unlock bytes

27.03.2019 15:49, Vladimir Sementsov-Ogievskiy wrote: > bdrv_replace_child() calls bdrv_check_perm() with error_abort on > loosening permissions. However file-locking operations may fail even > in this case, for example on NFS. And this leads to Qemu crash. > > Let's ignore such errors, as we do a

[Qemu-devel] [PATCH v2] block/file-posix: ignore fail on unlock bytes

bdrv_replace_child() calls bdrv_check_perm() with error_abort on loosening permissions. However file-locking operations may fail even in this case, for example on NFS. And this leads to Qemu crash. Let's ignore such errors, as we do already on permission update commit and abort. Signed-off-by: Vl

Re: [Qemu-devel] [qemu-s390x] [PATCH v5 13/15] s390-bios: Use control unit type to determine boot method

On 13/03/2019 17.31, Jason J. Herne wrote: > The boot method is different depending on which device type we are > booting from. Let's examine the control unit type to determine if we're > a virtio device. We'll eventually add a case to check for a real dasd device > here as well. > > Since we have

Re: [Qemu-devel] [qemu-s390x] [PATCH v5 14/15] s390-bios: Add channel command codes/structs needed for dasd-ipl

On 13/03/2019 17.31, Jason J. Herne wrote: > The dasd IPL procedure needs to execute a few previously unused > channel commands. Let's define them and their associated data > structures. > > Signed-off-by: Jason J. Herne > Acked-by: Cornelia Huck > --- > pc-bios/s390-ccw/cio.h | 23

Re: [Qemu-devel] [PATCH v2 1/3] iotests: Add 241 to test NBD on unaligned images

28.03.2019 1:39, Eric Blake wrote: > Add a test for the NBD client workaround in the previous patch. It's > not really feasible for an iotest to assume a specific tracing engine, > so we can't really probe for the new > trace_nbd_parse_blockstatus_compliance to see if the server was fixed > vs. wh

Re: [Qemu-devel] [PATCH 0/5] QEMU VFIO live migration

hi Alex and Dave, Thanks for your replies. Please see my comments inline. On Thu, Mar 28, 2019 at 06:10:20AM +0800, Alex Williamson wrote: > On Wed, 27 Mar 2019 20:18:54 + > "Dr. David Alan Gilbert" wrote: > > > * Zhao Yan (yan.y.z...@intel.com) wrote: > > > On Wed, Feb 20, 2019 at 07:42:42P

Re: [Qemu-devel] [qemu-s390x] [PATCH for-4.0?] exec: Only count mapped memory backends for qemu_getrampagesize()

On 28.03.19 01:27, David Gibson wrote: > On Wed, Mar 27, 2019 at 02:19:41PM +0100, David Hildenbrand wrote: >> On 27.03.19 10:03, David Gibson wrote: >>> On Wed, Mar 27, 2019 at 09:10:01AM +0100, David Hildenbrand wrote: On 27.03.19 01:12, David Gibson wrote: > On Tue, Mar 26, 2019 at 06:0

Re: [Qemu-devel] [PATCH] Revert "audio: fix pc speaker init"

Le jeu. 28 mars 2019 08:12, Gerd Hoffmann a écrit : > This reverts commit bd56d378842c238c8901536c06c20a4a51ee9761. > > Turned out it isn't that simple as the device needs the pit object link. > So "-device isa-pcspk" isn't going wo work anyway. We are in freeze, so > just reverting the thing is

Re: [Qemu-devel] [PATCH v2 3/3] nbd/server: Advertise actual minimum block size

28.03.2019 1:39, Eric Blake wrote: > Both NBD_CMD_BLOCK_STATUS and structured NBD_CMD_READ will split their > reply according to bdrv_block_status() boundaries. If the block device > has a request_alignment smaller than 512, but we advertise a block > alignment of 512 to the client, then this can r

Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 4/6] Categorize devices: i82374

Le jeu. 28 mars 2019 08:10, Thomas Huth a écrit : > On 27/03/2019 14.34, Ernest Esene wrote: > > Set category and describe the i82374 device > > > > Signed-off-by: Ernest Esene > > > > --- > > v2: > > * split into separate patches > > --- > > hw/dma/i82374.c | 2 ++ > > 1 file changed, 2 inse

Re: [Qemu-devel] [PATCH 2/2] accel: Unbreak accelerator fallback

Le mer. 27 mars 2019 16:09, Markus Armbruster a écrit : > When the user specifies a list of accelerators, we pick the first one > that initializes successfully. Recent commit 1a3ec8c1564 broke that. > Reproducer: > > $ qemu-system-x86_64 --machine accel=xen:tcg > xencall: error: Could no

Re: [Qemu-devel] [PULL] target/xtensa fixes for v4.0

On Tue, 26 Mar 2019 at 18:03, Max Filippov wrote: > > Hi Peter, > > please pull the following batch of target/xtensa fixes for v4.0. > > The following changes since commit 62a172e6a77d9072bb1a18f295ce0fcf4b90a4f2: > > Update version for v4.0.0-rc0 release (2019-03-19 17:17:22 +) > > are avai

Re: [Qemu-devel] [PATCH for-4.0?] nbd/client: Deal with unaligned size from server

28.03.2019 5:02, Eric Blake wrote: > When a server advertises an unaligned size but no block sizes, the > code was rounding up to a sector-aligned size (a known limitation of > bdrv_getlength(); maybe 4.1 will fix it to be byte-accurate), then > assuming a request_alignment of 512 (the recommendati

Re: [Qemu-devel] [qemu-s390x] [PATCH for-4.0?] exec: Only count mapped memory backends for qemu_getrampagesize()

On 28.03.19 02:18, David Gibson wrote: > On Wed, Mar 27, 2019 at 03:22:58PM +0100, David Hildenbrand wrote: >> On 27.03.19 10:03, David Gibson wrote: >>> On Wed, Mar 27, 2019 at 09:10:01AM +0100, David Hildenbrand wrote: On 27.03.19 01:12, David Gibson wrote: > On Tue, Mar 26, 2019 at 06:0

Re: [Qemu-devel] [PATCH 0/5] QEMU VFIO live migration

On Thu, Mar 28, 2019 at 04:36:03AM -0400, Zhao Yan wrote: > hi Alex and Dave, > Thanks for your replies. > Please see my comments inline. > > On Thu, Mar 28, 2019 at 06:10:20AM +0800, Alex Williamson wrote: > > On Wed, 27 Mar 2019 20:18:54 + > > "Dr. David Alan Gilbert" wrote: > > > > > * Zhao

Re: [Qemu-devel] [PATCH 2/2 v2] usb-mtp: refactor the flow of usb_mtp_write_data

On Tue, 26 Mar 2019 at 17:58, Bandan Das wrote: > > There's no functional change but the flow is (hopefully) > more consistent for both file and folder object types. > > Signed-off-by: Bandan Das > --- > hw/usb/dev-mtp.c | 53 > 1 file changed, 26

Re: [Qemu-devel] About making QEMU to LIBs!

On Thu, Mar 28, 2019 at 02:45:37PM +0800, Xiao Guangrong wrote: > On 3/27/19 5:41 PM, Stefano Garzarella wrote: > > Hi Yang, Xiao, > > Just adding few things, because I'm currently exploring the QEMU modules > > in order to reduce the boot time and the footprint. > > > > Hi Stefan Hajnoczi and St

[Qemu-devel] [Bug 1818207] Re: [aarch64] VM status remains "running" after it's suspended

In order for the guest kernel to expose ACPI S3 suspend to a privileged guest user, the guest kernel first checks if the platform (hardware and firmware) support ACPI S3. This in turn depends on whether the DSDT offers a package called _S3. For example, on the "pc" machine type, S3 can be disabled

Re: [Qemu-devel] [PATCH for-4.0 1/3] block: continue until base is found in bdrv_freeze_backing_chain() et al

26.03.2019 20:07, Alberto Garcia wrote: > All three functions that handle the BdrvChild.frozen attribute walk > the backing chain from 'bs' to 'base' and stop either when 'base' is > found or at the end of the chain if 'base' is NULL. > > However if 'base' is not found then the functions return wi

[Qemu-devel] [PATCH] spapr/irq: Add XIVE sanity checks on non-P9 machines

On non-P9 machines, the XIVE interrupt mode is not advertised, see spapr_dt_ov5_platform_support(). Add a couple of checks on the machine configuration to filter bogus setups and prevent OS failures : Interrupt modes CPU/Compat XICSXIVEdual P8/P

Re: [Qemu-devel] [PATCH for-4.0 2/3] block: freeze the backing chain earlier in stream_start()

26.03.2019 20:07, Alberto Garcia wrote: > Commit 6585493369819a48d34a86d57ec6b97cb5cd9bc0 added code to freeze > the backing chain from 'top' to 'base' for the duration of the > block-stream job. > > The problem is that the freezing happens too late in stream_start(): > during the bdrv_reopen_set_

Re: [Qemu-devel] [PATCH for-4.0?] exec: Only count mapped memory backends for qemu_getrampagesize()

On 26.03.19 04:50, David Gibson wrote: > qemu_getrampagesize() works out the minimum host page size backing any of > guest RAM. This is required in a few places, such as for POWER8 PAPR KVM > guests, because limitations of the hardware virtualization mean the guest > can't use pagesizes larger tha

Re: [Qemu-devel] [PATCH for-4.0] hw/arm/raspi: Diagnose requests for too much RAM

Le jeu. 28 mars 2019 10:57, Peter Maydell a écrit : > The Raspberry Pi boards have a physical memory map which does > not allow for more than 1GB of RAM. Currently if the user tries > to ask for more then we fail in a confusing way: > > $ qemu-system-aarch64 --machine raspi3 -m 8G > Unexpected er

[Qemu-devel] [PATCH for-4.0] hw/arm/raspi: Diagnose requests for too much RAM

The Raspberry Pi boards have a physical memory map which does not allow for more than 1GB of RAM. Currently if the user tries to ask for more then we fail in a confusing way: $ qemu-system-aarch64 --machine raspi3 -m 8G Unexpected error in visit_type_uintN() at qapi/qapi-visit-core.c:164: qemu-sys

Re: [Qemu-devel] [PATCH for-4.0] spapr: Simplify handling of host-serial and host-model values

On Thu, Mar 28, 2019 at 03:40:25PM +1100, David Gibson wrote: > 27461d69a0f "ppc: add host-serial and host-model machine attributes > (CVE-2019-8934)" introduced 'host-serial' and 'host-model' machine > properties for spapr to explicitly control the values advertised to the > guest in device tree p

Re: [Qemu-devel] [PATCH for-4.0 1/3] block: continue until base is found in bdrv_freeze_backing_chain() et al

On Thu 28 Mar 2019 10:45:51 AM CET, Vladimir Sementsov-Ogievskiy wrote: >> -for (i = bs; i != base && i->backing; i = backing_bs(i)) { >> -if (i->backing->frozen) { >> +for (i = bs; i != base; i = backing_bs(i)) { >> +if (i->backing && i->backing->frozen) { > > may be a bit

Re: [Qemu-devel] [PATCH for-4.0 1/3] block: continue until base is found in bdrv_freeze_backing_chain() et al

28.03.2019 13:04, Alberto Garcia wrote: > On Thu 28 Mar 2019 10:45:51 AM CET, Vladimir Sementsov-Ogievskiy wrote: >>> -for (i = bs; i != base && i->backing; i = backing_bs(i)) { >>> -if (i->backing->frozen) { >>> +for (i = bs; i != base; i = backing_bs(i)) { >>> +if (i->back

Re: [Qemu-devel] [PATCH for-4.0 3/3] block: test block-stream with a base node that is used by block-commit

26.03.2019 20:07, Alberto Garcia wrote: > The base node of a block-stream operation indicates the first image > from the backing chain starting from which no data is copied to the > top node. > > The block-stream job allows others to use that base image, so a second > block-stream job could be wri

Re: [Qemu-devel] [PATCH v1] s390x/kvm: Configure page size after memory has actually been initialized

On 28.03.19 01:24, David Gibson wrote: > On Wed, Mar 27, 2019 at 09:06:53PM +0100, David Hildenbrand wrote: >> On 27.03.19 17:45, Igor Mammedov wrote: >>> On Wed, 27 Mar 2019 14:59:44 +0100 >>> David Hildenbrand wrote: >>> Right now we configure the pagesize quite early, when initializing KVM

Re: [Qemu-devel] [PATCH for-4.0 1/3] block: continue until base is found in bdrv_freeze_backing_chain() et al

26.03.2019 20:07, Alberto Garcia wrote: > All three functions that handle the BdrvChild.frozen attribute walk > the backing chain from 'bs' to 'base' and stop either when 'base' is > found or at the end of the chain if 'base' is NULL. > > However if 'base' is not found then the functions return wi

Re: [Qemu-devel] [PATCH v7 6/6] migration: Block migration while handling machine check

On Thu, Mar 28, 2019 at 12:09:05PM +0530, Aravinda Prasad wrote: > > > On Thursday 28 March 2019 06:18 AM, David Gibson wrote: > > On Tue, Mar 26, 2019 at 12:22:50PM +0530, Aravinda Prasad wrote: > >> > >> > >> On Tuesday 26 March 2019 09:49 AM, David Gibson wrote: > >>> On Mon, Mar 25, 2019 at 0

Re: [Qemu-devel] [PATCH for-4.0 1/3] block: continue until base is found in bdrv_freeze_backing_chain() et al

28.03.2019 13:27, Vladimir Sementsov-Ogievskiy wrote: > 26.03.2019 20:07, Alberto Garcia wrote: >> All three functions that handle the BdrvChild.frozen attribute walk >> the backing chain from 'bs' to 'base' and stop either when 'base' is >> found or at the end of the chain if 'base' is NULL. >> >>

[Qemu-devel] [Bug 1794187] Re: improve error message, when using raspi3 and RAM>4G

I've submitted a patch to the list: http://patchwork.ozlabs.org/patch/1067963/ With it, QEMU will give this error instead: qemu-system-aarch64: Requested ram size is too large for this machine: maximum is 1GB (Note that the maximum is 1GB, not 4GB -- it's just that values between 1 and 4GB happe

Re: [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space

Hi Alex, [+ Robin] On 3/27/19 5:37 PM, Alex Williamson wrote: > On Wed, 27 Mar 2019 14:25:00 +0800 > Peter Xu wrote: > >> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote: >>> Conventional PCI buses pre-date requester IDs. An IOMMU cannot >>> distinguish by devfn & bus between d

[Qemu-devel] [PATCH RFC] block/gluster: limit the transfer size to 512 MiB

Several versions of GlusterFS (3.12? -> 6.0.1) fail when the transfer size is greater or equal to 1024 MiB, so we are limiting the transfer size to 512 MiB to avoid this rare issue. Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1691320 Signed-off-by: Stefano Garzarella --- RFC: Should I a

[Qemu-devel] [Bug 1813010] Re: Parallel builds fail (make -j >=2) when using --extra-cflags "--save-temps"

Hi; I'm going to close this bug because there's no way that QEMU's build process can handle being passed -save-temps via --extra-cflags, because this will cause GCC to use the same output files for multiple different source files, and they will clash. (Even with a non-parallel build, one compile is

[Qemu-devel] [PATCH 2/2] intel_iommu: Drop extended root field

VTD_RTADDR_RTT is dropped even by the VT-d spec, so QEMU should probably do the same thing (after all we never really implemented it). Since we've had a field for that in the migration stream, to keep compatibility we need to fill the hole up. Please refer to VT-d spec 10.4.6. Signed-off-by: Pete

[Qemu-devel] [PATCH 0/2] intel_iommu: misc scalable mode fixes for 4.0

The first patch is the important one. It should fix up a migration issue that Dave reported between 3.1<->4.0. The second patch is born only because I noticed it when drafting patch 1 and I think we can probably do that too together as a fixup to the scalable patchset for 4.0. Please have a look

[Qemu-devel] [Bug 1816052] Re: qemu system emulator fails to start if no sound card is present on host

This bug was fixed by commit 7183834a29fbaf422a6 which will be in 4.0. ** 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/1816052 Title: qemu sy

[Qemu-devel] [PATCH for-4.0] target/i386: Generate #UD for LOCK on a register increment

Fix a TCG crash due to attempting an atomic increment operation without having set up the address first. This is a similar case to that dealt with in commit e84fcd7f662a0d8198703, and we fix it in the same way. Fixes: https://bugs.launchpad.net/qemu/+bug/1807675 Signed-off-by: Peter Maydell ---

[Qemu-devel] [PATCH 1/2] intel_iommu: Fix root_scalable migration breakage

When introducing the initial support for scalable mode we added a new field into vmstate however we blindly migrate that field without notice. That'll break migration no matter forward or backward. The normal way should be that we use something like VMSTATE_UINT32_TEST() or subsections for the ne

[Qemu-devel] [Bug 1806243] Re: ARM conditional branch after if-then instruction not working

** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1806243 Title: ARM conditional branch after if-then instruction not working Status in QEMU: Inc

Re: [Qemu-devel] [PATCH for-4.1 v3 00/12] bundle edk2 platform firmware with QEMU

On 27/03/19 21:27, Philippe Mathieu-Daudé wrote: > > > Le mer. 27 mars 2019 17:06, Daniel P. Berrangé > a écrit : > > On Wed, Mar 27, 2019 at 04:58:23PM +0100, Paolo Bonzini wrote: > > On 27/03/19 16:30, Daniel P. Berrangé wrote: > > > Perhaps the VM test

Re: [Qemu-devel] [PATCH for-4.0] target/i386: Generate #UD for LOCK on a register increment

On 28/03/19 11:47, Peter Maydell wrote: > Fix a TCG crash due to attempting an atomic increment > operation without having set up the address first. > This is a similar case to that dealt with in commit > e84fcd7f662a0d8198703, and we fix it in the same way. > > Fixes: https://bugs.launchpad.net/q

[Qemu-devel] "qemu-img: File contains external, encrypted or compressed clusters."

This error message is confusing and looks wrong to me: $ ./nbdkit -U - data data="1" size=1M --run 'qemu-img map $nbd' Offset Length Mapped to File qemu-img: File contains external, encrypted or compressed clusters. With JSON output it's fine: $ ./nbdkit -U - data data="1

[Qemu-devel] [Bug 1807675] Re: qemu commit 80422b0: tcg.c crash in temp_load

I've sent patch https://patchwork.ozlabs.org/patch/1068003/ to the list which fixes this. (There might be other failures to check for bogus LOCK prefixes elsewhere, though.) ** Changed in: qemu Status: Confirmed => In Progress -- You received this bug notification because you are a membe

[Qemu-devel] [Bug 1721275] Re: Support more ARM CPUs

We now support Cortex-M0 (v6M) and Cortex-M33 (v8M mainline). We don't have Cortex-M7, Cortex-M23 (v8M baseline) or Cortex-A35. In general, adding an extra CPU to QEMU really requires us to have a decent use-case for it, probably including a board model for it, especially for the M-profile CPUs. T

[Qemu-devel] [Bug 1734792] Re: linux-user mode does not support memfd_create syscall

** Summary changed: - qemu-x86_64 fails with unsupported syscall 319 + linux-user mode does not support memfd_create syscall ** Changed in: qemu Status: New => Confirmed ** Tags added: linux-user -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1751422] Re: some instructions translate error in x86

Since Richard pointed out a commit which fixed this in 2.12 and we haven't heard back from the submitter, I'm going to close this bug as fixed. ** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subsc

[Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory

This is based on the patch [PATCH for-4.0?] exec: Only count mapped memory backends for qemu_getrampagesize() While the detection on s390x of the maximum ram pagesize works by pure luck, we should try to do better. Especially, once "-mem-path" is replaced by memory backends, the current ap

[Qemu-devel] [PATCH v2 2/2] exec: Introduce qemu_getmaxrampagesize() and rename qemu_getrampagesize()

Rename qemu_getrampagesize() to qemu_getminrampagesize(). While at it, properly rename find_min_supported_pagesize() to find_max_pagesize(). s390x is actually interrested into the maximum ram pagesize, so introduce and use qemu_getmaxrampagesize(). Signed-off-by: David Hildenbrand --- exec.c

[Qemu-devel] [Bug 1777777] Re: arm9 clock pending (SP804)

Mark this bug as Incomplete as we're still waiting for the test case binary and command line to reproduce it. ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpa

[Qemu-devel] [PATCH v2 1/2] s390x/kvm: Configure page size after memory has actually been initialized

Right now we configure the pagesize quite early, when initializing KVM. This is long before system memory is actually allocated via memory_region_allocate_system_memory(), and therefore memory backends marked as mapped. Instead, let's configure the maximum page size after initializing memory in s3

Re: [Qemu-devel] [PATCH v1] s390x/kvm: Configure page size after memory has actually been initialized

On Thu, 28 Mar 2019 11:18:02 +0100 David Hildenbrand wrote: > On 28.03.19 01:24, David Gibson wrote: > > On Wed, Mar 27, 2019 at 09:06:53PM +0100, David Hildenbrand wrote: > >> On 27.03.19 17:45, Igor Mammedov wrote: > >>> On Wed, 27 Mar 2019 14:59:44 +0100 > >>> David Hildenbrand wrote: > >

Re: [Qemu-devel] [Xen-devel] [PATCH v2 0/2] xen-block: fix sector size confusion

On Wed, Mar 27, 2019 at 08:32:28PM +, Paul Durrant wrote: > > -Original Message- > > From: Andrew Cooper > > Sent: 27 March 2019 18:20 > > To: Paul Durrant ; xen-de...@lists.xenproject.org; > > qemu-bl...@nongnu.org; > > qemu-devel@nongnu.org > > Cc: Kevin Wolf ; Stefano Stabellini >

Re: [Qemu-devel] [PATCH for-4.0?] nbd/client: Deal with unaligned size from server

Am 28.03.2019 um 03:02 hat Eric Blake geschrieben: > When a server advertises an unaligned size but no block sizes, the > code was rounding up to a sector-aligned size (a known limitation of > bdrv_getlength(); maybe 4.1 will fix it to be byte-accurate), then > assuming a request_alignment of 512 (

Re: [Qemu-devel] [Xen-devel] [PATCH v2 0/2] xen-block: fix sector size confusion

On 28/03/2019 11:40, Anthony PERARD wrote: > On Wed, Mar 27, 2019 at 08:32:28PM +, Paul Durrant wrote: >>> -Original Message- >>> From: Andrew Cooper >>> Sent: 27 March 2019 18:20 >>> To: Paul Durrant ; xen-de...@lists.xenproject.org; >>> qemu-bl...@nongnu.org; >>> qemu-devel@nongnu.or

[Qemu-devel] [Bug 1714750] Re: 2.10.0 cannot be installed on case-insensitive file system

We updated our u-boot sources to v2019.01 in QEMU commit f2a3b549e357041f86d7e, and we removed the scripts/make-release workaround in commit 082c0543baa6f23770, so all the loose ends I mentioned in comment #18 are now fixed and will be in QEMU 4.0. ** Changed in: qemu Status: New => Fix Co

Re: [Qemu-devel] [Qemu-block] [PATCH RFC] block/gluster: limit the transfer size to 512 MiB

On Thu, Mar 28, 2019 at 11:52:27AM +0100, Stefano Garzarella wrote: > Several versions of GlusterFS (3.12? -> 6.0.1) fail when the > transfer size is greater or equal to 1024 MiB, so we are > limiting the transfer size to 512 MiB to avoid this rare issue. > > Buglink: https://bugzilla.redhat.com/s

Re: [Qemu-devel] [Xen-devel] [PATCH v2 0/2] xen-block: fix sector size confusion

Am 28.03.2019 um 12:46 hat Andrew Cooper geschrieben: > On 28/03/2019 11:40, Anthony PERARD wrote: > > On Wed, Mar 27, 2019 at 08:32:28PM +, Paul Durrant wrote: > >>> -Original Message- > >>> From: Andrew Cooper > >>> Sent: 27 March 2019 18:20 > >>> To: Paul Durrant ; > >>> xen-de...@l

[Qemu-devel] [Bug 1681398] Re: hw/core: segmentation fault

This bug seems to have been fixed: we now report the command line issue with a more helpful message: $ qemu-system-i386 -S -machine isapc,accel=tcg -device amd-iommu qemu-system-i386: -device amd-iommu: Machine-type 'isapc' not supported by IOMMU This was in QEMU 3.1, so I'm closing this bug. *

Re: [Qemu-devel] [PATCH 2/2] intel_iommu: Drop extended root field

* Peter Xu (pet...@redhat.com) wrote: > VTD_RTADDR_RTT is dropped even by the VT-d spec, so QEMU should > probably do the same thing (after all we never really implemented it). > Since we've had a field for that in the migration stream, to keep > compatibility we need to fill the hole up. > > Plea

Re: [Qemu-devel] [PATCH RFC] block/gluster: limit the transfer size to 512 MiB

Am 28.03.2019 um 11:52 hat Stefano Garzarella geschrieben: > Several versions of GlusterFS (3.12? -> 6.0.1) fail when the > transfer size is greater or equal to 1024 MiB, so we are > limiting the transfer size to 512 MiB to avoid this rare issue. > > Buglink: https://bugzilla.redhat.com/show_bug.c

Re: [Qemu-devel] [PULL 00/23] Misc patches for QEMU 4.0-rc, mostly Kconfig refinements

On Wed, 27 Mar 2019 at 12:39, Paolo Bonzini wrote: > > The following changes since commit 9164add701788075f229b560bc3e92f6562ff857: > > Merge remote-tracking branch > 'remotes/stsquad/tags/pull-gitdm-next-120319-1' into staging (2019-03-14 > 13:48:48 +) > > are available in the git reposit

[Qemu-devel] [Bug 1659901] Re: Regression: SIGSEGV running Java

Hi -- I believe we fixed the Java crashes as part of work done for the 2.12 release (and perhaps 3.0, I forget). Does this still reproduce with the most recent release of QEMU (eg the 4.0 release candidate) ? -- You received this bug notification because you are a member of qemu- devel-ml, which

Re: [Qemu-devel] [PATCH for-4.0] qemu-img: Gracefully shutdown when map can't finish

Am 26.03.2019 um 19:40 hat Eric Blake geschrieben: > Trying 'qemu-img map -f raw nbd://localhost:10809' causes the > NBD server to output a scary message: > > qemu-nbd: Disconnect client, due to: Failed to read request: Unexpected > end-of-file before all bytes were read > > This is because the

Re: [Qemu-devel] [PATCH] iotests: Fix test 200 on s390x without virtio-pci

Am 27.03.2019 um 07:43 hat Thomas Huth geschrieben: > virtio-pci is optional on s390x, e.g. in downstream RHEL builds, it > is disabled. On s390x, virtio-ccw should be used instead. Other tests > like 051 or 240 already use virtio-scsi-ccw instead of virtio-scsi-pci > on s390x, so let's do the same

Re: [Qemu-devel] [PATCH for-4.0?] nbd/client: Deal with unaligned size from server

On 3/28/19 6:40 AM, Kevin Wolf wrote: >> Note that qemu as the server refuses to send an unaligned size, as it >> has already rounded the unaligned image up to sector size, and then >> happily resizes the image on access (at least when serving a POSIX >> file over NBD). But since third-party serve

Re: [Qemu-devel] [PULL 0/2] seccomp branch queue

On Wed, 27 Mar 2019 at 12:16, Eduardo Otubo wrote: > > The following changes since commit 49fc899f8d673dd9e73f3db0d9e9ea60b77c331b: > > Update version for v4.0.0-rc1 release (2019-03-26 17:02:29 +) > > are available in the Git repository at: > > https://github.com/otubo/qemu.git tags/pull-

Re: [Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory

Patchew URL: https://patchew.org/QEMU/20190328113458.8405-1-da...@redhat.com/ Hi, This series failed the docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN === #!/b

Re: [Qemu-devel] [PATCH for-4.0?] nbd/client: Deal with unaligned size from server

Am 28.03.2019 um 13:23 hat Eric Blake geschrieben: > On 3/28/19 6:40 AM, Kevin Wolf wrote: > > >> Note that qemu as the server refuses to send an unaligned size, as it > >> has already rounded the unaligned image up to sector size, and then > >> happily resizes the image on access (at least when s

Re: [Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory

Patchew URL: https://patchew.org/QEMU/20190328113458.8405-1-da...@redhat.com/ Hi, This series failed the asan build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN === #!/bin/bash time mak

Re: [Qemu-devel] "qemu-img: File contains external, encrypted or compressed clusters."

On 3/28/19 5:59 AM, Richard W.M. Jones wrote: > This error message is confusing and looks wrong to me: Confusing, but intentional design decision at the time (that said, I would also welcome an improvement). > > $ ./nbdkit -U - data data="1" size=1M --run 'qemu-img map $nbd' > Offset Le

Re: [Qemu-devel] [PATCH for-4.0] spapr: Simplify handling of host-serial and host-model values

On Thu, Mar 28, 2019 at 09:55:24AM +, Daniel P. Berrangé wrote: > On Thu, Mar 28, 2019 at 03:40:25PM +1100, David Gibson wrote: > > 27461d69a0f "ppc: add host-serial and host-model machine attributes > > (CVE-2019-8934)" introduced 'host-serial' and 'host-model' machine > > properties for spapr

Re: [Qemu-devel] [PATCH v2 0/2] block/vhdx: Use IEC binary prefixes from "qemu/units.h"

Am 27.03.2019 um 10:56 hat Stefano Garzarella geschrieben: > v2: > - Included units.h directly in the vhdx.h header file (John, Philippe) > - Added a comment next to DEFAULT_LOG_SIZE definition (Kevin) > - Added a second patch where I fixed some size constants using IEC > binary prefixes. > Not

Re: [Qemu-devel] [PATCH for-4.0?] nbd/client: Deal with unaligned size from server

On Thu, Mar 28, 2019 at 07:23:33AM -0500, Eric Blake wrote: > On 3/28/19 6:40 AM, Kevin Wolf wrote: > > >> Note that qemu as the server refuses to send an unaligned size, as it > >> has already rounded the unaligned image up to sector size, and then > >> happily resizes the image on access (at lea

Re: [Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory

On 28.03.19 13:38, no-re...@patchew.org wrote: > Patchew URL: https://patchew.org/QEMU/20190328113458.8405-1-da...@redhat.com/ > > > > Hi, > > This series failed the docker-mingw@fedora build test. Please find the > testing commands and > their output below. If you have Docker installed, you c

Re: [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space

Hi Robin, On 3/28/19 11:56 AM, Robin Murphy wrote: > On 28/03/2019 10:38, Auger Eric wrote: >> Hi Alex, >> >> [+ Robin] >> >> On 3/27/19 5:37 PM, Alex Williamson wrote: >>> On Wed, 27 Mar 2019 14:25:00 +0800 >>> Peter Xu wrote: >>> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wr

Re: [Qemu-devel] [PATCH for-4.0] spapr: Simplify handling of host-serial and host-model values

On Thu, 28 Mar 2019 15:40:25 +1100 David Gibson wrote: > 27461d69a0f "ppc: add host-serial and host-model machine attributes > (CVE-2019-8934)" introduced 'host-serial' and 'host-model' machine > properties for spapr to explicitly control the values advertised to the > guest in device tree proper

[Qemu-devel] [Bug 1652286] Re: man qemu 2.8.0

This still reproduces with current QEMU: $ man -l build/qemu.1 >/dev/null :248: warning [p 3, 6.8i, div `an-div', 0.2i]: can't break line :376: warning [p 5, 2.5i, div `an-div', 0.2i]: can't break line :667: warning [p 8, 9.7i, div `an-div', 0.2i]: can't break line (and so on for more warnings)

[Qemu-devel] [Bug 1806243] Re: ARM conditional branch after if-then instruction not working

Jesus... I'm sorry about the delay. Eclipse kept dying on me when launching gdb so I had to first set up another IDE since I really really didn't want to single-step through with the command line. Anyhow. The behavior of QEMU during debugging is now identical to the one when running it. Even with

Re: [Qemu-devel] [PATCH] spapr/irq: Add XIVE sanity checks on non-P9 machines

On Thu, 28 Mar 2019 11:00:44 +0100 Cédric Le Goater wrote: > On non-P9 machines, the XIVE interrupt mode is not advertised, see > spapr_dt_ov5_platform_support(). Add a couple of checks on the machine > configuration to filter bogus setups and prevent OS failures : > > Inter

Re: [Qemu-devel] [PULL 0/1] device-tree queue

On Wed, 27 Mar 2019 at 17:06, Alistair Francis wrote: > > The following changes since commit 49fc899f8d673dd9e73f3db0d9e9ea60b77c331b: > > Update version for v4.0.0-rc1 release (2019-03-26 17:02:29 +) > > are available in the Git repository at: > > g...@github.com:alistair23/qemu.git tags/

[Qemu-devel] [Bug 1603580] Re: [gdbstub] qemu is killed when using remote debugger with qemu -S -s

The sequence of gdb commands here is a bit odd since it's switching the gdb session from targeting a remote gdb stub to targeting a local executable. However, if you want to do this without killing QEMU you can: (gdb) target remote :1234 (gdb) detach (gdb) target exec /bin/ls The 'detach' tells g

Re: [Qemu-devel] [PATCH v7 0/2] spapr-rtas: add ibm, get-vpd RTAS interface

On Wed, 27 Mar 2019 17:41:00 -0300 "Maxiwell S. Garcia" wrote: > Here are two patches to add a handler for ibm,get-vpd RTAS calls. > This RTAS exposes host information in case of set QEMU options > 'host-serial' and 'host-model' as 'passthrough'. > > The patch 1 creates helper functions to get v

[Qemu-devel] [Qemu] questions about kvm and windows

We have implemented dynamic instrumentation mechanism (for guest code) DECAF (https://github.com/sycurelab/DECAF) with 2.7 version of qemu, and we have a few questions regarding that: 1. Why does qemu “without” kvm so slow to run Windows 10 guest? Simply booting or connecting ssh are too slow to r

Re: [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space

On 28/03/2019 10:38, Auger Eric wrote: Hi Alex, [+ Robin] On 3/27/19 5:37 PM, Alex Williamson wrote: On Wed, 27 Mar 2019 14:25:00 +0800 Peter Xu wrote: On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote: Conventional PCI buses pre-date requester IDs. An IOMMU cannot distingui

[Qemu-devel] [Bug 1806243] Re: ARM conditional branch after if-then instruction not working

There might still be some issues... Single-stepping works as long as I don't let GDB display the assembly with "display/i $pc". Once GDB decodes and displays every instruction the debugging session gets canceled when I hit the unpredictable branch. I'm not sure if this has anything to do with QEMU

[Qemu-devel] qemu-img: block/io.c:2122: bdrv_co_block_status: Assertion `*pnum && QEMU_IS_ALIGNED(*pnum, align) && align > offset - aligned_offset' failed.

Not sure if this is a bug in qemu or nbdkit or the NBD protocol, so I didn't file a bug yet. When returning NBD_CMD_BLOCK_STATUS extents which aren't aligned to a sector size, qemu-img gives an assert failure. This is reproducible using the block-status branch here: https://github.com/rwmjones

[Qemu-devel] [Bug 1806243] Re: ARM conditional branch after if-then instruction not working

That's great -- thanks for confirming that we've fixed the bug. ** Changed in: qemu Status: Incomplete => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1806243 Title: ARM cond

Re: [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space

On 28/03/2019 12:53, Auger Eric wrote: Hi Robin, On 3/28/19 11:56 AM, Robin Murphy wrote: On 28/03/2019 10:38, Auger Eric wrote: Hi Alex, [+ Robin] On 3/27/19 5:37 PM, Alex Williamson wrote: On Wed, 27 Mar 2019 14:25:00 +0800 Peter Xu wrote: On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex

[Qemu-devel] [PATCH for-4.0] hw/usb/bus.c: Handle "no speed matched" case in usb_mask_to_str()

In usb_mask_to_str() we convert a mask of USB speeds into a human-readable string (like "full+high") for use in tracing and error messages. However the conversion code doesn't do anything to the string buffer if the passed in speedmask doesn't match any of the recognized speeds, which means that th

Re: [Qemu-devel] [PATCH RFC] block/gluster: limit the transfer size to 512 MiB

On Thu, Mar 28, 2019 at 12:59:55PM +0100, Kevin Wolf wrote: > Am 28.03.2019 um 11:52 hat Stefano Garzarella geschrieben: > > Several versions of GlusterFS (3.12? -> 6.0.1) fail when the > > transfer size is greater or equal to 1024 MiB, so we are > > limiting the transfer size to 512 MiB to avoid t

[Qemu-devel] [Bug 1806243] Re: ARM conditional branch after if-then instruction not working

That sounds odd (and also like it might be a gdb bug, since 'display /i' is just implemented as memory reads from QEMU's point of view). I can have a look if you provide repro instructions. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QE

[Qemu-devel] [Bug 1603785] Re: trace_usb_port_attach prints junk data

This bug is still present in current head of git; I've just sent a patch: http://patchwork.ozlabs.org/patch/1068196/ ** Changed in: qemu Status: New => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.

[Qemu-devel] [Bug 1600681] Re: Usermode qemu-mips64 does not run on 32 bit i686 hosts

Whoops, I noted that 64-on-32 linux-user mode isn't expected to work back in 2016 but forgot to close the bug... ** Changed in: qemu Status: New => Won't Fix -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launch

Re: [Qemu-devel] [Qemu-arm] [RFC PATCH 15/17] Convert zynq's slcr to 3-phases reset

Hi Philippe, On 3/25/19 2:28 PM, Philippe Mathieu-Daudé wrote: > Hi Damien, > > Le lun. 25 mars 2019 12:16, Damien Hedde > a écrit : > > Change the legacy reset function into the init phase and test the > resetting flag in register accesses. > > S

Re: [Qemu-devel] Maintainers, please tell us how to boot your machines!

> -Original Messages- > From: "Markus Armbruster" > Sent Time: 2019-03-20 02:34:45 (Wednesday) > To: qemu-devel@nongnu.org > Cc: "Edgar E. Iglesias" , "Hervé Poussineau" > , "Aleksandar Markovic" , > "Aleksandar Rikalo" , "Alexander Graf" , > "Andrey Smirnov" , "Andrzej Zaborowski" > ,

  1   2   3   >