* [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported
@ 2014-02-06 1:14 tyler knosis
2014-02-06 1:46 ` Laszlo Ersek
` (12 more replies)
0 siblings, 13 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-06 1:14 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
** Affects: qemu
Importance: Undecided
Status: New
--
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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
@ 2014-02-06 1:46 ` Laszlo Ersek
2014-02-06 1:47 ` [Qemu-devel] [Bug 1276879] " tyler knosis
` (11 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: Laszlo Ersek @ 2014-02-06 1:46 UTC (permalink / raw)
To: Bug 1276879; +Cc: qemu-devel
On 02/06/14 02:14, tyler knosis wrote:
> Public bug reported:
>
> Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
> In the terminal that started QEMU, there are a lot of
> dma: command 10 not supported
> and
> dma: command 14 not supported
> messages.
These correspond to
CMD_CYCLIC_PRIORITY
and
CMD_CYCLIC_PRIORITY | CMD_BLOCK_CONTROLLER
in write_cont() [hw/dma/i8257.c]. They are not supported (see
CMD_NOT_SUPPORTED in the same file).
> When the installation of NeXTSTEP gets to
> 'preparing disk for nextstep installation', there are a lot
> of messages that ATA command c5 failed and other info.
> The result is a failed installation.
0xC5 is WIN_MULTWRITE ("write sectors using multiple mode"), and it
seems to hook into DMA.
> Is this a bug in QEMU?
Probably not, it's more likely "incomplete" DMA emulation ("lack of
support").
> Is there a workaround, e.g. by
> disabling DMA altogether?
It's worth a try I guess, if you can figure out a way how to do that.
FWIW, ide_identify() appears to report unconditional support for:
- single word dma0-2
- mdma0-2
- udma5
(I have no clue about IDE or DMA btw.)
Laszlo
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
2014-02-06 1:46 ` Laszlo Ersek
@ 2014-02-06 1:47 ` tyler knosis
2014-02-06 16:51 ` tyler knosis
` (10 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-06 1:47 UTC (permalink / raw)
To: qemu-devel
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.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not supported
Status in QEMU:
New
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
2014-02-06 1:46 ` Laszlo Ersek
2014-02-06 1:47 ` [Qemu-devel] [Bug 1276879] " tyler knosis
@ 2014-02-06 16:51 ` tyler knosis
2014-02-06 20:58 ` BALATON Zoltan
2014-02-07 18:54 ` tyler knosis
` (9 subsequent siblings)
12 siblings, 1 reply; 15+ messages in thread
From: tyler knosis @ 2014-02-06 16:51 UTC (permalink / raw)
To: qemu-devel
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
Title:
lots of dma command 10, 14 not supported
Status in QEMU:
New
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 16:51 ` tyler knosis
@ 2014-02-06 20:58 ` BALATON Zoltan
0 siblings, 0 replies; 15+ messages in thread
From: BALATON Zoltan @ 2014-02-06 20:58 UTC (permalink / raw)
To: tyler knosis; +Cc: qemu-devel
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 liner patch referenced here:
http://lists.nongnu.org/archive/html/qemu-devel/2013-10/msg03329.html
so it's most probably not a BIOS problem. The fix was not merged though
due to some risks with migration and maybe other bugs that could currently
be masked by this one but I don't know if the risks are well understood.
Some discussion can be found in this thread:
http://lists.nongnu.org/archive/html/qemu-devel/2013-01/msg02396.html
Could you please let us know if this fixes the irq timeout you are seeing
with NeXTSTEP too? The dma commands are something else though that may not
be related.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (2 preceding siblings ...)
2014-02-06 16:51 ` tyler knosis
@ 2014-02-07 18:54 ` tyler knosis
2014-02-07 21:39 ` BALATON Zoltan
` (8 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-07 18:54 UTC (permalink / raw)
To: qemu-devel
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 supported
Status in QEMU:
New
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (3 preceding siblings ...)
2014-02-07 18:54 ` tyler knosis
@ 2014-02-07 21:39 ` BALATON Zoltan
2014-02-08 2:19 ` tyler knosis
` (7 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: BALATON Zoltan @ 2014-02-07 21:39 UTC (permalink / raw)
To: qemu-devel
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
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (4 preceding siblings ...)
2014-02-07 21:39 ` BALATON Zoltan
@ 2014-02-08 2:19 ` tyler knosis
2014-02-08 10:59 ` BALATON Zoltan
` (6 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-08 2:19 UTC (permalink / raw)
To: qemu-devel
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 ignored.
NextStep can now install its basic system onto a file.
Thank you for the help so far.
Now, I get to the point when NeXTStep want me to click on something to configure
the new system, but QEMU is not grabbing the mouse. After this step, it will install
the remainder of the system + apps.
I have a USB mouse on a x86_64 linux machine, and QEMU 1.7.0. This is the
command line I used:
qemu-system-x86_64 -hda x.img -fda f.img -cdrom cd.img
I have tried ctl-alt (both sides of the keyboard) to no avail.
--
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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (5 preceding siblings ...)
2014-02-08 2:19 ` tyler knosis
@ 2014-02-08 10:59 ` BALATON Zoltan
2014-02-08 18:13 ` tyler knosis
` (5 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: BALATON Zoltan @ 2014-02-08 10:59 UTC (permalink / raw)
To: qemu-devel
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 what
QEMU emulates. Since NeXTSTEP is quite old you may have better luck with
a serial mouse emulation such as msmouse or make sure a PS/2 mouse
driver is selected in NeXTSTEP (it may not autodetect 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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (6 preceding siblings ...)
2014-02-08 10:59 ` BALATON Zoltan
@ 2014-02-08 18:13 ` tyler knosis
2014-02-08 18:22 ` BALATON Zoltan
` (4 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-08 18:13 UTC (permalink / raw)
To: qemu-devel
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 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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (7 preceding siblings ...)
2014-02-08 18:13 ` tyler knosis
@ 2014-02-08 18:22 ` BALATON Zoltan
2014-02-08 18:59 ` tyler knosis
` (3 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: BALATON Zoltan @ 2014-02-08 18:22 UTC (permalink / raw)
To: qemu-devel
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 mouse emulation with the PS/2 or serial driver also on VMWare which made the mouse pointer jump around and then freeze. This may also happen with QEMU but it was never debugged AFAIK.
--
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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (8 preceding siblings ...)
2014-02-08 18:22 ` BALATON Zoltan
@ 2014-02-08 18:59 ` tyler knosis
2014-02-08 23:28 ` tyler knosis
` (2 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-08 18:59 UTC (permalink / raw)
To: qemu-devel
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 NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (9 preceding siblings ...)
2014-02-08 18:59 ` tyler knosis
@ 2014-02-08 23:28 ` tyler knosis
2017-10-28 13:49 ` Thomas Huth
2017-12-28 4:17 ` Launchpad Bug Tracker
12 siblings, 0 replies; 15+ messages in thread
From: tyler knosis @ 2014-02-08 23:28 UTC (permalink / raw)
To: qemu-devel
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
Status in QEMU:
New
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (10 preceding siblings ...)
2014-02-08 23:28 ` tyler knosis
@ 2017-10-28 13:49 ` Thomas Huth
2017-12-28 4:17 ` Launchpad Bug Tracker
12 siblings, 0 replies; 15+ messages in thread
From: Thomas Huth @ 2017-10-28 13:49 UTC (permalink / raw)
To: qemu-devel
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 QEMU.
https://bugs.launchpad.net/bugs/1276879
Title:
lots of dma command 10, 14 not supported
Status in QEMU:
Incomplete
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
` (11 preceding siblings ...)
2017-10-28 13:49 ` Thomas Huth
@ 2017-12-28 4:17 ` Launchpad Bug Tracker
12 siblings, 0 replies; 15+ messages in thread
From: Launchpad Bug Tracker @ 2017-12-28 4:17 UTC (permalink / raw)
To: qemu-devel
[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 command 10, 14 not supported
Status in QEMU:
Expired
Bug description:
Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0.
In the terminal that started QEMU, there are a lot of
dma: command 10 not supported
and
dma: command 14 not supported
messages. When the installation of NeXTSTEP gets to
'preparing disk for nextstep installation', there are a lot
of messages that ATA command c5 failed and other info.
The result is a failed installation.
Is this a bug in QEMU? Is there a workaround, e.g. by
disabling DMA altogether?
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1276879/+subscriptions
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2017-12-28 4:30 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-06 1:14 [Qemu-devel] [Bug 1276879] [NEW] lots of dma command 10, 14 not supported tyler knosis
2014-02-06 1:46 ` Laszlo Ersek
2014-02-06 1:47 ` [Qemu-devel] [Bug 1276879] " tyler knosis
2014-02-06 16:51 ` tyler knosis
2014-02-06 20:58 ` BALATON Zoltan
2014-02-07 18:54 ` tyler knosis
2014-02-07 21:39 ` BALATON Zoltan
2014-02-08 2:19 ` tyler knosis
2014-02-08 10:59 ` BALATON Zoltan
2014-02-08 18:13 ` tyler knosis
2014-02-08 18:22 ` BALATON Zoltan
2014-02-08 18:59 ` tyler knosis
2014-02-08 23:28 ` tyler knosis
2017-10-28 13:49 ` Thomas Huth
2017-12-28 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.