When a Virtual Machine crashed it might happen that you cannot power it off with the vSphere Client. In that case, you have to kill the VM through the ESXi command-line. Connect to the ESXi host with SSH. (If a virtual machine crashed in a cluster and you cannot identify where it is running, you have to identify the ESXi Hosts where the VM is running ) Locate the World ID with esxcli vm process list or vmdumper -l [root@esx1:~] vmdumper -l wid= 462925 pid=-1 cfgFile="/vmfs/volumes/5474e3ca-af7a8515-9aef-001b2193b3b0/vcsa.virten.lab/vcsa.virten.lab.vmx" uuid="56 4d a9 f8 05 4a d6 a6-cb 08 de 39 a6 e7 a4 38" displayName="vcsa.virten.lab" vmxCartelID=462924 [root@esx1:~] esxcli vm process list vcsa.virten.lab World ID: 462925 Process ID: 0 VMX Cartel ID: 462924 UUID: 56 4d a9 f8 05 4a d6 a6-cb 08 de 39 a6 e7 a4 38 Display Name: vcsa.virten.lab Config File: /vmfs/volumes/5474e3ca-af7a8515-9aef-001...
Posts
Version 1.0 Author: Srijan Kishore Last edited 1/Sep/2014 This guide explains how to configure VNC-server in CentOS 7.0 server. It is a very convinient way of administrating the CentOS 7.0 with the help of GUI(Graphics User Interface). The GUI can be access any where with the help of the VNC-client on any OS. The basic condition is that the connecting OS must have VNC-clients installed in it. 1 Preliminary Note This tutorial is based on CentOS 7.0 server, so you should set up a basic CentOS 7.0 server installation before you continue with this tutorial. The system should have a static IP address. I use 192.168.0.100 as my IP address in this tutorial and server1.example.com as the hostname. IP address 192.168.0.100 Gateway 192.168.0.1 DNS 8.8.8.8 8.8.4.4 Hostname server1.example.com VNC-server benefits Remote GUI administration makes work easy & conven...
You can install Hyper-V Manager on a client computer, and from that computer, you can manage the virtual machines that are running on your virtualization server. The user experience is the same as that of Hyper-V Manager running on the virtualization server. Note The client computer can be running Windows 7, Windows Vista® with Service Pack 1, Windows Vista with Service Pack 2, a full installation of Windows Server 2008 R2, or a full installation of Windows Server 2008 with the update to the release version of Hyper-V ( KB950050 in the Microsoft Knowledge base – http://go.microsoft.com/fwlink/?LinkID=122188 ). Additionally, the client computer does not need to be a computer that supports virtualization, and it does not need to be running a 64-bit operating system. For this test scenario, a computer that is running Windows 7 is used as the client computer, as explained in the following scenario prerequis...
When you start an automatic upgrade of VMware Tools, you do not need to perform any operations in the guest operating system that is running on the virtual machine. The automatic upgrade uninstalls the previous version of VMware Tools, installs the latest version that is available for your ESXi host, and if necessary, reboots the virtual machine. Automatic VMware Tools upgrade is not supported for virtual machines with Solaris or NetWare guest operating systems. Prerequisites The following requirements are for each virtual machine in the upgrade: ■ Power on the virtual machine. ■ Verify that the guest operating system is running. ■ To determine whether you have the latest version of VMware Tools, look on the Summary tab for the virtual machine. Procedure 1 Select Automatic Tools Upgrade . 2 (Optional) In the Advanced Options field, ...
VMware ESXi 5.5 Purple Diagnostic Screen Exception 14 in SEsparse and LibAIO (LibAIODrainMergeQueue, LibAIOMergedIODone, SESparseAsyncDataDone) (2073516)
Symptoms VMware ESXi 5.5 host fails with a purple diagnostic screen You see backtrace similar to: cpu0:33101)@BlueScreen: #PF Exception 14 in world 33101:memMap-0 IP 0x4180182f4948 addr 0x4108fffffff0 PTEs:0x100088063;0x80000020ad5bf063;0x0; cpu0:33101)Code start: 0x418018000000 VMK uptime: 1:09:27:02.593 cpu0:33101)0x4123c535cb20:[0x4180182f4948]LibAIODrainMergeQueue@vmkernel#nover+0x150 stack: 0x4130002a85c0 cpu0:33101)0x4123c535cb80:[0x4180182f53fd]LibAIOMergedIODone@vmkernel#nover+0x211 stack: 0x412ec622ef90 cpu0:33101)0x4123c535cbb0:[0x41801802d21f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x1 cpu0:33101)0x4123c535cbe0:[0x418018bb9798]SESparseAsyncDataDone@esx#nover+0x15c stack: 0x41300007b0c0 cpu0:33101)0x4123c535cc10:[0x41801802d21f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x4123c535cc70 ...
:: resets the ipv4 interface netsh interface ip reset :: flush and reregister DNs ipconfig flushdns net stop dnscache net start dnscache ipconfig /registerdns :: clear persistent routes route print -f :: start / restart mrxdav net stop netbt net stop mrxdav 2>nul net start mrxdav net start netbt :: clean the arpcache arp -a -d :: I might have the order of the switches backwards and the order matters, so if that doesnt do anything put the -d before the -a :: make sure winhttp and webclient services are running (this is a mystery to me / neither appear necessary, but both have fixed my problem on various occasions) net start webclient net start winhttp From < http://superuser.com/questions/631681/ping-cmd-request-timed-out-for-all-websites-but-sites-are-accessible-through-bro >
By default, In Solaris 10, VNC service is almost configured. Below is the process to enable it. Check VNC service root# svcs -a | grep -i vnc disabled 13:47:12 svc:/application/x11/xvnc-inetd:default We need to enable the VNC service root# svcadm enable svc:/application/x11/xvnc-inetd:default By default, it broken we need to so some changes. root# svcs svc:/application/x11/xvnc-inetd:default STATE STIME FMRI maintenance 14:22:41 svc:/application/x11/xvnc-inetd:default Need to append vnc to the /etc/services root# echo “vnc-server\t5900/tcp\t\t\t# Xvnc” >>/etc/services Cross verify /etc/services root# tail /etc/services snmpd 161/udp snmp # SMA snmp daemon vnc-server 5900/tcp # Xvnc Need to customizethe gnu display manager root# ls -al /etc/X11/gdm/custom.conf /etc/X11/gdm/custom.conf: No such file o...