public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	David Evensky <evensky@dancer.ca.sandia.gov>,
	kvm@vger.kernel.org
Subject: Re: kvm-tools: can't seem to set guest_mac and KVM_GET_SUPPORTED_CPUID failed.
Date: Thu, 17 Nov 2011 11:04:05 +0200	[thread overview]
Message-ID: <4EC4CE05.6000607@redhat.com> (raw)
In-Reply-To: <1321512998.4221.7.camel@lappy>

On 11/17/2011 08:56 AM, Sasha Levin wrote:
> On Thu, 2011-11-17 at 08:53 +0200, Pekka Enberg wrote:
> > On Thu, Nov 17, 2011 at 8:07 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > >> Also, when I start the guest I sometimes get the following error message:
> > >>
> > >>   # kvm run -k /path/to/bzImage-3.0.8 -m 256 -c 1 --name guest-15757
> > >> KVM_GET_SUPPORTED_CPUID failed: Argument list too long
> > >
> > > Heh, we were talking about it couple of weeks ago, but since I couldn't
> > > reproduce it here (it was happening to me before, but now it's gone) the
> > > discussing died.
> > >
> > > Could you please provide some statistics on how often it happens to you?
> > > Also, can you try wrapping the ioctl with a 'while (1)' (theres only 1
> > > ioctl call to KVM_GET_SUPPORTED_CPUID) and see if it would happen at
> > > some point?
> > 
> > I'm no longer able to reproduce it here with 3.2-rc1. We could just
> > try the easy way out and do what Qemu does and retry for E2BIG...
>
> Let's not do that :)

Right :)

> It'll just get uncovered again when someone decides to use
> KVM_GET_SUPPORTED_CPUID somewhere else (like in Avi's cpuid patch).
>
> I'll try going back to <3.0 later today and see if it comes back.

It might be worthwhile to write a small program that only does
KVM_GET_SUPPORTED_CPUID, to rule out issues in userspace (though there
isn't much of a window for such issues).


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-11-17  9:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  0:42 kvm-tools: can't seem to set guest_mac and KVM_GET_SUPPORTED_CPUID failed David Evensky
2011-11-17  6:07 ` Sasha Levin
2011-11-17  6:53   ` Pekka Enberg
2011-11-17  6:56     ` Sasha Levin
2011-11-17  9:04       ` Avi Kivity [this message]
2011-11-17 10:08         ` Sasha Levin
2011-11-17 15:38       ` David Evensky
2011-11-17 15:43         ` Sasha Levin
2011-11-17 15:50           ` David Evensky
2011-11-17 15:52             ` Sasha Levin
2011-11-17 15:53               ` Avi Kivity
2011-11-17 16:12                 ` David Evensky
2011-11-17 16:20                   ` Sasha Levin
2011-11-17 16:20                   ` Avi Kivity
2011-11-17 16:29                     ` David Evensky
2011-11-17 16:49                       ` Avi Kivity
2011-11-17 17:13                         ` David Evensky
2011-11-17 17:30                           ` Avi Kivity
2011-11-17 15:55   ` David Evensky

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=4EC4CE05.6000607@redhat.com \
    --to=avi@redhat.com \
    --cc=evensky@dancer.ca.sandia.gov \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox