Author Topic: Help me understand Virtual Machine [VMWare] (Read 37966 times)

tomos · « **on:** August 17, 2012, 09:11 AM »

OK

I've installed VMWare Player
I have my winXP iso ready to roll

I've been reading the documentation, it's confusing, because there seems to be many versions/aspects to VMWare. But mainly confusing cause they dont cater to users who dont already understand (there's got to be a name for that - insider-manual-syndrome maybe).

I understand it's going to be a completely separate virtual install, but I'm not sure if this completely seperate (virtual) machine can see the real machine, and vice versa.

What I dont know (so far) is:

1) I suspect ideally an empty partition would be good for the virtual machine(s) - but dont know.
2) I presume it will create a virtual drive anyway?
3) if yes to #2: can it create virtual partitions on the virtual drive?
4) if yes to #3: can files on virtual partitions be accessed from outside the virtual OS?
5) within the virtual OS, will I be able to access and modify files from the "real" machine i.e. outside of the virtual machine

Any help much appreciated

tomos · « **Reply #1 on:** August 17, 2012, 09:17 AM »

Possibly relevant:

I'm using a single Windows 7 machine (no network)
I do have an external drive that I could store files on for sharing with both OS's.

Or could I network the two machines: real/virtual (remember here: I'm a noob - also with networking :p)

Josh · « **Reply #2 on:** August 17, 2012, 09:19 AM »

1) I suspect ideally an empty partition would be good for the virtual machine(s) - but dont know.
2) I presume it will create a virtual drive anyway?
3) if yes to #2: can it create virtual partitions on the virtual drive?
4) if yes to #3: can files on virtual partitions be accessed from outside the virtual OS?
5) within the virtual OS, will I be able to access and modify files from the "real" machine i.e. outside of the virtual machine
-tomos (August 17, 2012, 09:11 AM)

1. You can use an empty partition on tools like VMware workstation. The player is limited to a virtual drive which is created when you create a new player image. Workstation can use a physical partition or other disk.
2. Yes, you will be prompted to create a virtual drive on VM creation.
3. Yes, you can partition the virtual drive just like a normal disk.
4. Yes, if you enable sharing within VMware
5. Again, you have to enable sharing which is done once you install the VMware tools.

VMware workstation provides greater flexibility and control over the VM. Player images are restricted to certain types of virtual hardware and settings. Workstation is designed for a more full-fledged image and setup a "virtual network" on the host system. Workstation is designed when you don't have a VMware VSphere server to play with.

mouser · « **Reply #3 on:** August 17, 2012, 09:33 AM »

VmWare *Player* is not what you want; You need the VmWare "Workstation" tool (not free), or one of the free alternative virtual machine tools, like VirtualBox.

Although I use VmWare myself, seeing as how you are just experimenting, VirtualBox seems the better route than buying VmWare Workstation.

1) I suspect ideally an empty partition would be good for the virtual machine(s) - but dont know.

no. these tools create everything they need in normal files. so when you run the program and create a new virtual machine, it will create a very large file (it could grow to be several gigabytes in size) that will simulate the hard drive of the virtual computer. Everything is stored in normal files.

3) if yes to #2: can it create virtual partitions on the virtual drive?

yes; it is basically going to simulate everything -- a partitionable hard drive, a bios, EVERYTHING. it's really quite remarkable.

4) if yes to #3: can files on virtual partitions be accessed from outside the virtual OS?
5) within the virtual OS, will I be able to access and modify files from the "real" machine i.e. outside of the virtual machine

the answer is that you can access files in both directions -- but not without some work. different virtual machine software handle this differently. for vmware, if you are using windows operating system as your host (real) pc and simulated pc, it will install special utilities to let you drag and drop files; if you are using linux it's more complicated.

tomos · « **Reply #4 on:** August 17, 2012, 09:44 AM »

thanks Josh

VmWare *Player* is not what you want; You need the VmWare "Workstation" tool (not free), or one of the free alternative virtual machine tools, like VirtualBox.
-mouser (August 17, 2012, 09:33 AM)

why do you say that mouser? (Josh's reply makes it sound quite usable). Is it because I mention wanting to use files outside the VM?
I may want to use it for actual work; initially I want to do a couple of test installs, also to try run an older app that doesnt work for me on Win7.

ps. back later ;-)

Josh · « **Reply #5 on:** August 17, 2012, 09:50 AM »

The question is do you plan to use the tool for more than a single machine? If not, then you do not need more than VMware player.

mouser · « **Reply #6 on:** August 17, 2012, 09:55 AM »

I stand corrected regarding VmWare Player. From the web, regarding VmWare Player:

In the latest version it can both create and edit virtual machines while it earlier could only possible to run pre-built VMs.

It used to be that VmWare Player could not be used to create virtual machines, only run those created by others. But it seems the new version can create them too -- that's very cool.

Renegade · « **Reply #7 on:** August 17, 2012, 10:19 AM »

I stand corrected regarding VmWare Player. From the web, regarding VmWare Player:

