hello
i'am using :
on my hosting machine :
VM WMARE : VMWARE WORKSTATION 12.5.2
COMPUTER : DELL PRECISION 7510
OS VMWARE: ELEMENTARY OS
VIRTUAL MACHINE : WINDOWS 7 64bits Pro
oftware working perfectly but i have got a problem with resolution....
I would like to use the virtual machine en 1920x1080
When i choose it in Windows 7 64bits virtual machine the screen size is reduiced but never adjust in fullscreen....
I have try a lot of test i don't managed it
someone as an idea ?
Thanks
The only solution i have found it's to use my elementary os in 1920x1080 too ????
Hello, I am new to this community and apologies if this is not the place for these type of inquiries. I have been trying to use vCenter Server Appliance to save costs from having to deploy a windows server to host vCenter. I quickly noticed many drawbacks vCSA has from vCenter. I was able to work though them and deploy several VMs.
Environment: ESXi 6.5.0 server. Installed vCSA on top of ESXi server. The state: Normal (not connected to any vCenter Server).
From here I am able to build VMs and can manage them remotely on port 902 using VMRC.
I have another server (Ubuntu 14.04), not a VM in ESXi, but in same subdomain as VMs, that I need to be able to issue vmrun commands from. It is running VM Workstation 12. Im getting the following error:
Unable to connect to host.
Error: The specified service provider was not found
vmrun -T esx -h https://<internal IP>/sdk -u <user> -p "<xxx>" list
ports tried: 443, 9443, 8333, 5480, 7343, 902, 943, 8089
Also tried -h with no https, port, or /sdk
Is this a limitation of using vCSA?
A colleague was moving a VM from one datastore to another datastore. Somehow in this process something has gone wrong.
All files are there except the snapshot information .vmsd file which i recreated. I checked the logs and can see that there are 2 snapshot delta files which i have.
Without the snapshots the machine starts normally but i need to revert to the latest snapshot.
After recreating the config vmdk files and snapshot (chain) info the snapshots show up in ESXI but reverting to a snapshot gives the following error
2016-12-27T09:38:09.269Z [33BC1B70 verbose 'Vmsvc.vm:/vmfs/volumes/58621528-51cb7ea2-6b52-d89d6729d8dc/Development new/Development new.vmx'] Power On message: Input/output error
--> Cannot open the disk '/vmfs/volumes/58621528-51cb7ea2-6b52-d89d6729d8dc/Development new/Development new-000002.vmdk' or one of the snapshot disks it depends on.
File structure looks like this
Developmentnew-000001-delta.vmdk 2.4G
Developmentnew-000001.vmdk 352
Developmentnew-000002-delta.vmdk 26.1G
Developmentnew-000002.vmdk 339
Developmentnew-flat.vmdk 64.0G
Developmentnew.nvram 8.5K
Developmentnew.vmdk 476
Developmentnew.vmsd 1.5K
Developmentnew.vmx 2.9K
Developmentnew.vmxf 269
If i look at the binary delta files they just look normally and also ends normally with zero's.
Snapshot 001 Binary headers
COWD € w)¥
Snapshot 002 Binary headers
COWD € Ë<D
Things i tried to recover the snapshot
- Cloning (using vmkfstools -i) the snapshot returns same Input/output error on both snapshots.
- Repair/fix using vmkfstools returns no errors
- Adding another snapshot and revert returns same errors (cloning still not possible)
- Deleting snapshot also returns error
- Deleting all snapshots needs snapshot consolidation but this fails.
- Using VMWare Workstation to start snapshot. But VMWare crashes with memory issues.
- Using vmware-vdiskmanager to repair returns the following
vmware-vdiskmanager.exe -R "g:\Dev3\Development new-000002.vmdk"
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
DISKLIB-LEGCHK: Ignoring holes in extent. --Ok
No errors were found on the virtual disk, 'g:\Dev3\Development new-000002.vmdk'.
vmware-vdiskmanager.exe -R "g:\Dev3\Development new-000001.vmdk"
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
DISKLIB-LEGCHK: Ignoring holes in extent. --Ok
The virtual disk, 'g:\Dev3\Development new-000001.vmdk', is corrupted and cannot be repaired.
vmware-vdiskmanager.exe -R "g:\Dev3\Development new.vmdk"
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
No errors were found on the virtual disk, 'g:\Dev3\Development new.vmdk'.
- Using DiskInternals VmfsRecovery which is able to read the snapshot partially but no path information.
- Trying to recover lost data on the ESXI machine filesystem but failed as there was no diskspace already on it.
- Using mount tools to mount the snapshot fails with read error.
Following is situation after adding more snapshots but 1 and 2 are still the same.
vmkfstools -t0 -v10 "Development new-000004.vmdk"
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000004-delta.vmdk" : open successful (14) size = 135168, hd = 499227139. Type 8
DISKLIB-DSCPTR: Opened [0]: "Development new-000004-delta.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000004.vmdk' (0xe): vmfsSparse, 134217728 sectors / 64 GB.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000002-delta.vmdk" : open successful (14) size = 28068417536, hd = 491887108. Type 8
DISKLIB-DSCPTR: Opened [0]: "Development new-000002-delta.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000002.vmdk' (0xe): vmfsSparse, 134217728 sectors / 64 GB.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000001-delta.vmdk" : open successful (14) size = 2599952384, hd = 646945285. Type 8
DISKLIB-DSCPTR: Opened [0]: "Development new-000001-delta.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000001.vmdk' (0xe): vmfsSparse, 134217728 sectors / 64 GB.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-flat.vmdk" : open successful (14) size = 68719476736, hd = 671259142. Type 3
DISKLIB-DSCPTR: Opened [0]: "Development new-flat.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new.vmdk' (0xe): vmfs, 134217728 sectors / 64 GB.
DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 4, numSubChains = 1
DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 671259142, extentType = 2
DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 646945285, extentType = 0
DISKLIB-CHAINESX : ChainESXOpenSubChain:(2) fid = 491887108, extentType = 0
DISKLIB-CHAINESX : ChainESXOpenSubChain:(3) fid = 499227139, extentType = 0
DISKLIB-CHAINESX : ChainESXOpenSubChainNode: can't create deltadisks node 48423dbe-Development new-000004-delta.vmdk failed with error Input/output error (0xbad000a, I/O error)
DISKLIB-CHAIN : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000004.vmdk" : failed to open (Input/output error).
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000004-delta.vmdk" : closed.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000002-delta.vmdk" : closed.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-000001-delta.vmdk" : closed.
DISKLIB-VMFS : "/vmfs/volumes/574dbe3f-e8ed28ab-bab5-a02bb8317488/Development/Development new-flat.vmdk" : closed.
DISKLIB-LIB : Failed to open 'Development new-000004.vmdk' with flags 0xe Input/output error (327689).
Failed to open virtual disk: Input/output error 327689
So as you can see i tried many things to recover/repair the snapshota but I'm out of options. Are there any other things i can try?
Or can i conclude that the moving operation corrupted the binary data in the process.
Hi Ilian,
Just a quick followup, I loaded up a vra 7.1 appliance and tested my original script and your right; the original script runs fine. So I will just run that workflow from the 7.1 appliance until the patch comes out. I'll keep an eye out and test the patch when it's out and then update this discussion thread.
Thanks again for you quick response...
RS
Absolutely a life saver
Searched and deleted all ***.lck files, booted up the guest machine, worked like a charm. Thanks.
André,
Thank you.
Thanks so much, using firefox 50.0.2 and Chrome 55.0.2883.87 I was able to upload files larger than 4gb to my datastore.
File Upload and Download Limits – IEInternals verifies the IE limit.
Thank you so much A.P. I thought I had some major issue here, you saved me!
Happy New Year!
John
Es geht nicht um das Kopieren einer VM von einem auf einen anderen Rechner. - Es geht einfach nur um eine Virtuelle Maschine, die die Spiegelung des Contents eines anderen Rechners enthält. - Aber diese eine, nicht kopierte und den Content eines anderen Rechners enthaltende VM war eine Weile lang ganz einfach zu öffnen, dann schon einmal nicht, dann wieder doch und jetzt zum zweitenmal wieder nicht. - Die Datei .vmx gibt es so im Verzeichnis nicht, sondern nur eine Datei .vmxf. - Kann man den Buchstaben f in der Dateierweiterung einfach löschen. Und wie ist der Buchstabe f da überhaupt hingekommen?
harry92
Dear all
Hi
during install VCSA 6.5 this error appear :
Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 2018, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1479, in configureSTS self.startSTSService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1141, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 88, in startService return service_start(svc_name, wait_time) File "/usr/lib/vmware/site-packages/cis/utils.py", line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { "resolution": null, "detail": [ { "args": [ "vmware-stsd" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-stsd'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null } Resolution This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.
what is my problem ?
BR
Babak
I need to simulate a server with 2 NICs and a desktop computer enviroment just as you can see on this picture
In the next screens you can also see some of the configuration settings of my Ubuntu virtual box
https://www.dropbox.com/s/md2dgaeabwd0pye/UbuntuFT2017.1-2016-12-31-11-17-03.png?dl=0
This happens when you run the VMRC installer on a system with Workstation/Player already installed. We will improve this in a future release, but at the moment you have two options:
I have tried many times to resolve the issues with upgrading the vCenter VSCA from the command line using the mounted "VMware-vCenter-Server-Appliance-6.0.0.20100-4632154-patch-FP.iso". I keep getting these errors on this system. See below...
Does anyone have any possible solutions to get past this?
Thanks in advance.
Command> software-packages install --iso
[2016-12-31T19:45:19.366] : Staging software update packages from ISO
[2016-12-31T19:45:19.366] : ISO mounted successfully
[2016-12-31 19:45:19,946] : Running pre-stage script.....
[2016-12-31T19:45:20.366] : Verifying staging area
[2016-12-31T19:45:20.366] : Staging area does not have sufficient space
[2016-12-31T19:45:20.366] : Installation process failed
ET-vCenter01:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 11G 9.3G 950M 91% /
udev 4.0G 164K 4.0G 1% /dev
tmpfs 4.0G 36K 4.0G 1% /dev/shm
/dev/sda1 128M 38M 84M 31% /boot
/dev/mapper/core_vg-core 25G 173M 24G 1% /storage/core
/dev/mapper/log_vg-log 15G 7.1G 7.0G 51% /storage/log
/dev/mapper/db_vg-db 9.9G 216M 9.2G 3% /storage/db
/dev/mapper/dblog_vg-dblog 5.0G 187M 4.5G 4% /storage/dblog
/dev/mapper/seat_vg-seat 9.9G 300M 9.1G 4% /storage/seat
/dev/mapper/netdump_vg-netdump 1001M 18M 932M 2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy 9.9G 151M 9.2G 2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc 5.0G 161M 4.6G 4% /storage/invsvc
/dev/sr0 1.6G 1.6G 0 100% /mnt/iso-contents
Just an hour later i finally had success.
I was able to recover all data using ufs explorer by attaching the snapshot 02 to the main flat file.
So my problem is solved. I think the snapshot 01 has been corrupted somehow since all data is still available with snapshot 02 and the flat file.
But still i think its a bit strange none of the tools worked except an exteral recovery tool.
I have the same issue, IE and Edge don't work, Firefox does. CIP service is running fine. Plugin does not show up in manage add-ons. Can't find manage add-ons in Edge.
I am attaching to my original posting the VMware-ui-7560.log.
I can see some errors there, but not sure what they mean.
If someone knows what other logs can be useful, please let me know.
I figured this out. I re downloaded the cert, re-imported it and it works.
I did not force quit VMWare Fusion 6 and my MacBook Air rebooted and is trying to restart the Applications that were opened.
Now everything is stalled with a black screen and I canot Force Quite VMWare Fusion 6 nor switch to another window/Application.
Booting in safe mode did not help.
I do not know what tot do to fix this problem, any suggestions?
I am also receiving this same error using ESXi 6.5. Should we be using 6.0 for fresh installs until 6.5 is more stable?
Unhandled exception (9)
Cause: TypeError: Cannot set property 'open' of undefined
Version: 1.8.0
Build: 4516221
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Exception stack:
TypeError: Cannot set property 'open' of undefined
at Object.fn (https://192.168.0.28/ui/scripts/main.js:399:29901)
at k.$digest (https://192.168.0.28/ui/scripts/main.js:265:15315)
at k.$apply (https://192.168.0.28/ui/scripts/main.js:265:16759)
at HTMLAnchorElement.<anonymous> (https://192.168.0.28/ui/scripts/main.js:366:31316)
at HTMLAnchorElement.dispatch (https://192.168.0.28/ui/scripts/main.js:262:14464)
at HTMLAnchorElement.r.handle (https://192.168.0.28/ui/scripts/main.js:262:11251)
good catch
the username is admin, i appened that at the key of key
but no luck
$SSHKey = "-----BEGIN SSH KEY-----
ssh-rsa ....E6AD8F6STpoYXVOx... admin
-----END SSH KEY-----"
Import-HPiLOSSHKey -DisableCertificateAuthentication -Server "ixx" -Username "admin" -Password "xx" -SSHKey $SSHKey