[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to Q
Mouse not working in WinXP with QEMU either.
But it is working with bochs (same disk image).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not supported
S
thank you. Will keep at it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not supported
Status in QEMU:
New
Bug description:
Trying to install NeXTS
I don't know about Bochs but here's another page with resources on running
OPENSTEP on a VM:
http://www.zebpedersen.co.uk/?p=126
The VMWare drivers (both svga and mouse) should work with QEMU too but I don't
know if they are compatible with NeXTSTEP.
Now I remember there was some problem with mou
No luck with msmouse. NextStep assumes a PS/2 mouse, I believe,
which is what QEMU emulates by default. In bochs, the mouse does
work in NextStep. Do you know if bochs emulates the PS/2 mouse
by default?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
The other patch is for KVM. Here's a way to build a patched kvm module (I did
not test it):
http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/#sec_0_kvm_kmod_build
A click in the window should be enough to grab the mouse. If it's not
working it may be that NeXTSTEP is using a different driver than
So, Zoltan pointed to two patches. I applied the first
(v8-06-10-i8259-fix.),
but the second patches a file that is not in version 1.7.0.
With the one patch, I am now able to get past the step where it crapped out
before. The dma messages are still there, but it seems that they can be
igno
http://lists.nongnu.org/archive/html/qemu-devel/2014-02/msg00889.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not supported
Status in QEMU:
New
B
Successfully installed NextStep in bochs, but not qemu.
Having same problem with OpenStep 4.2 in qemu.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not s
On Thu, 6 Feb 2014, tyler knosis wrote:
p.s. I tried Bochs 2.6.2, and it is not stuck at the same place. Did qemu
take the bochs bios
and change anything regarding the IDE drives?
With OPENSTEP 4.2 a similar irq hang is happening due to a bug in the
i8259 model which is fixed by the one lin
p.s. I tried Bochs 2.6.2, and it is not stuck at the same place. Did qemu
take the bochs bios
and change anything regarding the IDE drives?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1276879
Ti
Getting the same result in QEMU 1.6.2. NeXT setup is reporting
'interrupt timeout, cmd: 0xc5', ATA command c5 failed,
resetting drives.
This repeats until it gives up.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.laun
13 matches
Mail list logo
