Bug 2035679

Summary: High performance Workload profile VM can not be started
Product: Container Native Virtualization (CNV) Reporter: Leon Kladnitsky <lkladnit>
Component: VirtualizationAssignee: sgott
Status: CLOSED DUPLICATE QA Contact: Kedar Bidarkar <kbidarka>
Severity: high Docs Contact:
Priority: high    
Version: 4.10.0CC: aos-bugs, cnv-qe-bugs, gouyang, ycui
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-29 14:01:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm_list
none
vm yaml
none
rhel9_vm_yaml none

Description Leon Kladnitsky 2021-12-26 20:09:21 UTC
Created attachment 1847863 [details]
vm_list

Created attachment 1847863 [details]
vm_list

Description of problem:

Windows 10 VM that was created using custom wizard will not start.

Version-Release number of selected component (if applicable):
4.10.0-0.ci-2021-12-23-133912


How reproducible:
 100%

Steps to Reproduce:
1. Create Windows 10 VM using from http://cnv-qe-server.rhevdev.lab.eng.rdu2.redhat.com/files/cnv-tests/windows-images/win_10.qcow2 with custom wizard
2. Check "Start this virtual machine after creation"  checkbox
3. Click "Create Virtual Machine" button

Actual results:
VM does not start. VM status is "CrashLoopBackOff"
Event tab contains error message:

    server error. command SyncVMI failed: "LibvirtError(Code=67, Domain=10, Message='unsupported configuration: kvm-hint-dedicated=on is only applicable for cpu host-passthrough')"


Expected results:
VM should start

Additional info:

The same VM when created with default wizard starts as expected

Comment 1 Guohua Ouyang 2021-12-27 03:21:34 UTC
Could not reproduce the issue, would you please try it again on the latest console?

Comment 2 Guohua Ouyang 2021-12-28 10:33:54 UTC
(In reply to Guohua Ouyang from comment #1)
> Could not reproduce the issue, would you please try it again on the latest
> console?

It's only reproduced when the VM workload is high-performance.

Comment 3 Guohua Ouyang 2021-12-28 10:38:41 UTC
Created attachment 1848061 [details]
vm yaml

Comment 4 Leon Kladnitsky 2021-12-28 11:50:37 UTC
(In reply to Guohua Ouyang from comment #2)
> (In reply to Guohua Ouyang from comment #1)
> > Could not reproduce the issue, would you please try it again on the latest
> > console?
> 
> It's only reproduced when the VM workload is high-performance.

Yes, I second that, VM with Desktop Workload Profile starts normally.

Comment 5 Leon Kladnitsky 2021-12-29 07:16:23 UTC
Created attachment 1848174 [details]
VM list

Comment 6 Leon Kladnitsky 2021-12-29 08:22:46 UTC
After additional tests it turns out that all templates are affected, not only Windows.
If  Workload Profile is set to High performance, VM can't start and is looped between Starting and Error states.

Comment 7 Leon Kladnitsky 2021-12-29 08:23:56 UTC
After additional tests it turns out that all templates are affected, not only Windows.
If  Workload Profile is set to High performance, VM can't start and is looped between Starting and Error states.

Comment 8 Leon Kladnitsky 2021-12-29 08:32:19 UTC
Created attachment 1848177 [details]
rhel9_vm_yaml

Comment 9 Kedar Bidarkar 2021-12-29 14:01:11 UTC

*** This bug has been marked as a duplicate of bug 2029343 ***