View Full Version : Howto: install Windows in Ubuntu Hoary for free
kLy
August 1st, 2005, 07:27 PM
Qemu is not comunicating directly with your network card, it's bridged if I remember correctly. The only thing you have to do to connect with the net is to use the -user-net then set the settings in Linux.
I know VMware let you communicate directly with the adapter, but I don't know if it's possible with Qemu.
ok, this is as far as I understand it:
Two options:
1. Using -user-net:
This does not do ANY sort of true networking with anything outside the virtual machine. Hence it is completely user mode: user runnable and no need for root. It does not do any communication with any ports on your actual machine, everything is completely faked in user space:
qemu makes a fake dhcp server at 10.0.2.2 that assigns the client the IP of 10.0.2.1 or something.
You can use two extra options here:
-smb : runs a FAKE samba server in userspace (does not open any samba ports on your actual machine).
This server can be accessed from the client at 10.0.2.4. Check the man pages for details. I never got this working but then I never got any sort of windoze networking working in all my years of admin. It always breaks randomly or slows for no reason. It's crap slow on look up. It plain sucks! And did I mention it sucks?
-tftp : this runs a FAKE tftp server. you can get a free tftp client for windoze (98 that is since 2000 and XP come with it) here:
http://www.tftp-server.com/tftp-download.html
This could work but it was such a MISSION since there's no directory listings or anything in tftp. Tried it, it sucked and I don't recommend it.
By the way to temporarily get some files onto your client, the easiest way I found (after trying to mount and unmount virtual floppies and other annoyances) is simply just to dump stuff in "folder", then mkisofs -o bla.iso folder. then use that as the CD image. This can be useful for dumping small data, such as the tftp client onto the client machine.
2. OK, finally we arrive at option 2, the default option, the one I'm using now and the one I recommend: tun/tap
This does true network bridging and requires some root priviledges. This option is enabled as long as you don't do a -user-net.
What it does is create (using /dev/net/tun) firstly a virtual network card on your host machine for the virtual network between host and client. This is generally tun0 (you can see it with ifconfig). The default ip is something like 172.20.0.1, though you can change with ifconfig.
Then with the virtual network card on the client, it can talk on *this* network to your host. You can then ping 172.20.0.1 from client and it *actually* goes through to the REAL host machine. So, any ports you have open on your real host machine you can access from the internal network. I have an ftp server up on my host and with this I can access it from the client simply with "ftp 172.20.0.1". If you like samba and windoze networkin (may your soul be saved), just run a samba server on the host and connect to it from the client. etc. You get the idea. You can even let it access your cups server on 631 and print from the virtual machine :)
Now this is a LOT more versatile since you can run any server on the host and connect to it from the client.
It also allows for a REAL network bridge, something like this:
client (172.20.0.2) <--- internal net ---> (172.20.0.1) host / qemu / firewall (142.5.21.41 or whatever your real IP is) <--- external net ---> Internet
This would require some esoteric firewalling / packet filtering, or what not (basically sets up a router I think), which I'm too lazy to investigate right now. But googling around should get you a decent guide. VMWare installs this by default so its easy peasy. QEmu does not. but you can get the functionality with a bit of work and have more control (and understanding) of it than you ever possibly could with vmware.
One caveat to this is that you need permissions on /dev/tun. What I did was mod the udev permissions so that anyone in the "admin" group can write to it. This might / might not be what you want. If it is, add:
net/tun:root:admin:660
to your udev permissions.
Phew! Hope this helps :)
Lunde
August 2nd, 2005, 04:33 AM
Nice. But what do you meen by:1. Using -user-net:
This does not do ANY sort of true networking with anything outside the virtual machine. Hence it is completely user mode: user runnable and no need for root. It does not do any communication with any ports on your actual machine, everything is completely faked in user space:
This on a normal setup with a network card connection, lets you connect with the actual network. Worked for me on the first try.
geearf
August 2nd, 2005, 07:45 AM
Hello,
it's me again, back from the fight with qemu :)
Then here what's good or not for me :
1- instead of samba, I use the 'connect a network drive option' as our drivers are in NFS under Ubuntu, that is not that bad I guess ..
2- AMD64 can't use ./configure, I had to use ./configure --target-list=x86_64-softmmu, and kqemu just crash qemu :(
3- I can't seem to understand how to make a simple copy / paste between Ubuntu and Windows (in fact I would need the ability to copy images too, just like in Virtual PC).
4- I can't put a CD in the drive to read it under Windows, if Windows was already started through qemu before.
In a few hours I may be able to tell you how fast it is on the amd64 comp, but for the moment still installing (and no more than 2Gb could be allocated too).
Thanks,
Lunde
August 2nd, 2005, 08:11 AM
There's no stabile version of KQemu on AMD64 yet I think, but there's supposed to be an alpha out there.
..the performance will drop a bit without KQemu
As for the copy / paste, I don't remember if there is a fix for that. I'm on VMware and find it a better option for my type of work.
The CD problem we did a round on that a coupple of pages back, I think the solution is in the terminal window (Monitor window) that started Qemu. where you can eject and insert disks and cd's.
I don't have Qemu operative anymore, but I'll try to help you as much as I can
geearf
August 2nd, 2005, 08:15 AM
Thanks for your help, I appreciate.
Just to explain it a bit more, my only goal here is to be able to use Office perfectly, people some folks here would like do their work under linux, do their report under Office, but without the need to swith computer or else :)
And the problem with VMWARE is that it costs a lot, and it's one license by proc I think, and some comp here have up to 4 proc, so it might get a bit expensive just for a little Word / Powerpoint.
rcerreto
August 2nd, 2005, 08:27 AM
Hello,
...
4- I can't put a CD in the drive to read it under Windows, if Windows was already started through qemu before.
...
1) Insert the CD/DVD
2) type "Ctrl-Alt-2" to open qemu console
3) type "change cdrom /dev/cdrom" or whatever your CD/DVD drive is
(yes, "change" even if there was no CD to change)
4) "Ctrl-Alt-1" to get back into the guest windows
5) Your CD/DVD is now accessible
It works for me, hope it will for you too
geearf
August 2nd, 2005, 08:33 AM
Thanks for this tip :)
Lunde
August 2nd, 2005, 10:04 AM
Thanks for your help, I appreciate.
Just to explain it a bit more, my only goal here is to be able to use Office perfectly, people some folks here would like do their work under linux, do their report under Office, but without the need to swith computer or else :)
And the problem with VMWARE is that it costs a lot, and it's one license by proc I think, and some comp here have up to 4 proc, so it might get a bit expensive just for a little Word / Powerpoint.
Have you tried Wine or Crossover office
Lunde
August 2nd, 2005, 10:05 AM
1) Insert the CD/DVD
2) type "Ctrl-Alt-2" to open qemu console
3) type "change cdrom /dev/cdrom" or whatever your CD/DVD drive is
(yes, "change" even if there was no CD to change)
4) "Ctrl-Alt-1" to get back into the guest windows
5) Your CD/DVD is now accessible
It works for me, hope it will for you too
Thanks I'll put this in the end of the howto
geearf
August 2nd, 2005, 10:15 AM
Have you tried Wine or Crossover office
Yes of course, and none of them did the job (and I tried a lot of versions of wine, and both the demo and the src of CrossOver)..
It seems they work with office XP but I only have 2003 licences here.
rcerreto
August 2nd, 2005, 11:16 AM
Thanks kLy, quite useful!!
Using tun/tap I can easily access the host samba and ftp servers.
Most important thing I can print now!
If you want to give the guest full access to the intranet/internet you just need to issue two commands in the host:
echo 1 > /proc/sys/net/ipv4/ip-forward # to allow packet forwarding
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # to enable NAT, change the net device accordingly
your choice where to put them but take into account the security issues. I placed them in a script together with some other iptables commands.
BTW, tun seems to disable dhcp services to the guest.
I had to assign addresses by hand: guest = 172.20.0.2, gateway = 172.20.0.1, DNS = my ISP dns (see /etc/resolv.conf)
Thanks a lot to all people posting in this thread!!!!
Qemu is great, long live qemu and to the people which are working on it
geearf
August 2nd, 2005, 11:55 AM
Yes you cannot use DHCP within the guest OS (well at least with windows) :)
kLy
August 2nd, 2005, 04:25 PM
Yeah, if you run with -use-net, it sets up a fake virtual dhcp server that sets the client address to 10.0.something
You could I guess set up a REAL dhcp server on the host to do the job, but that's overkill. I just assigned the client IP manually. Make sure it's in the same subnet as the host IP tho!
This on a normal setup with a network card connection, lets you connect with the actual network. Worked for me on the first try.
OK, let me correct myself :) This was very early in the morning when I tried it. lol. It seems that you CAN actually connect to the rest of the net using -user-net. Sorry!
It's just that it does a fake internal network (and with fake samba if you want it). You just can't do certain things like ping since it requires root priviledges. See here:
http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC21
kLy
August 2nd, 2005, 04:57 PM
hey. another tip.
Hope this wasn't mentioned before. The qcow image format is great! It lets you only use up as much space as needed for the actual files, not the empty space and it's fully windoze 98 compatible:
qemu-img create -f qcow bla.img
Now these things can grow and even if you delete data, it still stays that big. Why because data isn't actually deleted! It's only marked as deleted and so the sectors are still filled with 1's and 0's. Now what you need to do is a disk space zero. Now most of the packages out there do space WIPING. I couldn't find any for space zeroing. What they want to do is securely delete all their kiddy porn using DOD standards compliant writing of various patterns into "empty" space. This wont help us since what we want is make plain old 0's to reclaim space, not porn-destroying 1's and 0's. Fortunately, certain packages allow you to define your own pattern, ie: 000000000000000
One such (Free) one I found was: http://www.heidi.ie/eraser/default.php
Now this can fill all empty space with 0's, and since we're writing to all this space, it'll make the image as big as the parition can be. ie. HUGE! It'll take up all the space.
BUT! Now that they're just plain old zero's, you can do a convert and qemu will nullify all the empty space:
qemu-img -convert -f qcow old.img -O qcow new.img
This reduced my 300MB image file to 100MB! A great space saver on the host! :)
Now next time, instead of deleting a file, WIPE it with zeroes. This will ensure that if you convert again, you reclaim the space. And you don't need to zero ALL free space ending up with a HUGE image file as an intermediate process.
Hope this helps! :)
kLy
August 2nd, 2005, 05:02 PM
To go with the above, you can also use the -c flag to do disk compression for an even smaller image. I don't think it would be a great performance hit since compression is read only, so you don't recompress data in realtime. ie. new sectors get written in uncompressed format, so you only need cycles to decompress sectors when running the emulator.
Happy Qemulating! :)
geearf
August 3rd, 2005, 06:13 AM
Hello,
I was told that this could help for the copy / past thing :
http://www.idata.sk/~robo/mpcb/
It's a deamon for copy pasting over an tcp/ip network.
Talldave2002
August 3rd, 2005, 08:34 AM
This has been extremely useful, I have managed to emulate both Win98 and WinXP in Qemu, Thanks so much for the info.
I have a slight problem though. I cannot figure out how to have a shared Folder Between my Win98 emulation and my Ununtu/Kubuntu Linux.
I only intend to use the Win98 for a few small progs that i cant find Linux alternatives for.
Can anyone help me?
kLy
August 4th, 2005, 05:48 AM
This has been extremely useful, I have managed to emulate both Win98 and WinXP in Qemu, Thanks so much for the info.
I have a slight problem though. I cannot figure out how to have a shared Folder Between my Win98 emulation and my Ununtu/Kubuntu Linux.
I only intend to use the Win98 for a few small progs that i cant find Linux alternatives for.
Can anyone help me?
check the posts about networking (I think on pg 26). You can either use -user-net -smb for fake samba or run a samba server on your host machine.
gangalee
August 4th, 2005, 06:16 PM
How do I get it recognize the size of the hd.img I created?
When I run the Win98 setup, it scans the (virtual) system registry, then bombs with "Setup requires 734xxx bytes available on your C: drive" I copied and pasted the command straight from your instructions.
Also, how are the USB devices in qemu in general, and how's the Sony NetMD support in particular?
Trojan1313
August 6th, 2005, 08:19 AM
Step 4. STARTING THE GUEST OS
Well.. we're sort of already there, again it's mostly just to change the -boot flag
$ qemu -boot c -fda /dev/fda -cdrom /dev/cdrom -hda hd.img -user-net -pci -m 256 -k en
Description of other flags used in this startup:
-k en
Keybord layout.. works with some languages
-user-net
Lets you connect to the net
-pci -m 256
Amount of memory provided the guest OS
Note: I will not go into details about networking here.. at least not yet. Internet should probably work from the guest without any modifications. To set up shared folders between the guest and the host, a tip is. Install samba, then share the folders with SMB and add the flag -smb /shared/folder to your startup command.
I'm stuck, how do I install the guest OS from my WinXP Boot-CD to the hd-img?
Boot as in install-boot, not live. :)
Lunde
August 6th, 2005, 10:12 AM
I'm stuck, how do I install the guest OS from my WinXP Boot-CD to the hd-img?
Boot as in install-boot, not live. :)
$ qemu -boot d -cdrom /dev/cdrom -hda hd.img
Then install as a normal XP installation, let me know if you have any problems reading the CD drive
gangalee
August 6th, 2005, 03:37 PM
I can read the CD fine, it just complains about installing to my hd.img
ira@gator:~/Qemu$ ls -l
total 12
-rwxrwxrwx 1 ira ira 3145728000 2005-08-04 16:11 hd.img
Scanning system registry...
Windows Setup requires 7340032 bytes available on your C: drive
?????????????????????????/
Lunde
August 6th, 2005, 04:03 PM
I can read the CD fine, it just complains about installing to my hd.img
ira@gator:~/Qemu$ ls -l
total 12
-rwxrwxrwx 1 ira ira 3145728000 2005-08-04 16:11 hd.img
Scanning system registry...
Windows Setup requires 7340032 bytes available on your C: drive
?????????????????????????/
First make sure your hd.img is created with the right size.
I had a similar problem with a win98 installation, I formated the hd.img first. Try and see if it helps. No point giving RWX to everybody, it'll do no difference.
Trojan1313
August 6th, 2005, 06:22 PM
$ qemu -boot d -cdrom /dev/cdrom -hda hd.img
Then install as a normal XP installation, let me know if you have any problems reading the CD drive
fourchan@Kaminix:~/Qemu$ qemu -boot d -cdrom /dev/cdrom -hda hd.img
warning: could not open /dev/net/tun: no virtual network emulation
qemu: could not open hard disk image '/dev/cdrom'
I have two optical devices, should I try the other one? (I would've done this directly if it wasn't for another question, I'm not that lazy)
What does the no virtual network emulation mean?
EDIT:
If this will works like I think it will, then I will love you forever. :)
geearf
August 6th, 2005, 06:35 PM
you may need to try the other /dev for your cdrom yes :)
and about the warning, it says that the network between both os won't work if I'm not guessing wrong.
Trojan1313
August 6th, 2005, 08:50 PM
you may need to try the other /dev for your cdrom yes :)
and about the warning, it says that the network between both os won't work if I'm not guessing wrong.
Meaning I won't be able to do something that's impossible anyway? (there's no network services that use network connection between two simultaniously runnings OSs, is there?)
Puh, lucky they warned me. :p
Going to try the other drive after I get some sleep. :)
geearf
August 6th, 2005, 08:52 PM
Wrong there are, else you cannot get the net or anything interesting ;)
Lunde
August 7th, 2005, 04:47 AM
fourchan@Kaminix:~/Qemu$ qemu -boot d -cdrom /dev/cdrom -hda hd.img
warning: could not open /dev/net/tun: no virtual network emulation
qemu: could not open hard disk image '/dev/cdrom'
I have two optical devices, should I try the other one? (I would've done this directly if it wasn't for another question, I'm not that lazy)
What does the no virtual network emulation mean?
Since you have two optical devices, you may have to look into /dev/cdrom0, /dev/cdrom1 and /dev/hdc
Network between the Guest and Host is just like a normal bridged or shared network device. You have an option for virtuel Samba or you can use Samba to share folders from the host. this subject is mentioned a coupple of times in the previous pages of this tread (2-3 pages back I think).
Trojan1313
August 7th, 2005, 07:42 AM
Wrong there are, else you cannot get the net or anything interesting ;)
Oh oh oh... I don't like that. How do I fix this? :p
How will the switch between the OS work? Will it be like I switch betwen Windows and Linux enviroment or will the installed Windows work like a driver for all Windows-programs in Linux?
Lunde
August 7th, 2005, 06:00 PM
Oh oh oh... I don't like that. How do I fix this? :p
How will the switch between the OS work? Will it be like I switch betwen Windows and Linux enviroment or will the installed Windows work like a driver for all Windows-programs in Linux?
What's there to not like? Can you describe your problem a bit more spesific
The network is bridged / routed from your network card, just like you would share your connectin between 2 adapters, just that one is virtual
Qemu is a complete emulator that shares / provide virtual hardware, memory and CPU to the windows / guest environment.
Trojan1313
August 7th, 2005, 07:17 PM
What's there to not like? Can you describe your problem a bit more spesific
The network is bridged / routed from your network card, just like you would share your connectin between 2 adapters, just that one is virtual
Qemu is a complete emulator that shares / provide virtual hardware, memory and CPU to the windows / guest environment.
Ah, I thought I wouldn't be able to use networking with Windows-thingies.
Then should I just ignore the error?
Lunde
August 8th, 2005, 06:18 AM
Ah, I thought I wouldn't be able to use networking with Windows-thingies.
Then should I just ignore the error?
So, what happens if you use the flag -user-net Do you use some kind of special network setup?
djmadkins
August 9th, 2005, 09:40 AM
Anyone having problems getting the cdrom recognized?
I am trying to get winXP instaklled and have downloaded and created the 6 "boot" disk's from M$ so I can install XP. Problem is when I get to the final disk it then asks for the CD to be installed.
I tried the following command lines (as well as remounting the CD, and converting the CD into an ISO even tho it is not a bootable cd):
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom0 -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/hdc -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
Anyone have any ideas?
Is there a link anywherre to an ISO of a "bootable" winXp CD? I could put in my own serial at the appropriate time.
Trojan1313
August 9th, 2005, 11:37 AM
Anyone having problems getting the cdrom recognized?
I am trying to get winXP instaklled and have downloaded and created the 6 "boot" cd's from M$ so I can install XP. Problem is when I get to the final disk it then asks for the CD to be installed.
I tried the following command lines (as well as remounting the CD, and converting the CD into an ISO even tho it is not a bootable cd):
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom0 -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/hdc -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
Anyone have any ideas?
Is there a link anywherre to an ISO of a "bootable" winXp CD? I could put in my own serial at the appropriate time.
...six boot CDs? :s
Sorry Lunde, forgot to write you back. I got it working now. :D
Thanks for your help. :)
btw, is there any way to send files between the virtual disk and the real disk? And is there a way to resize it?
Lunde
August 9th, 2005, 12:09 PM
Anyone having problems getting the cdrom recognized?
I am trying to get winXP instaklled and have downloaded and created the 6 "boot" disk's from M$ so I can install XP. Problem is when I get to the final disk it then asks for the CD to be installed.
I tried the following command lines (as well as remounting the CD, and converting the CD into an ISO even tho it is not a bootable cd):
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/cdrom0 -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
qemu -boot c -fda /dev/fd0 -cdrom /dev/hdc -hda /home/adkinsj/Qemu/hd.img -user-net -pci -m 512 -k en-us
Anyone have any ideas?
Is there a link anywherre to an ISO of a "bootable" winXp CD? I could put in my own serial at the appropriate time.
Some other people have reported strange problems if you have more then 1 CD device.
For the .iso you can use the following command (If this is not what you have already tried):
mkisofs -RJ -o file.iso /cdrom/
Then link up the cdrom as -cdrom file.iso
Do you have more then 1 CD player (RW / R)?
Lunde
August 9th, 2005, 12:15 PM
...six boot CDs? :s
Sorry Lunde, forgot to write you back. I got it working now. :D
Thanks for your help. :)
btw, is there any way to send files between the virtual disk and the real disk? And is there a way to resize it?
Resize:
http://www.carlsonhome.net/computer_help_log.php
All the commands regarding fdisk is not written in this howto, but it shows the general procedure. You don't have to use Knoppix, any distro / livecd with ntfs resize and fdisk may do.
As for inserting files into the image, I've read somewhere that its possible, but can't remember how. I don't see the point, it's a better solution to set up networking and shared forlders.
Trojan1313
August 9th, 2005, 01:23 PM
Resize:
http://www.carlsonhome.net/computer_help_log.php
All the commands regarding fdisk is not written in this howto, but it shows the general procedure. You don't have to use Knoppix, any distro / livecd with ntfs resize and fdisk may do.
As for inserting files into the image, I've read somewhere that its possible, but can't remember how. I don't see the point, it's a better solution to set up networking and shared forlders.
Oh, right, I forgot I'm in network with my guest. :p
tmasboa
August 9th, 2005, 05:19 PM
mine says it can't find qemu
Lunde
August 10th, 2005, 06:46 AM
mine says it can't find qemu
How far did you get with the installation?
gangalee
August 10th, 2005, 01:57 PM
First make sure your hd.img is created with the right size.
I had a similar problem with a win98 installation, I formated the hd.img first. Try and see if it helps. No point giving RWX to everybody, it'll do no difference.
It does seem to not be the proper size, since I tried formatting the hd.img with fdisk in the dos window and it bombed out after 32% saying no space left in the drive. What's wrong with my size?
Lunde
August 10th, 2005, 02:18 PM
It does seem to not be the proper size, since I tried formatting the hd.img with fdisk in the dos window and it bombed out after 32% saying no space left in the drive. What's wrong with my size?
Do you have enough space left on your drive?
Try to create the image with dd instead:
$ dd of=hd.img bs=1024 seek=2000000 count=0
..will create an image almost 2gig
Trojan1313
August 10th, 2005, 06:43 PM
I was thinking 'bout something... I have some network problems in Linux wich I didn't have in Windows... will I have those if I emulate Windows like this?
fago
August 10th, 2005, 07:23 PM
I was thinking 'bout something... I have some network problems in Linux wich I didn't have in Windows... will I have those if I emulate Windows like this?
yes, i think so
i'm currently installing winme, seems to work great.
i just wanted to note that another quick option to install the latest qemu without kqemu is to download the binary tgz from qemu-site and convert it with alien to a deb.
c4pp4
August 10th, 2005, 11:43 PM
so finally i got it!
my first problem was that i didn't know where paste: kernel_path="/usr/src/linux-headers-2.6.10-5-386"
because there are two places within the configure file.
then came first error after command ./configure
ERROR: QEMU requires SDL or Cocoa for graphical output To build QEMU with graphical output configure with --disable-gfx-check Note that this will disable all output from the virtual graphics card
after i used ./configure --disable-gfx-check it was o.k.
then came next error after command make, something like:
dyngen: ret or jmp expected at the end of op_divb_AL_T0 ...
i found out that i didn't install gcc (there was installed only gcc-3.3 in the synaptic)
i erased qemu dir and began again
after command checkinstall next error
dpkg-deb: subprocess paste killed by signal (Broken pipe)
i erased qemu dir and began again
instead of checkinstall i used sudo make install and there was no problem finally
my cpu ran 100% all the time so it was very slow :(
when i fired up qemu command for 256MB of mem it didn't run and wanted me to use:
sudo umount /dev/shm
sudo mount -t tmpfs -o size=272m none /dev/shm
so i did it and it works but i don't understand it (:o?)
sequence of my steps to the end:
i downloaded from http://fabrice.bellard.free.fr/qemu/download.html
qemu-0.7.1.tar.gz and kqemu-0.7.1-1.tar.gz to my /home/user/temp
fired up terminal
uname -r
checked all packages:
sudo apt-get install linux-headers-2.6.10-5-386
sudo apt-get install make
sudo apt-get install gcc
sudo apt-get install libsdl1.2-dev
sudo apt-get install zlib1g-dev
cd temp
tar zxvf qemu-0.7.1.tar.gz
cd qemu-0.7.1
tar zxvf ../kqemu-0.7.1-1.tar.gz
sudo chmod -R 775 /home/user/temp/qemu-0.7.1
i found out where synaptic installed files for linux-headers
sudo gedit configure
i changed path right here:
# Linux specific kqemu configuration
if test $kqemu = "yes" -a $linux = "yes" ; then
# find the kernel path
if test -z "$kernel_path" ; then
kernel_version=`uname -r`
kernel_path="/lib/modules/$kernel_version/build"
if test '!' -d "$kernel_path/include" ; then
kernel_path="/usr/src/linux-headers-2.6.10-5-386"
if test '!' -d "$kernel_path/include" ; then
echo "Could not find kernel includes in /lib/modules or /usr/src/linux - cannot build the kqemu module"
kqemu="no"
fi
fi
fi
if test $kqemu = "yes" ; then
./configure
make
sudo make install
sudo modprobe kqemu
sudo gedit /etc/init.d/bootmisc.sh
cd ..
cd ..
mkdir Qemu ##/home/user/Qemu
cd Qemu
qemu-img create hd.img 5000M
qemu -boot d -cdrom /dev/cdrom -hda hd.img
sudo umount /dev/shm
sudo mount -t tmpfs -o size=272m none /dev/shm
qemu -boot c -hda /home/user/Qemu/hd.img -user-net -pci -m 256
that's all and many thanks to mr. Lunde for my new experiences with Linux :D
btw: please what about uninstall info from Qemu forum?
Lunde
August 11th, 2005, 06:13 AM
when i fired up qemu command for 256MB of mem it didn't run and wanted me to use:
sudo umount /dev/shm
sudo mount -t tmpfs -o size=272m none /dev/shm
so i did it and it works but i don't understand it (?)
The /dev/shm is the mounted memory for Qemu to use, the command you ran is to increase the amount of memory. I found earlier the place to set the default amout, but can't remember where.
Uninstall:
This is the only answere I got from the Qemu forum. I'll see if I can make an uninstaller shellscript that reads the tar directory and removes the files from the system, but I don't have time for a coupple of weeks, I'm moving and will not be on the net for a while.
I faced the same problem months ago. Finally, I searched my harddisk for all the qemu files.
But I just found a new method: download qemu for linux-i386, and look what is inside the file with a software to uncompress files (like ark in kde). That is the list of all the files created by a compilation of qemu for linux on your harddisk.
There are other files, like /etc/qemu-ifup-sudo, or /dev/kqemu, but it is better not to delete them if you want to reinstall qemu. You would have to spend time creating them again.
You can delete the kqemu module in /lib/modules/kernel_version/misc
If you do this, don't forget to remove the:
# Start Qemu with KQemu accelerator
/sbin/modprobe kqemu
mknod /dev/kqemu c 250 0 # Create the KQEMU device
chmod 666 /dev/kqemu # Make it accessible to all users
from the /etc/init.d/bootmisc.sh
gangalee
August 11th, 2005, 02:01 PM
Do you have enough space left on your drive?
Try to create the image with dd instead:
$ dd of=hd.img bs=1024 seek=2000000 count=0
..will create an image almost 2gig
I'm still having problems getting this to install Windows, now it just freezes. Could I use an existing hd.img? I remember seeing something about OSZoo. Is there a Win98 image I could download and use?
Lunde
August 11th, 2005, 06:52 PM
I'm still having problems getting this to install Windows, now it just freezes. Could I use an existing hd.img? I remember seeing something about OSZoo. Is there a Win98 image I could download and use?
Are you using a XP recovery cd that came with your comuter? That may cause problems, the hardware is completly different when Qemu emulates it.
gangalee
August 12th, 2005, 09:41 AM
Are you using a XP recovery cd that came with your comuter? That may cause problems, the hardware is completly different when Qemu emulates it.
It's a Win98SE install disk.
Here's my disk space:
ira@gator:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 26G 21G 4.1G 84% /
tmpfs 249M 0 249M 0% /dev/shm
/dev 26G 21G 4.1G 84% /.dev
none 5.0M 2.8M 2.3M 56% /dev
/dev/sda1 488M 216M 273M 45% /media/usbdisk
/dev/hdc 626M 626M 0 100% /media/cdrom0
Lunde
August 12th, 2005, 09:50 AM
It's a Win98SE install disk.
Here's my disk space:
ira@gator:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 26G 21G 4.1G 84% /
tmpfs 249M 0 249M 0% /dev/shm
/dev 26G 21G 4.1G 84% /.dev
none 5.0M 2.8M 2.3M 56% /dev
/dev/sda1 488M 216M 273M 45% /media/usbdisk
/dev/hdc 626M 626M 0 100% /media/cdrom0
win98 you need to start without KQemu if you have installed it... I think that's what causing the problem.
-no-kqemu
in the startup command
gangalee
August 12th, 2005, 10:23 AM
win98 you need to start without KQemu if you have installed it... I think that's what causing the problem.
-no-kqemu
in the startup command
I haven't installed KQemu (as far as I know).
Sorry, I really appreciate you trying to help me out- what's the exact syntax?
ira@gator:~/Qemu$ qemu -boot d -cdrom /dev/cdrom -hda hd.img -no-kqemu
qemu: invalid option -- '-no-kqemu'
ira@gator:~/Qemu$ qemu -boot-no-kqemu d -cdrom /dev/cdrom -hda hd.img
qemu: invalid option -- '-boot-no-kqemu'
Lunde
August 12th, 2005, 10:29 AM
I haven't installed KQemu (as far as I know).
Sorry, I really appreciate you trying to help me out- what's the exact syntax?
ira@gator:~/Qemu$ qemu -boot d -cdrom /dev/cdrom -hda hd.img -no-kqemu
qemu: invalid option -- '-no-kqemu'
ira@gator:~/Qemu$ qemu -boot-no-kqemu d -cdrom /dev/cdrom -hda hd.img
qemu: invalid option -- '-boot-no-kqemu'
Correct should be like this:
qemu -boot d -cdrom /dev/cdrom -hda hd.img -no-kqemu
So you compiled it without kqemu or did you just do atp-get install qemu?
gangalee
August 12th, 2005, 07:06 PM
Correct should be like this:
qemu -boot d -cdrom /dev/cdrom -hda hd.img -no-kqemu
So you compiled it without kqemu or did you just do atp-get install qemu?
I just apt-get install qemu
The syntax you just gave me is the same as the one I tried. Notice the error.
Is it a conspiracy to keep me from escaping booting into Windoze!!???
n1tro
August 16th, 2005, 01:36 AM
Thanks for the great tutorial. I had to redo the steps several times because I am a complete n00b at Linux but I managed to get XP sp2 installed onto my Asus laptop. :) But here something odd that happened and maybe the more experienced users can answer this one for me quickly. When I first installed qemu and made the launcher for it, I had the option (-cdrom /dev/cdrom) for the cdrom to be emulated fine. However, now when I press on my launcher, nothing happens. But when I take out the option for the cdrom in the command line, qemu boots my XP fine. What's up with that? Does it have anything to do with me installing cd/dvd burning apps? Possibly the new apps took over control of the cdrom? Any help is greatly appreciated.
Ozziej
August 16th, 2005, 06:07 PM
I tried installing kqemu bu i get the following error:
Warning: could not find /home/ozzie/documents/download/qemu-0.7.1/kqemu/.kqemu-mod.o.cmd for /home/ozzie/documents/download/qemu-0.7.1/kqemu/kqemu-mod.o
i get this while doing make in de qemu dir. I followed every step in the howto, but i cant get past make, cause it keeps on giving this error.
does anyone know what to do about it?
i tried redownloading the files and extracting them but that doesnt help.
btw, both of the files named in the error message are in the specified diretory.
n1tro
August 17th, 2005, 09:11 AM
Solved my own problem. Apparently you have to put "sudo" in front of the command line for qemu for it to run with the cdrom option. otherwise it would just run the hard drive image. :-?
Thanks for the great tutorial. I had to redo the steps several times because I am a complete n00b at Linux but I managed to get XP sp2 installed onto my Asus laptop. :) But here something odd that happened and maybe the more experienced users can answer this one for me quickly. When I first installed qemu and made the launcher for it, I had the option (-cdrom /dev/cdrom) for the cdrom to be emulated fine. However, now when I press on my launcher, nothing happens. But when I take out the option for the cdrom in the command line, qemu boots my XP fine. What's up with that? Does it have anything to do with me installing cd/dvd burning apps? Possibly the new apps took over control of the cdrom? Any help is greatly appreciated.
gangalee
August 17th, 2005, 09:54 AM
If anyone gets a clean Win98SE image built, could you send it to me before you start customizing it?
Thanks,
rherman
August 17th, 2005, 12:37 PM
I'm a complete noobie at this, but I am going to give it a try. I own a license for Windows 2000 and Windows 2000 Server. I only need to run a few simple apps in emulation. How can I avoid the lengthy install and load a "skinnier" version if one exsists? Or do I just do a complete install and how do i trim off the fat? Thanks.
Rob
rherman
August 17th, 2005, 07:12 PM
NEWBIE WARNING****
The install works as written step-by-step; HOWEVER, make your hd image size larger than 3500M for Win 2K Server. I just finished rebooting the hd.img after installing, and my 'c:' drive shows 132kb free! Is there a way to change the hd.img size available at this point? Please say yes.
Rob
edongski
August 17th, 2005, 10:23 PM
Pardon me for my inability to comprehend. I have this problem:
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/root/qemu-0.7. 1/target-i386 -I/root/qemu-0.7.1 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFI LE_SOURCE -I/root/qemu-0.7.1/fpu -I/root/qemu-0.7.1/slirp -c -o translate-op.o / root/qemu-0.7.1/translate-op.c
In file included from /root/qemu-0.7.1/translate-op.c:36:
op.h: In function `dyngen_code':
op.h:12842: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions, see
<URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
make[1]: *** [translate-op.o] Error 1
make[1]: Leaving directory `/root/qemu-0.7.1/x86_64-softmmu'
make: *** [all] Error 1
**** Installation failed. Aborting package creation.
Cleaning up...OK
I just followed the instructions but I get this.
Thank you for your help.
EDIT:
I skipped the QEMU WITH KQEMU ACCELERATOR procedure.
I got the WinXP to install but when I enter: qemu -boot c -fda /dev/fda -cdrom /dev/cdrom -hda hd.img -user-net -pci -m 256 it shows the attached image.
What did I do wrong? Please help.
ShagzModo
August 18th, 2005, 06:59 AM
Thanks for the info!
I will try implementing this tonight, see if i can reverse engineer Active Directory / Exchange to get rid of microsoft licensing fees.... should all be done tomorrowmorning... ;-)
s_p_a_r_k_y
August 18th, 2005, 12:10 PM
hi...I'm having a problem as my tun0 is 172.20.0.1 so I setup win98 to use 172.20.0.2
I can ping from windows the linux machine and the reverse as well. However I'm not sure how to setup the routing.... I cannot ping from the windows virtual machine my Router which is 192.168.0.1. I tried
iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
to nat masquerade traffic from the tun0 device. Can someone help or should I just put tun0 into the 192.168.0.0/24 range and the win98 machine as well?
EDIT
I CAN ping the 192.168.0.8 address which is eth0 on the host computer. However it doesn't seem to be routing and letting the packets out.
sudo iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
eth1 Link encap:Ethernet HWaddr 00:90:4B:68:F2:A4
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::290:4bff:fe68:f2a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79817 errors:0 dropped:0 overruns:0 frame:0
TX packets:82751 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29359588 (27.9 MiB) TX bytes:48261534 (46.0 MiB)
Interrupt:19 Base address:0x8000
tun0 Link encap:Ethernet HWaddr 00:FF:19:F1:D2:24
inet addr:172.20.0.1 Bcast:172.20.255.255 Mask:255.255.0.0
inet6 addr: fe80::2ff:19ff:fef1:d224/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11970 (11.6 KiB) TX bytes:8692 (8.4 KiB)
s_p_a_r_k_y
August 20th, 2005, 12:29 PM
no one?
mulperi
August 21st, 2005, 03:26 AM
Thanks Lunde for this howto.
I tried the version (0.6.1) in Synaptic but win98 crashed with BSOD. It might be because I'm running K7 kernel version.
However with your compile instructions I was able to make a working copy. I also did not even know something as good as checkinstall existed \\:D/
//mulperi
Lunde
August 26th, 2005, 10:06 AM
Hi all!
I just moved to Sweden and have not been able access the internet. I'll be back online and can answere your questions in about a week from now.
mata_svada
August 27th, 2005, 01:28 AM
What it does is create (using /dev/net/tun) firstly a virtual network card on your host machine for the virtual network between host and client. This is generally tun0 (you can see it with ifconfig). The default ip is something like 172.20.0.1, though you can change with ifconfig.
This just doesn't work on my PC: When I boot Windows with qemu and then go to ifconfig, it only shows my normal eth0.
I modified my udev and it didn't help.
Any idea what I'm doing wrong??
Trojan1313
August 27th, 2005, 01:25 PM
Hi all!
I just moved to Sweden and have not been able access the internet. I'll be back online and can answere your questions in about a week from now.
Welcome. ;)
domstyledesign
August 27th, 2005, 04:56 PM
I have a dual boot system w/ one hd. ubuntu on /dev/sda2 and windows on /dev/sda1.
if i use
qemu -hda /dev/sda1 -snapshot -user-net
qemu just hangs @ "Booting from hard disk..."
however, if i use
qemu -hda /dev/sda -snapshot -user-net
then GRUB loads and i can select windows. however, after doing so, this is all i get:
Booting 'Windows XP Pro SP2'
root (hd0,0)
Filesystem type is fat, partition type 0xc
savedefault
makeactive
chainloader +1
Disk error
Press any key to restart
Boot from Hard Disk 0 failed
FATAL: Could not read the boot disk
is there any way i can make this work w/o making an image of my windows partition?
fig_jam_uk
August 27th, 2005, 06:19 PM
Well, I just got sound working in XP.
Qemu emulates a sound blaster 16 sound card and I manually installed this new device through the windows add hardware wizard. I followed this guide (http://www.ubuntuforums.org/showthread.php?t=32063&highlight=audio) to get multiple sounds working. Then I ran Qemu with this option -enable-audio Hope it helps.
Qemu seems to continuously use the ALSA driver because while it is running, I cannot play any sounds in hoary due to the ALSA driver being in use.
...hopefully there is a solution
thankyou very much now all i need to figure out is to get rid of the 169 IP im plagued by ](*,) ](*,)
flange
August 28th, 2005, 03:01 PM
Hi
When trying to ./configure I get this:
kbuild type 2.6
ERROR: QEMU requires SDL or Cocoa for graphical output
To build QEMU with graphical output configure with --disable-gfx-check
Note that this will disable all output from the virtual graphics card.
I did install libsdl1.2-dev :( What's wrong?
Did anyone else encounter this problem and solve it? I'm stuck on this now, and so far haven't found a fix.
fig_jam_uk
August 28th, 2005, 04:28 PM
Hi Lunde thanx for a very helpfull how to... :razz:
I have tried win 98SE, win ME and XP all install and run fine :) the only problem is they wont go on the net, reading what other people have posted on this thread and others it looks like i need some sort of VPN/Tunneling connection, i have installed a few packages and i managed to get tun working with a 172IP after it asked for my password :) yay (much joy and rejoycing) but upon a second check with ifconfig i see that it has dissapeard again after about only 10 seconds (boo hoo :-x ) if anybody can give me any pointers it would be greatly appreciated.... ](*,) ](*,) ](*,)
mata_svada
August 30th, 2005, 04:01 AM
Hi Lunde thanx for a very helpfull how to...
I have tried win 98SE, win ME and XP all install and run fine the only problem is they wont go on the net, reading what other people have posted on this thread and others it looks like i need some sort of VPN/Tunneling connection, i have installed a few packages and i managed to get tun working with a 172IP after it asked for my password yay (much joy and rejoycing) but upon a second check with ifconfig i see that it has dissapeard again after about only 10 seconds (boo hoo ) if anybody can give me any pointers it would be greatly appreciated....
ehhmm..., fig_jam_uk, did you get a connection between Ubuntu and the guest OS working. If yes, could you tell me what I did wrong (have a look at my post above)
thx a lot...
meastp
August 30th, 2005, 10:31 AM
Hi!
This looks amazing! Now it will be easier, not having to reboot when transferring stuff to my minidisc (hopefully, anyway)!
However, there is one thing I have always wanted, and that is to play good, old Command & Conquer (Tiberian Dawn) and Red Alert (1) on LAN (Need win95 or 98 for that). Do you think that would be possible?
---
meastp
CHUCKYCHUCK
August 31st, 2005, 05:08 AM
Hi ! ( my 1st post on the english-speaking ubuntu forum :) ) I plan to use Qemu to install win xp, but i have a few question :
_ how much ram/hard drive space would you advise me to use ?? ( i think i'll juste use quicktime pro, flash mx, virtual dub, dvd shrink | not at the same time :D ), and i have a P4 3Ghz, 512 Ram
_ how can we share files between the fake windows and ubuntu ?? :
_can we access the ubuntu partitions directly ? or do we have to 1st write the files in the hd image and then copy them under ubuntu ??
_ the emulated windows can access the cd-driver and burn cds/dvds can it ??
Thanks
domstyledesign
August 31st, 2005, 09:17 AM
how much ram/hard drive space would you advise me to use ?? ( i think i'll juste use quicktime pro, flash mx, virtual dub, dvd shrink | not at the same time :D ), and i have a P4 3Ghz, 512 Ram
_ how can we share files between the fake windows and ubuntu ?? :
_can we access the ubuntu partitions directly ? or do we have to 1st write the files in the hd image and then copy them under ubuntu ??
_ the emulated windows can access the cd-driver and burn cds/dvds can it ??
i'd recommend 256mb ram and 2gb hd space. You can use smb to share files (check the man page). The man page says that qemu will give windows CD-ROM support, but not CDR/RW or DVD support.
gangalee
August 31st, 2005, 09:36 AM
Hi!
This looks amazing! Now it will be easier, not having to reboot when transferring stuff to my minidisc (hopefully, anyway)!
---
meastp
This is pretty much all I use Windoze for, my Mini-disc. I haven't been able to install a hd.img yet however. Could you send me your Windows.img?
CHUCKYCHUCK
August 31st, 2005, 10:19 AM
thx domstyledesign, well i think i'll use wine for dvd shrink ...
domstyledesign
August 31st, 2005, 01:27 PM
no prob chuck. now if i could only get help with my problem...
I have a dual boot system w/ one hd. ubuntu on /dev/sda2 and windows on /dev/sda1.
if i use
qemu -hda /dev/sda1 -snapshot -user-net
qemu just hangs @ "Booting from hard disk..."
however, if i use
qemu -hda /dev/sda -snapshot -user-net
then GRUB loads and i can select windows. however, after doing so, this is all i get:
Booting 'Windows XP Pro SP2'
root (hd0,0)
Filesystem type is fat, partition type 0xc
savedefault
makeactive
chainloader +1
Disk error
Press any key to restart
Boot from Hard Disk 0 failed
FATAL: Could not read the boot disk
is there any way i can make this work w/o making an image of my windows partition?
confused
September 1st, 2005, 02:55 AM
cannot connect to fabrice.bellard website. No such site exists. Is there any other source to download the qemu source codes
CHUCKYCHUCK
September 1st, 2005, 04:26 AM
Could you tell me exactly what to do to share files between WinXP and ubuntu with samba ??
( i'm a samba newbie )
i tried to do what's written in the " WinXP under Qemu " wiki page, but i didn't succeed ...
thx
here's what i've already done :
installed samba via synaptics
_ shortcut=>connect server, service type : windows share
server : mshome
share : qemushare
folder : #i left this blank
user name: qemushare
connection name : qemushare
then:
_ system=> administration=> shared folders
i shared my home folder : share with samba, name : home
i start qemu sith the option -smb qemushare
in the emulated winxp, i can't access anything ...
could u help me ? thx ( P.S. i use win XP )
Beestar
September 1st, 2005, 08:00 AM
Hi all!
I had a severe problem with sharing files in a Samba directory, I even posted this in the qemu forum:
The problem is this: how to share files between the Linux host OS and the Windows guest OS. Preferably not using FTP, but by sharing a directory. This should be possible, according to QEMU's author's documentation, Fabrice. So far, I haven't succeeded.
I have Kubuntu 5.04 as host, Win2K as guest. I compiled qemu 0.7.0, without accellerator, from source and installed it, using the standard ./configure, make, sudo make install. Following this thread I conclude that the file sharing problem is not limited to the Kubuntu/Win2K combination, but dare I say to all Linux host / Windows guest combinations?
I start qemu as non root with:
$ qemu -user-net -smb /home/bee/qemuwinshare hd.img
In the guest Win2K I can ping 10.0.2.2 and 10.0.2.3 fine. However, 10.0.2.4 (the supposed Samba server) does not respond.
I put "10.0.2.4 smbserver" in /winnt/system32/drivers/etc/lmhosts (not in lmhosts.sam!). "\\smbserver\qemu" is not accessable in Windows Explorer.
My smbd is installed in the place qemu expects it: /usr/sbin/
Samba is working correctly, other Windows machines can access my Samba share just fine.
When I start qemu with a non-existing directory, qemu doesn't complain and starts, with the same result as with an existing directory.
The Windows user name and password are the same as the one I use to log into Linux.
I chmod'ed the sharing directory to "ugo+rwx".
I can use Internet Explorer from the guest OS to surf the Internet fine.
I really have run out of things to try. I think qemu is an awesome piece of work, and I am dying to use it on a daily basis. However, the file sharing is a must for me.
and thanks to this thread I found the answer. I posted it back into the qemu forum:
There appears to be two typo's in Qemu man page/website/documentation, which are crucial. ;)
1. The IP address should NOT be 10.0.2.4, but 10.0.2.2.
2. The shared directory is NOT in \\10.0.2.2\qemu, but in \\10.0.2.2\<samba share name>
Hope this solution helps a lot of other people, too. To me it was quite frustrating, to say the least... :)
Anyway, good-bye dual booting... :D
Since it took me a loooooooooong time and a lot of effort to find the solution, I hereby ask Lunde to PLEASE make your excellent HowTo even better by adding this information.
Many thanks in advance, and welcome in Sweden, Lunde!
Bee
CHUCKYCHUCK
September 1st, 2005, 09:07 AM
the windows file which has to be modified, is it the same in xp and 2000 ??
i juste have to paste that line at the very end of the file ???
thx
when i try to access the shared file, i have to enter a user name and password ????? strange ....
i have to add that line to the windows file: smbserver 10.0.2.2 right ??
and then from windows \\10.0.2.2\qemushare ??
thx
domstyledesign
September 1st, 2005, 02:07 PM
the windows file which has to be modified, is it the same in xp and 2000 ??
i juste have to paste that line at the very end of the file ???
thx
when i try to access the shared file, i have to enter a user name and password ????? strange ....
i have to add that line to the windows file: smbserver 10.0.2.2 right ??
and then from windows \\10.0.2.2\qemushare ??
thx
your first question is a little unclear. as for the second, i suspect the user name and password are probably in your samba config.
samba users are listed in the samba conf file. try:sudo cat /etc/samba/smbpasswd
you can use the smbpasswd command to add users and change passwords. check the man page for more info, and good luck.
rcerreto
September 5th, 2005, 04:33 AM
hi...I'm having a problem as my tun0 is 172.20.0.1 so I setup win98 to use 172.20.0.2
I can ping from windows the linux machine and the reverse as well. However I'm not sure how to setup the routing.... I cannot ping from the windows virtual machine my Router which is 192.168.0.1. I tried
iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
to nat masquerade traffic from the tun0 device. Can someone help or should I just put tun0 into the 192.168.0.0/24 range and the win98 machine as well?
EDIT
I CAN ping the 192.168.0.8 address which is eth0 on the host computer. However it doesn't seem to be routing and letting the packets out.
sudo iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
eth1 Link encap:Ethernet HWaddr 00:90:4B:68:F2:A4
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::290:4bff:fe68:f2a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79817 errors:0 dropped:0 overruns:0 frame:0
TX packets:82751 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29359588 (27.9 MiB) TX bytes:48261534 (46.0 MiB)
Interrupt:19 Base address:0x8000
tun0 Link encap:Ethernet HWaddr 00:FF:19:F1:D2:24
inet addr:172.20.0.1 Bcast:172.20.255.255 Mask:255.255.0.0
inet6 addr: fe80::2ff:19ff:fef1:d224/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11970 (11.6 KiB) TX bytes:8692 (8.4 KiB)
You need to forward packets through the host real NIC (not tun0):
sudo echo 1 > /proc/sys/net/ipv4/ip_forward # to allow forwarding
sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # change NIC accordingly
dante.hicks
September 7th, 2005, 11:55 AM
Hello all,
thanks to this great howto - and especially c4pp4's post on his way to success, I was able to get qemu 0.7.1 and kqemu to run win xp as well as w2k on my XP2800+ with 1GB RAM and an ATI Radeon 9600 (running the recent fglrx drivers).
My aim is to be able to run a modeling software for which I only have a windows license without having to reboot into windows all the time. And here's the catch: the UI runs only at resolutions of 1280 by 1024 or higher...
Unfortunately Win XP is slow on my machine, even after stripping all the styles and background services. And I mean really slow. Except for the speed problem, it works, even at 1280 by 1024.
Win2k on the other hand runs at a reasonable pace which would allow for the anticipated use - but once I try to switch from 1024 by 768 to a higher resolution, the output is distorted, except for any pictures. To give you an idea of the phenomenon, I attached to screenshots: one at normal resolution, one at 1280 by 1024.
Since I'd like to make the switch away from Windoze as my primary OS to Ubuntu, I'd really appreciate any input on this!
Orunitia
September 9th, 2005, 08:36 PM
Edit: Figured it out. Had to format with fdisk beforehand.
Edit 2: I got it installed, but when it goes to boot, it just freezes, and I have to kill Qemu. Any ideas what could be going wrong?
Bomper
September 10th, 2005, 03:25 PM
New version:
--- qemu-0.7.2
http://fabrice.bellard.free.fr/qemu/changelog.html
--- kqemu-0.7.2
http://fabrice.bellard.free.fr/qemu/kqemu-changelog.html
domstyledesign
September 10th, 2005, 04:05 PM
can anyone explain to me how i can boot windows from my dual boot partition?
Orunitia
September 10th, 2005, 06:55 PM
I got Windows 98 running, but now I can't get online with it. I followed the guide exactly, so I don't know what is wrong. Any help?
MikePB
September 14th, 2005, 11:34 PM
I'm having trouble getting 98 to boot consistantly... plus, the video wn't go above 16 colors/ 640x480, or it'll crash
geearf
September 15th, 2005, 11:55 AM
Hello, just to say that for the moment I am using BOCHS at my university and it works pretty well, I will soon install it on my ubuntu box at home, and test it against qemu I think and see therefore ..
sethmahoney
September 15th, 2005, 12:16 PM
Has anyone gotten this working in Breezy yet? I'd be surprised if the process was much different, but, you know, thought I'd ask before I stepped into it.
rcerreto
September 19th, 2005, 04:55 AM
Has anyone gotten this working in Breezy yet? I'd be surprised if the process was much different, but, you know, thought I'd ask before I stepped into it.
When compiling qemu/kqemu you have to use gcc-3.4 instead of gcc-4.0 (which is the default in breezy) otherwise you'll fail.
After that, I followed the same steps and everything looked OK but...
qemu seems to start and keeps running in the background but no output is produced.
Any suggestion?
Tao
September 20th, 2005, 02:57 PM
When compiling qemu/kqemu you have to use gcc-3.4 instead of gcc-4.0 (which is the default in breezy) otherwise you'll fail.
After that, I followed the same steps and everything looked OK but...
qemu seems to start and keeps running in the background but no output is produced.
Any suggestion?
Qemu run with no problem on my Breezy (exept I have to force gcc3.4 to compile qemu as you said). Your problem (no output) seems to be not directly linked with Breezy.
jervine
September 20th, 2005, 11:47 PM
ei guyz i finally got it running.. the problem is... i cant find other computers on my network... anybody got a solution about it??
fortytwo
September 21st, 2005, 07:00 PM
I was just taking a look at QEMU and noticed that it has "Full system emulation. In this mode, QEMU emulates a full system (for example a PC), including a processor and various peripherials"...Does this mean I could get my non-linux supported printer to work if I ran windows through QEMU?
weijie90
September 24th, 2005, 04:48 AM
IF USING BREEZY OR GCC-4.0:
run this to compile qemu:
cd /path/to/qemuSources
apt-get install gcc-3.4
./configure --cc=/usr/bin/gcc-3.4
make
make install
mthaddon
September 29th, 2005, 04:26 PM
I have QEMU installed in binary mode and have two questions. I should note I'm still using Hoary at the moment.
1) What are the implications of allocating shared memory for emulated machines? Is there a limit to this, and is this the amount of my physical memory?
2) I'd like to install from source so I can install the accelerator as well. This is a little complicated by the fact that I'm running on AMD64 and so my binary install is actually in the 32bit chroot. I can't seem to get past the make script in AMD64. Here's what I get:
[abbreviated]
gcc -g -Wl,-T,/home/mthaddon/downloads/qemu-0.7.2/x86_64.ld -o qemu-i386 elfload.o main.o syscall.o mmap.o signal.o path.o osdep.o thunk.o vm86.o libqemu.a gdbstub.o -lm
/usr/bin/ld:/home/mthaddon/downloads/qemu-0.7.2/x86_64.ld:62: parse error
collect2: ld returned 1 exit status
make[1]: *** [qemu-i386] Error 1
make[1]: Leaving directory `/home/mthaddon/downloads/qemu-0.7.2/i386-user'
make: *** [all] Error 1
Any ideas?
Thanks, Tom
mthaddon
September 29th, 2005, 04:58 PM
Okay, I have it installed, thanks to this thread: http://ubuntuforums.org/showthread.php?t=50203
Still wondering about the shared memory issue - can anyone help me out on that?
Thanks, Tom
sparhawk
September 29th, 2005, 06:24 PM
Ok I have tried installing qemu about 20 times now but keep getting the same error when I run 'make'
Warning: could not find /home/mmartino/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd for /home/mmartino/qemu-0.7.2/kqemu/kqemu-mod.o
CC /home/mmartino/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/mmartino/qemu-0.7.2/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.10-5-386'
make[1]: Leaving directory `/home/mmartino/qemu-0.7.2/kqemu'
I have checked and I have gcc3.4 install so thats not the problems and the permissions are correct of the files.
mmartino@tomdickandharry:~/qemu-0.7.2/kqemu$ ls -al
total 420
drwxrwxr-x 3 mmartino mmartino 4096 2005-09-29 18:12 .
drwxr-xr-x 26 mmartino mmartino 4096 2005-09-29 18:08 ..
-rwxrwxr-x 1 mmartino mmartino 545 2005-09-04 09:46 Changelog
-rwxrwxr-x 1 mmartino mmartino 435 2005-02-12 09:36 install.sh
-rwxrwxr-x 1 mmartino mmartino 5863 2005-09-04 12:47 kqemu-doc.html
-rwxrwxr-x 1 mmartino mmartino 4714 2005-09-04 12:47 kqemu-doc.texi
-rwxrwxr-x 1 mmartino mmartino 7216 2005-08-14 12:34 kqemu-freebsd.c
-rwxrwxr-x 1 mmartino mmartino 4134 2005-08-15 09:30 kqemu.h
-rwxrwxr-x 1 mmartino mmartino 1552 2005-09-03 13:46 kqemu.inf
-rwxrwxr-x 1 mmartino mmartino 1374 2005-08-14 12:26 kqemu-kernel.h
-rwxrwxr-x 1 mmartino mmartino 39385 2005-09-29 18:12 kqemu.ko
-rwxrwxr-x 1 mmartino mmartino 194 2005-09-29 18:12 .kqemu.ko.cmd
-rwxrwxr-x 1 mmartino mmartino 8988 2005-09-03 12:39 kqemu-linux.c
-rwxrwxr-x 1 mmartino mmartino 5816 2005-09-29 18:12 kqemu-linux.o
-rwxrwxr-x 1 mmartino mmartino 9725 2005-09-29 18:12 .kqemu-linux.o.cmd
-rwxrwxr-x 1 mmartino mmartino 1625 2005-09-29 18:12 kqemu.mod.c
-rwxrwxr-x 1 mmartino mmartino 31857 2005-09-04 09:37 kqemu-mod-i386.o
-rwxrwxr-x 1 mmartino mmartino 32002 2005-09-04 12:44 kqemu-mod-i386-win32.o
-rwxrwxr-x 1 mmartino mmartino 31857 2005-09-29 18:12 kqemu-mod.o
-rwxrwxr-x 1 mmartino mmartino 3744 2005-09-29 18:12 kqemu.mod.o
-rwxrwxr-x 1 mmartino mmartino 7098 2005-09-29 18:12 .kqemu.mod.o.cmd
-rwxrwxr-x 1 mmartino mmartino 37032 2005-09-04 12:43 kqemu-mod-x86_64.o
-rwxrwxr-x 1 mmartino mmartino 36275 2005-09-29 18:12 kqemu.o
-rwxrwxr-x 1 mmartino mmartino 199 2005-09-29 18:12 .kqemu.o.cmd
-rwxrwxr-x 1 mmartino mmartino 54012 2005-09-04 12:44 kqemu.sys
-rwxrwxr-x 1 mmartino mmartino 10221 2005-09-03 13:45 kqemu-win32.c
-rwxrwxr-x 1 mmartino mmartino 778 2005-08-14 12:25 LICENSE
-rwxrwxr-x 1 mmartino mmartino 1232 2005-09-04 12:45 Makefile
-rwxrwxr-x 1 mmartino mmartino 184 2005-07-28 17:37 Makefile.freebsd
-rwxrwxr-x 1 mmartino mmartino 992 2005-04-17 12:36 Makefile.winnt
-rwxrwxr-x 1 mmartino mmartino 185 2005-02-12 09:34 README
drwxrwxr-x 2 mmartino mmartino 4096 2005-09-29 18:12 .tmp_versions
The file its looking for... '.kqemu-mod.o.cmd' is in the path its looking for so I am at a loss. When I try to finish the install and load the module it says module not found. Any help in this would be welcome.
mthaddon
September 30th, 2005, 07:56 AM
what does your ./configure look like?
sparhawk
September 30th, 2005, 09:32 PM
Show me yours and I will show you mine... ah just kidding
Here it is
mmartino@tomdickandharry:~/qemu-0.7.2$ ./configure
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /home/mmartino/qemu-0.7.2
C compiler gcc
Host C compiler gcc
make make
host CPU i386
host big endian no
target list i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu
gprof enabled no
static build no
SDL support yes
SDL static link no
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /lib/modules/2.6.10-5-386/build
kbuild type 2.6
So any ideas????????
oddflux
September 30th, 2005, 10:24 PM
Why would you want windows in linux o_0, I think we all agree that windows doesn't tickle our fancy.
sparhawk
October 1st, 2005, 01:09 AM
I would love not to use windows but I work for an IT company and we use Radmin for remote desktop administration and you can not use it in linux if you need NT/Auth... so here I am. I am working on a way around the issue but for a couple of weeks I need Radmin to work... :( I guess that might mean staying with windows for a while.
neouser99
October 4th, 2005, 03:26 AM
Did anyone else encounter this problem and solve it? I'm stuck on this now, and so far haven't found a fix.
Yes, I am also having the same troubles and was wondering how people got around this...it is early in the morning, and maybe I am just too lazy to figure it out...but if it has been figured out, that is easier then trying.
I apologize for the strange message, I thought that the quote would include the quote that flange had inside of it...
here is my error. i have run apt-get install libsdl1.2-dev
root@trinity:~/qemu-0.7.2 # ./configure
big/little test failed
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /root/qemu-0.7.2
C compiler gcc
Host C compiler gcc
make make
host CPU i386
host big endian no
target list i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu
gprof enabled no
static build no
SDL support no
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /usr/src/linux-headers-2.6.10-5-686-smp
kbuild type 2.6
ERROR: QEMU requires SDL or Cocoa for graphical output
To build QEMU with graphical output configure with --disable-gfx-check
Note that this will disable all output from the virtual graphics card.
neouser99
October 4th, 2005, 05:55 PM
Yes, I am also having the same troubles and was wondering how people got around this...it is early in the morning, and maybe I am just too lazy to figure it out...but if it has been figured out, that is easier then trying.
I apologize for the strange message, I thought that the quote would include the quote that flange had inside of it...
here is my error. i have run apt-get install libsdl1.2-dev
root@trinity:~/qemu-0.7.2 # ./configure
big/little test failed
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /root/qemu-0.7.2
C compiler gcc
Host C compiler gcc
make make
host CPU i386
host big endian no
target list i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu
gprof enabled no
static build no
SDL support no
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /usr/src/linux-headers-2.6.10-5-686-smp
kbuild type 2.6
ERROR: QEMU requires SDL or Cocoa for graphical output
To build QEMU with graphical output configure with --disable-gfx-check
Note that this will disable all output from the virtual graphics card.
I seemed to have fixed my problem...qemu's configure was looking for gcc, not gcc-3.3 which was the bin installed on my computer. all i had to do to fix things was softlink using this command
ln -sf /usr/bin/gcc-3.3 /usr/bin/gcc
Hope this helps someone else, if they are having issues.
refdoc
October 5th, 2005, 04:47 AM
My laptop came with one of those stupid recovery disks. The installer stops when probing my qemu install whether it is the real thing.
Anyone any ideas?
Thanks!
Lunde
October 6th, 2005, 03:27 AM
There are problems with some recovery CD's because the hardware that Qemu emulates is not similar the hardware of your computer.
Lunde
October 6th, 2005, 03:29 AM
I'm back, just moved to Sweeden and have not been able to answere any questions the last weeks.
Lunde
October 6th, 2005, 03:47 AM
/home/mmartino/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd (-)
-rwxrwxr-x 1 mmartino mmartino 7098 2005-09-29 18:12 .kqemu.mod.o.cmd (.)
Hmm.. this looks like a typo in this release. I don't know if it's possible and if it would work, but I would try to rename the file.
Ok I have tried installing qemu about 20 times now but keep getting the same error when I run 'make'
Warning: could not find /home/mmartino/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd for /home/mmartino/qemu-0.7.2/kqemu/kqemu-mod.o
CC /home/mmartino/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/mmartino/qemu-0.7.2/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.10-5-386'
make[1]: Leaving directory `/home/mmartino/qemu-0.7.2/kqemu'
I have checked and I have gcc3.4 install so thats not the problems and the permissions are correct of the files.
mmartino@tomdickandharry:~/qemu-0.7.2/kqemu$ ls -al
total 420
drwxrwxr-x 3 mmartino mmartino 4096 2005-09-29 18:12 .
drwxr-xr-x 26 mmartino mmartino 4096 2005-09-29 18:08 ..
-rwxrwxr-x 1 mmartino mmartino 545 2005-09-04 09:46 Changelog
-rwxrwxr-x 1 mmartino mmartino 435 2005-02-12 09:36 install.sh
-rwxrwxr-x 1 mmartino mmartino 5863 2005-09-04 12:47 kqemu-doc.html
-rwxrwxr-x 1 mmartino mmartino 4714 2005-09-04 12:47 kqemu-doc.texi
-rwxrwxr-x 1 mmartino mmartino 7216 2005-08-14 12:34 kqemu-freebsd.c
-rwxrwxr-x 1 mmartino mmartino 4134 2005-08-15 09:30 kqemu.h
-rwxrwxr-x 1 mmartino mmartino 1552 2005-09-03 13:46 kqemu.inf
-rwxrwxr-x 1 mmartino mmartino 1374 2005-08-14 12:26 kqemu-kernel.h
-rwxrwxr-x 1 mmartino mmartino 39385 2005-09-29 18:12 kqemu.ko
-rwxrwxr-x 1 mmartino mmartino 194 2005-09-29 18:12 .kqemu.ko.cmd
-rwxrwxr-x 1 mmartino mmartino 8988 2005-09-03 12:39 kqemu-linux.c
-rwxrwxr-x 1 mmartino mmartino 5816 2005-09-29 18:12 kqemu-linux.o
-rwxrwxr-x 1 mmartino mmartino 9725 2005-09-29 18:12 .kqemu-linux.o.cmd
-rwxrwxr-x 1 mmartino mmartino 1625 2005-09-29 18:12 kqemu.mod.c
-rwxrwxr-x 1 mmartino mmartino 31857 2005-09-04 09:37 kqemu-mod-i386.o
-rwxrwxr-x 1 mmartino mmartino 32002 2005-09-04 12:44 kqemu-mod-i386-win32.o
-rwxrwxr-x 1 mmartino mmartino 31857 2005-09-29 18:12 kqemu-mod.o
-rwxrwxr-x 1 mmartino mmartino 3744 2005-09-29 18:12 kqemu.mod.o
-rwxrwxr-x 1 mmartino mmartino 7098 2005-09-29 18:12 .kqemu.mod.o.cmd
-rwxrwxr-x 1 mmartino mmartino 37032 2005-09-04 12:43 kqemu-mod-x86_64.o
-rwxrwxr-x 1 mmartino mmartino 36275 2005-09-29 18:12 kqemu.o
-rwxrwxr-x 1 mmartino mmartino 199 2005-09-29 18:12 .kqemu.o.cmd
-rwxrwxr-x 1 mmartino mmartino 54012 2005-09-04 12:44 kqemu.sys
-rwxrwxr-x 1 mmartino mmartino 10221 2005-09-03 13:45 kqemu-win32.c
-rwxrwxr-x 1 mmartino mmartino 778 2005-08-14 12:25 LICENSE
-rwxrwxr-x 1 mmartino mmartino 1232 2005-09-04 12:45 Makefile
-rwxrwxr-x 1 mmartino mmartino 184 2005-07-28 17:37 Makefile.freebsd
-rwxrwxr-x 1 mmartino mmartino 992 2005-04-17 12:36 Makefile.winnt
-rwxrwxr-x 1 mmartino mmartino 185 2005-02-12 09:34 README
drwxrwxr-x 2 mmartino mmartino 4096 2005-09-29 18:12 .tmp_versions
The file its looking for... '.kqemu-mod.o.cmd' is in the path its looking for so I am at a loss. When I try to finish the install and load the module it says module not found. Any help in this would be welcome.
Lunde
October 6th, 2005, 04:00 AM
There might be several reasons for this error.
Your screencard does not handle the 2 screens in this resolution, check if you have the latest linux driver.
Might be that it's the resolution change that causes it and not the resolution it self. try to shutdown windows with the new settings even if it's wrong, then restart X and boot up Qemu again
geearf
October 6th, 2005, 06:45 AM
Hello,
I am writing a mini OS, and I use bochs a lot to try it, but I cannot run it on Qemu, it tells me there is no bootable media, where my image is one of a floppy that works fine on bochs and on real hardware.
I'd like to try it on Qemu, to see if it's faster.
Thanks.
Lunde
October 6th, 2005, 08:32 AM
Not sure if it works, but I can't see why not. What command do you use to start it? and are all permissions set correct?
geearf
October 6th, 2005, 08:57 AM
Hello,
I need to set permissions ?
Oh and I tried various commandes like "qemu -boot a -fda image"
Lunde
October 6th, 2005, 09:30 AM
Permissions.. Only that the user you start Qemu with has permissions to use the image.
OK try this.. download a bootdisk image from bootdisk.com and extract the image from the .exe file with Archive Manager. Then see if your able to boot that image to check if the problem is with the image or with Qemu.
geearf
October 6th, 2005, 05:35 PM
Hello,
good guess it works with another image, but not mine (which was made with tools provided by the theachers, that work with bochs and real computer, how strange).
Also about permissions, I only have one user, so no problem there.
Thanks,
barmaley
October 7th, 2005, 05:34 AM
Hallo, guys!
1st of all thank you for this great guide.
2nd of all - HEEEEEEEEELP!
I failed to install win2k for a couple of days already and it drives me crazy. I really need windows on my comp to run OriginLab, Shadow ray tracing and sometimes for MS Word and IE.
The problem is that win2k installation goes smoothely up to a point where it says:
"The disk space on C: is insufficient for the components that are currently selected. You will need to change your component selections".
From this point I don't know what to do. I created an image of 3.5G, should be enough. For installation I use:
qemu -hda win2k.img -cdrom /dev/cdrom -boot d -m 256
After reboot I type 'c' instead of 'd'.
Does anybody know what can be done?
Thank you in advance.
geearf
October 7th, 2005, 08:18 AM
There is a parameter to give to qemu for that bug, I don't remember which but you'll find it in the man of qemu.
Zenbob96
October 7th, 2005, 08:38 AM
If your image area is only set at 3.5 GB for Windows 2000, plus some rather resource hungry applications and the Windows memory manager, you will likely need a larger partition area. I have never tried running Windows on less than about 5.5 to 6.5 GB, as it is a real memory hog, and even when forced into smaller partition sizes (that install indicates will work) it does not work well.
Ubuntu can run very well in very small environments, but of course, it's not the resource zombie that MS Windows ends up being.
If your HDD allows for a bigger Windows environment, go ahead and allocate more space to it, rather than try to compress it all into the most "effecient" envelope possible.
Hard driv prices continue to drop, and if you need to install a new drive or second drive, that is also a reasonable option.
Good Luck!
barmaley
October 7th, 2005, 09:24 AM
Thank you guys!
I'll try both geearf's and Zenbob96's advices. Though throughout the thread 3.5G was enough for everybody and noone came up with my problem.
geearf, if you could remember this option, plese post it here.
I'll try to find it by myself, bit one always wants to save time.
Thank you one more time! Ubuntu guys are great!
barmaley
October 7th, 2005, 03:27 PM
geearf, is this the option you meant?
-win2k-hack
Use it when installing Windows 2000 to avoid a disk full bug. After Windows 2000 is installed, you no longer need this option (this option slows down the IDE transfers).
This is the only option I found in the qemu man to be somehow relevant to my problem, though I did not have full disk error, on the contrary disk was empty and had a capacity of 0 B.
I'll try it. It is strange, I made same steps as everybody did and only I experience this problem. Is it because of my luck or because of win2k? :)
oxEz
October 7th, 2005, 06:18 PM
When I first tried to compile it, I receive an error about 'GENERAL_REG', which can be found here (http://gcc.gnu.org/ml/gcc-bugs/2005-06/msg02034.html).
I fixed it by installing gcc-3.3 (3.4 could be fine), and editing the configure script as follows:
cc="gcc-3.3"
host_cc="gcc-3-3"
It suddently worked. Apparently it won't compile on GCC4.
Thank you for the HOWTO, I have read it and it seems pretty accurate. Thanks!
oxEz
October 7th, 2005, 06:56 PM
Okay, compilation is done, installation is completed. However when I run qemu I have this error:
qemu: could not open hard disk image 'hd.img'
The command I ran was: qemu -boot d -cdrom /dev/cdrom -hda hd.img -user-net
Yes I created the disk image, and I'm in it's directory. I have to mention I'm installing QEMU on a free FAT32 partition newly created (it is totally empty).
Thanks!
[EDIT]
Okay, I figured out that FAT32 file system cannot handle large files.. and obviously 4 GB was a large file. That's why it didn't create the .img at first. I reformated the partition at ext2, and now it works.
barmaley
October 8th, 2005, 05:07 AM
Hallo, guys.
I have at last win2k running with Qemu.
When installing windows 2000, the correct option is -win2k-hack.
It is mentioned in the qemu man.
Win2k runs a bit slower than I expected, but I like it even this way.
Thank you, Lunde for the guide, and geearf and Zenbob96 for your advices.
Great community. :D
dis-abled
October 8th, 2005, 05:11 AM
One thing you may want to add. Instead of using "make install", you could use checkinstall (apt-get install checkinstall or use Synaptic). checkinstall is the best way to install compiled programs because it will make and install deb's instead of just installing the program! This means that you will have QEMU installed as if it were installed via apt-get or Synaptic! Neat stuff! To remove all you would have to do is apt-get remove qemu or removie via Synaptic. That is, everything would be done the same way as if you were to install a deb.
Quick rundown for any source code package using configure:
./configure
make
checkinstall
In other words, just replace the step "make install" with "checkinstall". That's it!
WARNING: make sure you are not running anything that touches your apt database. This means that you should not have Synaptic open or have apt-get running while using checkinstall. This will screw up checkinstall because it will be unable to install the deb files that it makes since the resources will be used by apt-get/Synaptic.
Awsome post, I am going to go try it!! Thanks!
Azrael
October 8th, 2005, 02:39 PM
Kudos for a great howto!
Before I try installing Qemu myself I have some (probably silly) question to ask.
How much hardware can you access from within the guest OS (would be Windows 2000 in my case)? Can you for instance communicate with USB peripherals?
I have a Palm m505 PDA and I would be really nice if I could sync my PDA with my Palm Desktop manager (in Windows 2000 over Qemu over Ubuntu).
meastp
October 11th, 2005, 06:21 AM
How much hardware can you access from within the guest OS (would be Windows 2000 in my case)? Can you for instance communicate with USB peripherals?
Could someone please answer? I want to use qemu->windows to transfer files to my netMD...
Brando569
October 12th, 2005, 01:43 AM
im using vmware 5 and ive set it up correctly according to the directions on their website, when i try to boot grub gives me error 17 anyone know how to fix this?
Azrael
October 16th, 2005, 11:05 PM
Kudos for a great howto!
Before I try installing Qemu myself I have some (probably silly) question to ask.
How much hardware can you access from within the guest OS (would be Windows 2000 in my case)? Can you for instance communicate with USB peripherals?
I have a Palm m505 PDA and I would be really nice if I could sync my PDA with my Palm Desktop manager (in Windows 2000 over Qemu over Ubuntu).
I figured I'd answer my own inquiries in the unlikely case that anyone cares.
No, you can't use USB in a Qemu guest OS. Maybe in the future...
However, if you have a PDA with a network sync function like I have you can still flawlessly sync between your PDA and PDA desktop software in the Qemu guest OS.
After a day of investigating, I arranged it like this:
On the Palm m505:
1) In the main menu choose "HotSync" > "Options" > "LANSync Prefs" > "LANSync".
2) Open "HotSync" > "options" > "Primary PC Setup" and enter as "Primary PC Name" the same name you use in Windows on Qemu and enter as "Primary PC Address" 10.0.2.15 and enter as "Subnet Mask" 255.255.255.0.
In Ubuntu
1)sudo apt-get install pilot-link
2)gedit /path/to/where-ever/you/want/your/shell/script.sh
3)Enter this:
#!/bin/sh
sudo iptables -t nat -A OUTPUT -d 10.0.2.15 -j DNAT --to-destination 127.0.0.1
sleep 2s
sudo pi-nredir -p /dev/ttyUSB1
sleep 40s
sudo iptables -t nat -D OUTPUT -d 10.0.2.15 -j DNAT --to-destination 127.0.0.1
#iptables are being (ab)used because after every sync the Palm resets the IP address
#it uses to the IP of the of the OS in which Palm Desktop runs, which in this case is the
#Qemu guest OS, which more or less needs to have 10.0.2.15 as its IP address.
4)chmod 755 /path/to/where-ever/you/want/your/shell/script.sh
5)sudo gedit /etc/udev/udev.rules
6)Change the line:
BUS=="usb", KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*", \
SYMLINK+="pilot"
To:
BUS=="usb", KERNEL=="ttyUSB1", SYSFS{product}=="Palm Handheld*", \
SYMLINK+="pilot", RUN="/path/to/where-ever/you/want/your/shell/script.sh"
7)Run Qemu with the options "-user-net" and "-redir tcp:14238::14238".
In Windows on Qemu:
1)Open "Palm Desktop" and "HotSync Manager".
2)Right-click the HotSync Manager icon in the systray and check (only) "Network".
3)Right-click the HotSync Manager icon in the systray and click "Setup" and set the correct user if necessary and set "Subnet Mask" to 255.255.255.0.
Syncing with the Palm Desktop should now happen automagically whenever you press the HotSync button on the Palm cradle.
geearf
October 17th, 2005, 04:58 AM
Hello,
I am writing a mini OS, and I use bochs a lot to try it, but I cannot run it on Qemu, it tells me there is no bootable media, where my image is one of a floppy that works fine on bochs and on real hardware.
I'd like to try it on Qemu, to see if it's faster.
Thanks.
still wondering if anyone know anything about that :)
hamacker
October 18th, 2005, 08:20 AM
if "make" show the follow error : "(...)/qemu-0.7.2/target-i386/ops_sse.h:574:
confused by earlier errors, bailing out" then probally you use a gcc4.
Please this form :
./configure --cc=gcc-3.4
make
(continue the article)
Oan
October 18th, 2005, 08:30 AM
I'm trying to install Windows XP with Qemu, following step-by-step this HOW-TO. Qemu installed fine, but alas! - when I try to use the Windows' install cd I encouter the same problem as Karl here (http://www.ubuntuforums.org/showpost.php?p=238348&postcount=150) had:
And this is the problem I came up with:
In the Terminal:
screenshot here (http://www.columbia.edu/~kts15/hblog/KarlQEMU.png)
I've tried to use both my cd-devices with different paths, make an iso-image of the cd and a pile of other "tricks" I've read over here..The result is always the Qemu-screen with "FATAL: Could not read the boot disk".
Were the any solutions for this?
suRoot
October 30th, 2005, 08:46 AM
Qemu is really cool - I've used it before & really like it. However, as the OP stated, performance is second to VMWare. That has been my experience, as well.
Luckily, as of a few days ago, VMWare has started to offer a new option (which happens to be free!!) - it's called VMWare Player. It runs on Ubuntu, as I'm using it now. You can read all about it at the VMWare site, but in a nutshell it only plays VM images - you can't create /edit new ones (although you can open the vmx file in vi or gedit and make some minor device related changes).
Here's what you do:
Download the VMWare Workstation eval at http://www.vmware.com/download/ws/eval.html
Install it (there are several walkthroughs on the boards for doing this - I can help if you have a problem). Once installed, setup as many virtual machines as you want.
After you create your virtual machines, you can get rid of VMWare workstation. Just make sure you've stored the image files someplace else so you can use them again.
Download the VMWare Player at http://www.vmware.com/download/player/
Install it - the process is basically the same as installing VMWare workstation. Once installed, fire it up & point it at your existing VM images. Bingo - now you've got all the benefits of running VMWare -- for free!
I like Qemu - I suggest you try it out as it's a great learning experience. It may run better than VMWare on your machine, anyway. For me, though, VMWare is the better option.
trinaryouroboros
November 2nd, 2005, 04:27 PM
Correction:
$ sudo chmod -R 775 /home/karl/qemu-0.7.0/kqemu
Sorry!
Hey, excellent troubleshooting Lunde!
I'm getting a similar problem however, and I've followed and tracked just about every bit of posted advice I could about Ubuntu / Debian kqemu issues.
I still get the same problem listed previous. I tried even using alternate kernels even to see if maybe my linux-header files and kernel might have had some type of conflict with qemu installs.
To note, I am not using 0.7.0 - the latest I nabbed is 0.7.2, and I'm hoping I can still use this newer package the same as 0.7.0.
I have Ubuntu 5.04 / Hoary Hedgehog - 64-bit edition, running on an AMD64 3000+ processor, Lanparty nF4 Ultra-D mobo with 1GB (2x512) of Corsair RAM, video card temporarily is ATI All-in-Wonder Pro 128 PCI (rage128), hard drive is simple 30GB Western Digital IDE, two cd-roms - the main one I'm using for kqemu purpose is specified as "/dev/cdrw" on my box.
Windows XP Corporate Edition SP2 was installed with qemu by .iso image, successful but miserably slow install, and no operable drivers installed appropriately to surf the internet / exchange files / whatever I need to do - and OS is junkily slow as well during emu. I picked up litexppro, which I will happily use if I can get this thing operable enough, otherwise it's going on my returns list.
A brief idea of what I need XP for: Mainly development and graphic work. I need it primarily for a graphical wargame, of which I'll be happy to update any contributors on it's progress. Genre is Cyberpunk/Hacker orient, mild William Gibson implementation, GNU public license - freeware.
uname -r returns: 2.6.10-5-amd64-xeon
I'm using the appropriate specified linux-headers, and edited the configure file with:
kernel_path="/usr/src/linux-headers-2.6.10-5-amd64-xeon"
I followed all instructions previous, and in order to properly configure, I have to do the following or make just does nothing:
./configure --target-list=x86_64-softmmu
then make is as follows at the kqemu portion:
make[1]: Leaving directory `/home/ouroboros/qemu-0.7.2/x86_64-softmmu'
make -C kqemu
make[1]: Entering directory `/home/ouroboros/qemu-0.7.2/kqemu'
make -C /usr/src/linux-headers-2.6.10-5-amd64-xeon M=`pwd` modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
CC [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu-linux.o
cp /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod-x86_64.o /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not find /home/ouroboros/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd for /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod.o
CC /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
make[1]: Leaving directory `/home/ouroboros/qemu-0.7.2/kqemu'
My kqemu permissions are as follows :
ouroboros@w0-rm-h0-l3:~/qemu-0.7.2$ ls -al kqemu
total 448
drwxrwxr-x 3 ouroboros root 4096 2005-11-02 11:45 .
drwxrwxr-x 26 ouroboros root 4096 2005-11-02 11:43 ..
-rwxrwxr-x 1 ouroboros ouroboros 545 2005-09-04 09:46 Changelog
-rwxrwxr-x 1 ouroboros ouroboros 435 2005-02-12 09:36 install.sh
-rwxrwxr-x 1 ouroboros ouroboros 5863 2005-09-04 12:47 kqemu-doc.html
-rwxrwxr-x 1 ouroboros ouroboros 4714 2005-09-04 12:47 kqemu-doc.texi
-rwxrwxr-x 1 ouroboros ouroboros 7216 2005-08-14 12:34 kqemu-freebsd.c
-rwxrwxr-x 1 ouroboros ouroboros 4134 2005-08-15 09:30 kqemu.h
-rwxrwxr-x 1 ouroboros ouroboros 1552 2005-09-03 13:46 kqemu.inf
-rwxrwxr-x 1 ouroboros ouroboros 1374 2005-08-14 12:26 kqemu-kernel.h
-rw-r--r-- 1 ouroboros ouroboros 48600 2005-11-02 11:45 kqemu.ko
-rwxrwxr-x 1 ouroboros root 200 2005-11-02 11:45 .kqemu.ko.cmd
-rwxrwxr-x 1 ouroboros ouroboros 8988 2005-09-03 12:39 kqemu-linux.c
-rw-r--r-- 1 ouroboros ouroboros 9136 2005-11-02 11:45 kqemu-linux.o
-rw-r--r-- 1 ouroboros ouroboros 8131 2005-11-02 11:45 .kqemu-linux.o.cmd
-rw-r--r-- 1 ouroboros ouroboros 1582 2005-11-02 11:45 kqemu.mod.c
-rwxrwxr-x 1 ouroboros ouroboros 31857 2005-09-04 09:37 kqemu-mod-i386.o
-rwxrwxr-x 1 ouroboros ouroboros 32002 2005-09-04 12:44 kqemu-mod-i386-win32.o
-rwxr-xr-x 1 ouroboros ouroboros 37032 2005-11-02 11:45 kqemu-mod.o
-rw-r--r-- 1 ouroboros ouroboros 5136 2005-11-02 11:45 kqemu.mod.o
-rw-r--r-- 1 ouroboros ouroboros 6384 2005-11-02 11:45 .kqemu.mod.o.cmd
-rwxrwxr-x 1 ouroboros ouroboros 37032 2005-09-04 12:43 kqemu-mod-x86_64.o
-rw-r--r-- 1 ouroboros ouroboros 44382 2005-11-02 11:45 kqemu.o
-rwxrwxr-x 1 ouroboros root 205 2005-11-02 11:45 .kqemu.o.cmd
-rwxrwxr-x 1 ouroboros ouroboros 54012 2005-09-04 12:44 kqemu.sys
-rwxrwxr-x 1 ouroboros ouroboros 10221 2005-09-03 13:45 kqemu-win32.c
-rwxrwxr-x 1 ouroboros ouroboros 778 2005-08-14 12:25 LICENSE
-rwxrwxr-x 1 ouroboros ouroboros 1232 2005-09-04 12:45 Makefile
-rwxrwxr-x 1 ouroboros ouroboros 184 2005-07-28 17:37 Makefile.freebsd
-rwxrwxr-x 1 ouroboros ouroboros 992 2005-04-17 12:36 Makefile.winnt
-rwxrwxr-x 1 ouroboros ouroboros 185 2005-02-12 09:34 README
drwxrwxr-x 2 ouroboros root 4096 2005-11-01 21:05 .tmp_versions
The official qemu-0.7.2 directory is as follows :
ouroboros@w0-rm-h0-l3:~/qemu-0.7.2$ ls -al ../qemu-0.7.2
total 2628
drwxrwxr-x 26 ouroboros root 4096 2005-11-02 11:43 .
drwxr-xr-x 52 ouroboros ouroboros 4096 2005-11-01 21:05 ..
-rwxrwxr-x 1 ouroboros ouroboros 61233 2005-09-04 13:11 aes.c
-rwxrwxr-x 1 ouroboros ouroboros 717 2005-09-04 13:11 aes.h
-rwxrwxr-x 1 ouroboros ouroboros 82481 2005-09-04 13:11 alpha-dis.c
-rwxrwxr-x 1 ouroboros ouroboros 4098 2005-09-04 13:11 alpha.ld
-rwxrwxr-x 1 ouroboros ouroboros 14095 2005-09-04 13:11 a.out.h
-rwxrwxr-x 1 ouroboros ouroboros 56493 2005-09-04 13:11 arm-dis.c
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 armeb-user
-rwxrwxr-x 1 ouroboros ouroboros 4107 2005-09-04 13:11 arm.ld
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 arm-user
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 audio
-rwxrwxr-x 1 ouroboros ouroboros 6328 2005-09-04 13:11 block-bochs.c
-rwxrwxr-x 1 ouroboros ouroboros 16254 2005-09-04 13:11 block.c
-rwxrwxr-x 1 ouroboros ouroboros 4953 2005-09-04 13:11 block-cloop.c
-rwxrwxr-x 1 ouroboros ouroboros 8028 2005-09-04 13:11 block-cow.c
-rwxrwxr-x 1 ouroboros ouroboros 8293 2005-09-04 13:11 block-dmg.c
-rwxrwxr-x 1 ouroboros ouroboros 3105 2005-09-04 13:11 block_int.h
-rwxrwxr-x 1 ouroboros ouroboros 22466 2005-09-04 13:11 block-qcow.c
-rwxrwxr-x 1 ouroboros ouroboros 14234 2005-09-04 13:11 block-vmdk.c
-rwxrwxr-x 1 ouroboros ouroboros 6641 2005-09-04 13:11 block-vpc.c
-rwxrwxr-x 1 ouroboros ouroboros 54492 2005-09-04 13:11 block-vvfat.c
-rwxrwxr-x 1 ouroboros ouroboros 4454 2005-09-04 13:11 bswap.h
-rwxrwxr-x 1 ouroboros ouroboros 12044 2005-09-04 13:11 Changelog
-rwxrwxr-x 1 ouroboros ouroboros 17443 2005-09-04 13:11 cocoa.m
-rwxrwxr-x 1 ouroboros root 284 2005-11-02 11:43 config-host.h
-rwxrwxr-x 1 ouroboros root 539 2005-11-02 11:43 config-host.mak
-rwxrwxr-x 1 ouroboros ouroboros 20487 2005-11-01 22:19 configure
-rwxrwxr-x 1 ouroboros ouroboros 19553 2005-09-04 13:11 console.c
-rwxrwxr-x 1 ouroboros ouroboros 17976 2005-09-04 13:11 COPYING
-rwxrwxr-x 1 ouroboros ouroboros 26428 2005-09-04 13:11 COPYING.LIB
-rwxrwxr-x 1 ouroboros ouroboros 18961 2005-09-04 13:11 cpu-all.h
-rwxrwxr-x 1 ouroboros ouroboros 2964 2005-09-04 13:11 cpu-defs.h
-rwxrwxr-x 1 ouroboros ouroboros 42833 2005-09-04 13:11 cpu-exec.c
-rwxrwxr-x 1 ouroboros ouroboros 264 2005-09-04 13:11 .cvsignore
-rwxrwxr-x 1 ouroboros ouroboros 9888 2005-09-04 13:11 disas.c
-rwxrwxr-x 1 ouroboros ouroboros 673 2005-09-04 13:11 disas.h
-rwxrwxr-x 1 ouroboros ouroboros 17154 2005-09-04 13:11 dis-asm.h
-rwxr-xr-x 1 ouroboros ouroboros 39043 2005-11-02 11:43 dyngen
-rwxrwxr-x 1 ouroboros ouroboros 81199 2005-09-04 13:11 dyngen.c
-rwxrwxr-x 1 ouroboros ouroboros 6558 2005-09-04 13:11 dyngen-exec.h
-rwxrwxr-x 1 ouroboros ouroboros 12377 2005-09-04 13:11 dyngen.h
-rwxrwxr-x 1 ouroboros ouroboros 162 2005-09-04 13:11 dyngen-op.h
-rwxrwxr-x 1 ouroboros ouroboros 42647 2005-09-04 13:11 elf.h
-rwxrwxr-x 1 ouroboros ouroboros 17893 2005-09-04 13:11 exec-all.h
-rwxrwxr-x 1 ouroboros ouroboros 72984 2005-09-04 13:11 exec.c
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 fpu
-rwxrwxr-x 1 ouroboros ouroboros 20370 2005-09-04 13:11 gdbstub.c
-rwxrwxr-x 1 ouroboros ouroboros 206 2005-09-04 13:11 gdbstub.h
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 hw
-rwxrwxr-x 1 ouroboros ouroboros 99388 2005-09-04 13:11 i386-dis.c
-rwxrwxr-x 1 ouroboros ouroboros 4547 2005-09-04 13:11 i386.ld
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 i386-softmmu
drwxrwxr-x 3 ouroboros root 4096 2005-11-01 22:20 i386-user
-rwxrwxr-x 1 ouroboros ouroboros 4455 2005-09-04 13:11 i386-vl.ld
-rwxrwxr-x 1 ouroboros ouroboros 8582 2005-09-04 13:11 ia64.ld
-rwxrwxr-x 1 ouroboros ouroboros 884 2005-09-04 13:11 ia64-syscall.S
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 keymaps
-rwxrwxr-x 1 ouroboros ouroboros 4285 2005-09-04 13:11 keymaps.c
drwxrwxr-x 3 ouroboros root 4096 2005-11-02 11:45 kqemu
-rwxrwxr-x 1 ouroboros ouroboros 21228 2005-09-04 13:11 kqemu.c
-rwxrwxr-x 1 ouroboros ouroboros 346 2005-09-04 13:11 LICENSE
-rwxrwxr-x 1 ouroboros ouroboros 2180 2005-09-04 13:11 linux-2.6.9-qemu-fast.patch
drwxrwxr-x 7 ouroboros root 4096 2005-09-04 13:11 linux-user
-rwxrwxr-x 1 ouroboros ouroboros 6090 2005-09-04 13:11 m68k.ld
-rwxrwxr-x 1 ouroboros ouroboros 3768 2005-09-04 13:11 Makefile
-rwxrwxr-x 1 ouroboros ouroboros 10087 2005-09-04 13:11 Makefile.target
-rwxrwxr-x 1 ouroboros ouroboros 161384 2005-09-04 13:11 mips-dis.c
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 mips-softmmu
-rwxrwxr-x 1 ouroboros ouroboros 55126 2005-09-04 13:11 monitor.c
-rwxrwxr-x 1 ouroboros ouroboros 15040 2005-09-04 13:11 osdep.c
-rwxrwxr-x 1 ouroboros ouroboros 1438 2005-09-04 13:11 osdep.h
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 pc-bios
-rwxrwxr-x 1 ouroboros ouroboros 132561 2005-09-04 13:11 ppc-dis.c
-rwxrwxr-x 1 ouroboros ouroboros 4559 2005-09-04 13:11 ppc.ld
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 ppc-softmmu
drwxrwxr-x 3 ouroboros root 4096 2005-11-01 22:20 ppc-user
-rwxrwxr-x 1 ouroboros ouroboros 15282 2005-09-04 13:11 qemu.1
-rwxrwxr-x 1 ouroboros ouroboros 1936 2005-09-04 13:11 qemu-binfmt-conf.sh
-rwxrwxr-x 1 ouroboros ouroboros 50911 2005-09-04 13:11 qemu-doc.html
-rwxrwxr-x 1 ouroboros ouroboros 37538 2005-09-04 13:11 qemu-doc.texi
-rwxr-xr-x 1 ouroboros ouroboros 218109 2005-11-02 11:43 qemu-img
-rwxrwxr-x 1 ouroboros ouroboros 8918 2005-09-04 13:11 qemu-img.1
-rwxrwxr-x 1 ouroboros ouroboros 17849 2005-09-04 13:11 qemu-img.c
-rwxrwxr-x 1 ouroboros ouroboros 4029 2005-09-04 13:11 qemu-img.texi
-rwxrwxr-x 1 ouroboros ouroboros 23957 2005-09-04 13:11 qemu-tech.html
-rwxrwxr-x 1 ouroboros ouroboros 18466 2005-09-04 13:11 qemu-tech.texi
-rwxrwxr-x 1 ouroboros ouroboros 11158 2005-09-04 13:11 readline.c
-rwxrwxr-x 1 ouroboros ouroboros 58 2005-09-04 13:11 README
-rwxrwxr-x 1 ouroboros ouroboros 525 2005-09-04 13:11 README.distrib
-rwxrwxr-x 1 ouroboros ouroboros 7195 2005-09-04 13:11 s390.ld
-rwxrwxr-x 1 ouroboros root 1094 2005-11-01 21:05 scr.sh
-rwxrwxr-x 1 ouroboros ouroboros 15862 2005-09-04 13:11 sdl.c
-rwxrwxr-x 1 ouroboros ouroboros 8772 2005-09-04 13:11 sdl_keysym.h
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 slirp
-rwxrwxr-x 1 ouroboros ouroboros 10165 2005-09-04 13:11 softmmu_header.h
-rwxrwxr-x 1 ouroboros ouroboros 10397 2005-09-04 13:11 softmmu_template.h
-rwxrwxr-x 1 ouroboros ouroboros 153195 2005-09-04 13:11 sparc-dis.c
-rwxrwxr-x 1 ouroboros ouroboros 4097 2005-09-04 13:11 sparc.ld
drwxrwxr-x 4 ouroboros root 4096 2005-11-01 22:20 sparc-softmmu
drwxrwxr-x 3 ouroboros root 4096 2005-11-01 22:20 sparc-user
drwxrwxr-x 3 ouroboros root 4096 2005-09-04 13:11 target-arm
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 target-i386
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 target-mips
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 target-ppc
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 target-sparc
drwxrwxr-x 2 ouroboros root 4096 2005-09-04 13:11 tests
-rwxrwxr-x 1 ouroboros ouroboros 11058 2005-09-04 13:11 texi2pod.pl
-rwxrwxr-x 1 ouroboros ouroboros 7061 2005-09-04 13:11 thunk.c
-rwxrwxr-x 1 ouroboros ouroboros 4108 2005-09-04 13:11 thunk.h
-rwxrwxr-x 1 ouroboros ouroboros 2230 2005-09-04 13:11 TODO
-rwxrwxr-x 1 ouroboros ouroboros 8367 2005-09-04 13:11 translate-all.c
-rwxrwxr-x 1 ouroboros ouroboros 1068 2005-09-04 13:11 translate-op.c
-rwxrwxr-x 1 ouroboros ouroboros 5 2005-09-04 13:11 VERSION
-rwxrwxr-x 1 ouroboros ouroboros 95581 2005-09-04 13:11 vgafont.h
-rwxrwxr-x 1 ouroboros ouroboros 102674 2005-09-04 13:11 vl.c
-rwxrwxr-x 1 ouroboros ouroboros 28184 2005-09-04 13:11 vl.h
-rwxrwxr-x 1 ouroboros ouroboros 6610 2005-09-04 13:11 x86_64.ld
drwxrwxr-x 4 ouroboros root 4096 2005-11-02 11:45 x86_64-softmmu
I'm at my wits end, I did so much already on this. Qemu works with WinXPcorpSP2 without a working kqemu, but it's miserably slow and I'd really like to get kqemu happy with it before going further on tweaking this emulation.
I'm in great hopes someone will help or inform me with this odd one.
Thanks much in advance!
geearf
November 2nd, 2005, 10:01 PM
Last time I tried on an amd64 box it didn't work that well, but I cannot help you though :(
kakashi
November 2nd, 2005, 10:53 PM
Has anyone tried this with XP, its the only windows disk I have handy at the moment. The QEMU site says its experimental, but been tested on version 0.5.5. No word yet on 0.70 it seems. I've seen Qemu running XP on some fedora forums, but I was wondering if anyone has gotten XP running on Ubuntu?
i have winxp working.
i even once managed to start it in safe mode.
it is **** slow. i think your probably better of borrowing a win 95 or 98 cd from a freind who haas it.
athough i have not yet installed win95 in qemu yet but since a only heard of qemu yesterday and al;ready have a working installation of winxp with kqemu i think i am doing quite well. :razz:
don't you . **becomes embaressed at self parise
LinuxWiz83
November 3rd, 2005, 06:45 AM
whats the -k en for from mu -boot c -fda /dev/fda -cdrom /dev/cdrom -hda /path/to/your/hd.img -user-net -pci -m 256 -k en because i get this error message (Could not read keymap file: '/usr/share/qemu/keymaps/en') when i keep the -k en on it?
LinuxWiz83
November 3rd, 2005, 07:22 AM
i have winxp working.
i even once managed to start it in safe mode.
it is **** slow. i think your probably better of borrowing a win 95 or 98 cd from a freind who haas it.
athough i have not yet installed win95 in qemu yet but since a only heard of qemu yesterday and al;ready have a working installation of winxp with kqemu i think i am doing quite well. :razz:
don't you . **becomes embaressed at self parise
Increase the memory size and it won't really be that bad but as of for win98 well that won't work for a lot of people because a lot of people use winxp software and even all the new media on web sites and such won't play on win98 because it uses old codecs.
kakashi
November 3rd, 2005, 07:39 AM
Increase the memory size and it won't really be that bad but as of for win98 well that won't work for a lot of people because a lot of people use winxp software and even all the new media on web sites and such won't play on win98 because it uses old codecs.
well i'm trying win 2000 now.
let you know how fast that is.
so far not too bad.
will most software work for win200.
as for codec i use mplayer in linux so no worries there.
kakashi
November 3rd, 2005, 07:59 AM
i have now installed win 2000 and its much faster than winxp but still sluggish.
i have only given it 100 mb ram so i guess that what i'll get but still i think
win98 will be almost perfect.
Lunde
November 3rd, 2005, 08:21 AM
100mb is a problem even for 98 if you start a coupple of programs. Why did you set the memory to 100?
Lunde
November 3rd, 2005, 08:35 AM
Warning: could not find /home/ouroboros/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd
This file does not exist, may be a typo in the script.
/home/ouroboros/qemu-0.7.2/kqemu/.kqemu.mod.o.cmd
kakashi
November 3rd, 2005, 10:20 AM
100mb is a problem even for 98 if you start a coupple of programs. Why did you set the memory to 100?
i only have 256 mb ram and 1 gb swap
how much should i mem should ???
Lunde
November 3rd, 2005, 10:30 AM
i only have 256 mb ram and 1 gb swap
how much should i mem should ???
Try to start it with 192 and check the sytem monitor in Ubuntu how your system is reacting.
kakashi
November 3rd, 2005, 11:06 AM
Try to start it with 192 and check the sytem monitor in Ubuntu how your system is reacting.
can i make a seperate swap area ony for this
LinuxWiz83
November 3rd, 2005, 01:28 PM
Well yea that's the problem Win2kPro/WinXP-Pro needs atleast 512 MB to run smoothly but with this emulator i would give it 1 GB of ram if you have it. As for win98 not running smoothly on 100 mb well no because beck in the days all i had was 32 mb and 64 mb and had no problems. Oh another way to speed up Win4Lin Pro is to increase the page file plus give Win4Lin Pro atleast 512MB of your memory.
trinaryouroboros
November 4th, 2005, 11:59 AM
Warning: could not find /home/ouroboros/qemu-0.7.2/kqemu/.kqemu-mod.o.cmd
This file does not exist, may be a typo in the script.
/home/ouroboros/qemu-0.7.2/kqemu/.kqemu.mod.o.cmd
Wow! Lunde, you are awesome.
Sometimes it's the stupidest thing, my bad...I've gotten alot further than I did before, but I've had to use a specific method now. I tried to do this in user mode, but I got an error that looks permission orientated:
Warning: could not open /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.c: No such file or directory
And sure enough the permissions were reset by something, so I tried a few ways with chmod 755 on all files in qemu and kqemu before and after .configure, but I always ended up with that same message...and it's there, the file does certainly exist and no typos this time.
By the way, I just cp'd that typo file with the correct format and it worked fine, passed that part.
Now I went to root, chmod 755'd qemu and kqemu dir's before and after ./configure ---blahblahx86 stuff, and during make install I get REAL further, but that message still appears midway during kqemu install this time :
make[1]: Leaving directory `/home/ouroboros/qemu-0.7.2/x86_64-softmmu'
make -C kqemu
make[1]: Entering directory `/home/ouroboros/qemu-0.7.2/kqemu'
make -C /usr/src/linux-headers-2.6.10-5-amd64-xeon M=`pwd` modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon' CC [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu-linux.o
cp /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod-x86_64.o /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not open /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.c: No such file or directory
CC /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
make[1]: Leaving directory `/home/ouroboros/qemu-0.7.2/kqemu'
mkdir -p "/usr/local/bin"
install -m 755 -s qemu-img "/usr/local/bin"
mkdir -p "/usr/local/share/qemu"
install -m 644 pc-bios/bios.bin pc-bios/vgabios.bin \
pc-bios/vgabios-cirrus.bin \
pc-bios/ppc_rom.bin pc-bios/video.x \
pc-bios/proll.elf \
pc-bios/linux_boot.bin "/usr/local/share/qemu"
mkdir -p "/usr/local/share/doc/qemu"
install -m 644 qemu-doc.html qemu-tech.html "/usr/local/share/doc/qemu"mkdir -p "/usr/local/share/man/man1"
install qemu.1 qemu-img.1 "/usr/local/share/man/man1"
mkdir -p "/usr/local/share/qemu/keymaps"
install -m 644 keymaps/da keymaps/en-gb keymaps/et keymaps/fr keymaps/fr-ch keymaps/is keymaps/lt keymaps/modifiers keymaps/no keymaps/pt-br keymaps/sv keymaps/ar keymaps/de keymaps/en-us keymaps/fi keymaps/fr-be keymaps/hr keymaps/it keymaps/lv keymaps/nl keymaps/pl keymaps/ru keymaps/th keymaps/common keymaps/de-ch keymaps/es keymaps/fo keymaps/fr-ca keymaps/hu keymaps/ja keymaps/mk keymaps/nl-be keymaps/pt keymaps/sl keymaps/tr "/usr/local/share/qemu/keymaps"
for d in x86_64-softmmu; do \
make -C $d install || exit 1 ; \
done
make[1]: Entering directory `/home/ouroboros/qemu-0.7.2/x86_64-softmmu'
install -m 755 -s qemu-system-x86_64 "/usr/local/bin"
make[1]: Leaving directory `/home/ouroboros/qemu-0.7.2/x86_64-softmmu'
cd kqemu ; ./install.sh
There's got to be something simple now at this juncture...I'm in high hopes!
Any further assistance is greatly appreciated in advance!
Thanks,
Lunde
November 4th, 2005, 01:02 PM
I can see that some of the files under your kqemu dir are in the root group, but this file is not. Try to chgrp and then do the chmod again on this specific file
-rw-r--r-- 1 ouroboros ouroboros 1582 2005-11-02 11:45 kqemu.mod.c
Strange if this helps, but stranger things has happend :-)
Wow! Lunde, you are awesome.
Sometimes it's the stupidest thing, my bad...I've gotten alot further than I did before, but I've had to use a specific method now. I tried to do this in user mode, but I got an error that looks permission orientated:
Warning: could not open /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.c: No such file or directory
And sure enough the permissions were reset by something, so I tried a few ways with chmod 755 on all files in qemu and kqemu before and after .configure, but I always ended up with that same message...and it's there, the file does certainly exist and no typos this time.
By the way, I just cp'd that typo file with the correct format and it worked fine, passed that part.
Now I went to root, chmod 755'd qemu and kqemu dir's before and after ./configure ---blahblahx86 stuff, and during make install I get REAL further, but that message still appears midway during kqemu install this time :
There's got to be something simple now at this juncture...I'm in high hopes!
Any further assistance is greatly appreciated in advance!
Thanks,
kakashi
November 5th, 2005, 12:13 AM
does anyone know how i can configure smb shares for win 98.
i managed to get smb for win 2000 but can't fint how to configure it for win 98
trinaryouroboros
November 5th, 2005, 01:26 AM
I can see that some of the files under your kqemu dir are in the root group, but this file is not. Try to chgrp and then do the chmod again on this specific file
-rw-r--r-- 1 ouroboros ouroboros 1582 2005-11-02 11:45 kqemu.mod.c
Strange if this helps, but stranger things has happend :-)
Ughck...it's a hanging deathtrap it is...my head is pounding, I'm going to sleep finally. I tried everything but reformatting and starting the whole silly OS from scratch.
started a brand new source directory, root only.
new commands used this round :
./configure --target-list=x86_64-softmmu --enable-adlib --cc=gcc-3.4 --host-cc=gcc-3.4
Now even with this beefcake, I still get the same weird "not found" message as mentioned previous.
Upon make clean from ./kqemu dir, I notice that the file in question gets rm'd ... soooo yeah. The thing gets rm'd, and make doesn't find the file...then somehow magically creates it after the fact it couldn't find the silly .c output module. Bah!
On a whim, I did touch kqemu/kqemu.mod.c, plus chgrp/chmod'd it up, and now instead of kqemu.mod.c being "not found" - make does :
make[1]: Leaving directory `/home/ouroboros/source/qemu-0.7.2/x86_64-softmmu'
make -C kqemu
make[1]: Entering directory `/home/ouroboros/source/qemu-0.7.2/kqemu'
make -C /lib/modules/2.6.10-5-amd64-xeon/build M=`pwd` modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
CC [M] /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu-linux.o
cp /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu-mod-x86_64.o /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu-mod.o
LD [M] /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not open /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.mod.c: Success
CC /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
make[1]: Leaving directory `/home/ouroboros/source/qemu-0.7.2/kqemu'
"Warning: could not open /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.mod.c: Success"
What in the nuggets of the backside is it saying "Success" for?!
Foiled again!
I tried at some points to force the linux-headers-2.6.10-5-amd64-xeon stuff to stick to gcc-3.4 only...boy was that useless.
I also tried from scratch using chgrp root, and chown 755, chown 777 on the file, etc...g'nite.
:evil:
Lunde
November 5th, 2005, 05:23 AM
does anyone know how i can configure smb shares for win 98.
i managed to get smb for win 2000 but can't fint how to configure it for win 98
If this is for Qemu, Share the disk from linux, no point sharing anything from the guest OS
Lunde
November 5th, 2005, 05:26 AM
Ughck...it's a hanging deathtrap it is...my head is pounding, I'm going to sleep finally. I tried everything but reformatting and starting the whole silly OS from scratch.
started a brand new source directory, root only.
new commands used this round :
./configure --target-list=x86_64-softmmu --enable-adlib --cc=gcc-3.4 --host-cc=gcc-3.4
Now even with this beefcake, I still get the same weird "not found" message as mentioned previous.
Upon make clean from ./kqemu dir, I notice that the file in question gets rm'd ... soooo yeah. The thing gets rm'd, and make doesn't find the file...then somehow magically creates it after the fact it couldn't find the silly .c output module. Bah!
On a whim, I did touch kqemu/kqemu.mod.c, plus chgrp/chmod'd it up, and now instead of kqemu.mod.c being "not found" - make does :
"Warning: could not open /home/ouroboros/source/qemu-0.7.2/kqemu/kqemu.mod.c: Success"
What in the nuggets of the backside is it saying "Success" for?!
Foiled again!
I tried at some points to force the linux-headers-2.6.10-5-amd64-xeon stuff to stick to gcc-3.4 only...boy was that useless.
I also tried from scratch using chgrp root, and chown 755, chown 777 on the file, etc...g'nite.
:evil:
What user are you running make from? Have you tried as root? Can it be that make clean mess up the files and that you need to unpack the files again
I have to add that I never had any such problems, but I never tried the 0.7.2.
LinuxWiz83
November 5th, 2005, 06:36 AM
does anyone know how i can configure smb shares for win 98.
i managed to get smb for win 2000 but can't fint how to configure it for win 98
Well it is the same setup but the only difference i think is win98 does not support spaces in the shares names.
trinaryouroboros
November 5th, 2005, 05:39 PM
What user are you running make from? Have you tried as root? Can it be that make clean mess up the files and that you need to unpack the files again
I have to add that I never had any such problems, but I never tried the 0.7.2.
I was running as root only. I've tried unpacking / starting from scratch several times with little success.
I think I'm dropping the project with 0.7.2 and trying just 0.7.0 instead, we'll see what happens - but, I can't seem to find the tars out there. Could someone possibly give me a link or send them via email to theallisone @ gmail.com ?
Much appreciated! :rolleyes:
kakashi
November 5th, 2005, 10:07 PM
I was running as root only. I've tried unpacking / starting from scratch several times with little success.
I think I'm dropping the project with 0.7.2 and trying just 0.7.0 instead, we'll see what happens - but, I can't seem to find the tars out there. Could someone possibly give me a link or send them via email to theallisone @ gmail.com ?
Much appreciated! :rolleyes:
if you have some extra space why not install ubuntu in that space and try there.
maybe something you have alreay done is effecting your install
trinaryouroboros
November 5th, 2005, 10:44 PM
if you have some extra space why not install ubuntu in that space and try there.
maybe something you have alreay done is effecting your install
Probably...my usual linux space tends to look very similar to my actual space - cluttered, unorganized, and deadly if left alone for too long...
:-k
Lunde
November 7th, 2005, 08:50 AM
I was running as root only. I've tried unpacking / starting from scratch several times with little success.
I think I'm dropping the project with 0.7.2 and trying just 0.7.0 instead, we'll see what happens - but, I can't seem to find the tars out there. Could someone possibly give me a link or send them via email to theallisone @ gmail.com ?
Much appreciated! :rolleyes:
I may have them on one of my disks at home, I'll check this a bit later and upload them to my server if I can find them
trinaryouroboros
November 7th, 2005, 09:22 AM
I may have them on one of my disks at home, I'll check this a bit later and upload them to my server if I can find them
That would be awesome. Else, I can give you an ftp account if you so desire.
kakashi
November 7th, 2005, 09:39 AM
Hallo, guys!
1st of all thank you for this great guide.
2nd of all - HEEEEEEEEELP!
I failed to install win2k for a couple of days already and it drives me crazy. I really need windows on my comp to run OriginLab, Shadow ray tracing and sometimes for MS Word and IE.
The problem is that win2k installation goes smoothely up to a point where it says:
"The disk space on C: is insufficient for the components that are currently selected. You will need to change your component selections".
From this point I don't know what to do. I created an image of 3.5G, should be enough. For installation I use:
qemu -hda win2k.img -cdrom /dev/cdrom -boot d -m 256
After reboot I type 'c' instead of 'd'.
Does anybody know what can be done?
Thank you in advance.
-win2k-hack
this is the parameter to avoid the disk full error.
i don;t know if this has been answered since i can't be bottheredto check
just thougth i'd let you know.
Lunde
November 8th, 2005, 10:53 AM
That would be awesome. Else, I can give you an ftp account if you so desire.
http://fabrice.bellard.free.fr/qemu/qemu-0.7.0.tar.gz
..It was just to change the version number at the end
Lunde
November 8th, 2005, 10:59 AM
-win2k-hack
this is the parameter to avoid the disk full error.
i don;t know if this has been answered since i can't be bottheredto check
just thougth i'd let you know.
above quote is is so true.. and in addition to the ansvere from kakashi, I worked around a similar issue by formatting the drive first and have the win installer change it to ntfs.
trinaryouroboros
November 8th, 2005, 06:53 PM
http://fabrice.bellard.free.fr/qemu/qemu-0.7.0.tar.gz
..It was just to change the version number at the end
This is true, but to get kqemu 0.7.0 - this same procedure does not work unfortunately. I was able to get qemu-0.7.0 just fine though, thank you!
Maybe I'll just play around with Win95 under regular qemu in the meantime.
Lunde
November 8th, 2005, 07:37 PM
This is true, but to get kqemu 0.7.0 - this same procedure does not work unfortunately. I was able to get qemu-0.7.0 just fine though, thank you!
Maybe I'll just play around with Win95 under regular qemu in the meantime.
I'm not sure the version number you are trying to download exists. The one I used in this howto is here:
http://fabrice.bellard.free.fr/qemu/kqemu-0.6.2-1.tar.gz
There's also a more resent version, might work but I never tried it:
http://fabrice.bellard.free.fr/qemu/kqemu-0.7.1-1.tar.gz
Changelog:
http://fabrice.bellard.free.fr/qemu/kqemu-changelog.html
trinaryouroboros
November 13th, 2005, 11:27 PM
I'm not sure the version number you are trying to download exists. The one I used in this howto is here:
http://fabrice.bellard.free.fr/qemu/kqemu-0.6.2-1.tar.gz
There's also a more resent version, might work but I never tried it:
http://fabrice.bellard.free.fr/qemu/kqemu-0.7.1-1.tar.gz
Changelog:
http://fabrice.bellard.free.fr/qemu/kqemu-changelog.html
Well, in update, I tried kqemu-0.7.1 with qemu-0.7.2, and when it came down to this bother:
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not open /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.c: No such file or directory
CC /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
root@w0-rm-h0-l3:/home/ouroboros/qemu-0.7.2/kqemu #
I decided to copy the kqemu.mod.c that WAS there, as kqemu.mod.c.2 - then make clean erased the kqemu.mod.c as usual...then I renamed kqemu.mod.c.2 to kqemu.mod.c - and make did the following :
root@w0-rm-h0-l3:/home/ouroboros/qemu-0.7.2/kqemu # make
make -C /usr/src/linux-headers-2.6.10-5-amd64-xeon M=`pwd` modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
CC [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu-linux.o
cp /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod-x86_64.o /home/ouroboros/qemu-0.7.2/kqemu/kqemu-mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
CC /home/ouroboros/qemu-0.7.2/kqemu/kqemu.mod.o
LD [M] /home/ouroboros/qemu-0.7.2/kqemu/kqemu.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.10-5-amd64-xeon'
root@w0-rm-h0-l3:/home/ouroboros/qemu-0.7.2/kqemu #
But, of course, when doing:
root@w0-rm-h0-l3:/home/ouroboros/qemu-0.7.2/kqemu # modprobe kqemu
FATAL: Error inserting kqemu (/lib/modules/2.6.12-9-amd64-generic/misc/kqemu.ko): Invalid module format
Oh well, you win some you lose some...I'll keep investigating. If I find a palpable solution I will certainly post it here for all to see, we can't live in the 32-bit ages forever you know.
.tommie
November 14th, 2005, 04:58 AM
I've followed the howto, but ran in some trouble when compiling. This is my output when i do 'make':
Could someone point me out what's going wrong? I've tried and tried, but can't find a solution.
thomas@Chimay:~/Desktop/qemu-0.7.2$ make
gcc -Wall -O2 -g -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o dyngen dyngen.c
dyngen.c: In functie ‘load_object’:
dyngen.c:508: let op: pointer targets in assignment differ in signedness
dyngen.c:544: let op: pointer targets in assignment differ in signedness
gcc -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing -g -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o qemu-img qemu-img.c block.c block-cow.c block-qcow.c aes.c block-vmdk.c block-cloop.c block-dmg.c block-bochs.c block-vpc.c block-vvfat.c -lz
block-cloop.c: In functie ‘cloop_read_block’:
block-cloop.c:116: let op: pointer targets in assignment differ in signedness
block-cloop.c:118: let op: pointer targets in assignment differ in signedness
block-dmg.c: In functie ‘dmg_read_chunk’:
block-dmg.c:231: let op: pointer targets in assignment differ in signedness
block-dmg.c:233: let op: pointer targets in assignment differ in signedness
block-vpc.c: In functie ‘vpc_probe’:
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
block-vpc.c:84: let op: pointer targets in passing argument 1 of ‘strncmp’ differ in signedness
block-vvfat.c: In functie ‘create_long_filename’:
block-vvfat.c:325: let op: pointer targets in passing argument 1 of ‘short2long_name’ differ in signedness
block-vvfat.c: In functie ‘fat_get’:
block-vvfat.c:393: let op: pointer targets in initialization differ in signedness
block-vvfat.c: In functie ‘long2unix_name’:
block-vvfat.c:446: let op: pointer targets in passing argument 1 of ‘__builtin_strncpy’ differ in signedness
block-vvfat.c:446: let op: pointer targets in passing argument 2 of ‘__builtin_strncpy’ differ in signedness
block-vvfat.c:453: let op: pointer targets in passing argument 1 of ‘__builtin_strncpy’ differ in signedness
block-vvfat.c:453: let op: pointer targets in passing argument 2 of ‘__builtin_strncpy’ differ in signedness
block-vvfat.c: In functie ‘create_short_filename’:
block-vvfat.c:492: let op: pointer targets in passing argument 1 of ‘__builtin_strncpy’ differ in signedness
block-vvfat.c: In functie ‘init_directory’:
block-vvfat.c:719: let op: pointer targets in passing argument 1 of ‘snprintf’ differ in signedness
block-vvfat.c: In functie ‘vvfat_write’:
block-vvfat.c:1620: let op: pointer targets in passing argument 1 of ‘long2unix_name’ differ in signedness
for d in i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/home/thomas/Desktop/qemu-0.7.2/i386-user'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o elfload.o /home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c: In functie ‘load_elf_binary’:
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:948: let op: pointer targets in passing argument 1 of ‘strncmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘strlen’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘__builtin_strcmp’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/elfload.c:1086: let op: pointer targets in passing argument 1 of ‘strncmp’ differ in signedness
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o main.o /home/thomas/Desktop/qemu-0.7.2/linux-user/main.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o syscall.o /home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c: In functie ‘do_getsockopt’:
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:647: let op: pointer targets in passing argument 5 of ‘getsockopt’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:680: let op: pointer targets in passing argument 5 of ‘getsockopt’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c: In functie ‘do_syscall’:
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:1750: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:1784: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:1870: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:1871: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2301: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2302: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2303: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2304: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2305: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2306: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2307: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2308: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2309: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2310: let op: pointer targets in passing argument 1 of ‘tswap32s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2630: let op: pointer targets in passing argument 1 of ‘tswap64s’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2934: let op: pointer targets in passing argument 1 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2934: let op: pointer targets in passing argument 2 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2934: let op: pointer targets in passing argument 3 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2954: let op: pointer targets in passing argument 1 of ‘getresgid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2954: let op: pointer targets in passing argument 2 of ‘getresgid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:2954: let op: pointer targets in passing argument 3 of ‘getresgid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3061: let op: pointer targets in passing argument 1 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3061: let op: pointer targets in passing argument 2 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3061: let op: pointer targets in passing argument 3 of ‘getresuid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3079: let op: pointer targets in passing argument 1 of ‘getresgid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3079: let op: pointer targets in passing argument 2 of ‘getresgid’ differ in signedness
/home/thomas/Desktop/qemu-0.7.2/linux-user/syscall.c:3079: let op: pointer targets in passing argument 3 of ‘getresgid’ differ in signedness
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o mmap.o /home/thomas/Desktop/qemu-0.7.2/linux-user/mmap.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o signal.o /home/thomas/Desktop/qemu-0.7.2/linux-user/signal.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o path.o /home/thomas/Desktop/qemu-0.7.2/linux-user/path.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o osdep.o /home/thomas/Desktop/qemu-0.7.2/osdep.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o thunk.o /home/thomas/Desktop/qemu-0.7.2/thunk.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o vm86.o /home/thomas/Desktop/qemu-0.7.2/linux-user/vm86.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o exec.o /home/thomas/Desktop/qemu-0.7.2/exec.c
/home/thomas/Desktop/qemu-0.7.2/exec.c: In functie ‘cpu_set_log’:
/home/thomas/Desktop/qemu-0.7.2/exec.c:1257: let op: pointer targets in passing argument 2 of ‘setvbuf’ differ in signedness
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o kqemu.o /home/thomas/Desktop/qemu-0.7.2/kqemu.c
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -mpreferred-stack-boundary=2 -falign-functions=0 -fno-gcse -fno-reorder-blocks -fno-optimize-sibling-calls -I. -I/home/thomas/Desktop/qemu-0.7.2/target-i386 -I/home/thomas/Desktop/qemu-0.7.2 -I/home/thomas/Desktop/qemu-0.7.2/linux-user -I/home/thomas/Desktop/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/thomas/Desktop/qemu-0.7.2/fpu -I/home/thomas/Desktop/qemu-0.7.2/slirp -c -o op.o /home/thomas/Desktop/qemu-0.7.2/target-i386/op.c
/home/thomas/Desktop/qemu-0.7.2/target-i386/ops_sse.h: In functie ‘op_pshufw_mmx’:
/home/thomas/Desktop/qemu-0.7.2/target-i386/ops_sse.h:574: fout: unable to find a register to spill in class ‘GENERAL_REGS’
/home/thomas/Desktop/qemu-0.7.2/target-i386/ops_sse.h:574: fout: dit is de insn:
(insn:HI 18 17 19 0 /home/thomas/Desktop/qemu-0.7.2/target-i386/ops_sse.h:569 (set (strict_low_part (subreg:HI (reg/v:DI 63 [ r ]) 0))
(mem/s/j:HI (plus:SI (mult:SI (reg:SI 64)
(const_int 2 [0x2]))
(reg/v/f:SI 59 [ s ])) [0 <variable>._w S2 A16])) 52 {*movstricthi_1} (insn_list:REG_DEP_TRUE 16 (insn_list:REG_DEP_TRUE 12 (insn_list:REG_DEP_TRUE 53 (nil))))
(expr_list:REG_DEAD (reg:SI 64)
(nil)))
/home/thomas/Desktop/qemu-0.7.2/target-i386/ops_sse.h:574: in de war door de voorgaande fouten, ik stop ermee
make[1]: *** [op.o] Fout 1
make[1]: Leaving directory `/home/thomas/Desktop/qemu-0.7.2/i386-user'
make: *** [all] Fout 1
.tommie
November 14th, 2005, 08:07 AM
Found a solution in another post. Check it out @ http://www.ubuntuforums.org/showpost.php?p=432781&postcount=5
hyg53
November 15th, 2005, 07:42 AM
Hum something strange in this method...
What is the point emulate windows like this when you have an install CD. Just insert the CD and install it I it's what you want.
What you only get with this method are problems and slow speed...
Am I wrong?
trinaryouroboros
November 25th, 2005, 11:11 AM
Hum something strange in this method...
What is the point emulate windows like this when you have an install CD. Just insert the CD and install it I it's what you want.
What you only get with this method are problems and slow speed...
Am I wrong?
Well, in truth you could make Ubuntu Live, but some of us prefer to do the Permanent install. If everyone on the planet wanted to use Windows and Ubuntu simultaneously, and wanted Windows to own their system, there would only be Live CD's, and no permanent install cd's.
Also, for certain developers Linux is the way to be, and to emulate Windows is sometimes neccessary for software testing purposes...
:KS
Trojan1313
November 25th, 2005, 12:05 PM
I've been thinking a little. Would it be possible to use this to have webcam conversations with MSN? Or would I need a Linux-supported webcam for that?
I'm guessing the second, but it might atleast be worth a shot. :)
trinaryouroboros
November 25th, 2005, 01:13 PM
I've been thinking a little. Would it be possible to use this to have webcam conversations with MSN? Or would I need a Linux-supported webcam for that?
I'm guessing the second, but it might atleast be worth a shot. :)
Have a looksie:
http://amsn.sourceforge.net/
They're still working on better webcam support, but it's worth a shot!
:KS
Also check out this local How-to:
HOWTO: aMSN 0.95 beta without compiling (http://ubuntuforums.org/archive/index.php/t-87001.html)
And check this How-to out for general video capture in linux:
http://www.faqs.org/docs/Linux-mini/BTTV.html
trinaryouroboros
November 25th, 2005, 01:34 PM
empty
Trojan1313
November 25th, 2005, 04:10 PM
Have a looksie:
http://amsn.sourceforge.net/
They're still working on better webcam support, but it's worth a shot!
:KS
Also check out this local How-to:
HOWTO: aMSN 0.95 beta without compiling (http://ubuntuforums.org/archive/index.php/t-87001.html)
And check this How-to out for general video capture in linux:
http://www.faqs.org/docs/Linux-mini/BTTV.html
I've thought about that already, actully. :) Problem is, my cam is four versions to early for support in linux. :p (this is the first model, the fifth has support in Linux)
trinaryouroboros
November 26th, 2005, 10:01 AM
I've thought about that already, actully. :) Problem is, my cam is four versions to early for support in linux. :p (this is the first model, the fifth has support in Linux)
Foiled! :eek:
Trojan1313
November 26th, 2005, 10:04 AM
Foiled! :eek:
I'm sorry, what?
trinaryouroboros
November 26th, 2005, 11:16 AM
I'm sorry, what?
Foiled...as in, "My plans have been Foiled, again."
yeah... :???:
Trojan1313
November 26th, 2005, 02:29 PM
Foiled...as in, "My plans have been Foiled, again."
yeah... :???:
Ah, okay... I just didn't understand. :)
*rubs hands together and puts on his evil grin*
`GooZ´
December 8th, 2005, 09:39 AM
Thanks alot for this very clear howto! :-)
dgermann
December 15th, 2005, 10:20 PM
Hi--
I'm stumped. Can you help me?
I have done apt-get install qemu, created the virtual disk, etc.
Now I want to install Win95. The problem seems to be that I have a Win95 CD which is not bootable, and a bootable floppy.
I have tried these things and cannot get Win95 to install:
# qemu -boot a -fda /dev/fd0 -hda /home/doug/qemu/hd.img
# qemu -boot d -cdrom /dev/hda -hda /home/doug/qemu/hd.img
# qemu -boot a -fda /dev/fd0 d -cdrom /dev/cdrom0 -hda /home/doug/qemu/hd.img
...and half a dozen other things, including trying format c:/s from within the dos window that opens up and shows me all the files on the floppy.
I suspect it is something simple....
I have visited the various websites shown in the howto that starts this thread and there does not seem to be an answer there....
Thanks!
Lunde
December 16th, 2005, 06:22 AM
Try to download a boot disk image from www.bootdisk.com, extract the .img file from the .exe (self extracting zip file) with Archive Manager, then refer to this image in your Qemu boot path:
$ qemu -boot a -fda /path/to/your/bootdisk.img - hda /home/doug/qemu/hd.img
dgermann
December 16th, 2005, 07:24 PM
Lunde--
Thanks for the quick reply!
Try to download a boot disk image from www.bootdisk.com, extract the .img file from the .exe (self extracting zip file) with Archive Manager, then refer to this image in your Qemu boot path:
$ qemu -boot a -fda /path/to/your/bootdisk.img - hda /home/doug/qemu/hd.img
Archive manager would not open this file. So I executed it in Windows and created a boot disk. Then I did this:# qemu -boot a -fda /dev/fd0 -hda /home/doug/qemu/hd.img
It got as far as to create an R:\ mapping, which is farther than before, but it then when I try to switch to drive R:\ says "Not ready reading drive R:." Drives C: and D: are invalid drive specs. Yes, the Win95 CD is in the drive.
I tried to pkunzip the image file, got winb95b.IMA which I renamed to winb95b.img, and then used your code on it--it gets to "booting from floppy" and then hangs.
In case it helps, here is the directory of the floppy:
total 1.3M
drwxr-xr-x 2 root root 7.0K 1969-12-31 18:00 .
drwxr-xr-x 4 root root 4.0K 2005-10-05 20:33 ..
-rwxr-xr-x 1 root root 15K 1996-08-24 11:11 attrib.exe
-rwxr-xr-x 1 root root 45 1999-05-26 16:45 autoexec.bat
-rwxr-xr-x 1 root root 34K 1996-09-26 17:13 cd1.sys
-rwxr-xr-x 1 root root 17K 1996-11-21 01:54 cd2.sys
-rwxr-xr-x 1 root root 20K 1996-08-13 01:03 cd3.sys
-rwxr-xr-x 1 root root 41K 1998-05-11 20:01 cd4.sys
-rwxr-xr-x 1 root root 28K 1996-08-24 11:11 chkdsk.exe
-r-xr-xr-x 1 root root 92K 1996-08-24 11:11 command.com
-rwxr-xr-x 1 root root 377 1999-05-29 12:20 config.sys
-rwxr-xr-x 1 root root 21K 1996-08-24 11:11 debug.exe
-rwxr-xr-x 1 root root 19K 1996-08-24 11:11 deltree.exe
-r-xr-xr-x 1 root root 64K 1996-08-24 11:11 drvspace.bin
-rwxr-xr-x 1 root root 69K 1996-08-24 11:11 edit.com
-rwxr-xr-x 1 root root 46K 1996-08-24 11:11 extract.exe
-rwxr-xr-x 1 root root 62K 1996-08-24 11:11 fdisk.exe
-rwxr-xr-x 1 root root 6.6K 1996-08-24 11:11 find.exe
-rwxr-xr-x 1 root root 49K 1996-08-24 11:11 format.com
-rwxr-xr-x 1 root root 33K 1996-08-24 11:11 himem.sys
-r-xr-xr-x 1 root root 210K 1996-08-24 11:11 io.sys
-rwxr-xr-x 1 root root 9.2K 1996-08-24 11:11 label.exe
-rwxr-xr-x 1 root root 32K 1996-08-24 11:11 mem.exe
-rwxr-xr-x 1 root root 27K 1996-08-24 11:11 move.exe
-rwxr-xr-x 1 root root 25K 1996-08-24 11:11 mscdex.exe
-r-xr-xr-x 1 root root 6 1999-11-17 16:37 msdos.sys
-rwxr-xr-x 1 root root 104K 1996-08-24 11:11 regedit.exe
-rwxr-xr-x 1 root root 140K 1996-08-24 11:11 scandisk.exe
-rwxr-xr-x 1 root root 7.2K 1996-08-24 11:11 scandisk.ini
-rwxr-xr-x 1 root root 19K 1996-08-24 11:11 sys.com
-rwxr-xr-x 1 root root 75K 1996-08-24 11:11 uninstal.exe
-rwxr-xr-x 1 root root 41K 1996-08-24 11:11 xcopy32.exe
-rwxr-xr-x 1 root root 3.8K 1996-08-24 11:11 xcopy.exe
So what am I missing, O guru? <grin>
Thanks, Lunde!
Juzz
December 16th, 2005, 07:30 PM
Did anyone find a resolution to the dependancy hell in Breezy?
ERROR: QEMU requires SDL or Cocoa for graphical output
To build QEMU with graphical output configure with --disable-gfx-check
Note that this will disable all output from the virtual graphics card.
Then:
:~/src/qemu-0.7.2$ sudo apt-get install libsdl1.2-dev zlib1g-dev
Reading package lists... Done
Building dependency tree... Done
zlib1g-dev is already the newest version.
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.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libsdl1.2-dev: Depends: libglu1-mesa-dev but it is not going to be installed or
libglu-dev
E: Broken packages
If I then fire up synaptic and try to do some backtracing - it ends with a libgl package that is too new!
If I try to force the Hoary version then synaptic wants to uninstall Ubuntu Desktop and x-window-core :o
Has anyone released a package for Breezy with kqemu inside?
isitututu
December 22nd, 2005, 12:24 AM
I have gone through this whole thread and all posts on the qemu forum and cant' find what I have done wrong. I am running Ubuntu 5, and have installed qemu without the accelerator and win98. All works fine exect that I can't get the samba share to work. I have the following share defined in samba:
[carlos]
path = /home/carlos
read only = No
I can access the web server using the url http://10.0.2.2/ and can also ping 10.0.2.2 and am able to surf the net in win98. Unfortunately the samba share is not accessible.
I use the following command to start win98 with and without samba running:
sudo qemu -boot c -hda /home/carlos/Qemu/hd.img -pci -m 128 -user-net -smb carlos
have also tried with and without samba running:
sudo qemu -boot c -hda /home/carlos/Qemu/hd.img -pci -m 128 -user-net
In win98 I have tried \\10.0.2.2\carlos and \\10.0.2.4\carlos, neither of these work, I always get a cannot find file or item error.
Also I know that the samba share works because I have win2K running on an evaluation copy of vmware and am able to access the share through win2K.
Any help would be appreciated greatly. VMWare is a GREAT piece of software, but a little overkill for what I want, so I do not want to spend the money at this time. Win4lin 9x used to be really good but since they stopped creating win4lin kernels it is beyond my linux abilities to get it working. The pro version is also way to slow even with win2k and acceleration.
Straker
December 22nd, 2005, 06:21 PM
I am very interested in this concept as I have been using Win4Lin Home on Hoary but now want to upgrade to Breezy and would like to try this QEMU method. However, the one issue I have is can QEMU print from Windows thru to native Ubuntu printers?
I ask this question, because there is essentially no documentation (web or otherwise) regarding how to print from within QEMU to native devices, and I have had no luck printing from a Linux QEMU session to native Windows printers.
Thanks in advance for any response.
Juzz
December 22nd, 2005, 08:11 PM
For those contemplating trying to get qemu or kqemu up and running - I can really recommend you try the vmware player, see this thread for more info:
http://ubuntuforums.org/showthread.php?t=84275
The vmware player runs extremely good and the speed is blistering compared to qemu :cool:
trinaryouroboros
December 23rd, 2005, 03:25 PM
For those contemplating trying to get qemu or kqemu up and running - I can really recommend you try the vmware player, see this thread for more info:
http://ubuntuforums.org/showthread.php?t=84275
The vmware player runs extremely good and the speed is blistering compared to qemu :cool:
Ole!!!
isitututu
December 31st, 2005, 12:04 PM
I solved my problem. When the system is installed the windows image that is created in your home directory is owned by root. I changed ownership to my self. This seemed to have caused the problem. I had to change permissions on the directory so that others could write to the file. Now it all seems to work fine.
Just one comment. Even win98 is slow. I am considering using a litePC product, however the only emulator that I have no problems with so far is VMWare. Probably just worth spending the money. I would NOT recommend win4lin to anyone. I still have not been able to get either 9x or the pro version working properly. 9x is GREAT on a system that has the kernel. My spouse is running Linspire with 9x.
drfalkor
January 1st, 2006, 06:34 AM
I can't live without paint! ;-)
Don't worry, take 2 pills, and try out gimp .
valnar
January 1st, 2006, 09:18 AM
I would NOT recommend win4lin to anyone. I still have not been able to get either 9x or the pro version working properly.
Sadly, I agree. Has anyone made Win4lin 9x work on Breezy?
Robert
isitututu
January 1st, 2006, 01:38 PM
Don't worry, take 2 pills, and try out gimp .
I was a paint junkie too. Photoshop and the Gimp are waaay to complex for me. Try Kolorpaint. It is a KDE app but I am running it on Gnome just fine.
sup
January 7th, 2006, 11:00 AM
thanks for the guide.
I encountered a small problem with compilation. Upon
tom@tom:~/Desktop/qemu-0.8.0$ ./configure
I got following
big/little test failed
ERROR: "gcc" looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
I have got gcc 3.4 installed as well as 4.0, so it wasnt an issue of installing new packages, but I was kind of at a loss as to how to tell QEMU to use 3.4 version, because
tom@tom:~/Desktop/qemu-0.8.0$ ./configure --help
gave me exactly the same result as shown above. It took me some time to figure out only thing I needed was
tom@tom:~/Desktop/qemu-0.8.0$ ./configure --disable-gcc-check --help which started help and I found out that only this simple command is needed: tom@tom:~/Desktop/qemu-0.8.0$ ./configure --cc=gcc-3.4 Maybe the first post could be upgraded since this can be a little confusing(at least it was for me)?
Ramses
January 11th, 2006, 04:04 AM
I am very interested in this concept as I have been using Win4Lin Home on Hoary but now want to upgrade to Breezy and would like to try this QEMU method. However, the one issue I have is can QEMU print from Windows thru to native Ubuntu printers?
I ask this question, because there is essentially no documentation (web or otherwise) regarding how to print from within QEMU to native devices, and I have had no luck printing from a Linux QEMU session to native Windows printers.
Thanks in advance for any response.
I Don't know if it's any help but I managed to get my linux printer to work from qemu running winxp. I am running Qemu 0.72 + KQemu 0.72.
First you need working samba and cups. If you have Samba and cups working, printer will show up when you browse samba share from explorer (in my case \\10.0.2.2. Printer installation did not work stright from printer icon.
You need to go in Windows: start --> settings --> printers and faxes --> add printer --> next --> local printer --next --> create new port --> local port (you should put here the samba printer share (example \\10.0.2.2\lp))
It took some time when it was looking for printer. Then it asks you to install drivers for printer.
This is all written from memory so there may be some flaws.
kenquad
January 11th, 2006, 03:24 PM
Hi all:
I'm running Breezy but still decided to try out the qemu howto listed here, since I have 3 Windows programs I have to run for work. BTW - and this is probably "news" like the discovery of America in 1492 :cool: - Nando Florestan has written a shell script for installing qemu with kqemu support, available at the same location: http://oui.com.br/n/content.php?article.21. I was ready to bite the bullet and type in all the code in the howto, but this script totally bypassed it!
On to my main point. Win2000 is running slow. Atrociously slow. As in five seconds to open the right-click menu on the desktop. Will this much slowness be fixable by just tweaking the OS? And boot parameters I can change?
Also, I can't get on my LAN or net access, which is a must.
I'd appreciate any ideas.
Thanks.
oswald-p
January 12th, 2006, 01:21 PM
This is very interesting indeed...
But I am not a Samba specialist so could you explain how you configure it?
Actually, I can ping 10.0.2.2 but I cannot connect through explorer...
thanks.
O-p
galgoz
January 12th, 2006, 03:11 PM
when I run the command
qemu -boot c -cdrom /dev/cdrom -hda /path/to/your/hd.img -user-net -pci -m 256 -k en
I get the following error.
qemu: invalid option -- '-user-net'
sup
January 12th, 2006, 05:50 PM
galgoz:I got the same mistake, so I just did not use that option, I think that this howto works well enough (if you of course want to run windows) (scroll down to Sharing Files With XP and Networking) https://wiki.ubuntu.com/WindowsXPUnderQemuHowTo?highlight=%28qemu%29
oswald-p:oswald:I am not sure, have you got file ssharing in windows enabled (including workgroup), but howto mentioned above should work as well.
kenquad:what is you hardware configuration? Are you sure you are using kqemu?
sup
January 12th, 2006, 05:51 PM
galgoz:I got the same mistake, so I just did not use that option, I think that this howto works well enough (if you of course want to run windows) (scroll down to Sharing Files With XP and Networking) https://wiki.ubuntu.com/WindowsXPUnderQemuHowTo?highlight=%28qemu%29
oswald-p:oswald:I am not sure, have you got file ssharing in windows enabled (including workgroup), but howto mentioned above should work as well.
kenquad:what is you hardware configuration? Are you sure you are using kqemu? As to the LAN part, see the howto mentioned above as well, it worked for me.
sup
January 12th, 2006, 05:51 PM
oops
galgoz
January 12th, 2006, 06:56 PM
2. One option is to use the -m 512 or what ever you want to give the host as memory, Qemu will tell you that you have to raise the shm by:
$ sudo umount /dev/shm
$ sudo mount -t tmpfs -o size=528m none /dev/shm
If you want to do this permanent, set up the mount in /etc/fstab
What do you mean by the last part? Do you mean change the second line to read...
$ sudo mount -t tmpfs -o size=528m none /etc/fstab
Then do I need to change the command line or the lines for the bootmisc.sh as well?
DavidGX
January 15th, 2006, 02:55 PM
Hey guys. I want to use windows xp to stream music (via windows media connect) to an xbox 360 I have connect to the network. I installed windows xp into Qemu, network was running, wmc installed on it but the xbox 360 can't see it. This is my setup..
*internet*
|
|
Cable Modem
|
|
Router
/ \
/ \
/ \
PC Xbox 360
|
Linux
|
Windows xp
Is there any way to configure networking so that the windows xp installed into qemu will see the 360?
kakashi
January 15th, 2006, 04:18 PM
theres a tutorial around here concerning qemu and bridge networking. use that.
galgoz
January 16th, 2006, 06:36 PM
When I am running Windows and it crashes (imagine that) my mouse will not work in Ubuntu. I assume because I didn't get to hit alt-ctrl before it crashed to release the Grab. Is there a way to get my mouse back without rebooting?
oswald-p
January 17th, 2006, 10:00 AM
Thanks Sup, I installed qemu 7.2 + Kqemu 7.2 as described above... it seems to work well except for file sharing / printing...
My distro is Ubuntu 5.10
I can browse web, ping 10.0.2.2 but I can't share files (user-net option activated).
I shared a directory with samba and it seems to work as I can connect to it via external computer on our network. I used "-smb" option to run qemu that run win98SE where I gave the same user/password as my ubuntu box (juste to be sure....)
Does anybody have any idea?
thanks
O-p
galgoz
January 17th, 2006, 11:02 PM
Originally Posted by Lunde
2. One option is to use the -m 512 or what ever you want to give the host as memory, Qemu will tell you that you have to raise the shm by:
$ sudo umount /dev/shm
$ sudo mount -t tmpfs -o size=528m none /dev/shm
If you want to do this permanent, set up the mount in /etc/fstab
What do you mean by the last part? Do you mean change the second line to read...
$ sudo mount -t tmpfs -o size=528m none /etc/fstab
Then do I need to change the command line or the lines for the bootmisc.sh as well?
Still looking for an answer as to how to do this permanently. Anyone know?
galgoz
January 24th, 2006, 03:21 AM
after command checkinstall next error
dpkg-deb: subprocess paste killed by signal (Broken pipe)
I get this same error. Is there a solution to this as I would like to be able to install qemu if I want later
trinaryouroboros
January 26th, 2006, 10:36 AM
Sorry, I sort of gave up since I couldnt' get kqemu working properly.
I do recall the error once however, I think it had something to do with the version of the compiler. Go back in history and ensure you have the older version.
galgoz
January 26th, 2006, 12:02 PM
I actually won't be using Qemu anymore. I now have my Dreamweaver 8 and Flash 8 working in Cedega! Yea, Windowz is gone.
trinaryouroboros
January 27th, 2006, 01:31 PM
I actually won't be using Qemu anymore. I now have my Dreamweaver 8 and Flash 8 working in Cedega! Yea, Windowz is gone.
Get outta here, you got a working link to a guide or something on that?
galgoz
January 27th, 2006, 02:23 PM
I am actually now an Advocate on Cedaga for Dreamweaver 8 and will be writing something up for the site as long as they approve the method that is required. If you want to IM me I can give you the quick quick version.
yetanothersteve
January 29th, 2006, 01:44 PM
Ridiculously easy way to to set up Qemu and KQemu on Hoary.
http://oui.com.br/n/content.php?article.23
I made a change to the script because I wanted Qemu 0.8.0.
KQemu turns it from a dog into something reasonable on my Athlon 3000 with 1Gb RAM.
xurizaemon
February 27th, 2006, 05:41 AM
kQemu really does make a difference, yes.
Tonight i decided i was bored of having no gTalk client on my linux box, and needed to get my audio working in either of the qEmu windozes i had set up.
To get it going in the win98, tried adding the option "-soundhw sb16", which detected the card when ran the add new hardware wiz, but then bluescreened on boot. So restarted qemu with "-soundhw es1370" instead and that worked a treat (had to d/l drivers though as i didn't have the correct 98 cd handy, haven't seen it since doing the install, whoops!)
The XP (home) install just needed me to start it with "-soundhw es1370". I didn't try -audio-hw sb16 because 1370 worked better on win98. Once it booted it detected a new audio device and went straight to work.
Amazingly, in 98 the sound started straight away - as i installed the drivers i heard the speakers pop into life. and let me check ... Yep. I can get sound from Amarok in Linux, AND from Win98 (in qEmu) AND from XP all at once. (XP just went 'ding' in the background to tell me it's finished d/l gTalk).
Wow. I wouldn't expect this of Windows normally! Haha, running XP and 98 on an Athlon XP 2800. Typing this in FFOx on the 98 'machine'. Crazy stuff.
Thanks Ubuntu! Thanks qEmu! And ... heh ... thanks Microsoft too!
:mrgreen:
Now on to test how well it copes with gTalk yakker ... hehe
clackey
March 9th, 2006, 09:54 PM
I'm having problems installing Qemu with KQemu in Dapper...
Everything works fine up until I needed to install. First, I tried using
sudo checkinstall
which generated a package called qemu_0.8.0-1_i386.deb.
Then, I did
sudo dpkg -i qemu_0.8.0-1_i386.deb
...which gave me this:
~/qemu-0.8.0$ sudo dpkg -i qemu_0.8.0-1_i386.deb
(Reading database ... 160124 files and directories currently installed.)
Unpacking qemu (from qemu_0.8.0-1_i386.deb) ...
dpkg: error processing qemu_0.8.0-1_i386.deb (--install):
trying to overwrite `/lib/modules/2.6.15-17-386/modules.alias', which is also in package linux-image-2.6.15-17-386
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
qemu_0.8.0-1_i386.deb
So then I tried
sudo make install
...that seemed to work fine; no errors. On to the next step:
sudo modprobe kqemu
...oops:
~/qemu-0.8.0$ sudo modprobe kqemu
FATAL: Error inserting kqemu (/lib/modules/2.6.15-17-386/misc/kqemu.ko): Invalid module format
I couldn't figure out what was wrong, so I tried to go ahead with the rest of the HOWTO... it worked, except I noticed that Qemu was unable to run KQemu (said something about /dev/kqemu in the terminal while Qemu was running; I forget exactly what, though).
Although Qemu itself runs fine, I'm trying to run XP under it; and without KQemu, it's painfully slow. I'm willing to bet this has something to do with the fact that I'm using Dapper, or the kernel version i'm using (uname -r gives me 2.6.15-17-386), or both. Can anyone help?
Thanks,
Clackey
trinaryouroboros
March 10th, 2006, 10:13 AM
I'm having problems installing Qemu with KQemu in Dapper...
Everything works fine up until I needed to install. First, I tried using
sudo checkinstall
which generated a package called qemu_0.8.0-1_i386.deb.
Then, I did
sudo dpkg -i qemu_0.8.0-1_i386.deb
...which gave me this:
~/qemu-0.8.0$ sudo dpkg -i qemu_0.8.0-1_i386.deb
(Reading database ... 160124 files and directories currently installed.)
Unpacking qemu (from qemu_0.8.0-1_i386.deb) ...
dpkg: error processing qemu_0.8.0-1_i386.deb (--install):
trying to overwrite `/lib/modules/2.6.15-17-386/modules.alias', which is also in package linux-image-2.6.15-17-386
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
qemu_0.8.0-1_i386.deb
So then I tried
sudo make install
...that seemed to work fine; no errors. On to the next step:
sudo modprobe kqemu
...oops:
~/qemu-0.8.0$ sudo modprobe kqemu
FATAL: Error inserting kqemu (/lib/modules/2.6.15-17-386/misc/kqemu.ko): Invalid module format
I couldn't figure out what was wrong, so I tried to go ahead with the rest of the HOWTO... it worked, except I noticed that Qemu was unable to run KQemu (said something about /dev/kqemu in the terminal while Qemu was running; I forget exactly what, though).
Although Qemu itself runs fine, I'm trying to run XP under it; and without KQemu, it's painfully slow. I'm willing to bet this has something to do with the fact that I'm using Dapper, or the kernel version i'm using (uname -r gives me 2.6.15-17-386), or both. Can anyone help?
Thanks,
Clackey
Please rewind, I had the same exact problem w/ no workaround to date.
It's a very intriguing problem. Fair warning, however, don't lose too much hair like I did with this one.
I thought it might have something to do with my 64-bit processor, at least I'm glad to know it's not the family of the cpu that matters in regards to this trouble. If you do discover a fix, please let us know, I've been fighting with that kqemu for a long time now.
clackey
March 10th, 2006, 11:38 AM
Hmm... I read over the Nando Florestan article, and it said this:
So the last step is to load the kqemu kernel module:
modprobe kqemu
What if this command does not work, saying this?
FATAL: Error inserting kqemu (/lib/modules/2.6.10-2-386/misc/kqemu.ko): Invalid module format
This means you did something wrong when compiling. For instance, the headers used during compilation are for a different kernel than the one you are actually using. You can run a "make clean" to wipe the compiled files and restart from the "./configure" step, doing something different this time.
...Now, I know I used the right headers for my kernel, however, I did read on a thread somewhere someone mentioning that in order for it to work, you have to have compiled your kernel with the same gcc version as qemu (or it could have been some other program that had the same module error). I'll try to find that thread and post it here.
Also, check this out: http://www.mepis.org/node/9277
It's a post by someone using Mepis who had the same problem; with a reply by someone with an apparent workaround. I might try it out.
Clackey
clackey
March 11th, 2006, 12:09 AM
The solution in the Mepis post seems to work!
Found the solution.
Steps I Took That Worked
Make sure to have the following line in /etc/apt/sources.list:
deb http://apt.mepis.org/3.4/ etch main
Then, as root:
# apt-get update
# apt-get install linux-headers-2.6.15-1-586tsc
# ln -sf /usr/src/linux-headers-2.6.15-1-586tsc /usr/src/linux
# apt-get install gcc-3.3 g++-3.3 libsdl1.2debian libsdl1.2debian-all build-essential libsdl1.2-dev zlib1g-dev
# ln -sf /usr/bin/gcc-3.3 /usr/bin/gcc
# wget -nv http://fabrice.bellard.free.fr/qemu/qemu-0.8.0.tar.gz
# tar zxvf qemu-*.tar.gz
# cd qemu-*
# wget -nv http://fabrice.bellard.free.fr/qemu/kqemu-0.7.2.tar.gz
# tar zxvf kqemu-*.tar.gz
# export CPP=g++-3.3
# export CC=gcc-3.3
# sh ./configure --prefix=/usr --cc=gcc-3.3 --host-cc=gcc-3.3 --kernel-path=/usr/src/linux
# rm /usr/bin/gcc
# ln -sf /usr/bin/gcc-3.3 /usr/bin/gcc
# make
# rm /usr/bin/gcc
# ln -sf /usr/bin/gcc-4.0 /usr/bin/gcc
# cd kqemu
# make clean
# make
# cd ..
# make install
...I just changed the kernel version to my own, skipped this
# ln -sf /usr/src/linux-headers-2.6.15-1-586tsc /usr/src/linux
changed --kernel-path=/usr/src/linux to --kernel-path=/usr/src/linux-headers-2.6.15-17-386
and that was that!
The reason why it wasn't working was exactly like I had mentioned; kqemu was compiled along with qemu using gcc-3.3, while the kernel was compiled with gcc-4.0, causing a conflict... using this fix recompiles kqemu after qemu using gcc-4.0 so it can work with the kernel.
However, I still wasn't able to use checkinstall without a "modules.alias" error, so I just used make install; which worked just fine.
Hope this can fix it for you too trinaryouroboros!
Clackey
trinaryouroboros
March 11th, 2006, 05:22 PM
The solution in the Mepis post seems to work!
...I just changed the kernel version to my own, skipped this
# ln -sf /usr/src/linux-headers-2.6.15-1-586tsc /usr/src/linux
changed --kernel-path=/usr/src/linux to --kernel-path=/usr/src/linux-headers-2.6.15-17-386
and that was that!
The reason why it wasn't working was exactly like I had mentioned; kqemu was compiled along with qemu using gcc-3.3, while the kernel was compiled with gcc-4.0, causing a conflict... using this fix recompiles kqemu after qemu using gcc-4.0 so it can work with the kernel.
However, I still wasn't able to use checkinstall without a "modules.alias" error, so I just used make install; which worked just fine.
Hope this can fix it for you too trinaryouroboros!
Clackey
Jesus! I'm freaking excited! I can't believe it's true, finally there's a real solution out there that works?!
My weekend already rocks, holy freakin cow! :mrgreen:
I'm trying this as soon as I get home! I had almost lost all hope on this!
\\:D/ WOOHOOOO!
ruscook
March 16th, 2006, 07:54 AM
I've tried Nando's script and get the following output from my attempt on my Dapper install. Anyone know why make is failing with a segementation error ?
InsQEMU - version 0.1 (2005-12-15)
======= by Nando Florestan -- http://oui.com.br/n
This script downloads and installs QEMU 0.8.0,
with the KQEMU accellerator, in Ubuntu 5.10 Breezy Badger.
Based on:
http://www.hants.lug.org.uk/cgi-bin/wiki.pl?LinuxHints/QemuCompilation
If this script succeeds, you will see a message at the end saying:
"InsQEMU SUCCEEDED!"
...else you have some problem.
If you have any difficulties, you can edit the script yourself.
It is heavily commented so as to help.
Please send any bug corrections to nandoflorestan@gmail.com
First of all, we install the dependencies.
Reading package lists...
Building dependency tree...
gcc-3.4 is already the newest version.
g++-3.4 is already the newest version.
libsdl1.2debian is already the newest version.
libsdl1.2debian-all is already the newest version.
build-essential is already the newest version.
libsdl1.2-dev is already the newest version.
zlib1g-dev is already the newest version.
checkinstall is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Finding out whether your kernel is i386 or i686.
Downloading Linux headers for K7...
Reading package lists...
Building dependency tree...
linux-headers-k7 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Directory already exists: /root/qemu-src/qemu-0.8.0
I will use its files instead of downloading them from the internet.
BEGINNING CONFIGURE !
Install prefix /usr
BIOS directory /usr/share/qemu
binary directory /usr/bin
Manual directory /usr/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /root/qemu-src/qemu-0.8.0
C compiler gcc-3.4
Host C compiler gcc-3.4
make make
host CPU i386
host big endian no
target list i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu arm-softmmu
gprof enabled no
static build no
SDL support yes
SDL static link no
mingw32 support no
Adlib support no
CoreAudio support no
ALSA support no
DSound support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /usr/src/linux-headers-2.6.15-8-k7/
kbuild type 2.6
BUILDING QEMU !
for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu arm-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/i386-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/i386-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/arm-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/arm-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/armeb-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/armeb-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/sparc-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/sparc-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/ppc-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/ppc-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mips-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mips-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mipsel-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mipsel-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/i386-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/i386-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/ppc-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/ppc-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/sparc-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/sparc-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/x86_64-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/x86_64-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mips-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mips-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/arm-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/arm-softmmu'
make -C kqemu
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/kqemu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/kqemu'
Now let us remove Qemu if it is installed...
Reading package lists...
Building dependency tree...
Package qemu is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
checkinstall 1.5.3, Copyright 2001 Felipe Eduardo Sanchez Diaz Duran
This software is released under the GNU GPL.
Installing with "make install"...
========================= Installation results ===========================
ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored.
Copying documentation directory...
/var/tmp/dfJLDOUimkZmjrDqKiaM/installscript.sh: line 13: 21034 Segmentation fault mkdir -p "/usr/share/doc/qemu"
for d in i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu arm-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/i386-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/i386-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/arm-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/arm-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/armeb-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/armeb-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/sparc-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/sparc-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/ppc-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/ppc-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mips-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mips-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mipsel-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mipsel-user'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/i386-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/i386-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/ppc-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/ppc-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/sparc-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/sparc-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/x86_64-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/x86_64-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/mips-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/mips-softmmu'
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/arm-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/arm-softmmu'
make -C kqemu
make[1]: Entering directory `/root/qemu-src/qemu-0.8.0/kqemu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/qemu-src/qemu-0.8.0/kqemu'
mkdir -p "/usr/bin"
make: *** [install] Segmentation fault
**** Installation failed. Aborting package creation.
Restoring overwritten files from backup...OK
Cleaning up...OK
Bye.
mrjohnston
March 18th, 2006, 11:05 AM
I have fixed the insQEMU script so it works with dapper. I did make a couple other changes like making it recognize k7 headers and I fixed the gcc issues. Let me know if you have any problems.
Maybe later if I get adventurous I'll try to make a cvs script for qemu as well.
Just untar and run the script below as you normally would to get working qemu + kqemu patch.
trinaryouroboros
March 20th, 2006, 10:23 AM
I have fixed the insQEMU script so it works with dapper. I did make a couple other changes like making it recognize k7 headers and I fixed the gcc issues. Let me know if you have any problems.
Maybe later if I get adventurous I'll try to make a cvs script for qemu as well.
Just untar and run the script below as you normally would to get working qemu + kqemu patch.
Dude, you rock!
:mrgreen:
Schrollini
March 28th, 2006, 04:23 AM
Thanks to everyone who has posted in this thread, I can now run Win98 inside of qemu, which is very handy for tax software.
I did have trouble with Samba, so I thought I would share how I got it (mostly) working. I found this thread (http://qemu.dad-answers.com/viewtopic.php?p=1934&sid=4785304a4f9888063c11763f5acdecf2) (which was referenced, but not linked to, from here) rather enlightening.
There seem to be two methods to get Samba working. The first is to note that the client OS sees the host OS running at 10.0.2.2 . Thus, if you already have Samba up and running, you should be able to access it at this address. I was unable to get this working under Windows 98, but this was my first time playing with Samba, so I may have screwed something up server-side.
The other method is to pass the -smb <directory> switch to qemu. This starts up a "fake" Samba server that client can access at 10.0.2.4 . After much confusion and frustration, here's what I finally got to work:
Install the "samba" package.
Turn off the "Folder sharing service (samba)" via System | Adminstration | Services. This isn't necessary, but I didn't need it running.
Start qemu with sudo qemu <options> -smb /full/path/to/shared/directory I could only get it to work if I used an absolute path to the shared directory.
After Windows boots, add the line 10.0.2.4 smbserver to the file C:\Windows\Lmhosts (at least in Win98. The qemu man page suggests that this should work for Win95 and ME as well, while the NT / 2000 branch should do this in C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS) Important: Make sure you are acutally editting Lmhosts. My install had a file named Lmhosts.sam, which with hidden file extensions appeared in Explorer as Lmhosts. I spent the better part of an hour editting it, to no avail.
You might have to reboot Windows at this point. I don't remember if it was necessary for me or not.
Now, you should be able to access the shared directory by entering "\\smbserver\qemu" into the location bar of Explorer.
(Optional) Right click "Network Neighborhood" and select "Map Network Drive". Accept the drive letter and enter "\\smbserver\qemu" as the path. Click the box to "Reconnect at login". Now, the shared folder is accessible through a network drive, which will automatically be set up each time you log in. (Maybe. It is Windows.)
Outstanding issues:
I can't use IP addresses to access the share in Windows; \\10.0.2.4\qemu doesn't work. I suspect this is a limitation in Windows.
I have to start qemu with sudo, otherwise Windows complains that it can't connect to the host. This doesn't seem necessary, but I haven't found a way around it.
If you want to write to the shared directory from Windows, it must have 777 permissions. This has security implications, I'm sure.
Along the same lines, files created in Windows in the share are owned by "nobody/nogroup". There ought to be a way to have them owned by the user who launched qemu, but I have no clue where to start looking to fix this.
I hope this saves somebody a bit of work!
Schrollini
March 28th, 2006, 04:36 AM
An excellent how-to, many thanks. I have now got Qemu installed and into it I have installed Win XP Pro. It all seems to work fine, however the XP box's clock runs way too fast affecting things that are animated etc. Has anybody else experienced this?
When the machine is idling and drops to 600MHz a minute in the XP window takes about 19 seconds. With some load so the host runs at 1.5GHz, the minute takes about 10 seconds. Is there anyway of having it sync to the local clock properly?
I've seen the same problem on my setup (Athlon 3500, Ubuntu 5.10, Windows 98 ). When the computer is idling, the clock speed seems right, but it rushes by whenever the CPU throttles up. I haven't found a fix.
A note to other Win9x users: These systems don't idle properly, and continue to use CPU cycles all of the time, as noted in the qemu user documentation (http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC34). Installing the patch linked to on that page seems to work. (Now the clock only races occasionally....)
bernardfrancois
April 6th, 2006, 07:10 AM
Wow, this is a very long thread :) I didn't read everything yet (but I searched on the topics I'm asking questions about).
I tried to compile it with the accelerator, but it didn't work. The modprobe command returned something like 'kqemu not found'. I will try it again later, and I'll read the instructions that came with the source.
I managed to make it work now. Probably there's something unclear in the howto.
What I did to compile/install qemu 0.8.0 + qemu accelerator 1.3.0pre5:
#get the path of the linux headers, for example /usr/src/linux-headers-2.6.12-10-amd64-generic (explained in the howto)
#edit quemu-0.8.0/configure; kernel_path="" -> kernel_path="/usr/src/linux-headers-2.6.12-10-amd64-generic"
ber@linber:qemu-0.8.0$ ./configure --cc=gcc-3.4
ber@linber:qemu-0.8.0$ make
ber@linber:qemu-0.8.0$ sudo checkinstall
#don't do the following step if you have an i386 architecture
Enter a number to change any of them or press ENTER to continue: 7
Enter the architecture type:
>> amd64
#edit kqemu-1.3.0pre5/configure; kernel_path="" -> kernel_path="/usr/src/linux-headers-2.6.12-10-amd64-generic
ber@linber:kqemu-1.3.0pre5$ ./configure
ber@linber:kqemu-1.3.0pre5$ make
ber@linber:kqemu-1.3.0pre5$ sudo checkinstall
#failed
ber@linber:kqemu-1.3.0pre5$ sudo make install
Note that the installation of the accelerator using checkinstall failed.
I found out that only this simple command is needed: tom@tom:~/Desktop/qemu-0.8.0$ ./configure --cc=gcc-3.4 Maybe the first post could be upgraded since this can be a little confusing(at least it was for me)?
I also suggest the above to be added to the howto. This was also necessary here.
For now, I tried the version from synaptic (without native execution of machine instructions). It took a long time to install windows XP.
Now I can't log on. If I try to log on, I get a warning (translated): 'Due to a problem, Windows can't accurately translate the license for this computer. Error code: 0x800703e6'. After clicking the OK-button, I get logged of and I see the screen where you can pick a user again (I attached a screenshot).
It is a legal version of Windows XP Professional. The key was accepted during the installation. It's the first time I install it (my school has a contract with M$, every student in the course I'm taking can download a legal version of windows and get a legal key).
bernardfrancois
April 6th, 2006, 11:14 AM
About the command to boot an image as suggested in the howto:
The -k option is obsolete if you use Linux and if you want to use the keyboard layout you use in Linux.
the -user net option is obsolete (this is the default setting).
the -kernel-kqemu option should be added (this works if the accelerator works) to make it 2-5x faster.
I found this information in the manual pages of qemu version 0.8.0
A problem:
The QEMU Accelerator needs QEMU >= 0.8.1 .
However, the current version of QEMU is 0.8.0 (downloadable here (http://fabrice.bellard.free.fr/qemu/download.html)). I want to download version 0.8.1 or newer from CVS, but I can't find more information on the site on how to do this.
Can anyone help me with this?
Burgresso
April 6th, 2006, 04:49 PM
Stupid question, but...
Will/does work on 6.04 Breezy? Anyone tried it?
bernardfrancois
April 6th, 2006, 05:13 PM
Stupid question, but...
Will/does work on 6.04 Breezy? Anyone tried it?
6.04 = dapper
breezy = 5.10
There's a script (few posts higher) to install it on Ubuntu 6.04
It works on any linux kernel 2.4.18 or higher.
These are the requirements:
host gcc binutils glibc linux
-----------------------------------------------------
x86 3.2 2.13.2 2.1.3 2.4.18
Burgresso
April 6th, 2006, 07:17 PM
thanks!
bernardfrancois
April 10th, 2006, 09:10 AM
Now I can't log on. If I try to log on, I get a warning (translated): 'Due to a problem, Windows can't accurately translate the license for this computer. Error code: 0x800703e6'. After clicking the OK-button, I get logged of and I see the screen where you can pick a user again (I attached a screenshot).
I think I had this error because I changed the amount of ram (passed with the command line) after the installation of windows. I also changed the version of qemu I was using.
I think windows won't work anymore after the hardware settings changed... If this is true, this is something to be added to the howto as well.
jalyst
April 11th, 2006, 12:58 AM
I have fixed the insQEMU script so it works with dapper. I did make a couple other changes like making it recognize k7 headers and I fixed the gcc issues. Let me know if you have any problems.
Maybe later if I get adventurous I'll try to make a cvs script for qemu as well.
Just untar and run the script below as you normally would to get working qemu + kqemu patch.
Dont spose you could write it to grab the latest CVS, and while you're at it, compile for A64?
Wishful thinking??!!? :D
-jedL.
wwitthoff1
April 11th, 2006, 08:44 PM
question for you. I am trying to install win 98 and it uses a floppy to boot the cd. the floppy works fine but it says that it can't find the cd. Any ideas?
jalyst
April 11th, 2006, 08:52 PM
no idea sorry :-(
wwitthoff1
April 12th, 2006, 02:02 AM
i found how to boot but now cannot install as i get the error "cannot create temp directory" any ideas?
bernardfrancois
April 12th, 2006, 03:39 PM
maybe it thinks the disk is full...
you could try the following option:
-win2k-hack use it when installing Windows 2000 to avoid a disk full bug
wwitthoff1
April 12th, 2006, 04:13 PM
would that work for 98 as well? and where does it go in the command. I am using the command:
$qemu -boot d -cdrom /home/bassclarinetl2/New_Compilation.iso -hda /home/bassclarinetl2/Qemu/hd.img
wwitthoff1
April 12th, 2006, 05:07 PM
found answer to previous post. tried win2k hack but no dice. same error:
"Cannot create a temporary directory. This may be caused by too many files in the root directory"
any ideas?
BTW The actuall "Pressed" install CD is not bootable and came with a floppy disk. I created a bootable CD with the contents of the Pressed cd on it.
monicams
April 27th, 2006, 04:24 PM
.
Doctor DEA
September 15th, 2006, 01:48 PM
Im really new to Linux/Ubuntu... Every single tutorial I come across in reguards to Linux, you people start gloating in knowledge and failing to break things down, and explaining things to make them more simple for us noobs.... LINUX TUTORIALS ARE PUTTING A BAD TASTE IN MY MOUTH.... In other words, you need tutorials for your tutorials.
Tried to run a simple resize for formatting to dual boot the Hard Drive with Win. and Ubuntu.
Its always nice when your thinkpad freezes during this.
I really want to sway from the big overtaker, but finding it to be very difficult to learn your O.S. Ive had to restrain myself from launching my computer through the wall in the past with UBUNTU....
xurizaemon
September 15th, 2006, 06:23 PM
Don't put all nerds in the same basket, DEA. Some of us do know how to talk human tongues. And the ones who talk gibberish, they might sound holier-than-thou (as a rule of thumb, the more evangelical and holier they sound, the more recent the convert) but they probably really do want to help you*.
And, if you've ever had to debug an error message like this one from Outlook:
51 messages couldn’t be retrieved from the server. This usually happens when the connection to the server is lost due to network problems. Contact your administrator. Download error 0×80040403.
which translates from MCSESpeke into:
51 messages couldn't be downloaded because of a filesystem limitation in FAT32 (dude, you have a 2GB mailbox). But ... saying so would be bad marketing, so here's a red herring and a secret hexidecimal clue to spend your day chasing.
you'll know that while O.S.S geeks sometimes talk nonsense with the best of intentions, the commercial geeks sometimes get paid to write stuff that is flat-out deliberately confusing ;)
http://glo.dyndns.org/glob/2006/08/30/0x80040403-argh/
So ... you say your ThinkPad freezes during Ubuntu install?
http://www.ubuntuforums.org/archive/index.php/t-222077.html
This thread seems to suggest that the gPartEd Live CD does the trick (resizing an XP - NTFS partition) when the Ubuntu Live CD doesn't.
If this works for you, you might want to a bug to LaunchPad saying "Live CD doesn't correctly resize NTFS but gPartEd does" and give the full details of what did and didn't work, including your laptop specs - that might help someone fix the bug that's tripping you up.
Good luck!
* (OK, Some users from all camps are just idiots. No OS can protect against its users being fools. Can't be helped.)
Doctor DEA
September 15th, 2006, 08:09 PM
Ok,
I was pretty aggrevated when I wrote that. Thank you for responding in kindness. O:)
IBM ThinkPad R51 Model 1836: Intel(R)Pentium(R)M
Processor 1.70GHz 1.70Ghz,
768MB of RAM HardDrive 55.89GB
81% free space.
Goal Has Changed To: To get Suse 10.1 with gnome + XGL to run along with current OS. Or Ubuntu 5.10 with XGL.
Why: So I can utilize the tools I know to help further my knowledge into linux without the hassel of dual booting. And because it's cool as hell!
:rolleyes:
Current Status: VMware Workstation installed on current OS with 20GB allocated for SUSE.
Question: Am I going about this the correct way, or should it be vise versa with my base OS. In other words, should I make Linux my core OS to run VMware Workstation on? And then install "The Others" OS onto VMware? I would have no problem with doing this, but fear that alot of drivers for my thinkpad will be lost.
Thanks for your help, this is what ill be doing for the remainder of my night until the morning... :biggrin: ](*,)
jmfv
May 6th, 2007, 02:33 PM
A very good free and opensource alternative to using qemu is VirtualBox.
http://www.virtualbox.org/
I've tried it and now I'm running WinXP flawlessly inside linux, with native emulation speed.
Cheers.
roimam
June 18th, 2007, 05:55 PM
Ok this is my goal... I already have Ubuntu installed but I need to install windows XP too, then I don't want to delete my Ubuntu. I want to have both Ubuntu and windows. Can anybody tell me how to do it?
Thanks everybody.
s_p_a_r_k_y
June 24th, 2007, 11:52 PM
hey, the easiest way to achieve this is by formatting the computer to have an NTFS partition and install windows there first, then install ubuntu onto another empty partition and have its bootloader allow you to boot to both OSes
ares623
December 24th, 2007, 07:46 PM
hello.
i'm having trouble with this step
$ gedit configure
where is this configure file located? I tried editing the configure file in the extracted qemu directory, but it has no line that says "kernel_path=..."
vBulletin® v3.8.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.