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
Bugs item #1689684, was opened at 2007-03-28 10:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1689684group_id=180599
Please note that this message will contain a full copy of
On Tue, 2007-03-27 at 08:57 +0200, Avi Kivity wrote:
Hollis Blanchard wrote:
Hi Avi, I was wondering what you think is the right abstraction layer to
target for porting KVM to non-x86 architectures? To me it looks like
libkvm is the answer.
The kernel/userland interface is heavily
On Wednesday 28 March 2007, Hollis Blanchard wrote:
I don't see a big difference between the ioctl layer and libkvm. In
general, a libkvm function is an ioctl, and kvm_callback members are a
decoding of kvm_run fields. If you edit kvm_run to suit your needs, you
can probably reuse
Avi,
On Tue, Mar 27, 2007 at 07:10:58PM +0200, Avi Kivity wrote:
The Performance counters (PMU) cannot be fully virtualized, they need to
run on the actual MSR registers. The PMU interrupt is controlled by the
local APIC. To get overflow-based sampling to work in a guest, we need to
I was messing around with using the perf counters a couple weeks ago
as a way to get deterministic exits in the instruction stream of the
guest. I used the h/w msr save/restore area to disable the counters
and save the values on guest exit and restore them on entry. I also
set up the LVT to
On Wed, 2007-03-28 at 17:48 +0200, Avi Kivity wrote:
Hollis Blanchard wrote:
On Tue, 2007-03-27 at 08:57 +0200, Avi Kivity wrote:
I don't think we should be aiming at full source portability.
Virtualization is inherently nonportable, and as it is mostly done in
hardware, software
Avi Kivity wrote:
Gregory Haskins wrote:
Hi Avi,
You make good points. I will convert to a nest lock design and
resubmit. Should I use two mutexes, or a mutex and spinlock?
Also, do you have any suggestions on the signum I should use to IPI
the running guest? Should I use one of the
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
