- RSS Channel Showcase 1128348
- RSS Channel Showcase 1071630
- RSS Channel Showcase 2317584
- RSS Channel Showcase 7941830
Articles on this Page
- 06/24/17--03:37: _Re: VMWare workstat...
- 06/24/17--03:49: _Re: Slow VM Windows...
- 06/24/17--03:56: _Re: Re-Add VMFS Dat...
- 06/24/17--04:01: _Re: VMware Workstat...
- 06/24/17--04:17: _Re: Made my VM part...
- 06/24/17--04:22: _Re: Cannot open dis...
- 06/24/17--04:24: _Re: Problem to moun...
- 06/24/17--04:45: _Issue in creating a...
- 06/24/17--04:56: _部署vRealize Automati...
- 06/24/17--05:13: _Re: VM Workstation ...
- 06/23/17--04:06: _"Locked master refu...
- 06/24/17--05:36: _Re: "Locked master ...
- 06/24/17--05:50: _Re: VMWare Workstat...
- 06/24/17--06:02: _Re: Made my VM part...
- 06/24/17--06:07: _Re: Issue in creati...
- 06/24/17--06:13: _Re: "Not all hosts ...
- 06/24/17--06:17: _Re: Android/3D="Loc...
- 06/24/17--06:46: _Re: Android/3D="Loc...
- 06/24/17--06:55: _vCenter snmp trap v...
- 06/24/17--07:03: _Having trouble with...
- 06/24/17--03:37: Re: VMWare workstation monitor.suspend_on_triplefault fails
- 06/24/17--03:49: Re: Slow VM Windows 2012 with VM ESX Nested
- 06/24/17--04:17: Re: Made my VM partition too big, please help
- 06/24/17--04:22: Re: Cannot open disk: *.vmdk
- 06/24/17--04:24: Re: Problem to mount a USB stick
- 06/24/17--04:56: 部署vRealize Automation VRM Agen 报错
- 06/24/17--05:13: Re: VM Workstation 12.5.6 GUI freezing/stuck when Client Power ON
- 06/23/17--04:06: "Locked master refused legacy surface reference"
- 06/24/17--05:36: Re: "Locked master refused legacy surface reference"
- 06/24/17--06:02: Re: Made my VM partition too big, please help
- 06/24/17--06:17: Re: Android/3D="Locked master refused legacy surface reference"
- 06/24/17--06:46: Re: Android/3D="Locked master refused legacy surface reference"
- 06/24/17--06:55: vCenter snmp trap version ? ?
- 06/24/17--07:03: Having trouble with police scanner Serial to USB cable on VM
That assertion is configured to fail whenever the virtual machine's CPU encounters a triple-fault. Our assumption is that if you are running with debugging enabled, a triple-fault is an event that you're likely to want to capture and debug, so it's wired up to trigger a virtual machine monitor panic by means of raising an assertion failure. It won't do this when the VM is configured with Gather debugging information set to anything other than Full.
With monitor.suspend_on_triplefault set, this should produce a pair of files named debug.guest (which is a trimmed-down .vmss file, not suitable for restoring the state of the whole VM, but containing enough CPU state to enable debugging) and debug.vmem (containing the state of the VM's memory). Are those files not being produced? Those two files should be suitable for use with vmss2core, which should be able to produce regular ELF corefiles from the VM's state at the time of the triple-fault.
The tweak you made is not enough.
Required reading: Running Nested VMs
> I'll get in touch with VMWare support on monday.
Good luck with that.
.... so I expect your call monday afternoon
Please note that more recent versions of VMware Workstation already include support for newer kernels and don't need to be patched in this way. I recommend upgrading to the latest version to ensure you've got the latest security and stability fixes in addition to compatibility with new Linux kernels.
So you already resized the partitions from inside the guest ?
Do you have one or two partitions inside the guest ?
Anyway - create new vmdk just large enough to contain the resized partitions.
Do not format the new vmdk.
Boot into a Linux-LiveCD.
You should now find one disk /dev/sda with the original installation and another blank disk /dev/sdb.
Check the size required for the partitions in the original. Get the size in Mbs and add some space at the end so that you have a value that is devidable by 8. Assume this is X.
Then launch a terminal as root and run the command
dd if=/dev/sda of=/dev/sdb bs=1M count=X conv=notrunc
This will take a while.
Once it is done reboot the Linux LiveCD and launch gparted or gdisk.
Both have a tool to fix the partitiontable (required if your VMs used a GPT-table.
Once that is done - reconfigure the VM so that the newly created vmdk is the only one connected.
Now boot into Windows again - if everything worked you can then delete the original large vmdk.
Maybe your VM just uses an absolute path to the vmdk ?
To check - open the bundle to view the actual files and then open the vmx-file with a texteditor.
Check if the referenced vmdk-files exist in the correct location.
If not - just provide the correct path and filename.
Attach the vmware.log to your next reply. It may tell you what is wrong.
I have setup a lab environment in my machine with VMware workstation. In the workstation i have created a domain controller , ESXi host 6.0 , vcenter server applicance and mapped the ESXI host to the VCSA server. But whenever i am trying to deploy virtual machine in the esxi host ( through vcenter or directly through the esxi host) the host goes to unresponsive state.
Could someone help me in resolving this issue.
部署vRealize Automation，添加代理时，日志提示：This exception was caught: 执行该操作的权限被拒绝,如何解决，已经授权了，还是提示这个……
Issue has not reappear since I uninstalled the Bitdefender Anti-Virus (2017),
hence I am going to mark it as the cause of the issue.
Thanks for the help.
after enabling 3d acceleration, guest kernel seems to fail some time after boot. dmesg says "Locked master refused legacy surface reference", or "Could not add a reference to a surface" depends on which host it is running
i5-2430M, Raideon 6600M + HD 3000, Windows 10: "Locked master refused legacy surface reference"
"Could not add a reference to a surface"
GT 730 or GTX 1050 Ti, Centos 7 or Windows 10: "Could not add a reference to a surface"
android-x86 x86_64 6.0 release r3.
i really need your help to nail this problem down. any suggestion where i should look into?
updated my first post thanks to your suggestion
> Are you sure that Android supports 3d acceleration at all ?
> Did it work without before ?
i didn't have old version tested, can't find an older version to download last time i check. the author claim to have fixed in r3
> It would help to see the vmware.log from last failed boot.
it didn't fail to boot but it's rendering problem, flicker.
Workstation 12.0.0 is from 2015
Workstation 12.5.7 is from last Thursday, June 22, 2017
Without even knowing what version you even tried to install beyond version "12", trying to help is guess work.
Shrinking the partition within the virtual disk has not the desired effect, in fact it means that the "clean up" function within vmware can no longer reclaim disk space as it can only reclaim disk space from supported file systems such as NTFS.
So the first step would be to undo that partition resize.
Then you are correct in that you cannot resize the virtual disk in Fusion to something smaller. There are ways to do that via other means, but perhaps it isn't needed.
Since your writing suggests that you are short on disk space, my first recommendation would be to make a backup to an external disk of the VM with the VM shut down (not suspended) before trying to reclaim disk space.
Then after the backup, with the VM shut down still
Go to the Fusion menu -> Virtual Machine -> Settings -> General
There's a button there "Clean up Virtual Machine"
This allows you to reclaim back any space used within the virtual machine of files that have been deleted and gives that space back to the host system.
Also note that if you have snapshots open or are using the auto protect feature that those also can use quite a bit of disk space at the host system and that the clean up works most effective (as in reclaims most disk space) with all snapshots committed and auto protect set to off.
Any disk space not used should then be reclaimed and give just as much space back to the host as a fully resized virtual disk could possibly do.
The only disadvantage over a resized smaller virtual disk is that it can grow out of proportions again.
Hope this helps,
I was able to resolve it. Seems the host was not hung. VM machine was showing a message as "
When powering on a nested virtual machine, vSphere Client reports the warning: Running VMware ESX in a virtual machine will result in degraded performance. Do you want to continue?" and after editing the vmx file of the machine to set it as true. It worked.
For me, One of the host in the cluster is in Not Responding state. As soon as i remove the host (I can afford to do that since its test lab) from the vCenter, I can select the Cluster and continue with the pool creation.
Android is not a supported guest OS and as such I would be surprised that it supports 3D acceleration as provided by VMware drivers.
In order for 3D acceleration to even work you have to install the specific VMware drivers that are supplied by installing VMware Tools.
AFAIK there is no such VMware Tools package for android. I'm happy to be wrong on that though, perhaps the android developers added open-vmware-tools.
FWIW, a year or so ago I also tried to run android on vmware and my experiences where lockups all the time so I gave up on it.
The first thing to check is what kernel modules have been loaded for graphics support.
Attaching a vmware.log file to your reply here might also help in seeing what it is actually trying to do.
Apologies, you already attached logs.
Read the logs and it is indeed using the vmwgfx driver (from 2015, but still), not seeing anything wrong in the logs though.
From the dmesg.log, it looks like this release of Android x86 is using vmwgfx but it is an old version
[ 2.506457] [drm] Initialized vmwgfx 2.9.0 20150810 for 0000:00:0f.0 on minor 0
FWIW, there is a patch related to that piece of code throws that error.
I don't even pretend to know what it all means. It may or may not have anything to do with this problem. The problem might be even with the Android port itself and not necessarily with the vmwgfx driver.
I know nothing about Android x86 (let alone the numerous sweet flavoured Androids) but AFAIK, the Accelerated 3D graphics will only help in Linux guests, if the application or OS itself in the guest VM is using OpenGL.
How can I configure my vCenter server 6.0 to send snmp trap with version v2c ?
I do the pcap when vCenter send alarm. The snmp trap send with snmp version version-1.
Dose vCenter server 6.0 support this?
I am running an ESXI on a desktop computer with 2 VMs. My windows 10 VM is used for recording and monitoring my 2 police scanners using proscan software. I am having trouble getting the VM to recognize my serial to USB cables. The software will usually see them and show the (virtual) com ports as available, but not properly detect my scanner or say the baud rate is incorrect. Does anyone know some other things I can try to get these to work? I am also having an issue getting a USB sound card to be detected. not sure if that is also related.
Thanks for the help!