#25 closed bug (fixed)
qemu 0.6.1/0.7.0 + 2005.05.26 haiku.image
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
vesa dies ant app_server too: qemu line: qemu -hda /path/to/haiku.image -boot c -serial stdio > haiku.log
Change History (9)
comment:1 by , 19 years ago
Owner: | changed from | to
---|
comment:2 by , 19 years ago
comment:3 by , 19 years ago
Ok seems like qemu does support up to 24 bit color depth. But m$ vpc2004 supports 32 bit. Quote from help: "Virtual PC 2004 supports 1, 2, 4, 8, 16, and 32-bit color depths. " And results are the same: http://mif.vu.lt/~dejo0032/bla/haiku.txt
comment:4 by , 19 years ago
Component: | Kernel → Servers |
---|
comment:5 by , 19 years ago
This is a known bug, or, rather, an unimplemented feature. 32-bit video modes are the only ones supported ATM, but IIRC the only changes needed are to the Painter backend to support other modes.
comment:6 by , 19 years ago
Status: | new → assigned |
---|
comment:7 by , 19 years ago
Oh silly me :) It works in vpc2004 and in vmware5 when i choose 32bit color depth in boot menu. vmware: http://uosis.mif.vu.lt/~dejo0032/bla/vmhaiku.png
p.s. should mouse work ? i can see it trying to detect usb mouse but those virtuals emulate ps2.
comment:8 by , 19 years ago
Resolution: | → fixed |
---|
comment:9 by , 19 years ago
Status: | assigned → closed |
---|
As you can easily see at this line: vm_page_fault: killing team 0x16, ip 0x26894b ("app_server_seg0ro" +0x6894b)
The app_server is crashing. AFAICT that happens when you don't boot in a 32 bit mode. IOW the app_server seems to be the cause. Everything works fine when you select a 32 bit video mode (but that one might not be available in qemu).