[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached

Fix has been pulled into the QEMU git repository: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=2c2311c5451f4555e850772 ** 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://

[Qemu-devel] [Bug 1581796] Re: console-gl.c:96:surface_gl_create_texture:code should not be reached

Thomas, thank you very much for your fix Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1581796 Title: console-gl.c:96:surface_gl_create_texture:code should not be reached Status in QEMU:

[Qemu-devel] [Bug 1555076] Re: Qemu 2.5 dont start with sdl, gl=on or gtk, gl=on

Fix has been pulled into the QEMU git repository: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=2c2311c5451f4555e850772 ** 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://

[Qemu-devel] [Bug 391879] Re: migrate exec ignores exit status

Patch has been included here: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=41ef56e61153d7bd27d34a63463 So I assume this should be working now. ** Changed in: qemu Status: In Progress => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which

[Qemu-devel] [Bug 1589564] Re: qemu/hw/scsi/scsi-disk.c:2741: possible missing break ?

The issue with the missing break has been fixed here: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ed45cae39117d41315541 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1589564 Title: qemu/hw/scsi/

[Qemu-devel] [Bug 1589564] Re: qemu/hw/scsi/scsi-disk.c:2741: possible missing break ?

I am currently not able to reproduce the problem with the format strings ... how did you get them? Which compiler (and version) did you use? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1589564 Titl

[Qemu-devel] [Bug 568053] Re: requires MSYS coreutils ext sub-package to build on Windows

signrom.sh has been removed/rewritten by this commit: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=0d6b9cc7420dd2d531b48508f0d4 ** Changed in: qemu Status: Confirmed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Qemu-devel] [Bug 1589564] Re: qemu/hw/scsi/scsi-disk.c:2741: possible missing break ?

>I am currently not able to reproduce the problem with the format strings ... >how did you get them? Which compiler (and version) did you use? I used a static analyser for C & C++ called cppcheck. It is available from sourceforge. I find it very useful. I think gcc might be able to reproduce the

Re: [Qemu-devel] [PATCH V9 0/9] Xilinx DisplayPort.

Le 09/06/2016 à 20:05, Peter Maydell a écrit : On 7 June 2016 at 22:39, Alistair Francis wrote: On Tue, Jun 7, 2016 at 1:30 PM, wrote: From: KONRAD Frederic Hey Peter, These are all reviewed by Xilinx, this is ready to merge from our point of view. This series breaks 'make check'. Sp

Re: [Qemu-devel] [Qemu-block] [PATCH] mirror: add target-zeroed flag

On 06/10/2016 07:59 PM, Stefan Hajnoczi wrote: On Tue, Jun 07, 2016 at 07:30:19PM +0300, Vladimir Sementsov-Ogievskiy wrote: On 03.06.2016 18:45, Denis V. Lunev wrote: On 06/03/2016 06:06 PM, Eric Blake wrote: On 06/03/2016 08:05 AM, Vladimir Sementsov-Ogievskiy wrote: Add target-zeroed flag

Re: [Qemu-devel] [RFC] Allow AMD IOMMU to have both SysBusDevice and PCIDevice properties.

On Thu, Jun 9, 2016 at 4:23 PM, Marcel Apfelbaum wrote: > On 06/07/2016 10:12 PM, Eduardo Habkost wrote: >> >> Hi, >> > > [...] > >> [...] >>> >>> diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c >>> index 04aae89..431eaed 100644 >>> --- a/hw/i386/pc_q35.c >>> +++ b/hw/i386/pc_q35.c >>> @@ -281,6

[Qemu-devel] qemu -nographics option

Hello qemu devs, I previously asked this question on stack overflow but didn't get an answer, so I thought I'd ask here: Stdio doesn't show in qemu with the -nographic option. This is my qemu invocation. It prints hello world when using `-serial stdio` but only displays kernel output when using `

[Qemu-devel] [PATCH] Call cmp with "-s" instead of "--quiet"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 - --quiet isn't available on FreeBSD and doesn't seem to be used in other places. This fixes some non-fatal build errors on FreeBSD. The use of "-s" over "--quiet" seems to be the preferred use in the Makefile. diff --git a/Makefile b/Makefile i

Re: [Qemu-devel] [RFC] hw/i386: Composite Bus and PCI device

