BSA 728x90 Center Banner

vSphere 5 Hardware Version 8 & New vCPU Config for Licensing Trickery

With vSphere 5 comes a new virtual machine hardware version... version 8. The vCPU configuration has changed a bit in the new layout and you can totally see why. When creating a new VM, or editing virtual machine hardware, you can now choose a virtual socket and core allocation to the VM instead of just choosing a "vCPU count".

 

The amount of vCPU's you can distribute is based on the amount of physical cores available on the host. For instance, I have a single Quad Core Intel chip on each of my home lab servers. That means a VM can be configured with up to 4 available vCPUs in an array of different options. Why would VMware do this?? For application licensing of course! If you have an application that needs some horsepower but is licensed by the socket, no difference if it is virtual or physical, you can get around that by applying multiple cores to a single socket. Think about the money you could save moving from a 12 vCPU VM in vSphere 4 with 12 licensed sockets to a single vCPU socket with 12 cores in vSphere 5!

Read more: vSphere 5 Hardware Version 8 & New vCPU Config for Licensing Trickery

Final RSS Feed Changes - New Feedburner Feed Enabled

OK... I swear this is THE LAST blast of RSS crap.

 

I have had people complaining of the double posts on RSS feeds so here is my attempt at a standard.

 

Please disregard my previous post on changing RSS feeds. I had no clue about Feedburner and that's where I'm building the new feed. This is the LAST blog post that will go out on all Syndicates so you may have double posts on this one too. Please make sure your RSS feed is updated and pointing towards my new feedburner address:

 

http://feeds.feedburner.com/KendrickColeman

 

Read more: Final RSS Feed Changes - New Feedburner Feed Enabled

New RSS Feed Syndicate To Remove Multiples

Hey Everyone. I've gotten lots of complaints lately about my postings showing up twice in some people's RSS feeds. I think I have solved the problem. It existed because I had two syndicates on here and that was causing the double postings.

 

I have removed one of them and am now using the default & native Joomla syndicate that can be found in the upper right hand corner on the home page which has replaced the old syndicate. Some people might be using the old RSS feed address, but that has now been removed. To continue getting RSS feed updates make sure you are pointing to only ONE of these addresses:

 

CHANGED!!

http://feeds.feedburner.com/KendrickColeman

http://kendrickcoleman.com/index.php?/feed/rss.html
or
http://kendrickcoleman.com/index.php?/feed/atom.html

 

Read more: New RSS Feed Syndicate To Remove Multiples

Realtek 8111E Works With VMware vSphere 5

EDIT 9/26/2013--- REALTEK DRIVERS ARE NO LONGER A PART OF VSPHERE 5.5!! If you would like to integrate the Realtek Drivers in the ESXi 5.5 ISO, please follow Erik's article -  Adding Realtek R8168 Driver to ESXi 5.5.0 ISO

 

I've had this one backlogged but finally got around to test it out. In my home lab, I am using the Shuttle SH55 that has a Realtek 8111E 1Gb on-board NIC.

 

Surprisingly enough, I see google keywords coming to my site to look at my homelab using the keywords Realtek and vsphere. With vSphere 4, there were some articles that I highlighted in my home lab post that pointed towards vm-help.com that used a new oem.tgz to inject Realtek drivers into the ESXi installer. The problems with injecting the oem.tgz drivers is that it wasn't native and was prone to problems. When I had a VM using that NIC with vSphere 4.1, pings were lost and things seemed to just disappear. Thus, I made the decision to skip out on using the on-board NIC and continued to use the Intel NICs that are on the HCL.

 

Well, the good news is that the Realtek NIC is working with vSphere 5 build 381646 (beta build). The bad news is that the vSphere HCL hasn't been updated for vSphere 5 so who knows if it's really supported.

 

Read more: Realtek 8111E Works With VMware vSphere 5

VCAP4-DCA Exam Experience and Tips

It was almost 1 year ago today that I published my VCAP4-DCA Landing Page. Back on July 16th, I finally got around to taking my VCAP4-DCA exam after the struggle with my VCAP Madness and accidentally passing the VCAP4-DCD.

 

