diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/118/peripherals/1801 | 81 | ||||
| -rw-r--r-- | results/classifier/118/peripherals/1801674 | 112 |
2 files changed, 193 insertions, 0 deletions
diff --git a/results/classifier/118/peripherals/1801 b/results/classifier/118/peripherals/1801 new file mode 100644 index 00000000..994ca8d0 --- /dev/null +++ b/results/classifier/118/peripherals/1801 @@ -0,0 +1,81 @@ +peripherals: 0.870 +mistranslation: 0.717 +hypervisor: 0.680 +TCG: 0.649 +performance: 0.636 +graphic: 0.628 +semantic: 0.613 +assembly: 0.611 +permissions: 0.605 +debug: 0.587 +device: 0.586 +ppc: 0.576 +register: 0.573 +architecture: 0.569 +user-level: 0.558 +socket: 0.539 +PID: 0.537 +arm: 0.528 +vnc: 0.525 +virtual: 0.507 +x86: 0.493 +kernel: 0.490 +VMM: 0.466 +boot: 0.451 +network: 0.447 +risc-v: 0.432 +files: 0.430 +KVM: 0.429 +i386: 0.352 + +qemu-system-arm: Linux doesn't boot with UEFI (hangs after printing `EFI stub: Exiting boot services... `.) +Description of problem: +Ubuntu 23.04 (armhf) doesn't boot with UEFI. +It hangs after printing `EFI stub: Exiting boot services... `. +Steps to reproduce: +```console +$ qemu-system-arm -machine virt -m 2048 -nographic -bios /usr/local/share/qemu/edk2-arm-code.fd -hda ubuntu-23.04-server-cloudimg-armhf.img -snapshot +UEFI firmware (version edk2-stable202302-for-qemu built at 17:13:00 on Mar 15 2023) +Error: Image at 000BFD84000 start failed: Not Found +Error: Image at 000BFCEE000 start failed: Unsupported +Error: Image at 000BFC85000 start failed: Not Found +Tpm2SubmitCommand - Tcg2 - Not Found +Tpm2GetCapabilityPcrs fail! +Tpm2SubmitCommand - Tcg2 - Not Found +BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x2,0x0) +BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x2,0x0) +EFI stub: Booting Linux Kernel... +EFI stub: Entering in SVC mode with MMU enabled +EFI stub: Using DTB from configuration table +EFI stub: Exiting boot services... +``` +Additional information: +It still boots when vmlinuz and initrd are directly specified: +```console +$ qemu-system-arm -machine virt -m 2048 -nographic -bios /usr/local/share/qemu/edk2-arm-code.fd -hda ubuntu-23.04-server-cloudimg-armhf.img -snapshot -kernel ubuntu-23.04-server-cloudimg-armhf-vmlinuz-lpae -initrd ubuntu-23.04-server-cloudimg-armhf-initrd-generic-lpae -append "root=LABEL=cloudimg-rootfs ro" +UEFI firmware (version edk2-stable202302-for-qemu built at 17:13:00 on Mar 15 2023) +Error: Image at 000BFD84000 start failed: Not Found +Error: Image at 000BFCEE000 start failed: Unsupported +Tpm2SubmitCommand - Tcg2 - Not Found +Tpm2GetCapabilityPcrs fail! +Tpm2SubmitCommand - Tcg2 - Not Found +EFI stub: Booting Linux Kernel... +EFI stub: Entering in SVC mode with MMU enabled +EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path +EFI stub: Using DTB from configuration table +EFI stub: Exiting boot services... +[ 0.000000] Booting Linux on physical CPU 0x0 +[ 0.000000] Linux version 6.2.0-26-generic-lpae (buildd@bos02-arm64-018) (arm-linux-gnueabihf-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU + Binutils for Ubuntu) 2.40) #26-Ubuntu SMP Tue Jul 11 10:32:58 UTC 2023 (Ubuntu 6.2.0-26.26-generic-lpae 6.2.13) +[ 0.000000] CPU: ARMv7 Processor [414fc0f0] revision 0 (ARMv7), cr=30c5387d +... +Ubuntu 23.04 ubuntu ttyAMA0 + +ubuntu login: +``` + + +Files: +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/ubuntu-23.04-server-cloudimg-armhf.img +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/unpacked/ubuntu-23.04-server-cloudimg-armhf-vmlinuz-lpae +- https://cloud-images.ubuntu.com/releases/23.04/release-20230729/unpacked/ubuntu-23.04-server-cloudimg-armhf-initrd-generic-lpae diff --git a/results/classifier/118/peripherals/1801674 b/results/classifier/118/peripherals/1801674 new file mode 100644 index 00000000..b096ddc2 --- /dev/null +++ b/results/classifier/118/peripherals/1801674 @@ -0,0 +1,112 @@ +peripherals: 0.892 +permissions: 0.869 +architecture: 0.864 +kernel: 0.846 +ppc: 0.845 +KVM: 0.841 +debug: 0.835 +hypervisor: 0.823 +risc-v: 0.819 +PID: 0.813 +register: 0.810 +semantic: 0.802 +user-level: 0.794 +network: 0.792 +files: 0.791 +virtual: 0.790 +device: 0.790 +performance: 0.783 +arm: 0.775 +TCG: 0.775 +vnc: 0.766 +socket: 0.758 +assembly: 0.757 +graphic: 0.754 +boot: 0.751 +VMM: 0.736 +x86: 0.720 +i386: 0.714 +mistranslation: 0.686 + +Ubuntu16.04 LTS - PCI Pass Through in Ubuntu KVM 16.04.x must use QEMU with DDW support from PPA (Documentation) + +== Comment: #0 - Siraj M. Ismail <email address hidden> - 2016-10-05 11:35:38 == +---Problem Description--- + +Customer running PCI pass through with 16.04.1 KVM and with the stock QEMU packages will hit a DI if they do not update to the QEMU packages with DDW support. The packages are in PPA for customers to download, and test has verified the fix. The details are in Bugzilla 144123. + +---uname output--- +Ubuntu 16.04.1 with 4.4.0 Kernel + +Machine Type = 8247-22L + +---Debugger--- +A debugger is not configured + +---Steps to Reproduce--- + Run guest with adapters assigned via PCI PT, The guest will start having DI issues as soon as I/O started on the Pass Through adapter. + +Contact Information = <email address hidden> + +---Patches Installed--- +QEMU was updated from 2.5 version to 2.6.1 with patches for DDW support, can be found at PPA location : +https://launchpad.net/~ibmpackages/+archive/ubuntu/ddw + +Userspace tool common name: QEMU + +Documentation version: N/A + +The userspace tool has the following bit modes: N/A + +Userspace rpm: N/A + +Userspace tool obtained from project website: na + +*Additional Instructions for <email address hidden>: +-Post a private note with access information to the machine that the bug is occuring on. +-Attach ltrace and strace of userspace application. + +== Comment: #5 - Leonardo Augusto Guimaraes Garcia <email address hidden> - 2017-04-25 16:23:57 == +I would rephrase to: + +------------------------------- + +Under KVM recommendations + +PCI passthrough recommendations + +If you are running PCI passthrough with 16.04.x KVM and with the stock QEMU package, update to the QEMU package that have DDW support. If you do not update the package, you will hit data integrity issues as soon as I/O is started on the adapter. + +The package is available at: https://launchpad.net/~ibmpackages/+archive/ubuntu/ddw + +------------------------------- + +Some time ago DDW was discussed in this ticket: +https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1541902 +And it got introduced in Yakkety and higher only. +Due to pretty complex changes and changes in the virtual machine attributes there is no plan to get it into xenial. +Also 'bugproxy' changed "targetmilestone-inin16041" to "targetmilestone-inin1610". +We are wondering why this now came up again? + +------- Comment From <email address hidden> 2018-11-05 05:57 EDT------- +(In reply to comment #14) +> Some time ago DDW was discussed in this ticket: +> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1541902 +> And it got introduced in Yakkety and higher only. +> Due to pretty complex changes and changes in the virtual machine attributes +> there is no plan to get it into xenial. +> Also 'bugproxy' changed "targetmilestone-inin16041" to +> "targetmilestone-inin1610". +> We are wondering why this now came up again? + +This bug was lying in LTC bugzilla since a while and i happen to +mirror it today after the previous QA left IBM. Its a documentation +bug for 16.04.x + +Okay, added it to: +- uKVM + https://wiki.ubuntu.com/ppc64el/uKVM#PCI_pass-through_with_QEMU-KVM_on_Ubuntu_16.04_using_kernel_4.4 +- and to the Release Notes: + https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#PCI_pass-through_with_QEMU-KVM +Closing ticket. + |