Triaging old bug tickets ... Can you still reproduce this problem with
the latest version of QEMU?
** 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/1
Triaging old bug tickets ... Can you still reproduce this problem with
the latest version of QEMU (currently version 2.9.0)?
** 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:/
On Tue, Jun 13, 2017 at 12:35:21PM +0200, Gioh Kim wrote:
> Hi,
>
> I'd like to report one use-after-free problem which is found by
> AddressSanitizer.
> My company provides virtualization server with Qemu-2.7.
> If customer commands Disk hot-unplug on Web-based application,
> the application sen
On 12/06/17 23:27, Laszlo Ersek wrote:
> It turns out that we introduced the "iobase" and "dma_iobase" properties
> *solely* so that we could pass arguments to fw_cfg_io_realize(). But
> fw_cfg_io_realize() only needed those parameters for the *wrong* purpose
> (namely calling sysbus_add_io()). By
Unfortunately the URL from comment #7 is dead nowadays ... has this fix
been committed to the QEMU repository?
** 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
Triaging old bug tickets ... Can you still reproduce this problem with
the latest version of QEMU (currently v2.9.0)?
** 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.l
Closing, as there is a work-around according to comment #6
** 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.launchpad.net/bugs/1090837
Title:
Error in building Qemu-1
From: Fam Zheng
Currently there are warnings about flex and bison being missing when
building in the centos6 image:
make[1]: flex: Command not found
BISON dtc-parser.tab.c
make[1]: bison: Command not found
Add them.
Reported-by: Thomas Huth
Signed-off-by: Fam Zheng
---
$ make docker-run-test-quick@centos6
In file included from hw/net/vmxnet3.c:30:
include/migration/register.h:18: error: redefinition of typedef
‘LoadStateHandler’
include/migration/vmstate.h:32: note: previous declaration of
‘LoadStateHandler’ was here
make: *** [hw/net/vmxnet
On Tue, Jun 06, 2017 at 09:19:38PM +0300, Roman Kagan wrote:
> Make Hyper-V SynIC a device which is attached as a child to X86CPU. For
> now it only makes SynIC visibile in the qom hierarchy and exposes a few
> properties which are maintained in sync with the respecitve msrs of the
> parent cpu.
>
Also included Fam's patch for bison/flex, not required but still silent few
warnings.
patchew output:
=== OUTPUT BEGIN ===
In file included from /tmp/qemu-test/src/hw/net/vmxnet3.c:30:
/tmp/qemu-test/src/include/migration/register.h:18: error: redefinition of
typedef ‘LoadStateHandl
On Tue, Jun 13, 2017 at 10:59:07AM -0700, Dave Hansen wrote:
> On 06/13/2017 10:56 AM, Michael S. Tsirkin wrote:
> >> +/* The size of one page_bmap used to record inflated/deflated pages. */
> >> +#define VIRTIO_BALLOON_PAGE_BMAP_SIZE (8 * PAGE_SIZE)
> > At this size, you probably want alloc_pa
On Tue, Jun 06, 2017 at 09:19:30PM +0300, Roman Kagan wrote:
> Hyper-V identifies vcpus by the virtual processor (VP) index which is
> normally queried by the guest via HV_X64_MSR_VP_INDEX msr.
>
> It has to be owned by QEMU in order to preserve it across migration.
>
> However, the current imple
On Tue, Jun 06, 2017 at 09:19:36PM +0300, Roman Kagan wrote:
> Use X86CPU pointer to refer to the respective HvSintRoute instead of
> vp_index. This is more convenient and also paves the way for future
> enhancements.
>
> Signed-off-by: Roman Kagan
[...]
> @@ -101,16 +101,18 @@ static void hv_te
Philippe Mathieu-Daudé writes:
> remove some copy/paste leftover, code seems sane.
>
> while running Alex Bennée's image aarch64-linux-3.15rc2-buildroot.img:
>
> Trace 0x7fa1904b0890 [0: ffc00036cd04]
>
> IN:
> 0xffc00036cd24: 5ac00694 rev16 w20, w20
>
> OP:
> ---
This way the bridge shows up in the correct section of the
"-device help" text.
Signed-off-by: Thomas Huth
---
hw/pci-bridge/dec.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/pci-bridge/dec.c b/hw/pci-bridge/dec.c
index cca9362..eb275e1 100644
--- a/hw/pci-bridge/dec.c
+++ b/hw/pci-
On 08.06.2017 20:49, Michael Rolnik wrote:
[...]
> diff --git a/hw/avr/sample.c b/hw/avr/sample.c
> new file mode 100644
> index 00..7b03130680
> --- /dev/null
> +++ b/hw/avr/sample.c
> @@ -0,0 +1,108 @@
> +/*
> + * QEMU AVR CPU
> + *
> + * Copyright (c) 2016 Michael Rolnik
> + *
> + * This
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Type: series
Subject: [Qemu-devel] [PATCH] hw/pci-bridge/dec: Classify the DEC PCI bridge as
bridge device
Message-id: 149738
On 08.06.2017 20:49, Michael Rolnik wrote:
> Signed-off-by: Michael Rolnik
> Message-Id: <1471522070-77598-10-git-send-email-mrol...@gmail.com>
> Signed-off-by: Richard Henderson
> ---
> target/avr/Makefile.objs | 1 +
> target/avr/decode.c | 691
> +++
On 08.06.2017 20:49, Michael Rolnik wrote:
> Signed-off-by: Michael Rolnik
> Message-Id: <1471522070-77598-9-git-send-email-mrol...@gmail.com>
> Signed-off-by: Richard Henderson
> ---
> target/avr/cpugen/CMakeLists.txt | 38 +++
> target/avr/cpugen/README.md| 17 ++
>
On 08.06.2017 21:38, Michael Rolnik wrote:
> From: Michael Rolnik
>
> From: Richard Henderson
>From whom is this patch? ... looks like there is something wrong with
the way you send the patches...
Thomas
On 08.06.2017 20:49, Michael Rolnik wrote:
> 1. basic CPU structure
> 2. registers
> 3. no instructions
> 4. saving sreg, rampD, rampX, rampY, rampD, eind in HW representation
>
> Signed-off-by: Michael Rolnik
> Message-Id: <1471522070-77598-2-git-send-email-mrol...@gmail.com>
> S
On 12/06/2017 16:37, David Gibson wrote:
> On Thu, Jun 08, 2017 at 07:27:42PM +0200, Laurent Vivier wrote:
>> If the OS is not started, QEMU sends an event to the OS
>> that is lost and cannot be recovered. An unplug is not
>> able to restore QEMU in a coherent state.
>> So, while the OS is not sta
=== Series dependencies ===
This series depends on v7 of Stefan's series
"qemu-img: add measure sub-command"
(http://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg03035.html).
=== Actual cover letter ===
This series adds preallocation to bdrv_truncate() and subsequently
qemu-img resize. T
Add a PreallocMode parameter to the bdrv_truncate() function implemented
by each block driver. Currently, we always pass PREALLOC_MODE_OFF and no
driver accepts anything else.
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
include/block/block_int.h | 3 ++-
block.c
preallocate() is and will be called only from places that do not
otherwise need to lock s->lock: Currently that is qcow2_create2(), as of
a future patch it will be called from qcow2_truncate(), too.
It therefore makes sense to move locking that mutex into preallocate()
itself.
Signed-off-by: Max
blk_truncate() itself will pass that value to bdrv_truncate(), and all
callers of blk_truncate() just set the parameter to PREALLOC_MODE_OFF
for now.
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
include/sysemu/block-backend.h | 3 ++-
block/block-backend.c | 5 +++--
block
For block drivers that just pass a truncate request to the underlying
protocol, we can now pass the preallocation mode instead of aborting if
it is not PREALLOC_MODE_OFF.
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
include/block/block.h | 3 ++-
block.c| 5 +++--
Currently, raw_regular_truncate() is intended for setting the size of a
newly created file. However, we also want to use it for truncating an
existing file in which case only the newly added space (when growing)
should be preallocated.
This also means that if resizing failed, we should try to rest
Add a --preallocation command line option to qemu-img resize which can
be used to set the PreallocMode parameter of blk_truncate().
While touching this code, fix the fact that we did not handle errors
returned by blk_getlength().
Signed-off-by: Max Reitz
---
qemu-img.c| 33 +
This functionality is part of raw_create() which we will be able to
reuse nicely in raw_truncate().
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Philippe Mathieu-Daudé
---
block/file-posix.c | 144 +
1 file changed, 78 i
Variables should be declared at the start of a block, and if a certain
parameter value is not supported it may be better to return -ENOTSUP
instead of -EINVAL.
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Philippe Mathieu-Daudé
---
block/file-posix.c | 5 +++--
1 file cha
From: David Hildenbrand
Let's properly expose the CPU type (machine-type number) via "STORE CPU
ID" and "STORE SUBSYSTEM INFORMATION".
As TCG emulates basic mode, the CPU identification number has the format
"An", whereby A is the CPU address, and n are parts of the CPU serial
number (0 for
This patch adds two new parameters to the preallocate() function so we
will be able to use it not just for preallocating a new image but also
for preallocated image growth.
The offset parameter allows the caller to specify a virtual offset from
which to start preallocating. For newly created image
this is generated code.
On Tue, Jun 13, 2017 at 11:01 PM, Thomas Huth wrote:
> On 08.06.2017 20:49, Michael Rolnik wrote:
> > Signed-off-by: Michael Rolnik
> > Message-Id: <1471522070-77598-10-git-send-email-mrol...@gmail.com>
> > Signed-off-by: Richard Henderson
> > ---
> > target/avr/Makefi
By using raw_regular_truncate() in raw_truncate(), we can now easily
support preallocation.
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
block/file-posix.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/block/file-posix.c b/block/file-p
We can support PREALLOC_MODE_METADATA by invoking preallocate() in
qcow2_truncate().
Signed-off-by: Max Reitz
---
block/qcow2.c | 33 +++--
1 file changed, 31 insertions(+), 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index c1aec07..f007aa8 100644
--- a
Implement the preallocation modes falloc and full for growing qcow2
images.
Signed-off-by: Max Reitz
---
block/qcow2.h | 5 +++
block/qcow2-refcount.c | 12 ++
block/qcow2.c | 100 -
3 files changed, 108 insertions(+), 9 de
the last version of my patches were done by Richard. Now I just reapplied
them to the master.
Should I have to remove "signed-off-by Richard" ?
On Tue, Jun 13, 2017 at 11:09 PM, Thomas Huth wrote:
> On 08.06.2017 20:49, Michael Rolnik wrote:
> > 1. basic CPU structure
> > 2. registers
>
This function creates a collection of self-describing refcount
structures (including a new refcount table) at the end of a qcow2 image
file. Optionally, these structures can also describe a number of
additional clusters beyond themselves; this will be important for
preallocated truncation, which wi
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
tests/qemu-iotests/125 | 130 +++
tests/qemu-iotests/125.out | 386 +
tests/qemu-iotests/group | 1 +
3 files changed, 517 insertions(+)
create mode 100755 tests/qemu-iotest
Now alloc_refcount_block() only contains a single fail label, so it
makes more sense to just name it "fail" instead of "fail_block".
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
block/qcow2-refcount.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
Signed-off-by: Max Reitz
Reviewed-by: Stefan Hajnoczi
---
tests/qemu-iotests/106 | 92 ++
tests/qemu-iotests/106.out | 50 +
tests/qemu-iotests/group | 1 +
3 files changed, 143 insertions(+)
create mode 100755 tests/qem
From: David Hildenbrand
Signed-off-by: David Hildenbrand
Message-Id: <20170609142156.18767-2-da...@redhat.com>
Signed-off-by: Richard Henderson
---
target/s390x/misc_helper.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/s390x/misc_helper.c b/target/s390x/misc_helper.c
index edcdf
Cleanups and fixes from David Hildenbrand.
r~
The following changes since commit 3f0602927b120a480b35dcf58cf6f95435b3ae91:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20170613'
into staging (2017-06-13 15:49:07 +0100)
are available in the git repository
From: David Hildenbrand
We can tell from the program interrupt code, whether a program interrupt
has to forward the address in the PGM new PSW
(suppressing/terminated/completed) to point at the next instruction, or
if it is nullifying and the PSW address does not have to be incremented.
So let's
please explain.
On Tue, Jun 13, 2017 at 11:07 PM, Thomas Huth wrote:
> On 08.06.2017 21:38, Michael Rolnik wrote:
> > From: Michael Rolnik
> >
> > From: Richard Henderson
>
> From whom is this patch? ... looks like there is something wrong with
> the way you send the patches...
>
> Thomas
>
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PULL 0/3] Queued s390x tcg patches
Type: series
Message-id: 20170613202659.1920-1-...@twiddle.net
===
uri_parse(...)->scheme may be NULL. In fact, probably every field may be
NULL, and the callers do test this for all of the other fields but not
for scheme (except for block/gluster.c; block/vxhs.c does not access
that field at all).
We can easily fix this by using g_strcmp0() instead of strcmp().
On Tue 13 Jun 2017 07:20:04 PM CEST, Max Reitz wrote:
> blkdebug and blkverify use snprintf() to generate a filename; however,
> that may not fit into the target buffer (BDS.exact_filename). If so,
> they generate a truncated and thus pretty much unusable filename. In
> this case it's better to ju
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 20170613205726.13544-1-mre...@redhat.com
Subject: [Qemu-devel] [PATCH v2] block: Do not strcmp() with NULL uri->sc
There used to be throttle_timers_{detach,attach}_aio_context() calls
in bdrv_set_aio_context(), but since 7ca7f0f6db1fedd28d490795d778cf239
they are now in blk_set_aio_context().
Signed-off-by: Alberto Garcia
---
block/throttle-groups.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20170613211612.9368-1-be...@igalia.com
Subject: [Qemu-devel] [PATCH] throttle: Update throttle-groups
Quoting Igor Mammedov (2017-06-09 03:27:33)
> On Thu, 08 Jun 2017 15:00:53 -0500
> Michael Roth wrote:
>
> > Quoting David Gibson (2017-05-30 23:35:57)
> > > On Tue, May 30, 2017 at 06:04:45PM +0200, Laurent Vivier wrote:
> > > > For QEMU, a hotlugged device is a device added using the HMP/QMP
This will not change the qemu model, we simply allow to enable the facility
for the qemu model.
A current upstream kernel (compiled for e.g. z900) can be tricked into
using MVCOS for uaccess by simply enabling the facility. This will work
even though the kernel is not compiled with z10+ support, a
Such shifts are usually used to easily extract the PSW KEY from the PSW
mask, so let's avoid the confisuing offset of 4.
Signed-off-by: David Hildenbrand
---
target/s390x/cpu.h | 2 +-
target/s390x/translate.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/s3
This allows botting a recent linux kernel (e.g. compiled for z900) and
using mvcos for uaccess:
qemu-system-s390x ... -cpu qemu,mvcos=on ...
While at it, correctly fake its abscence.
Signed-off-by: David Hildenbrand
---
target/s390x/cpu_models.c | 1 +
target/s390x/mem_helper.c | 3 +++
2 file
This adds support for the MOVE WITH OPTIONAL SPECIFICATIONS (MVCOS)
instruction (in a relatively slow way). But it is enough to boot
a linux kernel that uses it for uacccess (primary <-> seconardy).
We are missing (as for most other part) low address protection checks,
PSW key / storage key checks
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20170613214736.19963-1-da...@redhat.com
Subject: [Qemu-devel] [PATCH v1 0/3] target/s390x: implement
Indeed, I had no problem booting the images this time around:
https://asciinema.org/a/d2m42g5c0n3z2pnbskhirdv5j
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't
The appended fixes it for me. Can you please test?
[ apply with `git am --scissors' ]
Thanks,
Emilio
8<
Commit e75449a3 ("target/aarch64: optimize indirect branches") causes
a regression by which aarch64 guests freeze under TCG with -smp > 1,
even with `-accel accel=tc
Some USB devices have sparse interface numbering which is not able to be
passthroughed.
For example, the Sierra Wireless MC7455/MC7430:
# lsusb -D /dev/bus/usb/003/003 | egrep
'1199|9071|bNumInterfaces|bInterfaceNumber'
Device: ID 1199:9071 Sierra Wireless, Inc.
idVendor 0x1199
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH] target/aarch64: exit to main loop after handling
MSR
Type: series
Message-id: 20170613225352.GA
Shorter timeouts will be useful for test code that needs to catch QEMU
exiting before it connects to the QMP socket.
Signed-off-by: Eduardo Habkost
---
scripts/qmp/qmp.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/qmp/qmp.py b/scripts/qmp/qmp.py
index 62d3651
Extend the device-crash-test script so it can test backend objects, too.
The new mode can be enabled using the "-O" option.
The script already found a crash using the following command-line:
$ qemu-system-x86_64 -S -machine none -object colo-compare,id=test-object
(qemu-system-x86_64:3812): G
To avoid waiting for the full 15-second timeout for a connection, check
if QEMU exited once in a while. Start with a very short timeout (15ms),
and double it on each try.
This will be helpful for scripts/device-crash-test, on cases where QEMU
crashes or exits before connecting to the QMP socket.
This series extends the device-crash-test script so it can test
backend objects, too. The new mode can be enabled using the "-O"
option.
The script already found a crash using the following command-line:
$ qemu-system-x86_64 -S -machine none -object colo-compare,id=test-object
(qemu-system-x
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH v2] usb-host: support devices with
sparse/non-sequential USB interfaces
Type: series
Message-id:
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20170613225900.1641-1-sam.br...@accelerated.com
Type: series
Subject: [Qemu-devel] [PATCH v2] usb-host: support devices with
sparse/non-sequential USB interfaces
=== TEST SCRIPT BEGIN ==
Original Message
Subject: Re: [Qemu-devel] [PATCH RFC v19 11/13] target-avr: Put all translation
code into one compilation unit
Local Time: June 13, 2017 10:07 PM
UTC Time: June 13, 2017 8:07 PM
From: th...@redhat.com
To: Michael Rolnik , qemu-devel@nongnu.org
Richard Henderson ,
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 20170613230627.17942-1-ehabk...@redhat.com
Type: series
Subject: [Qemu-devel] [PATCH 0/3] device-crash-test: New m
Some USB devices have sparse interface numbering which is not able to be
passthroughed.
For example, the Sierra Wireless MC7455/MC7430:
# lsusb -D /dev/bus/usb/003/003 | egrep
'1199|9071|bNumInterfaces|bInterfaceNumber'
Device: ID 1199:9071 Sierra Wireless, Inc.
idVendor 0x1199
Done. Had to V3 it to pass the formatting check. Sorry about that.
Sam
On 13/06/17 20:22, Gerd Hoffmann wrote:
On Tue, 2017-06-13 at 14:17 +1000, Samuel Brian wrote:
This change allows sparse USB interface numbering.
Instead of only claiming the interfaces in the range reported by the
USB
devi
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 20170613234039.27201-1-sam.br...@accelerated.com
Subject: [Qemu-devel] [PATCH v3] usb-host: support devices with
Hi Adam
Do these arguments sound reasonable to apply the patch?
On Thu, Jun 8, 2017 at 2:07 PM, Anatol Pomozov wrote:
> +reply-all
>
> On Thu, Jun 8, 2017 at 1:41 PM, Adam Lackorzynski
> wrote:
>>
>> On Tue Jun 06, 2017 at 21:41:48 -0700, Anatol Pomozov wrote:
>>> It is possible to create a 64
At 06/12/2017 10:05 PM, Keith Busch wrote:
On Fri, Jun 02, 2017 at 03:51:51PM +0200, Kevin Wolf wrote:
Am 02.06.2017 um 03:47 hat Qu Wenruo geschrieben:
When going through NVMe specification and hw/block/nvme.c,
I found that it seems that NVMe qemu implementation only support PRP
for sq entry
On Tue, Jun 13, 2017 at 12:55:29PM +0200, Thomas Huth wrote:
> Since the introduction of MTTCG, using the msgsnd instruction
> abort()s if being called without holding the BQL. So let's protect
> that part of the code now with qemu_mutex_lock_iothread().
>
> Buglink: https://bugs.launchpad.net/qem
On Tue, Jun 13, 2017 at 01:59:29PM +0530, Nikunj A Dadhania wrote:
> Greg Kurz writes:
>
> > On Sun, 11 Jun 2017 17:38:42 +0800
> > David Gibson wrote:
> >
> >> On Fri, Jun 09, 2017 at 05:09:13PM +0200, Greg Kurz wrote:
> >> > On Fri, 9 Jun 2017 20:28:32 +1000
> >> > David Gibson wrote:
> >> >
On Tue, Jun 13, 2017 at 05:24:28PM +0200, Greg Kurz wrote:
> On Tue, 13 Jun 2017 18:01:46 +0800
> David Gibson wrote:
>
> > On Tue, Jun 13, 2017 at 11:21:50AM +0200, Greg Kurz wrote:
> > > On Tue, 13 Jun 2017 10:00:03 +0100
> > > "Dr. David Alan Gilbert" wrote:
> > >
> > > > * Greg Kurz (gr..
On Tue, Jun 13, 2017 at 09:48:49PM +0200, Thomas Huth wrote:
> This way the bridge shows up in the correct section of the
> "-device help" text.
>
> Signed-off-by: Thomas Huth
Reviewed-by: David Gibson
> ---
> hw/pci-bridge/dec.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/
On Tue, Jun 13, 2017 at 12:58:13PM -0700, no-re...@patchew.org wrote:
> In file included from /tmp/qemu-test/src/hw/net/vmxnet3.c:30:
> /tmp/qemu-test/src/include/migration/register.h:18: error: redefinition of
> typedef ‘LoadStateHandler’
> /tmp/qemu-test/src/include/migration/vmstate.h:32: note:
On Tue, Jun 13, 2017 at 08:16:35AM -0300, Eduardo Habkost wrote:
> On Tue, Jun 13, 2017 at 11:41:02AM +0800, Peter Xu wrote:
> > On Mon, Jun 12, 2017 at 04:18:06PM +0800, Peter Xu wrote:
> > > On Fri, Jun 09, 2017 at 10:40:10AM -0300, Eduardo Habkost wrote:
> > > > On Fri, Jun 09, 2017 at 11:48:59A
Programs running inside of QEMU can sometimes use more CPU time than is really
needed. To solve this problem, we just need to throttle the virtual CPU. This
feature will stop laptops from burning up.
This patch adds a menu called Speed that has menu items from 100% to 1% that
represent the speed
Hello Paolo,
About you below A20 fixed patch has been merged in QEMU latest release,
commit bbfa326fc8028e275eddf8c9965c2a1b59405b2e
target/i386: enable A20 automatically in system management mod
I also disabled the kvmvapic rom with below patch and use qemu command to
verify your patch
#disa
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Type: series
Message-id: d6faaabf-064d-49c0-b572-c73679f34...@gmail.com
Subject: [Qemu-devel] [PATCH v3] ui/cocoa.m: add Speed
From: Li Qiang
In 'xhci_write_event' function, the 'ev_trb' is not full initialized.
This will lead an info leak issue. This patch avoid this.
Signed-off-by: Li Qiang
---
hw/usb/hcd-xhci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/usb/hcd-xhci.c b/hw/usb/hcd-xhci.c
index a0c7960..
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1497411544-80213-1-git-send-email-liqiang...@360.cn
Subject: [Qemu-devel] [PATCH] usb: xhci: fix info
As you said, due to Travis using Ubuntu still not all libs get detected
but at least the following:
$ ./configure ${CONFIG}
-VirtFS supportno
+VirtFS supportyes
-bluez supportno
+bluez supportyes
-xfsctl supportno
+xfsctl supportyes
-lzo support no
+lzo support
2017-06-14 11:47 GMT+08:00 :
> Hi,
>
> This series failed automatic build test. Please find the testing commands
> and
> their output below. If you have docker installed, you can probably
> reproduce it
> locally.
>
>
>
> CC hw/timer/a9gtimer.o
> In file included from /tmp/qemu-test/src/hw/
[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/1030666
Title:
gdb can't p
On 06/13/2017 02:47 PM, David Hildenbrand wrote:
+static inline bool psw_key_valid(CPUS390XState *env, uint8_t psw_key)
+{
+uint16_t pkm = ((env->cregs[3] & CR3_PKM) >> 16);
+
+if (env->psw.mask & PSW_MASK_PSTATE) {
+/* PSW key has range 0..15, it is valid if the bit is 1 in the P
On Wed, Jun 14, 2017 at 05:19:18AM +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 13, 2017 at 12:58:13PM -0700, no-re...@patchew.org wrote:
> > In file included from /tmp/qemu-test/src/hw/net/vmxnet3.c:30:
> > /tmp/qemu-test/src/include/migration/register.h:18: error: redefinition of
> > typedef ‘
On 06/13/2017 02:47 PM, David Hildenbrand wrote:
+if (!s390_has_feat(S390_FEAT_MOVE_WITH_OPTIONAL_SPEC)) {
+program_interrupt(env, PGM_OPERATION, 6);
+}
This is (supposed to be) done via the feature field of insn-data.def.
Except that we do not yet enforce that; we haven't upda
On 06/13/2017 03:53 PM, Emilio G. Cota wrote:
The appended fixes it for me. Can you please test?
[ apply with `git am --scissors' ]
Thanks,
Emilio
8<
Commit e75449a3 ("target/aarch64: optimize indirect branches") causes
a regression by which aarch64 guests freeze und
On Wed, 06/14 10:30, David Gibson wrote:
> On Wed, Jun 14, 2017 at 05:19:18AM +0300, Michael S. Tsirkin wrote:
> > On Tue, Jun 13, 2017 at 12:58:13PM -0700, no-re...@patchew.org wrote:
> > > In file included from /tmp/qemu-test/src/hw/net/vmxnet3.c:30:
> > > /tmp/qemu-test/src/include/migration/reg
David Gibson writes:
> On Tue, Jun 13, 2017 at 01:59:29PM +0530, Nikunj A Dadhania wrote:
>> Greg Kurz writes:
>>
>> > On Sun, 11 Jun 2017 17:38:42 +0800
>> > David Gibson wrote:
>> >
>> >> On Fri, Jun 09, 2017 at 05:09:13PM +0200, Greg Kurz wrote:
>> >> > On Fri, 9 Jun 2017 20:28:32 +1000
>>
On Tue, Jun 13, 2017 at 03:00:28PM +0300, Alexey Perevalov wrote:
> On 06/13/2017 02:42 PM, Juan Quintela wrote:
[...]
> >>Bitmap is placed into RAMBlock as another postcopy/precopy
> >>related bitmaps.
> >Why are we not using the TARGET_PAGE_SIZE as units of the bitmap?
> Page size per ram block
On Tue, 06/13 15:30, Philippe Mathieu-Daudé wrote:
> $ make docker-run-test-quick@centos6
> In file included from hw/net/vmxnet3.c:30:
> include/migration/register.h:18: error: redefinition of typedef
> ‘LoadStateHandler’
> include/migration/vmstate.h:32: note: previous declaration
On Tue, Jun 13, 2017 at 12:36:33PM +0300, Alexey Perevalov wrote:
> This patch adds ability to track down already copied
> pages, it's necessary for calculation vCPU block time in
> postcopy migration feature, maybe for restore after
> postcopy migration failure.
> Also it's necessary to solve shar
On 13.06.2017 22:29, Michael Rolnik wrote:
> this is generated code.
Hmm, then it should likely not be included in a patch, but generated
during built-time instead, I guess?
Thomas
1 - 100 of 387 matches
Mail list logo
