Skip to main content

Posts

Showing posts with the label Virtualization

Great 6-part article about server memory architecture & subsystem, UMA, NUMA, DDR4 and how to optimize for performance

I was just surfing about and was reading about PernixData releaseing FVP v2.5 in a blog , and my attention was directed to a great 6-part article about Server memory architecture, UMA, NUMA, memory subsystems, DDR4 and how to optimize memory for performance by Frank Denneman - you'll find it here:  http://frankdenneman.nl/2015/02/18/memory-configuration-scalability-blog-series/

VMware Virtual SAN

Just found whats looksl like a good article about VMware Virtual SAN. Putting a link her so I can go back to read all of it later when I have time. Article: VMware Arena - VMware Virtual SAN : Basics of VSAN

WHATS NEW in VMware vSphere 5.1

I found a nice blog article listing new features in vSphere 5.1. The main stuff (taken from the article) was: vRAM has been killed. vSphere is again licensed per CPU just as it was before vSphere 5.0. The licensing whitepaper is here. Enhanced vMotion allows you to combine a vMotion and Storage vMotion into a single operation, without shared storage. vSphere replication has been decoupled from SRM, and released as an available feature of every vSphere license from Essentials Plus through Enterprise Plus New VMware vSphere Storage Appliance 5.1 for SMBs New backup solution named vSphere Data Protection replacing VDR. You'll find the entire article over at the VMware VCP blog

eth0+N headache in linux with virtual templates

If you keep getting eth1 instead of eth0 as your main ethernet interface on a (newer) linux template/clone in a virtualized environment it's most likely because your udev rules is in affect and creates a new eth1 since eth0 is already defined and bound to the clone/template source's MAC address. This can be fixed in a couple of ways (in your template/clone source image): 1) You can delete the ' SUBSYSTEM ' line in your  /etc/udev/rules.d/70-persistent-net.rules : Edit the rules files   vi /etc/udev/rules.d/70-persistent-net.rules Delete the SUBSYSTEM line(s), feel free to also delete the comment about PCI device just above: # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION==...

Hyper-V and Virtualbox is a 'no go' together on a Windows 8 PC

I just tried to run VirtualBox on my Windows 8 computer where I already had activated Hyper-V. That was a 'no go' - it borked out with missing VT-x support: You simply can't run Hyper-V and VirtualBox simultaneously, as any application that uses the virtualization-specific instruction sets on the CPU  (Intel VT-x in my case)  does so alone and therefore locks other programs out of using them. Too bad, but probably security-wisely good. 

VMware ESX3 and Windows XP

http://virtrix.blogspot.com/2007/09/vmware-installing-windows-xp-on-esx.html QuickTip: When using the BusLogic driver instead, you can download & use a preconfigured .flp file from the VMware site: http://download3.vmware.com/software/vmscsi-1.2.0.4.flp .