Hello,
i've tried the driver, attached here in ESXi 6.7 U1, card was recognized but i was not able to get vmnic up and running.
However, i've contacted Aquantia directly
They have "official" test driver here:
Releases · Aquantia/AQtion-esxi · GitHub
I've already install the driver, everything works very well so far.
Hope this helps.
Greetings!
I have 2 Windows 7 x64 Virtual Machines, and after upgrading to VMware Workstation Pro 15.0.4, I got this error after opening this 2 Windows 7 machines:
Failed to get exclusive lock on the configuration file. Another VMware process might be running using this configuration file.
After closing this error, I get the "Internal error" and the VM crashes. When I look to my VMware shortcut on my taskbar and It says that 2 VMs are running. When I click to Power Off, Suspend or Pause the VMs, it doesn't change anything. Also, when I open VMware, this VMs aren't running in background.
I opened taskmgr and killed the VMX processes, it didn't work either. I don't know if my other VMs have the same problem (Windows 10, Longhorn, Whistler, Whistler, 98, Neptune, MacOS 10.14 and Android 8), but I don't rescue opening them. If you want to know, here are the symptoms:
Symptoms
*Virtual Machines are always running in the background
*Can't open Virtual Machines
*Don't react to shutdown, pause or suspend
*Can't be killed using taskkill or taskmgr
If you know what's the problem, Please type in comment section to help me or other users.
Do you have any error when VM crashes?
Because excluding 2 vms, other vms are running well on my Windows 10 1903 Insider Preview
Search for "Run" and type "gpedit.msc"
Go to Local Computer Policy - Computer Configuration - Administrative Templates - System - Device Guard - Turn on Virtualization
Double click that settings and select "Disable" .
Go to Control Panel - Uninstall a Program - Turn Windows features on or off - (uncheck/turn off) Hyper-V.
Click OK
Select Do not restart.
Start cmd as admin and type this
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set hypervisorlaunchtype off
Restart your OS
If it didn't work, go to Turn Off CG/DG for more information
Try turning off "Accelerate 3D graphics"
Sure that's a very old thread, but I've hit same problem in 2019 with ESXi 6.5. Increased RAID array with datastore, then increased the partition with partedUtil, and got stuck with "vmkfstools --growfs" reporting "No such file or directory". I've tried passing device name (disk:partition) with and without quotes, tried using different path - /vmfs/devices/disks/... and /dev/disks/..., rebooted host, dismounted and resignatured the datastore - all to no success. GUI wasn't helpful either, it was showing an empty list of devices when I was trying to increase my single existing datastre extent. And then finally what worked was using a relative partition name, without path!
cd /dev/disks
vmkfstools --growfs naa....:1 naa...:1
(My disk name starts from "naa...") And it magically succeeded. No idea why - maybe vmkfstools has some bug in device path buffer allocation or parsing, or something else.
Thanks!
Thanks
Hola que tal, es este.....
Antes de formatearlo lo tenia instalado..... no se porque ahora no puedo...
Me da error cualquier versión.
Saludos.
What I think the OP is saying, is they, like myself, click on the link above and click on the blue register button, we are brought to a screen saying:
Dear user, the web content you have requested is not available.
We cannot register for the product because the page is dead or something, and cannot therefore get a key.
Additionally, I have tried twice to contact sales/support via their web form, both times getting messages stating it was successfully sent, but haven't heard anything. It doesn't even send an autoreply to your mail to indicate they received it. Like the user above, time, as they say is ticking. I too am a home user, dabbling in some server operating systems. In my case (which makes me worry more) I'm running ESXi 6.0 (not 6.7) because that is what the version created for my server (Dell Poweredge R710) needed to run. Hopefully someone will come along and fix the registration portion of the site, or be able to help us here in the forum.
I have upgraded from VMWare 12. I installed VMWARE workstation Player 15 on Windows 10. I clicked on the ICON, and it starts to load. It fails with:
"Host supports AMD-V, but AMD-V is disabled".
Player 12 was running Windows XP Pro.as an operating system.
As I cannot run VMWare 15 how can I enable AMD-V setting?
Hello,
The possible solution was reported in another thread:
ESXi 6.7u1 RMRR overlaps system memory
The short answer is that it seems that you need to update BIOS to the latest version or disable Intel VT for directed I/O in the current BIOS version.
I'm trying to create an error handler workflow and noticed an odd behavior I cannot understand. In the following example I'm simplifying my workflow as much as possible to reproduce my issue.
I'll show 2 workflows. The first one, called buggy, is the main workflow throwing an error:
I use the Default error handler with a workflow called handle error to react on errors.
Here is how handle error looks like:
This flow is also throwing an error, and I try to handle it with another Default error handler. But this is not working, if I run buggy, I end up in an infinite loop:
[2019-04-06 22:33:12.314] [E] Error in (Workflow:buggy / Throw error (item1)#0) bug1
[2019-04-06 22:33:12.375] [I] Don't worry, I'll take care of bug1
[2019-04-06 22:33:12.392] [E] Error in (Workflow:handle error / Oops (item2)#0) Oops
[2019-04-06 22:33:12.429] [I] Don't worry, I'll take care of Oops
[2019-04-06 22:33:12.444] [E] Error in (Workflow:handle error / Oops (item2)#0) Oops
[2019-04-06 22:33:12.482] [I] Don't worry, I'll take care of Oops
[2019-04-06 22:33:12.501] [E] Error in (Workflow:handle error / Oops (item2)#0) Oops
[2019-04-06 22:33:12.547] [I] Don't worry, I'll take care of Oops
[2019-04-06 22:33:12.564] [E] Error in (Workflow:handle error / Oops (item2)#0) Oops
[2019-04-06 22:33:12.598] [I] Don't worry, I'll take care of Oops
This was the only way to make handle error work:
And the resulting (desired) logs:
[2019-04-06 22:53:55.027] [E] Error in (Workflow:buggy / Throw error (item1)#0) bug1
[2019-04-06 22:53:55.076] [I] Don't worry, I'll take care of bug1
[2019-04-06 22:53:55.125] [I] Ignoring Oops
So the goal is catch errors in the handle error flow itself. My real handle error flow is much more complex and I did not like this workaround of setting the error path of each step. I prefer a nested Default error handler but I could not make it behave.
Any ideas?
Hi,
I tried to deploy Skyline but after request access and register the system search an entitlement but cannot fin it. We have an EA with production support level so I think that we are entitled to use Skylane after reading faqs.
I tried to setup also via my.vmware.com instead cloud.vmware.com but at the end it redirects me to the same portal.
Could anyone help me to associate the EA entlement to my account?.
Best Regards,
Iker.
Hi Thanks
I am having to wait for each vm to shutdown one by one. How can i change it to do a shutdown-vmguest all at same time?
Hi,
I was able to make Solidworks use hardware OpenGL on VMWare 11.0. It took me a while and I kept coming across this post so hopefully, this will save someone some time.
To recap, Solidworks must "recognize" a graphics card to enable OpenGL support for it. If it doesn't, the option "Use Software OpenGL" in Solidworks settings is checked and grayed out.
Apparently, they have workarounds that can be enabled to "force" Solidworks to recognize specific adapters as OpenGL capable.
Open regedit.exe and navigate to
HKEY_CURRENT_USER\Software\SolidWorks\SOLIDWORKS 2019\Performance\Graphics\Hardware\VMware, Inc.
There should be a DWORD entry called Workarounds. Mine was set to 0x10. Change it to 0x09 and start Solidworks. The option "Use Software OpenGL" should be unchecked and not grayed out.
I have no idea what do these values mean (chances are it's a bit-mapped value and one bit enables the opengl). feel free to experiment with different values if you'd like.
Since there is no RunAsync option for the Stop-VMGuest cmdlet, you could go for parallelism.
Stop 1 or more VMs in a background job, and launch multiple of those background jobs.
I am testing VMWare Workstation 15 on Ubuntu Desktop 18.04 (64bit)
I startup a VM using the commandline:
vmware -t -X -q <path to vm>/<titel>.vmx
I am getting numerous errors (in terminal session).
Some of them I could erradicate using:
sudo apt install libaio1
sudo apt install libgtkmm-2.4-1v5
sudo apt install libgtkmm-3.0-1v5
The one that keeps repeating during running:
(vmware:7098): Gtk-WARNING **: 20:03:20.474: ../../../../gtk/gtkwidget.c:13195: widget class 'gtkmm__CustomObject_ui_TabManagerProxy' has no property named 'ythickness'
This error comes up as soon as I click on the the pop-out bar at the top, when the VM is in full screen modus. The VM is running fine though.
Is there a solution for this error?
Vmware Workstation 15 Pro (tested with two versions)
host OS : 4.18.0-16-generic
ubuntu-18.04.2-desktop-amd64.iso ; with all latest updates
VMware-Workstation-Full-15.0.3-12422535.x86_64.bundle
VMware-Workstation-Full-15.0.4-12990004.x86_64.bundle
VM: Windows 10
No solution? I have this on 3 different hardware platforms. All different versions of 6.7.
Any idea what OCFlush is used for?
I am currently running GNS3 and VMWare Workstation on my Laptop. Previous iterations of the tandem worked reasonably well until the last update. Now I can't get my VM's to ping any devices on my GNS3 Network. I can ping between GNS3 devices, and to my external network. It's only unable to reach the VMWare endpoints and servers. This is consistent whether the images are VIRL image or running IOS on Dynamips.
I am considering rolling back to a previous version, but I wanted to check here first. Has anyone else run into this issue since the update? If so, how did you manage to make it work? Any help would be appreciated. Thanks!!!
P.S. As an aside, the upgrade process froze 60 percent of the way through, and it screwed up my NIC card drivers. I had to revert to a prior restore point to make them functional. That's there just in case developers may be reading.
Software: VMWare Workstation 14 Pro - 14.1.7 build-12989993
GNS3: Version 2.1.15
GNS3 VM: Version 2.1.15