Changes not persistant
Submitted by Joseph Swaminathan on August 13, 2007 - 5:04pm.
My LivePC is locally hosted, and any changes I make is not made persistant on the http server. I edited the vmx file to set the "should_persist" flag to "true". Still its not persistant.
Stopping and restarting the virtual machine shows the change (I guess it is cached on the client PC where Iam running the engine. I monitored all the http traffic and I only see GET & HEAD operations and the files are unmodified on the server.) I had assumed the moka5 engine implements COW functionality, and I hoped to see some requests going back to the HTTP server to this effect, but didnt see.
Hence when I remove the engine and readd it, it doesnt show the changes as the files on the server are not modified.
I herewith attach the contents of my .vmx file
checkpoint.disableCpuCheck = "true"
checkpoint.overrideVersionCheck = "true"
checkpoint.vmState = ""
config.version = "8"
displayname = "Redhat"
ethernet0.addresstype = "generated"
ethernet0.connectiontype = "nat"
ethernet0.generatedAddressOffset = "0"
ethernet0.present = "true"
floppy0.autodetect = "true"
floppy0.filename = "auto detect"
floppy0.present = "true"
floppy0.startconnected = "FALSE"
guestos = "other26xlinux"
gui.fullScreenAtPowerOn = "FALSE"
ide0:0.autodetect = "false"
ide0:0.devicetype = "disk"
ide0:0.disksize = "20000"
ide0:0.filename = "system.vmdk"
ide0:0.present = "true"
ide0:0.redo = ""
ide0:0.should_persist = "true"
ide0:0.startconnected = "true"
ide0:1.autodetect = "false"
ide0:1.devicetype = "disk"
ide0:1.disksize = "2000"
ide0:1.filename = "local.vmdk"
ide0:1.present = "true"
ide0:1.redo = ""
ide0:1.should_persist = "true"
ide0:1.startconnected = "true"
ide1:0.autodetect = "true"
ide1:0.devicetype = "cdrom-raw"
ide1:0.filename = "auto detect"
ide1:0.present = "true"
ide1:0.redo = ""
ide1:0.should_persist = "true"
ide1:0.startconnected = "true"
isolation.tools.copy.enable = "true"
isolation.tools.hgfs.disable = "TRUE"
isolation.tools.paste.enabled = "true"
logo = "/app/Redhat-e7a974c0-f366-4aa9-a610-cdb8e3533ce9/original/moka5icon.png"
mainMem.useNamedFile = "FALSE"
memsize = "256"
memsize.min = "256"
mouse.autograb = "false"
sched.mem.pshare.enable = "false"
scsi0.present = "false"
serial0.fileName = "\\.\pipe\m5gdrv"
serial0.fileType = "pipe"
serial0.pipe.endPoint = "server"
serial0.present = "true"
serial0.tryNoRxLoss = "true"
sharedFolder.maxNum = "0"
sound.present = "TRUE"
sound.startconnected = "TRUE"
sound.virtualdev = "es1371"
tools.remindInstall = "false"
tools.syncTime = "true"
tools.upgrade.policy = "manual"
usb.generic.autoconnect = "true"
usb.present = "true"
uuid.action = "create"
uuid.location = "56 4d 41 f9 5a 78 0a 9f-70 00 ec 17 97 66 eb cc"
virtualHW.productCompatibility = "hosted"
virtualHW.version = "4"
vmmouse.present = "true"
vm_engine.vmplayer = "true"
thanks
Joseph
Hi John, Thanks once
Submitted by Joseph Swaminathan on August 13, 2007 - 10:00pm.
Hi John,
Thanks once again for a quick and detailed reply.
thanks
Joseph
Hi Joseph, The
Hi Joseph,
The "should_persist" flag only affects local changes. It doesn't update the copy on the server. To update the copy on the server, you need to make changes locally, package the LivePC, upload it to the server, then publish that update so whoever is subscribed to that LivePC will get the updated version.
You can think of it like this: The publisher turns on "Let me make changes", makes whatever modifications he wants to share, tests them out locally and makes sure they are working OK, then publishes an update. When the LivePC is updated, subscribers automatically pick up the new version and start using it the next time they start the LivePC. Hope that makes sense.
-John