Advertisements

Category Archives: VMware

VMware guest server taking a long time to finish boot stuck at Bringing up interface

Rebooted a server and saw some messages about VM communication interface showing errors

Starting VMware Tools services in the virtual machine
Switching to guest configuration: OK
Paravirtual SCSI module: OK
Guest memory manager: OK
VM communication interface: FAILED
VM communication interface socket family: FAILED
File system sync driver: OK
Guest operating system daemon: OK
FAILED

Long time at the message Bringing up interface eth0
vmware_bringing
Updated VMware Tools VMware Tools does not start after updating the kernel

Had to changed the driver for network interface for the server to finish the boot sequence

Advertisements

Error when you try to search a server in VMware vCenter client: Login to the query service failed

When using the VMware vCenter client you get the error message: Login to the query service failed.
A connection failure occured (Unable to connect to the remote server)
VMware vCenter query
Check if you are able to resolve the FQDN for the ESX server.
vcenter
I had to put the IP and host in the hosts file on my Windows machine – C:\Windows\System32\drivers\etc\hosts

Scanning for new disk in a VMware host running Suse Linux 10 SP4

Scanning for new disk in a VMware host running Suse 10 SP4

root@linux:~ # cat /etc/*release
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 4
LSB_VERSION=”core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64″

I use the following command to scan the SCSI bus

root@linux:~ # echo “- – -” > /sys/class/scsi_host/host0/scan

List the disks. It’s the last one

root@linux:~ # fdisk -l

Then I make a partition for the disk. The first time, when there is not a valid DOS partition I like to write and call fdisk again

root@linux:~ # fdisk /dev/sdf
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won’t be recoverable.

The number of cylinders for this disk is set to 9137.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

Running again and this time creating the partition

root@linux:~ # fdisk /dev/sdf

The number of cylinders for this disk is set to 9137.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-9137, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-9137, default 9137):
Using default value 9137

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): 8e
Changed system type of partition 1 to 8e (Linux LVM)

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

Add the partition to LVM

root@linux:~ # pvcreate /dev/sdf1
Physical volume “/dev/sdf1” successfully created

Verify the file system size

root@linux:~ # df -h /usr/oradata/oradvt061t
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/softwarevg-dvt061lv
168G 133G 26G 84% /usr/oradata/oradvt061t

Add the disk to the volume group

root@linux:~ # vgextend softwarevg /dev/sdf1
Volume group “softwarevg” successfully extended

See the characteristics of the volume group

root@linux:~ # vgdisplay softwarevg
— Volume group —
VG Name softwarevg
System ID
Format lvm2
Metadata Areas 4
Metadata Sequence No 11
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 4
Max PV 0
Cur PV 4
Act PV 4
VG Size 385.98 GB
PE Size 4.00 MB
Total PE 98810
Alloc PE / Size 69376 / 271.00 GB
Free PE / Size 29434 / 114.98 GB
VG UUID 0BsKwN-18al-1TT8-gctq-fRK4-ccJl-fNXL6g

And the disk added

root@dsv080:~ # pvdisplay /dev/sdf1
— Physical volume —
PV Name /dev/sdf1
VG Name softwarevg
PV Size 69.99 GB / not usable 793.00 KB
Allocatable yes
PE Size (KByte) 4096
Total PE 17918
Free PE 17918
Allocated PE 0
PV UUID 21Q3wb-2tKn-xUdP-9ZBa-tqbp-vhvS-MhSbVt

Increase the logical volume using the new disk

root@linux:~ # lvextend -l +17918 /dev/softwarevg/dvt061lv
Extending logical volume dvt061lv to 239.99 GB
Logical volume dvt061lv successfully resized

Then resize the file system

root@linux:~ # ext2online /dev/softwarevg/dvt061lv
ext2online v1.1.18 – 2001/03/18 for EXT2FS 0.5b

Verify the file system size

root@linux:~ # df -h /usr/oradata/oradvt061t
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/softwarevg-dvt061lv
237G 133G 92G 60% /usr/oradata/oradvt061t

VMware vSphere Client – Error: Call “ServiceInstance.RetrieveContent” for object “ServiceInstance” on Server failed

I was receiving the error below: The request failed because of a connection failure. (Unable to connect to the remote server)

Call “ServiceInstance.RetrieveContent” for object “ServiceInstance” on Server failed

Despite having followed the instructions for this error I was still unable to connect. I solved this problem by uninstalling Widecap, an alternative that I was trying to replace Proxifier

Failed to delete VM – VMware Server

Right clicked the VM to delete and it removed from the Inventory but showed the following message:

Failed to delete VM
Reason: Failed to unregister the VM after it was deleted.

Another VMware error where Google showed nothing. 😦

Unable to find the answer LIBDIR – VMware Server

Does anybody know how to solve this problem?

root@memcached:~ # rpm -ivh –force VMwareTools-1.0.5-80187.i386.rpm
Preparing… ########################################### [100%]
Unable to find the answer LIBDIR in the installer database
(/etc/vmware-tools/locations). You may want to re-install VMware
Tools.\n\nExecution aborted.

error: %pre(VMwareTools-6533-80187.i386) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping VMwareTools-6533-80187

I cancelled (CTRL+C) in the middle of the installation of the rpm and now I can’t run the installer or reinstall the rpm.

%d bloggers like this: