Weblog entry #114 for ajt

VirtualBox in Lenny
Posted by ajt on Mon 12 Nov 2007 at 10:02
Tags: ,
Over the weekend I "nursed" a cold at home rather than go to my LUG meeting as I had intended. After 1 g of paracetamol and plenty of hot honey and lemon tea I was able to get moving. I decided to give VirtualBox a go as it is now included in the official Debian Lenny repositories. I've used Qemu before, which VirtualBox shares some code with, but never found it that fast and though the kqemu kernel module is available now in Debian I didn't find many guest OSes that worked with it properly.

VirtualBox went in quickly from aptitude install, though I did have to use the Debian module-assistant to auto-install the VirtualBox kernel component, and manually add myself to the virtualbox group.

Comparing the two I found VirtualBox faster than Qemu, with measurably lower CPU load on the host system. However Windows98 didn't have any suitable graphics drivers in the VirtualBox, so it runs as only 16-colour VGA and I couldn't get sound to work at all with VirtualBox on either Windows98 or Windows NT4.

On Qemu I found Windows 98, NT4 and 2K all worked okay, though I needed different network cards on Win98 than the NTs. Sound and graphics worked on all of them, unlike VirtualBox, but I only ever got the kqemu kernel mode tool to work with NT4, the others all BSOD. Several Linux and BSDs worked under Qemu without a hitch, but again I never got kqemu to work with them.

I only really want a windows environment to play the original Age of Empires game, so as I have a working WINE environment I thought I'd give it a go too. It installed without a hitch, and would start okay, but I can't get it to recognise my genuine AoE CD or detect my network stack. I know networking works under WINE as Eudora is perfectly happy to talk IMAP to my home server.

 

Comments on this Entry

Posted by Utumno (60.248.xx.xx) on Mon 12 Nov 2007 at 11:00
[ Send Message | View Utumno's Scratchpad | View Weblogs ]

Did you install Guest Additions?

I am not sure if they are available in VB from Debian's repositories, but the VB from www.virtualbox.org contains driver packs for guest OSes called 'Guest Additions' which should make the OS run smoothly. At least my Win 2000 guest is running without a hitch.

Thinking again, I recall that starting from VB 1.5, it should be possible to download Guest Additions directly from www.virtualbox.org (rather than from the package itself), so now it should be possible to use them even with VB from Debian repo.

Oh wait,

http://www.virtualbox.org/wiki/Guest_OSes

says that no guest additions are available for Win 98. Eh!

[ Parent | Reply to this comment ]

Posted by ajt (204.193.xx.xx) on Mon 12 Nov 2007 at 12:00
[ Send Message | View Weblogs ]
You are correct the "guest additions" made quite a difference on Win NT4. It installed on Win98 but does not do anything - which is a real pain.

I did a bit of digging on the VirtualBox forums, the VB people said they were not interested in supporting older OSes like Win98 but people were welcome to submit patches. I understand their position but the tone of the posting was a little unhelpful.

It's also annoying that VB can not use the QEMU file containers (QCOW), even though they use QEMU code for some of the core CPU emulation.

If I could get sound working under NT4 I'd be really happy - well I'd be able to play Age of Empires without a hitch. Win98 on VB is a lost cause I fear - though it does work perfectly under Qemu.

--
"It's Not Magic, It's Work"
Adam

[ Parent | Reply to this comment ]

Posted by Utumno (211.72.xx.xx) on Mon 12 Nov 2007 at 17:28
[ Send Message | View Utumno's Scratchpad | View Weblogs ]

I made sound in my Win2000 work my kicking ESD out and reverting to pure ALSA.

Then VB -> Settings -> Audio -> check 'enable Audio' and set 'host audio driver' to ALSA.

[ Parent | Reply to this comment ]

Posted by ajt (85.211.xx.xx) on Mon 12 Nov 2007 at 20:33
[ Send Message | View Weblogs ]
Mine is running with ALSA sound already. The problem is that the client system doesn't know what sound system to install.

At the moment I'm trying a fresh Qemu/WinNT4 system to see if I can create a stable one.

Then I'll try to install an Intel ICH AC97 audio driver onto my VB/NT4 system.

--
"It's Not Magic, It's Work"
Adam

[ Parent | Reply to this comment ]

Posted by Anonymous (80.171.xx.xx) on Sun 16 Mar 2008 at 18:34
I just struggled through installing it on Lenny from the repositories. Here is how it worked:

First I marked virtualbox-ose-modules-2.6.22-3-686 for installation in aptitude, then virtualbox-ose (the other way around aptitude wanted to install modules for -486...).

After installing I added "virtualbox-ose" to /etc/modules (Yes, the module is not called vboxdrv. No, I have no idea why...). I am not sure this is the right way but it works. Of course a simple "modprobe virtualbox-ose" is ok if you don't want to reboot.
Then I added my user to the vboxusers group in /etc/group. I logged out and back in.

Now it works. I really would like to know why the module is named differently and the installation does only do half the work, oh well. :)

[ Parent | Reply to this comment ]

Posted by ajt (204.193.xx.xx) on Mon 17 Mar 2008 at 13:09
[ Send Message | View Weblogs ]
You are quite right it is very confusing. I believe part of the reason for the confusion is that the Debian packages are based on the Open Source Edition (OSE) version of the product, you have to pay for a full automatic version. The Debian community could patch the OSE to make it fully automatic but that takes time to happen.

You run into the same odd problems within the guest OS when you install the guest-OSE components. It's a bit of a pain to set up, but once it's all running VirtialBox is a very slick VM and client integration is good in Debian Sid.

--
"It's Not Magic, It's Work"
Adam

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search