Hi everyone,
So I have been trying to get together some hands on 4.1 videos for you guys (and girls)
however KB1011292 has been my main reason for not upgrading.
What is KB1011292 I here you ask?:
"VMware View Composer 2.0.x is not supported in a vSphere vCenter Server 4.1 managed environment as vSphere vCenter Server 4.1 requires a 64 bit operating system and VMware View Composer does not support 64 bit operating systems.
VMware View 4.0.x customers who use View Composer should not upgrade to vSphere vCenter Server 4.1 at this time. Our upcoming VMware View 4.5 will be supported on VMware vSphere 4.1."
As you know the supported way of upgrading your vSphere enviroment is like this:
1) Upgrade vCenter
2) Upgrade ESX hosts
3) Upgrade vmware tools
4) Upggrade vm hardware version.
Therefore if you run VMware View 4 with composer your trip into 4.1 greatness is going to come grinding to a halt with step 1.
Having VDI is great however it makes upgrading a pain...so roll on VMware View 4.5 with your 64bit composer.
And for those not tide to VDI here is the Vsphere upgrade guide:
Upgrade Guide
Showing posts with label vmware view. Show all posts
Showing posts with label vmware view. Show all posts
Tuesday, 20 July 2010
Thursday, 6 May 2010
Using VMware View with Network cards as Removeable Devices
This is only going to be a quick on hopefully :)
For those that do not know vmware presents most of their nics as removeable/USB devices PCNET(Vlance),Intel e1000 and vmxnet,vmxnet2,vmxnet3 this is to allow the feature of "hot add" which is a great way off adding hardware to a VM without powering the machine off.
Today whilst playing around it was highlighted to me that some "adventurous" VM View users that had USB enabled used that oppurtunity to disable the network card. Forcing the intervention of the admin from the cloud to re-add the vnic
Heres a couple of ways around it:
1) Use the configuration options to add "devices.hotplug" = "false" like this:
*Also does not affect cpu/mem hotplug
2) Edit the *.vmx file and add:
3) Hide the "safelty remove hardware option" like this:
4) Use the "NoDisplayClass" to customize the driver *yuck!
Hope that helps someone out there!
Source:http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012225&sliceId=1&docTypeID=DT_KB_1_1&dialogID=64244650&stateId=0%200%2067543541
*NB:Using VMXnet3 does not disable hot plug as indicated in the KB
For those that do not know vmware presents most of their nics as removeable/USB devices PCNET(Vlance),Intel e1000 and vmxnet,vmxnet2,vmxnet3 this is to allow the feature of "hot add" which is a great way off adding hardware to a VM without powering the machine off.
Today whilst playing around it was highlighted to me that some "adventurous" VM View users that had USB enabled used that oppurtunity to disable the network card. Forcing the intervention of the admin from the cloud to re-add the vnic
Heres a couple of ways around it:
1) Use the configuration options to add "devices.hotplug" = "false" like this:
*Also does not affect cpu/mem hotplug
2) Edit the *.vmx file and add:
devices.hotplug = "false"
3) Hide the "safelty remove hardware option" like this:
4) Use the "NoDisplayClass" to customize the driver *yuck!
Hope that helps someone out there!
Source:http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012225&sliceId=1&docTypeID=DT_KB_1_1&dialogID=64244650&stateId=0%200%2067543541
*NB:Using VMXnet3 does not disable hot plug as indicated in the KB
Subscribe to:
Posts (Atom)