Posts Tagged ‘vmware’
Direct Launch, OpenGL 2.1, Bigger VMs Now In VMware Workstation 7.1 and Player 3.1 Public Betas
Almost as if to segue from my recent Virtumania Podcast episode about type 2 hypervisors, VMware has announced the release of the public betas for the latest versions of their popular Workstation and Player desktop products. Touting several new features and performance improvements, VMware Workstation 7.1 and Player 3.1 betas can now be downloaded from their VMware Beta Community pages.
I am downloading my copy as I write this post, but several new features have caught my attention.
- Open GL 2.1 support for Windows 7 and Vista guests
- Improved graphics support enabling high resolution videos in VMs
- Autologin for Windows Guests
- Inclusion of the OVF 1.0 command line tool to convert VMs to .OVF files for exporting to other hypervisors
- 8 way vCPU support in VMs
- up to 2TB virtual disks
- Direct Launch – drag icon to host desktop and seamlessly start an application inside a VM – even after closing VMware Workstation or Player.
- Support for Fedora 12 as a guest OS
- VMware Ace upgraded to version 3.7
Also, I can’t help but notice Known Issues from the Release Notes such as the following:
“Display
- Exiting FIFA 08 game on Windows 7 guests and hosts with Aero enabled, might cause the desktop wallpaper to turn black.
- There are known issues with the ATI Linux driver 10.2. VMware recommends that you use ATI Linux driver 9.11 for the best 3D user experience.”
Looks like I’ve got some new testing to do! (and maybe a new 3D games video to make!)
Copying more information from the Release Notes:
Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch
The vSphere Enterprise Plus vNetwork Distributed Switch (vDS) has been heralded as, and I might add lives up to it’s reputation of, an administrator’s time saver and single point of virtual networking configuration and visibility across many ESX/ESXi 4 hosts. However, the vDS presents some administrative challenges unique from the traditional vNetwork Standard Switch (vSS) that admins are used to. Specifically, since the vCenter 4 Server actually maintains the vDS configuration, some extra design thinking needs to be built into a vSphere 4 environment where a vDS will be used. If vCenter 4 Server itself will be a virtual machine in the environment with a vDS, the design gets even more involved.
There are a few possible problems to consider. In this post I’ll first cover (with the help of a several others) general VM and vCenter vDS networking issues, but along the way I’ll explore thoughts about designing around a vDS for keeping vCenter as a VM.
Restore Connectivity To ESXi 4 Management Network After Adding Second NIC
Managing and troubleshooting ESXi 4 can be a little alien when an administrator is used to the Service Console of ESX Classic. Specifically, troubleshooting remote connectivity to the ESX management interface after adding a second NIC involves local esxcfg-vswitch commands on ESX, but with ESXi the esxcfg commands are only available via the RCLI. Problem is you can’t use the RCLI if you lost remote management connectivity! Luckily, the local ESXi GUI lets you reconfigure your mistake and re establish remote connections.
Hit F2 on the ESXi Console and enter the System Configuration Menu
Choose to Configure Management Network > Network Adapters
24 Hour Timeout Prevents Removing ESX vNetwork Distributed Switch
http://kb.vmware.com/kb/1010718 explains the normal way for disabling and removing a VMware ESX/ESXi vNetwork Distributed Switch (vDS or DVS or VDS – LOL), but when I recently tried to do so I received the following error:
“The resource ‘1′ is in use. DVS [vDS Name] port 1 is reserved by to entity <not-found.> vnic 4000, type:vmVnic”
The screen shot shows the actual error I received.
After thinking about that message, I decided to check to see if any ports were in fact being used on the vDS. Although PortID 1 dvPortGroups did not show it being used as expected, other PortIDs were, in fact, in use. See image below.
I tried messing around with disabling the ports (blocking was the terminology in the vSphere Client, I believe) but I still could not delete the vDS. It was Saturday and I had family stuff to do so I reluctantly gave up at the time. However, 3 days later I was able to easily remove it via the Remove link on vDS Configuration screen just like I was supposed to be able to do all along. Needless to say I was a bit perplexed.
After researching I discovered that
Dallas Cowboys Virtualize New Stadium Servers With HP Converged Infrastructure
|
The first thing we were shown this week at HP Blades Day was a video about how the Dallas Cowboys have virtualized some of their server infrastructure in the new Cowboys Stadium. A shining example of HP’s Converged Infrastructure, Cowboys Stadium leverages VMware and HP Blades for consolidating the servers required to run the venue’s 200 concession stands. Since each concession stand requires it’s own Windows 2003 server, by virtualizing on HP Blades and VMware the Cowboys were able to implement only 16 physical servers. I’ve found it tough to visualize exactly what HP means by Converged Infrastructure at times, but Cowboys Stadium helps illustrate the big picture. Check out the three and a half minute video to also understand how several more HP Blades (outside of the virtual infrastructure) are used to operate the entire state of the art stadium. |
Dallas Cowboys Stadium and HP |
VM /ETC readers will probably recall that I love to report on the NFL and it’s teams use of virtualization and blade centers. I must say, as a man born in Philadelphia who is a long time Atlanta Falcons season ticket holder, I had to “do what’s right” and publish this post.
All rivalries aside, I find examples of popular events, teams, and venues such as Cowboys Stadium to be the most interesting real world virtualization implementations to reference.
Disclosure – I was introduced to this video during an all expenses paid blogging event at the HP Campus in Houston, TX.
VMware VCB To Be Replaced by VADP. Does That Mean vDR Is The VMware Alternative?
I received an email today from VMware addressed to all customers about the end of availability for VMware Consolidated Backup (VCB). Quoting from the beginning of the communication but not the entire message, it reads:
“The purpose of this letter is to inform you of our vSphere backup product strategy, ongoing enhancements, and end of availability plans for VMware Consolidated Backup.
VMware Backup Product Strategy
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP).”[omited]
I’ll go out on a limb and say that most of the VMware community will
Use Veeam FastSCP For Easy ESXi File Management
ESXi doesn’t have a Service Console like ESX. Therefore, you can’t SSH to the server without entering unsupported mode. That process may be a hassle if all you need to do is modify VM configuration files. Of ourse, you could use the Datastore Browser from the VI/vSphere Client, but to make file edits you would have to download a file to your desktop, edit it, and then upload the changed version back to ESXi again. On the other hand, with Veeam’s free FastSCP editing files on ESXi datastores is easy.
To be clear, you can’t edit configuration files of the ESXi host itself with FastSCP, but there really should not be a need to do so. That’s one of the benefits of ESXi not having a Service Console!
Download FastSCP here. You will have to register with Veeam first, and the registration form will not accept a personal email. I’m guessing there is some kind of lead qualification strategy and support registration involved with this requirement for download, but I learned a work address is unavoidable. I tried to use my gmail address but received a message similar to “you must use a company email address.” The registration process ends with a confirmation email to be acknowledged before you can download, so making up a fake email is futile. Hey, it’s a small price to pay for a free, quality admin tool.
After you install FastSCP you’ll discover you have access to a trial period of Veeam Backup and Replication. I suggest exploring










