Tag Info

Hot answers tagged

7

Resolved. When looking at the datastore through the vSphere Web Interface (my fault, I still prefer the old client) it correctly shows the 62TB max size limit. Potentially a hardcoded value in the old GUI given it's now deprecated.


4

1) they do have a linux client - the web-client - you know when you log into the .net client - well it says in that little text bit at the top something along the lines of 'stop using this, it's going away, use the web-client' - well, that. 2) As a rule of thumb I assume about 200 random IOPS per 15krpm disk - I know you may well get more but it's a ...


3

ESXi should automatically pick up any existing datastores if you do a rescan on the controllers - the rescan all... button: A more detailed instruction can be found in the vmware knowledgebase


3

You don't really install nagios-tools on an ESXi host. The only thing you actually install are hardware specific VIBs that allow monitoring of the hardware itself. What VIB you need to install depends on the hardware, usually you can get them from the manufacturer. If you installed the ESXi using an image from the manufacturer the VIBs are usually already ...


3

I think you're supposed to use open-vm-tools for that OS/hypervisor combination.


2

In case the software inside your VMs relies on a CPU feature that the chosen EVC mode hides it will crash. A lot of software doesn't take some CPU features for granted and falls back to doing things themselves ("in software") instead of offloading tasks to specialized CPU instructions. So even if your software can run without certain CPU features you might ...


2

Add a domain controller (or take a clone of one of the existing ones) Move it to your test network, fire it up. Seize all of the FSMO roles. Use ntdsutil to clean up the old DCs that it can no longer contact.


2

Did you try the "No access" role on "SUB-Folder"? That should override the permissions propagated from "Top-Folder" with, well, no access at all. edit: "Use the No Access role to mask specific areas of the hierarchy if you do not want for certain users or groups to have access. Best Practices for Roles and Permissions


1

It is better to use snmp with supported OIDS, better than nrpe and custom scripts, which you need to porting into the system. You can find howto enable snmpd server on vmware site/google. Something like this: esxcli system snmp set --communities YOUR_STRING esxcli system snmp set --enable true esxcli network firewall ruleset set --ruleset-id snmp ...


1

According to the documentation, the -Location parameter for New-VM expects an object of type Folder. If you're passing in a path string, then it's not going to work. You'd need to use Get-Folder, with either the folder ID (Get-Folder -ID Folder-group-v30070), or the name of the folder itself (Get-Folder destfolder) to store the Folder object and then pass ...


1

If you enable ssh on the esxi server then you can scp the files off into an attached vmdk either using winpe or another suitable bootdisc.


1

Try and see. What else can you do? You can't let the snapshot run forever. And you're going to have to consolidate the disk files at some point.


1

Then setup a terminal server for your users to work with. What you want to do is like multiple PCs using only one hard disk, which just can't work, at least in write mode.


1

You have to fix this at the Linux level. And that is going to depend on your specific Linux system's version. For a virtual machine, though, I'd try to avoid working on the VMware console. It's not a good user experience. Please see: Isn't Ctrl-Alt-Delete on Linux *really* dangerous?


1

This looks like a former VMFS-3 volume. The block size impacts the maximum capacity of the datastore under the legacy VMFS-3 format. But beyond that and with vSphere 5.5, you have to use the Web client to do anything with larger VMs and VMDKs. Use the vSphere Web Client to create VMDKs larger than 4 TB, or to extend an existing VMDK beyond 4 TB.


1

Your vm is still in your datastore but is locked (raw format). Do you have fault tolerance activated ? Put your server on maintenance mode and on tab machine try to move the vm on other esx.


1

If you shut everything down, then take snapshots of everything as they are shutdown, and when you revert back, you shut everything down and revert everything back to the same snapshot, you should be fine.


1

No, you cannot have multiple vCenter servers managing the same hosts at the same time. In KB1024051 the supported HA options for vCenter are outlined. New in version 6.0 is the option to use Microsoft Clustering for the Windows version of vCenter which probably provides the best availability, but also introduces the highest possible complexity.



Only top voted, non community-wiki answers of a minimum length are eligible