From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: rsyncing to Guest Ubuntu System Date: Sun, 11 Nov 2007 13:02:34 +0200 Message-ID: <4736E14A.7040202@qumranet.com> References: <4733A8E7.8020201@vilaj.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: dba-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org Return-path: In-Reply-To: <4733A8E7.8020201-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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 > > The error probably appears even before the freeze (right after boot). > 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. > Please try '-net nic,model=rtl8139,...' Though a long bug report on sourceforge doesn't indicate much chances of success. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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/