On Thu, Apr 05, 2018 at 03:56:36PM +0200, Greg Kurz wrote:
> On Thu, 5 Apr 2018 12:20:01 +1000
> David Gibson wrote:
>
> > qemu_mempath_getpagesize() gets the effective (host side) page size for
> > a block of memory backed by an mmap()ed file on the host. It requires
> > the mem_path parameter
On 05.04.2018 17:07, Viktor Mihajlovski wrote:
> Splitting out the the CCW device extraction allows reuse.
>
> Signed-off-by: Viktor Mihajlovski
> ---
> hw/s390x/ipl.c | 81
> --
> 1 file changed, 51 insertions(+), 30 deletions(-)
>
> dif
Am 05.04.2018 um 19:06 hat Kevin Wolf geschrieben:
> The legacy command line syntax supports a "password-secret" option that
> allows to pass an authentication key to Ceph. This was not supported in
> QMP so far.
>
> This patch introduces authentication options in the QAPI schema, makes
> them do
On Thu, 5 Apr 2018 10:35:21 -0400
Serhii Popovych wrote:
> Now PowerPC Linux kernel supports hot-add to NUMA nodes not populated
> initially with memory we can enable such support in qemu. This requires
> two changes:
>
> o Add device tree property "ibm,max-associativity-domains" to let
>
On 05.04.2018 17:07, Viktor Mihajlovski wrote:
> Operating systems may request an IPL from a virtio-scsi device
> by specifying an IPL parameter type of CCW. In this case QEMU
> won't set up the IPLB correctly. The BIOS will still detect
> it's a SCSI device to boot from, but it will now have to se
On Thu, 5 Apr 2018 19:17:47 +0200
Halil Pasic wrote:
> On 04/05/2018 06:38 PM, Tony Krowiak wrote:
> >> Hard to really give good advice without access to the documentation, but:
> >> - If we tell the guest that the feature is available, but it does not
> >> get any cards to use, returning an e
On 5 April 2018 at 21:31, Paolo Bonzini wrote:
> On 28/03/2018 15:31, Laurent Vivier wrote:
>> configure tries to detect if the compiler
>> supports 16-byte vector operations.
>>
>> As stated in the comment of the detection
>> program, there is a problem with the system
>> compiler on GCC on Cento
Hi,
> > * The general interface should be able to express sharing from any
> > guest:guest, not just guest:host. Arbitrary G:G sharing might be
> > something some hypervisors simply aren't able to support, but the
> > userspace API itself shouldn't make assumptions or restrict tha
On 06.04.2018 10:40, Cornelia Huck wrote:
> On Thu, 5 Apr 2018 19:17:47 +0200
> Halil Pasic wrote:
>
>> On 04/05/2018 06:38 PM, Tony Krowiak wrote:
Hard to really give good advice without access to the documentation, but:
- If we tell the guest that the feature is available, but it does
On 05.04.2018 17:07, Viktor Mihajlovski wrote:
> IPL over a virtio-scsi device requires special handling not
> available in the real architecture. For this purpose the IPL
> type 0xFF has been chosen as means of communication between
> QEMU and the pc-bios. However, a guest OS could be confused
> b
Hi,
> The pages backing a DMA-buf are not allowed to move (at least not without a
> patch set I'm currently working on), but for certain MM operations to work
> correctly you must be able to modify the page tables entries and move the
> pages backing them around.
>
> For example try to use fork
On Fri, 6 Apr 2018 09:52:35 +0200
Thomas Huth wrote:
> On 05.04.2018 17:07, Viktor Mihajlovski wrote:
> > Splitting out the the CCW device extraction allows reuse.
> >
> > Signed-off-by: Viktor Mihajlovski
> > ---
> > hw/s390x/ipl.c | 81
> > ---
On 04/06/2018 12:07 PM, Gerd Hoffmann wrote:
Hi,
* The general interface should be able to express sharing from any
guest:guest, not just guest:host. Arbitrary G:G sharing might be
something some hypervisors simply aren't able to support, but the
userspace API itself shoul
Manually having to use cpu_synchronize_state() is error prone. And as
Christian Borntraeger discovered, e.g. handle_diag() is currently
missing a cpu_synchronize_state(), as decode_basedisp_s() uses a
general purpose register value internally.
So let's do an overall cpu_synchronize_state(), which
On 5 April 2018 at 15:22, Peter Maydell wrote:
> On 29 March 2018 at 11:54, Peter Maydell wrote:
>> On 23 March 2018 at 12:08, Peter Maydell wrote:
>>> On 21 March 2018 at 08:00, Shannon Zhao wrote:
On 2018/3/20 19:54, Peter Maydell wrote:
> Can you still successfully migrate a VM from
On 06.04.2018 11:35, David Hildenbrand wrote:
> Manually having to use cpu_synchronize_state() is error prone. And as
> Christian Borntraeger discovered, e.g. handle_diag() is currently
> missing a cpu_synchronize_state(), as decode_basedisp_s() uses a
> general purpose register value internally.
>
On 5 April 2018 at 22:23, wrote:
> "Peter Maydell" wrote on 04/05/2018 12:28:01
> PM:
>
>> From: "Peter Maydell"
>> To: alar...@ddci.com
>> Cc: "QEMU Developers"
>> Date: 04/05/2018 12:28 PM
>> Subject: Re: [Qemu-devel] -icount changes physical address assignments
> in QEMU 2.10/2.11
>>
>> On
On Fri, 6 Apr 2018 11:28:31 +0200
Thomas Huth wrote:
> On 05.04.2018 17:07, Viktor Mihajlovski wrote:
> > IPL over a virtio-scsi device requires special handling not
> > available in the real architecture. For this purpose the IPL
> > type 0xFF has been chosen as means of communication between
>
On 06.04.2018 11:40, Thomas Huth wrote:
> On 06.04.2018 11:35, David Hildenbrand wrote:
>> Manually having to use cpu_synchronize_state() is error prone. And as
>> Christian Borntraeger discovered, e.g. handle_diag() is currently
>> missing a cpu_synchronize_state(), as decode_basedisp_s() uses a
>
On Thu, 5 Apr 2018 17:07:21 +0200
Viktor Mihajlovski wrote:
> IPL from virtio-scsi currently uses a non-standard parameter
> type definition to pass boot parameters from QEMU to the
> BIOS.
>
> There are two potential issues with this approach:
> o If the guest operating systems requests a re-i
On Fri, 6 Apr 2018 11:46:22 +0200
David Hildenbrand wrote:
> On 06.04.2018 11:40, Thomas Huth wrote:
> > On 06.04.2018 11:35, David Hildenbrand wrote:
> >> Manually having to use cpu_synchronize_state() is error prone. And as
> >> Christian Borntraeger discovered, e.g. handle_diag() is currentl
On 04/06/2018 11:35 AM, David Hildenbrand wrote:
> Manually having to use cpu_synchronize_state() is error prone. And as
> Christian Borntraeger discovered, e.g. handle_diag() is currently
> missing a cpu_synchronize_state(), as decode_basedisp_s() uses a
> general purpose register value internal
Hello!
In the qemu source tarball, roms/skiboot/ can't be built due to a trivial
error: the directory lacks expected-to-be-there .version file, which can
be built using roms/skiboot/make_version.sh script (which actually just
runs git --describe). However it is impossible to create from the
tarbal
On 06/04/2018 01:10, Daniel Henrique Barboza wrote:
> Yet another fix is to fully prohibit the user to set scsi_version
> scsi-block and scsi-generic cases, returning an error message right off
> the start. Not sure how hard this would be - perhaps the above
> alternatives are cleaner.
>
> Another
Am 06.04.2018 um 11:41 schrieb Peter Maydell:
> On 5 April 2018 at 22:23, wrote:
>> Linux "works". I installed ubuntu 17.10 in a VM on my windows box,
>> recompiled QEMU 2.12.0-rc2 (same sources as above), using a configure
>> line the same as above except omitting --cross-prefix and --with-sdlab
On 06.04.2018 11:28, Thomas Huth wrote:
> On 05.04.2018 17:07, Viktor Mihajlovski wrote:
>> IPL over a virtio-scsi device requires special handling not
>> available in the real architecture. For this purpose the IPL
>> type 0xFF has been chosen as means of communication between
>> QEMU and the pc-b
02.04.2018 17:30, BALATON Zoltan wrote:
> On Mon, 2 Apr 2018, Michael Tokarev wrote:
>> roms/u-boot-sam460ex/tools/updater/stubs.c -
>> it is some strange symlink pointing to a strange place, probably should be
>> removed?
>
> This does not seem to matter for building the rom image but this can b
On Fri, Apr 06, 2018 at 10:52:21AM +0100, Daniel Stone wrote:
> Hi Gerd,
>
> On 14 March 2018 at 08:03, Gerd Hoffmann wrote:
> >> Either mlock account (because it's mlocked defacto), and get_user_pages
> >> won't do that for you.
> >>
> >> Or you write the full-blown userptr implementation, inclu
On 04/05/2018 05:07 PM, Viktor Mihajlovski wrote:
> IPL over a virtio-scsi device requires special handling not
> available in the real architecture. For this purpose the IPL
> type 0xFF has been chosen as means of communication between
> QEMU and the pc-bios. However, a guest OS could be confuse
02.04.2018 17:30, BALATON Zoltan wrote:
> On Mon, 2 Apr 2018, Michael Tokarev wrote:
>> roms/u-boot-sam460ex/tools/updater/stubs.c -
>> it is some strange symlink pointing to a strange place, probably should be
>> removed?
>
> This does not seem to matter for building the rom image but this can b
On Fri, 6 Apr 2018 11:35:52 +0200
David Hildenbrand wrote:
> Manually having to use cpu_synchronize_state() is error prone. And as
> Christian Borntraeger discovered, e.g. handle_diag() is currently
> missing a cpu_synchronize_state(), as decode_basedisp_s() uses a
> general purpose register val
On 04/06/2018 12:07 PM, Gerd Hoffmann wrote:
I'm not sure we can create something which works on both kvm and xen.
The memory management model is quite different ...
On xen the hypervisor manages all memory. Guests can allow other guests
to access specific pages (using grant tables). In theor
On 06/04/2018 07:34, Michael Chapman wrote:
> When migrating from a pre-2.9 QEMU, no clock_is_reliable flag is
> transferred. We should assume that the source host has an unreliable
> KVM_GET_CLOCK, rather than using whatever was determined locally, to
> ensure that any drift from the TSC-based val
On 05/04/2018 14:55, Stefan Hajnoczi wrote:
> bdrv_copy_file_range() will invoke bdrv_co_copy_file_range_src() on
> src[qcow2]. The qcow2 block driver will invoke
> bdrv_co_copy_file_range_src() on src[file]. The file-posix driver will
> invoke bdrv_co_copy_file_range_dst() on dst[raw]. The raw
On Fri, 6 Apr 2018, Michael Tokarev wrote:
02.04.2018 17:30, BALATON Zoltan wrote:
On Mon, 2 Apr 2018, Michael Tokarev wrote:
roms/u-boot-sam460ex/tools/updater/stubs.c -
it is some strange symlink pointing to a strange place, probably should be
removed?
This does not seem to matter for buil
Hi,
> > I fail to see any common ground for xen-zcopy and udmabuf ...
> Does the above mean you can assume that xen-zcopy and udmabuf
> can co-exist as two different solutions?
Well, udmabuf route isn't fully clear yet, but yes.
See also gvt (intel vgpu), where the hypervisor interface is abs
On Fri, 6 Apr 2018, Michael Tokarev wrote:
02.04.2018 17:30, BALATON Zoltan wrote:
On Mon, 2 Apr 2018, Michael Tokarev wrote:
roms/u-boot-sam460ex/tools/updater/stubs.c -
it is some strange symlink pointing to a strange place, probably should be
removed?
This does not seem to matter for buil
On 04/05/2018 01:11 AM, Emilio G. Cota wrote:
> This paves the way for upcoming work.
>
> Cc: Bastian Koppelmann
> Reviewed-by: Alex Bennée
> Signed-off-by: Emilio G. Cota
> ---
> include/fpu/softfloat.h | 20
> 1 file changed, 20 insertions(+)
Reviewed-by: Bastian Koppel
On 04/05/2018 01:11 AM, Emilio G. Cota wrote:
> Cc: Bastian Koppelmann
> Signed-off-by: Emilio G. Cota
> ---
> target/tricore/fpu_helper.c | 9 ++---
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
Reviewed-by: Bastian Koppelmann
Cheers,
Bastian
A guest boot hangs while probing the network interface when
iommu_platform=on is used.
The following qemu cli hangs without this patch:
# $QEMU \
-netdev tap,fd=3,id=hostnet0,vhost=on,vhostfd=4 3<>/dev/tap67
4<>/dev/host-net \
-device
virtio-net-pci,netdev=hostnet0,id=net0,iommu_platform=on
On 04/05/2018 01:11 AM, Emilio G. Cota wrote:
> glibc >= 2.25 defines canonicalize in commit eaf5ad0
> (Add canonicalize, canonicalizef, canonicalizel., 2016-10-26).
>
> Given that we'll be including soon, prepare
> for this by prefixing our canonicalize() with sf_ to avoid
> clashing with the li
On 04/06/2018 07:12 AM, Paolo Bonzini wrote:
On 06/04/2018 01:10, Daniel Henrique Barboza wrote:
Yet another fix is to fully prohibit the user to set scsi_version
scsi-block and scsi-generic cases, returning an error message right off
the start. Not sure how hard this would be - perhaps the ab
On 04/06/2018 11:11 AM, David Hildenbrand wrote:
> On 06.04.2018 10:40, Cornelia Huck wrote:
>> On Thu, 5 Apr 2018 19:17:47 +0200
>> Halil Pasic wrote:
>>
>>> On 04/05/2018 06:38 PM, Tony Krowiak wrote:
> Hard to really give good advice without access to the documentation, but:
> - If we
On 04/05/2018 05:07 PM, Viktor Mihajlovski wrote:
> IPL from virtio-scsi currently uses a non-standard parameter
> type definition to pass boot parameters from QEMU to the
> BIOS.
>
> There are two potential issues with this approach:
> o If the guest operating systems requests a re-ipl of type
On Fri, 6 Apr 2018 14:30:45 +0200
Christian Borntraeger wrote:
> On 04/05/2018 05:07 PM, Viktor Mihajlovski wrote:
> > IPL from virtio-scsi currently uses a non-standard parameter
> > type definition to pass boot parameters from QEMU to the
> > BIOS.
> >
> > There are two potential issues with t
On 04/06/2018 02:09 PM, Halil Pasic wrote:
> Yes it is conceptually ugly. I'm 100% with you. That's why it should go
> away soon. From the practicality perspective however I would even argue that
> it's
> helpful to the user: tells 'oops you have forgotten something'. IMHO
> it's a shortcut of t
On 04/06/2018 02:57 PM, Gerd Hoffmann wrote:
Hi,
I fail to see any common ground for xen-zcopy and udmabuf ...
Does the above mean you can assume that xen-zcopy and udmabuf
can co-exist as two different solutions?
Well, udmabuf route isn't fully clear yet, but yes.
See also gvt (intel vgp
On Fri, Apr 06, 2018 at 02:32:49PM +0200, Halil Pasic wrote:
>
>
> On 04/06/2018 02:09 PM, Halil Pasic wrote:
> > Yes it is conceptually ugly. I'm 100% with you. That's why it should go
> > away soon. From the practicality perspective however I would even argue
> > that it's
> > helpful to the u
When we run in TCG icount mode, we calculate the number of instructions
to execute using tcg_get_icount_limit(), which ensures that we stop
execution at the next timer deadline. However there is a bug where
currently we do not recalculate that limit if the guest reprograms
a timer so that the next
On 5 April 2018 at 19:41, Alex Williamson wrote:
> The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:
>
> Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)
>
> are available in the Git repository at:
>
> git://github.com/awilliam/qemu-vfio.git tags/vf
On 02/17/2018 09:31 PM, Richard Henderson wrote:
> Convert the BREAK instruction to start.
>
> Signed-off-by: Richard Henderson
> ---
> target/hppa/translate.c | 14 +++---
> target/hppa/Makefile.objs | 8
> target/hppa/insns.decode | 24
> 3 files c
On 04/06/2018 10:38 PM, Peter Maydell wrote:
> When we run in TCG icount mode, we calculate the number of instructions
> to execute using tcg_get_icount_limit(), which ensures that we stop
> execution at the next timer deadline. However there is a bug where
> currently we do not recalculate that li
Thanks for the test case; that was very useful. I've sent a patch which should
fix this bug:
https://patchwork.ozlabs.org/patch/895693/
The "writing a reload value smaller than the current counter" bug is one
of the ones I know about in our systick implementation. I may have time
to overhaul that
On 04/06/2018 10:45 PM, Bastian Koppelmann wrote:
>> +break 00 - - --- -
>>
>
> Why are the im13 and im5 fields don't care? Is nobody using them?
The entire insn is placed in CR[IIR] for the kernel to use (distinguishing
different software breaks?), but the
Peter Maydell writes:
> When we run in TCG icount mode, we calculate the number of instructions
> to execute using tcg_get_icount_limit(), which ensures that we stop
> execution at the next timer deadline. However there is a bug where
> currently we do not recalculate that limit if the guest rep
On 6 April 2018 at 13:58, Alex Bennée wrote:
>
> Peter Maydell writes:
>> -if (!qemu_in_vcpu_thread() && first_cpu) {
>> +if (qemu_in_vcpu_thread()) {
>> +/* A CPU is currently running; kick it back out to the
>> + * tcg_cpu_exec() loop so it will recalculate its
>> +
Richard Henderson writes:
> On 04/03/2018 07:26 PM, Alex Bennée wrote:
>> You don't use it yet but probably worth a:
>>
>> static inline int ffr_full_reg_offset(DisasContext *s)
>> {
>> return pred_full_reg_offset(s, 16);
>> }
>>
>> here when you get to it to avoid the magic 16 appearing in
Am 06.04.2018 um 11:33 schrieb Gerd Hoffmann:
Hi,
The pages backing a DMA-buf are not allowed to move (at least not without a
patch set I'm currently working on), but for certain MM operations to work
correctly you must be able to modify the page tables entries and move the
pages backing the
On 04/06/2018 03:11 AM, Matt Roper wrote:
On Thu, Apr 05, 2018 at 10:32:04PM +0200, Daniel Vetter wrote:
Pulling this out of the shadows again.
We now also have xen-zcopy from Oleksandr and the hyper dmabuf stuff
from Matt and Dongwong.
At least from the intel side there seems to be the idea t
Hi Gerd,
On 14 March 2018 at 08:03, Gerd Hoffmann wrote:
>> Either mlock account (because it's mlocked defacto), and get_user_pages
>> won't do that for you.
>>
>> Or you write the full-blown userptr implementation, including mmu_notifier
>> support (see i915 or amdgpu), but that also requires Ch
On 02/17/2018 09:31 PM, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> target/hppa/translate.c | 57
> +---
> target/hppa/insns.decode | 15 +
> 2 files changed, 40 insertions(+), 32 deletions(-)
>
[...]
> @@ -2267,24
Fixes the reported problem w/ ppc64 host (gcc 4.8.5) + aa64 guest.
r~
The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:
Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)
are available in the Git repository at:
git://github.com/rth7680/qemu.git
A mistake in the type passed to sizeof, that happens to work
when the out-of-line fallback itself is using host vectors,
but fails when using only the base types.
Tested-by: Emilio G. Cota
Reported-by: Emilio G. Cota
Signed-off-by: Richard Henderson
---
accel/tcg/tcg-runtime-gvec.c | 2 +-
1 f
Helge Deller has fixed some bios bugs and has asked
that I update qemu thus.
r~
The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:
Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)
are available in the Git repository at:
git://github.com/rth7680
A dozen or so fixes from Helge upstream.
---
pc-bios/hppa-firmware.img | Bin 215696 -> 215936 bytes
roms/seabios-hppa | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/pc-bios/hppa-firmware.img b/pc-bios/hppa-firmware.img
index
d2098f1fd9ffd86554ba66088d462208b7182f0
"Peter Maydell" wrote on 04/06/2018 04:41:01
AM:
> From: "Peter Maydell"
> To: alar...@ddci.com
> Cc: "QEMU Developers" , "Stefan Weil"
> Date: 04/06/2018 04:41 AM
> Subject: Re: [Qemu-devel] -icount changes physical address assignments
in QEMU 2.10/2.11
>
> On 5 April 2018 at 22:23, wrot
The TLS test cert generation relies on a fixed set of algorithms that are
only usable under GNUTLS' default priority setting. When building QEMU
with a custom distro specific priority setting, this can cause the TLS
tests to fail. By forcing the tests to always use "NORMAL" priority we
can make the
The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:
Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)
are available in the Git repository at:
https://github.com/berrange/qemu tags/qcrypto-next-pull-request
for you to fetch changes up to 057ad0b46992
From: Christophe Fergeau
This was added in 13f1243, but is missing from qemu-options.hx
Signed-off-by: Christophe Fergeau
Signed-off-by: Daniel P. Berrangé
---
qemu-options.hx | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
ind
On 6 April 2018 at 14:28, wrote:
> "Peter Maydell" wrote:
>> On 5 April 2018 at 22:23, wrote:
>> > I installed a fresh Cygwin with just the packages suggested at
>> > https://wiki.qemu.org/Hosts/W32#Native_builds_with_Mingw-w64 (plus
>> > some obviously missing ones like python, make, etc.) an
From: "Daniel P. Berrange"
The current docs for TLS assume only VNC is using TLS. Some of the information
is also outdated (ie lacking subject alt name info for certs). Rewrite it to
more accurately reflect the current situation.
Reviewed-by: Eric Blake
Reviewed-by: Kashyap Chamarthy
Signed-of
On 04/06/2018 11:14 PM, Bastian Koppelmann wrote:
> On 02/17/2018 09:31 PM, Richard Henderson wrote:
>> Signed-off-by: Richard Henderson
>> ---
>> target/hppa/translate.c | 57
>> +---
>> target/hppa/insns.decode | 15 +
>> 2 files changed
The 'vlan' term caused a lot of confusion and misconfigurations in the
past. The parameter has been marked as deprecated since QEMU v2.9.0, so
it's now time to finally remove the parameter and use the better word "hub"
in the remaining spots that actually mean the QEMU emulated hub feature.
v2:
-
It's been marked as deprecated since QEMU v2.9.0, so that should have
been enough time for everybody to switch to the modern -device + -netdev
syntax for connecting guest NICs with host network backends, or to switch
to the "hubport" netdev in case hubs are really wanted instead.
Buglink: https://
'vlan' is very confusing since it does not mean something like IEEE
802.1Q, but rather emulated hubs, so let's switch to that terminology
instead. While we're at it, move the subsection about hub a little bit
downward in the documentation (it's not as important anymore as it was
before the inventio
'vlan' is very confusing since it does not mean something like IEEE
802.1Q, but rather emulated hubs, so let's switch to that terminology
instead.
Buglink: https://bugs.launchpad.net/qemu/+bug/658904
Signed-off-by: Thomas Huth
---
net/hub.c | 7 +++
net/slirp.c | 8
net/tap.c |
On 04/06/2018 03:33 PM, Richard Henderson wrote:
> On 04/06/2018 11:14 PM, Bastian Koppelmann wrote:
>> On 02/17/2018 09:31 PM, Richard Henderson wrote:
>>> Signed-off-by: Richard Henderson
>>> ---
>>> target/hppa/translate.c | 57
>>> +---
>>> target
On 02/17/2018 09:31 PM, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> target/hppa/translate.c | 92
> ++--
> target/hppa/insns.decode | 12 +++
> 2 files changed, 55 insertions(+), 49 deletions(-)
>
Reviewed-by: Bastian Kop
On 16/03/2018 00:24, Tony Krowiak wrote:
If the CPU model indicates that AP facility is installed on
the guest (i.e., -cpu ,ap=on), then the expectation is that
the AP bus running in the guest will initialize; however, if the
AP instructions are not being interpreted by the firmware, then
the
Hi Peter,
I just tested your patch, I confirm it is also working on my side. Many
thanks.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1754038
Title:
ARM M: Systick first wrap delayed (qemu-timer
On 06/04/18 14:28, alar...@ddci.com wrote:
I was not successful with the wiki instructions for "Native builds
with MSYS2":
./qemu-2.12.0-rc2/configure --python=/usr/bin/python2 \
'--with-pkgversion=DDCI QEMU 2.12.0-rc2' \
--prefix=/usr/local/qemu \
'--target-list=aarch64
On 06/04/2018 15:37, Thomas Huth wrote:
> It's been marked as deprecated since QEMU v2.9.0, so that should have
> been enough time for everybody to switch to the modern -device + -netdev
> syntax for connecting guest NICs with host network backends, or to switch
> to the "hubport" netdev in case hu
Could you provide a binary that we can use to reproduce, please?
(preferably a setup that doesn't require me to figure out how to install
and use docker...)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bu
On 05/04/18 10:32, Thomas Huth wrote:
The instance_init function of devices should always succeed to be able
to introspect the device. However, the instance_init function of the
"openprom" device can currently fail, for example like this:
$ echo "{'execute':'qmp_capabilities'}"\
"{'exec
On 05/04/18 11:43, Thomas Huth wrote:
Several devices of the sun4m machines are using &error_fatal in
their instance_init function and thus can cause QEMU to abort
unexpectedly:
$ echo "{'execute':'qmp_capabilities'}"\
"{'execute':'device-list-properties',"\
" 'arguments':{'typen
On 06/04/2018 16:08, Pierre Morel wrote:
On 16/03/2018 00:24, Tony Krowiak wrote:
If the CPU model indicates that AP facility is installed on
the guest (i.e., -cpu ,ap=on), then the expectation is that
the AP bus running in the guest will initialize; however, if the
AP instructions are not b
On 06.04.2018 16:41, Mark Cave-Ayland wrote:
> On 05/04/18 10:32, Thomas Huth wrote:
>
>> The instance_init function of devices should always succeed to be able
>> to introspect the device. However, the instance_init function of the
>> "openprom" device can currently fail, for example like this:
>
On 02/17/2018 09:31 PM, Richard Henderson wrote:
> With decodetree.py, the specializations would conflict so we
> must have a single entry point for all variants of OR.
>
> Signed-off-by: Richard Henderson
> ---
> target/hppa/translate.c | 108
> +++-
On 6 April 2018 at 14:33, Peter Maydell wrote:
> On this end I should try this with a 32-bit Linux host.
I've now done this, and can reproduce the problem. So the
issue is generic to 32-bit hosts.
I'll see if I can figure out what's going wrong. In the
meantime, you can probably work around it b
On 6 April 2018 at 14:14, Richard Henderson
wrote:
> Fixes the reported problem w/ ppc64 host (gcc 4.8.5) + aa64 guest.
>
>
> r~
>
>
> The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:
>
> Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)
>
> are avail
On 16/03/2018 00:24, Tony Krowiak wrote:
A new CPU model feature and two new CPU model facilities are
introduced to support AP devices for a KVM guest.
CPU model features:
1. The KVM_S390_VM_CPU_FEAT_AP CPU model feature indicates that
AP facilities are installed. This feature will be enabl
Signed-off-by: Eugene Minibaev
---
It seems that x86 vector instructions encoded in VEX are not properly
decoded because of missing bit, here is the example:
IN:
0x08048060: c5 f9 6f c1 vmovdqa %xmm1, %xmm0
0x08048064: b8 01 00 00 00 movl $1, %eax
0x08048069: bb 00
On 04/03/2018 01:46 PM, Eric Blake wrote:
> On 03/27/2018 03:21 PM, Eric Blake wrote:
>> gcc 8 on rawhide is picky enough to complain:
>>
>> /home/dummy/qemu/dump.c: In function 'create_header32':
>> /home/dummy/qemu/dump.c:817:5: error: 'strncpy' output truncated before
>> terminating nul copying
On 04/03/2018 01:45 PM, Eric Blake wrote:
> On 03/26/2018 01:41 PM, Eric Blake wrote:
>> The list did not author any patches, but it does rewrite the
>> 'From:' header of messages sent from any domain with restrictive
>> SPF policies that would otherwise prevent the message from reaching
>> all lis
The vfio_ccw_realize() function currently leaks vcdev->vdev.name if
the subchannel is already attached or if vfio_get_device() fails.
This happens because vcdev->vdev.name is expected to be freed in
vfio_put_device() which isn't called in this case.
Adding g_free(vcdev->vdev.name) on these two er
My non-Fedora testing system does not have a kernel with userfaultfd
support which causes 181 and 201 to fail. That is annoying. This
series makes those tests recognize the issue and convert it into a
_notrun.
Max Reitz (2):
iotests: Add failure matching to common.qemu
iotests: Skip 181 and
The new test case for compressed clusters (added in commit
abd3622cc03cf41ed542126a540385f30a4c0175) requires two refcount bits to
succeed, so we need to skip the test when refcount_bits=1 was requested.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/122 | 4
1 file changed, 4 insertions(+
Currently, common.qemu only allows to match for results indicating
success. The only way to fail is by provoking a timeout. However,
sometimes we do have a defined failure output and can match for that,
which saves us from having to wait for the timeout in case of failure.
Because failure can som
Adds --enable-fdpic and --disable-fdpic configure options. This
feature is disabled by default, that's why it is not described in the
"Optional features" help section (which are enabled by default if
possible).
FDPIC ELF objects are identified with e_ident[EI_OSABI] ==
ELFOSABI_ARM_FDPIC.
Co-Aut
userfaultfd support depends on the host kernel, so it may not be
available. If so, 181 and 201 should be skipped.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/181 | 13 +
tests/qemu-iotests/201 | 13 +
2 files changed, 26 insertions(+)
diff --git a/tests/qemu-iotests
1 - 100 of 185 matches
Mail list logo
