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.

Description of problem:

From cockpit UI:

 Virtual Machines -> Select a VM -> Overview


Version-Release number of selected component (if applicable):

kernel-4.18.0-64.el8.x86_64
cockpit-system-184-1.el8.noarch

How reproducible:

100%


Actual results:

There is no option / link to modify virtual machine memory/max mem when the VM is powered off.

Expected results:

Ability to change the amount of VM RAM like we do for virtual CPUs

Additional info:

This is currently being worked on on https://github.com/cockpit-project/cockpit/pull/10547

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. Create a VM, then open the memory setting dialog which is in the overview tab
2. Change 'Current Allocation' to 0, 128 MB, the memory which is the same as 'Maximum Allocation' and the memory which is over than 'Maximum Allocation', at the same time, check the memory of the VM by using command "watch -n 1 'virsh dumpxml ${vm_name} | grep memory -A 1'"
3. Change 'Maximum Allocation' value, then repeat step 2


Test Results:
Memory of the VM can be set.



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