Bug 1892800
| Summary: | NVDIMM: VM hangs in wait for launch for more than 7 minutes before VM is up. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Nisim Simsolo <nsimsolo> | ||||||||
| Component: | General | Assignee: | Milan Zamazal <mzamazal> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.40.35 | CC: | ahadas, bugs, nsimsolo | ||||||||
| Target Milestone: | ovirt-4.4.6 | Keywords: | TestOnly | ||||||||
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
|
||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | vdsm-4.40.60.1 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
Starting VMs with NVDIMM devices could take an extra time, depending on the NVDIMM device size. This has been fixed and VMs with NVDIMM devices start without unnecessary delays now.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-05-05 05:36:26 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: | |||||||||||
| Bug Depends On: | 1894053, 1933974 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1725106 [details]
qemu.log
Created attachment 1725107 [details]
engine.log
Created attachment 1725108 [details]
vdsm.log
Verified:
ovirt-engine-4.4.5.9-0.1.el8ev
vdsm-4.40.50.10-1.el8ev.x86_64
libvirt-daemon-7.0.0-11.module+el8.4.0+10505+3a8d753f.x86_64
qemu-kvm-5.2.0-14.module+el8.4.0+10425+ad586fa5.x86_64
2xNVDIMM devices for each VM with the next namespaces:
# ndctl list --namespaces
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":270582939648,
"uuid":"3647813f-1850-4ca9-a2ee-e6faabad979e",
"sector_size":4096,
"blockdev":"pmem1"
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":270582939648,
"uuid":"e6a7f67b-8f4e-41dc-93bc-4c1201ed1e63",
"sector_size":4096,
"blockdev":"pmem0"
}
]
Verification scenario:
1. Verify VM launches immediately with the next NVDIMM modes:
sector, raw and fsdax
2.Verify VM launches immediately after reboots.
3. Verify VM launches immediately after power off.
4. Verify VM launches immediately after shut down.
5. Verified with RHEL8, Win16 and Win19 VMs.
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Description of problem: - When running VM with NVDIMM device attached, the loading time is taking more than 7 minutes till the VM is up. - during that time VM state is "wait for launch" - domstate reason is: # virsh -r domstate --reason 8 paused (starting up) - out of 3 times powering off -> running the VM, 2 times it took 10 minutes till the VM goes up, and one time it took 7 minutes. - When removing NVDIMM device, VM is going up immediately. Version-Release number of selected component (if applicable): ovirt-engine-4.4.3.8-0.1.el8ev vdsm-4.40.35-1.el8ev.x86_64 libvirt-daemon-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64 qemu-kvm-5.1.0-13.module+el8.3.0+8382+afc3bbea.x86_64 How reproducible: 100% Steps to Reproduce: 1. Add NVDIMM device to VM. 2. Run VM. 3. Actual results: VM is hanging for more than 7 minutes in wait for launch state before it goes up. Expected results: Loading time should not be that long. Additional info: engine.log, qemu.log and vdsm.log attached: VM started at: 2020-10-29 12:03:09,906-0400 INFO (jsonrpc/0) [api.virt] START create(vmParams={'vmId': '2bec1859-c649-47c9-a3ef-27813f633dd0', VM is up at: 2020-10-29 12:13:24,362-0400 INFO (libvirt/events) [virt.vm] (vmId='2bec1859-c649-47c9-a3ef-27813f633dd0') CPU running: onResume (vm:5633)