Category Archives: Virtualization

Installing Kubuntu 7.10 In Virtual PC 2007

After last weeks post on Ubuntu 7.10 (https://arcanecode.wordpress.com/2007/10/18/installing-ubuntu-710-under-virtual-pc-2007/), I had several requests for Kubuntu. Since I’m happy to please, here are the step by step instructions for Kubnutu. By the way, I’ve reduced the screen sizes a little to make them fit the flow of the blog, but you can click any of them to see them in full size should you need to make out any of the details.

If you haven’t already done so, you’ll need to download the latest image of Kubuntu, you can get it from http://www.kubuntu.com/download.php .

Kubuntu has some of the same issues as Ubuntu under Virtual PC when it comes to graphics and the mouse. When you fire up the VPC with the Kubuntu disk in the drive (or you’ve captured it’s ISO image), you’ll want to move the highlight down to “Start Kubuntu in safe graphics mode”. To fix the mouse, at least for this session, press F6 for boot options, and type in “i8042.noloop” after the –. Once your screen looks like the one below, press Enter to continue.

k710_001

Once Kubuntu boots, click the install icon on the desktop to begin the installation process.

k710_002

On the Welcome screen, just confirm your language, then press Next.

k710_003

In this step you get to play Carmen whats-her-name and do the “Where in the world are you” bit. Select a city in the time zone in which you live, then click Next.

k710_004

Now pick your keyboard, and click Next.

k710_005

On the disk space screen, just take the defaults and click next.

k710_006

OK, now we actually have to do some work, and give Kubuntu some info. Make sure to remember your password, not only will you need it to login but you’ll also need it for any commands that need super user privlidges.

k710_007

OK, Kubuntu finally knows everything it needs in order to install so just hit next.

k710_008

And wait. And wait. And wait. If you thought Ubuntu took a while to install, just wait for Kubuntu. My experience was a couple of hours, but to be fair I was also playing a couple of Quicktime videos (some of the cool shows from http://www.revision3.com) and testing an openSuse install in another VPC. And I have sloooooooooooow hard disks, so your milage (or kilometers) may vary. But it’ll still take a while.

About 84% or so into it I got this error. This is similar to the error I got with Ubuntu, just click OK to let it keep going. Oh, and wait some more.

k710_009

Yea! It finally finished the install.

k710_010

When you get to this screen, just press OK, then reboot Kubuntu. Don’t forget to eject the CD (or release the ISO) during the reboot. But before you press OK, make sure to read the next step!

OK, time for a tricky part. Pay close attention during the reboot. When you get to the screen that talks about the GRUB menu, press the ESCape key. You should see a screen like this:

k710_011

With the top line highlighted, press the e key to edit the command line.

On the next screen, press the down arrow once to highlight the line that begins in “kernel”, then press e again to edit that line. When the edit screen appears, we need to add the – i8042.noloop to the end of the line. It should look something like:

k710_012

Press Enter, then when you return to the screen with “kernel” on it, press ‘b’ (just the letter b) to boot Kubuntu. What this will do is enable the mouse for this session only! Once we get booted, we’ll fix the mouse permanently, so hang on.

When the login screen appears, enter your user name and password (the ones you entered on the “Who Are You” screen during the installation) and press enter. Now give it a minute while Kubuntu finishes loading.

OK, now it’s time to fix that pesky mouse issue once and for all. Click on the big K in the lower left (it’s like the Start button in Windows), and go to System, then bring up Konsole.

k710_013

Now in the Konsole window, type in

sudo kate /boot/grub/menu.lst

and press enter.

k710_014

Enter your password when prompted, and you should be in the kate editor. Note you may see a few errors on the terminal window. These can be ignored.

Once kate is up, scroll to the very bottom of the editor where you’ll find three sections of “title… kernel… “ etc. In the first section, which is the default, we need to edit the kernel line to add:

— i8042.noloop

to the end of the line, as you see here. Once done, save it by using File, Save on the menu or clicking the floppy disk. Then exit kate (File, Quit) and exit the terminal window (type exit and press enter, or close by just clicking the x button as you would in Windows).

k710_015

And that’s it, you should be good to go and enjoy Kubuntu 7.10 virtually.

PS If you found this useful, please give it a digg so others can find it too.

Installing Ubuntu 7.10 Under Virtual PC 2007

Update April 24, 2008 – The newest version of Ubuntu, 8.04 is out. Look for complete install instructions here.

Update April 7 2008 – If you are interested in also playing with the 8.04 BETA, you can read my post here.

Ubuntu version 7.10 was just released. In keeping up with tradition I’d like to describe step by step instructions on how to install and get it running under Virtual PC 2007.

Before I begin though, I’d like to give a word of thanks to all the folks who have commented on my previous postings. It was their findings and efforts that helped to create this work, I owe them a big thanks.

OK, first thing you need is to download the Desktop install ISO from the Ubuntu site (http://www.ubuntu.com). You can skip right to the download mirrors page at http://www.ubuntu.com/getubuntu/downloadmirrors if you want to save a few mouse clicks.

Once you get it downloaded fire up Virtual PC, and create a new machine. If you are not familiar with VPC, see my step by step instructions for creating a machine at https://arcanecode.wordpress.com/2006/09/20/virtual-pc-step-by-step/ Make sure to pick “other” as the OS type. I used 512 meg of ram because my system has 2 gig, but if you have less you can get away with 256 meg of ram for the Ubuntu Virtual machine.

Fire up your new virtual machine, and use the option in the CD menu to “Capture ISO image”. Point the image at the desktop iso you just downloaded.When it starts, immediately press the down arrow, so that “Start Ubuntu in Safe Graphics Mode” is highlighted.

When 7.04 was released, the new kernel had issues with the mouse emulated by Virtual PC. To be blunt, the mouse just didn’t work. However, several work arounds were found. The easiest was brought to my attention via comments on the blog, the i8042.noloop option. That’s what we’ll implement, so we can use the mouse during the “live mode”.

Hit the F6 key, for Options. When the line appears, at the very end type in a space (if there’s not one after the two dashes) then i8042.noloop . Your screen should look something like this:

u710_001

Press Enter to start the launch process. Be patient, it takes quite a while. Once it’s finally up though, you’ll see this screen:

u710_002

Double click on the Install icon to begin the install.

On the first screen, below, you are welcomed and asked about a language. Pick your language and hit Forward.

u710_003

Now pick your time zone, since I’m in the Central zone I picked Chicago as a city in my time zone and clicked Forward.

u710_004

No it asks about keyboard layout, pick your keyboard if yours isn’t US English, then press Forward.

u710_005

Ubuntu will crank and grind for a minute, then you’ll see this dialog asking about your disks. Just take the defaults and click Forward.

u710_006

Time for a little personal info, give your name, a login id, enter the password you want to use, and what you want to name the “computer”. When done click Forward.

u710_007

OK, you’re almost ready to start the install process. Look this over, if everything looks good just press the Install button and we’re off to the races.

u710_008

Did I say races? Well, turtle race might be more like it, the install runs pretty slow, so get some coffee, or maybe a second bowl of ice cream if you’re doing a late night install.

u710_009

I did encounter one error during the install. You may see this as well, but you can go back later and correct this through the normal updates process.

u710_010

Now Ubuntu will finish, and ask if we want to reboot. Tell it no, then reboot by shutting down by pressing the red shut down icon in the very upper right of the Ubuntu window.

OK, you’ll have to be very quick with this next step. Remember the mouse issue? We’ll still need to fix it. First, boot the new machine, after clicking on CD and releasing the ISO if it’s still held. Now when you see the words “Grub loader” hit the Escape key. If you were fast enough, you’ll see this screen.

u710_012

With the line you see selected, press the “e” to edit the line. Now a new screen will appear.

u710_013

Move the highlight down one to the Kernal line, and press “e” to edit that line. When the new screen appears, you’ll need to add two dashes, then the i8042.noloop command. Your screen should look like this:

u710_014

Press Enter, then when you are returned to the screen with “kernel…” on it, make sure the kernel line is still highlighted and press b to boot.

Once booted, login using your user id and password. When Unbuntu is up, it’s time to fix the mouse issue once and for all. Click on Applications, Accessories, Terminal. When the terminal window appears, type in:

sudo gedit /boot/grub/menu.lst

u710_015

When you press Enter you’ll be prompted for your password, enter it. An editor should appear. Scroll down to the very bottom of the text and find the line that begins with “kernel”. Add the – i8042.noloop to the end of the line, as I’ve shown below. (Note I have highlighted the line to make it easy to see, yours won’t be normally highlighted in your session.)

u710_016

Save the file and exit the editor and the terminal window. When you next reboot, you should be able to just login normally, and the mouse should work.

And there you go, Ubuntu 7.10 up and running, complete with mouse, under Virtual PC 2007.

P.S. If you found this post useful, please give it a Digg so others can find the same happiness you did.

Downloading a Virtual PC Image of Visual Studio 2008 Beta 2

During last week’s WPF class, several of my coworkers expressed an interest in using the 2008 edition to experiment with WPF. They were concerned installing the beta on their production box could damage their boxes, even though in theory part of the beauty of .Net is the ability to run multiple versions of the framework side by side.

To alleviate those fears, Microsoft has provided a Beta of 2008 already in a ready to run Virtual PC. First, you’ll need to have Microsoft Virtual PC 2007 installed on your box. If you don’t, you can grab a copy from

http://www.microsoft.com/downloads/details.aspx?familyid=04D26402-3199-48A3-AFA2-2DC0B40A73B6&displaylang=en

(Even though the instructions indicate it should work with VPC 2004 SP1 or Virtual Server, I haven’t tried it with them. Virtual Server should be fine, but I would highly suggest upgrading your VPC 2004 to 2007 if you haven’t done so already, there’s lots of nice new features that make it worth the effort.)

Now you can grab the 2008 image. You will actually need two sets of files, the base image and the 2008 Beta 2 image. You can download the 2008 Beta 2 from

http://www.microsoft.com/downloads/details.aspx?FamilyID=3b72271c-e996-4989-898d-72d684966ce6&DisplayLang=en

The download is in the form of 7 files, the first is an exe and the rest are rar files. Download all 7 to a folder and run the exe, and it will combine all 7 to create the virtual pc image.

Make sure to read all of the instructions on this page! The user ID and password to login to the virtual image, along with a link to the needed base image, are contained in the instructions!

Now you need the Orcas base image. If you read through the instructions you saw the link to the compressed file, right above the user id / password. Right click on the link and “Save As…” to the same folder where you saved the other items. Run it to uncompress the base image.

OK, in a folder you should now have OrcasBeta2_VSTS.vmc, OrcasBeta2_VSTS.vhd, Base01.vmc, and Base02.vhd. I also copied the user id and password from the above linked page and saved it in a text file called “Orcas Beta 2 user id and password.txt”, just so I could remember it easily.

When you login, it tells you that the password expries today, and asks if you wish to change it. I’ve always just said no, and it seems to work fine, but you are welcome to change it if you want.

When you shut down the Virtual PC, you will be prompted first for why you are shuting down. This is a Windows Server 2003 prompt, I just select “Other (Planned) under the option and put an ‘x’ for the comment. Once you do the OK button will be enabled.

Next, Virtual PC prompts you, to see if you want to commit your changes or abandon them. If you select “Commit changes to the virtual hard disk”, any changes you made will be saved and ready for next time. If you choose “Delete undo disk changes”, everything you did during that session will be lost forever.

Since it’s just a virtual image, I usually pick commit, but if you have really hosed things up you might want to know about the Delete option.

All of the software I’ve mentioned here is free, so there’s no reason why you can’t run this at home, even if you don’t have an MSDN subscription. Be warned, although Microsoft hasn’t specified a date I would think the image will expire not long after the release of the full Visual Studio 2008 product.

Using the virtual image will allow you to experiment with WPF, as well as the new 2008 features in a safe, risk free environment.

Note: If you want to use Visual Studio 2005 to write WPF (as well as other .Net 3.0 projects), I have documented the bits you need to download in this post:

https://arcanecode.wordpress.com/2007/08/20/installing-the-wpf-bits/

VirtualBox – USB Support

So far I haven’t had a lot of success getting USB devices working under VirtualBox with XP as the guest. Perhaps it has something to do with Vista being my host?

I’ve been testing using some USB keys, and while VirtualBox seems to know they are present, the message never seems to make it into my guest OS of XP. I intend to keep working with it, USB support would be one of the most compelling things to make me start using VirtualBox as my primary virtualization platform. However, as of right now USB support doesn’t seem quite up to prime time.

VirtualBox – Communicating to the Host OS via Networking

This evening I installed my old copy of XP (I’m now running Vista) into VirtualBox. The install was pretty easy and straight forward, so much so that it’s not even worth doing step by step instructions. A simple wizard setup my base machine, and XP installed just like it would as a “real” machine.

Using the default of NAT for networking (Networking Address Translation) seemed OK for getting to the internet, but I spent most of my evening trying to make the guest OS, in this case XP, talk to the hard disks of my host OS, Vista.

To save you a lot of grief and manual digging, here’s what I finally had to do. First, I setup a single folder on my host OS, right clicked on it to bring up properties. I then picked the Sharing tab and told the OS to share it with others on the network. (Yes, I’m firewalled, both hardware at the router and within the OS as well. I haven’t been listening to all those security now episodes for nothing! )

The folder I created was named “Z”, for no better reason than it’d be easy to find. I also named the share Z, for consistency. Once I had it shared, I went back into the guest OS of XP, which was running inside VirtualBox. I opened an explorer (aka My Computer) window, and picked Tools, Map Network Drive. OK, here comes the tricky part:

After picking the drive letter, for the Folder I had to use the IP address of the guest OS, followed by the name of the share, as in \\192.168.1.1\Z . I could not browse my local network, I couldn’t enter the machine name, only using the combo of IP address followed by share name would work.

Digging in the documentation it said that running VirtualBox’s network emulation in NAT mode caused the issue, and gave the solution, but I wish they had mentioned it a bit more prominently in the software, since using a lot of common techniques was not working.

A few notes, yes I could have chosen to share my entire drive. However, being security conscious I prefer to setup a single folder and share it. That allows me a comfortable level of isolation, and allows my to quickly and easily scan the contents with antivirus / spyware applications before using the files. And, if anyone should “break in” my exposure via shared networking will be limited to that single folder, which will be empty 99.9% of the time.

To find your machine’s IP, in the host box (outside VirtualBox) open a command window and type in IPCONFIG and hit enter. In the list of wireless adapters should be your hard wired network card, just grab it’s IP address.

Also, the share name of “Z” was because I was testing, for longer term I’ll probably setup something more meaningful like “VirtualBox Shared Folder”.

Be aware that the moment you share a folder between your VirtualBox (or any Virutal Machine) and the host OS, you have a security vulnerability. That may be fine, and will be one of the better solutions for transferring data and application installs between the host and guest OS.

Many people though use virtual machines to test new software (especially “free”applications) for viruses / spyware / malware. If that’s your goal, make sure to disconnect your mapped network drive before testing these potentially harmful applications.

Hopefully I’ve saved you a bit of effort in establishing a connection between your guest and host OS’s hard disks when running VirtualBox.

Virtual Box

I’ve started playing with a new virtualization alternative, Virtual Box (http://www.virtualbox.org/ ). It’s an open source alternative to other virtual machine programs like VMWare or Microsoft’s Virtual PC. It runs on both Windows and several flavors of Linux, and has guest additions for Windows and Linux. It also has USB support, a feature lacking in Microsoft’s product.

I found the user interface very intuitive. Simply clicking New brings up a wizard and walks you through the steps to setup a new machine.

You can choose to use a physical CD/DVD or mount one off of an ISO file, access hard disk info, audio, etc all by clicking on the blue links you see above.

As an initial test I downloaded Damn Small Linux (http://www.damnsmalllinux.org/ ) as a ISO file, and ran it in “Live” version as a mounted image. I only gave it a quick run, but so far it seems to work OK. I plan further testing with XP as a test image, but would be interested in seeing comments with your experiences.

Fixing Ubuntu 7.04 Fiesty Fawn Mouse under Virtual PC 2007

Update: October 18, 2007 – Ubuntu 7.10 was released today, and I’ve now posted step by step instructions for installing it. If you haven’t yet installed Ubuntu, you may prefer to start with the instructions on 7.10, found here: https://arcanecode.wordpress.com/2007/10/18/installing-ubuntu-710-under-virtual-pc-2007/


OK, one of my readers “John” (thanks John!) shared a link to an unsupported patch that fixed the Ubuntu 7.04’s mouse under Virtual PC. Let me give you the quick summary of what I did:

  1. Fired up a new VirtualPC with the Fiesty Fawn “Live CD” in the drive. Booted up in safe graphics mode.
  2. Once up, I activated the keyboard mouse using the fix I described in my post “Ubuntu 7.04 and Virtual PC 2007 – Mouse Issue Workaround (sort of)” at http://shrinkster.com/p2u.
  3. I then installed Ubuntu, it was pretty straightforward although a bit annoying using the numeric keypad as a mouse. One hint, sometimes it didn’t recognize my mouse click until I moved the mouse off a button then back on.
  4. After the install I rebooted, then in my new install repeated step 2 to activate the keyboard mouse in my new install. Setting this in the Live CD didn’t carry over to the new install.
  5. I then opened firefox and went to the link John provided, https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/87262/comments/13. Since that’s a lot of typing, I shrinksterized it to make it very easy to type, http://shrinkster.com/p2t.
  6. Joe Soroka has posted a script, I downloaded it using the “shell script” link at the very top of the message and saved it to my home folder.
  7. I opened my File Browser (use Left Alt+F1 select Places, Home Folder). I moved the mouse (again using the numeric keypad) and clicked once on the sh file I’d saved.
  8. Now in the browser, with the file highlighted, hit left alt+enter or select File, Properties on the File Browser menu.
  9. In the dialog that appears, move to the Permissions tab, and check on the box that says “Allow executing file as program”. Click the close button to close the dialog.
  10. Now double click the sh file or press enter. You should see a dialog appear that asks if you want to open in a text editor or run the script. Select the “run in terminal” option. (Update, added “in terminal” based on feedback.)
  11. While the script executes it will ask for your admin password, give it.
  12. At one point it will also stop to ask if you want to skip or configure grub manually, or let it do it for you. I pressed enter to let the script do it for me.
  13. That ended the app, when the terminal window closed I rebooted (still using the numeric keypad as my mouse).
  14. When Ubuntu came back up, it flashed a quick message from the grub asking which kernel I wanted to load, I just took the default.
  15. I logged in and what do you know, my mouse worked!

Just FYI, I’m running Virutal PC 2007 under Vista, using the standard desktop version of Ubuntu 7.04.

The real hero here is Joe Soroka for posting such a simple fix. I encourage you to give it a try. If you are concerned about messing up your Ubuntu install, simply copy the VHD/VPC files to a backup location before running the fix.

A big thanks to Joe Soroka, and to “John” for posting the link. Now I can actually start playing with Ubuntu 7.04.