On Fri, Jun 10, 2016 at 8:30 AM, Jan Kiszka wrote: > On 2016-06-08 17:25, Eduardo Habkost wrote: >> On Wed, Jun 08, 2016 at 01:00:32PM +0300, David Kiarie wrote: >>> Sample composite SysBus and PCI device similar to AMD IOMMU setup >>> >>> Signed-off-by: David Kiarie >>> --- >>> hw/i386/composit

Re: [Qemu-devel] qemu -nographics option

Hello, Have you try to add chardev device? -chardev stdio,mux=on,id=terminal -serial chardev:terminal I am also not sure if you so many consoles in kernel command line, since you do not want to use any graphic mode. Regards, Marcin W dniu 11.06.2016 o 16:22, David Craven pisze: Hello qemu d

Re: [Qemu-devel] [RFC 02/10] softmmu_llsc_template.h: Move to multi-threading

On 10/06/16 19:15, Alex Bennée wrote: > Sergey Fedorov writes: > >> On 26/05/16 19:35, Alvise Rigo wrote: >>> Using tcg_exclusive_{lock,unlock}(), make the emulation of >>> LoadLink/StoreConditional thread safe. >>> >>> During an LL access, this lock protects the load access itself, the >>> update

Re: [Qemu-devel] [PATCH] hw/usb/dev-network.c: Use ldl_le_p() and stl_le_p()

On 06/10/2016 09:37 AM, Peter Maydell wrote: > Use stl_le_p() and ldl_le_p() to read and write data from > buffers, rather than using pointer casts and cpu_to_le32() > for writes and le32_to_cpup() for reads. This: > * avoids lots of casts > * works even if the buffer isn't as aligned as the host

Re: [Qemu-devel] [PATCH] block: drop support for using qcow[2] encryption with system emulators

On 06/10/2016 09:32 AM, Daniel P. Berrange wrote: > Back in the 2.3.0 release we declared qcow[2] encryption as > deprecated, warning people that it would be removed in a future > release. > > commit a1f688f4152e65260b94f37543521ceff8bfebe4 > Author: Markus Armbruster > Date: Fri Mar 13 2

Re: [Qemu-devel] qemu -nographics option

Hello Marcin Reordering the console statements worked. The reason I had so many consoles in the kernel command line was because it was recommended in redirect-qemu-window-output-to-terminal-running-qemu

Re: [Qemu-devel] [PATCH] hw/sh4/sh_pci.c: Use ldl_le_p() and stl_le_p()

On 06/10/2016 10:10 AM, Peter Maydell wrote: > Use ldl_le_p() and stl_le_p() instead of le32_to_cpup() and > cpu_to_le32w(); the former handle misaligned addresses and don't > need casts, and the latter are deprecated. > > Signed-off-by: Peter Maydell > --- > hw/sh4/sh_pci.c | 4 ++-- > 1 file c

Re: [Qemu-devel] [PATCH] Call cmp with "-s" instead of "--quiet"

On 06/11/2016 11:15 AM, Sean Bruno wrote: > > > --quiet isn't available on FreeBSD and doesn't seem to be used in > other places. This fixes some non-fatal build errors on FreeBSD. The > use of "-s" over "--quiet" seems to be the preferred use in the Makefile. > > diff --git a/Makefile b/Makef

Re: [Qemu-devel] [PATCH 2/5] block: Honor flags during bdrv_aligned_preadv()

On 06/07/2016 06:12 AM, Kevin Wolf wrote: > Am 03.06.2016 um 19:03 hat Eric Blake geschrieben: >> Not that we pass any flags during reads yet, but we may want to >> support BDRV_REQ_FUA on reads in the future. So don't throw >> away the input flags. >> >> Signed-off-by: Eric Blake > > Do we want

Re: [Qemu-devel] [PATCH 3/5] block: Switch transfer length bounds to byte-based

