Hi,
i'd like to know, what the qemu-project aims at.
Do the authers aim at writing (together with kqemu or qv86) an
alternative to VMWare? (At least in the x86 virtualization case)
I first thought that way and i still hope that, but i was disappointed
by qemu 0.8.0 and the latest version from CVS
> Sounds good, so at least it's on its way :-)
> It's on of those big items left on the TODO, so will be good to see go
> in. Then one should implement an ahci host controller for queued
> command support next...
Or use the scsi emulation :-)
>>> Ah, did not know that queueing
>>> IDE only supports one outstanding request, so having a thread that runs
>>> the synchronous block routines appears reasonable. However, SATA and SCSI
>>> both support multiple outstanding requests. The extension to the existing
>>> patch would be simple--increase the number of threads.
>> ???
>> 3) async block I/O (not merged yet)
>> It's not in HEAD yet, isn't it?
>
> The pthread-based async patch is a band-aid. No doubt it helps your
> particular case, but it's not the right approach long term.
>
> IDE only supports one outstanding request, so having a thread that runs
> the synchr
Hi,
sorry for bothering, but the last time i heard something about asyn IO
was on Feb 2nd. Fabrice said:
[quote]
I have at least 5 items on my TODO list :
1) New kqemu which virtualizes both user and kernel code (currently in
alpha stage but not released yet).
2) DMA block I/O (merged)
3) async b
> Just a note: setting DMA through hdparm doesn't work on Linux since
> tens of versions ago, it's been depreceted and you have to trust the
> on-boot autodetection (and it works fine -- unless you didn't compile
> the right driver in). It's the same on real machines.
WHAT!?
i have used it with K
> Win2k and Linux 2.6 (w/o kqemu) seem to work fine.
have you reinstalled Win2k?
Or did you somehow manage, to turn an already installed Win2k from a
"Standard PC" into a "ACPI PC" (as the hardware-manager calls it)?
___
Qemu-devel mailing list
Qemu-
>> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
>> stuff. I don't know, how odd that might seem to some OS.
>
> It's irrelevant to any OS that i know of.
;-)
>> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
>> pciid-database.
>
> Huh?
# cat /usr/share/mi
> i just booted a recent knoppix-cd (4.0.2) and i'm trying to enable DMA,
> but it won't work!
>
> I started qemu with that command:
>
> qemu -m 256 -cdrom knoppix.iso -boot d
>
> But inside knoppix, a "hdparm -d1 /dev/hdc" won't work:
> HDIO_SET_DMA failed: Operation not permitted
Ah ha! DMA
>> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
>> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
>
> Wrong device id, should be 0x7113.
Hmmm, i looked it up, and i think i know why the author "preferred" 7013
instead of 7113.
7113 is 82371AB/
Hi,
i just booted a recent knoppix-cd (4.0.2) and i'm trying to enable DMA,
but it won't work!
I started qemu with that command:
qemu -m 256 -cdrom knoppix.iso -boot d
But inside knoppix, a "hdparm -d1 /dev/hdc" won't work:
HDIO_SET_DMA failed: Operation not permitted
Are there some issues
> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
> regression found using the current CVS with ACPI...
I think, this answer is fairly useless for the OP.
So perhaps the OP wanted to ask: how do i tell my Win2k to properly use
the new PCI device?
I'm especially interested
> I have seen thoughts about asynchronous IO for qemu. I thought that they
> would have been integrated along with the DMA-patches already.
I'm sorry, i read a mail by Fabrice that async block I/O is not merged yet.
___
Qemu-devel mailing list
Qemu-de
>> I thought, that qemu-0.8.0's problem would be disk-IO. I installed
>> Windows 2000 and in the task-manager the CPU-Time is 100% during intense
>> IO. A "dir c:\ /A /S /B >NUL:" on the console causes 100% CPU-time and
>> most of it being that red-colored "in-kernel-time".
>
> Qemu host IO is syn
Hi,
i'd like to know, what the qemu-project aims at.
Do the authers aim at writing (together with kqemu or qv86) an
alternative to VMWare? (At least in the x86 virtualization case)
I first thought that way and i still hope that, but i was disappointed
by qemu 0.8.0 and the latest version from CVS
Hi,
are there any Gentoo-users out there?
Well, here are 2 ebuilds to use newest qemu-version from CVS:
http://bugs.gentoo.org/show_bug.cgi?id=125668
Greetings
Sven
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailma
16 matches
Mail list logo
