I only enable a few emulators and qemu-system-s390x isn't one of them.
I was thinking it couldn't be useful on an x86_64 host, even if using
the qemu-system-s390x emulator! I guess my understanding was wrong. Will
close as invalid.
** Changed in: qemu
Status: Incomplete => Invalid
--
You
If 'virgl_cmd_get_capset' set 'max_size' to 0,
the 'virgl_renderer_fill_caps' will write the data after the 'resp'.
This patch avoid this by checking the returned 'max_size'.
virtio-gpu fix: abd7f08b23 ("display: virtio-gpu-3d: check
virgl capabilities max_size")
Fixes: CVE-2021-3546
Reported-by:
Call 'vugbm_buffer_destroy' in error path to avoid resource leak.
Fixes: CVE-2021-3544
Reported-by: Li Qiang
Reviewed-by: Prasad J Pandit
Signed-off-by: Li Qiang
---
contrib/vhost-user-gpu/vhost-user-gpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/vhost-user-gpu/vhost-user-gp
Currently in vhost-user-gpu, we free resource directly in
the cleanup case of resource. If we change the cleanup logic
we need to change several places, also abstruct a
'vg_create_mapping_iov' can be symmetry with the
'vg_create_mapping_iov'. This is like what virtio-gpu does,
no function changed.
Check whether the 'res' has already been attach_backing to avoid
memory leak.
Fixes: CVE-2021-3544
Reported-by: Li Qiang
virtio-gpu fix: 204f01b309 ("virtio-gpu: fix memory leak
in resource attach backing")
Signed-off-by: Li Qiang
---
contrib/vhost-user-gpu/vhost-user-gpu.c | 5 +
1 file c
Otherwise some of the 'resp' will be leaked to guest.
Fixes: CVE-2021-3545
Reported-by: Li Qiang
virtio-gpu fix: 42a8dadc74 ("virtio-gpu: fix information leak
in getting capset info dispatch")
Signed-off-by: Li Qiang
---
contrib/vhost-user-gpu/virgl.c | 1 +
1 file changed, 1 insertion(+)
dif
If 'virgl_renderer_resource_attach_iov' failed, the 'res_iovs' will
be leaked.
Fixes: CVE-2021-3544
Reported-by: Li Qiang
virtio-gpu fix: 33243031da ("virtio-gpu-3d: fix memory leak
in resource attach backing")
Signed-off-by: Li Qiang
---
contrib/vhost-user-gpu/virgl.c | 5 -
1 file change
The 'res->iov' will be leaked if the guest trigger following sequences:
virgl_cmd_create_resource_2d
virgl_resource_attach_backing
virgl_cmd_resource_unref
This patch fixes this.
Fixes: CVE-2021-3544
Reported-by: Li Qiang
virtio-gpu fix: 5e8e3c4c75 ("virtio-gpu: fix reso
These security issue is low severity and is similar with the
virtio-vga/virtio-gpu device. All of them can be triggered by
the guest user.
Change since v1:
Add the CVE information:
Several memory leak issues is combined assigned CVE-2021-3544.
Information disclosure is assigned CVE-2021-3545.
OOB
If the guest trigger following sequences, the attach_backing will be leaked:
vg_resource_create_2d
vg_resource_attach_backing
vg_resource_unref
This patch fix this by freeing 'res->iov' in vg_resource_destroy.
Fixes: CVE-2021-3544
Reported-by: Li Qiang
virtio-gpu fix: 5e
On 5/3/21 4:50 PM, Philippe Mathieu-Daudé wrote:
Hi Richard,
On 5/3/21 1:57 AM, Richard Henderson wrote:
Signed-off-by: Richard Henderson
---
tcg/internal.h | 5 +
tcg/tcg.c | 5 ++---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/tcg/internal.h b/tcg/internal.h
in
On 5/15/21 5:57 AM, Philippe Mathieu-Daudé wrote:
+switch (op) {
+case INDEX_op_br:
+case INDEX_op_call:
+case INDEX_op_exit_tb:
+case INDEX_op_goto_tb:
+tci_args_l(&tb_ptr, &ptr);
+info->fprintf_func(info->stream, "%-12s %p", op_name, ptr);
+break;
On Sun, May 16, 2021 at 1:33 AM Philippe Mathieu-Daudé
wrote:
>
> On 5/14/21 5:02 AM, Bin Meng wrote:
> > On Fri, May 14, 2021 at 12:53 AM Philippe Mathieu-Daudé
> > wrote:
> >>
> >> Per the kconfig.rst:
> >>
> >> A device should be listed [...] ``imply`` if (depending on
> >> the QEMU comman
I just wanted to give you guys an update on this issue. The libusb people have
fixed the issue with USB device driver detaching on Mac OS. Here is where the
code for the fix is located: https://github.com/libusb/libusb/pull/911/commits.
I was able to build the library and connect it to QEMU on
Signed-off-by: Michael Rolnik
---
MAINTAINERS | 2 +
hw/avr/Kconfig| 1 +
hw/avr/atmega.c | 15 +-
hw/avr/atmega.h | 2 +
hw/watchdog/Kconfig | 3 +
hw/watchdog/avr_wdt.c | 279 +++
1. Initial implementation of AVR WDT
There are two issues with this implementation so I need your help here
a. when I configure the WDT to fire an interrupt every 15ms it actually
happens every 6 instructions
b. when I specify --icount shift=0 qemu stucks
changes since v1
1. correct
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning, the runtime component of th
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
On 5/15/21 4:37 PM, BALATON Zoltan wrote:
On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
On 5/13/21 1:54 PM, BALATON Zoltan wrote:
On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
On 5/11/21 3:09 PM, BALATON Zoltan wrote:
On Tue, 11 Ma
Le 13/04/2021 à 22:58, Ilya Leoshkevich a écrit :
> The current code dumps the memory between arg_start and arg_end,
> which contains the argv pointers. This results in the
>
> Core was generated by ``
>
> message when opening the core file in GDB. This is because the code is
> supposed to du
Le 13/04/2021 à 22:56, Ilya Leoshkevich a écrit :
> Provide the following definitions required by the common code:
>
> * ELF_NREG: with the value of sizeof(s390_regs) / sizeof(long).
> * target_elf_gregset_t: define it like all the other arches do.
> * elf_core_copy_regs(): similar to kernel's s39
On 5/15/21 9:41 PM, BALATON Zoltan wrote:
> On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
>> From: Philippe Mathieu-Daudé
>>
>> While the ATI VGA device isn't a requisite (no crash without it):
>>
>> $ qemu-system-ppc -M pegasos2
>> qemu-system-ppc: standard VGA not available
>>
>> it is us
Le 23/04/2021 à 01:02, Richard Henderson a écrit :
> Alpha had two bugs, one with the non-ka_restorer fallback
> using the wrong offset, and the other with the ka_restorer
> value getting lost in do_sigaction.
>
> Sparc had another bug, where the ka_restorer field was
> written to user memory.
>
Le 05/05/2021 à 12:37, Daniel P. Berrangé a écrit :
> The GDateTime APIs provided by GLib avoid portability pitfalls, such
> as some platforms where 'struct timeval.tv_sec' field is still 'long'
> instead of 'time_t'. When combined with automatic cleanup, GDateTime
> often results in simpler code t
Le 03/05/2021 à 19:41, LemonBoy a écrit :
> From: Giuseppe Musacchio
>
> An unwanted sign-extension is currently making the host kernel return
> EOVERFLOW
> when calling copy_file_range with a count of 0x, despite the host
> being
> a 64bit platform.
>
> The fix is only affecting 32bit
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
From: Philippe Mathieu-Daudé
Looking at the MV64340 model source, there is a dependency on the
8259 interrupt controller:
523 case MV64340_PCI_1_INTERRUPT_ACKNOWLEDGE_VIRTUAL_REG:
524 /* FIXME: Should this be sent via the PCI bus
Le 28/04/2021 à 21:33, Richard Henderson a écrit :
> Version 2 splits lazy do-it-all patch.
> Patch 1 has an additional fix, so I dropped the r-b.
>
> r~
>
> Richard Henderson (15):
> linux-user/s390x: Fix sigframe types
> linux-user/s390x: Use uint16_t for signal retcode
> linux-user/s390x
Le 26/04/2021 à 04:53, Richard Henderson a écrit :
> Supercedes: 20210425155749.896330-1-richard.hender...@linaro.org
> ("linux-user/sparc64: Implement signals")
>
> This time, in the lead-up, merge the sparc and sparc64 directories.
> Implement rt signals for sparc32 as well, since there are only
Le 12/05/2021 à 12:13, Kito Cheng a écrit :
> Some target are using llseek instead of _llseek like riscv,
> nios2, hexagon, and openrisc.
>
> Signed-off-by: Kito Cheng
> ---
> linux-user/strace.c| 3 ++-
> linux-user/strace.list | 3 +++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
>
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
From: Philippe Mathieu-Daudé
The VT82C686 device model misses various dependencies:
/usr/bin/ld: libcommon.fa.p/hw_isa_vt82c686.c.o: in function
`vt82c686b_realize':
hw/isa/vt82c686.c:622: undefined reference to `i8259_init'
/usr/bin/ld:
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
From: Philippe Mathieu-Daudé
While the ATI VGA device isn't a requisite (no crash without it):
$ qemu-system-ppc -M pegasos2
qemu-system-ppc: standard VGA not available
it is useful to have it with the Pegasos2 machine:
$ qemu-system-ppc
Le 23/04/2021 à 18:54, Richard Henderson a écrit :
> The bug fix is patch 2, the rest is a bit of tidy-up.
>
>
> r~
>
> Richard Henderson (4):
> linux-user/arm: Split out emulate_arm_fpa11
> linux-user/arm: Do not emulate fpa11 in thumb mode
> linux-user/arm: Do not fill in si_code for fpa
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
From: Philippe Mathieu-Daudé
When building the Pegasos2 machine stand-alone we get:
$ qemu-system-ppc -M pegasos2 -bios pegasos2.rom
ERROR:qom/object.c:714:object_new_with_type: assertion failed: (type != NULL)
Bail out! ERROR:qom/object.c:
Le 06/04/2021 à 16:42, Matus Kysel a écrit :
> Syscall unshare did not have custom print function for strace, but it's
> argument is same as flags in clone syscall, so it can be easily implemented.
> Also updated missing flags from clone_flags.
>
> Signed-off-by: Matus Kysel
> ---
> linux-user/
On Sat, 15 May 2021, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Sinc
Le 03/03/2021 à 22:46, Philippe Mathieu-Daudé a écrit :
> We can not use watchpoints in user-mode emulation because we
> need the softmmu slow path to detect accesses to watchpointed
> memory. This code is expanded as empty stub in "hw/core/cpu.h"
> anyway, so we can drop it.
>
> Reviewed-by: Laur
Hi
On Sat, May 15, 2021 at 5:20 PM Philippe Mathieu-Daudé
wrote:
> On 5/14/21 8:33 PM, Peter Maydell wrote:
> > On Fri, 14 May 2021 at 12:13, wrote:
> >>
> >> From: Marc-André Lureau
> >>
> >> The following changes since commit
> 2d3fc4e2b069494b1e9e2e4a1e3de24cbc036426:
> >>
> >> Merge remo
When selecting an ARM target on Debian unstable, we get:
Compiling C++ object libcommon.fa.p/disas_libvixl_vixl_utils.cc.o
FAILED: libcommon.fa.p/disas_libvixl_vixl_utils.cc.o
c++ -Ilibcommon.fa.p -I. -I.. [...] -o
libcommon.fa.p/disas_libvixl_vixl_utils.cc.o -c ../disas/libvixl/vixl/utils.
** Attachment added: "Full build failure log"
https://bugs.launchpad.net/qemu/+bug/1914870/+attachment/5497821/+files/disas_libvixl_vixl_utils.cc.o.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
Looking at commit 875df03b221 logic ("osdep: protect qemu/osdep.h with extern
"C"")
I tried this:
-- >8 --
diff --git a/disas/libvixl/vixl/utils.h b/disas/libvixl/vixl/utils.h
index 5ab134e240..fc28d7456c 100644
--- a/disas/libvixl/vixl/utils.h
+++ b/disas/libvixl/vixl/utils.h
@@ -27,8 +27,10 @@
Still an issue as of commit 6d34aa9969f.
** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914870
Title:
libvixl compilation failure on Debi
New issue on GitLab https://gitlab.com/qemu-project/qemu/-/issues/326
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #326
https://gitlab.com/qemu-project/qemu/-/issues/326
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
From: Philippe Mathieu-Daudé
Looking at the MV64340 model source, there is a dependency on the
8259 interrupt controller:
523 case MV64340_PCI_1_INTERRUPT_ACKNOWLEDGE_VIRTUAL_REG:
524 /* FIXME: Should this be sent via the PCI bus somehow? */
525 if (s->gpp_int_level &&
Commit 7abb479c7ab ("PPC: E500: Add FSL I2C controller and integrate
RTC with it") added a global dependency on the DS1338 model, instead
of a machine one (via Kconfig). This gives trouble when building
standalone machines not exposing I2C bus:
The following clauses were found for DS1338
On 5/15/21 4:37 PM, BALATON Zoltan wrote:
> On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
>> On 5/13/21 1:54 PM, BALATON Zoltan wrote:
>>> On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
On 5/11/21 3:09 PM, BALATON Zoltan wrote:
> On Tue, 11 May 2021, Philippe Mathieu-Daudé wrote:
Only the Virt and Spike machines use NUMA. Add a RISCV_NUMA Kconfig
symbol and only have these machines select it. Adapt the Meson file
to only built it if required.
Acked-by: Paolo Bonzini
Reviewed-by: Bin Meng
Signed-off-by: Philippe Mathieu-Daudé
---
hw/riscv/Kconfig | 5 +
hw/riscv
From: Philippe Mathieu-Daudé
When building the Pegasos2 machine stand-alone we get:
$ qemu-system-ppc -M pegasos2 -bios pegasos2.rom
ERROR:qom/object.c:714:object_new_with_type: assertion failed: (type != NULL)
Bail out! ERROR:qom/object.c:714:object_new_with_type: assertion failed:
(type
Commit a8fb0a500a6 ("hw/char: Add Microchip PolarFire SoC MMUART
emulation") added a dependency on the SERIAL model, but forgot to
add the Kconfig selector.
Add the dependency to the MCHP_PFSOC_MMUART symbol to fix when
building the MICROCHIP_PFSOC machine stand-alone:
/usr/bin/ld: libcommon.fa.
Commit bfae1772c43 ("hw/arm/fsl-imx25: Wire up eSDHC controllers")
added a dependency on the TYPE_IMX_USDHC model, but forgot to add
the Kconfig selector. Fix that to solve when built stand-alone:
$ qemu-system-arm -M imx25-pdk
qemu-system-arm: missing object type 'imx-usdhc'
Aborted (core d
From: Philippe Mathieu-Daudé
The VT82C686 device model misses various dependencies:
/usr/bin/ld: libcommon.fa.p/hw_isa_vt82c686.c.o: in function
`vt82c686b_realize':
hw/isa/vt82c686.c:622: undefined reference to `i8259_init'
/usr/bin/ld: hw/isa/vt82c686.c:624: undefined reference to `i825
In commit c4f00daa5b3 ("imx25-pdk: create ds1338 for qtest inside
the test") we removed the DS1338 device from the i.MX25 machine
but forgot to remove it in the machine Kconfig definitions, do
it now.
Acked-by: Paolo Bonzini
Reviewed-by: Bin Meng
Signed-off-by: Philippe Mathieu-Daudé
---
hw/ar
The TYPE_NPCM7XX_SMBUS device model exposes an SMBus, but
this isn't advertised with proper Kconfig symbol, leading
to an early build failure when building NPCM7XX machines
standalone:
The following clauses were found for AT24C
config AT24C depends on I2C
select AT24C if NPCM7XX
Fi
From: Philippe Mathieu-Daudé
While the ATI VGA device isn't a requisite (no crash without it):
$ qemu-system-ppc -M pegasos2
qemu-system-ppc: standard VGA not available
it is useful to have it with the Pegasos2 machine:
$ qemu-system-ppc -M pegasos2 -vga none -bios pegasos2.rom -device
Per the kconfig.rst:
A device should be listed [...] ``imply`` if (depending on
the QEMU command line) the board may or may not be started
without it.
This is the case with the NVDIMM device (it is certainly possible
to start a machine without NVDIMM) , so use the 'imply' weak
reverse depe
The pci_ide_create_devs() function is declared i hw/ide/qdev.c:
$ git grep ide_create_drive
hw/ide/pci.c:491:ide_create_drive(d->bus + bus[i], unit[i],
hd_table[i]);
hw/ide/qdev.c:127:IDEDevice *ide_create_drive(IDEBus *bus, int unit, DriveInfo
*drive)
include/hw/ide/internal.h:6
Various Kconfig fixes when building stand-alone machine binaries.
Since v1:
- Fixed Pegasos2 machine
- Removed SEMIHOSTING related patches (will repost them later)
Philippe Mathieu-Daudé (12):
hw/mem/nvdimm: Use Kconfig 'imply' instead of 'depends on'
hw/ide/Kconfig: Add missing dependency PC
On 5/14/21 5:02 AM, Bin Meng wrote:
> On Fri, May 14, 2021 at 12:53 AM Philippe Mathieu-Daudé
> wrote:
>>
>> Per the kconfig.rst:
>>
>> A device should be listed [...] ``imply`` if (depending on
>> the QEMU command line) the board may or may not be started
>> without it.
>>
>> This is the c
On 5/13/21 2:25 PM, Peter Maydell wrote:
+static bool do_neon_ddda(DisasContext *s, int q, int vd, int vn, int vm,
+ int data, gen_helper_gvec_4 *fn_gvec)
This patch seems to be doing more than its commit message suggests.
If we want to share code between trans_VDOT and
On 5/13/21 2:25 PM, Peter Maydell wrote:
-VDOT_scalar 1110 0 . 10 1101 . q:1 index:1 u:1 rm:4 \
- vm=%vm_dp vn=%vn_dp vd=%vd_dp
+VDOT_scalar 1110 0 . 10 1101 . q:1 index:1 u:1 vm:4 \
+ vn=%vn_dp vd=%vd_dp
Is it possible to make thi
On 5/13/21 12:04 PM, Peter Maydell wrote:
We now have a full set of these macros in vec_helper.c and sve_helper.c,
and I'm going to need them in the MVE mve_helper.c too. This seems like
a good point to pull them out into a suitable header file and add a
documentation comment that makes it clear
On 5/13/21 11:57 AM, Peter Maydell wrote:
On Fri, 30 Apr 2021 at 22:17, Richard Henderson
wrote:
From: Stephen Long
Implements SQSHL/UQSHL, SRSHR/URSHR, and SQSHLU
Signed-off-by: Stephen Long
Message-Id: <20200430194159.24064-1-stepl...@quicinc.com>
Signed-off-by: Richard Henderson
---
On 5/15/21 4:35 PM, BALATON Zoltan wrote:
> On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
>> On 5/15/21 1:31 PM, Volker Rümelin wrote:
>>> This patch series fixes two different PS/2 mouse stream corruptions
>>> and adds a feature that allows some old misbehaving DOS programs to
>>> have a work
On 5/13/21 9:25 AM, Peter Maydell wrote:
@@ -5551,7 +5547,9 @@ static void do_ldrq(DisasContext *s, int zt, int pg,
TCGv_i64 addr, int msz)
t_pg = tcg_temp_new_ptr();
tcg_gen_addi_ptr(t_pg, cpu_env, poff);
-fns[s->be_data == MO_BE][msz](cpu_env, t_pg, addr, t_desc);
+gen_hel
On 5/13/21 9:18 AM, Peter Maydell wrote:
+static int64_t do_float64_logb_as_int(float64 a, float_status *s)
+{
+if (float64_is_normal(a)) {
+return extract64(a, 52, 11) - 1023;
+} else if (float64_is_infinity(a)) {
+return INT64_MAX;
+} else if (float64_is_any_nan(a) |
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning, the runtime component of th
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
Patch has been merged:
https://gitlab.com/qemu-project/qemu/-/commit/8196fe9d83d6519128b5
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/324
** Changed in: qemu
Status: New => Expired
** Bug watch
On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
On 5/13/21 1:54 PM, BALATON Zoltan wrote:
On Thu, 13 May 2021, Philippe Mathieu-Daudé wrote:
On 5/11/21 3:09 PM, BALATON Zoltan wrote:
On Tue, 11 May 2021, Philippe Mathieu-Daudé wrote:
Hi Zoltan,
On 5/11/21 1:28 PM, BALATON Zoltan wrote:
O
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
On 5/15/21 1:31 PM, Volker Rümelin wrote:
This patch series fixes two different PS/2 mouse stream corruptions
and adds a feature that allows some old misbehaving DOS programs to
have a working keyboard. With the last few patches, the PS/2 con-
t
On Sat, 15 May 2021, Philippe Mathieu-Daudé wrote:
Add a pair of tests for the Pegasos2 machine following the steps from:
https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg01553.html
$ PEGASOS2_ROM_PATH=/tmp/pegasos2.rom AVOCADO_ALLOW_UNTRUSTED_CODE=1 \
avocado --show=app,console,t
15.05.2021 16:46, Vladimir Sementsov-Ogievskiy wrote:
Hi all!
Alberto, I'm sorry for not consulting with you about sending this.
Actually, I wanted only one patch
"block: Allow changing bs->file on reopen", as I'm going to send another
series based on it.
Haha. Actually I need instead a way t
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/323
** Tags added: feature-request
** Changed in: qemu
Stat
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/322
** Changed in: qemu
Status: New => Expired
** Bug watch
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/317
** Changed in: qemu
Status: New => Expired
** Bug watch
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/321
** Changed in: qemu
Status: Confirmed => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/318
** Changed in: qemu
Status: Confirmed => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/320
** Changed in: qemu
Status: Confirmed => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/319
** Changed in: qemu
Status: New => Expired
** Bug watch
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
The logic around finding overlay here is not obvious. Actually it does
two simple things:
1. If new bs is already in backing chain, split from parent bs by
several implicit filters we are done, do nothing.
2. Otherwise, don't try to replace implicit filter.
Let's rewrite this in more obvious
To be used for reopen in future commit.
Notes:
- It seems OK to update inherits_from if new bs is recursively inherits
from parent bs. Let's just not check for backing_chain_contains, to
support file child of non-filters.
- Simply check child->frozen instead of
bdrv_is_backing_chain_frozen
From: Alberto Garcia
When the x-blockdev-reopen was added it allowed reconfiguring the
graph by replacing backing files, but changing the 'file' option was
forbidden. Because of this restriction some operations are not
possible, notably inserting and removing block filters.
This patch adds suppo
From: Alberto Garcia
This patch adds new tests in which we use x-blockdev-reopen to change
bs->file
Signed-off-by: Alberto Garcia
---
tests/qemu-iotests/245 | 109 -
tests/qemu-iotests/245.out | 11 +++-
2 files changed, 117 insertions(+), 3 deletions(-
Hi all!
Alberto, I'm sorry for not consulting with you about sending this.
Actually, I wanted only one patch
"block: Allow changing bs->file on reopen", as I'm going to send another
series based on it. I started to work on updating this one patch it and
it turned into a refactoring series below.
We don't need this check: bdrv_set_backing_noperm() will do it anyway
(actually in bdrv_attach_child_common()).
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block.c | 33 -
1 file changed, 33 deletions(-)
diff --git a/block.c b/block.c
index 5141c04815..4e18bc
Move supports_backing check of bdrv_reopen_parse_backing to called
(through bdrv_set_backing_noperm()) bdrv_set_file_or_backing_noperm()
function. The check applies to general case, so it's appropriate for
bdrv_set_file_or_backing_noperm().
We have to declare backing support for two test drivers,
To be used for reopen in future commit.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/block.c b/block.c
index 9ad725d205..75565ce4d4 100644
--- a/block.c
+++ b/block.c
@@ -4770,16 +4770,14 @@
It's used only in bdrv_reopen_commit(). "backing" is covered by the
loop through all children except for case when we removed backing child
during reopen.
Make it more obvious and drop extra boolean field: qdict_del will not
fail if there is no such entry.
Signed-off-by: Vladimir Sementsov-Ogievs
bdrv_set_backing_noperm() takes care of it (actual check is in
bdrv_set_file_or_backing_noperm()), so we don't need to check it here.
While being here, improve error message a bit.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block.c| 14 +-
tests/qemu-iotests/245
If a guest sends binary data on the serial console, we get:
File "tests/acceptance/avocado_qemu/__init__.py", line 92,
in _console_interaction msg = console.readline().strip()
File "/usr/lib64/python3.8/codecs.py", line 322,
in decode (result, consumed) = self._buffer_decode(data, self.err
Add a pair of tests for the Pegasos2 machine following the steps from:
https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg01553.html
$ PEGASOS2_ROM_PATH=/tmp/pegasos2.rom AVOCADO_ALLOW_UNTRUSTED_CODE=1 \
avocado --show=app,console,tesseract \
run -t machine:pegasos2 tests/acce
Philippe Mathieu-Daudé (2):
tests/acceptance: Ignore binary data sent on serial console
tests/acceptance: Add tests for the Pegasos2 machine
tests/acceptance/avocado_qemu/__init__.py | 7 +-
tests/acceptance/machine_ppc_pegasos.py | 98 +++
2 files changed, 103 insert
On 5/14/21 8:33 PM, Peter Maydell wrote:
> On Fri, 14 May 2021 at 12:13, wrote:
>>
>> From: Marc-André Lureau
>>
>> The following changes since commit 2d3fc4e2b069494b1e9e2e4a1e3de24cbc036426:
>>
>> Merge remote-tracking branch 'remotes/armbru/tags/pull-misc-2021-05-12'
>> into staging (2021-0
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1926246
Title:
chrome based apps can not be run under qemu user mode
Status in QEMU:
New
Bug d
KVM Forum 2021 virtual experience
September 15-16, 2021
(All submissions must be received before May 31, 2021 at 23:59 PST)
=
KVM Forum is an annual event that present
If it’s included in qemu when one downloads the sources I’m happy.
Sent from my iPhone
> On 15 May 2021, at 11:55, Thomas Huth <1914...@bugs.launchpad.net> wrote:
>
> Could we close this ticket now if there is a workaround in libslirp now?
>
> ** Changed in: qemu
> Status: New => Incompl
On 5/15/21 1:31 PM, Volker Rümelin wrote:
> This patch series fixes two different PS/2 mouse stream corruptions
> and adds a feature that allows some old misbehaving DOS programs to
> have a working keyboard. With the last few patches, the PS/2 con-
> troller behaves more like a real controller.
>
Currently the PS/2 controller command KBD_CCMD_MOUSE_DISABLE
doesn't disable the PS/2 mouse communication at all, and the
PS/2 controller commands KBD_CCMD_KBD_DISABLE and
KBD_CCMD_KBD_ENABLE only disable and enable the keyboard
interrupt, which is very different from what a real PS/2
controller do
Currently there is only one flag to distinguish between two
interrupt sources and there are no available flags for more
sources. Add an internal state variable to store the interrupt
source. The next patch will introduce an additional interrupt
source. There is no functional change.
Signed-off-by:
Replace reads of the variable s->pending with a call to a new
function kbd_pending() to ease the review of the next patch.
There is no functional change.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Volker Rümelin
---
hw/input/pckbd.c | 21 ++---
1 file changed, 14 inserti
1 - 100 of 175 matches
Mail list logo