On 06/07/2016 06:45 AM, Kevin Wolf wrote: > Am 03.06.2016 um 19:03 hat Eric Blake geschrieben: >> Sector-based limits are awkward to think about; in our on-going >> quest to move to byte-based interfaces, convert max_transfer_length >> and opt_transfer_length. Rename them (dropping the _length suf

Re: [Qemu-devel] [PULL 00/15] tb hash improvements

On 06/10/2016 09:41 AM, Peter Maydell wrote: On 10 June 2016 at 17:34, Emilio G. Cota wrote: On Fri, Jun 10, 2016 at 16:33:10 +0100, Peter Maydell wrote: Fails to build on ppc64be :-( In file included from /home/pm215/qemu/include/qemu/thread.h:4:0, from /home/pm215/qemu/incl

[Qemu-devel] [PULL v2 00/15] tb hash improvements

0 15:47:17 +0100) are available in the git repository at: git://github.com/rth7680/qemu.git tags/pull-tcg-20160611 for you to fetch changes up to 329844d4bc3d5a11f1e63938d66f74c9584c7abc: translate-all: add tb hash bucket info to 'info jit' dump (2016-0

[Qemu-devel] [PULL v2 04/15] include/processor.h: define cpu_relax()

From: "Emilio G. Cota" Taken from the linux kernel. Reviewed-by: Sergey Fedorov Reviewed-by: Richard Henderson Reviewed-by: Alex Bennée Signed-off-by: Emilio G. Cota Message-Id: <1465412133-3029-5-git-send-email-c...@braap.org> Signed-off-by: Richard Henderson --- include/qemu/processor.h

[Qemu-devel] [PULL v2 12/15] qht: add qht-bench, a performance benchmark

From: "Emilio G. Cota" This serves as a performance benchmark as well as a stress test for QHT. We can tweak quite a number of things, including the number of resize threads and how frequently resizes are triggered. A performance comparison of QHT vs CLHT[1] and ck_hs[2] using this same benchmar

[Qemu-devel] [PATCH] block: Avoid bogus flags during mirroring

Commit e253f4b8 converted mirroring from sector-based bdrv_aio_* to byte-based blk_aio_*, but failed to account for the subtle difference in signatures (the former takes a semi-redundant length, the latter takes a flags parameter). Since all of our flags are currently smaller in size than BDRV_SEC

Re: [Qemu-devel] [PATCH] block: Avoid bogus flags during mirroring

On Sat, 06/11 19:18, Eric Blake wrote: > Commit e253f4b8 converted mirroring from sector-based bdrv_aio_* > to byte-based blk_aio_*, but failed to account for the subtle > difference in signatures (the former takes a semi-redundant length, > the latter takes a flags parameter). Since all of our fl

Re: [Qemu-devel] [PATCH] block-backend: allow flush on devices with open tray

On Fri, 06/10 17:59, John Snow wrote: > If a device still has an attached BDS because the medium has not yet > been removed, we will be unable to migrate to a new host because > blk_flush will return an error for that backend. > > Replace the call to blk_is_available to blk_is_inserted to weaken >

Re: [Qemu-devel] [PATCH v8 11/12] vfio: register aer resume notification handler for aer resume

Hi, Alex It seems like we have a number of questions open in the thread with MST from the previous version, particularly whether we should actually drop the resume notifier and block the reset in the kernel. The concern being that it's not very well specified what we can and cannot do between t

Re: [Qemu-devel] [PATCH 5/6] qcow2: Let vmstate call qcow2_co_preadv/pwrite directly

On Fri, 06/10 16:39, Eric Blake wrote: > > +++ b/block/qcow2.c > > @@ -2903,36 +2903,20 @@ static int qcow2_save_vmstate(BlockDriverState *bs, > > QEMUIOVector *qiov, > >int64_t pos) > > { > > BDRVQcow2State *s = bs->opaque; > > -int64_t total_sectors = bs

Re: [Qemu-devel] [PATCH 0/6] block: bdrv_load/save_vmstate() cleanups

On Fri, 06/10 18:05, Kevin Wolf wrote: > This series contains a few cleanups with respect to the vmstate I/O functions. > Apart from making the interface more consistent (writes were already vectored, > but not reads), this makes use of the new byte-based .bdrv_co_preadv/pwritev > callbacks in qcow

Re: [Qemu-devel] [RFC PATCH 0/3] x86: Add support for guest DMA dirty page tracking

Hi, Alex On 2016/6/9 23:39, Alexander Duyck wrote: On Thu, Jun 9, 2016 at 3:14 AM, Zhou Jie wrote: TO Alex TO Michael In your solution you add a emulate PCI bridge to act as a bridge between direct assigned devices and the host bridge. Do you mean put all direct assigned devices to

Re: [Qemu-devel] [PATCH v3 1/5] block: Allow replacement of a BDS by its overlay

On Fri, 06/10 20:57, Max Reitz wrote: > change_parent_backing_link() asserts that the BDS to be replaced is not > used as a backing file. However, we may want to replace a BDS by its > overlay in which case that very link should not be redirected. > > For instance, when doing a sync=none drive-mir

[Qemu-devel] ext4 error when testing virtio-scsi & vhost-scsi

Here is one question about testing virtio-scsi & vhost-scsi. I met ext4 error using fileio or iblock. And after the error, the filesystem can not be remount next time in guest os except mkfs.ext4 again. Any suggestions? Thanks in advance. Basic steps. fileio: mount /dev/sda3 /mnt dd if=/dev/zero

Re: [Qemu-devel] [PATCH v3 3/5] block/null: Implement bdrv_refresh_filename()

On Fri, 06/10 20:57, Max Reitz wrote: > Signed-off-by: Max Reitz The commit message could go a little more informative. Seems nothing special in the added callback, aren't things supposed to just work without this patch? What is missing? > --- > block/null.c | 20 > 1 file

Re: [Qemu-devel] [PATCH v3 4/5] iotests: Add test for post-mirror backing chains

On Fri, 06/10 20:57, Max Reitz wrote: > +import os > +import stat > +import time Unused import 'stat' and 'time'? > +import iotests > +from iotests import qemu_img

Re: [Qemu-devel] [PATCH v3 0/5] block/mirror: Fix (?) target backing BDS

On Fri, 06/10 20:57, Max Reitz wrote: > Issue #1: If the target image does not have a backing BDS before mirror > completion, qemu tries really hard to give it a backing BDS. If the > source has a backing BDS, it will actually always "succeed". > In some cases, the target is not supposed to have a

Re: [Qemu-devel] [PATCH v2 2/3] hw/iommu: enable iommu with -device

On Thu, Jun 02, 2016 at 11:15:54PM +0300, Marcel Apfelbaum wrote: [...] > static void vtd_realize(DeviceState *dev, Error **errp) > { > +PCIBus *bus = PC_MACHINE(qdev_get_machine())->bus; > IntelIOMMUState *s = INTEL_IOMMU_DEVICE(dev); > > VTD_DPRINTF(GENERAL, ""); > @@ -2029,6

Re: [Qemu-devel] [PATCH V3] block/iscsi: allow caching of the allocation map

On Tue, 05/24 10:40, Peter Lieven wrote: > until now the allocation map was used only as a hint if a cluster > is allocated or not. If a block was not allocated (or Qemu had > no info about the allocation status) a get_block_status call was > issued to check the allocation status and possibly avoid

Re: [Qemu-devel] [RESEND] [PATCH 0/6] virtio: refactor host notifiers

On Fri, 06/10 11:04, Cornelia Huck wrote: > Hi, > > this is a resend of the host notifier refactoring I last sent out > on 2016/04/25. Just rebased on current master and pushed out to > github.com/cohuck/qemu host-notifier-refactor. > > Blurb from the last posting follows: > > This still fixes a

[Qemu-devel] [Bug 1591611] [NEW] chroot using qemu-x86_64-static fails on ppc64el

Public bug reported: When attempting to use qemu-x86_64-static from qemu 2.5.0 on a ppc64el host to chroot into an amd64 environment, all commands fail with an assertion error. /usr/bin/qemu-x86_64-static from the host was copied into the chroot /usr/bin, and the host has multiformat support in t

Re: [Qemu-devel] [PATCH v2 1/3] tests/docker/docker.py: docker_dir outside build

On Wed, 06/08 17:35, Alex Bennée wrote: > Instead of letting the build_image create the temporary working dir we > move the creation to the build command. This is preparation for the > later patches where additional files can be added to the build context > before the build step is run. > > We als

Re: [Qemu-devel] [PATCH v2 2/3] tests/docker/docker.py: support --include-executable

On Wed, 06/08 17:35, Alex Bennée wrote: > When passed the path to a binary we copy it and any linked libraries > into the docker build context. These can then be included by a > dockerfile with the line: > > # Copy all of context into container > ADD . / > > This is mainly intended for settin

[Qemu-devel] [PATCH v2] mirror: follow AioContext change gracefully

From: Stefan Hajnoczi When dataplane is enabled or disabled the drive switches to a new AioContext. The mirror block job must also move to the new AioContext so that drive accesses are always made within its AioContext. This patch partially achieves that by draining target and source requests t

[Qemu-devel] [PATCH] macio: Use blk_drain instead of blk_drain_all

We only care about the associated backend, so blk_drain is more appropriate here. Signed-off-by: Fam Zheng --- hw/ide/macio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw/ide/macio.c b/hw/ide/macio.c index 78c10a0..a8c7321 100644 --- a/hw/ide/macio.c +++ b/hw/ide/macio.