** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/939027
Title:
Combining direct_io and non-direct_io leads to hang
Status in QEMU:
Won't F
Unfortunately I don't have access to a qemu instance to test this any
more :)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/939027
Title:
Combining direct_io and non-direct_io leads to hang
Status
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 QE
On Thu, Feb 23, 2012 at 9:39 PM, Avleen Vig <939...@bugs.launchpad.net> wrote:
> Nothing else at all accesses those files, which is one of the things that
> concerned me the most :-/
> It looks like it call came from the same place.
It's possible to check the file descriptor flags using
/proc/$PI
Nothing else at all accesses those files, which is one of the things that
concerned me the most :-/
It looks like it call came from the same place.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/93902
