Bug 1786464 - [4.4] Run vm with windows as OS type fail
Summary: [4.4] Run vm with windows as OS type fail
Keywords:
Status: CLOSED DUPLICATE of bug 1782882
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.0
: ---
Assignee: Steven Rosenberg
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-25 12:04 UTC by Beni Pelled
Modified: 2019-12-26 09:00 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-12-26 09:00:21 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)

Description Beni Pelled 2019-12-25 12:04:52 UTC
Description of problem:

Can't start vm with OS type set to any windows version.


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

ovirt-engine-4.4.0-0.13.master.el7.noarch
vdsm-4.40.0-164.git38a19bb.el8ev.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Create VM with 'Windows7 x64' as OS type (or any other windows version)
2. Start VM

Actual results:
The VM starts faling with:
VM <vm_name> is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2019-12-25T11:53:15.440747Z qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=1024: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead

Expected results:
Start VM successfully

Additional info:

The problem is quite clear (deprecated parameter) by the error specified on the vdsm log

------ vdsm log:

2019-12-25 06:47:49,567-0500 DEBUG (check/loop) [storage.check] START check '/dev/9a96404e-09a7-4b5d-bf6b-16fe9f649d31/metadata' (delay=0.01) (check:289)
2019-12-25 06:47:49,587-0500 DEBUG (check/loop) [storage.check] FINISH check '/dev/9a96404e-09a7-4b5d-bf6b-16fe9f649d31/metadata' (rc=0, elapsed=0.02) (check:359)
2019-12-25 06:47:49,769-0500 ERROR (vm/12c5fe4a) [virt.vm] (vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c') The vm start process failed (vm:835)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 769, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2585, in _run
    dom.createWithFlags(flags)
  File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1166, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2019-12-25T11:47:48.017283Z qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=1024: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead
Hyper-V synthetic interrupt controller (hv-synic) requires Hyper-V VP_INDEX MSR (hv-vpindex)
2019-12-25T11:47:48.018734Z qemu-kvm: kvm_init_vcpu failed: Function not implemented
2019-12-25 06:47:49,769-0500 INFO  (vm/12c5fe4a) [virt.vm] (vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c') Changed state to Down: internal error: process exited while connecting to monitor: 2019-12-25T11:47:48.017283Z qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=1024: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead
Hyper-V synthetic interrupt controller (hv-synic) requires Hyper-V VP_INDEX MSR (hv-vpindex)
2019-12-25T11:47:48.018734Z qemu-kvm: kvm_init_vcpu failed: Function not implemented (code=1) (vm:1604)
2019-12-25 06:47:49,895-0500 INFO  (vm/12c5fe4a) [virt.vm] (vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c') Stopping connection (guestagent:455)
2019-12-25 06:47:49,908-0500 INFO  (jsonrpc/2) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.46.16.85,41654, flow_id=1f93e606, vmId=12c5fe4a-1436-4200-a5ed-ccf3c62dc46c (api:48)
2019-12-25 06:47:49,908-0500 INFO  (jsonrpc/2) [virt.vm] (vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c') Release VM resources (vm:4819)


------ engine log:

2019-12-25 13:47:49,905+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [1f93e606] START, DestroyVDSCommand(HostName = host_mixed_2, DestroyVmVDSCommandParameters:{hostId='521a0fb8-230c-42
b6-94f1-3e73e1d745f4', vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 61a4c5fc
2019-12-25 13:47:50,669+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [1f93e606] FINISH, DestroyVDSCommand, return: , log id: 61a4c5fc
2019-12-25 13:47:50,669+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [1f93e606] VM '12c5fe4a-1436-4200-a5ed-ccf3c62dc46c'(test_vm_windows_type) moved from 'WaitForLaunch' --> 'Down'
2019-12-25 13:47:50,739+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-7) [1f93e606] EVENT_ID: VM_DOWN_ERROR(119), VM test_vm_windows_type is down with error. Exit message: internal error: process exited while connecting to monitor: 2019-12-25T11:47:48.017283Z qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=1024: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead
Hyper-V synthetic interrupt controller (hv-synic) requires Hyper-V VP_INDEX MSR (hv-vpindex)
2019-12-25T11:47:48.018734Z qemu-kvm: kvm_init_vcpu failed: Function not implemented.
2019-12-25 13:47:50,740+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [1f93e606] add VM '12c5fe4a-1436-4200-a5ed-ccf3c62dc46c'(test_vm_windows_type) to rerun treatment
2019-12-25 13:47:50,745+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-7) [1f93e606] Rerun VM '12c5fe4a-1436-4200-a5ed-ccf3c62dc46c'. Called from VDS 'host_mixed_2'
2019-12-25 13:47:50,760+02 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] EVENT_ID: USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM test_vm_windows_type on Host host_mixed_2.
2019-12-25 13:47:50,766+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] Lock Acquired to object 'EngineLock:{exclusiveLocks='[12c5fe4a-1436-4200-a5ed-ccf3c62dc46c=VM]', sharedLocks=''}'
2019-12-25 13:47:50,825+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='12c5fe4a-1436-4200-a5ed-ccf3c62dc46c'}), log id: 3325a960
2019-12-25 13:47:50,825+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 3325a960
2019-12-25 13:47:50,843+02 WARN  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS
2019-12-25 13:47:50,843+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] Lock freed to object 'EngineLock:{exclusiveLocks='[12c5fe4a-1436-4200-a5ed-ccf3c62dc46c=VM]', sharedLocks=''}'
2019-12-25 13:47:50,852+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-49740) [1f93e606] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM test_vm_windows_type  (User: admin@internal-authz).
2019-12-25 13:47:50,873+02 INFO  [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-49741) [58bb678f] Running command: ProcessDownVmCommand internal: true.
2019-12-25 13:47:52,624+02 INFO  [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /10.46.17.131

Comment 1 Michal Skrivanek 2019-12-26 06:20:33 UTC
Behavior changed by https://patchwork.kernel.org/patch/10648275/

Comment 2 Steven Rosenberg 2019-12-26 09:00:21 UTC

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


Note You need to log in before you can comment on or make changes to this bug.