:15 PM Pry Mar wrote:
> Similar trouble in domU, independent of the dom0 kernel:
>
> [0.605954] UBSAN: array-index-out-of-bounds in
> /build/linux-D15vQj/linux-6.5.0/drivers/block/xen-blkfront.c:1544:3
> [0.605962] index 1 is out of range for type 'blkif_sring_entry [1]'
0-9-generic
#9-Ubuntu
domU is giving far more trace output.
On Mon, Nov 6, 2023 at 11:20 AM Pry Mar wrote:
> Hello,
>
> These 2 errors show in dmesg late in boot process when xen domU launch:
> 1) blkback
> UBSAN: array-index-out-of-bounds in
> /build/linux-D15vQj/linux-6.5.0/
Hello,
These 2 errors show in dmesg late in boot process when xen domU launch:
1) blkback
UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/block/xen-blkback/blkback.c:1227:4
2) netback
[ 55.209063] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/d
Hello,
First attempt to build xen-4.18-unstabl in deb12 (Bookworm):
/home/mockbuild/pbdeps/xen-4.18~rc0/debian/build/build-utils_amd64/tools/firmware/hvmloader/dsdt_anycpu.asl
9851: Name ( SLT, 0x0 )
Remark 2173 - Creation of named objects within a method is
highly ineffic
>Unexpectedly the environment variable which needs to be passed is
>$LDSHARED and not $LD. Otherwise Python may find the build `ld` instead
>of the host `ld`.
>
>Replace $(LDFLAGS) with $(SHLIB_LDFLAGS) as Python needs shared objects
>it can load at runtime, not executables.
>
>This uses $(CC) ins
Hello Ayush Dosaj,
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1851091
see the bug report above ^.
As soon as Ubuntu 19.10 went to LZ4 kernel compression this bug
appeared. As Stefan Bader reports in his testing, the hypervisor not
only crashes, but resets the machine.
The same trouble c
kevin,
http://prymar56.org/xen/debian/buster-nmu/4cx/source/xen_4.12.2-1+deb10u1.2.debian.tar.xz
debian/patches/misc-0111-tools-xenmon-make-xenmon.py-compatible-with-python-2-.diff
debian/patches/misc-0112-xenmon-fix-mixed-tabs-and-spaces.diff
debian/patches/misc-0113-tools-python-Python-3-compat
hello,
Referencing this report against kernel-5.3 and xen-4.9.2:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1851091
I see the same behavior with the hypervisor from xen-4.12.x and xen-4.13.0.
Using legacy bios, boot never starts and host resets.
Adding more:
If I copy into Focal /boot th
On 12/4/19, Jan Beulich wrote:
> On 04.12.2019 08:14, Jeremi Piotrowski wrote:
>> Any suggestions how to proceed?
>
> Actually here's a better version (I think).
>
> Jan
>
> lz4: refine commit 9143a6c55ef7 for the 64-bit case
>
> I clearly went too far there: While the LZ4_WILDCOPY() instances ind
Hello xen-devel,
https://paste.debian.net/plain/1109374
shows my traces from a healthy CentOS 8, xen-4.12.1 dom0 when trying
to launch a pv install of the newly released ub1910. The source is a
block-attached ISO and the kernel/ramdisk was copied off locally.
Iso is named, eoan-live-server-amd64
On 4/16/19, Roger Pau Monné wrote:
> On Mon, Apr 15, 2019 at 04:18:57PM -0700, Pry Mar wrote:
>> Hello,
>>
>> https://paste.debian.net/1077718/
>>
>> I get a kernel panic as shown in the paste above no matter how I
>> launch pvh, with bootloader (pygrub
Hello,
https://paste.debian.net/1077718/
I get a kernel panic as shown in the paste above no matter how I
launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
pvgrub2 (i386-xen_pvh support).
The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
packages (self built).
~$ sudo
qemu build config:
http://paste.debian.net/plain/1062777/
domU startup trace:
http://paste.debian.net/plain/1062768/
This release uses qemu-3.0.0 which has a depends on libxentoolcore.
In xen-4.11.1 with qemu-2.11.2 vfb objects (VNC) always worked in pv
domU. Only now with qemu-3.x is it failing
13 matches
Mail list logo
