From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFT] Fix for unhandled msr c0000081 problems under Intel cpus Date: Thu, 28 Dec 2006 15:21:18 +0200 Message-ID: <4593C4CE.4040203@qumranet.com> References: <457FCBB9.5070800@qumranet.com> <45805400.3060308@mr511.de> <458117E4.4010807@qumranet.com> <45812407.7010803@qumranet.com> <20061228131445.GA1438@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: To: Ingo Molnar In-Reply-To: <20061228131445.GA1438-X9Un+BFzKDI@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 Ingo Molnar wrote: > * Avi Kivity wrote: > > >>> I'll commit the previous patch (which is correct, even if no guest >>> actually uses syscall), and teach qemu not to read MSR_STAR when it >>> isn't available. >>> >> A patch is attached. Please test. >> >> (note it changes libkvm too) >> > > hm, this patch doesnt seem to work, qemu gives me: > > Could not create KVM context > > it comes from: > > 3064 ioctl(3, 0x4004ae0b, 0) = 0 > 3064 ioctl(3, 0xc004ae0f, 0xbff8bd98) = -1 E2BIG (Argument list too long) > > but i have an older (2-weeks) qemu drop from branches/release/qemu - is > that one supposed to work? > There was an accompanying bug in libkvm or qemu IIRC. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV