Bugzilla – Bug 1212225
No response for login KVM workload after run VM Guest in ALP
Last modified: 2024-04-19 08:13:05 UTC
Description of problem: No shown like login text when Running the KVM virtualization workload using Podman Version-Release number of selected component (if applicable): https://mirror.tspu.ru/opensuse/repositories/SUSE%3A/ALP%3A/Products%3A/Installer%3A/0.8/images/iso/d-installer-live.x86_64-ALP.iso Steps to Reproduce: 1.Follow steps under https://documentation.suse.com/alp/bedrock/html/alp-bedrock/available-alp-workloads.html#task-run-kvm-with-podman 2.Step 5.Run the GDM container,run a VM Guest on top of the started KVM VM Guest using the virt-install-demo.sh script Expected results: Can not login the VM Addition info: 1.# virt-manager using /etc/kvm-container.conf as configuration file + '[' '!' -d /tmp/container ']' + mkdir /tmp/container/ + cp -af /root/.Xauthority /tmp/container/.Xauthority cp: cannot stat '/root/.Xauthority': No such file or directory 2.
# virt-install-demo.sh + '[' -f /etc/kvm-container-functions ']' + . /etc/kvm-container-functions ++ '[' -z ']' ++ CONF=/etc/kvm-container.conf ++ '[' -z ']' ++ DEFAULT_CONF=/etc/default/kvm-container ++ echo 'using /etc/kvm-container.conf as configuration file' using /etc/kvm-container.conf as configuration file + check_load_config_file + '[' -f /etc/kvm-container.conf ']' + source /etc/kvm-container.conf ++ CONTAINER_NAME=libvirtd ++ IMAGE=registry.opensuse.org/suse/alp/workloads/tumbleweed_containerfiles/suse/alp/workloads/kvm:latest ++ DATA=/var/lib/libvirt/images ++ LIBVIRTDQEMU=/etc/libvirt/qemu ++ VARRUNLIBVIRT=/var/run/libvirt ++ APPLIANCE_MIRROR=https://download.opensuse.org/tumbleweed/appliances ++ APPLIANCE=openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen ++ BACKING_DIR=/var/lib/libvirt/images ++ BACKING_FORMAT=qcow2 ++ BACKING_STORE=/var/lib/libvirt/images/openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen.qcow2 ++ DOMAIN=Tumbleweed-JeOS ++ BRIDGEIF=virbr5 ++ DISKSIZE=1 ++ VMMEMORY=1024 ++ VCPU=1 + '[' -e /etc/default/kvm-container ']' + source /etc/default/kvm-container ++ IMAGE=registry.opensuse.org/suse/alp/workloads/tumbleweed_containerfiles/suse/alp/workloads/kvm:latest + '[' '!' -f /var/lib/libvirt/images/openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen.qcow2 ']' + pushd /var/lib/libvirt/images /var/lib/libvirt/images /home/test + curl -L -o /var/lib/libvirt/images/openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen.qcow2 https://download.opensuse.org/tumbleweed/appliances/openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen.qcow2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:06 --:--:-- 0 100 213M 100 213M 0 0 1291k 0 0:02:49 0:02:49 --:--:-- 2453k + popd /home/test ++ openssl rand -hex 5 + RANDOMSTRING=b231d1bfb2 + VMNAME=Tumbleweed-JeOS_b231d1bfb2 + create_vm + podman exec -ti libvirtd virt-install --connect qemu:///system --import --name Tumbleweed-JeOS_b231d1bfb2 --osinfo opensusetumbleweed --virt-type kvm --hvm --machine q35 --boot uefi --cpu host-passthrough --video vga --console pty,target_type=virtio --noautoconsole --network network=default --rng /dev/urandom --vcpu 1 --memory 1024 --cloud-init --disk size=1,backing_store=/var/lib/libvirt/images/openSUSE-Tumbleweed-Minimal-VM.x86_64-kvm-and-xen.qcow2,backing_format=qcow2,bus=virtio,cache=none --graphics vnc,listen=0.0.0.0 WARNING Defaulting to --cloud-init root-password-generate=yes,disable=yes Starting install... Password for first root login is: 4hpTtCkwqneooOAH Allocating 'Tumbleweed-JeOS_b231d1bfb2.qcow2' | 0 B 00:00:00 ... Creating domain... | 0 B 00:00:00 Domain creation completed. + cat To connect to the VM in console mode: virsh console Tumbleweed-JeOS_b231d1bfb2 To detach from the console: crtl + ] # virsh console using /etc/kvm-container.conf as configuration file + podman exec -ti libvirtd virsh console error: command 'console' requires <domain> option localhost:/home/test # virsh console Tumbleweed-JeOS_b231d1bfb2 using /etc/kvm-container.conf as configuration file + podman exec -ti libvirtd virsh console Tumbleweed-JeOS_b231d1bfb2 Authorization not available. Check if polkit service is running or see debug message for more information. Connected to domain 'Tumbleweed-JeOS_b231d1bfb2' Escape character is ^] (Ctrl + ])
Virt-manager has been dropped as we no longer ship any X GUI inside the kvm container anymore. There is ongoing work to split Libvirt client and server into different containers.
Actually,I have two questions: First, in The SUSE ALP Bedrock Guide of ALP, It tells me "Run the GDM container,run a VM Guest on top of the started KVM VM Guest using the virt-install-demo.sh script", but after run 'virt-install-demo.sh', it exits automatically and does not show 'localhost login:'.So I can not access VM Guest.This comment1 shows this situation. Second, in ALP,I do not know how to install VM Guest manually with specify OS like SLES15SP5 or others. Could you share with me that?
(In reply to su jiajia from comment #3) > Actually,I have two questions: > First, in The SUSE ALP Bedrock Guide of ALP, It tells me "Run the GDM > container,run a VM Guest on top of the started KVM VM Guest using the > virt-install-demo.sh script", but after run 'virt-install-demo.sh', it exits > automatically and does not show 'localhost login:'.So I can not access VM > Guest.This comment1 shows this situation. virt-install-demos.sh is given as an example script. You don't need to use the GDM container to install a VM or use the virt-install-demo.sh. > Second, in ALP,I do not know how to install VM Guest manually with specify > OS like SLES15SP5 or others. Could you share with me that? Its like any other SLE, virt-install is available and could be used to install any kind of guest.
Thanks for your pateint and information. I have no questions about this defect now.
Hi, localhost:~ # virt-install --connect=qemu:///system -n alpvm_1 -r 9632 --arch=x86_64 --vcpus=4 -c /root/ALP-Dolomite.x86_64-1.0-Default-SelfInstall-Milestone7.install.iso --disk size=10 --osinfo detect=on,name=sle15-unknown ERROR Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory localhost:~ # When I use above command to install a VM, it will throw this error.Could you tell me what virtualization components should be installed in order to create and start VM on ALP host server
(In reply to su jiajia from comment #6) > Hi, > > localhost:~ # virt-install --connect=qemu:///system -n alpvm_1 -r 9632 > --arch=x86_64 --vcpus=4 -c > /root/ALP-Dolomite.x86_64-1.0-Default-SelfInstall-Milestone7.install.iso > --disk size=10 --osinfo detect=on,name=sle15-unknown > ERROR Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No > such file or directory > localhost:~ # > > When I use above command to install a VM, it will throw this error.Could you > tell me what virtualization components should be installed in order to > create and start VM on ALP host server You need to have the libvirt-daemon-qemu package installed and the virtqemud service enabled/started (e.g. 'systemctl start virtqemud.service').
Created attachment 871580 [details] rpm -qa Hi, It shows virtqemud.service not found localhost:~ # rpm -qa|grep -i libvirt-daemon-qemu libvirt-daemon-qemu-9.9.0-1.1.x86_64 localhost:~ # systemctl start virtqemud.service Failed to start virtqemud.service: Unit virtqemud.service not found. localhost:~ # rpm -qa > rpm_-qa
(In reply to su jiajia from comment #8) > Created attachment 871580 [details] > rpm -qa > > Hi, > It shows virtqemud.service not found > > localhost:~ # rpm -qa|grep -i libvirt-daemon-qemu > libvirt-daemon-qemu-9.9.0-1.1.x86_64 > localhost:~ # systemctl start virtqemud.service > Failed to start virtqemud.service: Unit virtqemud.service not found. > localhost:~ # rpm -qa > rpm_-qa How about the libvirt-daemon-driver-qemu package? (The attached file "rpm -qa" shows your host doesn't have it installed) On my host: host:~ # rpm -ql libvirt-daemon-driver-qemu | grep virtqemud.service /usr/lib/systemd/system/virtqemud.service Could you please install it and try starting virtqemud.service again?
localhost:~ # transactional-update pkg in libvirt-daemon-driver-qemu ... 2023-12-28 09:32:18 Executing `zypper -R /tmp/transactional-update-83sEol install libvirt-daemon-driver-qemu`: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: This request will break your system! the to be installed libvirt-daemon-driver-qemu-9.9.0-1.1.x86_64 requires '/usr/bin/lzop', but this requirement cannot be provided not installable providers: busybox-misc-1.36.1-2.25.noarch[ALP-Dolomite-1.0] Solution 1: Following actions will be done: ignore the warning of a broken system (requires:transactional-update) deinstallation of lsof-4.98.0-3.6.x86_64 deinstallation of e2fsprogs-1.46.5-2.8.x86_64 deinstallation of dosfstools-4.2-2.5.x86_64 deinstallation of patterns-alp-base-5.0-11.3.x86_64 deinstallation of transactional-update-4.4.0-1.5.x86_64 deinstallation of dracut-kiwi-lib-9.25.12-1.7.x86_64 deinstallation of patterns-alp-base-zypper-5.0-11.3.x86_64 deinstallation of patterns-alp-defaults-5.0-11.3.x86_64 deinstallation of transactional-update-zypp-config-4.4.0-1.5.noarch deinstallation of dracut-kiwi-oem-dump-9.25.12-1.7.x86_64 deinstallation of dracut-kiwi-oem-repart-9.25.12-1.7.x86_64 Solution 2: do not install libvirt-daemon-driver-qemu-9.9.0-1.1.x86_64 Solution 3: break libvirt-daemon-driver-qemu-9.9.0-1.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
libvirt-daemon-qemu requires libvirt-daemon-driver-qemu, so I'm not sure how your system got in a state where the former is installed but not the latter.
Closing. Please rerun the test on SLES 16 once it's available.