From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dba-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: rsyncing to Guest Ubuntu System
Date: Fri, 09 Nov 2007 02:34:58 +0200 [thread overview]
Message-ID: <4733AB32.9040308@qumranet.com> (raw)
In-Reply-To: <4733A8E7.8020201-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org>
Clive Stewell wrote:
> I have been testing KVM for eventual use in a production server
> environment and am running into some trouble when I attempt to rsync my
> data from the current production system to the test system.
> Specifically, whenever I hit a large file, the guest freezes and I get
> the following in the host's system log:
>
> Nov 8 16:14:20 vcr1 kernel: [2847590.399951] kvm: 10680: cpu0 unhandled
> wrmsr: 0xc1
> Nov 8 16:14:20 vcr1 kernel: [2847590.399959] inject_general_protection:
> rip 0xc01162ff
>
> I have Googled the error, but can't see anything that leads me to
> believe that I've made any errors in the configuration. Other things
> seem to work fine, but I can reproduce this freeze every time. Here's a
> recap of my environment...
>
> CPU Model: Intel Xeon 5130 2.0 Ghz
> KVM Version: 50
> Host Kernel: Linux version 2.6.20-16-generic (root@king) (gcc version
> 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Sep 23 18:31:23 UTC 2007
> Host Kernel Arch: i386
> Guest: Ubuntu Gutsy (i386)
> QEMU Command Line: /opt/kvm/bin/qemu-system-x86_64 -hda
> /home/kvm/images.d/w5.img -boot c -m 384 -net
> nic,macaddr=00:14:1C:30:AF:03 -net tap,ifname=tap3,script=no -daemonize
> -vnc :3
>
> Thanks for any pointers you can provide.
>
>
You can try this [Not tested]:
diff --git a/kernel/x86.c b/kernel/x86.c
index e905d46..71307cb 100644
--- a/kernel/x86.c
+++ b/kernel/x86.c
@@ -460,6 +460,7 @@ int kvm_get_msr_common(struct kvm_vcpu *vcpu, u32 msr, u64 *pdata)
case MSR_IA32_UCODE_REV:
case MSR_IA32_PERF_STATUS:
case MSR_IA32_EBL_CR_POWERON:
+ case 0xc1:
/* MTRR registers */
case 0xfe:
case 0x200 ... 0x2ff:
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-11-09 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 0:25 rsyncing to Guest Ubuntu System Clive Stewell
[not found] ` <4733A8E7.8020201-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org>
2007-11-09 0:34 ` Dor Laor [this message]
2007-11-11 11:02 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4733AB32.9040308@qumranet.com \
--to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dba-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.