Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
pwc101, I was just looking at your list again and notice you mentioned issues with X and graphics. Have you looked at VirtualBox's technical information? It emulates an AMD PCNet NIC, an Intel 88082 sound card and it's own unique video adapter. The addons iso provides drivers for NT-based Windows and 2.6.x linux kernels. Since Win9x are still DOS-based it's pretty much impossible to find an appropriate video driver. For Linux guests, in some cases, the vesa driver will have to suffice. The provided driver works for me in SLED10, but crashed my Ubuntu. Also note that VirtualBox has no 3D accelleration support.
@dracolich: Yeah, in those installations I've managed to get a working desktop running (where appropriate), I've always tried to install the Guest Additions, and like you say, for all the modern (2000 and XP) Windows operating systems, that's worked great. For both windows 98 and 95 (if I remember rightly), I couldn't get the guest additions to install, because, as you mentioned, there are no drivers (unless Innotek write some) for those systems.
I haven't managed to get either version of Fedora working (yet). The FC6 install stalled last night at about 98%, which was annoying. I'm going to try and tweak it tonight, and if that doesn't work, I'll reinstall and see if I can do it differently (I know now that I installed _way_ too many packages).
@rkelsen: I'm running VirtualBox on Slackware 11.0 with 512MB RAM, and each guest typically taking half of that. Even running KDE, I rarely go into swap. I tried to run two guest systems the other day at the same time, with slightly less RAM for each, and it really didn't like that!
I'll try DOSBox when I have a minute. When I tried to install Windows 3.11, it was the DOS installation which failed. I don't think it enjoyed reading the VirtualBox hard disk at all, and would fail to recognise it as a disk if you rebooted the virtual machine. Very odd. Perhaps DOSBox will fare better
@Emerson: I'll look into FreeDOS (think I might have an iso for it somewhere...)
Suse 7.3 with host Suse 9.2, P4 3.2, 2GB. Production machine, works flawlessly.
Suse 7.3 with host winXP SP2,P4 3.2, 1GB. Works.
Debian Sarge with host Debian Testing. Works
Debian Testing using Debian Etch. Works
Arm7 using Debian Etch. Little tests done, Works.
Sparc using Suse 9.2. Heavily tested for production level . Works fine taking into account the price of some commercial cpu-simulators.
WinXP with host Debian Etch. Doesn't work. Not needed anymore as we don't play games..
Several Debian Testing in parallel in Debian Etch. Under test (not by me). It looks like it works very well (stability and moreover performance with 4 or 5 virtual servers) when you know what you are doing.
When you tried to install DOS how large was your virtual disk? IIRC, DOS had a limit for the disk size, which is why when disks began to appear in GBs they would come with programs like EZDrive. I think the limits were ~540 MB for <=5.0 and ~840 for >=6.0. My DOS virtual disk size is 512 with 32MB RAM and I installed 5.0, then upgraded to 6.0 -> 6.2 -> and 6.22 without any problems. I haven't tried putting Win3.x on top of it since I wouldn't expect much from it, and because it already works fairly well in DOSBox.
One trick I found to make installations easier is to first dd the original disk to an image file (example: dd -if /dev/floppy -of dos5.img) then tell VirtualBox to use the image instead of a physical disk. Itworks for CDs too and it's faster and easier to swap disks.
EDIT: Oh, maybe distros like FC actually need more than 256MB RAM, and with a gui like Gnome or KDE they definitely do. Adjusting the packages is good but you need more RAM or a lighter gui.
dracolich: Yeah, I've already got the DOS setup as an iso. That's a very good point about the disk size though, I'll have to check that that wasn't the problem (I've a niggling feeling it was). I tend to oversize the virtual hard drive, since they're dynamic anyway, it doesn't make any difference to me if I tell the OS it's 5GB or 15GB, but evidently this time, it was a problem!
rkelsen: I found that I had to symlink some of the .vdi files (the VirtualBox disk images) onto an external hard drive as my measly 40GB hard drive was beginning to creak a little! Perhaps those spare partitions of yours will come in handy!...
Yes I've looked at the changelog and seen all the "sync from qemu".
I just hope qemu also syncs improvements from VirtualBox.
It's the game of forking projects but it would have been good to only have one product and not several that do the same. My opinion...
It's a moving area, the future will tell.
Innotek Gmbh has released VirtualBox 1.4 for Etch 386 and AMD64. It's a virtualizing solution based on Qemu. Innotek has improved it a lot:
- new kernel module 'vboxsrv' - compiles with on problems on both architectures
- sound works
- shared folders between Linux host and the guest operation system work without the need for Samba installed in the host ( which didn't work with Qemu in Debian anyway )
- USB, Remote Desktop supposedly work ( untested by me as of yet )
- so-called 'guest additions': Innotek provides a CD image full of ( getting automatically installed , at least on Windows guests ) drivers for the guest OS
- clipboard copying , working both ways, supposedly work ( untested )
- nice userspace s/w to control your virtual machines
- ability to take a snapshot of a working VM and return to it later (buggy?)
- no need to grab-ungrab the mouse with 'Ctrl-Alt' like in Qemu ( in Qemu>=0.8.2 that works too, but with 20% CPU utilization )