Ely Soto wrote:
Ok this is the fix I came up with.
Basically it will check all the other objects that could potentially be
waiting for service. This will prevent one high priority object from
starving the rest.
I'm not certain what the intention for the timeout 0 check but this
Ok I located the source of the problem.
The code in main_loop_wait() that uses WaitForMultipleObjects will only
service one object that woke it up.
What is occuring is that the host_alarm timer is being serviced anytime
the tap_semaphore is also signaled, therefore the tap callback function is
);
==
Ely Soto
Ely Soto [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/09/2007 01:54 PM
Please respond to
qemu-devel@nongnu.org
To
qemu-devel@nongnu.org
cc
Subject
Re: [Qemu-devel] 0.9.0 Win32 Tap inferface PPC Guest issue
Ok I located the source of the problem
I'm having an issue getting the 0.9.0 build ppc to work with tap.
OpenVPN 2.09
Relevant Parameters
-net nic -net tap,ifname=tap-lan
0.8.2 works quite well.
I've narrowed the break to the change described here.
http://lists.gnu.org/archive/html/qemu-devel/2006-08/msg00243.html
Backing this
Further details:
This call functions correctly and returns true.
tap-win32.c, line 534
ReleaseSemaphore(overlapped-tap_semaphore, 1, NULL)
However, WaitForMultipleObjects never returns successfully to execute the
callback function.
vl.c, line 5859
main_loop_wait()
...
Initially it looks like it may be some sort of timing issue.
It happened to start working a bit without any code changes after I was
stepping through the code.
Can't reproduce that yet.
Ely Soto
-
Notice: This e-mail is intended solely for use of the
