Bug 1004704 - [RHEVM] [backen] cannot start VM with iso/vfd attached because of wrong path
[RHEVM] [backen] cannot start VM with iso/vfd attached because of wrong path
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
x86_64 Linux
unspecified Severity urgent
: ---
: 3.3.0
Assigned To: Arik
Jiri Belka
: Regression, TestBlocker, Triaged
Depends On:
Blocks: 928381
  Show dependency treegraph
Reported: 2013-09-05 05:52 EDT by Martin Pavlik
Modified: 2015-04-06 23:10 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-02 07:32:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs (8.03 MB, application/x-compressed-tar)
2013-09-05 05:52 EDT, Martin Pavlik
no flags Details

  None (edit)
Description Martin Pavlik 2013-09-05 05:52:00 EDT
Created attachment 794147 [details]

Description of problem:
cannot start VM with iso/vfd attached because of wrong path

it seems that engine is looking in 


while it should probably go into


Error message from GUI
VM w7_x64 is down. Exit message: [Errno 2] No such file or directory: '/virtio-win-1.6.4_amd64.vfd'.

File exists with correct permission on storage
[root@str-02 11111111-1111-1111-1111-111111111111]# ll virtio-win-1.6.4_amd64.vfd
-rw-r--r--. 1 vdsm kvm 2949120 Jun  4 22:10 virtio-win-1.6.4_amd64.vfd

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

How reproducible:

Steps to Reproduce:
1. create VM
2. run once -> attach .iso or .vfd image
3. click OK

Actual results:
VM fails to start with Exit message: [Errno 2] No such file or directory: '/virtio-win-1.6.4_amd64.vfd'.

Expected results:
VM starts ok

Additional info:


2013-09-05 11:04:33,050 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-87) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM w7_x64 is down. Exit message: [Errno 2] No such file or directory: '/virtio-win-1.6.4_amd64.vfd'.


read-55034::ERROR::2013-09-05 11:04:30,469::vm::2064::vm.Vm::(_startUnderlyingVm) vmId=`f62f8c72-ae28-4d61-a647-a359c8efa21f`::The vm start process failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 2024, in _startUnderlyingVm
  File "/usr/share/vdsm/vm.py", line 2884, in _run
    domxml = hooks.before_vm_start(self._buildCmdLine(), self.conf)
  File "/usr/share/vdsm/vm.py", line 2689, in _buildCmdLine
  File "/usr/share/vdsm/vm.py", line 2656, in _appendDevices
    deviceXML = dev.getXML().toxml(encoding='utf-8')
  File "/usr/share/vdsm/vm.py", line 1536, in getXML
  File "/usr/lib64/python2.6/site-packages/vdsm/utils.py", line 704, in getUserPermissions
    fileStats = os.stat(path)
OSError: [Errno 2] No such file or directory: '/virtio-win-1.6.4_amd64.vfd'

This problem applies also for .iso images
Comment 1 Arik 2013-10-02 06:50:25 EDT
The '/virtio-win-1.6.4_amd64.vfd' string should be appended to the 'iso prefix' - the path to the iso domain. so it seems that for some reason the returned iso prefix is empty string.

I can't reproduce it on my environment though. it would be best if I can access your environment or alternatively you check the iso prefix on the host that you're trying to run the VM on (by running: vdsClient 0 getStoragePoolInfo `vdsClient 0 getConnectedStoragePoolsList`), if it is still reproducible on your environment.

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