When capturing installation - if I saw the virtual machine is it captured as well?
All right, let's assume that I am ThinApping an application and I'm in the middle of the installation of the main application and a few children and updates applications.
If something goes wrong, I don't want to start from the beginning. So after that I installed can the first main application I take a snapshot of the virtual machine? Well, I know I can, but my question is will be captured by thinapp and packed to the top in the final exe file this snapshot? Something I want to happen.
If so, how would I exclude in the build? If the snapshot is not captured, so it's perfect.
Snapshots of workstation are stored on the host computer. ThinApp scans the guest and will not see the snapshots of work stations. So you can take snapshots of work when you want, they are included in the package.
Tags: VMware
Similar Questions
-
Crash when the instant withdrawal: State of the virtual machine is 'unknown (invalid) '.
Hi all
Currently, I'm in the middle of a nightmare: a few moments I tried to delete a snapshot that has been there for a while on one of my virtual machines. Of course, it can take a loy of time for this kind of operation to achieve, so I waited patiently so that it reaches its end.
But in the middle of it my host had a kernel panic (I'll have to diagnose this one).
When I got to new host, the virtual machine was not the webui, try saving it shows the machine as being "unknow (invalid)"...
I scoured Suur intrenet for a while, but everything I have read until knowledge is quiet frightneging.
Currently, the directory that stores all the files of the virtual machine is looking as follows:
drwxrwxrwx 2 root root 4096 12 October 2008 564d583c-363e-0c7a-96e0-cd07d5b1a8e1.vmem.lck
-rw - 1 root root 2147221504 2 May 20:31 colossus2_2new - f001.vmdk
-rw - 1 root root 2147221504 19 Dec 13:04 colossus2_2new - f002.vmdk
-rw - 1 root root 1074266112 Jan 11 22:27 colossus2_2new - f003.vmdk
-rw - 1 root root 528 2 May 20:31 colossus2_2new.vmdk
-rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f001.vmdk
-rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f002.vmdk
-rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f003.vmdk
-rw - 1 root root 2147221504 19 Dec 13:04 colossus2_3new - f004.vmdk
-rw - 1 root root 2147221504 Jan 11 22:35 colossus2_3new - f005.vmdk
-rw - 1 root root 1310720 Jan 11 22:35 colossus2_3new - f006.vmdk
-rw - 1 root root 661 2 May 20:32 colossus2_3new.vmdk
-rw - 1 root root 2147221504 2 May 20:32 colossus2_4new - f001.vmdk
-rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f002.vmdk
-rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f003.vmdk
-rw - 1 root root 2147221504 2 May 20:34 colossus2_4new - f004.vmdk
-rw - 1 root root 2147221504 2 May 20:35 colossus2_4new - f005.vmdk
-rw - 1 root root 1310720 Jan 11 22:42 colossus2_4new - f006.vmdk
-rw - 1 root root 661 2 May 20:35 colossus2_4new.vmdk
-rw - 1 root root 1868365824 2 May 22:13 colossus2_5new-000001 - s001.vmdk
-rw - 1 root root 1637482496 2 May 22:13 colossus2_5new-000001 - s002.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s003.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s004.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s005.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s006.vmdk
-rw - 1 root root 2096824320 2 May 22:13 colossus2_5new-000001 - s007.vmdk
-rw - 1 root root 554369024 2 May 22:13 colossus2_5new-000001 - s008.vmdk
-rw - 1 root root 1728839680 2 May 22:13 colossus2_5new-000001 - s009.vmdk
-rw - 1 root root 2114191360 2 May 22:13 colossus2_5new-000001 - s010.vmdk
-rw - 1 root root 1659371520 2 May 22:13 colossus2_5new-000001 - s011.vmdk
-rw - 1 root root 1527775232 2 May 22:13 colossus2_5new-000001 - s012.vmdk
-rw - 1 root root 1578958848 2 May 22:13 colossus2_5new-000001 - s013.vmdk
-rw - 1 root root 1611792384 2 May 22:13 colossus2_5new-000001 - s014.vmdk
-rw - 1 root root 1602945024 2 May 22:13 colossus2_5new-000001 - s015.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s016.vmdk
-rw - 1 root root 2085617664 2 May 22:13 colossus2_5new-000001 - s017.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s018.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s019.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s020.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s021.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s022.vmdk
-rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s023.vmdk
-rw - 1 root root 132055040 2 May 22:13 colossus2_5new-000001 - s024.vmdk
-rw - 1 root root 327680 2 May 22:13 colossus2_5new-000001 - s025.vmdk
-rw - 1 root root 65536 2 May 22:13 colossus2_5new-000001 - s026.vmdk
-rw - 1 root root 1582 Mar 8 17:53 colossus2_5new - 000001.vmdk
drwxrwxrwx 3 root root 4096 2 May 22:14 colossus2_5new - 000001.vmdk.lck
-rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f001.vmdk
-rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f002.vmdk
-rw - 1 root root 2147221504 2 May 20:37 colossus2_5new - f003.vmdk
-rw - 1 root root 2147221504 2 May 20:38 colossus2_5new - f004.vmdk
-rw - 1 root root 2147221504 2 May 20:39 colossus2_5new - f005.vmdk
-rw - 1 root root 2147221504 2 May 20:41 colossus2_5new - f006.vmdk
-rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f007.vmdk
-rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f008.vmdk
-rw - 1 root root 2147221504 2 May 20:43 colossus2_5new - f009.vmdk
-rw - 1 root root 2147221504 2 May 20:45 colossus2_5new - f010.vmdk
-rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f011.vmdk
-rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f012.vmdk
-rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f013.vmdk
-rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f014.vmdk
-rw - 1 root root 2147221504 2 May 20:48 colossus2_5new - f015.vmdk
-rw - 1 root root 2147221504 Feb 11 13:19 colossus2_5new - f016.vmdk
-rw - 1 root root 2147221504 8 Mar 17:17 colossus2_5new - f017.vmdk
-rw - 1 root root 2147221504 Jan 11 23:02 colossus2_5new - f018.vmdk
-rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f019.vmdk
-rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f020.vmdk
-rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f021.vmdk
-rw - 1 root root 2147221504 19 Dec 13:04 colossus2_5new - f022.vmdk
-rw - 1 root root 2147221504 Jan 11 23:04 colossus2_5new - f023.vmdk
-rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f024.vmdk
-rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f025.vmdk
-rw - 1 root root by 6553600 Jan 11 23:05 colossus2_5new - f026.vmdk
-rw - 1 root root 1562 2 May 20:35 colossus2_5new.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f001.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f002.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f003.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f004.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f005.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f006.vmdk
-rw - 1 root root 2147221504 2 May 20:31 colossus2 - f007.vmdk
-rw - 1 root root 1075576832 2 May 20:31 colossus2 - f008.vmdk
-rw - 1 root root 8684 2 May 20:19 colossus2.nvram
-rw - 1 root root 714 2 May 20:31 colossus2.vmdk
-rw - 1 root root 821 2 May 20:31 colossus2.vmsd
drwxrwxrwx 2 root root 4096 2 May 22:13 colossus2.vmsd.lck
-rwxr-xr-x 1 root root 2680 may 2 21:35 colossus2.vmx
-rw - 1 root root 264 Jan 11 22:25 colossus2.vmxf
-rw - r
r1 root root 98347008 1 October 2008 gparted-live - 0.3.9 - 4.ISO-rw - r
r1 root root 1581428 Jan 13 11:53 0.log - vmware-rw - r
r1 root root 771239 19 Dec 12:59 vmware - 1.log-rw - r
r1 root root 76388 Jan 11 23:21 vmware - 2.log-rw - r
r1 root root 10161063 2 May 20:18 vmware.logThe vmx file contains the following:
#! / usr/bin/vmware
. Encoding = 'UTF-8 '.
config.version = '8 '.
virtualHW.version = "7".
floppy0. Present = "FALSE".
MKS. Enable3D = 'TRUE '.
pciBridge0.present = 'TRUE '.
pciBridge4.present = 'TRUE '.
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = '8 '.
pciBridge5.present = 'TRUE '.
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = '8 '.
pciBridge6.present = 'TRUE '.
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = '8 '.
pciBridge7.present = 'TRUE '.
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = '8 '.
vmci0. Present = 'TRUE '.
NVRAM = "colossus2.nvram."
virtualHW.productCompatibility = "hosted".
FT.secondary0.enabled = 'TRUE '.
Tools.Upgrade.Policy = "useGlobal".
powerType.powerOff = 'soft '.
powerType.powerOn = "hard."
powerType.suspend = "hard."
powerType.reset = 'soft '.
displayName = "colossus2."
extendedConfigFile = "colossus2.vmxf".
scsi0. Present = 'TRUE '.
scsi0.sharedBus = 'none '.
scsi0.virtualDev = "free".
memsize = "4096".
scsi0:0. Present = 'TRUE '.
scsi0:0. FileName = "colossus2.vmdk".
IDE1:0. Present = "FALSE".
IDE1:0. FileName = ' / vmachines/colossus2/gparted-live-0.3.9-4.iso '.
IDE1:0. DeviceType = "cdrom-image".
IDE1:0.allowGuestConnectionControl = "FALSE".
ethernet0. Present = 'TRUE '.
ethernet0.allowGuestConnectionControl = "FALSE".
ethernet0. Features = "1".
ethernet0.wakeOnPcktRcv = "FALSE".
ethernet0.networkName = "Bridged".
ethernet0. AddressType = 'generated '.
guestOS = "rhel3.
UUID. Location = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.
UUID. BIOS = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.
VC. UUID = "52 88 6f 19 b2 66 ae 20-28 5 c 6 b 8 b 96 a1 15 6 d.
scsi0:1.present = 'TRUE '.
scsi0:1.filename = "colossus2_2new.vmdk".
scsi0:1.writeThrough = 'TRUE '.
scsi0:2.present = 'TRUE '.
scsi0:2.filename = "colossus2_3new.vmdk".
scsi0:2.writeThrough = 'TRUE '.
scsi0:3.present = 'TRUE '.
scsi0:3.filename = "colossus2_4new.vmdk".
scsi0:3.writeThrough = 'TRUE '.
scsi0:4.present = 'TRUE '.
scsi0:4.filename = "colossus2_5new - 000001.vmdk".
scsi0:4.writeThrough = 'TRUE '.
IDE1:0.startConnected = 'TRUE '.
IDE1:0.clientDevice = "FALSE".
ethernet0.generatedAddress = "00: 0C: 29:b1:a8:e1.
tools.syncTime = "TRUE".
scsi0:0. Redo = «»
scsi0:1.redo = «»
scsi0:2.redo = «»
scsi0:3.redo = «»
scsi0:4.redo = «»
vmotion.checkpointFBSize = "16777216.
pciBridge0.pciSlotNumber = "17".
pciBridge4.pciSlotNumber = "21".
pciBridge5.pciSlotNumber = "22".
pciBridge6.pciSlotNumber = "23".
pciBridge7.pciSlotNumber = "24".
scsi0.pciSlotNumber = "16".
ethernet0.pciSlotNumber = "32".
vmci0.pciSlotNumber = "33".
ethernet0.generatedAddressOffset = '0 '.
vmci0.ID = "-709777183".
sched.mem.pshare.Enable = "FALSE".
mainMem.useNamedFile = "FALSE".
MemTrimRate = '0 '.
MemAllowAutoScaleDown = "FALSE".
Could someone point me to a solution if there is? I have Saturday night here and I would not spend my Sunday to rebuild the server from scratch and have to explain Monday morning I lost 2 months of work for users little by relying on this virtual machine.
Thank you very much in advance!
bugjargal,
In the past if I had a VM that is displayed as invalid when you try to add it to the inventory, I usually just created a new virtual machine based on the original settings & attached the existing VMDK. Not sure how that will work with a virtual machine that has snapshots, but can be worth (nothing to lose)?
Doug.
-
Unable to power on the virtual machine
Hello
I cloned virtual machine within the ESX Server and when I try to turn on the virtual machine, observed following error message and that it cannot go further. Can you let me know the error that I do here.
Kind regards
R
Hello
It is complaing about the SCSI adapter.
> An unexpected error has been received from the ESX host turning on VM vm-8033.
Try changing the type of SCSI LSI Logic SAS adapter or in parallel.
-
Default password Machine virtual XP Mode
I've set up the virtual machine in win 7 Ultimate and put some data. Now when I try to connect it asks password and does not accept any password. Please giveme the default passwordIf you're talking about XP Mode the default password is XPMUser. In general you can not use Windows without a password in Windows Virtual PC that you can with Virtual PC 2007 and before. XPMUser is used only with the XP Mode virtual machine. All other virtual machines requires a user created password. If you have changed the password in XP Mode and forgotten, then you have to start over.
Windows Virtual PC is based on virtual server rather than VPC and all virtual machines need a password. If necessary, uninstall the integration features, start the virtual machine and create a password for the admin user. Restart the virtual machine, and then reinstall the integration features. You will not be able to access a virtual machine created by the user that has no password, while the integration features are installed. Once you have everything right, that a virtual machine will not be asked a password if you are the admin user in Windows 7.
@george1009,.
Everything got? :)
-
I have Win7 Pro SP1 x 64. I downloaded WindowsXPMode_en - us.exe (from Microsoft downloads) and run it. The installation seems to work OK (I've specified a different location for the parent virtual hard disk file). Then, installation happening and I provide the information requested (name of user and password for the XP Mode), updates Windows and OK to the issue of sharing. The installation program then reports the following error:
The disk hard virtual parent is in a saved state. Discard the saved state or stop the virtual machine and try again.
I get the error even if I try manually configure XP Mode (use the Setup Wizard). I downloaded the installer XPMode (3 times) and reinstalled several times, always with the same result. If it helps, I can't locate anywhere .vsv file.
Any idea what's going on?
Original title: XP Mode Setup error
Hi smithnr10,
You must post your question in the TechNet forums because it caters to an audience of it professionals.
To do this, you must consult the link-
http://social.technet.Microsoft.com/forums/en-us/w7itprovirt/threads
Hope this helps!
-
I received the "low disk space error" on a hard drive of the virtual machine dynamic expanding. I have increased my space of virtual hard disk using "My Computer" > manage > storage > "Disk management" and choose "Attach VHD" then resizing to max available (64 GB), and now I can not start the virtual machine. It gives the error: encountered an error when you try to use one of its virtual hard disks. Help?
Hi NatalieFoster,
The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums to get help:
-
Using vmrun to obtain an IP address when you run the virtual machine mode headless fails customers
Operating system: OS X Yosemite 10.10.5
VMware Fusion: Professional Version 8.1.1 (3771013)
When you run a VM guest in headless mode I can't use vmrun to get IP clients. If I eventually bring to the top/start the merger GUI, the command returns the IP address as planned. It is always reproducible.
$ vmrun -T fusion start "path/to/MyVMs.vmx" nogui 2016-06-12T10:55:46.626| ServiceImpl_Opener: PID 11515 ... wait for VM to come up. If the VM has a static IP address I can now ssh into the instance. $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx" Error: The VMware Tools are not running in the virtual machine: "path/to/MyVMs.vmx" $ vmrun -T fusion checkToolsState "path/to/MyVMs.vmx" installed ... Start the VMware GUI and ensure the VM's console window is open $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx" 192.168.100.23
I tested with open-vm-tools and tools VMware packaged with the merger and the behavior is the same. I also spoke with others on the channel of freenode #vmware who have confirmed that the problem exists for users of workstation as well.
Hi danandham,
Welcome in the vmware community. Iyou s really a problem, we try to fix it.
After a command, you can use as a workaround:
vmrun t fusion getGuestIPAddress "path/to/MyVMs.vmx" - wait
See you soon
-
"Unable to connect to MKS" when connecting to the virtual machine shared
Hello
I have a handful of Shared VMs Im trying to access remotely with VMware Workstation Pro 12 (same version on the client and the host - two Windows 10 machines). I am able to connect to the host that shares virtual machines, I can see all the virtual machines shared, open the virtual machine (as in it opens in a tab within the workstation) and virtually no action on the virtual machine including all power options, instant, change settings, etc.. The problem is that if I turn on a virtual computer (or connect to an existing virtual machine under tension, I get the following error and Im not able to access the actual console since it remains as a black screen.
Unable to connect to the MKS: (name of user and password) Login incorrect.
I also noticed that on the client Windows Event Viewer is to launch the following warning events at the same time that the error in the Workstation has been lifted - Im not seeing any on the host are thrown.
I've seen a lot of posts here with users who run the question and he usually ended up being a network problem. I turned off the Windows Firewall on both machines, checked ports 443 and 902 listening on the host and Im in telnet from the client to the host on port 902. I also saw another suggestion for updating the client Windows hosts file to include [host name] [IP address] and [FQDN of the host name] [ip address], but this subject seems not helped either.
Suggestions in this regard does not happen what keeps or where to find more information about the cause?
Thank you!
Post edited by: Tim Graffam
Thank you for using the workstation. I think that this will solve your problem.
Unable to connect to the MKS: (name of user and password) Login incorrect
-
Question: We have configured replication vsphere in our environment and when replication is triggered according to the OFR start us below the questions on the virtual machines that are configured for replication.
Version for esxi: Patch 5.1 level 7
Virtual center of version 5.1
Source of storage - IBM v7000
Destination storage - Hitachi
Questions:
Events of breach RPO
Consolidation for the VM disk failure
Delta abandoned events
Time change events
NTFS error and warning (event ID: 137, 57)
RDP disconnect and ping does matter
Standby error
Volsnap error
Stop the server and offline issue
Install vmtools emits automaticallywell, in this case, we need to disable the standby of the end of the replication.
So that everything in triggering replication does not trigger the snapshot of the suspension.
Then test the if you get these errors.
-
I am the creation of virtual machines using PowerCLI 5.5 on vSphere 5.0; and while the virtual machine is turned off, I am able to mount an ISO on a CD player and change the boot order to boot from the CD-ROM (for another post). I have the flag startConnected set to true, but am not having much luck getting the virtual machine to connect to the CDDrive
$cdObj = $Vm | New-CDDrive - IsoPath $isoPathName - StartConnected: $true
If ($cdObj - no $null)
{
#Power off VM if it is on
$VmState = $Vm.PowerState
If ($VmState - eq "Receptor")
{
$Vm | Stop-Vm-confirm: $false - ea 0
}$BootHardDiskName = 'disk 1 '.
$VmView = get - VM $VmName - Server $serverObj.Name | Get-View
$HardDiskDeviceKey = ($VmView.Config.Hardware.Device |) Where-Object {$_.} DeviceInfo.Label - eq $BootHardDiskName}). Key$BootableHardDisk = new-Object - TypeName VMware.Vim.VirtualMachineBootOptionsBootableDiskDevice - property @{'DeviceKey' = $HardDiskDeviceKey}
$BootableCDRom = new-Object-Type VMware.Vim.VirtualMachineBootOptionsBootableCdromDevice
#Set for CDRom boot order
$BootIso = new-Object VMware.Vim .VirtualMachineConfigSpec - property @ {}
"BootOptions' = New-Object VMware.Vim.VirtualMachineBootOptions - property @ {}
BootOrder = $BootableCDRom
}
}
#Set VM from the start settings at the start of the first CD and forces the display to update (sometimes delayed)
$VmView.ReconfigVM_Task ($BootIso) | out-null
$VmView.UpdateViewData ("Config.BootOptions.BootOrder")
#Power on VM
$Vm | Start-VM-confirm: $false - ea - global 0EV: vmOpsError | out-nullWhen I start the VM, it does start the ISO.
If I go to vCenter, the CD is pointing to the ISO file, but the 'Connected' to change settings option is not checked; I can restart the VM of vCenter and then the VM restarts the ISO, but not in the script.
I even put code to add a lead time of 5 to 10 seconds; I restart the virtual machine twice in the script and I can't CD to connect to start the virtual computer.
Appreciate any suggestions.
Maureen
Have you tried to do a
Game-CDDrive - CD $cdObj - connected - confirm: $false
immediately after the start-VM?
-
black screen, when you open the virtual machine console
Hi guys need help in answering the following questions:
When you open the console of the virtual machine, the connection process is fine, but it stops at a black screen
That's what I use:
(1) Windows 7 x 32
VMRC 2) 5.1.0.20447
(3) Mozilla Firefox 18.0.1
(4) VMware vSphere Client 5.1
(5) Vcloud 5.1.0.810718Here is my log:
13/01/29 10:15:42.100 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:42.101 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, VMRC_EVENT_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}"ID - 2 modes - message mode has 2-3
29-01-2013 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:42.103 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:42.832 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C]}
29-01-2013 10:15:42.833 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:42.845 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379] 10:15:43.901: control of the VM has not been created
29-01-2013 10:15:43.902 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:15:43.909 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.909: control of the VM has not been created
29-01-2013 10:15:43.923 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.923: control of the VM has not been created
29-01-2013 10:15:43.925 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.925: control of the VM has not been created
29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:44.275 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, VMRC_EVENT_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}"ID - 2 modes - message mode has 2-3
29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:44.276 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:44.958 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD]}
29-01-2013 10:15:44.959 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:44.970 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 10:15:46.770 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:46.770 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, VMRC_EVENT_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance ID 'vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}' - mode 4 - message mode has 2-3
29-01-2013 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:46.772 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/ScriptableObject.cc:321]: ID of property not found: onMessage
29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/VmrcPlugin.cc:2548]: onMessage Manager call failed
29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:47.380 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996]}
29-01-2013 10:15:47.381 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:47.388 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 10:17:20.197 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:13.788 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:13.792 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:15.303 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:59:15.308 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:59:15.324 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.324: control of the VM has not been created
29-01-2013 10:59:15.326 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.326: control of the VM has not been created
29-01-2013 10:59:33.283 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:33.284: control of the VM has not been created
29-01-2013 10:59:33.540 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:59:33.540 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3Windows 7 x 32
That's kinda our old friend is back.
Two checklists
1. check the version of the VM VGA driver, if that's the case, you must update the WDDM driver display driver.
2. make sure that you use HW 7 and more.
More info here
-
When a snapshot is complete, so I can start to make changes to the virtual machine?
When I take a snapshot in merge, a progress bar appears in the window of virtual computer, then disappears in a few seconds.
But a picture of a clock also appears on the Fusion icon in the dock. Only the clock takes a minute or two to disappear.
What process is the clock? What is the take a complete snapshot? When the progress bar disappears, or when the clock disappears?
Can I safely begin to make changes to the virtual machine, I want to be able to restore, immediately after the progress bar disappears?
Or, it is more prudent to wait to make changes until the clock disappears?
Thank you
(The progress bar and the clock appear in my Fusion 3 that I use always happy... I don't know what appears in more recent versions).
While the stopwatch turns, Fusion is busy writing the snapshot to disk, so the performance of your comments and your host could be reduced.
As long as the performance isn't an obstacle, you can continue to use the virtual machine while the snapshot is taken. Merger will ensure that the snapshot includes the exact state of the virtual machine at the moment, you started the snapshot: nothing of what you are doing inside the guest, while the snapshot is in progress does not affect the State of the socket.
See you soon,.
--
Darius
-
Hi friends,
Will the virtual machines in the space are automatically deleted when the protected group are removed?
Thank you.
Hello
When you choose to delete the Protection Group, first virtual machines are unprotected and placeholders are deleted.
Michael.
-
AutoSave is slow when the virtual machine is not active
When I actively use a Windows 2000 Server VM and AutoSave is triggered, it's very fast. But if I did not use the virtual machine for a while, it takes some minutes and minutes. If I'm trying to go back to the virtual machine, I have to wait indefinitely for the automatic backup complete.
Is it possible to set the priority for the automatic backup feature?
Are you talking about VMware Fusion AutoProtect feature, or something else (perhaps in the comments)? Offhand, it seems that when you have not used within a certain time, Fusion got paged out. Taking the automatic snapshot requires paging backward, which can take some time. You can test this theory by looking at activity monitor and looking at the pageout/publication numbers when you see an automatic preview slow.
Pageouts and pageins are controlled by OS X and not something we have control over. Adding RAM to the Mac, it is more likely merger will stay in memory and avoid this situation.
-
is it possible to access the virtual machine when the network is down...
Hello. He... IAM wondering is it possible that we can access the virtual machine when the network is down... (Because of power outages or when the fluctuations...) ................?
Is it possible that I can configure my Virtual Machine...?
Thank you and best regards...
Indianmale...
Hello
Not really...
For an environment hosted... If you can access the console of the host, you can always access the console of the virtual machine regardless of the State of the network outside of the console. VMware Workstation, Fusion and server all fall into this category.
For ESXi/ESX... you need a host outside to access the console of the virtual machine. ESX and ESXi not displayed graphics or VMs of their consoles and management devices. So, you need an external machine that can run the vSphere Client or access to the virtual machine via RDP, VNC according to Guest OS involved or SSH.
Best regards
Edward L. Haletky
VMware communities user moderator, VMware vExpert 2009, Analyst of DABCC
====
Author of the books ' VMware vSphere (TM) and Virtual Infrastructure Security: ESX security and virtual environment ' available for pre-order now
"VMWare ESX in the Enterprise Server: planning and securing virtualization servers, Copyright 2008 Pearson Education."
SearchVMware Pro| Blue gears. Top virtualization security links| Security Round Table Podcast virtualization
Maybe you are looking for
-
The sound died today on my iMac. iTunes opens by itself, and I can't listen to music if I try to play anything. I checked mute and in system preferences, he has not yet shown built-in speakers, just the headphones and it kept flashing like a neon s
-
The drop down menus work intermittently; all add-ons are disabled.
When I run the cursor over a menu item; File, Edit, history, etc., the drop down menu does not decrease. If I click on the menus, drop down menus will appear and then disappear. If I continue to do this for several seconds, the menu will be displayed
-
is the 3rd generation apple TV speaker bluetooth support
I was wondering if apple tv 3rd generation supports bluetooth speakers?
-
Name of access to case / battery inside the case using VI scripts
Hello everyone. I have a script that finds all instances of a specific under vi. All instances of this subroutine VI will be contained in a box structure. Using VI scripts, I want to be able to cross back and determine the name of the case that the s
-
high definition audio does not work - error code 10
Current title: idt high definition autio does not work My idt high definition autio does not work it gives me a code 10 how to fix