Bug 6728 - [build Appliance] The vmdk image path is hardcoded in Yocto_Build_Appliance.vmx
Summary: [build Appliance] The vmdk image path is hardcoded in Yocto_Build_Appliance.vmx
Status: VERIFIED FIXED
Alias: None
Product: Runtime
Classification: Build System, Metadata & Runtime
Component: build-appliance (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Cristian Iorga
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-16 06:08 UTC by Yi Zhao
Modified: 2014-09-23 08:10 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2014-09-16 06:08:40 UTC 
Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M3.rc2/build-appliance/

Git rev: master/429802fe6691c8a70ec9735c0db4c6a4e1e1b038

Currently the vmdk image path is hardcoded in Yocto_Build_Appliance.vmx:

sata0:0.fileName = "/mnt/Yo/yoctoproject/VMs/BA/Yocto_Build_Appliance.vmdk"

If I extracted the image to a different directory and start to launch the vmdk in Vmware-workstation, I got the following error:

File not found: /mnt/Yo/yoctoproject/VMs/BA/Yocto_Build_Appliance.vmdk

I must correct the path in vmx file manually.

It's better to use a relative path in the config file. I try to change it with 
sata0:0.fileName = "Yocto_Build_Appliance.vmdk" . It works well.
Comment 1 Cristian Iorga 2014-09-16 06:17:28 UTC 
Fix comming.
Comment 2 Cristian Iorga 2014-09-16 07:19:56 UTC 
Fix submitted for review.
Comment 4 Yi Zhao 2014-09-23 08:10:30 UTC 
Verified with 2014-09-16-2 build

Git rev: master/7d80f8e9468253496a7097685aac8f468940a9c5