Virtual Machines - WinXP guest on Linux Host

Discussion in 'Software' started by Hedon James, Jan 11, 2010.

  1. Hedon James

    Hedon James Sergeant

    Hello everyone,

    Quite a lengthy post, but I’ve recently installed Ubuntu Linux on my computer and am attempting to completely migrate away from Windows programs. I’ve run into some problems with that idealistic concept, realizing that WINE and CrossOver don’t run my Win programs the way they should; no problems…I’ve also recently learned about the wonders of Virtual Machine software. But now I have numerous questions and concerns about various options using a WinXP Virtual Machine as a guest OS in my Ubuntu Linux host. I’ve cruised numerous forums and gathered all kinds of information, but I just can’t find the answers to MY specific questions…so I’m asking you folks already “in the know” with VM experience.

    In order to make recommendations, I think it’s important you know that the SOLE reason for wanting to do a VM is to run specific Windows programs in Linux that I just can’t replace with Linux programs. These programs are Quickbooks Pro, Microsoft Zune, and WinTOTAL (real estate appraisal software). Also, don’t know if this matters, but after much consideration and research, I’ve decided to use VirtualBox OSE as my VM program.

    Other important considerations are that I have WinXP (OEM installed) and Ubuntu dual-booting on my 40GB desktop; Win occupies a 29GB partition (although only 21GB is used) and Ubuntu occupies the remaining 11GB. With that background, I’m having trouble deciding what is the appropriate strategy to implement a VM. It appears that my primary options are as follows, with questions/concerns for each option discussed below:

    1. Install WinXP as guest OS VM from a “raw” or “native” partition;
    2. Install WinXP as guest from Clonezilla iso image;
    3. Install WinXP as guest from self-created slipstream disk;

    Potential considerations for option #1 are that I will not be able to expand my Linux partition, as needs dictate. Also, if I have a WinXP VM, there’s no reason to continue with a dual-boot arrangement. I’d like to just wipe out my Win partition and utilize the whole hard drive for Linux. Option #1 will preclude this in the future. Also, does this option allow for access to the aforementioned previously installed Win programs on that partition, or does it only create a WinXP environment, with my desired programs to be added from within the VM?

    Potential considerations for option #2 are that a cloned image will also be 29GB. How does this work when the “native” install is 29GB and the Linux install is 11GB? Seems like the hard drive is completely spoken for, right? Also considering #1 issues, this seems like a chicken & egg proposition where I need a WinXP VM to wipe out the native partition, but I need the native partition to create and verify the VM. Is it possible to save the cloned disk image ISO file on an external network drive and have VirtualBox access that image to create my VM, thereby proving its viability before I wipe out the windows partition? And again, will the cloned image include the aforementioned previously installed Win programs on that partition, or does it only create a WinXP environment, with programs to be added from within the VM?

    Lastly, potential considerations for option #3 primarily revolve around the creation of a slipstream disk from Dell OEM-installed WinXP. My current XP configuration is up-to-date with SP2 and SP3, as well as all the latest hotfixes. Obviously, this disk will be bare-bones WinXP installation as VM, without anything but XP programs, which isn’t necessarily a bad thing. Obviously, I will have to install my previously aforementioned WinXP programs in the newly created VM; but this begs the question of “should I just create a basic slipstream install disk, updating SP2 and SP3 from within the VM; or should I try to create a slipstream disk with all SPs and hotfixes that will not require updating?” Not sure of the pros and cons of each method…any insights from someone who has already done it?

    In summary, I think I’ve considered all the potential scenarios, but cannot quantify the risks/rewards of each scenario. I’m a 2 month old Linux “newbie” and I’d really appreciate some guidance from someone who has already “been there and done that”… What is the BEST way, in your opinion, to accomplish my stated goals? Thank you in advance for any insights/guidance you can offer!
     
  2. mhh53

    mhh53 Private E-2

    Wow. For a 2 month old "newbie" you certainly have done a complete analysis. From the age of this post it seems that you are now a 5 month old Ubuntu adolescent... and probably more experienced than me.
    If you are still working on this project I can offer some Clonezilla tips. I don't have first hand knowledge of VM, but would like to help since you still have no replies. First it is easy to save and restore images so that you can test different approaches without loosing a working configuration... only time. I use a bootable Clonezilla USB stick and an external USB HD to library images. This works well to recover destroyed workstations after users "didn't mean to click on that..." I also use it to play with different OS's on my 16GB ssd netbook - too small to waste disk space. However it takes only a few minutes to partition and reinstall an image.
    I believe that Clonezilla can restore partitions to different sizes ( maybe only larger?) when cloning partitions instead of disks because I have gone between different drive sizes.
    The final suggestion is to eliminate temporary files, especially virtual memory swap files, before cloning your partitions in order to minimize the image files.
    This doesn't address your core questions but I hope that it may be helpful. Once you have your solution maybe you could do a tutorial on VM's. I would like to hear about your experience.

    Good luck.
     
    Last edited by a moderator: Apr 12, 2010
  3. Hedon James

    Hedon James Sergeant

    Wow, forgot about that post, but thanks for your reply! I did get that project finished, but almost nothing turned out as originally planned.

    Inasmuch as I really just wanted a complete Linux machine, but I can't replace the 3 mentioned programs (yet!) for various reasons, I eventually went with option #3 (slipstream disk) for a basic Windows VM, with installation of the 3 specific programs mentioned and an anti-virus program. Cut my 29GB windows partition down to a 3.5GB windows VM!!!

    This was the simplest option, as options #1 (VM from native partion) & #2 (VM from Clonezilla) involved cloning Windows AND a host of other Win programs that didn't really matter anymore, but I wanted to have handy "just in case" things didn't work out, but I didn't have enough hard drive, an external HDD to spare, or the coin for a new drive in the machine. I was kinda handcuffed!

    I wanted to make an image of the Windows partition "before" my project, so I could easily restore it if things went horribly wrong. But Clonezilla wouldn't work for me, as I didn't have a "connected drive" that was large enough to save the image to. Ended up using a freeware online version of Seagate DiscWizard to make disk image and save it on the hard drive on another computer of home network.

    Creating a slipstream disk from OEM Windows installation ended up being a series of comedies of errors that really weren't that funny (turns out I had some corrupted Windows files, which actually explained a lot of quirky behavior of that computer over the years?!), but I eventually made a Windows SP3 slipstream disk for installation and got it installed as a Windows VM guest within VirtualBox OSE program.

    Turns out the OSE version did not have USB support, which was absolutely required in order to access my network files in various NAS devices. After some helpful troubleshooting from a complete stranger, I found the VirtualBox program for my Ubuntu platform and installed that instead, configured the Windows VM per his instructions and VOILA(!), everything started working as originally hoped for, despite the numerous detours along the way.

    In short, I was trying to use the wrong backup imaging software, the wrong Windows installation disc creation software, and the wrong Virtual Machine software!! The above story is a greatly condensed version! Too many boring, frustrating, anecdotes to relate, but I'm happy to share the acquired knowledge.

    It's basically only 4 primary steps:
    1. Create partition backup image (optional, but better safe than sorry)
    2. Create Windows installation CD (or find one with valid COA)
    3. Install Virtual Machine software
    4. Create Virtual Machine/Disk

    As long as you're willing to use VirtualBox and you tell me what your host OS, I'll tell you what you need to do to duplicate that project. Looking back on it, it wasn't really difficult to do (with the proper tools/software); I just took the educational "scenic" route!
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds