On 8/12/22 04:26, Claudio Imbrenda wrote:
On Thu, 11 Aug 2022 23:05:52 -0300
Murilo Opsfelder Araújo wrote:
On 8/11/22 11:02, Daniel P. Berrangé wrote:
[...]
Hmm, I was hoping you could just use SIGKILL to guarantee that this
gets killed off. Is SIGKILL delivered too soon to allow for the
On 8/11/22 11:02, Daniel P. Berrangé wrote:
[...]
Hmm, I was hoping you could just use SIGKILL to guarantee that this
gets killed off. Is SIGKILL delivered too soon to allow for the
main QEMU process to have exited quickly ?
yes, I tried. qemu has not finished exiting when the signal is
delive
Hi, Claudio.
On 8/9/22 03:40, Claudio Imbrenda wrote:
This patch adds support for asynchronously tearing down a VM on Linux.
When qemu terminates, either naturally or because of a fatal signal,
the VM is torn down. If the VM is huge, it can take a considerable
amount of time for it to be cleane
Hi, Daniel, David.
On 7/12/22 10:03, Daniel Henrique Barboza wrote:
On 7/12/22 00:46, David Gibson wrote:
On Mon, Jul 11, 2022 at 04:37:43PM -0300, Murilo Opsfelder Araujo wrote:
Some systems have /proc/device-tree/cpus/../clock-frequency. However,
this is not the expected path for a CPU dev
Hi, Matheus.
On 5/31/22 15:04, Matheus K. Ferst wrote:
On 31/05/2022 14:27, Murilo Opsfelder Araujo wrote:
Update max alias to power10 so users can take advantage of a more
recent CPU model when '-cpu max' is provided.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1038
Cc: Daniel P.
Hi, Daniel.
On 6/1/22 06:59, Daniel Henrique Barboza wrote:
On 6/1/22 06:25, Thomas Huth wrote:
On 01/06/2022 10.38, Greg Kurz wrote:
On Wed, 1 Jun 2022 09:27:31 +0200
Thomas Huth wrote:
On 31/05/2022 19.27, Murilo Opsfelder Araujo wrote:
Update max alias to power10 so users can take adv
Hi, Cédric.
On 6/1/22 04:44, Cédric Le Goater wrote:
On 6/1/22 09:27, Thomas Huth wrote:
On 31/05/2022 19.27, Murilo Opsfelder Araujo wrote:
Update max alias to power10 so users can take advantage of a more
recent CPU model when '-cpu max' is provided.
Resolves: https://gitlab.com/qemu-projec
Hi, Greg.
On 6/1/22 05:38, Greg Kurz wrote:
On Wed, 1 Jun 2022 09:27:31 +0200
Thomas Huth wrote:
On 31/05/2022 19.27, Murilo Opsfelder Araujo wrote:
Update max alias to power10 so users can take advantage of a more
recent CPU model when '-cpu max' is provided.
Resolves: https://gitlab.com/q
Hi, Thomas.
On 6/1/22 04:27, Thomas Huth wrote:
On 31/05/2022 19.27, Murilo Opsfelder Araujo wrote:
Update max alias to power10 so users can take advantage of a more
recent CPU model when '-cpu max' is provided.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1038
Cc: Daniel P. Berrang
Hi, Thomas.
On 5/10/22 04:24, Thomas Huth wrote:
On 06/05/2022 03.16, Murilo Opsfelder Araujo wrote:
When CONFIG_MOS6522 is not set, building ppc64-softmmu target fails:
/usr/bin/ld: libqemu-ppc64-softmmu.fa.p/monitor_misc.c.o:(.data+0x1158):
undefined reference to `hmp_info_via'
Make d
On 5/2/22 06:43, Mark Cave-Ayland wrote:
On 30/04/2022 00:31, Murilo Opsfelder Araujo wrote:
When CONFIG_MOS6522 is not set, building ppc64-softmmu target fails:
/usr/bin/ld: libqemu-ppc64-softmmu.fa.p/monitor_misc.c.o:(.data+0x1158):
undefined reference to `hmp_info_via'
clang-13:
Hi, Mark.
On 5/4/22 11:32, Mark Cave-Ayland wrote:
On 04/05/2022 14:16, Murilo Opsfelder Araújo wrote:
Hi, Mark.
On 5/4/22 04:10, Mark Cave-Ayland wrote:
On 02/05/2022 14:36, Murilo Opsfelder Araújo wrote:
Hi, Mark.
Thanks for reviewing. Comments below.
On 5/2/22 06:43, Mark Cave-Ayland
Hi, Mark.
On 5/4/22 04:10, Mark Cave-Ayland wrote:
On 02/05/2022 14:36, Murilo Opsfelder Araújo wrote:
Hi, Mark.
Thanks for reviewing. Comments below.
On 5/2/22 06:43, Mark Cave-Ayland wrote:
On 30/04/2022 00:31, Murilo Opsfelder Araujo wrote:
When CONFIG_MOS6522 is not set, building
Hi, Mark.
Thanks for reviewing. Comments below.
On 5/2/22 06:43, Mark Cave-Ayland wrote:
On 30/04/2022 00:31, Murilo Opsfelder Araujo wrote:
When CONFIG_MOS6522 is not set, building ppc64-softmmu target fails:
/usr/bin/ld: libqemu-ppc64-softmmu.fa.p/monitor_misc.c.o:(.data+0x1158):
un
Hi, Philippe.
On Monday, March 14, 2022 10:47:11 AM -03 Philippe Mathieu-Daudé wrote:
> On 11/3/22 23:16, Murilo Opsfelder Araujo wrote:
> > Building QEMU on Fedora 37 (Rawhide Prerelease) ppc64le failed with the
> > following error:
> >
> > $ ../configure --prefix=/usr/local/qemu-disabletcg
Hi, Markus.
On 3/11/22 06:33, Markus Armbruster wrote:
Murilo Opsfelder Araujo writes:
Building QEMU on Fedora 37 (Rawhide Prerelease) ppc64le failed with the
following error:
$ ../configure --prefix=/usr/local/qemu-disabletcg
--target-list=ppc-softmmu,ppc64-softmmu --disable-tcg --dis
On 3/10/22 15:30, Daniel Henrique Barboza wrote:
Hi,
These are more test fixes that I missed from my first series [1]. Thanks
Murilo Opsfelder and Fabiano for letting me know that we still had broken
tests to deal with.
All these tests were either a case of 'this needs kvm_pr' or 'this needs
kv
On Tuesday, January 26, 2021 2:10:55 PM -03 Cédric Le Goater wrote:
> The current settings are useful to load large kernels (with debug) but
> it moves the initrd image in a memory region not protected by
> skiboot. If skiboot is compiled with DEBUG=1, memory poisoning will
> corrupt the initrd.
>
Bonjour, Cédric.
On Tuesday, January 26, 2021 2:10:55 PM -03 Cédric Le Goater wrote:
> The current settings are useful to load large kernels (with debug) but
> it moves the initrd image in a memory region not protected by
> skiboot. If skiboot is compiled with DEBUG=1, memory poisoning will
> corr
Thank you for verifying, Satheesh.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866962
Title:
[Regression]Powerpc kvm guest unable to start
This issue seems to be fixed by
commit 78b3f67acdf0f646d35ebdf98b9e91fb04ab9a07
Author: Paolo Bonzini
Date: Tue Mar 10 18:58:30 2020 +0100
oslib-posix: initialize mutex and condition variable
The mutex and condition variable were never initialized, causing
-mem-prealloc to abort with an asser
On Thursday, March 5, 2020 11:29:40 AM -03 David Hildenbrand wrote:
> When shrinking a mmap we want to re-reserve the already activated area.
> When growing a memory region, we want to activate starting with a given
> fd_offset. Prepare by allowing to pass these parameters.
>
> Also, let's make sur
On Thursday, March 5, 2020 11:29:33 AM -03 David Hildenbrand wrote:
> Factor it out and properly use it where applicable. Make
> qemu_vfio_undo_mapping() look like qemu_vfio_do_mapping(), passing the
> size and iova, not the mapping.
>
> Reviewed-by: Peter Xu
> Cc: Richard Henderson
> Cc: Paolo B
On Thursday, March 5, 2020 11:29:41 AM -03 David Hildenbrand wrote:
> Implement resizeable mmaps. For now, the actual resizing is not wired up.
> Introduce qemu_ram_mmap_resizeable() and qemu_ram_mmap_resize(). Make
> qemu_ram_mmap() a wrapper of qemu_ram_mmap_resizeable().
>
> Reviewed-by: Peter X
On Thursday, March 5, 2020 11:29:37 AM -03 David Hildenbrand wrote:
> Let's factor out calculating the size of the guard page and rename the
> variable to make it clearer that this pagesize only applies to the
> guard page.
>
> Reviewed-by: Peter Xu
> Cc: "Michael S. Tsirkin"
> Cc: Murilo Opsfeld
On Thursday, March 5, 2020 11:29:44 AM -03 David Hildenbrand wrote:
> We want to actually use resizeable allocations in resizeable ram blocks
> (IOW, make everything between used_length and max_length inaccessible) -
> however, not all ram block notifiers can support that.
>
> Introduce a way to de
On Thursday, March 5, 2020 11:29:45 AM -03 David Hildenbrand wrote:
> We can now make use of resizeable anonymous allocations to implement
> actually resizeable ram blocks. Resizeable anonymous allocations are
> not implemented under WIN32 yet and are not available when using
> alternative allocato
On Thursday, March 5, 2020 11:29:43 AM -03 David Hildenbrand wrote:
> Introduce qemu_anon_ram_alloc_resizeable() and qemu_anon_ram_resize().
> Implement them under POSIX and make them return NULL under WIN32.
>
> Under POSIX, we make use of resizeable mmaps. An implementation under
> WIN32 is theor
On Thursday, March 5, 2020 11:29:42 AM -03 David Hildenbrand wrote:
> Let's implement ram_block_resized(), allowing resizeable mappings.
>
> For resizeable mappings, we reserve $max_size IOVA address space, but only
> map $size of it. When resizing, unmap the old part and remap the new
> part. We'l
On Thursday, March 5, 2020 11:29:32 AM -03 David Hildenbrand wrote:
> Everybody discards the error. Let's error_report() instead so this error
> doesn't get lost.
>
> This is now the same error handling as in qemu_vfio_do_mapping(). However,
> we don't report any errors via the return value to the
On Monday, February 24, 2020 11:16:16 AM -03 Murilo Opsfelder Araújo wrote:
> On Monday, February 24, 2020 7:57:03 AM -03 David Hildenbrand wrote:
> > On 24.02.20 11:50, David Hildenbrand wrote:
> > > On 19.02.20 23:46, Peter Xu wrote:
> > >> On Wed, Feb 12, 2
On Monday, February 24, 2020 7:57:03 AM -03 David Hildenbrand wrote:
> On 24.02.20 11:50, David Hildenbrand wrote:
> > On 19.02.20 23:46, Peter Xu wrote:
> >> On Wed, Feb 12, 2020 at 02:42:46PM +0100, David Hildenbrand wrote:
> >>> Factor it out and add a comment.
> >>>
> >>> Reviewed-by: Igor Kotr
Hello, David.
On Monday, February 3, 2020 3:31:21 PM -03 David Hildenbrand wrote:
> Implement resizable mmaps. For now, the actual resizing is not wired up.
> Introduce qemu_ram_mmap_resizable() and qemu_ram_mmap_resize(). Make
> qemu_ram_mmap() a wrapper of qemu_ram_mmap_resizable().
>
> Cc: "Mic
Hello, David.
On Thursday, February 6, 2020 5:52:26 AM -03 David Hildenbrand wrote:
> On 06.02.20 00:00, Murilo Opsfelder Araújo wrote:
> > Hello, David.
> >
> > On Monday, February 3, 2020 3:31:20 PM -03 David Hildenbrand wrote:
> >> When shrinking a mmap we
Hello, David.
On Monday, February 3, 2020 3:31:20 PM -03 David Hildenbrand wrote:
> When shrinking a mmap we want to re-reserve the already populated area.
> When growing a memory region, we want to populate starting with a given
> fd_offset. Prepare by allowing to pass these parameters.
>
> Also
Hello, David.
On 2/3/20 3:31 PM, David Hildenbrand wrote:
We want to populate memory within a reserved memory region. Let's factor
that out.
Cc: "Michael S. Tsirkin"
Cc: Greg Kurz
Cc: Murilo Opsfelder Araujo
Cc: Eduardo Habkost
Cc: "Dr. David Alan Gilbert"
Signed-off-by: David Hildenbrand
Hello, David.
On 2/3/20 3:31 PM, David Hildenbrand wrote:
We want to reserve a memory region without actually populating memory.
Let's factor that out.
Cc: "Michael S. Tsirkin"
Cc: Greg Kurz
Cc: Murilo Opsfelder Araujo
Cc: Eduardo Habkost
Cc: "Dr. David Alan Gilbert"
Signed-off-by: David H
Hello, David.
On 2/3/20 3:31 PM, David Hildenbrand wrote:
Factor it out and add a comment.
Cc: "Michael S. Tsirkin"
Cc: Murilo Opsfelder Araujo
Cc: Greg Kurz
Cc: Eduardo Habkost
Cc: "Dr. David Alan Gilbert"
Signed-off-by: David Hildenbrand
Acked-by: Murilo Opsfelder Araujo
---
util
Hi, Greg.
Greg Kurz writes:
> Signed-off-by: Greg Kurz
> ---
> target/ppc/kvm.c| 68
> +++
> target/ppc/trace-events | 25 +
> 2 files changed, 52 insertions(+), 41 deletions(-)
>
> diff --git a/target/ppc/kvm.c b/target/
Hi, Cameron.
The step "Start QEMU and boot Mac OS X 10.4.11" is not clear to me. Is
there a location where one could download such image and boot?
I wonder how one without access to a Mac image can reproduce this issue.
Cheers
Murilo
--
You received this bug notification because you are a mem
I'll work on a fix for configure.
** Changed in: qemu
Status: New => Confirmed
** Changed in: qemu
Assignee: (unassigned) => Murilo Opsfelder Araújo (mopsfelder)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Public bug reported:
QEMU v3.0.0-rc4 configure fails with --enable-mpath on CentOS 7.5.
After commit b3f1c8c413bc83e4a2cc7a63e4eddf9fe6449052 "qemu-pr-helper: use new
libmultipath API", QEMU started using new libmultipath API, which is not
available on CentOS 7.5. Reverting this commit, configur
Hi, Nigel.
Support for powerpc64 is available since FreeBSD 9.0-RELEASE, I think.
FreeBSD 11.2-RC2 boots fine in QEMU (at commit 46012db666990ff2eed1d3dc)
running on an x86 host with accel=tcg. Below are the steps I have
followed to boot it.
Build QEMU:
$ mkdir build && cd build
$ ../configure
With QEMU from tag v2.12.0-rc4 on Fedora 27 x86_64, it works too.
muriloo@laptop$ docker run --rm -it qemutest
/go # qemu-ppc64le-static --version
qemu-ppc64le version 2.11.94 (v2.12.0-rc4)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
/go # go version
go version go1.10.1
Using QEMU from tag v2.12.0-rc4 on Ubuntu Xenial ppc64el, it works.
muriloo@jaspion1:~/go-docker$ sudo docker run --rm -it qemutest
/go # /usr/bin/qemu-ppc64le-static --version
qemu-ppc64 version 2.11.94 (v2.12.0-rc4-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
/g
Hi, Timothy.
I tried to reproduce this issue on a POWER8 box and couldn't reproduce
it.
Whatever the issue was, it seems to be fixed on kernel v4.16-rc4 with
qemu 2.11.50.
I downloaded vmlinux/initrd.gz from Ubuntu 18.04 to boot guest. It
booted fine up to the installer initial screen.
Please f
The fix was committed:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c4365735a7d38f4355c6f77e6670d3972315f7c2
commit c4365735a7d38f4355c6f77e6670d3972315f7c2
Author: Murilo Opsfelder Araujo
Date: Fri Jan 5 11:32:41 2018 -0200
block/nbd: fix segmentation fault when .desc is not null-term
The fix was committed:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c4365735a7d38f4355c6f77e6670d3972315f7c2
commit c4365735a7d38f4355c6f77e6670d3972315f7c2
Author: Murilo Opsfelder Araujo
Date: Fri Jan 5 11:32:41 2018 -0200
block/nbd: fix segmentation fault when .desc is not null-term
On 01/09/2018 07:21 AM, Suraj Jitindar Singh wrote:
> The new H-Call H_GET_CPU_CHARACTERISTICS is used by the guest to query
> behaviours and available characteristics of the cpu.
>
> Implement the handler for this new H-Call which formulates its response
> based on the setting of the new capabili
On 01/09/2018 07:21 AM, Suraj Jitindar Singh wrote:
> This patch adds three new capabilities:
> cap-cfpc -> safe_cache
> cap-sbbc -> safe_bounds_check
> cap-ibs -> safe_indirect_branch
Hi, Suraj.
What about splitting this into smaller patches, one per capability?
> Each capability is tristate w
On 01/09/2018 07:21 AM, Suraj Jitindar Singh wrote:
> Currently spapr_caps are tied to boolean values (on or off). This patch
> reworks the caps so that they can have any value between 0 and 127,
> inclusive. This allows more capabilities with various values to be
> represented in the same way inte
As per previous comments, this bug was fixed by commit
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d659d94013390238961fac741572306c95496bf5
(released in QEMU v2.11.0):
commit d659d94013390238961fac741572306c95496bf5
Author: Aleksandr Bezzubikov
Date: Mon Sep 25 02:21:58 2017 +0300
hw/p
ative
** Changed in: qemu
Status: New => Fix Released
** Changed in: qemu
Assignee: (unassigned) => Murilo Opsfelder Araújo (mopsfelder)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/b
I confirmed that my patch http://lists.nongnu.org/archive/html/qemu-
devel/2018-01/msg00883.html fixes this bug too.
** Changed in: qemu
Status: New => In Progress
** Changed in: qemu
Assignee: (unassigned) => Murilo Opsfelder Araújo (mopsfelder)
--
You received th
On 01/05/2018 11:57 AM, Eric Blake wrote:
> On 01/05/2018 07:32 AM, Murilo Opsfelder Araujo wrote:
>> The find_desc_by_name() from util/qemu-option.c relies on the .name not being
>> NULL to call strcmp(). This check becomes unsafe when the list is not
>> NULL-terminated, which is the case of nbd_r
Patch sent:
http://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00883.html
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1727259
Title:
I'll work on this.
** Changed in: qemu
Assignee: (unassigned) => Murilo Opsfelder Araújo (mopsfelder)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1727259
Title:
qemu-io-test 58 s
I confirmed with Stefan and this bug was fixed by
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=fb0c43f34eed8b18678c6e1f481d8564b35c99ed
commit fb0c43f34eed8b18678c6e1f481d8564b35c99ed
Author: Stefan Hajnoczi
Date: Mon Nov 6 19:02:33 2017 +
tests-aio-multithread: fix /aio/multi/sched
On 11/13/2017 07:39 PM, Amador Pahim wrote:
> To launch a VM, we need to create basically two files: the monitor
> socket (if it's a UNIX socket) and the qemu log file.
>
> For the qemu log file, we currently just open the path, which will
> create the file if it does not exist or overwrite the fi
59 matches
Mail list logo
