diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/kvm/772 | 13 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/kvm/772358 | 23 |
2 files changed, 36 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kvm/772 b/results/classifier/gemma3:12b/kvm/772 new file mode 100644 index 000000000..6847b45e1 --- /dev/null +++ b/results/classifier/gemma3:12b/kvm/772 @@ -0,0 +1,13 @@ + +Pop!_OS 20.10 host + RHEL 8.5 guest = Oh no! Something has gone wrong. +Description of problem: +Whenever starting the Qemu VM, there is an error covering the whole desktop "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." After clicking the "Log Out" button and waiting for hours, the guest RHEL may or may not recover, based on your luck and other qemu options used. +Steps to reproduce: +1. Build qemu using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek +``` +2. Install Red Hat Enterprise Linux 8.5 in qemu +3. Run qemu using the above command line. +Additional information: + diff --git a/results/classifier/gemma3:12b/kvm/772358 b/results/classifier/gemma3:12b/kvm/772358 new file mode 100644 index 000000000..d063d0ed1 --- /dev/null +++ b/results/classifier/gemma3:12b/kvm/772358 @@ -0,0 +1,23 @@ + +VNC working depends on command line options order + +OS: Ubuntu 10.04.2, amd64 +Pkg version: 0.12.3+noroms-0ubuntu9.5 + +if -nographic option is specified before -vnc, vnc works, if vice-versa, it does not. I have been told (thanks, mjt), that -nographic is supposed to disable any graphic output, including vnc, so possibly it's a documentation bug: + +- kvm man page talks about -nographic disabling SDL , not VNC. While it might be the same to you, it was not to me and my colleagues + +- if -vnc and -nographic are conflicting, perhaps kvm should error out or at least warn + +- monitor console's message on "change vnc 127.0.0.1:1" command: "Could not start server on 127.0.0.1:1" is not helpful either + +- order of the options should not matter + +Example: (VNC works) + +/usr/bin/kvm -name ubuntu.example.com -m 3076 -smp 2 -drive if=virtio,file=/dev/vg0/kvm-ubuntu,boot=on,media=disk,cache=none,index=0 -net nic,vlan=0,model=virtio,macaddr=00:03:03:03:03:01 -net tap,ifname=kvm_ubuntu,vlan=0,script=no,downscript=no -balloon virtio -nographic -daemonize -vnc 127.0.0.1:1 -pidfile /var/run/kvm/1 + +Example: (VNC does not work, also confuses terminal): + +/usr/bin/kvm -name ubuntu.example.com -m 3076 -smp 2 -drive if=virtio,file=/dev/vg0/kvm-ubuntu,boot=on,media=disk,cache=none,index=0 -net nic,vlan=0,model=virtio,macaddr=00:03:03:03:03:01 -net tap,ifname=kvm_ubuntu,vlan=0,script=no,downscript=no -balloon virtio -vnc 127.0.0.1:1 -nographic -daemonize -pidfile /var/run/kvm/1 \ No newline at end of file |