In cfcacba an `error_report` was added to this file, but the
corresponding include of `qemu/error-report.h` was missed. This
only becomes apparent when building against Xen 4.20+.
Signed-off-by: Adam Williamson
---
hw/xen/xen_pt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/xen
On Mon, Feb 03, 2025 at 11:33:54AM +, Jonathan Cameron wrote:
>
> > >
> > > > +int dpa_range_count = san_info->dpa_range_count;
> > > > +int rc = 0;
> > > > +
> > > > +for (int i = 0; i < dpa_range_count; i++) {
> > > > +rc = sanitize_range(ct3d,
> > > > san_info->dpa_r
On Fri, Jan 24, 2025 at 03:19:46PM +, Jonathan Cameron wrote:
> On Thu, 23 Jan 2025 10:39:03 +0530
> Vinayak Holikatti wrote:
>
> > CXL spec 3.1 section 8.2.9.9.5.3 describes media operations commands.
> > CXL devices supports media operations Sanitize and Write zero command.
>
> As
, upon creating the new XML based on the original .qcow2 file, it
still changed the CPU back to qemu default instead of host-passthrough.
Regards,
A>AM
On 1/8/25 09:22, Daniel P. Berrangé wrote:
On Wed, Jan 08, 2025 at 09:13:47AM -0600, Adam wrote:
I have backups of the xml and image, and t
I have backups of the xml and image, and they too report the same issue.
vFRANK
88c29f0e-0d18-42f9-a198-bc9c679fdf8d
On 1/8/25 08:58, Daniel P. Berrangé wrote:
On Wed, Jan 08, 2025 at 08:51:52AM -0600, Adam wrote:
TWIMC:
Had an issue with VM networking that turned out to be the host
TWIMC:
Had an issue with VM networking that turned out to be the host. In the
process of troubleshooting, I
sudo apt reinstall libvirt (and other QEMU/KVM virtualization
dependencies)
Now I am getting this particular error when trying to use the
host-passthrough for the CPU.
"error
\
-append "console=ttyS0 nokaslr" \
-initrd ramdisk.img \
-boot c -kernel $HOME/workspace/kvmctf-6.1.74/bzImage/bzImage
On Sat, Sep 7, 2024 at 2:58 PM Kenneth Adam Miller <
kennethadammil...@gmail.com> wrote:
> Hello,
>
> I've got qemu built and now I
Hello,
I've got qemu built and now I need to figure out how to run it with what
I've got. I have a vmlinux and a bzImage that I want to serve as the kernel
that QEMU runs with, and a single binary, let's just call it
literally `program`, that I want to issue a command to run once QEMU boots
with t
I got this to build following option 2 listed and it built with ubuntu
18.04.
On Sat, Sep 7, 2024 at 4:45 AM Peter Maydell
wrote:
> On Sat, 7 Sept 2024 at 07:39, Michael Tokarev wrote:
> >
> > 07.09.2024 02:59, Kenneth Adam Miller wrote:
> > > Hello,
> > >
&
Hello,
I'm on commit bd80b59 and my host is:
$lsb_release -s
...
Description: Pop!_OS 20.04 LTS
Release: 20.04In file included from
...
I get a compile error:
...
/home/kennethadammiller/workspace/vm_escape/qemu/include/hw/xen/xen_backend.h:4,
from
/home/kennethadammiller/worksp
w64 gdb, but to
somehow launch in the context of WSL2)
Could I please get some help?
Sidenote: IMO the bug tracker should cc this list, at least for the initial
issue message.
Thanks,
Adam
On Thu, Oct 27, 2022 at 11:58:54AM +0100, Jonathan Cameron wrote:
> On Wed, 26 Oct 2022 16:47:18 -0400
> Gregory Price wrote:
>
> > On Wed, Oct 26, 2022 at 08:13:24PM +, Adam Manzanares wrote:
> > > On Tue, Oct 25, 2022 at 08:47:33PM -0400, Gregory Price wrote:
On Tue, Oct 25, 2022 at 08:47:33PM -0400, Gregory Price wrote:
> Submitted as an extention to the multi-feature branch maintained
> by Jonathan Cameron at:
> https://urldefense.com/v3/__https://gitlab.com/jic23/qemu/-/tree/cxl-2022-10-24__;!!EwVzqGoTKBqv-0DWAJBm!RyiGL5B1XmQnVFwgxikKJeosPMKtoO1cTr61
terface.
>
>
> By "bootloader" you mean grub, correct?
Yeah, exactly, the grub menu. On our installer images we use it to
offer various choices (install, run a media check and install, run
rescue mode...)
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
On Tue, 2022-09-27 at 13:34 -0300, Daniel Henrique Barboza wrote:
> Hi Adam,
>
> On 9/26/22 06:26, Gerd Hoffmann wrote:
> > On Sat, Sep 24, 2022 at 12:12:45AM -0700, Adam Williamson wrote:
> > > On Mon, 2022-09-19 at 06:42 +0200, Gerd Hoffmann wrote:
> > > >
st to understand the TCG documentation but
this appears to not be too straightforward.
On Fri, Jul 22, 2022 at 5:31 AM Alex Bennée wrote:
>
> Kenneth Adam Miller writes:
>
> > I need to determine the set of instruction encodings that the TCG can
> support for a given platform. I am n
when the target encounters the instruction
would be good. Additionally, the ability to force the translation of
arbitrary encodings would be good. I would like to not have to engineer
some binary file format.
On Wed, Jul 20, 2022 at 1:37 PM Peter Maydell
wrote:
> On Wed, 20 Jul 2022 at 17
I have
to query and interact with the TCG to find out what opcodes are supported
or not.
On Wed, Jul 20, 2022 at 4:46 AM Alex Bennée wrote:
>
> Kenneth Adam Miller writes:
>
> > Hello,
> >
> > I would like to be able to, from the linux-user/main.c, access the
> ta
Hello,
I would like to be able to, from the linux-user/main.c, access the target's
registered TranslatorOps instance. How would I do that when 1) the TCG is
correctly initialized and ready to run 2) before QEMU starts to run or when
it is safely paused?
Actually, I have gotten the QEMU disassembler to run with some short
customization. But I am having trouble understanding the output. I see lots
of lines like this:
|
OBJD-H: 06040102a83507000cd8027620272573004c04cd20c100782244038c
On Sun, Jun 26, 2022 at 11:00 PM Kenneth Adam Miller
Hello all,
How can I call the QEMU disassembler to run on an argument set of bytes?
Hello all,
Suppose I am wanting to implement and test for the TCG. Is there any set of
interactive binaries or other things that I could use to work with it?
Could I open a shell to it? Perhaps feed it specific byte sequences for
tests to ensure correct operation? Are there a canonical set of uni
Hello,
I am working on a qemu target under development. and I am wondering how I
should differentiate the MachineState from the MachineClass.
Hello all,
I'm starting to develop with the surrounding qemu libraries trying to add
the internals of a system target. I am working with the type system right
now, which I do know how to interact with. I think there is like some way
to script or interact with the qemu periphery via a cli. I found
On Fri, Apr 01, 2022 at 02:30:34PM +0100, Jonathan Cameron wrote:
> On Thu, 31 Mar 2022 22:13:20 +
> Adam Manzanares wrote:
>
> > On Wed, Mar 30, 2022 at 06:48:48PM +0100, Jonathan Cameron wrote:
> > > On Tue, 29 Mar 2022 18:13:59 +
> > > Adam Manzanare
On Wed, Mar 30, 2022 at 06:48:48PM +0100, Jonathan Cameron wrote:
> On Tue, 29 Mar 2022 18:13:59 +
> Adam Manzanares wrote:
>
> > On Fri, Mar 18, 2022 at 03:05:53PM +, Jonathan Cameron wrote:
> > > From: Ben Widawsky
> > >
> > > A CXL device i
On Wed, Mar 30, 2022 at 01:15:58PM +0100, Jonathan Cameron wrote:
> On Tue, 29 Mar 2022 12:53:51 -0700
> Davidlohr Bueso wrote:
>
> > On Tue, 29 Mar 2022, Adam Manzanares wrote:
> > >> +typedef struct cxl_device_state {
> > >> +MemoryRegion device_regi
, 0x10)
> +FIELD(CXL_DEV_MAILBOX_STS, BG_OP, 0, 1)
> +FIELD(CXL_DEV_MAILBOX_STS, ERRNO, 32, 16)
> +FIELD(CXL_DEV_MAILBOX_STS, VENDOR_ERRNO, 48, 16)
> +
8.2.8.4.7
> +REG64(CXL_DEV_BG_CMD_STS, 0x18)
> +FIELD(CXL_DEV_BG_CMD_STS, BG, 0, 16)
Should we call this OP since it is implied that we are BG given the register?
> +FIELD(CXL_DEV_BG_CMD_STS, DONE, 16, 7)
NUM_DONE? since this is a percentage.
> +FIELD(CXL_DEV_BG_CMD_STS, ERRNO, 32, 16)
Isn't this a RET_CODE since it is only valid if previous field is 100%
> +FIELD(CXL_DEV_BG_CMD_STS, VENDOR_ERRNO, 48, 16)
VENDOR_RET_CODE since the same rule for the previous field applies here.
> +
> +REG32(CXL_DEV_CMD_PAYLOAD, 0x20)
> +
> +#endif
> --
> 2.32.0
>
>
+cc Dave, Klaus, Tong
Other than the minor issues raised.
Looks good.
Reviewed by: Adam Manzanares
tain DVSEC IDs, and can [optionally]
> + * implement others.
> + *
> + * CXL 2.0 Device: 0, [2], 5, 8
> + * CXL 2.0 RP: 3, 4, 7, 8
> + * CXL 2.0 Upstream Port: [2], 7, 8
> + * CXL 2.0 Downstream Port: 3, 4, 7, 8
> + */
> +
> +/* CXL 2.0 - 8.1.5 (ID 0003) */
> +struct cxl_dvsec_port_extensions {
> +struct dvsec_header hdr;
> +uint16_t status;
> +uint16_t control;
> +uint8_t alt_bus_base;
> +uint8_t alt_bus_limit;
> +uint16_t alt_memory_base;
> +uint16_t alt_memory_limit;
> +uint16_t alt_prefetch_base;
> +uint16_t alt_prefetch_limit;
> +uint32_t alt_prefetch_base_high;
> +uint32_t alt_prefetch_base_low;
Limit high?
> +uint32_t rcrb_base;
> +uint32_t rcrb_base_high;
> +};
> +QEMU_BUILD_BUG_ON(sizeof(struct cxl_dvsec_port_extensions) != 0x28);
> +
> +#define PORT_CONTROL_OFFSET 0xc
> +#define PORT_CONTROL_UNMASK_SBR 1
> +#define PORT_CONTROL_ALT_MEMID_EN4
> +
> +/* CXL 2.0 - 8.1.6 GPF DVSEC (ID 0004) */
> +struct cxl_dvsec_port_gpf {
> +struct dvsec_header hdr;
> +uint16_t rsvd;
> +uint16_t phase1_ctrl;
> +uint16_t phase2_ctrl;
> +};
> +QEMU_BUILD_BUG_ON(sizeof(struct cxl_dvsec_port_gpf) != 0x10);
> +
> +/* CXL 2.0 - 8.1.8/8.2.1.3 Flexbus DVSEC (ID 0007) */
> +struct cxl_dvsec_port_flexbus {
> +struct dvsec_header hdr;
> +uint16_t cap;
> +uint16_t ctrl;
> +uint16_t status;
> +uint32_t rcvd_mod_ts_data_phase1;
> +};
> +QEMU_BUILD_BUG_ON(sizeof(struct cxl_dvsec_port_flexbus) != 0x14);
> +
> +/* CXL 2.0 - 8.1.9 Register Locator DVSEC (ID 0008) */
> +struct cxl_dvsec_register_locator {
> +struct dvsec_header hdr;
> +uint16_t rsvd;
> +uint32_t reg0_base_lo;
> +uint32_t reg0_base_hi;
> +uint32_t reg1_base_lo;
> +uint32_t reg1_base_hi;
> +uint32_t reg2_base_lo;
> +uint32_t reg2_base_hi;
> +};
> +QEMU_BUILD_BUG_ON(sizeof(struct cxl_dvsec_register_locator) != 0x24);
> +
> +/* BAR Equivalence Indicator */
> +#define BEI_BAR_10H 0
> +#define BEI_BAR_14H 1
> +#define BEI_BAR_18H 2
> +#define BEI_BAR_1cH 3
> +#define BEI_BAR_20H 4
> +#define BEI_BAR_24H 5
> +
> +/* Register Block Identifier */
> +#define RBI_EMPTY 0
> +#define RBI_COMPONENT_REG (1 << 8)
> +#define RBI_BAR_VIRT_ACL (2 << 8)
> +#define RBI_CXL_DEVICE_REG (3 << 8)
> +
> +#endif
> --
> 2.32.0
>
>
+cc (Klaus, Dave, Tong)
Other than the minor cleanups/nits.
Looks good.
Reviewed by: Adam Manzanares
iceClass;
> DECLARE_OBJ_CHECKERS(PCIDevice, PCIDeviceClass,
> PCI_DEVICE, TYPE_PCI_DEVICE)
>
> +/*
> + * Implemented by devices that can be plugged on CXL buses. In the spec,
> this is
> + * actually a "CXL Component, but we name it device to match the PCI naming.
> + */
> +#define INTERFACE_CXL_DEVICE "cxl-device"
> +
> /* Implemented by devices that can be plugged on PCI Express buses */
> #define INTERFACE_PCIE_DEVICE "pci-express-device"
>
> --
> 2.32.0
>
>
Looks good.
Reviewed by: Adam Manzanares
Could someone add me to wiki? Username: sheerun
I'd like to describe on https://wiki.qemu.org/Hosts/Mac how to setup QEMU
on Mac with volumes.
Best Regards,
Adam Stankiewicz
Hello all,
I would like to emulate something on a pi so that I don't have to pay as
high of a translation penalty since the guest and host will share the same
arch. I'm finding that on some forums that people have been having trouble
getting QEMU to run on raspberry pi. The posts are kind of old,
build successfully.
Regards,
Adam
I'm using.
Is this a musl issue or a qemu issue?
Thanks,
Adam
Dockerfile
Description: Binary data
QEMU_CFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes
-Wredundant-decls -Wundef -Wwrite-s
Would it be possible somehow to save the TCG cache, as with user binaries,
but for a kernel module, before then loading that kernel module into memory
the target architecture whether in or outside of QEMU?
On Wed, Jan 19, 2022 at 2:42 PM Kenneth Adam Miller <
kennethadammil...@gmail.com>
The source for it isn't available in order that it be compiled to the
desired architecture.
What 3rd party forks take this approach?
On Wed, Jan 19, 2022 at 2:06 PM Alex Bennée wrote:
>
> Kenneth Adam Miller writes:
>
> > Hello all,
> >
> > I just wa
Hello all,
I just want to pose the following problem:
There is a kernel module for a non-native architecture, say, arch 1. For
performance reasons, the rest of all of the software needs to run natively
on a different arch, arch 2. Is there any way to perhaps run multiple QEMU
instances for the di
ähnel
Signed-off-by: Adam Lackorzynski
---
pc-bios/multiboot.bin | Bin 1024 -> 1536 bytes
pc-bios/optionrom/multiboot.S | 10 ++---
pc-bios/optionrom/optionrom.h | 77 ++
3 files changed, 82 insertions(+), 5 deletions(-)
diff --git a/pc-bios/multiboot.
Also, that command flag was *really really buried, and I couldn't find it
at all in the help.
On Wed, Sep 22, 2021 at 1:50 PM Kenneth Adam Miller <
kennethadammil...@gmail.com> wrote:
> It's just the overhead of running a cross architecture emulation. For Arm
> to x86_64
ck in to make sure that that wasn't it.
I can't see it right now, I was just looking into it.
On Wed, Sep 22, 2021 at 1:39 PM Alex Bennée wrote:
>
> Kenneth Adam Miller writes:
>
> > Well, maybe I'm understanding that wrong. I am talking the cache that
> the
54 AM Alex Bennée wrote:
>
> Kenneth Adam Miller writes:
>
> > Hello all,
> >
> > I just want to ask this one question: if I change the qemu tcg cache
> > size (TB_JMP_CACHE_SIZE), will that force any errors at run time?
>
> Hopefully not - for both user-mo
Hello all,
I just want to ask this one question: if I change the qemu tcg cache size (
TB_JMP_CACHE_SIZE), will that force any errors at run time?
Hi Andre,
On Wed Sep 08, 2021 at 00:47:10 +0100, Andre Przywara wrote:
> On Wed, 8 Sep 2021 01:25:04 +0200
> Adam Lackorzynski wrote:
>
> Hi Adam,
>
> > On Mon Sep 06, 2021 at 16:34:03 +0100, Andre Przywara wrote:
> > > On Sat, 4 Sep 2021 21:26:45 +0200
Hi Andre,
On Mon Sep 06, 2021 at 16:34:03 +0100, Andre Przywara wrote:
> On Sat, 4 Sep 2021 21:26:45 +0200
> Adam Lackorzynski wrote:
>
> Hi Adam,
>
> > while trying to launch an EFI-enabled arm32 Linux binary (zImage) I
> > noticed I get an undefined instruc
001 1 @S_xri_rot
CMP_xri 001 1010 1 @S_xri_rot
CMN_xri 001 1011 1 @S_xri_rot
Any thoughts on this?
Adam
Hello,
I am trying to discover how to schedule QEMU to begin actual emulation as
currently my target correctly starts QEMU but only shows the shell, and not
even boot loading occurs within QEMU. I'm trying to learn from example, and
so will focus my questions only on X86. I can see the MachineClas
Hello,
I think I need a concurrent radix tree that is written to work with atomic
updates. I would like to ask if anyone knows of one within qemu? Or at
least to efficiently obtain the page address/mmu index corresponding for a
given address.
Is there any documentation on cpu_mmu_index? Each tar
ell
> wrote:
> >
> > On Tue, 20 Jul 2021 at 10:06, Peter Maydell
> wrote:
> > >
> > > On Mon, 19 Jul 2021 at 23:20, Kenneth Adam Miller
> > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > I get the f
I saw that TARGET_PAGE_SIZE gets a value that depends on TARGET_PAGE_BITS
using tags and grep, but I did not see either of them take a value that is
beyond the idxmap size.
On Tue, Jul 20, 2021 at 5:07 AM Peter Maydell
wrote:
> On Mon, 19 Jul 2021 at 23:20, Kenneth Adam Miller
>
Hello,
I get the following error:
-c ../accel/tcg/cputlb.c
../qemu/accel/tcg/cputlb.c: In function 'tlb_flush_page_by_mmuidx':
../qemu/accel/tcg/cputlb.c:602:23: error: comparison is always true due to
limited range of data type [-Werror=type-limits]
} else if (idxmap < TARGET_PAGE_SIZE) {
Hello all,
I'm getting a strange error while doing some system target development. In
the periphery of the qemu internals (things specifically other than the
target), I'm getting uninitialized variable errors. I'm pretty sure I can't
submit a patch to modify those internals, so I was wondering how
After checking around, I don't see any _user_ss in any target
directory. And I only see *_user_ss in the linux-user subdirectory. Were
you talking about that meson.build in linux-user?
On Fri, Jul 16, 2021 at 1:20 PM Kenneth Adam Miller <
kennethadammil...@gmail.com> wrote:
> Righ
ar to me as I'm
just becoming familiar with the code base.
On Fri, Jul 16, 2021 at 1:05 PM Peter Maydell
wrote:
> On Fri, 16 Jul 2021 at 18:50, Kenneth Adam Miller
> wrote:
> > There's a lot of files and I don't want to muddy up the discussion with
> too many detai
ared.
On Fri, Jul 16, 2021 at 10:38 AM Peter Maydell
wrote:
> On Fri, 16 Jul 2021 at 16:16, Kenneth Adam Miller
> wrote:
> >
> > When I go to build the qemu softmmu target the shared files - the
> i386_ss of my arch - gives problems where the build system isn't speci
hu, Jul 15, 2021 at 11:39 AM Kenneth Adam Miller <
kennethadammil...@gmail.com> wrote:
> Oh I didn't know that there was a i386_user_ss in order to see that it was
> intended that they were shared that way, so I initially thought that
> i386_ss was user only until I saw it in the b
Oh I didn't know that there was a i386_user_ss in order to see that it was
intended that they were shared that way, so I initially thought that
i386_ss was user only until I saw it in the build.
On Thu, Jul 15, 2021 at 11:35 AM Peter Maydell
wrote:
> On Thu, 15 Jul 2021 at 17:25, Kenn
M Peter Maydell
wrote:
> On Thu, 15 Jul 2021 at 16:59, Kenneth Adam Miller
> wrote:
> >
> > If I am right, the softmmu/system build target for each architecture
> subsumes the source of the user target.
>
> I'm not sure what you mean by "subsumes" here.
If I am right, the softmmu/system build target for each
architecture subsumes the source of the user target. It's what I see in the
build of i386. But then, I think the user targets have some dedicated user
layer which allow a foreign architecture user binary to be relayed through
in order to map t
Hello,
I was wondering if the meson build system is symbolic when initializing
variables? For example, I have:
var1=ss.source_set()
var2=ss.source_set()
And in the body of the rest of meson.build there are mutually exclusive
additions to var1 and var2. When I go to configure and build, I configu
Hello,
I just wanted to ask how I can get started developing other than just
starting building? QEMU is a huge project, and getting familiar with all of
the source and stuff is a lot of work. Probably, it wouldn't be helpful to
know the entire source, but just what I need.
I want to add a new sys
Hello,
I'm new and can't use GitHub/GitLab, but I noticed this about the Windows
installer:
Does not add (nor offer to add) "C:\Program Files\qemu" to path.
It should maybe be an optional choice in the installer.
Have a wonderful day!
Hello,
Sorry I cannot use github/gitlab.
I'm new to QEMU but I found this typo (mismatched braces) in the *installed*
HTML manual:
In: "file:///C:/Program%20Files/qemu/share/doc/tools/qemu-img.html"
This should *not* have ending ']':
measure [--output=OFMT] [-O OUTPUT_FMT] [-o OPTIONS] [--size
This got resolved along the way and wasn't really a qemu bug anyway.
** Changed in: qemu
Status: Incomplete => 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/1762558
Title:
Many
Public bug reported:
There's a documented change in qemu 6.0:
https://qemu-project.gitlab.io/qemu/system/removed-features.html#floppy-
controllers-drive-properties-removed-in-6-0
where you can't configure floppy controller device properties with
-global any more. However, there's a thing you cou
Hi,
On Sun Mar 21, 2021 at 12:56:12 +, Peter Maydell wrote:
> On Sat, 20 Mar 2021 at 22:38, Adam Lackorzynski wrote:
> >
> > Hi,
> >
> > I'm seeing a regression in Arm's vfp handling, giving an undefined
> > instruction when reading mvfr1 in PL2
Hi,
I'm seeing a regression in Arm's vfp handling, giving an undefined
instruction when reading mvfr1 in PL2/armv7 although the FPU is enabled.
The following makes it work again for me, however this just looks like a
band-aid. Thanks for taking a look.
Adam
diff --git a/target/arm
Thank you for your answer, we understand that compatibility with all Linux
versions is a priority for you.
We have small hope that this email will help other QEMU users in struggling
with QNX on QEMU.
Regards,
Adam Olek
-Original Message-
From: Peter Maydell [mailto:peter.mayd
x27;t negative impact on anything else?
Regards,
Adam Olek
Senior Software Engineer
APTIV
Different problem here I think John. If you run the following you should
the user mode networking that involves Slirp and has the problem.
```
qemu-system-i386 -m 700 -hda -net user -net nic
```
It's worth noting however that the problem most regularly manifest
itself when a remote server deliv
Public bug reported:
I have been doing some work cross compiling qemu for Windows using a
minimal Fedora container. Recently I started hitting some timeouts on
the CI service and noticed a build of all targets was going over 1 hour.
It seems like the 'cmp' utility from diffutils is used somewhere
On Mon Jun 01, 2020 at 13:36:13 +0100, Peter Maydell wrote:
> On Sat, 30 May 2020 at 00:07, Adam Lackorzynski wrote:
> >
> > Initialize the CPU interface registers also
> > for Cortex-A15 and Cortex-A7 CPU models, in
> > the same way as done for 64bit CPU models.
&g
Initialize the CPU interface registers also
for Cortex-A15 and Cortex-A7 CPU models, in
the same way as done for 64bit CPU models.
This fixes usage of GICv3 in virtualization
contexts in 32bit configurations.
Signed-off-by: Adam Lackorzynski
---
target/arm/cpu.c | 6 ++
1 file changed, 6
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Low
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM
Can confirm this is still an issue with 4.1.0.
?field.comment=Can confirm this is still an issue with 4.1.0.
** Attachment added: "Files created on Windows and Debian"
https://bugs.launchpad.net/qemu/+bug/1759522/+attachment/5300530/+files/vhdx_comparison.7z
--
You received this bug notifi
Hi,
I've attached some example files to
https://bugs.launchpad.net/qemu/+bug/1759522 - the bug still exists in qemu
4.1.0.
Thanks,
Adam
ails. No need for full XP
installation to test that.
Nevertheless I would really appreciate Paolo looking into this.
Many thanks for great software,
Adam
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
deve
el0 00000e2a6990
>D/TC:0 0 get_fault_type:602 [abort] Unhandled fault!
Thanks,
Adam Parker
On Thu, Apr 04, 2019 at 02:12:30AM -0400, Pankaj Gupta wrote:
> > All this ad hoc IS_DAX conditional logic is getting pretty nasty.
> >
> > xfs_file_mmap(
> >
> > {
> > struct inode*inode = file_inode(filp);
> >
> > if (vma->vm_flags & VM_SYNC) {
> > if (!IS_DAX(inode
in $SECOND; do strings $d | grep '\.dll' | sort -u |
xargs -I{} readlink -e /usr/x86_64-w64-mingw32/sys-root/mingw/bin/{};
done)
echo $FIRST $SECOND $THIRD | sed 's/ /\n/g' | sort -u | xargs -I{} cp
-v {} $STAGING
--Adam
On Thu, 31 Jan 2019 at 21:49, Daniel P. Berrangé wrote:
>
umented at
https://qemu.weilnetz.de/FAQ but this doesn't cover building the actual
installer.
Regards,
Adam
l] [/a] ([/r] [/x filespec [...]] filespec [...] |
/oname=outfile one_file_only)
Error in script "/drone/src/qemu.nsi" on line 122 -- aborting creation process
make: *** [Makefile:915: qemu-setup-3.99.99.exe] Error 1
Any ideas?
Platform is Fedora / mingw x86_64-w64-mingw32 in a Docker container.
Thanks,
Adam
I'm not subscribed there, so will note here: I tried the proposed
changes - the commits from https://lists.gnu.org/archive/html/qemu-
devel/2018-12/msg04819.html , backported to 3.0.0 - and that seems to
work. A test which would previously have hit this bug ran OK, without
the changes to the en-us
solve this problem.
I'll try and find a minute to do a scratch build with this patch (and
without my keymap patch) and throw it on openQA staging, since openQA
seems to do a great job of testing qemu input code. :P
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Indeed the bug does not exist in this exact form any more, but it seems
the stray '86' keymap entry *does* still cause problems in current qemu
in one specific case:
https://bugzilla.redhat.com/show_bug.cgi?id=1658676
basically, if using 'usb-kbd', we still get trouble when openQA (os-
autoinst)
This is
important because of applications that need OpenGL ES, SDL2, or Love2D.
Sincerely,
Adam Palmer
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Use an int64_t as a return type to restore
the negative check for arm_load_as.
Signed-off-by: Adam Lackorzynski
---
hw/arm/boot.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index e09201cc97..ca9467e583 100644
--- a/hw/arm/boot.c
Up to you, of course. Just realized I didn't mention here that I also
reported this downstream, and since it turns out to be not triggered by
a qemu change I've been doing most of the investigation there:
https://bugzilla.redhat.com/show_bug.cgi?id=1565354
So far it's looking like the change that
...on the other hand, I was clearly not thinking straight in associating
this with the qemu version bump in Rawhide, because we don't *run* that
qemu. We use the qemu from the worker host, not from the image under
test, and the worker hosts are not running Rawhide, and their qemu
hasn't changed dur
Nothing about SPICE changed in the affected time frame. This started
happening between 2018-04-02 and 2018-04-07. The last time SPICE was
changed in Rawhide was on 2018-02-09. However, qemu was bumped from rc1
to rc2 on 2018-04-05.
It's possible that https://bugzilla.redhat.com/show_bug.cgi?id=156
Public bug reported:
Since qemu 2.12.0 rc2 - qemu-2.12.0-0.6.rc2.fc29 - landed in Fedora
Rawhide, just about all of our openQA-automated tests of Rawhide guests
which run with qxl / SPICE graphics in the guest have died partway in,
always shortly after the test switches from the installer (an X
en
Public bug reported:
This has been reported and discussed downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1484130
but doesn't seem to be getting a lot of traction there.
Basically, with qemu since at least 2.10, you cannot use a disk image on
an SMB share that's mounted with protocol ve
Note: I wondered if specifying a correct model for qemu-keymap to pass
to xkb would help. But it doesn't :( That is, these:
qemu-keymap -l us
qemu-keymap -l us -m pc101
qemu-keymap -l us -m pc104
qemu-keymap -l us -m pc105
all produce the same output except for the commented-out 'model' line at
t
Confirmed that dropping the offending keycode 86 definition out of
keymaps/en-us fixes the problem. Scratch build for Fedora Rawhide was
https://koji.fedoraproject.org/koji/taskinfo?taskID=23814932 , I'll
probably send this out as an official build so I can get os-autoinst
built without hacking up
FWIW, I think this keycode represents the key between the left shift key
and the first letter key on the fourth row, if there is one. European
keyboards have one, and on e.g. a UK keyboard it types a \ unshifted and
a | shifted - this is exactly how it looks in the en-gb keymap file:
# evdev 86 (0
Aha. This looks like my bug!
I'm running into this in what I suspect is the same situation as Michal
Nowak: openQA. But in Fedora. openQA (well, its test runner, os-
autoinst) works by running virtual machines and interacting with them
over VNC. It seems that with qemu 2.11, typing certain charact
I found something interesting using showkey in the VM. This is all
assuming en-US everywhere, note. On a US keyboard, "<" is a shifted
comma (shift-,), ">" is a shifted period (shift-.), and "|" is a shifted
backslash (shift-\).
If I run showkey and try the affected characters in virt-manager, the
I also confirm Michal's observation of virt-manager and tigervnc
behaving differently with the same VM: I ran a VM set up with VNC
display server in virt-manager and can type < from the virt-manager UI
fine, but if I connect to the same VM with tigervnc and try to type < ,
I get > . This is with cu
I note this block in pc-bios/keymaps/en-us with interest:
# evdev 86 (0x56), QKeyCode "less", number 0x56
less 0x56
greater 0x56 shift
bar 0x56 altgr
brokenbar 0x56 shift altgr
That block was added in commit a7815faffb2bd594b92aa3542d7b799cc89c5414
, which I am very suspicious was the cause of th
Note, os-autoinst is its own VNC client. Most of the implementation can
be found in https://github.com/os-autoinst/os-
autoinst/blob/master/consoles/VNC.pm . The functions relevant to sending
key events are `shift_keys`, `init_x11_keymap`, `map_and_send_key`, and
`_send_key_event`.
--
You receive
On Wed, Sep 13, 2017 at 6:47 PM, John Snow wrote:
> On 09/13/2017 05:36 PM, Adam Wolfe Gordon via Qemu-devel wrote:
>> On Wed, Sep 13, 2017 at 2:53 PM, John Snow wrote:
>> We have a storage orchestration service that manages our ceph block
>> storage clusters and doesn
1 - 100 of 335 matches
Mail list logo
