Two questions:
1) Why not combine steps 2 & 3 — both are just install operations

2) The light gray text of your code sections is very hard to read against the white background. It’s pretty, but hard to read. Any chance of changing up the CSS a tiny bit so that it’s either light on dark or vice versa?

The first point, right now as is just because it will not fit at one line in current blog design.

And for the second point, yes. I am not very happy with the current design. It is just a default one. I am currently collecting opinions, like your’s, about the things to pay attention to when I’ll decide to change it.

after I run qemu -boot d -hda winxp.img -cdrom /dev/cdrom -m 192 -localtime

I get this when I close the qemu

Could not open ‘/dev/kqemu’ - QEMU acceleration layer not activated

but it does boot and install the OS.

Thanks,

Darrell

sudo /etc/init.d/qemu stop
sudo /etc/init.d/qemu start

Reason 2: kqemu module is not well compiled or installed.
Check: does the next three commands pass without errors?

sudo m-a prepare
sudo m-a build kqemu
sudo m-a install kqemu

sudo m-a prepare
sudo m-a build kqemu
sudo m-a install kqemu

but i tried running apt-get install qemu, and it starts to download, will it not work because of the 3 commands not being successful

Qemu will work without kqume module but very slooow.

What are the errors when you execute these commands?

Did you executed the command

sudo aptitude install module-assistant

and what is the result?

sudo: m: command not found

I Tried this one –> sudo aptitude install module-assistant, it was ok.

the ff commands were not recognized:
sudo m-a prepare
sudo m-a build kqemu
sudo m-a install kqemu

Hmm… That is a quite strange output: “sudo: m: command not found”… Should be at least “sudo: m-a: command not found”. See the difference? It is just in m and m-a. Check, that you have no space between m and -a. You can also try to use module-assistant instead m-a, so the commands will be:

sudo module-assistant prepare
sudo module-assistant build kqemu
sudo module-assistant install kqemu

I receive these:

Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
No candidate version found for module-assistant
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information… Done

Aha! Module assistant is at the universe repository. Check that it is included in /etc/apt/sources.list. I’ve pointed that at the instruction, but not concentrated an attention on it.

but again, i received these:

sudo aptitude install kqemu
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
Couldn’t find package “kqemu”. However, the following
packages contain “kqemu” in their name:
kqemu-common kqemu-source
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.

———————- DirectFB v0.9.24 ———————
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
———————————————————–

(*) DirectFB/Core: Single Application Core. (2006-10-13 15:40)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(!) Direct/Util: opening ‘/dev/fb0′ failed
–> No such device
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use ‘fbdev’ option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize ’system’ core!
–> Initialization error!
Could not initialize SDL - exiting

After reboot check that file /dev/kqemu exists. That means that all is done properly.

Just for the note: there is no kqemu package, it is compiled from kqemu-sorce package. And you have always to build it if a new (or updated) linux kernell installed.

If you’re on a server, you have to work through an serial port emulation (but no graphics will be), or you have to forward a video output through vnc session. I’m not familar with bot of them, and can’t help there.

If you’re running qemu from a text console, just install a libdirectfb-0.9-24 package, and probably reboot to get a /dev/fb0 device.

Reading package lists… Done
Building dependency tree
Reading state information… Done
libdirectfb-0.9-24 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 156 not upgraded.

after these i received this error again :

qemu -cdrom /dev/cdrom -hda c.img -m 256 -boot d

———————- DirectFB v0.9.24 ———————
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
———————————————————–

(*) DirectFB/Core: Single Application Core. (2006-10-13 15:40)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(!) Direct/Util: opening ‘/dev/fb0′ failed
–> No such device
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use ‘fbdev’ option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize ’system’ core!
–> Initialization error!
Could not initialize SDL - exiting

Thanks

At first get a list of all related packages:

sudo dpkg -l "*qemu*"

And purge them all with dpkg. In my case that is:

sudo dpkg --purge qemu kqemu-source \
    kqemu-modules-2.6.17-11-generic \
    kqemu-modules-2.6.17-11-386 \
    kqemu-modules \
    kqemu-common

dpkg -L qemu | grep "init.d"

Is the init script listed there? If not, you’ve installed something not from my repository.

WARNING: untrusted versions of the following packages will be installed!

Untrusted packages could compromise your system’s security.
You should only proceed with the installation if you are certain that
this is what you want to do.

kqemu-common kqemu-source

Do you want to ignore this warning and proceed anyway?
To continue, enter “Yes”; to abort, enter “No”: yes

I got a similar warning when I tried to install qemu.

Otherwise, this page is awesome! Thanks!

m-a prepare
Getting source for kernel version: 2.6.17-11-generic
Kernel headers available in /lib/modules/2.6.17-11-generic/build
apt-get install build-essential
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
build-essential: Depends: libc6-dev but it is not going to be installed or
libc-dev
Depends: g++ (>= 4:4.1.1) but it is not going to be installed
E: Broken packages

Done!

but this probable because the prepare command didn’t work

sorry im sort of a noob
I have been running Ubuntu Edgy for about 5 months.

The command line has the following:

lurch@Eve:/tmp$ sudo m-a build kqemu
The source tarball could not be found!
Package kqemu-source not installed?
Running "m-a -f get kqemu-source" may help.
find: /usr/src/modules: No such file or directory

I’m in /tmp with kqemu-1.3.0pre11.tar

Trying m-a get. gets me:

lurch@Eve:/tmp$ sudo m-a -f get kqemu-source
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package kqemu-source

Updated infos about 1 packages

I have your repository in apt sources list:

deb http://ubuntu.tolero.org/ dapper main
deb-src http://ubuntu.tolero.org/ dapper main

did I miss something?

qemu -boot c -hda winxp.img -m 512 -localtime

I get this:

‘/dev/kqemu’ - QEMU acceleration layer not activated

I’ve read the above replies, and for the life of me I can’t seem to get this working. I’m a newb for linux, and step by step instructions on what to do to get kqemu working would be greatly appreciated! Thanks!

/dev/kqemu is not created by udev
https://bugs.launchpad.net/ubuntu/+source/kqemu/+bug/105933

It solved it for me…
I did

echo ‘KERNEL==”kqemu”, NAME=”%k”, MODE=”0666″‘ >> /etc/udev/rules.d/90-kqemu.rules

mv /etc/modprobe.d/kqemu /etc/modprobe.d/disabled-kqemu

have a look at this

https://help.ubuntu.com/community/WindowsXPUnderQemuHowTo

hope it helps