Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1635607

Summary: hotplug memory failed
Product: [oVirt] ovirt-engine Reporter: Pedut <pchocron>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED WORKSFORME QA Contact: Pedut <pchocron>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.6CC: bugs, pchocron, ratamir, rbarry
Target Milestone: ---Keywords: Automation, AutomationBlocker, Regression
Target Release: ---Flags: ratamir: blocker?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-11 12:12:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Pedut 2018-10-03 11:21:07 UTC
Created attachment 1489925 [details]
logs

Description of problem:
An extension of the memory with hotplug completed fine.
But memory does not expand on the VM.

Version-Release number of selected component (if applicable):
Red Hat Virtualization Host 4.2.7 (el7.6)
host and vm must be with RHEL - 7.6 - 7.0.el7

How reproducible:
Always

Steps to Reproduce:
1. Create a VM with RHEL - 7.6 - 7.0.el7 and disable memory balloon device
2. Run the VM
3. Expand VM memory using memory hot-plug

Actual results:
From the engine, the memory seems to expand. However, when connected to the guest the memory size remains the same.

Expected results:
The memory expanded

Additional info:

Comment 1 Michal Skrivanek 2018-10-03 13:35:43 UTC
guest agent stuff doesn't work due to bug 1634765. Please retest with a workaround (you can change permissions on the socket file) or once that is fixed.

Comment 3 Pedut 2018-10-03 14:47:12 UTC
I tried to check the permissions of the guest agent socket file but I cant find it in the path /var/lib/libvirt/qemu/channel/target/domain-100-hotplug_76/

[root@lynx10 target]# ll -a /var/lib/libvirt/qemu/channel/target/domain-100-hotplug_76/
total 8
drwxr-x---. 2 qemu qemu 4096 Oct  3 17:25 .
drwxr-xr-x. 3 qemu qemu 4096 Oct  3 17:25 ..

Do I need to change the permissions of another socket file?
If so, could you please provide me details about the workaround(the relevant socket file and permissions). 
Otherwise, I will retest it when it will be fixed.

Comment 4 Michal Skrivanek 2018-10-03 15:15:48 UTC
The VM needs to be running. 

Otherwise I provided link to fixed libvirt build in private comment #2

Comment 5 Pedut 2018-10-04 06:44:23 UTC
The VM ran while I checked it.

Comment 6 Michal Skrivanek 2018-10-04 08:00:58 UTC
/var/lib/libvirt/qemu/channels/, not /var/lib/libvirt/qemu/channel/...

Comment 7 Pedut 2018-10-08 07:13:46 UTC
Somehow I can't reproduce the bug even if I don't change the permissions of the socket file.
Nevertheless the bug can't vanish.

Comment 8 Michal Skrivanek 2018-10-08 08:12:16 UTC
well, if you can't reproduce it then it does end up as CLOSED WORKSFORME:)

Comment 9 Ryan Barry 2018-10-11 12:12:08 UTC
Please re-open if this can be reproduced.