It took exactly 9 business days to get the email from the certification team, and they do a good job with scaring the crap out of you. The email reads as such:

Hello,

Thank you for participating in the VMware Certified Advanced Professional program.  Please find your VCAP4-DCA score report attached.


Kind Regards,

The VMware Technical Certification Team

 

Wow! How scary is that? They make you open an attachment to see if you passed! Loading the PDF is the most nervous 3 seconds of your life, but it's worth the wait when you see that word "PASS". Whew...

 

 

Read more: VCAP4-DCA Exam Experience and Tips

Virtual HD Audio Hardware in vSphere 5

I was in the midst of getting a few play VMs setup for my nested vCloud Director 1.5 environment and I ran into something new. I grabbed 2 linux distros from bagside.com because all of the distros there are top notch and have VMware tools already installed which makes life much easier.

 

These machines won't boot up because they were created with VMware Workstation. I have the vCenter Converter 5 public beta (which i highly suggest checking out) that can convert virtual machines while automatically upgrading them to HW v8. After the conversion, I looked at the virtual hardware and saw a new piece called "HD Audio".

 

Read more: Virtual HD Audio Hardware in vSphere 5

Thanks John

Today is a day worth celebrating. John Troyer is a social media icon at VMware. John is responsible for the weekly VMTN podcasts, the Planet V12N RSS feed, and the famed vExpert Program. Today is also John's birthday.

 

John's dedication is valuable to all of us that partake in VMware's social media presence. I've been fortunate enough to talk to John several times and it's always a fun time. Even though my neck may hurt from looking up because John is like 9 feet tall! Laughing

 

Read more: Thanks John

Indy Demo Days 7/28 - It's Like A Mini VMworld

Next week on July 28th, make sure you make the trip to Indianapolis IN for the 4th annual VMware User Group Demo Days! This is a fantastic event that truly feels like a mini VMworld.

 

This is no ordinary VMUG. There will be some great sessions with some great speakers as well: David Davis, Scott Lowe, Mike Laverick, and Vaughn Stewart to name a few! There are also going to be hands on labs, food, and more! I do have to say thank you to Frank Seal, an organizer for this event, who asked me to be a speaker as well a few months back.

 

Read more: Indy Demo Days 7/28 - It's Like A Mini VMworld

vSphere 5 Brings VMKernel Port Binding To The GUI

When I first started testing vSphere 5 in my home lab, I began from scratch. One of the steps that was relatively familiar was binding VMKernal adapters to the physical NICs for iSCSI use.

 

If you have NICs that have iSCSI offload capabilities without having to use the Software iSCSI Adapter, then you are used to using a command similar to this:

esxcli swiscsi nic add -n vmk2 -d vmhba34

 

You can watch more on it here How to configure iSCSI Port Binding on vSphere 4

 

Read more: vSphere 5 Brings VMKernel Port Binding To The GUI

vSphere vCenter 5 Design Considerations

A few days ago I posted vCenter 5 - To Appliance or Not? talking about using the virtual appliance. I'm glad that article has been popular because it's a very important decision to make as you move forward with vSphere 5. As I move forward with my choice of using the original Windows installer, here are some design considerations to keep in mind.

 

During my beta testing for vSphere 5, i stuck the vCenter ISO into my existing vCenter and started going install crazy. I upgraded vCenter to version 5, installed auto-deploy, log collector, web services, update manager, and the whole shabang. It wasn't until one day when I had to reboot my vCenter VM that everything became clear. Upon reboot, my vCenter service failed to start.

 

I took a gander at the logs thinking it would be a DB miscommunication and there was an entry with something along the lines of failure to lock a socket. It makes perfect sense. vCenter services depend on port 80 and I installed vCenter Web Services which also defaults to port 80. Since vCenter Web Services was already in use of port 80, the service wouldn't start. I stopped all the IIS services and restarted the vCenter service and all was well again. Therefore, I started to think of what the best design practice should be for vCenter components.

 

Read more: vSphere vCenter 5 Design Considerations

Page 18 of 32

Related Items

Related Tags