Hi cbaptiste,
Correct, by putting pool-specific conditions on the global setting you can control which pools have application blocking enabled (further controlled by specific application blocking config files, if you wish) and which pools don't.
Hi cbaptiste,
Correct, by putting pool-specific conditions on the global setting you can control which pools have application blocking enabled (further controlled by specific application blocking config files, if you wish) and which pools don't.
Bump
When you say "export", I assume you mean you want a report or data dump?
You will need to write your own against the API.
I need to P2V a windows 2003 server, and apparently 6.0 was the last version to support win2003. Anyone know where I can get a copy?
Hi,
Hmm.. what is the setting of Fusion -> Preferences -> General tab -> Gaming ?
Does it say "Auto-detect for games" or another value?
FWIW, I do not see the problem you have down here.
What kind of mac are you using?
Is the mouse wired or is it a blue tooth mouse?
If it is a blue tooth mouse then try turning off passing through blue tooth to the guest under the USB settings.
That does not appear to work well in the latest VMware Fusion 15.5.
--
Wil
Hi,
If you want to print via the host then you have to install the additional software from the menu "Virtual Machine" -> "Install Virtual Printer".
The alternative is to connect the printer directly to the guest (if the printer is connected via USB)
--
Wil
I got Two site with a cluster on each.
each site has his own IP addressing, but I would like to bridge the "VM Network" on the distant site to the local "VM Network" so I could start a VM replicat on the distant site and it will be visible on the local "VM Network" without IP address changes.
I have no dedicated switch between the two site, I use routers and telecom provided MPLS link with 30Mbits throughput.
I was thinking of an openvpn link with TAP drivers so I can bridge at ethernet layer, but there may exist better solutions.
thank for your directions.
Cheers from Tahiti.
D.
Hi,
Same issue for me - also the control key doesn't reliably pass through.
Can get a shift to work by pressing once the pressing again and then having to delete the first character. Not a great way to work tho :-)
Moderator: Moved to vSphere vNetwork
Hey radostin,
Thanks for the update, and it's great to hear that a fix will be coming by 8.0.1.
Is nodejs used to build the python containers as well? I just tested an on-prem FaaS Python ABX through zip import and it has the same behaviour. None of the additional files in my zip are uploaded and requirements.txt is blank.
cheers
steve
It's working in all my instances of vRA 7.4. I also just tested against vRA 7.6 and it worked there too, so I can only assume it will work in vRA 7.5.
How are you setting the property in your EBS workflow? And you're definitely not setting other values in the same lifecycle with a different EBS (e.g., in PRE-Requested you're setting the machine name)? Remember that only one EBS workflow can update values on the machine entity per lifecycle state; whatever runs last takes precedence.
If between the state that you set it (e.g., pre-requested) and the next state (e.g., pre-building) the payload of your EBS workflow has not updated the __amazon.Image.ID value then the way you are setting it is not correct. This value should reflect the updated value which then correspondingly builds the correct AMI in EC2.
Have you tried doing it with a clean slate of EBS, ignoring all your normal provisioning activities? Just one EBS that runs in PRE-Requested which changes the value and one EBS in PRE-Building that validates the value has changed; you can fail the Building EBS to prevent any actual deployment from occurring.
I still have no idea what actually causes the issue but seeing how they dropped support for these types of sockets/CPUs I doubt anyone will get any actual answers. For anyone seeing this in the future if you really need to emulate on your current system that uses an older CPU you're probably better off using VirtualBox or buying a newer system and running a newer version of VMWare on that.
You'd either have to stretch L2 or use an overlay technology like VXLAN to achieve this. There's nothing built in to vSphere that'll allow this.
ls -l on datastore Temp folder directory
-rw-r--r-- 1 root root 54760833024 Nov 28 06:03 VM-flat.vmdk
-rw-r--r-- 1 root root 488 Nov 28 07:03 VM.vmdk
Disk Descriptor File
# Disk DescriptorFile
version=1
encoding="windows-1252"
CID=b062bf1f
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 106954752 VMFS "VM-modified-flat.vmdk" 0
# The Disk Data Base
#DDB
ddb.adapterType = "buslogic"
ddb.geometry.cylinders = "6657"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "ee2e1b74629e496c3a6fca3cb062bf1f"
ddb.thinProvisioned = "1"
ddb.uuid = "60 00 C2 9b be 29 8e 76-ea 4a e0 f9 8e 34 9a cd"
ddb.virtualHWVersion = "4"
As it turns out as I was writing this post, I noticed that the "VM-modified-flat.vmdk" line should actually say "VM-flat.vmdk". After making that edit, the two .vmdk files showed as one .vmdk file with the proper icon in the datastore browser.
Thanks for the guidance. I just ordered it.
Have a nice day!!
There is one more syntax error you have in the descriptor.
You should not have a 0 at the end of the RW line.
Looks like this VMDK was once used as type "monolithicFlat" from Workstation.
the user guide 3.1 described how to mitigate the CVE-2018-3646 in page 104, which is setting up the ESXi host parameter ''VMkernel.Boot.hyperthreadingMitigation" to ''true".
i'm wondering about if I utilize vSphere 6.7U3 with VMmark 3.1 and wanna mitigate the CVE-2018-3646 correctly, should I also set the ESXi host parameter "VMkernel.Boot.hyperthreadingMitigationIntraVM" to "false"?
these two parameters are described in VMware Knowledge Base , in which the ESXi Side-Channel-Aware Scheduler Version 2 (SCAv2) must be enabled to deal with "Concurrent-context attack vector".
the user guide 3.1 p.104 only mentioned about the configuration of ''VMkernel.Boot.hyperthreadingMitigation". Does the config. of "VMkernel.Boot.hyperthreadingMitigationIntraVM" impact on VMmark test's compliance???
thx
Solved! its a problem with SQL 130 mode, the database is almost with 400gb.