Memory Limits on Microsoft OS

Physical Memory Limits: Windows 8

The following table specifies the limits on physical memory for Windows 8.

Version	Limit on X86	Limit on X64
Windows 8 Enterprise	4 GB	512 GB
Windows 8 Professional	4 GB	512 GB
Windows 8	4 GB	128 GB

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.

Version	Limit on X64
Windows Server 2012 Datacenter	4 TB
Windows Server 2012 Standard	4 TB
Windows Server 2012 Essentials	64 GB
Windows Server 2012 Foundation	32 GB
Windows Storage Server 2012 Workgroup	32 GB
Windows Storage Server 2012 Standard	4 TB
Hyper-V Server 2012	4 TB

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Version	Limit on X86	Limit on X64
Windows 7 Ultimate	4 GB	192 GB
Windows 7 Enterprise	4 GB	192 GB
Windows 7 Professional	4 GB	192 GB
Windows 7 Home Premium	4 GB	16 GB
Windows 7 Home Basic	4 GB	8 GB
Windows 7 Starter	2 GB	N/A

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version	Limit on X64	Limit on IA64
Windows Server 2008 R2 Datacenter	2 TB
Windows Server 2008 R2 Enterprise	2 TB
Windows Server 2008 R2 for Itanium-Based Systems		2 TB
Windows Server 2008 R2 Foundation	8 GB
Windows Server 2008 R2 Standard	32 GB
Windows HPC Server 2008 R2	128 GB
Windows Web Server 2008 R2	32 GB

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit on X86	Limit on X64	Limit on IA64
Windows Server 2008 Datacenter	64 GB	1 TB
Windows Server 2008 Enterprise	64 GB	1 TB
Windows Server 2008 HPC Edition		128 GB
Windows Server 2008 Standard	4 GB	32 GB
Windows Server 2008 for Itanium-Based Systems			2 TB
Windows Small Business Server 2008	4 GB	32 GB
Windows Web Server 2008	4 GB	32 GB

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version	Limit on X86	Limit on X64
Windows Vista Ultimate	4 GB	128 GB
Windows Vista Enterprise	4 GB	128 GB
Windows Vista Business	4 GB	128 GB
Windows Vista Home Premium	4 GB	16 GB
Windows Vista Home Basic	4 GB	8 GB
Windows Vista Starter	1 GB

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit on X86	Limit on X64
Windows Server 2003 R2 Datacenter Edition	64 GB (16 GB with 4GT)	1 TB
Windows Server 2003 R2 Enterprise Edition	64 GB (16 GB with 4GT)	1 TB
Windows Server 2003 R2 Standard Edition	4 GB	32 GB

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit on X86	Limit on X64	Limit on IA64
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition	64 GB (16 GB with 4GT)	1 TB	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition	64 GB (16 GB with 4GT)	1 TB	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition	4 GB	32 GB

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit on X86	Limit on X64	Limit on IA64
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition	64 GB (16 GB with 4GT)	X64 1 TB	1 TB
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition	64 GB (16 GB with 4GT)	X64 1 TB	1 TB
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition	4 GB	32 GB

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit on X86	Limit on IA64
Windows Server 2003, Datacenter Edition	64 GB (16 GB with 4GT)	512 GB
Windows Server 2003, Enterprise Edition	64 GB (16 GB with 4GT)	512 GB
Windows Server 2003, Standard Edition	4 GB
Windows Server 2003, Web Edition	2 GB
Windows Small Business Server 2003	4 GB
Windows Compute Cluster Server 2003		32 GB
Windows Storage Server 2003, Enterprise Edition	8 GB
Windows Storage Server 2003	4 GB

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version	Limit on X86	Limit on X64	Limit on IA64
Windows XP	4 GB	128 GB	128 GB (not supported)
Windows XP Starter Edition	512 MB	N/A	N/A

Physical Memory Limits: Windows Embedded

The following table specifies the limits on physical memory for Windows Embedded.

Version	Limit on X86	Limit on X64
Windows XP Embedded	4 GB
Windows Embedded Standard 2009	4 GB
Windows Embedded Standard 7	4 GB	192 GB

Vmware Guest mount USB external Disk

USB can be used by Guest OS by editing the settings of a Virtual Machine and then choosing the "Hardware" TAB Once you are at the HARDWARE Tab you can click "ADD" and select a USB Controller.

Once you have added a USB Controller you then repeat the same process, except this tieme add a USB Device instead of a controller.

You will see any attached USB devices in a list to choose from.

Once added you then need to open the console of the Virtual Machine, and Mount it to the USB connector. (the little USB icon at the top of the Console Window).

Login the windows system and it should find the disk automaticaly.

Linux partitioning with fdisk

I start fdisk from the shell prompt:

# fdisk /dev/hdb

which indicates that I am using the second drive on my IDE controller. (See Section 2.1.) When I print the (empty) partition table, I just get configuration information.

Command (m for help): p Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes

I knew that I had a 1.2Gb drive, but now I really know: 64 * 63 * 512 * 621 = 1281982464 bytes. I decide to reserve 128Mb of that space for swap, leaving 1153982464. If I use one of my primary partitions for swap, that means I have three left for ext2 partitions. Divided equally, that makes for 384Mb per partition. Now I get to work.

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

Next, I set up the partition I want to use for swap:

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

Now the partition table looks like this:

Device Boot Start End Blocks Id System /dev/hdb1 1 196 395104 83 Linux /dev/hdb2 197 262 133056 83 Linux

I set up the remaining two partitions the same way I did the first. Finally, I make the first partition bootable:

Command (m for help): a Partition number (1-4): 1

And I make the second partition of type swap:

