Hello, it seems that you could use some inspection of /etc/fstab in recovery mode. Maybe the device naming (mainly /dev/sda2) or UUIDs got changed after you have virtualized the machine, this ...
See more...
Hello, it seems that you could use some inspection of /etc/fstab in recovery mode. Maybe the device naming (mainly /dev/sda2) or UUIDs got changed after you have virtualized the machine, this is why the mounting fails and then eventually it crashes. In rescue mode, can you post the output of blkid and cat /etc/fstab? Thanks!
Hi there, is the Spanning Tree Protocol configured correctly on your switch for all the ports connected from VRTX? Try consulting this with network Team.
Hi there, What you need to do first is to upgrade your vCenter Server to the version that you plan install on your ESXi hosts. If you would be going to 5.5U2 on ESXi, you will need to upgrade ...
See more...
Hi there, What you need to do first is to upgrade your vCenter Server to the version that you plan install on your ESXi hosts. If you would be going to 5.5U2 on ESXi, you will need to upgrade vCenter Server it to that version. The same goes for vCenter Server 6.0 etc. Then and only then you can upgrade and manage the ESXi hosts that are included in its release. Make sure that all preemptive actions (consistent database backup, enough downtime) are in order before you start the upgrade. To do it the least invasive way without using the ESXi shell, could you build one additional VM that would host the VMware Update Manager? Or even better, if your policy allows to, install it on the newly upgraded vCenter Server - if you have a Windows based machine running that. With the help of VUM you can upgrade your ESXi host with offical packages downloaded straight from VMware's repositories. There is plenty of documentation to go around on this cause, see the main Update Manager documentation here: vSphere Update Manager Documentation. Any further questions you have, please ask. Good luck!
Hello, you've run into an Uncorrectable Machine Check Error. The Error register's value is be00000000010093. After debugging this means that you have a memory read error (that also points out ...
See more...
Hello, you've run into an Uncorrectable Machine Check Error. The Error register's value is be00000000010093. After debugging this means that you have a memory read error (that also points out to the memMap throwing the PSOD) on Channel 17 - there is not that many channels in modern systems. The first thing I recommend doing is checking the CPU1's memory - ideally by running memtest for an extended period of time. If you have a warranty contact with vendor, have them replace the CPU along with all the memory sticks because in my live I haven't seen Channel 17. Good luck!
The nicest thing the vCenter (Web)Client Team could do is to develop a HTML5 web client with the interface being exactly the same as in continue developing the Thick Client. That would be a nice ...
See more...
The nicest thing the vCenter (Web)Client Team could do is to develop a HTML5 web client with the interface being exactly the same as in continue developing the Thick Client. That would be a nice band-aid to our pain... in my dreams though
Hmmm... are there any new patches for your ESXi available? This can also be a physical RAM stick failing but it's highly unlikely. The "last resort" option I'd recommend is installing GLRoman's I...
See more...
Hmmm... are there any new patches for your ESXi available? This can also be a physical RAM stick failing but it's highly unlikely. The "last resort" option I'd recommend is installing GLRoman's Intel NIC drivers and see if the situation improves https://vibsdepot.v-front.de/wiki/index.php/Net-e1000e but this will put your host into "CommunitySupported" state instead of VMware/Partner Supported.
Hello, it seems the kernel crashes while trying to map memory for a Network component (accessing physical socket/virtual switch.... could be whatever). Can you please make sure that your BIOS,...
See more...
Hello, it seems the kernel crashes while trying to map memory for a Network component (accessing physical socket/virtual switch.... could be whatever). Can you please make sure that your BIOS, network Drivers & Firmware are up-to-date? What vendor/model is your server?
Hello, from the look at the crash stack you are getting what seems is an uncorrectable Machine Check Error. This is caused by faulting hardware when it causes your system to hang. Uncorrectable M...
See more...
Hello, from the look at the crash stack you are getting what seems is an uncorrectable Machine Check Error. This is caused by faulting hardware when it causes your system to hang. Uncorrectable MCEs come most often from CPUs. If you could please provide vmkernel.log and vmkwarning.log from your ESXi host we could take a look where exactly the problem lies. Do you have an Intel or AMD processor inside your ESXi?
Hi there, I'm glad you are one step closer (or hopefully done the final step ) towards resolving the issue. It makes sense now that the "power efficient" (ie. underclocked system) could cau...
See more...
Hi there, I'm glad you are one step closer (or hopefully done the final step ) towards resolving the issue. It makes sense now that the "power efficient" (ie. underclocked system) could cause the VMs to be starved for resources. Fingers crossed!
I'm afraid the only method on how to team your NICs is to give them pass-through to the guest OS and then install their own driver from vendor (Intel, Broadcom, HP), and create a team that way.
If you're talking about vCenter Server, then the one and only concern is security. The vCenter Server is one huge bundle of services which increases the attack surface and you don't want anyone t...
See more...
If you're talking about vCenter Server, then the one and only concern is security. The vCenter Server is one huge bundle of services which increases the attack surface and you don't want anyone to mess with your AD Data, rendering users or computers in your company unable to log in or effectively do anything. You are running the vCenter Server as a System Service by default, with some service account you can have further granularity. It extends even more if you decide to have the database locally (another account). vCenter Server installation will even refuse to initialize if it detects the current PC is a Domain Controller
Hello, you can find the thick vSphere clients in this VMware KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 Make sure you have been g...
See more...
Hello, you can find the thick vSphere clients in this VMware KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 Make sure you have been given required access in the Active Directory though, or if you are using local users, make sure your local user has sufficient permissions,
Hi there, can you please try removing all available NIC drivers again, this time with "remove drivers" checkbox checked as well? Also check for any hidden NIC drivers that might be present in ...
See more...
Hi there, can you please try removing all available NIC drivers again, this time with "remove drivers" checkbox checked as well? Also check for any hidden NIC drivers that might be present in the Device Manager and remove them as well.
Yes, you can reserve the affinitized CPU to be exclusively used by that VM by selecting "HyperThreaded Sharing" option to "None" while on the CPU Affinity settings screen. Otherwise there is no o...
See more...
Yes, you can reserve the affinitized CPU to be exclusively used by that VM by selecting "HyperThreaded Sharing" option to "None" while on the CPU Affinity settings screen. Otherwise there is no other "Direct Passthrough" you can do -everything has to undergo ESXi's internal scheduler.
Hello Mariusz, Windows 2008 should contain the basic the Intel E1000(e) NIC drivers. However it is possible that there is now some conflict between the driver version that was installed and th...
See more...
Hello Mariusz, Windows 2008 should contain the basic the Intel E1000(e) NIC drivers. However it is possible that there is now some conflict between the driver version that was installed and the one that is present in the current Virtual environment. A few things you could do is: Uninstall all available Intel NIC Drivers from the Add&Remove Programs menu in the Guest OS Better option in my opinion: Change the NIC driver to vmxnet3 in the vCenter, but beware you'll lose all the NIC settings that way - make sure to note them down before you do this. Mouse control might again be conflicting with the driver that is already present from the physical guest OS. Check for all HID compliant devices and all devices under Mice tree and remove them. Good luck!
Hello there, "a general rule of thumb" for direct-attached storage on ESXi host would be to have a RAID controller with some NVRAM cache ( > 512 MB) for the performance where this cache is flu...
See more...
Hello there, "a general rule of thumb" for direct-attached storage on ESXi host would be to have a RAID controller with some NVRAM cache ( > 512 MB) for the performance where this cache is flushed out to disks where available, and BBU (back-up battery unit) in case of power outage and the disks attached to it. RAID10 is the best possible choice for magnetic spindles in terms of performance, but could be hard to justify if you are on a tight budget. Next is the spindles' RPM - the more you have the more IOPS you are able to handle. 7400 RPM SATA tops out at somewhere between 75-100 IOPS, whereas SAS 10k RPM at ~140 IOPS and 15k RPM at 175-210 IOPS (source). Using any RAID calcluator on-line can give you a rough estimate of how much combined IOPS will your drives be able to handle. Since many VMs running on a datastore will result in random reads/writes to disk, this will be the main metric to go by. I can also recommend making one datastore from all the drives on the same RAID controller - this way you'll avoid wasting the fragments of leftover space on your datastore. Make sure you understand what exactly will these "high performance" VMs need - consult the owners, monitor them for a day or two during their peak times to be able to completely emulate the current performance under a virtualized solution. Cheers, and good luck!
Hi there, I'm glad that you are getting the environment slowly optimized up to boot. The thing that should be done next is actually pinpointing all the orange VMs and getting us their: proce...
See more...
Hi there, I'm glad that you are getting the environment slowly optimized up to boot. The thing that should be done next is actually pinpointing all the orange VMs and getting us their: process explorer sorted by CPU usage esxtop of the ESXi the machines run on - it seems that in this case there'd be only two ESXi hosts requiring further investigation also if you can try to get in touch with their users as to confirm what all suits their needs. Good luck!
A great idea there! - I'd strongly recommend snapshotting before this is done. I think I have done some rescue-mission once on a Windows boot drive and after mounting it to another VM it didn't b...
See more...
A great idea there! - I'd strongly recommend snapshotting before this is done. I think I have done some rescue-mission once on a Windows boot drive and after mounting it to another VM it didn't boot anymore after I've re-attached it. Either magic happened or I did something wrong, anyways that was a long time ago. Also, while you are in the process of mounting the VMDK to another VM for rescue, I think a sfc /scannow with offline option would be for the best - this checks integrity of the whole OS and repairs any errors.
Hello everyone, what is the SAS/SCSI/SATA virtual adapter you are using and have you tried changing it around? Think LSI Logic SAS or Parallel switch could help, maybe even trying a SATA contr...
See more...
Hello everyone, what is the SAS/SCSI/SATA virtual adapter you are using and have you tried changing it around? Think LSI Logic SAS or Parallel switch could help, maybe even trying a SATA controller for your disk storage could help.