Hi Sephe,
Sorry for the slow res too.
The response mail to sub...@... failed some reasons, also it took me a
few days to realize :-)
I'll test your 3 patches for a while and your patches (including
'closed-out' flag operation)
work well with qemu/kqemu environment.
BTW, I guess we need a small
Here is what I saw on messages when booting guest Linux.
May 5 11:03:28 pata kernel: ata0: FAILURE - oversized DMA transfer
attempt 98304 65536
May 5 11:03:28 pata kernel: acd0: setting up DMA failed
Any comments are welcome. thank you.
-Naoya
On 5/5/09, Naoya Sugioka naoya.sugi...@gmail.com
Hi,
Naoya Sugioka naoya.sugi...@gmail.com wrote:
[-- text/plain, encoding 7bit, charset: ISO-8859-1, 61 lines --]
Hi all,
Yes, now I fixed some kemu kernel module codes and which is ready for
your testing.
It works fine under current my environmtn (thinkpat t60p) with
DragonFry
2009/4/23 Johannes Hofmann johannes.hofm...@gmx.de:
When unloading kqemu.ko I get:
destroy_dev(): too few references on device! 0xc33746d8
kqemu(minor=) refs=1
A subsequent kldload ./kqemu.ko panics the system with
assertion: sr-refcnt == 0 in sysref_alloc
When you create a device
Hi all,
Yes, now I fixed some kemu kernel module codes and which is ready for
your testing.
It works fine under current my environmtn (thinkpat t60p) with
DragonFry 2.3-0-dev host,
DragonFly 2.2 guest.
The problem causing performance issue was in ioctl call with KQEMU_SET_PHYS_MEM.
Pleaes
Hi,
Michael Neumann mneum...@ntecs.de wrote:
On Fri, 10 Apr 2009 23:16:37 -0700
Naoya Sugioka naoya.sugi...@gmail.com wrote:
Hi,
I just motivated to port kqemu module since QEMU starts working good
recently, according to this mailing list.
Hi,
I'd really like to see a working
Ping! Hi again,
After some code review, I just found set_phys_mem command for ioctl
was missing in kqemu_ioctl() from original kqemu-freebsd.c and my
porting kqemu-dragonfly.c
(kqemu never work correctly under *BSD ?)
Anyway, I updated kqemu module,but still kqemu does not give me any benefit.
