Leslie Mann wrote:
FYI, a switch to rtl8139 from the default NE2000 nic has cured the problem
under both kvm-18 and kvm-svn.
The hint finally sank in, I was able to reproduce after switching to
ne2k (I usually use rtl8139). The attached patch (for kvm-18) fixes it
for me. Confirmation
Avi,
Please test the attached patch [..]
Same problem here, except that I can reproduce the network hanger just
by mounting an SMB share and producing a certain network load, for
example copying a file of several megabytes or rapidly moving the slider
up and down. Setting the network device
Leslie Mann wrote:
Avi Kivity [EMAIL PROTECTED] writes:
Please test the attached patch, against kvm-17. This is subversion
revision 4546 and git commit c01571ed56754dfea458cc37d553c360082411a1.
Fails.
I notice that a lot of new code is related to pio. Seeing that it locks up
Avi Kivity [EMAIL PROTECTED] writes:
That's a good indication the problem is with handling I/O instructions.
I have an image that exhibits similar behavior (but on Windows chkdsk on
boot) so I'll try debugging that. If that does not work I'll try to
send you debug patches.
Would be glad
Avi:
Leslie Mann [EMAIL PROTECTED] writes:
Fails.
I notice that a lot of new code is related to pio. Seeing that it locks up
when
the VPN starts using the network, I sprinkled some printk's around and have
discovered that we enter an long running (endless?) loop in kvm_run.
Avi Kivity [EMAIL PROTECTED] writes:
Please test the attached patch, against kvm-17. This is subversion
revision 4546 and git commit c01571ed56754dfea458cc37d553c360082411a1.
Fails.
I notice that a lot of new code is related to pio. Seeing that it locks up when
the VPN starts using the
Leslie Mann wrote:
I'll prepare the first patch. Can you ensure that your upgraded setup
still works kvm-17.
It does, as I use it daily in order to run a Win app that I need.
Please test the attached patch, against kvm-17. This is subversion
revision 4546 and git commit
Leslie Mann wrote:
Avi Kivity [EMAIL PROTECTED] writes:
The SIGIO means some I/O has occured, but what exactly, we don't know.
Can you generate a core, attach it with gdb, and generate a backtrace?
Check the backtrace for signs of your password and delete them if
found. It shouldn't
Avi Kivity [EMAIL PROTECTED] writes:
It's probably the aio thread. But wasn't there a segfault? That should
get us a nice core.
No segfault. I don't believe that qemu has crashed, it just doesn't respond.
Only ill effect after killing the process is that the mouse dies.
The
Avi Kivity [EMAIL PROTECTED] writes:
The SIGIO means some I/O has occured, but what exactly, we don't know.
Can you generate a core, attach it with gdb, and generate a backtrace?
Check the backtrace for signs of your password and delete them if
found. It shouldn't be there, but then
breaks Cisco VPN on WinXP SP1
Leslie Mann wrote:
That works. Here is the last 100 lines from the strace capture. Letme know if
there is anything else you need.
[...]
21:05:48.736568 clock_gettime(CLOCK_MONOTONIC, {1334, 970496230}) = 0
0.10
21:05:48.736618 sigreturn
Leslie Mann wrote:
Avi Kivity [EMAIL PROTECTED] writes:
Can you run qemu under strace -ttT? Be prepared for a long log.
Also, checking with the -no-kvm option is worthwhile.
Avi:
Can't run under strace. XP starts to boot then blue screens complaining of an
infinite loop in
Avi Kivity [EMAIL PROTECTED] writes:
Ah, Windows sets a timeout when loading drivers, and of course strace
slows down the initial screen clear.
You can try attaching strace with the '-p' option, just before
connecting. This will reduce the log size greatly. I should have
thought of it
Leslie Mann wrote:
That works. Here is the last 100 lines from the strace capture. Letme know if
there is anything else you need.
[...]
21:05:48.736568 clock_gettime(CLOCK_MONOTONIC, {1334, 970496230}) = 0
0.10
21:05:48.736618 sigreturn() = ? (mask now []) 0.08
Leslie Mann wrote:
kvm-18 has broken use of Cisco VPN client on WinXP SP1 running on a FC6
2.6.19-1.2911 client, Intel Core Duo system. I have been running
successfully from kvm-11 thru kvm-17 without issue. After upgrading to
kvm-18 any attempts to connect the VPN client result in an
Avi Kivity [EMAIL PROTECTED] writes:
Can you run qemu under strace -ttT? Be prepared for a long log.
Also, checking with the -no-kvm option is worthwhile.
Avi:
Can't run under strace. XP starts to boot then blue screens complaining of an
infinite loop in the cirrus driver. I have
kvm-18 has broken use of Cisco VPN client on WinXP SP1 running on a FC6
2.6.19-1.2911 client, Intel Core Duo system. I have been running
successfully from kvm-11 thru kvm-17 without issue. After upgrading to
kvm-18 any attempts to connect the VPN client result in an unresponsive
X11 session
17 matches
Mail list logo