Command (m for help): t Partition number (1-4): 2 Hex code (type L to list codes): 82 Changed system type of partition 2 to 82 (Linux swap) Command (m for help): p

The end result:

Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 196 395104+ 83 Linux /dev/hdb2 197 262 133056 82 Linux swap /dev/hdb3 263 458 395136 83 Linux /dev/hdb4 459 621 328608 83 Linux

Finally, I issue the write command (w) to write the table on the disk.
to format disk:

mkfs.ext3 (for ext3 file system)
mkfs.ext4 (for ext4 file system)
mkfs.swap (for swap file system)

VMware Import Export OVA files

About OVF (Open Virtualization Format)

It is an open standard used across different virtualization platform. An OVF virtual machine consists of a directory containing virtual machine files and a file describing them.

Read more …
http://en.wikipedia.org/wiki/Open_Virtualization_Format

About OVA (Open Virtualization Appliance)

It is a single compressed file containing the contents of an OVF directory.

Read more …
http://www.vmware.com/technical-resources/virtualization-topics/virtual-appliances/ovf

VMware OVF tool

VMware OVF tool is a command line utility that supports import and export of OVF packages to and from vSphere infrastructure.

Download Tool – http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/ovfDocumentation – http://www.vmware.com/support/developer/ovf/

ExportC:\Program Files\VMware\VMware OVF Tool>ovftool.exe "vi://username:password@vCenterIP:443/DataCenter_Name/vm/Demo-W7-VM" "C:\VM-Backup\Demo-W7-VM.ova"

ImportC:\Program Files\VMware\VMware OVF Tool>ovftool.exe "--datastore=datastore1" "--network=VM-Network" "C:\VM-Backup\Demo-W7-VM.ova" "vi://username:password@vCenterIP/DataCenter_Name/host/Cluster_Name/hostIP"

VMware Manually Assigning a MAC Address to Virtual machine Cisco CUOM

Operations Manager supports VMware ESX 3.5, ESXi 4.x, and ESXi 5.0. Operations Manager musthave the same system resources available to it, inside the virtualization environment that it has for astandard (nonvirtual) installation.While determining the performance of Operations Manager in your virtual setup, you should be awarethat the VMware instance will use some system resources that would normally be available to OperationsManager in a standard installation. Additional requirements for running Operations Manager in avirtualization environment might vary with your environment and system load.Operations Manager can be installed on a virtual machine with dynamic MAC address for evaluation.However, you must configure the virtual machine with a static MAC address to purchase the permanentlicense for Operations Manager.

The static MAC address is required because licensing uses node-locking technology. The license file can

only be used with the static MAC address that you supply.

Note The static MAC address must be within the following range: 00:50:56:00:00:00 to 00:50:56:3F:FF:FF.

To set up a static MAC address:

Step 1 Power down the virtual machine.

Step 2 In the Inventory panel, select the virtual machine.

Step 3 Click the Summary tab and then click Edit Settings.

Step 4 In the Hardware list, select Network Adapter.

Step 5 For MAC address, select Manual.

Step 6 Change the current MAC address of the virtual machine to a static MAC address in the following range:

00:50:56:00:00:00 to 00:50:56:3F:FF:FF.

Step 7 Click OK.

Enable Automatic Start Up for Guest OS on VMware ESX

18 July, 2008 at 2:36 pm by Phil Wiffen · Filed under Design and Usability, Virtualisation

This one had me tearing my hair out. We needed to enable auto startup on some of our Virtual Machines on the VMware ESX server, but I couldn’t for the life of me work out how. After a stupid amount of Googling around, turning up nothing, I actually RTFM! Page 177-178 had the answers 

Here’s how to do it:

Launch the Virtual Infrastructure Client. If you don’t have it, just http:// to your VMware ESX host and grab it from the front page.

Go to the Configuration tab of your ESX Server, then click on Virtual Machine Startup/Shutdown.

By default (I’m pretty sure) automatic startup is disabled. To enable it, click on “Properties…” on the far upper right of the window.

You’ll now see this window:

Check/Tick “Allow virtual machines to start and stop automatically with the system”.

Now, this is the bit where I nearly cried…

You know you want to “enable” your Guest OSes to automatically boot, but how? I tried clicking and dragging, right clicking for a context menu to enable “Automatic start up” and gave up.

Turns out, you need to click on the Guest OS you’d like to enable, and then click “Move Up” until it sits underneath the “Automatic startup” title. Argh!

I really hope this helps someone out! 

Controllo bad blocks sul disco con linux

badblocks is a Linux utility to check for bad sectors on a disk drive (A bad sector is a sector on a computer's disk drive or flash memory that cannot be used due to permanent damage or an OS inability to successfully access it.). It creates a list of these sectors that can be used with other programs, like mkfs, so that they are not used in the future and thus do not cause corruption of data. It is part of the e2fsprogs project.

It can be a good idea to periodically check for bad blocks. This is done with the badblocks command. It outputs a list of the numbers of all bad blocks it can find. This list can be fed to fsck to be recorded in the filesystem data structures so that the operating system won’t try to use the bad blocks for storing data. The following example will show how this could be done.

From the terminal, type following command:

$ sudo badblocks -v /dev/hda1 > bad-blocks

The above command will generate the file bad-blocks in the current directory from where you are running this command.

Now, you can pass this file to the fsck command to record these bad blocks

$ sudo fsck -t ext3 -l bad-blocks /dev/hda1
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Check reference counts.
Pass 5: Checking group summary information.

/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****

/dev/hda1: 11/360 files, 63/1440 blocks

If badblocks reports a block that was already used, e2fsck will try to move the block to another place. If the block was really bad, not just marginal, the contents of the file may be corrupted.

Looks at badblocks man pages for more command line options.