In the latest version it can both create and edit virtual machines while it earlier could only possible to run pre-built VMs.

It used to be that VmWare Player could not be used to create virtual machines, only run those created by others. But it seems the new version can create them too -- that's very cool.
-mouser (August 17, 2012, 09:55 AM)

Thanks for that. I have VMware Workstation, and really didn't want to pay to upgrade...

Jibz · « **Reply #8 on:** August 17, 2012, 11:54 AM »

Interesting .. anyone have some insights into how VMware player compares to VirtualBox?

vlastimil · « **Reply #9 on:** August 17, 2012, 12:19 PM »

VMWare Player is a feature-limited VMWare Workstation. The most notable feature that is missing in the Player is snapshots. Snapshot allow you to revert to a previous state, which is very useful when repeatedly testing your software in a controlled environment.

Without the snapshots, VMWare Player is not usable for convenient software testing. But if you just want to use a different OS, by all means, get and use the Player, its compatibility and performance are top class.

Shades · « **Reply #10 on:** August 17, 2012, 12:22 PM »

My anecdotal view is this: the portable version of VirtualBox that I tried was not that nice to work with. The VMWare Player v3+ was a lot smoother in creating and using a virtual setup.

Not sure about the speed with which a virtual setup is executed/handled in both environments. I don't think one is substantially faster than the other in day-to-day use. I did feel at the time that VirtualBox gave me a more hands-on experience.

Then again, I was also pressed for time at that moment so I went with the easiest one. As far as I know VirtualBox can work with a virtual setup created by VMWare and vice versa.

Jibz · « **Reply #11 on:** August 17, 2012, 12:46 PM »

Thanks for the comments

.. the lack of snapshot feature would definitely make it less useful for me.

40hz · « **Reply #12 on:** August 17, 2012, 12:48 PM »

I'm generally bullish on F/OSS projects. DOSBox and VirtualBox are both workable for casual to semi-serious use. But VMWare Workstation is a far better product if you have more complex requirements or do a lot of software testing.

I tried DOSBox and VirtualBox. I bought VMWare Workstation.

YMMV.

Renegade · « **Reply #13 on:** August 17, 2012, 01:00 PM »

Thanks for the comments .. the lack of snapshot feature would definitely make it less useful for me.
-Jibz (August 17, 2012, 12:46 PM)

Don't be so quick there. You can simply copy the files at a given point, and then you have a "snapshot". Yeah, might be a bit of a pain, but it still works. You need to have some rather complex requirements before the VMware snapshots are useful.

And I also bought a VMware Workstation license. So, I'm not trying to push anything there. VMware is fantastic. The question is whether you need those additional features.

(I remember using Ghost to restore machines for testing... That was a while ago.

)

40hz · « **Reply #14 on:** August 17, 2012, 01:36 PM »

If you can spare about 25 mins and would like to watch a really good hands-on for VirtualBox, take a look at Eli the Computer Guy's video on YouTube:

You may find the (usually) free VirtualBox software all you want or need.

Note: He also has a good intro to both virtualization and cloud computing. I often drop copies of these off with people (i.e. non-clients and tire-kickers) who want to know more about these technologies - but who haven't invited me out to discuss them over pizza.

Actually, all of Eli's videos are pretty good. You can find the complete collection here.

His reality check presentation on How to Become an IT Professional (see below) should be required viewing for anyone who is considering pursuing one of those "highly paid professional careers" the late night cable TV ads for private technical 'institutes' boast so much about. Seriously, if you're at all thinking about going into IT (as opposed to just "getting into computers") take the time to watch it. It can save you tens of thousands of dollars, and a few years of your life!

xtabber · « **Reply #15 on:** August 17, 2012, 01:53 PM »

A VMware virtual disk is just a set of files contained in a directory. Some tools even allow you to mount a VMware VM to your host system as a virtual drive. I suggest using the option to limit file sizes to 2GB because it makes it much easier to manage and copy or move large VMs than as a single huge file.

Player doesn't have the snapshot feature of Workstation, but you can close a VM and make a backup image of the VM directory, then restore it later to return to the initial state. The easiest way to do that is just make a Zip archive of the VM directory. I do that anyway to make backups of some of the VMs I use regularly.

You can create as many virtual machines as you want on a single host system, although you can only open one at a time with Player -- Workstation allows you to network multiple VMs.

If you use VMs more than occasionally, Workstation is well worth the price, IMHO. That said, Player is probably adequate for most people's purposes.

tomos · « **Reply #16 on:** August 17, 2012, 01:59 PM »

Thanks for the comments .. the lack of snapshot feature would definitely make it less useful for me.
-Jibz (August 17, 2012, 12:46 PM)

Don't be so quick there. You can simply copy the files at a given point, and then you have a "snapshot". Yeah, might be a bit of a pain, but it still works.
-Renegade (August 17, 2012, 01:00 PM)

that's good to know,
I was going to ask whether to save the virtual disk as a single file or to split it into multiple files - for splitting files, they say may reduce performance with very large disks. I dont know if they mean large physical discs or large virtual discs (and WTF is "large" these days... $:-\$ )

