Simon,
There's a known issue with using suspend2 on a QEMU host, described here:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html#suspend
But, it sounds like you have trouble with a suspend2-capable guest
kernel, and that the trouble starts as soon as you boot (ie before yo
I can't reproduce this. Please check two things:
1. In "block.c", the first two lines of the "bdrv_cancel_nonblock_io"
function should read:
if( bs->nbst.booted &&
bs->nbst.state != STATE_IDLE ) {
There was a bugfix here, in the most recent version of the patch, and if
you didn't
John R. Hogerhuis wrote:
I have no idea what 'frozen state' means in this context. Do you?
I guess not, since I suppose as soon as you really knew you would be in
a position to kill the fly with a fly swatter rather than running over
it with your car :-).
Not a criticism just a nudge... this
OK, maybe "robust" should read "slightly less flimsy" :)
It'd be nice if these use cases worked, under user-mode networking:
1. The user disables and re-enables a network interface in windows.
Instead of hanging, it should come back up. (Does anyone else have this
issue?)
2. The host's DNS
After I hibernate my x86 linux host machine (using the "swsusp2"
package) and resume, QEMU and guest hang. That is odd, because
hibernation is transparent to all other user programs.
Has anyone else noticed this? If so please try the patch.
You know QEMU is doing something weird, for it to b
Troy Benjegerdes wrote:
Which smbd are you using? The one on debian sarge wants to have write access
to some /var/run and /var/lib directories to coordinate locking. Because
it gets run as a regular user, (and is not suid root), it winds up
spitting out an error to the logfile and dying. It too
The most common use case for the '-smb' option may be '-smb $HOME'.
There is a problem with this case:
Windows attempts to connect as user "nobody". Smbd allows the connection
-- unfortunately, it also maps the "nobody" accesses to the host's
"nobody" account, so all write accesses fail.
Ho
Uli Heller wrote:
Problem: Starting QEMU with the option "-snapshot" produces
the following error message:
qemu: /usr/src/packages/BUILD/qemu-snapshot-2005-10-03_23/block.c:424:
bdrv_cancel_nonblock_io: Assertion `nbst->state == STATE_READ_DONE' failed.
Aborted
It doesn't matter if I us
Here are two new patches, which attempt to fix the QEMU build for the
dependency on pthreads introduced by nonblocking IO. They are on the
nonblocking IO page:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html#install
The first is a quick fix to the QEMU's 'configure' scrip
Brad Campbell wrote:
With this patch qemu will not boot the qcow files but will boot the base
images (I copy them and then try to boot to test). As soon as I patch -R
&& make, qemu will boot the qcow files no problems..
Let me clarify that..
qemu-img create -f qcow xp.img 4G
qemu -cdrom xp.i
I had to download and install Win2k SP4, then Win2k SP4 "Hotfixes," and
also an IE6 upgrade, before windows update ran.
Are you running with a tun/tap device, or -user-net ? I'm still unable
to get windowsupdate to work. Getting it to work in vmware seems to work
on the first try.
I've been
Christian MICHON wrote:
hmmm
the static binary crashes, the one with ptreadGC2.dll is ok.
What I tried to measure, on windows host, kqemu-0.7.2
loaded, was:
(1) tar -jxf linux-2.6.10.tar.bz2
(2) make allnoconfig; make
I confirm ~18% speed improvement in case (1), but no change
more or le
Whoops. I had the mistaken belief that Qemu already used pthreads.
So, the makefiles and configure script need to handle pthreads somehow
(especially on windows.) Pthreads-w32 is refusing to 'make install'
itself into standard lib and include directories. Unlike SDL, there is
no 'pthread-conf
Why is there a posix async IO 'standard', but a different linux AIO standard?
Linux has a Posix AIO library that sits on top of linux's native AIO:
http://www.bullopensource.org/posix/
It's pretty new, version 0.6. We might not want qemu to depend on it,
because most distros probably do
Troy Benjegerdes wrote:
I am also haveing trouble getting a fresh win2k install under qemu to actually
be able to run windows update.
I had to download and install Win2k SP4, then Win2k SP4 "Hotfixes," and
also an IE6 upgrade, before windows update ran.
-john
Jens Axboe wrote:
> Why not use aio for this instead, seems like a better fit than spawning
a thread per block device? That would still require a thread for
handling completions, but you could easily just use a single completion
thread for all devices for this as it would not need to do any re
Magnus,
I don't think the Windows 2000 install hack will ever be obsolete.
The installer assumes that a hard disk will take nonzero time to read
some data. QEMU always services a read in zero-guest-time. (With the
nonblocking IO patch, zero-guest-time reads still occur, when the
requested da
Non-blocking disk IO now works for any type of disk image, not just
"raw" format. There is no longer any format-specific code in the patch:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html
You might want this patch if:
* you run a multitasking guest OS,
* you access a dis
Folks,
Here's a patch which allows guest CPU cycles to run concurrent with IO
syscalls:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html
It's actually two patches -- a patch which enables DMA support (the same
one posted here a few days ago) and a second patch which appli
Hi,
Here's another patch to enable IDE DMA:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html
This patch, like Juergen Lock's earlier patch from which it is derived,
replaces the virtual PIIX3 IDE controller with a PIIX4.
It applies cleanly to 0.7.2.
This patch extends
20 matches
Mail list logo
