diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1633 | 83 | ||||
| -rw-r--r-- | results/classifier/108/other/1633508 | 65 |
2 files changed, 148 insertions, 0 deletions
diff --git a/results/classifier/108/other/1633 b/results/classifier/108/other/1633 new file mode 100644 index 000000000..496c9772c --- /dev/null +++ b/results/classifier/108/other/1633 @@ -0,0 +1,83 @@ +other: 0.780 +device: 0.745 +graphic: 0.724 +permissions: 0.705 +semantic: 0.701 +boot: 0.699 +performance: 0.689 +PID: 0.689 +debug: 0.660 +vnc: 0.645 +KVM: 0.644 +socket: 0.603 +network: 0.599 +files: 0.551 + +[8.0.0] Broken icount support on RISC-V +Description of problem: +After https://gitlab.com/qemu-project/qemu/-/commit/5a4ae64cac49564354cd6f17598840e4af70e4f5 was merged, RISC-V VMs no longer run with -icount 1 specified in the QEMU arguments. Reverting this commit resolves the issue. +Steps to reproduce: +1. Download preinstalled Ubuntu 22.04.2 image from [here](https://cdimage.ubuntu.com/releases/22.04.2/release/ubuntu-22.04.2-preinstalled-server-riscv64+unmatched.img.xz) +2. Download uboot from [here](http://security.ubuntu.com/ubuntu/pool/main/u/u-boot/u-boot-qemu_2022.01+dfsg-2ubuntu2.3_all.deb) +3. Extract both. +4. Run with the command-line specified above. +Additional information: +Reading Ubuntu wiki describing how to run RISC-V VMs can help: https://wiki.ubuntu.com/RISC-V/QEMU + +Full output: + +``` +% qemu-system-riscv64 \ +-machine virt -nographic -m 2048 -smp 4 \ +-kernel u-boot/qemu-riscv64_smode/uboot.elf \ +-device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ +-drive file=ubuntu-22.04.2-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio -icount 1 + +OpenSBI v1.2 + ____ _____ ____ _____ + / __ \ / ____| _ \_ _| + | | | |_ __ ___ _ __ | (___ | |_) || | + | | | | '_ \ / _ \ '_ \ \___ \| _ < | | + | |__| | |_) | __/ | | |____) | |_) || |_ + \____/| .__/ \___|_| |_|_____/|____/_____| + | | + |_| + +Platform Name : riscv-virtio,qemu +Platform Features : medeleg +Platform HART Count : 4 +Platform IPI Device : aclint-mswi +Platform Timer Device : aclint-mtimer @ 10000000Hz +Platform Console Device : uart8250 +Platform HSM Device : --- +Platform PMU Device : --- +Platform Reboot Device : sifive_test +Platform Shutdown Device : sifive_test +Firmware Base : 0x80000000 +Firmware Size : 236 KB +Runtime SBI Version : 1.0 + +Domain0 Name : root +Domain0 Boot HART : 0 +Domain0 HARTs : 0*,1*,2*,3* +Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I) +Domain0 Region01 : 0x0000000080000000-0x000000008003ffff () +Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X) +Domain0 Next Address : 0x0000000080200000 +Domain0 Next Arg1 : 0x00000000bfe00000 +Domain0 Next Mode : S-mode +Domain0 SysReset : yes + +Boot HART ID : 0 +Boot HART Domain : root +Boot HART Priv Version : v1.12 +Boot HART Base ISA : rv64imafdch +Boot HART ISA Extensions : time,sstc +Boot HART PMP Count : 16 +Boot HART PMP Granularity : 4 +Boot HART PMP Address Bits: 54 +Boot HART MHPM Count : 16 +Boot HART MIDELEG : 0x0000000000001666 +Boot HART MEDELEG : 0x0000000000f0b509 +qemu-system-riscv64: Bad icount read +``` diff --git a/results/classifier/108/other/1633508 b/results/classifier/108/other/1633508 new file mode 100644 index 000000000..65fb09951 --- /dev/null +++ b/results/classifier/108/other/1633508 @@ -0,0 +1,65 @@ +network: 0.849 +device: 0.837 +PID: 0.773 +performance: 0.759 +semantic: 0.752 +permissions: 0.710 +socket: 0.658 +other: 0.653 +graphic: 0.613 +debug: 0.613 +boot: 0.572 +files: 0.506 +vnc: 0.474 +KVM: 0.127 + +libvirt cannot hot insert interfaces to qemu + +When attempting to hot insert an interface using Ubuntu 16.04.1, I get the following +$ virsh attach-interface --domain gluster1 --type direct \ +> --source test0 --model virtio \ +> --mac 2a:b6:b0:dc:c7:c4 --config --live +error: Failed to attach interface +error: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS + +test0 exists: +$ ip link show test0 +35: test0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 + link/ether aa:8c:65:2e:79:61 brd ff:ff:ff:ff:ff:ff + +Just in case I did it wrong with direct, I did network +$ virsh net-list + Name State Autostart Persistent +---------------------------------------------------------- + default active yes yes + mgmtnet0 active yes yes + +$ virsh attach-interface --domain gluster1 --type network \ +> --source default --model virtio \ +> --mac 2a:b6:b0:dc:c7:c4 --config --live +error: Failed to attach interface +error: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS + + +This seems to be an old bug, but is still present. Other relevant information: +$ qemu-system-x86_64 --version +QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.5), Copyright (c) 2003-2008 Fabrice Bellard +$ virsh -v +1.3.1 + +This looks like a libvirt bug at a first glance. Have you tried to report it to the libvirt project? (See https://libvirt.org/bugs.html ) ... also, can you re-create the bug with the very latest upstream version of libvirt and qemu, or does it only occur with an (older?) version of Ubuntu? + +That seems to be the Libvirt of Ubuntu in Xenial. + +In the past similar issues were uncommon configs or changed behavior on updates that triggered apparmor or SELinux protection. + +=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1747442 +=> https://bugzilla.redhat.com/show_bug.cgi?id=731243 + +It could as well be some variant of bug 1677398. + +If you are still affected by this, could you check: +1. if it also happens on newer libvirt versions e.g. do a trial run in the most recent Ubuntu +2. if it does could you check dmesg in your setup for related apparmor denials? + + |