Thin Client and Virtual Machines Thread, VMware vSphere in Technical; Along with your ISCSI traffic being on a separate p-network or vlan. vMotion traffic should also be separated at least ...
3rd June 2009, 04:15 PM #16
Along with your ISCSI traffic being on a separate p-network or vlan. vMotion traffic should also be separated at least onto another vlan as the VM being vMotioned transfers its memory in plaintext across the vmotion network.
You can insert rootkits in vmotioning VMs, in turn these can effect VMs on the new box the infected VM can move to.
ESX eats network cards. The more the better.
Last edited by Theblacksheep; 3rd June 2009 at 04:21 PM.
4th June 2009, 02:06 PM #17
- Rep Power
Just thought it was odd, as i didnt have to with v3.5...
Anyway, found the licence stuff on their website, bit of a sod to find! lol.
So, for virtualising a few of our lighter servers (IIS, Print, AV, ect; ) + some test beds, will the following suffice?
Think i already know the answer:
2x Quad Core Xeon E5410 @2.33Ghz
2x PCI-E teamed Gig (VM Network, VMKernal, Service Console)
1x PCI-E Gig NIC (un-used at the moment)
137Gb internal SAS
100Gb iSCSi target
300Gb iSCSI target
If it turns out to be successful, i think i'll look into converting our spare blade into an ESXi server as well and look into ways to cluster it all for failover.
By somabc in forum Thin Client and Virtual Machines
Last Post: 22nd April 2009, 06:25 PM
By wesleyw in forum Thin Client and Virtual Machines
Last Post: 6th March 2009, 04:06 PM
By itgeek in forum Windows
Last Post: 17th November 2008, 04:06 PM
By Ric_ in forum General Chat
Last Post: 12th January 2006, 04:32 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)