Dne 20.7.2017 v 20:44 Eduardo Habkost napsal(a):
> On Thu, Jul 20, 2017 at 06:28:15PM +0200, Lukáš Doktor wrote:
>> The list is a mutable object and is dangerous to use it. Recently the
>> QEMUMachine was adjusted to allow None as default, let's use it here as
>> well.
>>
>> Signed-off-by: Lukáš Do
Hello,
We shared a proposal for 'KVM fake DAX flushing interface'.
https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg02478.html
We did initial POC in which we used 'virtio-blk' device to perform
a device flush on pmem fsync on ext4 filesystem. They are few hacks
to make things work. We
On Fri, Jul 21, 2017 at 10:21:06AM +0530, Bharata B Rao wrote:
> Commit 0cffce56 (hw/ppc/spapr.c: adding pending_dimm_unplugs to
> sPAPRMachineState) introduced a new way to track pending LMBs of DIMM
> device that is marked for removal. Since this commit we can hit the
> assert in spapr_pending_di
This series add support querying local apic through apic-id for 'info
lapic'.
As cpu_index will not be used afterwards, so extend 'info registers'
firstly to get apic-id through monitor commands.
Yi Wang (2):
hmp: dump ids including socket-id, core-id and so on for 'info registers'
hmp: allow
This patch add output of CPUs' socket-id, core-id, thread-id and
apic-id for 'info registers', which can be used for querying other
hmp commands.
Signed-off-by: Yi Wang
Signed-off-by: Yun Liu
---
include/qom/cpu.h| 12
monitor.c| 1 +
qom/cpu.c| 10
Add [apic-id] support for hmp command "info lapic", which is
useful when debugging ipi and so on. Current behavior is not
changed when the parameter isn't specified.
Signed-off-by: Yi Wang
Signed-off-by: Yun Liu
---
hmp-commands-info.hx | 6 +++---
target/i386/cpu.h | 10 ++
targe
On 21/07/17 16:48, Philippe Mathieu-Daudé wrote:
> Hi Alexey,
>
> On 07/21/2017 01:19 AM, Alexey Kardashevskiy wrote:
>> This reverts c8e1158cf611 "elf-loader: warn about invalid endianness"
>> as it produces a useless message every time an LE kernel image is
>> passed via -kernel on a ppc64-pseri
Dne 20.7.2017 v 22:14 Amador Pahim napsal(a):
> On Thu, Jul 20, 2017 at 7:49 PM, Eduardo Habkost wrote:
>> On Thu, Jul 20, 2017 at 05:09:11PM +0200, Markus Armbruster wrote:
>>> Amador Pahim writes:
>>>
On Thu, Jul 20, 2017 at 1:49 PM, Markus Armbruster
wrote:
> Amador Pahim writ
Hi Thomas,
thnx for coming back on this. Currently on vacation, but just gave it a
shot on fresh compiled qemu-2.9.0:
—
savevm
Error while writing VM state: Operation not supported
—
I think there once existed a patch from the Proxmox guys dealing with the VM
state informations. But
apparentl
On Wed, Jul 19, 2017 at 02:02:18PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2017-07-19 at 13:08 +1000, David Gibson wrote:
> >
> > I'm somewhat uncomfortable with an irq allocater here in the intc
> > code. As a rule, irq allocation is the responsibility of the machine,
> > not any sub-comp
On 07/21/2017 04:30 AM, Alexey Kardashevskiy wrote:
On 21/07/17 16:48, Philippe Mathieu-Daudé wrote:
I submitted this patch because I spent some time debugging while QEMU was
failing silently using a MIPS kernel image which used to work, after
realizing I was in an incorrect build_dir using qemu
On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
* Peter Maydell (peter.mayd...@linaro.org) wrote:
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
* Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
Is there a way we can prevent migration of the RAMBlock?
Not yet, I think w
On 20/07/2017 9:52, Gerd Hoffmann wrote:
On Wed, 2017-07-19 at 16:20 +0300, Aleksandr Bezzubikov wrote:
Now PCI bridges (and PCIE root port too) get a bus range number in
system init,
basing on currently plugged devices. That's why when one wants to
hotplug another bridge,
it needs his child bus
Since commit cfc87e00 "block/vpc.c: Handle write failures in
get_image_offset()" older versions of gcc (in this case 4.7) incorrectly
warn that "ret" can be used uninitialised in vpc_co_pwritev().
Setting ret to 0 at the start of vpc_co_pwritev() prevents the warning
in gcc 4.7 and enables compila
On 20.07.2017 20:59, Richard Henderson wrote:
> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>> This is a massive but mechanical patch, the result of:
>>
>>(cd fpu/softfloat3c; and find . | xargs dos2unix)
>>(cd include/fpu/softfloat3c; and dos2unix *)
>>
>> Signed-off-by: Alex Bennée
>> ---
On Fri, 2017-07-21 at 17:50 +1000, David Gibson wrote:
> On Wed, Jul 19, 2017 at 02:02:18PM +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2017-07-19 at 13:08 +1000, David Gibson wrote:
> > >
> > > I'm somewhat uncomfortable with an irq allocater here in the intc
> > > code. As a rule, irq allo
On 20/07/17 22:09, Peter Maydell wrote:
>> The fix is seemingly quite simple:
>>
>> diff --git a/block/vpc.c b/block/vpc.c
>> index 10e6519..574879b 100644
>> --- a/block/vpc.c
>> +++ b/block/vpc.c
>> @@ -649,7 +649,7 @@ vpc_co_pwritev(BlockDriverState *bs, uint64_t
>> offset, uint64_t bytes,
>>
On 20/07/2017 3:44, Kinsella, Ray wrote:
Hi Marcel,
Hi Ray,
You can use multi-function PCIe Root Ports, this will give you 8 ports
per slot, if you have 16 empty slots (I think we have more) you reach
128 root ports.
Then you can use multi-function virtio-net-pci devices, this will
give you
On Fri, Jul 21, 2017 at 09:44:33AM +0800, 陳培泓 wrote:
> I re-build qemu from the https://github.com/qemu/qemu, and it didn't show
> any errors.
>
> I tried the cmd you suggested below:
>
> > qemu-nbd --object secret,id=sec0,file=passwd.txt,format=raw \
> >-c /dev/nbd0 \
> >
Patch has finally been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=b02cf99b9d998b3ec23dae8
** 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.launchp
OK, thanks for your answer - so I'm closing the ticket now
** Changed in: qemu
Status: Incomplete => 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/1196727
Title:
SLIRP on Windows
** Changed in: qemu
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1185395
Title:
qemu-1.5.0 savevm error -95 while writing vm with ceph-rbd as storage-
backen
Am 20.07.2017 um 21:19 schrieb Eric Blake:
> On 07/20/2017 11:30 AM, Peter Lieven wrote:
>
>>> The new code is now unconditionally initializing with -15 instead of
>>> -12. Does that matter, or does decompression work regardless of window
>>> size used at creation, as long as the initialized size
Thomas Huth writes:
> On 20.07.2017 20:59, Richard Henderson wrote:
>> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>>> This is a massive but mechanical patch, the result of:
>>>
>>>(cd fpu/softfloat3c; and find . | xargs dos2unix)
>>>(cd include/fpu/softfloat3c; and dos2unix *)
>>>
>>> Si
On Thu, 20 Jul 2017 21:29:33 +0200
Phil Dennis-Jordan wrote:
> On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
> wrote:
> > I noticed that Windows 2000 does not boot up in QEMU recently. After
> > bisecting the issue I found the offending commit:
w2k is very ancient (and long time EOLed), I can
On Fri, Jul 21, 2017 at 11:06 AM, Igor Mammedov wrote:
> On Thu, 20 Jul 2017 21:29:33 +0200
> Phil Dennis-Jordan wrote:
>
>> On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
>> wrote:
>> > I noticed that Windows 2000 does not boot up in QEMU recently. After
>> > bisecting the issue I found the o
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> > > On 17 July 2017 at 19:58, Dr. David Alan Gilbert
> > > wrote:
> > > > * Edgar E. Iglesias (edgar.igles...@gmail.com) wro
On 21 July 2017 at 05:10, Fam Zheng wrote:
> On Thu, 07/20 19:06, 陳培泓 wrote:
>> I build qemu from the https://github.com/qemu/qemu, and it didn't show any
>> errors.
>>
>> I tried qemu-nbd --object secret,id=sec0...
>> but it shows unrecognized option '--object '
>>
>> how to solve it?
>
> -object
On Thu, Jul 20, 2017 at 09:29:33PM +0200, Phil Dennis-Jordan wrote:
> On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
> wrote:
> > I noticed that Windows 2000 does not boot up in QEMU recently. After
> > bisecting the issue I found the offending commit:
>
> Ouch. I reckon we have 2 options for f
Hi,
Ping
On Thu, Jul 13, 2017 at 7:51 AM, sundeep subbaraya
wrote:
> Hi Phiiippe,
>
> Gentle reminder.
>
> Thanks,
> Sundeep
>
>
> On Mon, Jul 10, 2017 at 1:55 PM, sundeep subbaraya > wrote:
>
>> Hi Alistair,
>>
>> On Fri, Jul 7, 2017 at 10:03 PM, Alistair Francis
>> wrote:
>>
>>> On Fri, Jul
On 21 July 2017 at 09:56, Alex Bennée wrote:
> One thing playing in my mind against moving to SoftFloat3c is the
> inscrutability of the upstream. It's nice there has been a new release
> with new features but there isn't a source repository or as far as I can
> tell a development list. It is basi
On Fri, Jul 21, 2017 at 11:06:36AM +0200, Igor Mammedov wrote:
> On Thu, 20 Jul 2017 21:29:33 +0200
> Phil Dennis-Jordan wrote:
>
> > On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
> > wrote:
> > > I noticed that Windows 2000 does not boot up in QEMU recently. After
> > > bisecting the issue I
On Fri, 07/21 10:15, Peter Maydell wrote:
> On 21 July 2017 at 05:10, Fam Zheng wrote:
> > On Thu, 07/20 19:06, 陳培泓 wrote:
> >> I build qemu from the https://github.com/qemu/qemu, and it didn't show any
> >> errors.
> >>
> >> I tried qemu-nbd --object secret,id=sec0...
> >> but it shows unrecogniz
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> > > On 17 July 2017 at 19:58, Dr. David Alan Gilbert
> > > wrote:
> > > > * Edgar E. Iglesias (edgar.igles...@gmail.com) wro
On Fri, Jul 21, 2017 at 09:56:23AM +0100, Alex Bennée wrote:
>
> Thomas Huth writes:
>
> > On 20.07.2017 20:59, Richard Henderson wrote:
> >> On 07/20/2017 05:04 AM, Alex Bennée wrote:
> >>> This is a massive but mechanical patch, the result of:
> >>>
> >>>(cd fpu/softfloat3c; and find . | x
On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
> I don't fully understand the way memory_region_do_invalidate_mmio_ptr
> works; I see it dropping the memory region; if that's also dropping
> the RAMBlock then it will upset migration. Even if the CPU is stopped
> I dont think that stops
It works after I replace the /usr/bin/qemu-nbd with binary I built.
My cmd is :
> qemu-nbd --object secret,id=sec0,file=passwd.txt,format=raw \
> --image-opts driver=qcow2,file.filename=
> demo.qcow2,encrypt.format=luks,encrypt.key-secret=sec0
But I got other message:
> Block form
On 20 July 2017 at 09:45, Gerd Hoffmann wrote:
> The following changes since commit d4e59218ab80e86015753782fb5378767a51ccd0:
>
> Merge remote-tracking branch
> 'remotes/berrange/tags/pull-qcrypto-2017-07-18-2' into staging (2017-07-19
> 20:45:37 +0100)
>
> are available in the git repository
w2k used to boot on QEMU until we bumped revision of FADT to rev3
(commit 77af8a2b hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to improve
guest OS support.)
Considering that w2k is ancient and long time EOLed, leave default
rev3 but make pc-i440fx-2.9 and older machine types to force rev1
s
It works when I replace /usr/bin/qemu-nbd with qemu-nbd which I just built
from qemu github.
2017-07-21 17:26 GMT+08:00 Fam Zheng :
> On Fri, 07/21 10:15, Peter Maydell wrote:
> > On 21 July 2017 at 05:10, Fam Zheng wrote:
> > > On Thu, 07/20 19:06, 陳培泓 wrote:
> > >> I build qemu from the https:
Richard Henderson writes:
> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>> +# so they can still be linked when needed. We build these files surpressing
>> so of the normal CFLAGS.
>
> "surpressing so" -> "suppressing some"
>
> Do we gain any confidence for our still supported but less tested
> 3
On Fri, Jul 21, 2017 at 05:31:04PM +0800, 陳培泓 wrote:
> It works after I replace the /usr/bin/qemu-nbd with binary I built.
>
> My cmd is :
>
> > qemu-nbd --object secret,id=sec0,file=passwd.txt,format=raw \
> > --image-opts driver=qcow2,file.filename=
> > demo.qcow2,encrypt.format=lu
On 07/21/2017 11:27 AM, Dr. David Alan Gilbert wrote:
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
* Peter Maydell (peter.mayd...@linaro.org) wrote:
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
* Edgar E. Iglesias
Richard Henderson writes:
> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>> +for (pass = 0; pass < elements; pass++) {
>> +TCGv_i32 tcg_op1 = tcg_temp_new_i32();
>> +TCGv_i32 tcg_res = tcg_temp_new_i32();
>> +
>> +read_vec_element_i32(s, tcg_op1, rn, pass, MO_16);
>> +
There is not much getting started documentation for qemu-iotests. This
patch explains how to create a new test and covers the overall testing
approach.
Cc: Ishani Chugh
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/README | 83 +++
1 file cha
On 07/21/2017 11:29 AM, Peter Maydell wrote:
On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
I don't fully understand the way memory_region_do_invalidate_mmio_ptr
works; I see it dropping the memory region; if that's also dropping
the RAMBlock then it will upset migration. Even if t
On 20.07.2017 17:04, Alex Bennée wrote:
> SoftFloat3c is a re-write of the BSD softfloat library which includes
> a number of new features. It has been written with libraries in mind
> and has a new API so hopefully we can use both side-by-side as we
> migrate.
>
> Signed-off-by: Alex Bennée
> --
oh Maybe the version is something wrong?
qemu-img -V
> qemu-img version 2.9.0
qemu-nbd -V
> qemu-nbd version 0.0.1
They're not correspondent?
2017-07-21 17:34 GMT+08:00 Daniel P. Berrange :
> On Fri, Jul 21, 2017 at 05:31:04PM +0800, 陳培泓 wrote:
> > It works after I replace the /usr/bin/qem
Peter Maydell writes:
> On 21 July 2017 at 09:56, Alex Bennée wrote:
>> One thing playing in my mind against moving to SoftFloat3c is the
>> inscrutability of the upstream. It's nice there has been a new release
>> with new features but there isn't a source repository or as far as I can
>> tell
On Fri, 21 Jul 2017 10:20:26 +0100
"Daniel P. Berrange" wrote:
> On Thu, Jul 20, 2017 at 09:29:33PM +0200, Phil Dennis-Jordan wrote:
> > On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
> > wrote:
> > > I noticed that Windows 2000 does not boot up in QEMU recently. After
> > > bisecting the is
* Jay Zhou (jianjay.z...@huawei.com) wrote:
> Qemu_savevm_state_cleanup() takes about 300ms in my ram migration tests
> with a 8U24G vm(20G is really occupied), the main cost comes from
> KVM_SET_USER_MEMORY_REGION ioctl when mem.memory_size = 0 in
> kvm_set_user_memory_region(). In kmod, the main
On Fri, Jul 21, 2017 at 11:32:11AM +0200, Igor Mammedov wrote:
> w2k used to boot on QEMU until we bumped revision of FADT to rev3
> (commit 77af8a2b hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to improve
> guest OS support.)
>
> Considering that w2k is ancient and long time EOLed, leave de
On 07/21/17 02:56 -0400, Pankaj Gupta wrote:
>
> Hello,
>
> We shared a proposal for 'KVM fake DAX flushing interface'.
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg02478.html
>
In above link,
"Overall goal of project
is to increase the number of virtual machines that can
On Fri, Jul 21, 2017 at 11:32 AM, Igor Mammedov wrote:
> w2k used to boot on QEMU until we bumped revision of FADT to rev3
> (commit 77af8a2b hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to improve
> guest OS support.)
>
> Considering that w2k is ancient and long time EOLed, leave default
>
This implements a testcase for pxe-test using the vhost-user interface. Spawn a
vhost-user-bridge process and connect it to the qemu process.
To make the testcase work we need to apply a few patches before the actual
testcase:
- Patch 1 disables debug output of vhost-user-bridge
- Patch 2 fixes p
This patch fixes -netdev socket,fd= for UDP sockets
Currently -netdev socket,fd=<...> results in
qemu: error: specified mcastaddr "127.0.0.1" (0x7f01) does not
contain a multicast address
qemu-system-x86_64: -netdev
socket,id=n1,fd=3: Device 'socket' could not be initialized
To fi
From: Jens Freimann
End processing of messages when VHOST_USER_NO_MESSAGE
is received.
Without this we run into a vubr_panic() call and get
"PANIC: Unhandled request: 0"
Signed-off-by: Jens Freimann
---
contrib/libvhost-user/libvhost-user.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletio
Richard Henderson writes:
> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>> +static softfloat_flags softfloat_mapping_table[] = {
>> +{ float_flag_inexact , softfloat_flag_inexact },
>> +{ float_flag_underflow, softfloat_flag_underflow },
>> +{ float_flag_overflow , softfloat_flag_ove
Richard Henderson writes:
> On 07/20/2017 05:04 AM, Alex Bennée wrote:
>> This brings in the initial decode skeleton and the helpers for a
>> scalar half-precision fadd using SoftFloat3c.
>>
>> Signed-off-by: Alex Bennée
>> ---
>> target/arm/advsimd_helper.c | 15
>> target/arm/t
Thomas Huth writes:
> On 20.07.2017 17:04, Alex Bennée wrote:
>> SoftFloat3c is a re-write of the BSD softfloat library which includes
>> a number of new features. It has been written with libraries in mind
>> and has a new API so hopefully we can use both side-by-side as we
>> migrate.
>>
>> Si
From: Jens Freimann
vhost-user-bridge prints out a lot of information, including dumps
of all transmitted data. When called from a testcase this output
clutters the actual test results, so let's make the default no debug
output.
Reviewed-by: Maxime Coquelin
Signed-off-by: Jens Freimann
---
te
From: Jens Freimann
Add a PXE testcase tunneling traffic through vhost-user-bridge process.
Create a vhost-user-bridge process and connect it to qemu via a socket.
Signed-off-by: Jens Freimann
---
tests/Makefile.include | 4 +-
tests/pxe-test.c | 140 ++
Hi,
> > What about window sizes? IIRC there was a plan to provide
> > allocation
> > hints for them too ...
>
> Yes, is in my TODO list, however not as part of Aleksandr's series
> which aims to provide PCIe-PCI bridge hotplug support.
I'd prefer to have a single vendor capability for all res
On Fri, 21 Jul 2017 10:49:55 +0100
"Daniel P. Berrange" wrote:
> On Fri, Jul 21, 2017 at 11:32:11AM +0200, Igor Mammedov wrote:
> > w2k used to boot on QEMU until we bumped revision of FADT to rev3
> > (commit 77af8a2b hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to
> > improve guest OS sup
On Fri, 21 Jul 2017 11:54:20 +0200
Ladi Prosek wrote:
> On Fri, Jul 21, 2017 at 11:32 AM, Igor Mammedov wrote:
> > w2k used to boot on QEMU until we bumped revision of FADT to rev3
> > (commit 77af8a2b hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to
> > improve guest OS support.)
> >
> > C
On Fri, Jul 21, 2017 at 12:10:48PM +0200, Igor Mammedov wrote:
> On Fri, 21 Jul 2017 10:49:55 +0100
> "Daniel P. Berrange" wrote:
>
> > On Fri, Jul 21, 2017 at 11:32:11AM +0200, Igor Mammedov wrote:
> > > w2k used to boot on QEMU until we bumped revision of FADT to rev3
> > > (commit 77af8a2b hw/
It is reported that on Windows Subsystem for Linux, ofd operations fail
with -EINVAL. In other words, QEMU binary built with system headers that
exports F_OFD_SETLK doesn't necessarily run in an environment that
actually supports it:
$ qemu-system-aarch64 ... -drive file=test.vhdx,if=none,id=hd0 \
Build time check of OFD lock is not sufficient and can cause image open
errors when the runtime environment doesn't support it.
Add a helper function to probe it at runtime, additionally. Also provide
a qemu_has_ofd_lock() for callers to check the status.
Signed-off-by: Fam Zheng
---
include/qe
This fixes the image opening failure reported by Andrew Baumann:
> 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
> >
> > Hello,
> >
> > We shared a proposal for 'KVM fake DAX flushing interface'.
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg02478.html
> >
>
> In above link,
> "Overall goal of project
>is to increase the number of virtual machines that can be
>run on a physic
On 20 July 2017 at 19:26, Eric Blake wrote:
> On 07/20/2017 11:32 AM, Peter Maydell wrote:
>> On NetBSD the compiler warns:
>> util/oslib-posix.c: In function 'sigaction_invoke':
>> util/oslib-posix.c:589:5: warning: missing braces around initializer
>> [-Wmissing-braces]
>> siginfo_t si = {
On 20 July 2017 at 17:31, Peter Maydell wrote:
> On NetBSD, where tolower() and toupper() are implemented using an
> array lookup, the compiler warns if you pass a plain 'char'
> to these functions:
>
> gdbstub.c:914:13: warning: array subscript has type 'char'
>
> This reflects the fact that toup
On 18 July 2017 at 17:26, Peter Maydell wrote:
> I've just managed to get an OpenBSD VM into my test set for processing
> pull requests. There are a handful of minor compiler warnings in
> bsd-user, which this patchset fixes, just to reduce the noise
> in my logs.
>
> thanks
> -- PMM
>
> Peter May
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
> > I don't fully understand the way memory_region_do_invalidate_mmio_ptr
> > works; I see it dropping the memory region; if that's also dropping
> > the RAMBlock then it will upset migratio
On Fri, Jul 21, 2017 at 11:46 AM, Igor Mammedov wrote:
> On Fri, 21 Jul 2017 10:20:26 +0100
> "Daniel P. Berrange" wrote:
>
>> On Thu, Jul 20, 2017 at 09:29:33PM +0200, Phil Dennis-Jordan wrote:
>> > On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
>> > wrote:
>> > > I noticed that Windows 2000 d
On Fri, 21 Jul 2017, Igor Mammedov wrote:
On Fri, 21 Jul 2017 10:20:26 +0100
"Daniel P. Berrange" wrote:
On Thu, Jul 20, 2017 at 09:29:33PM +0200, Phil Dennis-Jordan wrote:
On Thu, Jul 20, 2017 at 6:40 PM, Programmingkid
wrote:
I noticed that Windows 2000 does not boot up in QEMU recently. A
A cut-and-paste error meant that instead of setting the
qdev parent bus for the SCC device we were setting it
twice for the ARMv7M container device. Fix this bug.
Signed-off-by: Peter Maydell
---
hw/arm/mps2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/arm/mps2.c b/hw
On Fri, Jul 21, 2017 at 11:58 AM Jens Freimann wrote:
> From: Jens Freimann
>
> End processing of messages when VHOST_USER_NO_MESSAGE
> is received.
>
>
What is VHOST_USER_NO_MESSAGE?
> Without this we run into a vubr_panic() call and get
> "PANIC: Unhandled request: 0"
>
> Signed-off-by: Jens
Peter Xu wrote:
> On Mon, Jul 17, 2017 at 03:42:38PM +0200, Juan Quintela wrote:
>> Each time that we sync the bitmap, it is a possiblity that we receive
>> a page that is being processed by a different thread. We fix this
>> problem just making sure that we wait for all receiving threads to
>> f
On 18.07.2017 18:26, Peter Maydell wrote:
> On OpenBSD the compiler complains:
> bsd-user/bsdload.c:54:17: warning: variable 'id_change' set but not used
> [-Wunused-but-set-variable]
>
> This is dead code that was originally copied from linux-user.
> We fixed this in linux-user in commit 331c23b
On Wed, Jul 19, 2017 at 09:39:54AM -0400, Andrew Jones wrote:
> Mimicking gicv3-maintenance-interrupt, add the PMU's interrupt to
> CPU state.
>
> Signed-off-by: Andrew Jones
> Reviewed-by: Peter Maydell
> ---
> hw/arm/virt.c| 3 +++
> target/arm/cpu.c | 2 ++
> target/arm/cpu.h | 2 ++
> 3
On 19.07.2017 10:19, Peter Maydell wrote:
> On 18 July 2017 at 23:01, Eric Blake wrote:
>> On 07/18/2017 11:26 AM, Peter Maydell wrote:
>>> On OpenBSD the compiler warns:
>>> bsd-user/main.c:622:21: warning: variable 'sig' set but not used
>>> [-Wunused-but-set-variable]
>>>
>>> This is because a
Hi
On Fri, Jul 21, 2017 at 7:18 AM w00273186 wrote:
> From: Yunjian Wang
>
> "nc" is freed after hotplug vhost-user, but the watcher don't be removed.
> The QEMU crash when the watcher access the "nc" on socket disconnect.
>
>
This is actually your 3rd iteration on the patch
Could your describ
On 07/21/2017 03:57 AM, David Gibson wrote:
On Fri, Jul 21, 2017 at 10:21:06AM +0530, Bharata B Rao wrote:
Commit 0cffce56 (hw/ppc/spapr.c: adding pending_dimm_unplugs to
sPAPRMachineState) introduced a new way to track pending LMBs of DIMM
device that is marked for removal. Since this commit
On Wed, Jul 19, 2017 at 09:39:55AM -0400, Andrew Jones wrote:
> When adding a PMU with a userspace irqchip we skip the set-irq
> stage of device creation. Split the 'create' function into two
> functions 'init' and 'set-irq' so they may be called separately.
>
> Signed-off-by: Andrew Jones
Revie
On Wed, Jul 19, 2017 at 09:39:56AM -0400, Andrew Jones wrote:
> Move the in-kernel-irqchip test to only guard the set-irq
> stage, not the init stage of the PMU. Also add the PMU to
> the KVM device irq line synchronization to enable its use.
>
> Signed-off-by: Andrew Jones
Reviewed-by: Christo
On Wed, Jul 19, 2017 at 09:39:57AM -0400, Andrew Jones wrote:
> If a KVM PMU init or set-irq attr call fails we just silently stop
> the PMU DT node generation. The only way they could fail, though,
> is if the attr's respective KVM has-attr call fails. But that should
> never happen if KVM adverti
On Fri, Jul 21, 2017 at 01:16:07PM +0200, Christoffer Dall wrote:
> On Wed, Jul 19, 2017 at 09:39:54AM -0400, Andrew Jones wrote:
> > Mimicking gicv3-maintenance-interrupt, add the PMU's interrupt to
> > CPU state.
> >
> > Signed-off-by: Andrew Jones
> > Reviewed-by: Peter Maydell
> > ---
> > h
On Fri, Jul 21, 2017 at 10:59:23AM +, Marc-André Lureau wrote:
On Fri, Jul 21, 2017 at 11:58 AM Jens Freimann wrote:
From: Jens Freimann
End processing of messages when VHOST_USER_NO_MESSAGE
is received.
What is VHOST_USER_NO_MESSAGE?
I meant VHOST_USER_NONE. Will fix in next versio
On Fri, Jul 21, 2017 at 12:50 PM, BALATON Zoltan wrote:
> On Fri, 21 Jul 2017, Igor Mammedov wrote:
>>
>> On Fri, 21 Jul 2017 10:20:26 +0100
>> "Daniel P. Berrange" wrote:
>>>
>>> On Thu, Jul 20, 2017 at 09:29:33PM +0200, Phil Dennis-Jordan wrote:
On Thu, Jul 20, 2017 at 6:40 PM, Progra
Peter, thanks for feedback. Diana will return from vacation next week,
I am trying clarify some of the questions.
>From: Peter Maydell
>Sent: Monday, July 10, 2017 8:10 PM
>To: Diana Madalina Craciun
>Cc: QEMU Developers; Michael S. Tsirkin; Eric Auger; Mike Caraman; qemu-arm;
>Marcel Apfelbaum;
The test-io-channel-tls test was mistakenly using two of the
same directories as test-crypto-tlssession. This causes a
sporadic failure when using make -j$BIGNUM.
Reported-by: Dr. David Alan Gilbert
Signed-off-by: Daniel P. Berrange
---
tests/test-io-channel-tls.c | 4 ++--
1 file changed, 2 in
* Daniel P. Berrange (berra...@redhat.com) wrote:
> The test-io-channel-tls test was mistakenly using two of the
> same directories as test-crypto-tlssession. This causes a
> sporadic failure when using make -j$BIGNUM.
>
> Reported-by: Dr. David Alan Gilbert
> Signed-off-by: Daniel P. Berrange
>
Am 21.07.2017 um 12:20 hat Fam Zheng geschrieben:
> This fixes the image opening failure reported by Andrew Baumann:
>
> > 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
On Fri, Jul 21, 2017 at 01:35:46PM +0200, Andrew Jones wrote:
> On Fri, Jul 21, 2017 at 01:16:07PM +0200, Christoffer Dall wrote:
> > On Wed, Jul 19, 2017 at 09:39:54AM -0400, Andrew Jones wrote:
> > > Mimicking gicv3-maintenance-interrupt, add the PMU's interrupt to
> > > CPU state.
> > >
> > > S
On 07/21/2017 01:42 AM, Markus Armbruster wrote:
>> But with json-lexer style, %s MODIFIES its input.
>
> Your assertion "MODIFIES its input" confused me briefly, because I read
> it as "side effect on the argument string". That would be bonkers.
> What you mean is it doesn't emit the argument st
On 07/21/2017 03:21 AM, Mark Cave-Ayland wrote:
> Since commit cfc87e00 "block/vpc.c: Handle write failures in
> get_image_offset()" older versions of gcc (in this case 4.7) incorrectly
> warn that "ret" can be used uninitialised in vpc_co_pwritev().
>
> Setting ret to 0 at the start of vpc_co_pwr
On Fri, Jul 21, 2017 at 02:56:34AM -0400, Pankaj Gupta wrote:
> A] Problems to solve:
> --
>
> 1] We are considering two approaches for 'fake DAX flushing interface'.
>
> 1.1] fake dax with NVDIMM flush hints & KVM async page fault
>
> - Existing interface.
>
> -
On Fri, Jul 21, 2017 at 09:21:05AM +0100, Mark Cave-Ayland wrote:
> Since commit cfc87e00 "block/vpc.c: Handle write failures in
> get_image_offset()" older versions of gcc (in this case 4.7) incorrectly
> warn that "ret" can be used uninitialised in vpc_co_pwritev().
>
> Setting ret to 0 at the s
On 21/07/2017 13:04, Gerd Hoffmann wrote:
Hi,
What about window sizes? IIRC there was a plan to provide
allocation
hints for them too ...
Yes, is in my TODO list, however not as part of Aleksandr's series
which aims to provide PCIe-PCI bridge hotplug support.
I'd prefer to have a single
1 - 100 of 306 matches
Mail list logo
