Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1521654[details]
sosreport from beaker system
Description of problem:
Tried creating a RHEL 8 VM and it seem to start then disappears from the UI completely? virsh list shows the vm as started?
Version-Release number of selected component (if applicable):
Latest RHEL 8 beta
How reproducible:
Every time
Steps to Reproduce:
1. Use the cockpit UI to create a RHEL 8 VM
2. VM shows as starting install then disappears.
Actual results:
VM disappears from the UI even though command line virsh list shows the vm as running.
[root@ibm-hs12-8014-1 home]# ps -elf|grep rhel8
0 S root 21056 1 0 80 0 - 133911 core_s 12:56 ? 00:00:01 /usr/libexec/platform-python /usr/share/virt-manager/virt-install --name rhel8 --os-variant auto --memory 1024 --quiet --disk size=10,format=qcow2 --wait -1 --noautoconsole --noreboot --cdrom /home/RHEL-8.0-20181113.1-x86_64-dvd1.iso --graphics vnc,listen=127.0.0.1
6 S qemu 21123 1 1 80 0 - 492399 x64_sy 12:56 ? 00:00:45 /usr/libexec/qemu-kvm -name guest=rhel8,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-rhel8/master-key.aes -machine pc-q35-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off -cpu Conroe,vme=on,ss=on,cx16=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc_adjust=on -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 44fea7ce-55e3-4968-8fe3-9e40acd04b09 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=28,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive file=/var/lib/libvirt/images/rhel8-1.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/home/RHEL-8.0-20181113.1-x86_64-dvd1.iso,format=raw,if=none,id=drive-sata0-0-0,media=cdrom,readonly=on -device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:5c:0d,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=33,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
Expected results:
VM should show in the UI no matter the state.
Additional info:
[root@ibm-hs12-8014-1 home]# virsh list
Id Name State
----------------------------------------------------
6 rhel8 running
Comment 2Dr. David Alan Gilbert
2019-01-18 20:24:46 UTC
Hi Frank,
That host has almost no RAM - 480MB.
It's useless for running VMs on (and frankly useless for running much else).
You're trying to run a 1GB VM on it; from the logs, 3 out of 4 times it's failed with qemu giving an out of memory; the 4th one is surviving in swap
by the looks of it, but I bet something else has fallen over out of RAM.
Please get a host with some RAM.
I tried creating a host with more RAM than what's available on the host, and I got an error message, so I don't think it's that.
I've filed an issue upstream suggesting to check the amount of RAM on the host before attempting to create the VM.
https://github.com/cockpit-project/cockpit/issues/11140
I already addressed the issue that Andreas pointed out in
commit efa902727bcfba053378113e3d0d676bc8ba391f
Author: Katerina Koukiou <kkoukiou>
machines: Set upper limit for VM's memory in the VM creation dialog
Which was part of 192 release.
Now the cockpit user will not be allowed to select memory greater than the host's memory. Please re-open if you hit this issue again.
Test Versions:
cockpit-machines-196-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64
Test Steps:
1. Open the creation dialog to prepare to create a VM
2. Check whether there is a notification below the memory input, that is showing the limit of memory
3. Input a value which is over than the host memory
Test Results:
1. After step 2, there is a notification shown below the memory input on the creation dialog, that shows the hosts memory limit.
2. After step 3, the input box can not be inputted a value which is larger than host memory
According to the results, move the status to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3325
Created attachment 1521654 [details] sosreport from beaker system Description of problem: Tried creating a RHEL 8 VM and it seem to start then disappears from the UI completely? virsh list shows the vm as started? Version-Release number of selected component (if applicable): Latest RHEL 8 beta How reproducible: Every time Steps to Reproduce: 1. Use the cockpit UI to create a RHEL 8 VM 2. VM shows as starting install then disappears. Actual results: VM disappears from the UI even though command line virsh list shows the vm as running. [root@ibm-hs12-8014-1 home]# ps -elf|grep rhel8 0 S root 21056 1 0 80 0 - 133911 core_s 12:56 ? 00:00:01 /usr/libexec/platform-python /usr/share/virt-manager/virt-install --name rhel8 --os-variant auto --memory 1024 --quiet --disk size=10,format=qcow2 --wait -1 --noautoconsole --noreboot --cdrom /home/RHEL-8.0-20181113.1-x86_64-dvd1.iso --graphics vnc,listen=127.0.0.1 6 S qemu 21123 1 1 80 0 - 492399 x64_sy 12:56 ? 00:00:45 /usr/libexec/qemu-kvm -name guest=rhel8,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-rhel8/master-key.aes -machine pc-q35-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off -cpu Conroe,vme=on,ss=on,cx16=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc_adjust=on -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 44fea7ce-55e3-4968-8fe3-9e40acd04b09 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=28,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive file=/var/lib/libvirt/images/rhel8-1.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/home/RHEL-8.0-20181113.1-x86_64-dvd1.iso,format=raw,if=none,id=drive-sata0-0-0,media=cdrom,readonly=on -device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:5c:0d,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=33,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on Expected results: VM should show in the UI no matter the state. Additional info: [root@ibm-hs12-8014-1 home]# virsh list Id Name State ---------------------------------------------------- 6 rhel8 running