 |
|
| Not working properly in Haiku |
|
|
By umccullough - Posted on February 12, 2011 - 21:11:53 (#23309)
Current version when comment was posted: 0.9.1 |
|
|
I had to symlink libssl.so and libcrypto.so to the versions that qemu is linked to since Haiku comes with a newer version.
After that, I was able to get qemu to run, but when i tried launching either ReactOS or Haiku within qemu, it eventually dies with a "killed (by death)" on the CLI. It seems like with Haiku the serial output shows it get killed right after it attempts to load the kernel.
|
|
| missing |
|
|
By kvdman - Posted on February 2, 2010 - 10:58:57 (#23259)
Current version when comment was posted: 0.9.1 |
|
|
|
| How to change the destination path to / |
|
|
By oco - Posted on November 16, 2009 - 19:45:31 (#23244)
Current version when comment was posted: 0.9.1 |
|
|
You can edit the destination path in the corresponding textbox and leave only "/".
|
|
| ho do you do this in haiku? |
|
|
By bbjimmy - Posted on November 14, 2009 - 01:03:45 (#23243)
Current version when comment was posted: 0.9.1 |
|
|
Expanding the image to / instead of /boot is another option. This option is available now !
The haiku Expander cannot do this. it will only expand to /boot.
|
|
| Installer script replacement |
|
|
By oco - Posted on November 11, 2009 - 18:14:35 (#23242)
Current version when comment was posted: 0.9.1 |
|
|
Expanding the image to / instead of /boot is another option. This option is available now !
|
|
| need an installer script. |
|
|
By bbjimmy - Posted on November 8, 2009 - 12:38:15 (#23241)
Current version when comment was posted: 0.9.1 |
|
|
Thanks for the new Haiku version. Expanding the image to /boot I ended up with a boot directory and all the files under it. I needed to manually move the files to their proper locations. An install script would be handy.
|
|
| Thank You Much! |
|
|
By StarWarsLegacy.net - Posted on March 20, 2008 - 00:02:44 (#22594)
Current version when comment was posted: 0.9.1 |
|
|
So now with this I should not need to install BeOS PE on a virtual 98 machine to make a custom BeOS CD, I'd think.
|
|
| Mounting Images |
|
|
By mmlr - Posted on March 19, 2008 - 13:58:55 (#22593)
Current version when comment was posted: 0.9.1 |
|
|
Or better yet, just use an automatic image mount tool like http://www.bebits.com/app/3576. Then you don't have to use mount at all.
|
|
| Re: Mount Point |
|
|
By mmlr - Posted on March 19, 2008 - 13:56:17 (#22592)
Current version when comment was posted: 0.9.1 |
|
|
In theory it does not matter, in practice you should just use a root directory. Meaning literally use "/theMount", "/qemuDisk", ...
|
|
| /The Mount |
|
|
By StarWarsLegacy.net - Posted on March 19, 2008 - 12:47:16 (#22591)
Current version when comment was posted: 0.9.1 |
|
|
So where would I make this directory, does it matter where it is?
|
|
| Re: Mounting QEMU image in BeOS |
|
|
By mmlr - Posted on March 19, 2008 - 12:19:12 (#22590)
Current version when comment was posted: 0.9.1 |
|
|
You do it the same way:
mkdir /theMount
mount -t <fstype> /path/to/image /theMount
Where you replace <fstype> with dos/ntfs/bfs/... as appropriate. This obviously only works if you have a file system add-on installed that can handle the file system inside the image. And this only works for direct images of file systems. If you have a full harddrive image including an MBR and partition table, then you cannot directly mount the individual partitions inside (even if there is only one).
|
|
| Mounting Qemu IMG in Be |
|
|
By StarWarsLegacy.net - Posted on March 19, 2008 - 05:41:13 (#22588)
Current version when comment was posted: 0.9.1 |
|
|
Is there a way to mount a Qemu img file as a virtual hard drive in BeOS as you can in Linux?
|
|
| Re: Updated Version |
|
|
By Cyan - Posted on February 22, 2008 - 18:33:22 (#22503)
Current version when comment was posted: 0.9.1 |
|
|
Thanks for the update! The new version seems to be working much better here -- the mouse is far easier to use, and I've not managed to reproduce the freezing keyboard issue since.
A couple of low-priority issues I've noticed, which have been around for a while:
- There doesn't seem to be any existence test for the hard disk image file? I noticed this when trying to launch QEMU, but forgot to mount the drive which holds the hard disk image, thus causing a crash.
- Pressing ctrl+alt to exit mouse grab sometimes results in ctrl/alt seeming "stuck" to the guest OS. I imagine this happens because the guest OS sees one key going down (e.g., alt), then the other key goes down (ctrl) which QEMU traps, and the guest OS never sees the "key off" events?
Both are easily avoided (the fix for the latter is just to tap ctrl then alt after exiting mouse grab), but I thought they might be worth mentioning.
Anyway, thanks again -- the mouse fix is already proving highly useful for designing PCBs (Haiku MIDI interface project).
|
|
| RE: adding files to a haiku image |
|
|
By mmlr - Posted on February 6, 2008 - 06:01:55 (#22470)
Current version when comment was posted: 0.9.1 |
|
|
Yes, mounting the image is certainly more comfortable if you want to put them there permanently. Using the cdrom trick is more useful if you want to get data into a running emulation. Also if you put all interesting stuff onto a secondary harddisk or cdrom image you can switch to a new haiku.image without having to mount and recopy everything.
|
|
| adding files to a haiku image |
|
|
By umccullough - Posted on February 5, 2008 - 13:36:28 (#22467)
Current version when comment was posted: 0.9.1 |
|
|
For a BeOS/Zeta host, wouldn't it be easier to just mount the haiku image using one of the following tools?
http://bebits.com/app/2932
http://bebits.com/app/3576
and then copy files to it?
|
|
| RE: if no network - is there a way to transfer files in? |
|
|
By mmlr - Posted on February 5, 2008 - 12:47:11 (#22466)
Current version when comment was posted: 0.9.1 |
|
|
Hi there
Well, with networking you could obviously simply ftp or wget it in, but without you have to go a bit further.
You can use CD images to transfer data into a running emulation. First, create an iso image with the data you want (using mkisofs from cdrtools for example "mkisofs -o image.iso </path/to/directory/containing/files>"). Then use the QEMU monitor to setup the emulated cdrom. To switch to the monitor hit Ctrl-Alt-2. Use the command "change cdrom /path/to/image.iso" to connect the virtual cdrom with the image. Then switch back to the emulation by Ctrl-Alt-1. Mounting directly from Tracker will probably not yet work, so you have to do that manually. Start a terminal and create a mount point by "mkdir /cd". Then use the command "mount -t iso9660 /dev/disk/atapi/1/master/raw /cd" which should mount the image to the "/cd" mount point you just created. It should also show up in Tracker now. Do whatever you need with the image and finally unmount it using the terminal and the command "unmount /cd". Now you can switch to the monitor again and change the image and again mount that within Haiku if you want to access multiple images. You will probably want to lookup the exact usage of mkisofs though to use rockridge or joliet to get around naming limitations.
Getting data out of the emulation is the more difficult thing when you can't use networking. You cannot use a cdrom image as it's read only. But you could attach a second harddisk image for data exchange if you need to.
Hope this helps
Michael
|
|
| if no network - is there a way to transfer files in? |
|
|
By hey68you - Posted on February 5, 2008 - 09:26:49 (#22464)
Current version when comment was posted: 0.9.1 |
|
|
Hi Michael,
Is there a way to get files on to my Haiku image (e.g. from my host BeOS)?
Thanks,
hey68you
|
|
| much faster mouse - really great thanks |
|
|
By hey68you - Posted on February 5, 2008 - 08:22:59 (#22463)
Current version when comment was posted: 0.9.1 |
|
|
This is a real improvement on my P4. I'm using the Haiku nightly image from today.
Thanks - your work is really appreciated.
|
|
| Silent Update of 0.9.1 Packages |
|
|
By mmlr - Posted on January 30, 2008 - 16:29:25 (#22446)
Current version when comment was posted: 0.9.1 |
|
|
So CD-Rom emulation was subtly broken in both 0.9.0 and 0.9.1 so that for example the Windows 98 installation could not be run from CD (read errors). Most other (newer) software wasn't affected by this. So if you have problems installing something from a CD, try re-downloading the 0.9.1 package. This is the only change in this update, so if you don't have any issues or don't use CD emulation there is no need to update.
Thanks to Bardulas for reporting and pointing out that 0.7.2 didn't have this issue. Ah and sorry if my upload corrupted someones download...
Regards
Michael
|
|
| CD not work |
|
|
By Bardulas - Posted on January 30, 2008 - 14:35:55 (#22445)
Current version when comment was posted: 0.9.1 |
|
|
I use Bone version. 9.1 verion fails to read from CD (image file) after boot install win95, 98. Version 7.2-bone works good.
Win2000 boot and start install but frozen on detecting devices.
|
|
| RE: CD not work |
|
|
By mmlr - Posted on January 30, 2008 - 12:30:33 (#22444)
Current version when comment was posted: 0.9.1 |
|
|
Could you be a bit more specific here please? What version do you use (BONE / net_server)? Did you use a real CD and tried using /dev/disk/ide/atapi... or did you use an image file? What exactly does not work, more like in crash, doesn't boot from CD, fails to read from CD once booted?
I have only quickly tested booting from a BeOS CD which worked as expected and did not try with a real CD drive (as I currently don't have one configured). So I really need some more pointers as to where the problem resides.
|
|
| CD not work |
|
|
By Bardulas - Posted on January 30, 2008 - 03:14:40 (#22443)
Current version when comment was posted: 0.9.1 |
|
|
CD not work (install win9x on qemu).
|
|
| Updated Version |
|
|
By mmlr - Posted on January 29, 2008 - 19:19:17 (#22442)
Current version when comment was posted: 0.9.1 |
|
|
Hi Cyan
I hope to have fixed all mouse related issues now. I cannot tell what happens with the keyboard, but BeOS does sometimes just have keys stuck. Easily visible when having the Keymap prefs open, especially when you press multiple keys at the same time.
Speed wise the new version should be pretty much the same as the previous one. I don't know what you have installed, but I must say that Windows 2000 is the absolutely best version to emulate using QEMU in my eyes. Windows 98 is not recommended as it does degrade in performance when used with KQEMU which kinda defeats it's purpose. With Windows 2000 you can even use -kernel-kqemu which makes this platform ideal. Also you don't really need too much of a CPU to have a usable system inside QEMU, but obviously it helps. Much RAM would be good, but with BeOS being stuck on that front... I'd recommend using Windows 2000 and disabling / removing anything unnecessary (i.e. disable all non-essential services and remove all components that are not used). With that you can get a pretty quick system.
About USB tablet emulation. It does still require the grab. It's no different than normal mouse to QEMU and the GUI. The only difference is in how data is delivered to the guest system. Since the issues you describe were caused by the GUI, it shouldn't have made any difference to use the tablet. Generally I'd recommend not using any devices that you do not require, so for optimal performance I'd not use USB and also disable networking (with -net none).
Hope the new version works better for everyone.
Regards
Michael
|
|
| Speed, mouse and keyboard |
|
|
By Cyan - Posted on January 9, 2008 - 16:43:41 (#22375)
Current version when comment was posted: 0.9.0 |
|
|
Not really, but it helps to have at least two processors, so one CPU can be dedicated to running the guest OS (as I'm sure you know, windows is very inefficient).
Either way, you definitely need something made in the last year or two if you want to run the worst versions of windows (e.g., 2K). On my old Athlon 1.3GHz system, 2K was unusable speed-wise.
The better versions, such as 98 and 95, actually ran at a usable speed, but suffered from some FPU issues which caused the GUIs of most applications to get automatically "redesigned" -- often to the point where the apps were no longer usable (this also happens when a human redesigns an application, but that's another matter...)
This doesn't seem to be a problem in 2K.
Regarding the previously mentioned problems I was having:
I have a workaround for the multithreading sound issue; I've written a "launcher" for QEMU that disables all other CPUs for 60 seconds, to allow the guest OS to finish booting.
I'm still having trouble with the mouse acceleration though, as described in my previous post.
Also, after extended hours of testing, I've also uncovered another problem -- heavy use of the keyboard (particularly the direction arrows in conjunction with other keys, e.g., for playing games) eventually kills all keyboard input to the guest OS, sometimes with some of the keys seeming "stuck" to the guest OS. There doesn't seem to be much of a pattern which triggers this, but it usually kicks in after about 20 minutes of gameplay.
This is restricted to the guest OS only, and the keyboard only -- ctrl+alt still exits grab, the keyboard still works in BeOS, and the mouse still works in the guest OS. Restarting QEMU fixes the problem. I'm using the default settings (apart from an emulated USB mouse) with a 2K guest OS. I haven't tried emulating a USB keyboard yet.
I'll do some more poking around to see if I can find out more...
|
|
| Wow |
|
|
By nutela - Posted on January 8, 2008 - 09:08:40 (#22371)
Current version when comment was posted: 0.9.0 |
|
|
So you can run Windows as a guest OS on a BeOS host, that's amazing. Do you really need a quad core system to run the guest OS with a 'workable' speed?
|
|
| Mouse and tablet |
|
|
By Cyan - Posted on November 9, 2007 - 06:10:48 (#22061)
Current version when comment was posted: 0.9.0 |
|
|
Hi, thanks for the response,
I tried using the USB tablet mode instead of PS/2 mouse as you suggested, but there seems to be an interesting issue.
- The guest OS (Windows 2000) sees the USB device as a "HID-compliant mouse" rather than "tablet", and also sees the PS/2 mouse. Disabling the PS/2 mouse makes no difference. I'm not sure if this is normal, because I've never tried using a real USB tablet on Windows.
No special drivers were installed -- Windows seemed to detect and install its own drivers for the device, without any error messages.
- If the mouse is moved, the cursor jumps to the top left of the screen and stays there. When the mouse is being moved down or right, the mouse position is equal to the mouse delta -- e.g., if the mouse is being moved right at 5 pixels per tick, the cursor position will be 5,0, jumping back to 0,0 when it stops moving. Moving up or left has no visible effect (it's capped to 0,0).
Interestingly, the rounding issue still seems to be present -- the mouse needs to be moved quite quickly before it will change from 0,0 to 1,1.
- QEMU still acts in the same way as when a mouse is being used -- clicking the window "grabs" the mouse as before. That surprised me, because I would've expected mouse grab to be unnecessary with absolute coordinates.
This, along with the other issues, seems to suggest that tablet-mode isn't engaging fully -- part of QEMU seems to think that a standard mouse is being used (and sending mouse delta values to the guest OS), while Windows is using the reported values as if a tablet were being used (as absolute coordinates).
Are there any other steps that need to be carried out, such as installing particular guest OS drivers, disabling the PS/2 mouse in QEMU somehow, etc.?
I've tried replacing -usbdevice tablet with -usbdevice mouse and that seems to restore normal operation, albeit with the same rounding error. In other words, it behaves almost the same as a PS/2 mouse, although without scroll-wheel support, and the guest OS seems more stable (less prone to experiencing mouse failure during heavy use).
I'm still investigating the mouse issue further; if I find out anything new, I'll post an update here.
Thanks again!
|
|
| RE: Some issues |
|
|
By mmlr - Posted on November 7, 2007 - 04:28:45 (#22057)
Current version when comment was posted: 0.9.0 |
|
|
Hi there
1) The sound issue that you mention is interesting. I cannot check currently, but it might very well be a race condition. I will look at the code when I get home and see if there is anything obvious.
2) The mouse problem is a known issue. You could try a different input device in QEMU by specifying "-usb -usbdevice tablet". It does use absolute coordinates instead of relative ones and could just solve this kind of problem.
3) It does indeed require a network connection when network emulation is enabled. I have not tracked this down fully but it might be QEMU trying to lookup the hostname by DNS as you say. It does not deadlock however, it just takes a while until the timeout happens. If you don't need networking you should disable network emulation by "-net none". This should "fix" the startup delay. It certainly does not require any outside services to run ;-).
Regards
Michael
|
|
| Some issues |
|
|
By Cyan - Posted on November 6, 2007 - 18:50:30 (#22055)
Current version when comment was posted: 0.9.0 |
|
|
Hi,
Firstly, thanks for porting this much-needed app to BeOS! Especially now with kqemu, it's fast enough to handle Flash playback among other things.
I've noticed a few weird issues though. I'm using the BONE version on an R5+BONE+beta media kit system. All of these issues appear with Windows 2000 as the guest OS; I haven't tested much with other guest OSs yet. The only command-line options used are the path to a hard disk image, -kernel-kqemu (tested both with and without), and -soundhw.
1) If sound is enabled (sb16 / es1370 / pcspk; makes no difference), "BSoundPlayer: no audio mixer" is printed to the terminal when the guest OS boots, and the media kit freezes up. Therefore, no sound can be heard. (restarting the media kit restores sound to other applications, but not QEMU)
It makes no difference whether kqemu is enabled.
This seems to be an SMP race condition (this is a quad-core system). When I disable all but one CPU in Pulse, the message does not appear, and the guest OS has flawless sound. Once the guest OS has booted up, the other CPUs can be re-enabled in Pulse with no problem -- the race condition only occurs during the initialization process.
Normally I'd blame the media kit for causing this, but I can't reproduce this problem with any other audio application in BeOS, even those that use BSoundPlayer objects -- it's unique to QEMU.
In case it's relevant, the BeOS soundcard driver buffer size is 64 frames (period = 1.45ms @ 44100Hz).
2) There seems to be some kind of rounding error with the mouse acceleration -- it may be rounding to minus infinity rather than zero. Moving the mouse up or left is easy, but moving it right or down requires quite a bit more speed before the pointer starts to move. This problem only seems to affect the pointer when it's being moved slowly.
This seems to occur with both Windows and also in pure DOS with the CuteMouse driver in exactly the same way, leading me to believe a rounding error is happening inside QEMU, rather than an FPU emulation error.
I haven't found a work-around for this problem. Thankfully it isn't major, but it does make the guest OS more difficult to use. Are there any guest OS drivers available to retrieve absolute mouse coordinates from the host OS? (this would fix the issue, and make it easier to use too)
3) QEMU seems to require an active connection to the Internet in order to run? When the Internet connection is down, running qemu seems to cause a deadlock (I haven't tested for long to see if it times out, but it lasts at least 30 seconds) -- the BApplication starts up, but no window is created. Restoring the Internet connection fixes the problem. It doesn't make any difference what command-line options are specified or what guest OS is used (even pure DOS).
Does it rely on outside services of some kind? (from a privacy standpoint, it would be very wise to disclose this!)
Could it be related to BONE+DNS in some way, trying to look up the host OS's hostname?
None of these issues are show-stoppers, but it would definitely make things even smoother if they could be resolved somehow.
Thanks!
|
|
| Re: qemu-img doesn't run |
|
|
By tonestone57 - Posted on July 6, 2007 - 11:34:26 (#21803)
Current version when comment was posted: 0.9.0 |
|
|
Try Libpak
http://bebits.com/app/3322
Check their homepage for newer version.
Missing symbol means qemu was compiled with newer version library/libraries.
Knowing which symbol is missing would tell us which library ( or libraries ) you need to update ( download source and compile ).
Libpak installs somewhat newer versions of many main libraries. It'll probably fix your problem.
|
|
| qemu-img doesn't run |
|
|
By bbjimmy - Posted on July 5, 2007 - 22:44:47 (#21801)
Current version when comment was posted: 0.9.0 |
|
|
Under BeOS Max 4b1 I get "Symbol not found" running qemu-img.
|
|
| where utf-8???? |
|
|
By michael_s - Posted on July 5, 2007 - 16:37:18 (#21800)
Current version when comment was posted: 0.9.0 |
|
|
http://qube.ru/forums/item/common/message/33562404/
|
|
| Russian: |
|
|
By michael_s - Posted on July 5, 2007 - 16:34:47 (#21799)
Current version when comment was posted: 0.9.0 |
|
|
Итак, производительность в числах:
Имеем Athloh64 3500+ (2200MHz), ось Dano, берём BYTEmark и запускаем его в нативном режиме. В итоге получаем:
MEMORY INDEX: 11.013
INTEGER INDEX: 9.725
FLOATING-POINT INDEX: 14.171
Далее грузим эту же установку Dano, но уже в QEMU и получаем:
MEMORY INDEX: 9.875
INTEGER INDEX: 8.704
FLOATING-POINT INDEX: 12.714
Путём несложных подсчётов выясняем, что производительность падает всего на ~11,5%, что очень даже неплохо. :)
|
|
| Re: minimum requirements |
|
|
By mmlr - Posted on July 2, 2007 - 18:42:51 (#21785)
Current version when comment was posted: 0.9.0 |
|
|
Hi there
I think that your crash could come from the P3 generation processor. I have just tested with my R5 system again and booting Haiku with and without kqemu worked fine from both a partition and an image. This is a P4 system though and I cannot really test a P3 as I don't have a corresponding R5 system installed on one of these anymore. If you could give a bit more details about the crash that would be helpful. Is it rebooting? KDL with something like invalid opcodes or is QEMU just crashing?
Regards
Michael
|
|
| re: crashing: forgot to say running Haiku raw images |
|
|
By hey68you - Posted on July 2, 2007 - 08:20:31 (#21784)
Current version when comment was posted: 0.9.0 |
|
|
not running win xp - just trying to run Haiku raw images.
Regards
|
|
| minimum system requirements on the host BeOS machine? |
|
|
By hey68you - Posted on July 2, 2007 - 08:13:06 (#21783)
Current version when comment was posted: 0.9.0 |
|
|
The net_server version is crashing for me unless I disable kqemu acceleration.
Anyone else having problems?
ok, I'm only running my BeOS on a P3 800 mhz 128mb RAM :)
Thanks,
hey68you
|
|
| thank you ... |
|
|
By rayman - Posted on July 2, 2007 - 02:41:21 (#21780)
Current version when comment was posted: 0.9.0 |
|
|
I did not expect any less ;) and in more one super profit in speed! excellent !
thank you more.
|
|
| Talk about speed increase |
|
|
By zenja - Posted on June 30, 2007 - 23:58:43 (#21778)
Current version when comment was posted: 0.9.0 |
|
|
I've just tried Haiku with the old version of QEMU and with this latest version, and GLTeapot went from 11 fps to 110 fps. That is a tenfold speed increase. Emulated haiku is just as usable under the BeOS family running QEMU as it is running VMWare on other operating systems.
Its great to see the Fabrice open source the kqemu module. He is an amazing engineer. Thanks a lot Michael for porting this to the BeOS family. Drinks on me.
|
|
| Thank you! |
|
|
By IgRussell - Posted on June 30, 2007 - 20:09:21 (#21777)
Current version when comment was posted: 0.9.0 |
|
|
|
| problem in Zeta 1.21 |
|
|
By IgRussell - Posted on April 5, 2007 - 08:05:53 (#21524)
Current version when comment was posted: 0.7.2 |
|
|
Hi,
I used Qemu before, I am now trying to install Win98 in a 1G partition on Zeta 1.21. The thing is that everything loads perfectly, it tells me if I want to install the system, but when I select yes, the MS appears OK finishing in "cannot find win98 installing files" and returns me into an A: symbol (its a laptop, only CD DVD combo). The Win98 is original, I can mount it on Desktop, and everything is in place. QemuVM can load everything too, finishing in the same result. Somebody have seen this before?
|
|
| Re: DVD-Drive on Zeta 1.2 |
|
|
By mmlr - Posted on August 30, 2006 - 15:51:50 (#20537)
Current version when comment was posted: 0.7.2 |
|
|
I don't really know the new structure, but it has probably just "moved" from "/dev/disk/ide/atapi/*" to something under "/dev/disk/scsi/*". Where exactly I can't tell, you'll have to try it out.
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
 |
| |
Recent Downloads - # 114
Total Downloads - # 979
Total Views - # 232
User Ratings - # 1
|
|
|
|
 |
| |
Computer Emulators
Emulators
|
|
|
|
 |
|
1. BePodder - 9.80
2. QEMU - 9.68
3. ScummVM - 9.57
4. Jukebox - 9.44
5. Haiku AGP busm... - 9.35
6. cpu_fix - 9.31
7. vim6 - 9.31
8. VNCServer - 9.30
9. Beezer - 9.26
10. HandBrake - 9.25
|
|
|
|
 |
|
1. Ati Radeon G... - 32,876
2. BeOS 5 Perso... - 32,449
3. Realtek RTL8... - 20,353
4. Ensoniq Audi... - 17,692
5. USB Joystick... - 16,553
6. BePDF - 15,349
7. ATI Rage 128... - 13,355
8. S3 Trio 64 v... - 10,305
9. VLC Media Pla... - 9,559
10. DOSBox - 9,466
|
|
|
|
 |
| You are not logged in.
Login
|
|
|
|
 |
|
