Some Clarification: Creation and Usage
A) I have an existing VM image that has the following contents
system.vmdk
system-flat.vmdk
system.vmx
nvram
I can't seem to get this to be "converted" by LivePC for Windows. I changed system.vmx to vm.vmx but I believe the problem is with having the 2 vmdk files. These don't have any snapshots in them and every vm I've ever created seems to have this structure so not sure what to do here.
B) I'm considering using LivePC as a nice way to have folks run my images. These images are intended to provide a trial experience of a true network appliance. Ultimately each users "instance" will be configured to their particular circumstance. How can/are these changes kept persistant as it seems to me that a user will get an "original state" image each time they start LivePC.
thanks
Hi,
Hi,
You will need to use the vmware-vdiskmanager to convert your disk into a format that our import tool can understand. Please see these steps.
-John
yes I stumbled across these
yes I stumbled across these references to vmdiskmanager...this got me to an "import". I then created a package but these appear to be almost stub like vmx and vmdk files, clearly not my original vmdk disk which is at 430 MB. I'm also curious as to what the difference 'tween a deepcopy and shallowcopy are.
Additionally how do I create a package with my actual true vm environment..sorry for the silly questions but maybe I'm missing some section of your documentation but it is complete but frankly a bit light.
Hi Colin,
Hi Colin,
Could you send us your vmx file? That might help us track down the problem. Also, if you could upload your original vmdk disk to e.g. www.sharebig.com we can take a stab at converting it.
Deep copy will include the entire virtual machine in the package. Shallow copy will only include the changes you made since the last publish. So you want to use deep copy if you haven't published before or if you need to host the whole image in one place.
Thanks for the feedback on the documentation. We are in the process of improving it and hopefully that section will be clearer in the updated version. We will roll out the new version hopefully sometime next week.
-John
Here is my original
Here is my original vmx...also where might I find a log of livepc ...did not get any obvious errors during my import/convert.
config.version = "8"
virtualHW.version = "4"
scsi0.present = "FALSE"
scsi0.virtualDev = "lsilogic"
memsize = "128"
ide0:0.present = "TRUE"
ide0:0.fileName = "system.vmdk"
ide0:0.deviceType = "plain"
ide1:0.present = "FALSE"
ide1:0.fileName = "D:"
ide1:0.deviceType = "cdrom-raw"
floppy0.fileName = "A:"
Ethernet0.present = "TRUE"
displayName = "AccessAnywhere Virtual Edition 3.0.1b"
guestOS = "other26xlinux"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
ide0:0.redo = ""
ethernet0.addressType = "generated"
ethernet0.connectionType = "custom"
ethernet0.vnet = "VMnet0"
uuid.location = ""
uuid.bios = ""
ide1:0.autodetect = "FALSE"
ethernet0.generatedAddress = ""
ethernet0.generatedAddressOffset = "0"
checkpoint.vmState = ""
checkpoint.vmState.readOnly = "FALSE"
floppy0.present = "FALSE"
all figured out folks...took
all figured out folks...took the disk type directive out and voila.
Thanks for your help
Can you provide additional
Can you provide additional information? Did importing just the system.vmx work or was the same warning "Cannot Process Disk .split.vmdx: Could it be a snapshot version" occur?
1. Is this a Desktop or USB version of the LivePC Engine that you are attempting to import the Virtual Machine on?
2. What are the sizes of the vmdks?
3. Can you send us the vmx file ([email protected])?
For item 2:
If a user needs to changes to the LivePC and doesn't need any updates, then enabling "Let me make changes" will do it.
Thanks
Kevin