Coherent on QEMU 0.9.1 works
txomsy
not install
or run in Qemu, and launched it with the install disks and an HD
image. It did
work flawlessly at least until the initial installation steps.
This morning, back to work, when I tried to continue installation it
failed to even
boot and I remembered it wasn't supposed to. A quick glance at the
laptop
showed I had release 0.9.1 of QEMU (vs. 0.9.0 on the workstation) and
a
new try confirmed it does work.
So, for all of you willing to resuscitate your old Coherent
experiences, just be
aware that QEMU up to 0.9.0 does not work, but it does on 0.9.1.
At least it is going through the fourth installation disk now, and it
recognized
all the virtual hardware correctly, partitioned the disk and booted
from hard
disk to complete installation.
Enjoy.
--
Jose R. Valverde
EMBnet/CNB
Andrzej Popielewicz
>
> aware that QEMU up to 0.9.0 does not work, but it does on 0.9.1.
>
> At least it is going through the fourth installation disk now, and it
> recognized
> all the virtual hardware correctly, partitioned the disk and booted
> from hard
> disk to complete installation.
> > Enjoy.
> EMBnet/CNB
Hi Jose,
I have just got the same message from You via TUHS.
OK, I can confirm Your result. I have used laptop AMILO Pro, 1400 MHZ
Celeron.I did not install yet completely , but I am now at creation of
Coherent filesystem and installing first floppy.I am using Ubuntu 7 Linux.
At the moment I do not know how it will find second floppy image, well
my laptop has no floppy.But so far so good.
I am sure it will open some interesting possibilities.
Andrzej
Andrzej Popielewicz
> txomsy pisze:
>>>
>
> At the moment I do not know how it will find second floppy image, well
> my laptop has no floppy.But so far so good.
>
> I am sure it will open some interesting possibilities.
>
OK, problem solved. After installing image of first floppy, one has to
restart qemu and set the image of the second floppy as a "floppy" etc.
So You do not need real floppy drive to install Coherent.Quite amazing.
Andrzej
txomsy
It's simple:
[ctrl][Alt][2] (stop the simulation and go to command mode)
change floppy0 name-of-file
[ctrl][Alt][1] (back to the simulation with floppy changed)
and so on...
BTW, my simulation goes terribly slow at times, seemingly while
accessing
the hard disk. May be I should try emulating an SCSI disk... Anyway,
it's
all a matter of trying now to discover the optimal setup. QEMU
emulates a
fairly recent system so it's no surprise Coherent has some concerns...
Andrzej Popielewicz
> On Jul 15, 2:03 am, Andrzej Popielewicz <va...@icpnet.pl> wrote:
>> Andrzej Popielewicz wrote:
>>>
> It's simple:
>
> [ctrl][Alt][2] (stop the simulation and go to command mode)
>
> change floppy0 name-of-file
>
> [ctrl][Alt][1] (back to the simulation with floppy changed)
>
> and so on...
OK, it is good to know standard procedure, although my worked fine.
>
> BTW, my simulation goes terribly slow
The same with me. After installation I have edited /etc/brc with
/usr/bin/elvis and removed fsck.brc script should return 0.
fsck is the most slow part.
I jave switched back from Ubuntu 7 to Ubuntu 6 (Dapper), because under 7
I could not compile kqemu accelerator.
kqemu seems not to help much. It is still slow.Perhaps with P4 would be
better,
On such hardware Coherent usually flies, so it is a problem of Qemu.
One could try to use virtualbox under Solaris/OpenSolaris.
One can make copy of disk iamge , and if image gets corrupted and can
take copy.
I will try to convince Robert, to allow publish small standard image.
BTW I am using 40 MB image.
This environment would be interesting for testing drivers.
What is interesting my Amilo Pro 2030 has SATA drive, and it works. It
seems SATA can understand IDE protocol. As far as know Qemu does not
know SATA.
Andrzej
Andrzej Popielewicz
> On Jul 15, 2:03 am, Andrzej Popielewicz <va...@icpnet.pl> wrote:
>y slow at times, seemingly while
> accessing
> the hard disk.
Sometimes helps using ramdisk. Try to create ramdisk (2 x 0.5 MB) and
copy frequently used excutables to it .
Then add ramdisk path to PATH etc...
Coherent at driver uses PIO, I have written VIA and SIS udma drivers,
but Qemu supports Intel PIIX pnly. Perhaps it motivates me to write PIIX
udma driver.It is on my TODO list.
Andrzej
Andrzej Popielewicz
On Thu, 17 Jul 2008, Andrzej Popielewicz wrote:
> txomsy napisał(a):
>> On Jul 15, 2:03 am, Andrzej Popielewicz <va...@icpnet.pl> wrote:
>>> Andrzej Popielewicz wrote>
>>
>>
> What is interesting my Amilo Pro 2030 has SATA drive, and it works. It seems
> SATA can understand IDE protocol.
I went too far with this hypothesis. Coherent IDE driver "talks" to QEMU
and NOT directly to Linux Sata driver and QEMU translates it to some Linux
calls.
Andrzej
Andrzej Popielewicz
On Thu, 17 Jul 2008, txomsy wrote:
> On Jul 15, 2:03 am, Andrzej Popielewicz <va...@icpnet.pl> wrote:
>> Andrzej Popielewicz wrote:
>>> txomsy pisze:
>
> BTW, my simulation goes terribly slow at times>
I have noticed , that Coherent boots with message showing Cyrix like CPU,
although I have Celeron.This suggests, that QEMU still translates some
Coherent calls not correctly.
For example Coherent uses a few busywait calls, some implemented with
hardware calls, perhaps these calls are not translated correctly and this
is why this slowness. Observing QEMU with top shows about 98% CPU usage,
as if perhaps some "looping(?)" took place.
Andrzej Popielewicz
On Thu, 17 Jul 2008, txomsy wrote:
> On Jul 15, 2:03 am, Andrzej Popielewicz <va...@icpnet.pl> wrote:
xxxxxxxx>> Andrzej Popielewicz wrote:
>>> txomsy pis
> BTW, my simulation goes terribly slow at times, seemingly while
> accessing
> the hard disk. May be I should try emulating an SCSI disk... Anyway,
> it's
> all a matter of trying now to discover the optimal setup. QEMU
> emulates a
> fairly recent system so it's no surprise Coherent has some concerns...
>
I have found in virtualbox forum, that 16 bit code is executed in
interpret mode, about 20-100 slower.Perhaps in qemu occurs the same.
Coherent caches io a little bit ( about 2 MB of buffers) , it means if You
run vsh for the second time, it is executed much faster.
I have succeeded to install ddk kit for Coherent under Coherent running in
qemu. I could also create new kernel in qemu using this kit. And newly
created Coherent
kernel works and boots fine in qemu.
Hint, do NOT reboot Coherent in qemu. make shutown : shutdown halt 0.
And then stop and start qemu.
Andrzej