VMware

lmilev

lmilev's Profile

  • Name: Lyuben Milev 
  • Email: (Private)
  • Member Since: Jul 1, 2008
  • Last Logged In: Jan 8, 2010 8:03 AM
  • Status Level: Novice Novice (20 points)
  • VMware Employee: VMware Employees Yes

lmilev's Latest Content

Wow!

Today, I was so excited that when I saw the VMware Fusion Homepage http://www.vmware.com/products/fusion with the large Fusion 3 Logo I had hard time to read "October 27" and was left with the impression it is already released!

I might actually buy a Mac for personal use after all!

0 Comments Permalink

People frequently ask several questions I decided to note here.

Q: vSphere's 4.0 Link Mode support?

A: Yes.

Q: My XYZ vendor's SRA version a.b.c is not shown in SRM 4.0 compatibility matrix?

A: Vendors usually release an updated version of their SRA relativelly soon after an SRM release. One could contact their vendor to ask for an ETA.

P.S. Hey, it's my first blog post!

0 Comments Permalink

It was the release of VMware Workstation 6 when I first looked into the command-line reference of VMware Workstation and Player, their config settings, etc.

Here is what made me interested:

  • I could create a command line that will POWER ON a vm and put it into a FULL SCREEN.

Great I told myself. Then I searched for which key is supposed to put the VM in, out of full screen.

Along the way I found that there is switch between VM key combination.

OK, is this a puzzle?! Yes and No. But how about redirecting user on a OS that has VMware Workstation installed to a VM automatically?

Work with your imagination... Here are the high-level components you'll need to create such an OS user account (when logged in, will automatically be put in front of a running VM in FULL SCREEN):

1. A custom shell to start when a user logs into the OS.

2. That shell doesn't allow certain key combinations to be processed by active application.

3. Configure those certain key combinations from VMware Workstations config file to be something that in practice is not needed by an end-user.

4. The shell needs to know which VM to run when it loads.

5. The shell needs to power on the VM in full screen.

6. The shell needs to logoff from the underlying OS when it detects the VM has been shutdown/suspended.

Viola! This is my imaginery wonder for today.

0 Comments Permalink

Brainstorm with co-workers, get your questions answered, build status with your responses.

Write your own drafts, invite selected collaborators, or leave it open for all to pitch in.

lmilev's Blogs

Communities