42 replies to this topic

[Galapo]

Just wondering if anyone else can't get VMXBuilder (the script on the LiveXP server, not the one from nativeEx_moa-lite as it doesn't work either) to work properly. When I attempt to create a new VM or edit an existing one, I get the following error:



Thanks,
Galapo.

[Galapo]

If not building with Thuun's Scripting Core script, I get this error:



Regards,
Galapo.

[dera]

I think VMXBuilder needs also these files:

MSCOMCTL.OCX
TABCTL32.OCX

[Galapo]

Hi Dera,

Yes, you are correct. However, the vb files are installed with the setup program from the author's site. Still have the error unfortunately...

Regards,
Galapo.

[dera]

Hi
I use this slightly modded script of Thuun
 ScriptingSup_mod.7z   7.17KB   563 downloads
I think the file:
mfc42.dll
is the main point

Edit:
and the '7 - OLESupport.Script' is not enabled
the %SystemDrive% is writable
seems VMXBuilder works
(but somehow e.g. I am not able to define a SCSI disk)
and sorry for my previous post, didn't noticed this 'Start_VMXBuilder.cmd' and 'CoreSetup.exe'

[dera]

Tried without Thuun's Scripting Core script
so seems:
mfc42.dll is needed
and also have to RegisterServer the file scrrun.dll but without mfc42.dll it is not successfull

[Lancelot]

With VMW Builder
i created new vm by using ScriptingSup_mod.7z
but after creation i couldnt play it, so i use CoreSetup.exe from website
After that i press play, VMware Player worked with giving warning "You may not power on a virtual machine in a virtual machine"

[sanbarrow]

"You may not power on a virtual machine in a virtual machine"

can be cheated with

monitor_control.restrict_backdoor = "true"

then VMplayer will not notice that it is running in a nested VM

see my site on vmx-parameters
http://sanbarrow.com...monitor_control

Ulli

[Galapo]

Tried without Thuun's Scripting Core script
so seems:
mfc42.dll is needed
and also have to RegisterServer the file scrrun.dll but without mfc42.dll it is not successfull

Thank you Dera! It's working! I'll upload an adjusted script shortly.

@Ulli
The VM Lancelot was referring to currently has the cheatcode, but still won't allow it to be powered on. Same result for me under Server 1.0.5.

Regards,
Galapo.

[sanbarrow]

Galapo - starting a nested VM should work in both cases - I need more info ...

[Galapo]

Here's the test.vmx that Peter has supplied with his VMWare Player script:

config.version = "8"

virtualHW.version = "6"

displayName = "Mini Test VM"

guestOS = "winxppro"

memsize = "8"



scsi0.present = "false"

usb.present = "false"

sound.present = "false"

floppy0.present = "false"



monitor_control.restrict_backdoor = "TRUE"



extendedConfigFile = "test.vmxf"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"



uuid.location = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

uuid.bios = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

checkpoint.vmState = "test.vmss"

Is this enoght info?

Regards,
Galapo.

[sanbarrow]

config.version = "8"

virtualHW.version = "6"

displayName = "Mini Test VM"

guestOS = "winxppro"

memsize = "8"



scsi0.present = "false"

usb.present = "false"

sound.present = "false"

floppy0.present = "false"



monitor_control.restrict_backdoor = "TRUE"



extendedConfigFile = "test.vmxf"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"



uuid.location = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

uuid.bios = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

checkpoint.vmState = "test.vmss"

Setting this

checkpoint.vmState = "test.vmss"

is a bad idea - vmss is the extension for a saved suspended state - if you don't have the file test.vmss starting this VM will fail.

This entries are not necessary:

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

uuid.location = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

uuid.bios = "56 4d 33 0b 56 86 72 7d-73 44 38 41 80 7c 05 c3"

Setting this may popup a question for XP-scsi-drivers

guestOS = "winxppro"

while

guestOS = "winnetenterprise"

will boot without question.

If that doesn't help post a vmware.log

[sanbarrow]

virtualHW.version = "4"

to test in VMserver you should also set this

[Lancelot]

Here is test.vmx i use

config.version = "8"

virtualHW.version = "6"

