Dear list,
I have a problem with a Windows XP guest that I connect to via VNC and
is using sl keymap (option -k sl).
The guest is Windows XP and the problematic characters are s, c and z
with caron... when I type them via VNC, they are not printed at all in
virtual system... I have checked the
On Thu, 2013-09-19 at 23:19 -0500, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 2:38 AM
To: Bhushan Bharat-R65777
Cc: b...@kernel.crashing.org; ag...@suse.de; pau...@samba.org;
kvm@vger.kernel.org;
From: James Hogan james.ho...@imgtec.com
The x86 and ppc targets call cpu_synchronize_state() from their
*_cpu_dump_state() callbacks to ensure that up to date state is dumped
when KVM is enabled (for example when a KVM internal error occurs).
Move this call up into the generic cpu_dump_state()
Hi Stefan
Everything looks as expected.
Even more wierd: when i execute the script 01remote-ssh.sh as stated in
http://roosbertl.blogspot.ch/2012/12/centos6-disk-encryption-with-remote.html
i can connect with ssh to that machine, so its not a kvm problem i guess.
Many thanks for your help.
[Re: [PATCH 0/3] KVM: Make kvm_lock non-raw] On 16/09/2013 (Mon 18:12) Paul
Gortmaker wrote:
On 13-09-16 10:06 AM, Paolo Bonzini wrote:
Paul Gortmaker reported a BUG on preempt-rt kernels, due to taking the
mmu_lock within the raw kvm_lock in mmu_shrink_scan. He provided a
patch that
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 11:38 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org; kvm@vger.kernel.org; kvm-...@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org
Subject:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 9:48 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org; kvm@vger.kernel.org; kvm-...@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org
Subject:
On 13-09-20 02:04 PM, Jan Kiszka wrote:
On 2013-09-20 19:51, Paul Gortmaker wrote:
[Re: [PATCH 0/3] KVM: Make kvm_lock non-raw] On 16/09/2013 (Mon 18:12) Paul
Gortmaker wrote:
On 13-09-16 10:06 AM, Paolo Bonzini wrote:
Paul Gortmaker reported a BUG on preempt-rt kernels, due to taking the
On Fri, 2013-09-20 at 13:04 -0500, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 9:48 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org; kvm@vger.kernel.org;
On 2013-09-20 20:18, Paul Gortmaker wrote:
On 13-09-20 02:04 PM, Jan Kiszka wrote:
On 2013-09-20 19:51, Paul Gortmaker wrote:
[Re: [PATCH 0/3] KVM: Make kvm_lock non-raw] On 16/09/2013 (Mon 18:12) Paul
Gortmaker wrote:
On 13-09-16 10:06 AM, Paolo Bonzini wrote:
Paul Gortmaker reported a
On 2013-09-20 19:51, Paul Gortmaker wrote:
[Re: [PATCH 0/3] KVM: Make kvm_lock non-raw] On 16/09/2013 (Mon 18:12) Paul
Gortmaker wrote:
On 13-09-16 10:06 AM, Paolo Bonzini wrote:
Paul Gortmaker reported a BUG on preempt-rt kernels, due to taking the
mmu_lock within the raw kvm_lock in
On Fri, 2013-09-20 at 09:55 +0530, Bharat Bhushan wrote:
On booke, struct tlbe_ref contains host tlb mapping information
(pfn: for guest-pfn to pfn, flags: attribute associated with this mapping)
for a guest tlb entry. So when a guest creates a TLB entry then
struct tlbe_ref is set to point to
This fixes a typo in the code that saves the guest DSCR (Data Stream
Control Register) into the kvm_vcpu_arch struct on guest exit. The
effect of the typo was that the DSCR value was saved in the wrong place,
so changes to the DSCR by the guest didn't persist across guest exit
and entry, and some
On Fri, Sep 20, 2013 at 02:52:40PM +1000, Paul Mackerras wrote:
@@ -536,6 +536,9 @@ struct kvm_get_htab_header {
#define KVM_REG_PPC_LPCR (KVM_REG_PPC | KVM_REG_SIZE_U32 | 0xb5)
#define KVM_REG_PPC_PPR (KVM_REG_PPC | KVM_REG_SIZE_U64 | 0xb6)
+/* Architecture
This enables us to use the Processor Compatibility Register (PCR) on
POWER7 to put the processor into architecture 2.05 compatibility mode
when running a guest. In this mode the new instructions and registers
that were introduced on POWER7 are disabled in user mode. This
includes all the VSX
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 11:38 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org; k...@vger.kernel.org; kvm-ppc@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org
Subject:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 9:48 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org; k...@vger.kernel.org; kvm-ppc@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org
Subject:
On Fri, 2013-09-20 at 13:04 -0500, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, September 20, 2013 9:48 PM
To: Bhushan Bharat-R65777
Cc: Wood Scott-B07421; b...@kernel.crashing.org; ag...@suse.de;
pau...@samba.org;
On Fri, Sep 20, 2013 at 02:52:40PM +1000, Paul Mackerras wrote:
@@ -536,6 +536,9 @@ struct kvm_get_htab_header {
#define KVM_REG_PPC_LPCR (KVM_REG_PPC | KVM_REG_SIZE_U32 | 0xb5)
#define KVM_REG_PPC_PPR (KVM_REG_PPC | KVM_REG_SIZE_U64 | 0xb6)
+/* Architecture
This enables us to use the Processor Compatibility Register (PCR) on
POWER7 to put the processor into architecture 2.05 compatibility mode
when running a guest. In this mode the new instructions and registers
that were introduced on POWER7 are disabled in user mode. This
includes all the VSX
20 matches
Mail list logo
