Category: General

XenServer CPU information.

A resource pool was transferred and missing where specifics to the cpus.

The command needed for this : lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
Stepping: 2
CPU MHz: 2600.082
BogoMIPS: 5200.16
Hypervisor vendor: Xen
Virtualization type: none
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 25600K


No more vRAM gouging!

I had been away for a long time due to workloads being crazy.  A good thing overall but it does get in the way of writing.

What better way to mark a return then VMwares announcement they have ended vRAM licensing! I never understood why VMware didn’t think this one out. Probably thought they could make a great deal of money but ended up loosing market share to Microsoft. It is interesting this announcement comes a week after the release of the RTM of 2012.

This will keep interest in VMware but in some cases it might be too late as 2012 with Hyper-V V3 looks very promising.

Time will tell.
CRN Article

CIO Article

This is not exactly a virtulization topic. However, I did run into a situation where I was trying trying to setup a machine with a six gigabyte WIM file. The network wouldn’t allow me to connect to remote storage to copy the WIM file to the new machine. Rather then waiting for networking to solve the problem; I decided to use a USB stick.  However, when I tried to copy the file; I received an error which stated:

The file is too large for the destination file system

All right? This is a 16 gigabit USB! How is this possible?  It has enough free space!

And then I remembered it was probably formatted for FAT32.

This left two choices.

1) Reformat the USB for NTFS

2) Convert the filesystem.

Probably the best thing to do would be to reformat it but I didn’t feel like copying the contents to another drive so I decided to run the convert command instead.

convert drivename: /fs:ntfs

The file system converted and I was able to copy my large WIM file to the USB.

Happy New Year!

A new year and I start with a backlog of posts.   Topics will include performance,  licensing, data sharing and some utilities.

I hope everybody has a great year!

RIP Steve Jobs

Not a virtualization topic. However, it’s not wrong to acknowledge a person who was able to change society.

Steve Jobs was many things. He has his good moments. He had his jerk moments.

Love him or hate him; nobody can’t argue he had vision for what things could be.

Nobody deserves to go the way he did.  I am happy he doesn’t have to pretend to be healthy for the sake of Apple anymore.

RIP Mr. Jobs

Virtualization is fun but it can cause legal problems if you don’t look at your vendors rules for licensing.

As the world turns to virtual computing, the need for hardware reduces. People might think “OH BOY, I can purchase one copy of the OS and use it for as many virtual machines as I want.  After all I am running it on the same computer!”

It would be great if that was the case but Microsoft obviously doesn’t want to loose money. They have changed the rules about virtualizing their operating systems and some of their products. Some cases, they are nice while others?….

If you plan to use Microsoft in the world of virtual machines, you should review their licensing guide lines.

Microsoft Volume Licensing and Virtualization

In fact, you should review them from time to time as they do change.

One area often overlooked are the client access licensing.   You will need them.