displayName = "Mini Test VM"

guestOS = "winnetenterprise"

memsize = "8"



scsi0.present = "false"

usb.present = "false"

sound.present = "false"

floppy0.present = "false"



monitor_control.restrict_backdoor = "TRUE"



extendedConfigFile = "test.vmxf"



virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

Here is the log file:
http://lancelot.winb...00810262340.log

I still get the same error Ulli !
ps: I use vmware workstation 6.5 to start livexp.iso

[sanbarrow]

ps: I use vmware workstation 6.5 to start livexp.iso

Then you must add that line
monitor_control.restrict_backdoor = "TRUE"
to the WS 6.5 vmx - this is the one you must cheat - not the nested one !


The entry in the mini-test-VM.vmx doesn't hurt but it is irrelevant.

[Galapo]

Thanks, Ulli! Now I get it!

Regards,
Galapo.

[sanbarrow]

@ Lancelot

Do you have Intel VT ? - most Intel Dual Core CPUs have this but some boards disable that function in BIOS

then also set
monitor.virtual_exec = "hardware"

then you can really test the nested VM - if you don't have VT support and don't set that entry the nested VM will be slow as molasses ....

Galapo - VMserver doesn't know how to make use of that ...

[Lancelot]

Ulli

as Galapo wrote Now I get it too

i add line to my existing vmwarevirtual pc .vmx file, still same error.

Sadly i dont have VT support, i know it by crying for a long time,
For others to check to see if they have VT support, here is a utility from vmware
http://www.vmware.co...vers_tools.html
download this file
http://download3.vmw...6.0.0-45731.exe

Galapo, maybe it is nice to put this (or sth like this) to one of the virtualization scripts for future questions of VT support, maybe not, you decide.

I wonder if Galapo had a success?

Thanks for everything Ulli

[Galapo]

Galapo - VMserver doesn't know how to make use of that ...

Oh, that's a bit sad...

[sanbarrow]

Galapo - why do you use VMserver 1 ?

VMplayer "plus" is free too

Just run Workstation without license - create VMs and edit them in vmware.exe - run them in vmplayer.exe.

@ Lancelot - the vmx-parameters that enable Intel VT or AMD Pacifica support have changed from WS 6 to WS 6.5 ...
If you ever want to add the parameters to a script I can show you which ones are appropriate

Ulli

[Galapo]

Yes, I'm currently using 1.0.5. By "Plus" I take it that you mean version 2. I didn't realise it was out of beta until I just checked the website now. Is it worth upgrading to?

Thanks,
Galapo.

[sanbarrow]

Do you ask about VMserver 2 ?

Forget it - its complete bloatware - you need a TomCat Java-server to run the web-interface and you need dotnet2 and ViClient to run something like a Console.
It no longer has what you know as VMserver-remote-console - it is slower ... needs a defined datastore ... only good thing is support for USB2.

Best hosted product IMHO is at the moment Workstation 6.0.5
6.5.0 at the moment is still buggy - hope for 6.5.1 soon

Same applies to VMplayer 2.5.0

[Galapo]

Sorry I misread. Player plus was what you were meaning. But what is the Plus version?

Thanks for the info -- I won't be "upgrading" to version 2 of Server then. It's sad that they've removed features and increased dependencies. But usb2 would be nice...

Thanks,
Galapo.

[sanbarrow]

But what is the Plus version?

Oh - thats just the nicname I use ...
VMplayer is just a ripped Workstation - if you run VMplayer and use Workstation-files you get additional features like editing and creating VMs with vmware.exe.
You only need the license to actually run VMs with vmware.exe - then you can use hot-snapshots and other WS-stuff.

The easiest way to get this - is install Workstation with trial-license and when it is expired simply keep the setup and only run VMs in VMplayer.exe.

[Lancelot]

Ulli, for now as i use Core2DuoE4400 i wont have a VT question.

Best hosted product IMHO is at the moment Workstation 6.0.5
6.5.0 at the moment is still buggy - hope for 6.5.1 soon

As Ulli, master of virtualization wrote 6.05 is best, than 6.05 i will use. But first i need to download, 45minutes (100kb/sec download speed)