Hey... new to this list. I was looking for a way to use Unix domain sockets
as a network transport between local VMs.
I'm part of a team where we run dozens if not hundreds of VMs on a single
compute instance which are highly interconnected.
In the current implementation, I use UDP sockets (e
On 23.04.21 08:40, Stefano Garzarella wrote:
On Thu, Apr 22, 2021 at 06:54:21PM +0200, Philippe Mathieu-Daudé wrote:
On 4/22/21 6:07 PM, Thomas Huth wrote:
On 22/04/2021 17.52, Stefano Garzarella wrote:
On Thu, Apr 22, 2021 at 05:38:26PM +0200, Thomas Huth wrote:
On 22/04/2021 16.31, Phili
On Mon, Feb 8, 2021 at 10:41 PM Bin Meng wrote:
>
> On Thu, Jan 21, 2021 at 10:18 PM Francisco Iglesias
> wrote:
> >
> > Hi Bin,
> >
> > On [2021 Jan 21] Thu 16:59:51, Bin Meng wrote:
> > > Hi Francisco,
> > >
> > > On Thu, Jan 21, 2021 at 4:50 PM Francisco Iglesias
> > > wrote:
> > > >
> > > >
On Thu, Apr 22, 2021 at 06:54:21PM +0200, Philippe Mathieu-Daudé wrote:
On 4/22/21 6:07 PM, Thomas Huth wrote:
On 22/04/2021 17.52, Stefano Garzarella wrote:
On Thu, Apr 22, 2021 at 05:38:26PM +0200, Thomas Huth wrote:
On 22/04/2021 16.31, Philippe Mathieu-Daudé wrote:
On 4/22/21 2:41 PM, Chr
在 2021/4/23 下午1:42, Stefan Weil 写道:
Am 23.04.21 um 05:18 schrieb Jason Wang:
There could be case that peer is NULL. This can happen when during
network device hot-add where net device needs to be added first. So
the patch check the existence of peer before trying to do the pad.
Fixes: 969e50
在 2021/4/23 下午12:47, Dongli Zhang 写道:
This is inspired by the discussion with Jason on below patchset.
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg09020.html
The new HMP command is introduced to dump the MSI-X table and PBA.
Initially, I was going to add new option to "info pci"
There was a customer request for const_tsc support on AMD guests. Right
now this feature is turned off by default for QEMU x86 CPU types (in
CPUID_Fn8007_EDX[8]). However we are seeing a discrepancy in guest
VM behavior between Intel and AMD.
In Linux kernel, Intel x86 code enables X86_FEA
Am 23.04.21 um 05:18 schrieb Jason Wang:
There could be case that peer is NULL. This can happen when during
network device hot-add where net device needs to be added first. So
the patch check the existence of peer before trying to do the pad.
Fixes: 969e50b61a285 ("net: Pad short frames to mini
From: Klaus Jensen
Commit 1901b4967c3f changed the nvme device from using a bar exclusive
for MSI-x to sharing it on bar0.
Unfortunately, the msix_uninit_exclusive_bar() call remains in
nvme_exit() which causes havoc when the device is removed with, say,
device_del. Fix this.
Additionally, a su
From: Klaus Jensen
If a controller is linked to a subsystem, do not allow it to be
hotplugged since this will mess up the (possibly shared) namespaces.
Signed-off-by: Klaus Jensen
---
hw/block/nvme.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/block/nvme.c b/hw/block/nvme.c
inde
From: Klaus Jensen
First patch fixes a regression where msix is not correctly uninit'ed
when an nvme device is hotplugged with device_del. When viewed in
conjunction with the commit that introduced the bug (commit
1901b4967c3f), I think the fix looks relatively obvious.
Second patch disables hot
This patch is to add the HMP interface to dump MSI-X table and PBA, in
order to help diagnose the loss of IRQ issue in VM (e.g., if an MSI-X
vector is erroneously masked permanently). Here is the example with
vhost-scsi:
(qemu) info msix /machine/peripheral/vscsi0
MSI-X Table
0xfee01004 0x
This is inspired by the discussion with Jason on below patchset.
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg09020.html
The new HMP command is introduced to dump the MSI-X table and PBA.
Initially, I was going to add new option to "info pci". However, as the
number of entries is not
Ok, thanks for answering! So I'm closing this issue now. In case anybody
still has similar issues, please open a new bug ticket instead.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217
Title:
Networking
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1778966
Title:
Windows 180
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1615212
Title:
SDL UI swit
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1725707
Title:
QEMU sends
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1820247
Title:
QEMU random
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1879425
Title:
The thread
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1642421
Title:
qemu-system
On Thu, Apr 22, 2021 at 04:35:34PM -0300, Fabiano Rosas wrote:
> Bruno Piazera Larsen writes:
>
> >> > You are correct! I've just tweaked the code that defines spr_register and
> >> > it should be working now. I'm still working in splitting the SPR
> >> > functions
> >> > from translate_init, si
On Fri, Apr 23, 2021 at 11:18 AM Jason Wang wrote:
>
> There could be case that peer is NULL. This can happen when during
> network device hot-add where net device needs to be added first. So
> the patch check the existence of peer before trying to do the pad.
>
> Fixes: 969e50b61a285 ("net: Pad s
There could be case that peer is NULL. This can happen when during
network device hot-add where net device needs to be added first. So
the patch check the existence of peer before trying to do the pad.
Fixes: 969e50b61a285 ("net: Pad short frames to minimum size before sending
from SLiRP/TAP")
Si
The last branch recording (LBR) is a performance monitor unit (PMU)
feature on Intel processors that records a running trace of the most
recent branches taken by the processor in the LBR stack. The QEMU
could configure whether it's enabled or not for each guest via CLI.
The LBR feature would be en
Instead of hardcoding the PERF_CAPABILITIES rules in this loop,
this could become a FeatureWordInfo field. It would be very useful
for other features like intel-pt, where we need some bits to match
the host bits too.
Suggested-by: Eduardo Habkost
Signed-off-by: Like Xu
---
target/i386/cpu.c | 2
On 4/21/2021 11:18 PM, Eduardo Habkost wrote:
On Wed, Apr 21, 2021 at 10:50:10PM +0800, Xiaoyao Li wrote:
On 4/21/2021 10:12 PM, Eduardo Habkost wrote:
On Wed, Apr 21, 2021 at 02:26:42PM +0800, Chenyi Qiang wrote:
Hi, Eduardo, thanks for your comments!
On 4/21/2021 12:34 AM, Eduardo Habko
在 2021/4/23 上午5:34, Cole Robinson 写道:
On 4/22/21 5:42 AM, Bin Meng wrote:
On Thu, Apr 22, 2021 at 5:36 PM Peter Maydell wrote:
On Thu, 22 Apr 2021 at 05:29, Bin Meng wrote:
On Thu, Apr 22, 2021 at 12:36 AM Philippe Mathieu-Daudé
wrote:
Cc'ing Bin.
On 4/21/21 5:22 PM, Cole Robinson wrote
On 4/22/21 12:38 PM, Philippe Mathieu-Daudé wrote:
Migration is specific to system emulation.
- Move the CPUClass::vmsd field to SysemuCPUOps,
- restrict VMSTATE_CPU() macro to sysemu,
- vmstate_dummy is now unused, remove it.
Signed-off-by: Philippe Mathieu-Daudé
---
Reviewed-by: Richard He
On 4/22/21 12:38 PM, Philippe Mathieu-Daudé wrote:
See rationale in previous commit. Targets should use the vmsd field
of DeviceClass, not CPUClass. As migration is not important on the
avr/lm32/moxie targets, break the migration compatibility and set
the DeviceClass vmsd field.
Signed-off-by: P
On 4/22/21 12:38 PM, Philippe Mathieu-Daudé wrote:
Quoting Peter Maydell [*]:
There are two ways to handle migration for
a CPU object:
(1) like any other device, so it has a dc->vmsd that covers
migration for the whole object. As usual for objects that are a
subclass of a parent
On 4/22/21 12:38 PM, Philippe Mathieu-Daudé wrote:
Migration is specific to system emulation.
Restrict current DeviceClass::vmsd to sysemu using #ifdef'ry,
and assert in cpu_exec_realizefn() that dc->vmsd not set under
user emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
cpu.c
Patchew URL:
https://patchew.org/QEMU/20210422230227.314751-1-richard.hender...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210422230227.314751-1-richard.hender...@linaro.org
Subject: [PATCH v2 0/7] li
Initialize variables instead of elses.
Use an else instead of a goto.
Add braces.
Signed-off-by: Richard Henderson
---
linux-user/syscall.c | 32 +---
1 file changed, 13 insertions(+), 19 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 9bc
Do not access a field that may not be present. This will
become an issue when sharing more code in the next patch.
Signed-off-by: Richard Henderson
---
linux-user/syscall.c | 4
1 file changed, 4 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 36169a0ded..89d6
The value of ka_restorer needs to be saved in sigact_table.
At the moment, the attempt to save it in do_syscall is
improperly clobbering user memory.
Signed-off-by: Richard Henderson
---
linux-user/syscall_defs.h | 2 +-
linux-user/signal.c | 5 -
linux-user/syscall.c | 19 +
Use ka_restorer, in line with TARGET_ARCH_HAS_KA_RESTORER
vs TARGET_ARCH_HAS_SA_RESTORER, since Alpha passes this
field as a syscall argument.
Signed-off-by: Richard Henderson
---
linux-user/syscall_defs.h | 2 +-
linux-user/alpha/signal.c | 8
linux-user/syscall.c | 4 ++--
3 file
There's no longer a difference between the alpha code and
the generic code.
There is a type difference in target_old_sigaction.sa_flags,
which can be resolved with a very much smaller ifdef, which
allows us to finish sharing the target_sigaction definition.
Signed-off-by: Richard Henderson
---
This means that we can share the TARGET_NR_rt_sigaction code,
and the target_rt_sigaction structure is unused. Untangling
the ifdefs so that target_sigaction can be shared will wait
until the next patch.
Signed-off-by: Richard Henderson
---
linux-user/alpha/target_signal.h | 1 +
linux-user/sy
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.
Version 2 splits patch 2 into 6.
r~
Richard Henderson (7):
We incorrectly used the offset of the non-rt sigframe.
Reviewed-by: Laurent Vivier
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
linux-user/alpha/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/alpha/signal.c b/linux-user/alpha
On Thu, 22 Apr 2021 at 18:23, Andreas Gustafsson
<1743...@bugs.launchpad.net> wrote:
>
> Ottavio Caruso wrote:
> > I am currently using:
> >
> > $ qemu-system-x86_64 --version
> > QEMU emulator version 5.2.0
> >
> > And I have no problem selecting from menu in serial console, so I
> > assume this i
From: Igor Mammedov
Do the same as in commit
(4d027afeb3a97 Virt: ACPI: fix qemu assert due to re-assigned table data
address)
for remaining tables that happen to use saved at
the beginning pointer to build header to avoid assert
when table_data is relocated due to implicit re-size.
In this ca
The following changes since commit d83f46d189a26fa32434139954d264326f199a45:
virtio-pci: compat page aligned ATS (2021-04-06 07:11:36 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
for you to fetch changes up to 9106db1038
From: Jean-Philippe Brucker
AMD IOMMU PTEs have a special mode allowing to specify an arbitrary page
size. Quoting the AMD IOMMU specification: "When the Next Level bits [of
a pte] are 7h, the size of the page is determined by the first zero bit
in the page address, starting from bit 12."
So if
The complete imm32 is computed by
%imm24 26:s1 13:1 11:1 16:10 0:11 !function=t32_branch24
so that H appears at bit 1 in a->imm in trans_BLX_i.
Returning false from any trans_* function means that the trans
function did not match. In some cases, this means that the next
possible match
On 4/22/21 5:42 AM, Bin Meng wrote:
> On Thu, Apr 22, 2021 at 5:36 PM Peter Maydell
> wrote:
>>
>> On Thu, 22 Apr 2021 at 05:29, Bin Meng wrote:
>>>
>>> On Thu, Apr 22, 2021 at 12:36 AM Philippe Mathieu-Daudé
>>> wrote:
Cc'ing Bin.
On 4/21/21 5:22 PM, Cole Robinson wrote:
>>
Hello,
I'm hitting a hard wall with qemu and efi.
I'm running multiple windows server 2019 vms which usually reboot on
updates.
The issue is, efi breaks on reboot.
It randomly(race condition?, does not occur consistently) ends up in a
blackscreen: no bootloader, no efi screen and the only way to
On 4/22/21 11:08 AM, Richard Henderson wrote:
Pass the ka_restorer value as an argument to do_sigaction,
and put it into the sigaction table.
Drop the separate TARGET_ALPHA struct target_rt_sigaction
and define TARGET_ARCH_HAS_KA_RESTORER.
Tidy up TARGET_NR_rt_sigaction, merging TARGET_ALPHA, a
Patchew URL:
https://patchew.org/QEMU/20210422193131.22560-1-lucas.ara...@eldorado.org.br/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210422193131.22560-1-lucas.ara...@eldorado.org.br
Subject: [RFC PATCH 0/4] hw/
Hi,
I'm working with Bruno Larsen (billionai) to enable the disable-tcg
option for PowerPC, right now I'm aiming at removing call to tcg-only
functions from hw/ppc, there is still some work to be done in
target/ppc.
This patch creates a spapr_hcall_tcg_stub.c file
that has the same hcalls as spap
Updated meson.build to compile spapr_hcall_tcg_stub.c instead of
spapr_hcall.c when disable-tcg option is used
Signed-off-by: Lucas Mateus Castro (alqotel)
---
hw/ppc/meson.build | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/hw/ppc/meson.build b/hw/ppc/meson.build
This file should be used instead of spapr_hcall.c when compiling
without tcg (--disable-tcg) as it does not call tcg-only functions and
trips fatal error when invalid functions are called
As of right now some functions are repeated here and in spapr_hcall.c,
as they are static, is some other metho
Somehow similar to commit 78271684719 ("cpu: tcg_ops: move to
tcg-cpu-ops.h, keep a pointer in CPUClass"):
We cannot in principle make the SysEmu Operations field definitions
conditional on CONFIG_SOFTMMU in code that is included by both
common_ss and specific_ss modules.
Therefore, what we can d
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 8
include/hw/core/sysemu-cpu-ops.h | 13 +
hw/core/cpu.c| 6 +++---
target/alpha/cpu.c | 2 +-
target/arm/cpu.c |
updated meson.build to not compile tcg-only files
Signed-off-by: Lucas Mateus Castro (alqotel)
---
target/ppc/meson.build | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/target/ppc/meson.build b/target/ppc/meson.build
index bbfef90e08..b369a6bcd0 100644
The write_elf*() handlers are used to dump vmcore images.
This feature is only meaningful for system emulation.
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 17 -
include/hw/core/sysemu-cpu-ops.h | 24 +++
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 2 --
include/hw/core/sysemu-cpu-ops.h | 4
hw/core/cpu.c| 4 ++--
target/i386/cpu.c| 4 +++-
4 files changed, 9 insertions(+), 5 deletions(-)
dif
moved the functions ppc_store_lpcr and ppc_hash64_filter_pagesizes to
common-misc.c so they can be used in a disable-tcg build and added the
necessary includes to files that call them. Created
ppc_(store|load)_vscr to be used by both tcg and kvm.
Signed-off-by: Lucas Mateus Castro (alqotel)
---
Introduce a structure to hold handler specific to sysemu.
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 5 +
include/hw/core/sysemu-cpu-ops.h | 21 +
target/alpha/cpu.c | 6 ++
target/arm/c
cpu_get_crash_info() is called on GUEST_PANICKED events,
which only occur in system emulation.
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 1 -
include/hw/core/sysemu-cpu-ops.h | 5 +
hw/core/cpu.c| 4 ++--
See rationale in previous commit. Targets should use the vmsd field
of DeviceClass, not CPUClass. As migration is not important on the
avr/lm32/moxie targets, break the migration compatibility and set
the DeviceClass vmsd field.
Signed-off-by: Philippe Mathieu-Daudé
---
target/avr/cpu.c | 2 +-
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 3 ---
include/hw/core/sysemu-cpu-ops.h | 5 +
hw/core/cpu.c| 4 ++--
target/arm/cpu.c | 2 +-
target/i386/cpu.c| 2 +-
5 files chan
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 3 ---
include/hw/core/sysemu-cpu-ops.h | 5 +
hw/core/cpu.c| 4 ++--
target/i386/cpu.c| 2 +-
4 files changed, 8 insertions(+), 6 deletions(-)
dif
Migration is specific to system emulation.
Restrict current DeviceClass::vmsd to sysemu using #ifdef'ry,
and assert in cpu_exec_realizefn() that dc->vmsd not set under
user emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
cpu.c | 1 +
target/sh4/cpu.c | 5 +++--
targe
Quoting Peter Maydell [*]:
There are two ways to handle migration for
a CPU object:
(1) like any other device, so it has a dc->vmsd that covers
migration for the whole object. As usual for objects that are a
subclass of a parent that has state, the first entry in the
VMStateDescriptio
Migration is specific to system emulation.
- Move the CPUClass::vmsd field to SysemuCPUOps,
- restrict VMSTATE_CPU() macro to sysemu,
- vmstate_dummy is now unused, remove it.
Signed-off-by: Philippe Mathieu-Daudé
---
Since v3: Merged in patch 1 (Eduardo)
therefore removed Richard R-b.
'vmsd' i
VirtIO devices are only meaningful with system emulation.
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h| 5 -
include/hw/core/sysemu-cpu-ops.h | 8
hw/core/cpu.c| 4 ++--
target/arm/cpu.c
No code uses CPUClass::get_paging_enabled() outside of hw/core/cpu.c:
$ git grep -F -- '->get_paging_enabled'
hw/core/cpu.c:74:return cc->get_paging_enabled(cpu);
hw/core/cpu.c:438:k->get_paging_enabled = cpu_common_get_paging_enabled;
target/i386/cpu.c:7418:cc->get_paging_enab
No code directly accesses CPUClass::write_elf*() handlers out
of hw/core/cpu.c (the rest are assignation in target/ code):
$ git grep -F -- '->write_elf'
hw/core/cpu.c:157:return (*cc->write_elf32_qemunote)(f, cpu, opaque);
hw/core/cpu.c:171:return (*cc->write_elf32_note)(f, cpu, cpu
No code uses CPUClass::get_memory_mapping() outside of hw/core/cpu.c:
$ git grep -F -- '->get_memory_mapping'
hw/core/cpu.c:87:cc->get_memory_mapping(cpu, list, errp);
hw/core/cpu.c:439:k->get_memory_mapping = cpu_common_get_memory_mapping;
target/i386/cpu.c:7422:cc->get_memory
To be able to later extract the cpu_get_phys_page_debug() and
cpu_asidx_from_attrs() handlers from CPUClass, un-inline them
from "hw/core/cpu.h".
Reviewed-by: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h | 33 -
hw/core/cpu.c
Introduce the cpu_virtio_is_big_endian() generic helper to avoid
calling CPUClass internal virtio_is_big_endian() one.
Similarly to commit bf7663c4bd8 ("cpu: introduce
CPUClass::virtio_is_big_endian()"), we keep 'virtio' in the method
name to hint this handler shouldn't be called anywhere but from
Missing review: patch 6, 7, 8, 10
Hi,
This series is inspired on Claudio TCG work.
Instead of separate TCG from other accelerators, here we
separate sysemu operations (system VS user).
Patches 1-5 are generic cleanups.
Patches 6-14 move from CPUClass to SysemuCPUOps
Patch 15 restricts SysemuC
Bruno Piazera Larsen writes:
>> > You are correct! I've just tweaked the code that defines spr_register and
>> > it should be working now. I'm still working in splitting the SPR functions
>> > from translate_init, since I think it would make it easier to prepare the
>> > !TCG case and for adding
Hi
I still feel QEMU's implementation is not right. Could you please check
it again.
According to https://developer.arm.com/documentation/ddi0406/c
/Application-Level-Architecture/Instruction-Details/Alphabetical-list-
of-instructions/BL--BLX--immediate-?lang=en
The encoding T2 for BLX is below:
On 4/22/21 8:08 PM, Richard Henderson wrote:
> We incorrectly used the offset of the non-rt sigframe.
>
> Signed-off-by: Richard Henderson
> ---
> linux-user/alpha/signal.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé
On Apr 22 19:58, Peter Maydell wrote:
On Thu, 22 Apr 2021 at 15:07, Klaus Jensen wrote:
On Apr 22 15:58, Klaus Jensen wrote:
>From: Klaus Jensen
>
>Hi Peter,
>
>The commit message on the patch describes the issue. This is a QEMU
>crashing bug in -rc4 that I introduced early in the cycle and n
Ottavio Caruso wrote:
> I am currently using:
>
> $ qemu-system-x86_64 --version
> QEMU emulator version 5.2.0
>
> And I have no problem selecting from menu in serial console, so I
> assume this is fixed for me. This is my command line:
>
> $ cat opt/bin/boot-netbsd-virtio
> #!/bin/sh
> qemu-sys
** Bug watch removed: github.com/novnc/noVNC/issues #431
https://github.com/novnc/noVNC/issues/431
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1725707
Title:
QEMU sends excess VNC data to webs
** Bug watch removed: bugzilla.libsdl.org/ #3287
http://bugzilla.libsdl.org/show_bug.cgi?id=3287
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1615212
Title:
SDL UI switching to monitor half-bro
** Bug watch removed: Red Hat Bugzilla #1040500
https://bugzilla.redhat.com/show_bug.cgi?id=1040500
** Bug watch removed: Red Hat Bugzilla #1262093
https://bugzilla.redhat.com/show_bug.cgi?id=1262093
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** Bug watch removed: Sourceware.org Bugzilla #5475
https://sourceware.org/bugzilla/show_bug.cgi?id=5475
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1642421
Title:
qemu-system-x86_64: ipv6 and
** Bug watch removed: Red Hat Bugzilla #1135772
https://bugzilla.redhat.com/show_bug.cgi?id=1135772
** Bug watch removed: Red Hat Bugzilla #1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
** Changed in: qemu
Assignee: Eduardo Habkost (ehabkost) => (unassigned)
--
You rece
** Changed in: qemu
Assignee: Stefan Weil (ubuntu-weilnetz) => (unassigned)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1766841
Title:
QEMU 2.12 Running Problem in Windows 7 Installation
St
** Bug watch removed: Red Hat Bugzilla #1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
** Bug watch removed: Red Hat Bugzilla #1593190
https://bugzilla.redhat.com/show_bug.cgi?id=1593190
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** Bug watch removed: Red Hat Bugzilla #980714
https://bugzilla.redhat.com/show_bug.cgi?id=980714
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1820247
Title:
QEMU random crash caused by libspic
** Bug watch removed: bugs.centos.org/ #17385
https://bugs.centos.org/view.php?id=17385
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1879425
Title:
The thread of "CPU 0 /KVM" keeping 99.9%CPU
It's right there in trans_BLX_i:
if (s->thumb && (a->imm & 2)) {
return false;
}
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1925
When i try to do it manually using the instructions provided here:
https://mricher.fr/post/boot-from-an-efi-shell/
I see that
Mapping table
FS0: Alias(s):HD0m:;BLK4:
VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A)/HD(12,GPT,49037CF8-B2EF-5B4B-8CCE-EF5803A9E8B3,0x3D0
On Thu, 22 Apr 2021 at 15:07, Klaus Jensen wrote:
>
> On Apr 22 15:58, Klaus Jensen wrote:
> >From: Klaus Jensen
> >
> >Hi Peter,
> >
> >The commit message on the patch describes the issue. This is a QEMU
> >crashing bug in -rc4 that I introduced early in the cycle and never
> >found in time. Lac
On 4/22/21 11:43 AM, Kevin Wolf wrote:
> Normally, blk_new_open() just shares all permissions. This was fine
> originally when permissions only protected against uses in the same
> process because no other part of the code would actually get to access
> the block nodes opened with blk_new_open(). H
Le 22/04/2021 à 20:08, Richard Henderson a écrit :
> We incorrectly used the offset of the non-rt sigframe.
>
> Signed-off-by: Richard Henderson
> ---
> linux-user/alpha/signal.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/linux-user/alpha/signal.c b/linux-user/alph
Patchew URL:
https://patchew.org/QEMU/20210422180819.252121-1-richard.hender...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210422180819.252121-1-richard.hender...@linaro.org
Subject: [PATCH 0/2] linux
We incorrectly used the offset of the non-rt sigframe.
Signed-off-by: Richard Henderson
---
linux-user/alpha/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/alpha/signal.c b/linux-user/alpha/signal.c
index c5c27ce084..86f5d2276d 100644
--- a/linux-user/alp
Pass the ka_restorer value as an argument to do_sigaction,
and put it into the sigaction table.
Drop the separate TARGET_ALPHA struct target_rt_sigaction
and define TARGET_ARCH_HAS_KA_RESTORER.
Tidy up TARGET_NR_rt_sigaction, merging TARGET_ALPHA, and
TARGET_SPARC into common code.
Signed-off-by
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.
Because do_sigaction didn't see TARGET_ARCH_HAS_SA_RESTORER
(which is correct for alpha, as the field isn't present in
the structure), we didn't
Hi Alex and QEMU developers,
Recently I was working with the TCG plugin. I found that
`qemu_plugin_cb_flags` seems to reserve the functionality to read / write
CPU register state, I'm wondering if you can share some roadmap or thoughts
on this feature?
Personally I see reading the CPU register st
Creating a device with a number of queues that isn't supported by the
backend is pointless, the device won't work properly and the error
messages are rather confusing.
Just fail to create the device if num-queues is higher than what the
backend supports.
Since the relationship between num-queues
VIRTIO_F_RING_PACKED and VIRTIO_F_IOMMU_PLATFORM need to be supported by
the vhost device, otherwise advertising it to the guest doesn't result
in a working configuration. They are currently not supported by the
vhost-user-blk export in QEMU.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1935
1 - 100 of 344 matches
Mail list logo
