While I'm no longer an on-premises customer, I did not have this issue either when I was at 19.07 and when I'm at 20.05.
Based on your experience in UAT, I would hold off replacing it manually until after upgrading your PROD to 20.05 and see. Unless of course if you are experiencing any issue related to this, then I recommend that you take necessary action to address it before your upgrade.
Like Wil said we're not ready to make announcements around that just yet, but what I would say is maybe hold off buying that windows PC for a little longer
Hey Lalegre, grateful for the swift reply, didn't expect to have an answer so quickly.
I managed to download the snapshot files by using PowerCLI and also by accessing through the /folder/ directory via the web browser.
I am aware that cloning consolidates the snapshots.
I also saw https://cormachogan.com/2015/07/22/migrating-a-vm-with-snapshots-tofrom-vsan/ where he migrated from vSAN to NFS using Storage vMotion (without consolidation?)
The process is similar to what I am trying to acheive, but i cannot try it as I only have a single vSAN datastore currently.
Hence, converting from vsanSparse (vSAN) to SEsparse (VMFS6) without Storage vMotion is something I am trying to do right now.
The suggestion of specifying a different datastore for Snapshot location is interesting, also cant try it as I only have a single vSAN datastore currently.
So I am trying to manually download the individual files and see if there is any unorthodox way to convert a vSAN snapshot to a VMFS6 compatible snapshot.
Hi Krishna,
It appears the database did not finish building correctly on DS3DB0. Please run this command on the primeclient and attach the output:
ssh DS3DB0 cat /ds3/VMmark3-DS3installoutput.txt
Thanks,
David
Hello-
I am working on an implementation plan which uses Dell R640 servers that have dual-port 100gb Mellanox adapters installed. These adapters were selected specifically because they support NVMe-oF. I am utilizing a PureStorage x70 array which also has 100gb NVMe-oF capable interfaces. This is all cabled between 2 Cisco Nexus 3k 100gb switches. What I was hoping to do was to create a single vSwitch on each host that utilizes both mellanox 100GB intefaces as an uplink. I would use standard active/standby teaming for Management, active/active for VMNetwork, and Active/Not used for A side vmotion and B side vmotion. I would also be creating 2 vmkernel ports on separate VLANs for RDMA traffic with each vmkernel port only using a single NIC for uplink and the other set as "not-used".
I have this all setup and have added my 2 RDMA software adapters and tied them to the appropriate physical uplink adapter. When i go to mount my storage, I am able to map to the B side of the PureArray on the appropriate RDMA adapter, but can never get the A side to connect on the other RDMA adapter. I have opened a case 2 weeks ago with VMware support but thus far they haven't been able to tell me why this doesn't work or that it is not supported to share the uplink for RDMA traffic with other services like we do with iSCSI traffic.
I will say that if I separate the nvme vmkernel ports so that they are on separate vSwitches, each with only 1 physical uplink, I can connect just fine to both sides of the PureStorage array. This would be fine, except that it would require me to cable separate 10gb ethernet to the Dell servers to handle all other traffice other than NVMe-oF.
Does anyone have any experience with NVMe-oF yet and can confirm whether it is supported to share the uplinks with other types of traffic? Thanks!
Our VM notes (annotations) have several styles depending on what point in history and who entered them. One thing that is common is there are multiple lines in the notes. One 'gotcha' I foresee problems in exporting the notes is some are using full colons and dates.
For example:
Team: the one that asks for VMs
Record ID: <data>
Date: <data>
Deployed by: <data>
Other VMs have no notes. Others have a one or two liner of text.
I'd like to export to csv in the following format:
| VM Name | Header 2 | Header 3 | Header 4 |
|---|---|---|---|
| machine1 | Team: Infrastructure | Deployment Date: June 20, 2019 | Deployed by: Fred |
| machine2 | Telephony | Template used: xxxxxxxx | |
| machine3 | line of text | another line of text |
One column per line of notes.
Hello Everyone ,
Installed Esxi 6.7 and whenever i try to start it, i do get this error message :
" Shutting down Firmware Services
Page allocation error : Out of resources
Failed to shutdown the booot services.
Unrecoverable error.
Any help would be apprecited.
We started to work on the problem - and I expect to be able to recover the most important VMs
I am trying to use Workstation Pro 15.5 to run Visual Studio 2019 in a windows guest, and the performance is pretty abysmal. It appears that hardware accelerated graphics is working fine for the OS, but Visual Studio is noticeably laggy and sluggish. Disabling 3d acceleration for VS improves things somewhat, but it's still crummy. As a rough kind of benchmark, I can open a code window on a native windows machine and scroll and see that it is fast and smooth, and CPU utilization is basically 0%. In the VM with 3d enabled it's very rough and stuttering, and CPU utilization is 30-40%. With 3d disabled in the VM it's less rough but still laggy, and CPU utilization is 20-25%. I've never received any errors, just poor performance.
Host:
HP Z4
i9 10980xe (18 core)
64gb ram
Quadro RTX 4000 (8gb)
Ubuntu 20.04 (5.4.0-42-generic)
Workstation 15.5.6 build-16341506
Guest:
Win10 2004
4 cores, 16gb ram, 2gb video ram allocated
VMware SVGA 3D driver 8.16.7.5
I've tried updating the NVidia driver to the latest (450), reinstalling VMWare Tools, I've swapped in different GPUs (an NVidia RTX 2080ti, and an AMD Radeon 5500xt), and I've tried various combinations of core counts, ram allocation, etc. Anything more than 4 cores seems to magnify the problem, but otherwise I haven't seen any change. FWIW, anything based on Chromium (Chrome, Atom, VSCode, etc) seems to have the same problem. Other Windows apps I've tried (eg, Paint 3d) run fine.
Is this a known issue with Workstation? Is there anything else I can do to troubleshoot it?
Yes it does thank you, good to know as since default is "Disabled" I was hesitant to change it apart for Host failure.
Have both vSAN and traditional storage so am summarizing the best practice/recommended HA settings below:
Host failure - Restart VMs
Host Isolation - Power off and restart VMs
Datastore with PDL - Power off and restart VMs
Datastore with ADP - Power off and restart VMs
Assume safe to change all these for existing live clusters also?
Thanks
Thanks David, for looking into this issue.
Please find the output file attached to this message.
oooooooooooooooooh.....now that's a tease
Note the hardware requirements and VM configuration as stated by Cisco: Cisco Modeling Labs 2.0 Quick Start Guide - Installing CML 2.0 [Cisco Modeling Labs] - Cisco
Are you sure your setup is in-line with what they say? Does your system BIOS have the CPU flags enabled?
That log indicates the database built successfully, so I'm not really sure why you're getting this error.
Could I ask you to delete all of the Tile0 VMs and Client0, and rebuild 1 tile again? Sorry for the inconvenience.
Thanks,
David
tdnf install powershell installs powershell LTS version 7.0. Simply use install-module to install modules supported on Linux.
Sorry, Photon 2.0 does not include Pwsh7. Try this .photonos-scripts/Pwsh7.0.3OnPhotonOS.sh at master · dcasota/photonos-scripts · GitHub
Forgot to mention, I did try Win10 1903 as well. Chromium/Atom/VSCode are much better, but VS is still laggy and using excessive CPU to draw basic windows.
Hi vBritinUSA
Clients are internaly and externaly, same behaviour.
The Issue occurs just with PCoIP, Blast and RDP are working.
But the customer want to switch back to PCoIP, because of the better image quality (Also because we are still on an older blast extreme version, with horizon <7.7)
regards
Hi DEMdev
After implementing the workaround, what exactly is the failure mode if printer mapping does not work correctly? Same as before, as in: async FlexEngine.exe instance hangs, or something else?
Same as before: async FlexEngine.exe instance hangs
You will see in the attached async log, that it suddenly stops logging. From that moment on I am unable to open the fog file as it is in use by another process. After the user logs off and the machine is deleted by Horizon vIew, I can access the log again.
Does this seem related to a particular printer?
Not 100% sure, but I have the impression that it might be related to printers that are offline at the moment we are trying to map
Can you "divide and conquer", by temporarily disabling individual printer mappings in DEM to see if there's a particular problematic one?
Very difficult to do as I am working remote and it's hard to choose a "victim" to test. Additionally there's about 80 printers around
How do elevated tasks fail? Does DEM's log indicate success with running your logon task and the referenced elevated task, but does the script not have the intended effect?
According to the blogs, the elevated task launched successfully. Attached are the logs
If you launch that batch file from a command prompt that you have elevated "manually" (as in, Run as Administrator via standard Windows functionality), does it always work?
Yes, this always works
BTW, refreshing does not serve a purpose here, unless you have modified elevated task definitions in the Management Console in the meantime.
Ah, yes. That's true. My mistake.
Answered on GitHub. Take a look and see if it works for you.
New-HVPool & Nics · Issue #376 · vmware/PowerCLI-Example-Scripts · GitHub