1. to switch focus between qemu mouse focus and X11 mouse focus use: left_CTRL+left_ALT2. to ensure that You use kqemu kernel module in user mode hit left_CTRL+left_ALT+2 and type info kqemu, if everything is ok You will see:

Code:

kqemu support: enabled for user code

if not You will see:

Code:

kqemu support: disabled

if disabled it will work, but terribly slow, You will be running at Pentium 75 speed at host with CPU AthlonXP 1.66GHz.3. to switch between qemu console and qemu os emualtion use left_CTRL+left_ALT+2 to go to console and left_CTRL+left_ALT+1 to back to emulation.4. enabling network on emulated os, use DHCP configuration inside emulated os to get automatic IP adress 10.x.x.x

after You quit You os inside emulated os, or by qemu console left_CTRL+left_ALT+2 and type quit use this command to launch again Your emulated OS:

Code:

% qemu -hda ~/qemu/win2000.img -m 256 -localtime

How to have sound in qemu OS, You just need to launch qemu the way I listed above, only with -soundhw sb16 or -soundhw es1370 to emulate Sound Blaster 16, or Sound Blaster 128. You can also enable standart annoying BEEP with -soundhw pcspk. You can also enable all three of them like that: -soundhw sb16,es1370,pcspk, or just BEEP + one of them: -soundhw es1370,pcspk, examples

The same schema works for Solaris 10 and WindowsXP, You only do not use -win2k-hack.

feel free to point errors, typo and Your hints/suggestions here.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

Last edited by Carpetsmoker; 7th May 2008 at 06:43 AM.
Reason: Fix title

Windows XP requires a minimal of 64MB of RAM; 128MB is recommended (although how anyone could live with that on XP, is beyond me). So let us say, QEMU will be allowed 96MB of memory for running an Windows XP image. Let us further postulate, that between stumpwm and QEMU itself, a further 4MB of memory is consumed (fair enough? This will probably be a bit worse, depending on the size of the disk image used with QEMU).

This leaves 156MB of memory free, not deducting memory space used by the Kernel, hardware resources, or incurred by file system related operations (a background fsck perhaps?).

You will have to be running the X Windows System. A standard X.Org installation I believe, maps part or all of the gfx cards memory into it's own address space where possible; so memory usage on X.Org should be less then most things could ever report; I'm not familiar with NetBSDs X setup, but assume it would be similiar to normal X.Org/Xenocara. So, let us say at least 20MB of system memory for X. If your graphics card uses shared memory, like several (cheaper) ATI Xpress and Intel GMA cards do; that will increase the drain on system memory. X also should be caching image data used by programs, so that out to keep its memory usage lower....

So in reality, you've got closer to < 2/3 your memory to run other applications in. The exact memory used by programs is very hard to gauge, and the figures I've given are for the sake of *example* only. Needless to say, running things like OpenOffice, MS Office, Flash player, Mozilla, running a 3D game, encoding/decoding video, or building anything from ports or with GCC -- will further reduce your memory closer to swap space by a 'nice chunk'. In short: it helps drains system resources, which depending on your needs could someday become a problem sooner then later. FreeBSD is pretty efficient with it's usage of memory IMHO, but not always wise to push it to low memory situations. That is why I said, 'If you only have 256MB for both NetBSD/X, adding QEMU is probably not a great idea.' If one wants to run multiple OSes at once.... oy: much higher chance of getting into SWAP.

Running Windows in QEMU with 96MB of RAM available to it, plus MS Office and IE6; alone would probably push XP into using SWAP file on the disk image. Most Linux or BSD systems, you'd want at least 64MB for QEMU... but ya get my point.

You should really test it out before you commit to it, if you have a real need for using it in such a configuration; rather then a passing fancy.

Because I don't know or understand the hardware requirements to run Xen.
Are their any memory requirements? I have only 256MB on my machine so would
Xen run on my machine?

You need at least 128 M to run the Xen dom0 (the management domain). If you want to run Windows, you also need a CPU that supports hardware virtualisation (Intel VT or AMD SVM). Then you need however much RAM the virtual OS requires (256 MB at least for Windows XP).

You really should not run any kind of VM software on a system with less than 512 MB of RAM.

Personally, I recommend 1 GHz of CPU power and 1 GB of RAM per VM as a starting point.

... but IMHO 512-1024MB will be a good start point for virtualization.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

Jurgen suggested
" Or if you really want to run qemu as root use something like kdesu to
allow root to access your X display, or just do the following `hack':
ln -sf ~yourlogin/.Xauthority ~
(as root.)"