Hello,
we just got a 6-core, 8GB memory machine. I need to support up to 4 concurrent users. I'd like to keep them completely separated (not 4 users in the same box), but if there was no other option, that'd be OK.
I have two configurations in my mind, and don't know if there's one better than the other.
Conf 1: Windows 7 host. Crack it open to allow multiple concurrent Remote Desktop Connections. Maybe install VB and serve a Linux box remotely.
Conf 2: Linux host. Allow the other users to remote to the box and launch W7 boxes as needed.
The ideal solution would be one where a minimal server runs VB and serves virtual boxes remotely. I don't know how to do that, but I'm sure it's possible.
So, is it?
How?
Thanks!
--
llappall
Which host to use?
-
tburt11
- Posts: 7
- Joined: 13. Apr 2011, 20:33
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: windows and linux
Re: Which host to use?
Fantastic Question! I hope someone here has experience in both camps, and can shed some light.
I am a relative Noob to Vbox, but an old hand at Unix/Linux. I just configured an Ubuntu 10.10 system to host a handful of legacy Windows boxes. Mostly because despite many hours of effort, I could not get Win2K server to load onto sata drives, and you cannot buy pata mobos anymore... But it installs like a breeze in a VBox VM! Problem solved.
I bought a AMD quad processor Lenovo box with 6GB ram at Frys for about $550, and added a hitachi 3 TB drive. Not alot of $$ for plenty of horsepower. I think I can get 4 to 5 VM's running simultaneously.
I am in the process of trying to migrate a few running windows systems to VM's. It is not easy, but I have not given up yet. I will keep you posted.
Two items of interest when considering this question, that I will point out (remember, I am pro-Linux):
1) When I run VBox on a Windows Vista box, and configure the client to use a bridged interface, windows creates another adapter on the fly. It works great, until I exit the VM and close down Vbox, then that remnant adapter that gets left behind causes problems with the Windows box. I cannot ping or RDP into the windows box. I have to go to the console and delete the rogue adapter and reboot. Ok, I guess if you will be running full time guests, but it was a show stopper for me.
2) Linux has way better scripting available in bash, then the dos .bat scripting language. I am writing scripts that will bring up my VM's with simple commands like "startvm win2Kserver", so my life is easier. I also plan on using rsync to mirror the VM data nightly to a remote server, rsync is incredibly efficient at keeping files in sync, and rsync is native to Linux, and not so native in Windows. Cron scripts are easier to setup, and from my experience, windows scheduler is not as reliable as cron. Just my experience mind you.
On the downside, I am having some challanges with how to deal with linux file permissions vs. windows file ACL's. I don't know which approach is better, but I am still trying to find the best solution.
At this time, format the filesystem you intend to keep the VDI's on as ext3. There is a small incompatibility with ext4 filesystems.
Thast is my two cents worth.
I have noticed that alot of the people posting to this board are running windows hosts. Lots more discussion about configuring Windows as a host, than linux, so I think there should be some pelple with useful input from the other perspective.
I am a relative Noob to Vbox, but an old hand at Unix/Linux. I just configured an Ubuntu 10.10 system to host a handful of legacy Windows boxes. Mostly because despite many hours of effort, I could not get Win2K server to load onto sata drives, and you cannot buy pata mobos anymore... But it installs like a breeze in a VBox VM! Problem solved.
I bought a AMD quad processor Lenovo box with 6GB ram at Frys for about $550, and added a hitachi 3 TB drive. Not alot of $$ for plenty of horsepower. I think I can get 4 to 5 VM's running simultaneously.
I am in the process of trying to migrate a few running windows systems to VM's. It is not easy, but I have not given up yet. I will keep you posted.
Two items of interest when considering this question, that I will point out (remember, I am pro-Linux):
1) When I run VBox on a Windows Vista box, and configure the client to use a bridged interface, windows creates another adapter on the fly. It works great, until I exit the VM and close down Vbox, then that remnant adapter that gets left behind causes problems with the Windows box. I cannot ping or RDP into the windows box. I have to go to the console and delete the rogue adapter and reboot. Ok, I guess if you will be running full time guests, but it was a show stopper for me.
2) Linux has way better scripting available in bash, then the dos .bat scripting language. I am writing scripts that will bring up my VM's with simple commands like "startvm win2Kserver", so my life is easier. I also plan on using rsync to mirror the VM data nightly to a remote server, rsync is incredibly efficient at keeping files in sync, and rsync is native to Linux, and not so native in Windows. Cron scripts are easier to setup, and from my experience, windows scheduler is not as reliable as cron. Just my experience mind you.
On the downside, I am having some challanges with how to deal with linux file permissions vs. windows file ACL's. I don't know which approach is better, but I am still trying to find the best solution.
At this time, format the filesystem you intend to keep the VDI's on as ext3. There is a small incompatibility with ext4 filesystems.
Thast is my two cents worth.
I have noticed that alot of the people posting to this board are running windows hosts. Lots more discussion about configuring Windows as a host, than linux, so I think there should be some pelple with useful input from the other perspective.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Which host to use?
Can't speak on Linux, tho I love its price, I haven't had time to figure out how to use it yet.
But I have had three VM's running at once on my Win7 flight-sim PC at home, all three XP clients. No configuring had to be done to the Win7 host to allow more Remote Desktop connections, the guests each handle their own RDP connections. You would remote in on the guest's IP address.
Also, at least on the Virtualbox version I'm still on (3.1.2 PUEL), there's a Virtualbox-provided, non-guest-related RDP in addition to whatever RDP the guest may or may not have, that still allows viewing the VM window over RDP. This involves opening extra ports on the host's firewall, nothing more (for me at least). You remote in on the host's IP address using the desired VM's RDP port, set in the VM's settings. I believe this version of RDP allows viewing the VM even if the network settings for the VM aren't Bridged.
But I have had three VM's running at once on my Win7 flight-sim PC at home, all three XP clients. No configuring had to be done to the Win7 host to allow more Remote Desktop connections, the guests each handle their own RDP connections. You would remote in on the guest's IP address.
Also, at least on the Virtualbox version I'm still on (3.1.2 PUEL), there's a Virtualbox-provided, non-guest-related RDP in addition to whatever RDP the guest may or may not have, that still allows viewing the VM window over RDP. This involves opening extra ports on the host's firewall, nothing more (for me at least). You remote in on the host's IP address using the desired VM's RDP port, set in the VM's settings. I believe this version of RDP allows viewing the VM even if the network settings for the VM aren't Bridged.