VMotion failed … everything looks right … why?

Obviously, if everything’s right, it won’t fail, but here, it’s more a bug than anything else. In this case, if you use dedicated NICs just for VMotion and you’ve just a crossover cable between the 2 nics, you may have a problem if you’re using the same network IP addresses for the Vmotion IPs. It seems to want to look for the router or something. You’ll see that it logs in both boxes, so you may want to rule out the networking issue, but you can’t in this case. The logs on both sides will indicate timeout. In this case, both of the servers are on the 10.x.x.x/24 network and the VMotion and iSCSI networks have ip addresses that were both 10.x.x.x/24, but the VMotion nics can’t access the router. The fix is easy. Just change the IPs to something that the server doesn’t know about … something like 192.168.0.1/24 or something.

Mandarin Garden in Berkeley, CA *****

This restaurant has the absolutely the most delicious Peking duck! I say, visit the place for the duck itself. It’s definitely worth driving a few miles for. They come with tortilla like wrapping paper instead of your typical bread – the skin is crispy and meat is juicy. In the bread, we put some hoisin sauce and cucumbers and green onions along with the meat/skin. The waiter was nice enough to give us a demonstration as well. The staff is very friendly and can speak Chinese, Japanese and English.

Aside from the duck, we’ve had other items on the menu that were quite good. I really liked the pot stickers and they seem to have a specialty called stuffed eggplants that other restaurants don’t seem to carry.

I’ll definitely visit the restaurant again should I be in Berkeley.

lost vmfs volume – says 100% available – SAN LUN, storage pr

1) fdisk -l

this would show which device doesn’t have a partition.

2) dd if=/dev/sd(x) of=/tmp/dump_sdx.txt count=100 bs=1024

file /tmp/dump_sdx.txt shows x86 boot sector.

strings /tmp/dump_sdx.txt shows some vmdk files

3) fdisk -lu /dev/sd(x) shows that there are no partitions on the disk.

4) ran fdisk /dev/sd(x). created new partition spanning entire lun and then used partition type fb.

5) run “vmkfstools -V”

That’s it

NTP notes

http://www.cisl.ucar.edu/nets/intro/sta … s/ntp.html NTP (Pete’s notes) To get ntpd working, get a version that’s at or later than
ntp-stable-4.2.0a-20040617. Gunzip it, untar it, run ./configure,
make and make install. I couldn’t RPM-delete the ntp that’s
installed, so I hand-deleted all the ntp* binaries in
/usr/sbin. I know this isn’t optimal. Then I
hand-edited the /etc/init.d/ntpd, deleted the
/etc/sysconfig/ntpd, and made
/etc/sysconfig/iptables allow ntp packets. Then
I edited /etc/ntp/conf to camment out all the
lines except restrict 128.117.0.0 mask 255.255.0.0
disable auth
broadcastclient
 I did
/etc/init.d/ntpd stop
/etc/init.d/ntpd start ,,,and waited a few minutes for the router’s broadcast packets to
be heard. Then I did ntpq and “peers” and saw the router listed.
One other possible problem: if your machine’s time is too far
out of sync with the router’s, ntpd won’t correct it. To force
synchronization, do “ntpdate mlra”.
The ntp.conf file has a section that configures
a fake driver. If you leave that on, you’ll see the “LOCAL”
peer. When you comment it out, ntpq “peers” will give
“No

How to build redhat kernel for VMware for time issue

