diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/boot/192 | 2 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1921280 | 8 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1921468 | 47 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1923497 | 28 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1925417 | 69 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1926052 | 16 |
6 files changed, 170 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/boot/192 b/results/classifier/gemma3:12b/boot/192 new file mode 100644 index 000000000..498af7490 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/192 @@ -0,0 +1,2 @@ + +xv6 Bootloop diff --git a/results/classifier/gemma3:12b/boot/1921280 b/results/classifier/gemma3:12b/boot/1921280 new file mode 100644 index 000000000..7780f5b42 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1921280 @@ -0,0 +1,8 @@ + +OpenIndiana stuck in boot loop when using hvf + +I'm using QEMU version 5.2.0 on macOS, and running the "OpenIndiana Hipster 2020.10 Text Install DVD (64-bit x86)" ISO: + +qemu-system-x86_64 -cdrom ~/Downloads/OI-hipster-text-20201031.iso -m 2048 -accel hvf -cpu host + +It gets to "Booting...", stays there for a bit, and then restarts. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/boot/1921468 b/results/classifier/gemma3:12b/boot/1921468 new file mode 100644 index 000000000..a7dad8fbc --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1921468 @@ -0,0 +1,47 @@ + +[UBUNTU 20.04] KVM guest fails to find zipl boot menu index + +---Problem Description--- +A KVM guest fails to find the zipl boot menu index if the "zIPL" magic value is listed at the end of a disk block. + +---System Hang--- +System sits in disabled wait, last console display +LOADPARM=[ ] +Using virtio-blk. +Using ECKD scheme (block size 4096), CDL +VOLSER=[0X0067] + + +---Steps to Reproduce--- +1. Install Distro KVM guest from ISO on a DASD, e.g. using virt-install, my invocation was +$ virt-install --name secguest2 --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.af6a --cdrom /var/lib/libvirt/images/xxxxxx.iso + +2. Select DHCP networking and ASCII console, and accept all defaults of the installer + +3. Let the installer reboot after the installation completes + +It is possible to recover by editing the domain XML with an explicit loadparm to select a boot menu entry. E.g. I changed the disk definition to + <disk type='block' device='disk'> + <driver name='qemu' type='raw' cache='none' io='native'/> + <source dev='/dev/disk/by-path/ccw-0.0.af6a'/> + <target dev='vda' bus='virtio'/> + <boot order='1' loadparm='1'/> + <address type='ccw' cssid='0xfe' ssid='0x0' devno='0xaf6a'/> + </disk> + +The patches are now upstream: +5f97ba0c74cc ("pc-bios/s390-ccw: fix off-by-one error") +468184ec9024 ("pc-bios/s390-ccw: break loop if a null block number is reached") + +Current versions of qemu within Ubuntu + +focal (20.04LTS) 1:4.2-3ubuntu6 [ports]: arm64 armhf ppc64el s390x +focal-updates (metapackages): 1:4.2-3ubuntu6.14: amd64 arm64 armhf ppc64el s390x + +groovy (20.10) (metapackages): 1:5.0-5ubuntu9 [ports]: arm64 armhf ppc64el s390x +groovy-updates (metapackages): 1:5.0-5ubuntu9.6: amd64 arm64 armhf ppc64el s390x + +hirsute (metapackages): 1:5.2+dfsg-9ubuntu1: amd64 arm64 armhf ppc64el s390x + + +git-commits will apply seamlessley for the requested levels if not already integrated \ No newline at end of file diff --git a/results/classifier/gemma3:12b/boot/1923497 b/results/classifier/gemma3:12b/boot/1923497 new file mode 100644 index 000000000..4f427def1 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1923497 @@ -0,0 +1,28 @@ + +bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed + +Trying boot/start a Windows 10 VM. Worked until recently when this error started showing up. + +I have the following installed on Fedora 33: +qemu-kvm-5.1.0-9.fc33.x86_64 + +This is the error: + +Error starting domain: internal error: process exited while connecting to monitor: qemu-system-x86_64: /builddir/build/BUILD/qemu-5.1.0/hw/acpi/bios-linker-loader.c:239: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed. + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup + self._backend.create() + File "/usr/lib64/python3.9/site-packages/libvirt.py", line 1234, in create + if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) +libvirt.libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: /builddir/build/BUILD/qemu-5.1.0/hw/acpi/bios-linker-loader.c:239: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed. + +I see this were referenced in a patch from some time ago and supposedly fixed. Here is the patch info I was able to find: + +http://next.<email address hidden><email address hidden>/ \ No newline at end of file diff --git a/results/classifier/gemma3:12b/boot/1925417 b/results/classifier/gemma3:12b/boot/1925417 new file mode 100644 index 000000000..ee2410b2c --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1925417 @@ -0,0 +1,69 @@ + +Cannot boot from EFI image on aarch64 + +I am unable to boot from a EFI disk image on aarch64 qemu. + +I have qemu built and installed from sources on a jetson-nano + +qemu-system-aarch64 -version +QEMU emulator version 5.2.50 (v5.2.0-3234-gbdee969c0e) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers + +KVM and and virtio are enabled in host kernel. + +Now I want to boot a ChromiumOS image. I have the image downloaded from here: + +https://chromium.arnoldthebat.co.uk/?dir=daily + +The image looks fine: + +rreddy78@jetson-nano:~/Downloads$ fdisk -lu chromiumos_image.bin +Disk chromiumos_image.bin: 6.2 GiB, 6606109184 bytes, 12902557 sectors +Units: sectors of 1 * 512 = 512 bytes +Sector size (logical/physical): 512 bytes / 512 bytes +I/O size (minimum/optimal): 512 bytes / 512 bytes +Disklabel type: gpt +Disk identifier: C5B6CA94-0AF1-374E-90B5-A5CF4DC1FF51 + +Device Start End Sectors Size Type +chromiumos_image.bin1 4513792 12902508 8388717 4G Linux filesystem +chromiumos_image.bin2 20480 53247 32768 16M ChromeOS kernel +chromiumos_image.bin3 319488 4513791 4194304 2G ChromeOS root fs +chromiumos_image.bin4 53248 86015 32768 16M ChromeOS kernel +chromiumos_image.bin5 315392 319487 4096 2M ChromeOS root fs +chromiumos_image.bin6 16448 16448 1 512B ChromeOS kernel +chromiumos_image.bin7 16449 16449 1 512B ChromeOS root fs +chromiumos_image.bin8 86016 118783 32768 16M Linux filesystem +chromiumos_image.bin9 16450 16450 1 512B ChromeOS reserved +chromiumos_image.bin10 16451 16451 1 512B ChromeOS reserved +chromiumos_image.bin11 64 16447 16384 8M unknown +chromiumos_image.bin12 249856 315391 65536 32M EFI System + +Partition table entries are not in disk order. + +Now I try booting like this: + +qemu-system-aarch64 -M virt -m 2048 -smp 2 -cpu host -enable-kvm \ +-device usb-ehci -device usb-kbd -device usb-mouse -usb -serial stdio \ +-device virtio-gpu-pci,virgl=on,xres=1600,yres=900 -display sdl,gl=on \ +-device virtio-blk-device,drive=hd \ +-drive if=none,file=chromiumos_image.bin,format=raw,id=hd \ +-netdev user,id=mynet \ +-device virtio-net-device,netdev=mynet \ +-bios edk2-aarch64-code.fd -no-reboot + +But I am unable to boot. + +Memory Type Information settings change. +[Bds]Booting UEFI Misc Device + BlockSize : 262144 + LastBlock : FF +[Bds] Expand VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00) -> <null string> +BdsDxe: failed to load Boot0001 "UEFI Misc Device" from VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00): Not Found + + +and + + +[Bds] Expand VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000) -> <null string> +BdsDxe: failed to load Boot0002 "UEFI Misc Device 2" from VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000): Not Found \ No newline at end of file diff --git a/results/classifier/gemma3:12b/boot/1926052 b/results/classifier/gemma3:12b/boot/1926052 new file mode 100644 index 000000000..203b38b98 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1926052 @@ -0,0 +1,16 @@ + +qemu freezes during grub on arch cloudimg + +When booting the Arch Linux cloud image and setting `-nographic`, qemu will freeze during the grub bootloader. +Tested with qemu 5.1 and 5.2. + +Reproduce: +``` +wget https://gitlab.archlinux.org/archlinux/arch-boxes/-/jobs/20342/artifacts/raw/output/Arch-Linux-x86_64-basic-20210420.20342.qcow2 + +qemu-system-x86_64 -hda Arch-Linux-x86_64-basic-20210420.20342.qcow2 -nographic + +``` + +It will get stuck while displaying `Welcome to GRUB!` +If -nographic is omitted, it will continue to boot (without any keyboard interaction) \ No newline at end of file |