Kindly ping...
On 2020/12/15 20:30, Jiahui Cen wrote:
> A VM in the cloud environment may use a virutal disk as the backend storage,
> and there are usually filesystems on the virtual block device. When backend
> storage is temporarily down, any I/O issued to the virtual block device
> will cause
On 2020/12/17 18:05, Stefan Hajnoczi wrote:
> On Mon, Nov 30, 2020 at 09:11:03PM +0800, Keqian Zhu wrote:
>> @@ -1839,15 +1841,26 @@ static void dirty_memory_extend(ram_addr_t
>> old_ram_size,
>> new_blocks = g_malloc(sizeof(*new_blocks) +
>>sizeof(new_b
Hi,
I noticed that booting Linux on PXA emulations no longer works with qemu v5.2.
When trying to boot akita, borzoi, or similar emulations, I get the following
crash.
[0.965279] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT ARM
[0.967273] Modules linked in:
[0.967875]
Hi all,
since qemu v5.1, nvme support has been dropped from several architectures.
Well, it was not exactly dropped, but disabled.
On those architectures, trying to boot from an nvme drive now results
in the following or a similar error message.
qemu-system-alpha: -device nvme,serial=foo,drive=d
I unmasked qemu-5.2.0-r1, well, actually any newer qemu coming
from gentoo, and rebuild the software. The situation is still
reproducible, which confirms what I tested yesterday with the
patch. I also cleaned up the launch script to remove several
spice related unneeded since I use the gtk display,
Yes, that's fine.
On Thu, Dec 17, 2020 at 2:11 AM Philippe Mathieu-Daudé wrote:
>
> Hi Huacai,
>
> On 12/15/20 1:57 PM, Huacai Chen wrote:
> > Preparing to add Loongson-3 machine support, add Loongson-3's LEFI (a
> > UEFI-like interface for BIOS-Kernel boot parameters) helpers first.
> >
> > Revi
Hi Michael,
On 2020/12/20 3:06, Michael S. Tsirkin wrote:
> On Fri, Dec 18, 2020 at 01:56:29PM +0800, Jiahui Cen wrote:
>> Hi Michael,
>>
>> On 2020/12/18 4:04, Michael S. Tsirkin wrote:
>>> On Thu, Dec 17, 2020 at 09:29:26PM +0800, Jiahui Cen wrote:
There may be some differences in pci resou
Patchew URL:
https://patchew.org/QEMU/20201221005318.11866-1-jiaxun.y...@flygoat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20201221005318.11866-1-jiaxun.y...@flygoat.com
Subject: [PATCH 0/9] Alpine Linux buil
We only run build test and check-acceptance as their are too many
failures in checks due to minor string mismatch.
Signed-off-by: Jiaxun Yang
---
.gitlab-ci.d/containers.yml | 5 +
.gitlab-ci.yml | 23 +++
2 files changed, 28 insertions(+)
diff --git a/.git
As per POSIX specification of limits.h [1], OS libc may define
PAGE_SIZE in limits.h.
To prevent collosion of definition, we discard PAGE_SIZE from
defined by libc and take QEMU's variable.
[1]: https://pubs.opengroup.org/onlinepubs/7908799/xsh/limits.h.html
Signed-off-by: Jiaxun Yang
---
acce
As per POSIX specification of limits.h [1], OS libc may define
PAGE_SIZE in limits.h.
To prevent collosion of definition, we rename PAGE_SIZE here.
[1]: https://pubs.opengroup.org/onlinepubs/7908799/xsh/limits.h.html
Signed-off-by: Jiaxun Yang
---
contrib/elf2dmp/addrspace.c | 4 ++--
contrib
As per POSIX specification of limits.h [1], OS libc may define
PAGE_SIZE in limits.h.
Self defined PAGE_SIZE is frequently used in tests, to prevent
collosion of definition, we give PAGE_SIZE definitons reasonable
prefixs.
[1]: https://pubs.opengroup.org/onlinepubs/7908799/xsh/limits.h.html
Sign
Musl libc complains about it's wrong usage.
In file included from ../subprojects/libvhost-user/libvhost-user.h:20,
from ../subprojects/libvhost-user/libvhost-user-glib.h:19,
from ../subprojects/libvhost-user/libvhost-user-glib.c:15:
/usr/include/sys/poll.h:1:2: er
It is not a part of standard time.h. Glibc put it under
time.h however musl treat it as a sys timex extension.
Signed-off-by: Jiaxun Yang
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index c228f7c21e..990f37e123 100755
--- a/configure
+++ b/configure
@@
As per POSIX specification of limits.h [1], OS libc may define
PAGE_SIZE in limits.h.
To prevent collosion of definition, we rename PAGE_SIZE here.
[1]: https://pubs.opengroup.org/onlinepubs/7908799/xsh/limits.h.html
Signed-off-by: Jiaxun Yang
---
hw/block/nand.c | 40 -
signal.h is equlevant of sys/signal.h on Linux, musl would complain
wrong usage of sys/signal.h.
In file included from /builds/FlyGoat/qemu/include/qemu/osdep.h:108,
from ../tests/qemu-iotests/socket_scm_helper.c:13:
/usr/include/sys/signal.h:1:2: error: #warning redirecting incor
Alpine Linux[1] is a security-oriented, lightweight Linux distribution
based on musl libc and busybox.
It it popular among Docker guests and embedded applications.
Adding it to test against different libc.
[1]: https://alpinelinux.org/
Signed-off-by: Jiaxun Yang
---
tests/docker/dockerfiles/a
Alpine Linux[1] is a security-oriented, lightweight Linux distribution
based on musl libc and busybox.
It it popular among Docker guests and embedded applications.
Adding it to test against different libc.
[1]: https://alpinelinux.org/
Tree avilable at: https://gitlab.com/FlyGoat/qemu/-/tree/al
I'm afraid it didn't. Jack version is:
* media-sound/jack2
Latest version available: 1.9.16
Latest version installed: 1.9.16
Size of files: 952 KiB
Homepage: https://jackaudio.org/
Description: Jackdmp jack implemention for multi-processor machine
Licens
Hi.
mkfs.ext4 on nbd device cause:
Discarding device blocks: failed - Input/output error
message.
The actions:
~# qemu-img create -f raw test.img 10G
Formatting 'test.img', fmt=raw size=10737418240
~# qemu-nbd -f raw -c /dev/nbd0 test.img
~# fdisk /dev/nbd0
...[PARTITION A DISK]...
~# fdisk -l
Does this patch make a difference for you?
https://github.com/qemu/qemu/commit/a6e037390dd91276f4a631d41188c87e8a60bb3f
If not, what's the precise JACK version you are using.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bu
Public bug reported:
Hi,
I'm testing the new jack audiodev backend in my
laptop. The host system is gentoo, using the
ebuild for qemu 5.1.0-r2, and I'm using jack
use flag globally in the system so any ebuild
that have support for jack should be build with
it. The jack setup reportedly works as I
In the kernel, virtio_gpu_init() uses virtio_get_shm_region()
since
commit 6076a9711dc5 ("drm/virtio: implement blob resources: probe for host
visible region")
but vm_get_shm_region() unconditionally uses VIRTIO_MMIO_SHM_SEL to
get the address and the length of the region.
commit 38e895487afc ("v
Oh, and I guess I misinterpreted what -mpx was for. To be clear, I was
running into 2 issues:
1. Hyper-V fails to initialize.
"Fixed" by one of:
a) using named cpu model
b) cpu=host and running `bcdedit /set xsavedisable 1` in Windows before
enabling Hyper-V
c) cpu=host,-mpx
It's more likely to be a bug in KVM.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in QEMU:
New
Status in qemu-kvm p
I haven't tried 5.9, just:
- 5.4.0-58 Works
- 5.8.0-33 (20.04 HWE Edge)Bootloop
- 5.10.1-051001Works
If I have time later I can try narrowing down which kernel causes the
issue.
But is the BNDCFGS MSR issue considered a bug in qemu or what?
--
You receive
If you can bisect between 5.9 (I understand it's bad?) and 5.10 we could
propose it for stable kernels.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu hos
Adding -mpx doesn't seem to help on 5.8, the guest still bootloops.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in Q
Aha! The final boot loop issue is resolved if I either upgrade to 5.10
or downgrade to 5.4 from 5.8.
So the main issue then seems to be the missing control bits.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.
Try instead disabling MPX with "-cpu host,-mpx".
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1908489
Title:
qemu 4.2 bootloops with -cpu host and nested hypervisor
Status in QEMU:
New
Status i
** Bug watch added: bugs.centos.org/ #17788
https://bugs.centos.org/view.php?id=17788
** Also affects: qemu-kvm (CentOS) via
https://bugs.centos.org/view.php?id=17788
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of qemu-
devel
Signed-off-by: Laurent Vivier
---
include/hw/misc/m68k_virt_ctrl.h | 22 +
hw/misc/m68k_virt_ctrl.c | 152 +++
hw/misc/Kconfig | 3 +
hw/misc/meson.build | 3 +
hw/misc/trace-events | 7 ++
5 files changed, 1
Signed-off-by: Laurent Vivier
---
include/hw/char/goldfish_tty.h | 36 +
hw/char/goldfish_tty.c | 266 +
hw/char/Kconfig| 3 +
hw/char/meson.build| 2 +
hw/char/trace-events | 9 ++
5 files changed, 316 inser
Signed-off-by: Laurent Vivier
---
include/hw/intc/goldfish_pic.h | 33 +
hw/intc/goldfish_pic.c | 214 +
hw/intc/Kconfig| 3 +
hw/intc/meson.build| 1 +
hw/intc/trace-events | 8 ++
5 files changed, 259 inser
The machine is based on Goldfish interfaces defined by Google
for Android simulator. It uses Goldfish-rtc (timer and RTC),
Goldfish-pic (PIC) and Goldfish-tty (for serial port and early tty).
The machine is created with 128 virtio-mmio bus, and they can
be used to use serial console, GPU, disk, NI
After a migration the clock offset is updated, but we also
need to re-arm the alarm if needed.
Signed-off-by: Laurent Vivier
Reviewed-by: Alistair Francis
---
hw/rtc/goldfish_rtc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/rtc/goldfish_rtc.c b/hw/rtc/goldfish_rtc.c
index 0f4e8185
The Quadra 800 machine is very limited to run linux, it manages
only 1 GiB of memory and only some specific interfaces.
The Virtual M68k Machine is based on Goldfish interfaces defined by Google
for Android simulator. It uses Goldfish-rtc (timer and RTC),
Goldfish-pic (PIC) and Goldfish-tty (for s
Signed-off-by: Laurent Vivier
---
include/hw/intc/m68k_irqc.h | 28 +
hw/intc/m68k_irqc.c | 120
hw/intc/Kconfig | 3 +
hw/intc/meson.build | 1 +
4 files changed, 152 insertions(+)
create mode 100644 include/hw/intc/m
Copy bootinfo.h and bootinfo-mac.h from arch/m68k/include/uapi/asm/
to include/standard-headers/asm-m68k/
Imported from linux v5.9 but didn't change since v4.14 (header update)
and since v4.10 (content update).
Signed-off-by: Laurent Vivier
---
hw/m68k/bootinfo.h| 5
Ok, so I narrowed done one possible issue: the BNDCFGS bits in the vm
entry/exit control MSRs are not set but HyperV expects them to be set if
xsave is supported. This quick patch actually lets Hyper-V initialize
and continue booting:
https://gist.github.com/552baa8be026e67bef2d223076b81636
An alt
On 18/12/20 23:32, Eduardo Habkost wrote:
Who owns the FlatView reference, exactly?
The AddressSpace. The device creates the AddressSpace, which holds a
reference to the MemoryRegion through FlatView and AddressSpaceDispatch,
which holds a reference to the device.
By destroying the address
On 19/12/20 22:30, Laurent Vivier wrote:
Then:
diff --git a/softmmu/vl.c b/softmmu/vl.c
index 0ed5c5ba9348..2f198e0023e0 100644
--- a/softmmu/vl.c
+++ b/softmmu/vl.c
@@ -2525,6 +2525,7 @@ void qmp_x_exit_preconfig(Error **errp)
qemu_init_board();
qemu_create_cli_devices();
+qemu
42 matches
Mail list logo
