View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006832 | Rocky-Linux-9 | General | public | 2024-05-23 16:42 | 2024-05-28 12:36 |
Reporter | Brad 2014 | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | x86_64 | OS | Rocky 9 | OS Version | 9.4 |
Summary | 0006832: Image Rocky-9-GenericCloud-Base-9.4-20240509.0.x86_64.qcow2 does not boot under qemu-kvm | ||||
Description | On a working x86_64 host running Rocky 9.4 (kernel 5.14.0-427.16.1.el9_4.x86_64), I am creating a qemu-kvm virtual machine. On a Rocky 9.4 host with qemu-kvm, libvirt, virt-manager and virt-install packages installed, the virtual machine starts cleanly with base=Rocky-9-GenericCloud-Base-9.3-20231113.0.x86_64.qcow2 and fails to start with base=Rocky-9-GenericCloud-Base-9.4-20240509.0.x86_64.qcow2 | ||||
Steps To Reproduce | To reproduce (see below for the content of ./test-user-data): # qemu-img create -b $base -f qcow2 -F qcow2 test.qcow2 # virt-install --import --os-variant=rocky9 --autostart --graphics none --autoconsole none "--name=test" "--ram=2048" "--vcpus=2" --network "type=default" --network "bridge=bridge,source=eno1,model=virtio,type=direct,trustGuestRxFilters=on" --disk "path=test.qcow2,format=qcow2" --cloud-init "user-data=test-user-data" # virsh console # (boot sequence output ending with login prompt, ^] to exit) # virsh destroy test # virsh undefine test | ||||
Additional Information | In the above example, the cloud-init data in ./test-user-data is minimal: --------------------- #cloud-config preserve_hostname: false hostname: test fqdn: test.example.com ssh_pwauth: True users: - name: root hashed_passwd: [redacted] lock_passwd: false ssh_authorized_keys: - ssh-ed25519 [redacted] --------------------- | ||||
Tags | No tags attached. | ||||
This failure to boot is also reproducible when using the LVM image: Rocky-9-GenericCloud-LVM-9.4-20240509.0.x86_64.qcow2 | |
I notice the following in the syslog: May 28 12:22:58 ... setroubleshoot[181117]: SELinux is preventing /usr/libexec/qemu-kvm from getattr access on the file /proc/sys/vm/max_map_count. For complete SELinux messages run: sealert -l 6b4461e1-8775-46d6-975b-2ec47d990999 May 28 12:22:58 ... setroubleshoot[181117]: SELinux is preventing /usr/libexec/qemu-kvm from getattr access on the file /proc/sys/vm/max_map_count. So may be related to https://gitlab.com/qemu-project/qemu/-/issues/2324 |
|
Belay that. The AVC above occurs on both booting and non-booting images. Probably a red herring. | |