But I think I'll take xtabber's recommendation anyway:

I suggest using the option to limit file sizes to 2GB because it makes it much easier to manage and copy or move large VMs than as a single huge file.
-xtabber (August 17, 2012, 01:53 PM)

it's great to get so much advice

tomos · « **Reply #17 on:** August 18, 2012, 11:41 AM »

Well, after a couple of false starts (it wouldnt accept the key using [XP"0" + SP3 slipstreamed via nlite] so I had to install the XP"0", then SP2, then SP3...) I have XP installed. I've done a backup before installing more updates etc etc. - I was able to copy the files even though the virtual OS was running.

It's a bit weird going back to XP

If I connect printer or scanner etc, I get this message (note: in a win7 frame):

Screenshot - 2012-08-18 , 18_00_19.png

I dont need them yet (I actually have my scanner, printer, external HD on a seperate extension lead that is normally switched off until I need one of them) but it looks like that's an either/or choice (I mean it will only work for one OS at a time) - and I'm wondering: how this works, especially if you need to swap over and back between the real and virtual machines.

mouser · « **Reply #18 on:** August 18, 2012, 11:52 AM »

Btw since it hasn't been said in this thread yet -- a virtual machine is an absolutely essential tool these days; it lets you test software safely and without polluting your real machine.

Renegade · « **Reply #19 on:** August 18, 2012, 12:27 PM »

Btw since it hasn't been said in this thread yet -- a virtual machine is an absolutely essential tool these days; it lets you test software safely and without polluting your real machine.
-mouser (August 18, 2012, 11:52 AM)

+1

I didn't think that needed to be said.

cyberdiva · « **Reply #20 on:** August 18, 2012, 04:58 PM »

Btw since it hasn't been said in this thread yet -- a virtual machine is an absolutely essential tool these days; it lets you test software safely and without polluting your real machine.
-mouser (August 18, 2012, 11:52 AM)

At the risk of appearing as dumb as I really am, I need to ask how this works. If I install a program on a virtual machine and the program turns out to be malware that starts doing harm when you install it, how am I better protected if this happens on a virtual machine rather than on my real machine? Obviously just getting rid of the malware program isn't enough. Do I have to remove the virtual machine? Is that what will solve the problem? And does that mean that every time I encounter a problem, I have to trash the virtual machine and start over again?

skwire · « **Reply #21 on:** August 18, 2012, 05:03 PM »

1) Create the VM.
2) Boot the VM and create snapshot.
3) Install and test chosen piece of software in the VM.
4) Shut down the VM.
5) Revert to previous snapshot, if necessary.

Honestly, the best way to learn about virutal machines is to actually create one. Once you see a VM in action, things instantly become clear.

Renegade · « **Reply #22 on:** August 18, 2012, 11:24 PM »

Btw since it hasn't been said in this thread yet -- a virtual machine is an absolutely essential tool these days; it lets you test software safely and without polluting your real machine.
-mouser (August 18, 2012, 11:52 AM)
At the risk of appearing as dumb as I really am, I need to ask how this works. If I install a program on a virtual machine and the program turns out to be malware that starts doing harm when you install it, how am I better protected if this happens on a virtual machine rather than on my real machine? Obviously just getting rid of the malware program isn't enough. Do I have to remove the virtual machine? Is that what will solve the problem? And does that mean that every time I encounter a problem, I have to trash the virtual machine and start over again?
-cyberdiva (August 18, 2012, 04:58 PM)

This is one of the PRIMARY reasons for using a VM. People PURPOSEFULLY install malware in VMs to study it. When you're done, you just delete the VM and the malware is gone with it. (It's not that simple, but just about. You still need to make sure that your network is protected if you are testing worms that reach out to find vulnerable machines - etc. etc.)

Well, you should create a clean copy of your VMs to store, then when you need to use a VM, copy it before you use it. This guarantees that you won't accidentally monkey everything up by forgetting to take a snapshot or something. Also, if you can't take snapshots, then you MUST copy the files.

I keep a folder called "originals" in my VMs folder. It takes up a bit more storage, but it's not really all that much. And it's just a heck of a lot safer, especially when you've gone through the trouble of actually setting up the VM yourself instead of just downloading a ready-to-go VM.

cyberdiva · « **Reply #23 on:** August 19, 2012, 08:05 AM »

Thanks VERY much, Skwire and Renegade, for your helpful responses. I've got one more dumb question (well, actually I have an almost infinite store, but....): is a "snapshot" the same as an "image" such as those made by Macrium Reflect, Acronis, etc.?

mouser · « **Reply #24 on:** August 19, 2012, 08:11 AM »

A snapshot is functionally equivelent to doing a drive image, with some advantages:

Snapshots are managed and executed by the virtual machine software so it is really just a menu click away and could not be easier to use, and requires no extra 3rd party software installation -- snapshot making and restoring are built into the virtual machine software.
Snapshots are saved and restored VERY quickly (maybe 10 seconds or so).