Tag Info

Hot answers tagged

14

Yes, there are performance implications for long-running snapshots. There are even greater implications for consolidating delta VMDKs back to the original disk file. This can cause unresponsiveness in your VM's operating system or other undesirable behavior. VMware has templating and cloning functionality built into vCenter. You need a $600 vSphere ...


6

According to the screenshot below, you have an "Unconfigured Disk"... This means that the drive needs to be configured on your HP Smart Array B120i RAID controller before it can be used by an operating system or VMware ESXi. You can perform this from the ESXi command line using the hpssacli command located in /opt/hp/hpssacli/bin/hpssacli on your ...


5

You don't need to wipe the drive to do what you're describing. You'll find that you won't even have a convenient way to erase a single disk. I'd urge you not to break the RAID 1 array as a form of backup, though. What happens if the upgrade "goes poorly"? This practice shouldn't be promoted because it carries some risk, and doesn't scale to other RAID ...


4

That's not the best way to migrate from W10 to ESXi, export the VM as an OVF/OVA and import it - basically, as I'm sure you've figured out, the file paths are wrong doing it the way you have. Alternatively just edit the .vmx file but to be honest it's just quicker to export/import.


4

Windows server downtime for updates is inevitable. Service downtime is avoidable, however. The key is to realize that downtime needs to be measured by service availability, not the status of individual servers. For your SQL Server instance, your best bet is to implement some form of multi-server instancing. One technique that Microsoft allows in SQL Server ...


4

ewwhite's answer is correct, but just to expand a bit more or the performance penalty, consider the following scenario: You create a VM. A virtual read from the vmdk takes one physical disk read of the same size. Fairly straightforward. Now imagine you take a snapshot of the VM. Now, for every virtual read, you're going to incur 2 physical reads, one from ...


3

No it doesn't support PCI passthrough. The CPU/BIOS feature you require is VT**-d** or IOMMU. The VT option you can see is to enable virtualisation extensions which are required for 64bit OS, paravirtualisation, etc. But do not include directed IO.


3

Yes, you can move the virtual machine from one host to the other. It's less than ideal, since your VM will be scheduled across two physical CPUs, but it will definitely work.


3

Think about the timing here... When will you receive your proper servers? You have a 60-day trial of VMware which is unrestricted, so if you receive you servers before then... Your Essentials Plus license covers 6 sockets, not "three servers". If you install your license key onto a 4-socket server, you'll consume 4 sockets of licenses, leaving 2 sockets ...


2

By upgrading to at least ESX 5.5 Update 1. Alternately, this is caused by guests with E1000 network adapters, so if updating isn't possible, or not possible immediately, you can always change the vNIC adapter type on the guests. Of course, there is the off chance that this PSOD is caused by something else, but since you haven't posted any error log ...


2

It could be a hardware issue, but probably more of a firmware thing. Can you ensure that your firmware is up-to-date on the host server? The other thing to do is update your ESXi host. Your build number is: 1623387. The current build number is 2302651. Many people don't understand that VMware actually needs to be patched and updated. The process is not ...


2

The HP P2000 G3 manual and SMU Reference Guide cover this quite well. The basic overview is: Plug the new disks in. Create a new Virtual Disk with the new physical disks. Create a volume. Assign it to your vSphere hosts. Rescan in VMware and format a VMFS volume. For the P2000 side, there's a "Provisioning Wizard" in the web interface that will guide you ...


2

At last got the answer to my question. Its was due to how Linux implelemts TCP/IP stack. By default it uses weak host model.[http://en.wikipedia.org/wiki/Host_model] . The Remote hosts network adapter which was connected to the private network was responding to request on the ip of the other adapter due to this. The host Z was always accessing the ...


2

You would need to create a static DNS entry on your DNS server for the ESXi host. It's not going to automatically create a DNS registration for you. Edit: It is possible to have an ESXi host perform a dynamic DNS registration (DDNS) if you go into the bowels of the ESXi command line and instruct it to... It's a strange request, as adding a static entry is ...


2

I'm not sure that I understand your network setup. In your management port group you work with a VLAN trunk range of 0-4094. This implies you're working with tagged VLANs on your uplinks, see Edit the VLAN Policy on a Distributed Port Group in the vSphere Web Client. On the other hand, the port group that gives you trouble works untagged. To the best of my ...


2

I did extensive tests with scenerio's like you describe. I tried having a storage server with failover capability using DRBD, then using iSCSI to attach that storage to Debian machines running Xen. I quickly gave up on that, because I had too many problems. Part of those could be me, though. One of them was that the iSCSI block devices weren't created. Then ...


2

I suspect an I/O issue. Can you detail the hardware and storage being used? Also provide the ESXi version and build number. Often times, you'll see this happen if the storage used by ESXi becomes unavailable. Remember that the networking stack and SSH daemon are running in RAM. But entering a password requires a read from disk. You likely won't see logging ...


1

Is it fair to assume (in this and similar cases): numbers 0 to 11 represent each of the physical cores (or are the 'hyperthreads' numbered too)? Yes and yes HT are included if I wanted to limit the VM to run on one of the physical CPUs, I should enter either 0-5 or 6-11 (or are these numbers in some different pattern)? ...


1

Your software is likely licensed per (visible) CPU socket. If you configure your destination virtual machine with the appropriate socket and core count, it doesn't really matter where ESXi decides to schedule threads on the underlying hardware. Your software should only be concerned with what's visible to the virtual machine. In this case, a 1-socket, 4-core ...


1

Vmware tools are actually a very important part of the VMware software packet. They contain the device drivers, and act as an API to the host for the ESXI. Upgrading them is a big part of maintaining stability and performance of your vSphere environment. A full list of features the vmware tools provide should be able to demonstrate quite quickly that they ...


1

Please use this procudure Migrating service console or VMkernel port from standard switches to VMware vSphere Distributed Switch (1010614) http://kb.vmware.com/kb/1010614


1

This is soooooo wrong... mismatched hosts, protocols, design, etc. But the reason solution here: Use NFS with NexentaStor for VMware That way, both of your hosts will be able to see your storage.


1

The proper solution for vSphere and host power management is linked to the Distributed Power Management feature available at the highest tier of vSphere Enterprise Plus licensing. You can place hosts in Standby/Sleep and wake via WOL and/or IPMI/ILO. But this cool stuff all requires vCenter. I believe you can send generic Wake-on-LAN packets to an ...


1

Typically the steps are: Resize the partitions to match the new disk size. You seem to have done that already. Resize the LVM Volgume group to make the new space in the partition available to the volume manager: vgextend Resize the Logical Volume with the file-system you want to extend: lvresize note: don't mistake the --size <new capacity> for ...


1

We've solved this problem last week. sorry for my late response. We've been trying to setup our Storage and vmotion network as following doc: http://blogs.vmware.com/vsphere/2011/08/vsphere-50-storage-features-part-12-iscsi-multipathing-enhancements.html We have created 2 vmkernel each using one of both physical interface who were added to the vswitch. To ...


1

This was probably firmware or driver issue. Please update your host to latest firmwares with SPP(Service Pack for Proliant.) Most probably about HPSA driver. please check out kb below. http://kb.vmware.com/kb/2075978



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