Anyways, here’s how you do it:
1) download kernel source. I got mine from:
ftp://ftp.redhat.com/pub/redhat/linux/u … EL.src.rpm 2) install source:
rpm -i kernel-2.6.9-34.0.2.EL.src.rpm
(You may need to run “mkdir -p /usr/src/redhat/SOURCES”. If that’s the case, then I’d run “mkdir -p /usr/src/redhat/SOURCES /usr/src/redhat/SPEC /usr/src/redhat/RPMS /usr/src/redhat/SRPMS /usr/src/redhat/BUILD” just in case. ) 3) edit files to include BusLogic driver:
cd /usr/src/redhat/SOURCES edit the following files:
kernel-2.6.9-i686.config
kernel-2.6.9-i686-hugemem.config
kernel-2.6.9-i686-smp.config replace all instances of:
# CONFIG_SCSI_BUSLOGIC is not set
with:
CONFIG_SCSI_BUSLOGIC=m 4) make a patch change the Internal kernel timer frequency.
cd /usr/src/redhat/SOURCES
tar jxvf linux-2.6.9.tar.bz2
mkdir -p linux-2.6.9-vmware/include/asm-i386
cp -pr linux-2.6.9/include/asm-i386/param.h linux-2.6.9-vmware/include/asm-i386/param.h
open linux-2.6.9-vmware/include/asm-i386/param.h
change
# define HZ 1000 /* Internal kernel timer frequency */
to
# define HZ 100 /* Internal kernel timer frequency */ diff -urN linux-2.6.9/include/asm-i386/param.h linux-2.6.9-vmware/include/asm-i386/param.h > vmware.patch add the patch to the spec file list
open /usr/src/redhat/SPECS/kernel-2.6.spec
added to where it lists the patches (your numbers may vary):
I just made it Patch 5 since it doesn’t exist:
so after the line: Patch4: linux-2.6.9-selected-ac-bits.patch
Patch5: vmware.patch and where it does the prep after the line: %patch4 -p1
%patch5 -p1 5) change the release of your kernel to differentiate:
cd /usr/src/redhat/SPECS
open the file: kernel-2.6.spec and change:
%define release 34.0.2.EL
to
%define release 34.0.2.EL.vmware 6) build the rpm.
rpmbuild -ba –target=i686 /usr/src/redhat/SPECS/kernel-2.6.spec You could use
rpmbuild -bb –target=i686 /usr/src/redhat/SPECS/kernel-2.6.spec
if you only need the binary rpms, but since we modified the source, I like to use ba, so I can reuse the source rpm should I need to compile again.]]>

Buslogic driver for RHEL4 update4 (2.6.9-39 kernel)

For the update4 (20060605) distro, the kernel version is 2.6.9-39, so the buslogic driver on VMware’s site doesn’t work anymore. You can use the one attached, but it’s not supported by VMware. Install Linux by following the instructions on their site.

This is obviously not supported by VMware, Inc. There’s also no guarantee that your VM will be stable, but I’d bet that it would be.

ESX 3.0 cdrom problem – won’t mount / won’t work for Guest

[root@wesx3 root]# mount /dev/cdrom /mnt/cdrom/
mount: /dev/cdrom: can’t read superblock from /var.log/messages
Apr 27 09:40:06 wesx3 modprobe: modprobe: Can’t locate module ide-cd Fix with the following:
1) remove the line from /etc/vmware/esx.conf by running:
nano /boot/kernelAppend = “hda=ide-scsi”
2) remove hda=ide-scsi from /etc/grub.conf using nano again:
nano /etc/grub.conf
3) reboot the machine. That’s it!]]>

Web access doesn’t work on new install or upgrade of ESX 3

You can run these commands:

esxcfg-vswitch -A serviceconsole vSwitch0

esxcfg-vswif -a -i 192.168.0.2 -n 255.255.255.0 -p serviceconsole vswif0

That should be it. The new interface is vswif0 rather than eth0.

This problem is common among upgrades that have 2 nics shared between the service console / vmkernel.

ESX VMkernel doesn’t load 0xbad0013

After install process completes, on first boot of ESX system the following error messages appear:

VGA: 297: VGA start b8000 end c0000 mapped start c00b8000 char height 16

VGA: 397:

VGA: 425: 0

Console: switching to colour VMNIX-VGA 80×25

VGA: 465: 0

Console: switching to colour VGA+ 80×25

WARNING: Mod: 2434: Initialization of vmkernel failed, status 0xbad0013

Mod: 4406: Waiting for vmklogger to dump log buffer…

Warning: Mod: 4429: Dumping vmkernel log buffer (5162 bytes):

after the rest of the Service console loads it indicates that a critical error and that the vmkernel didn’t load

We’re running on an HP DL385 (dual opeteron at 2.6 GHz) running the VMware Starter edition off of an array.

Strange – the solution of the problem was just to put the DIMMs into the right place – the memory was placed incorrectly as we didn’t read the decals on the box. hehe…