All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: kvm <kvm@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@kernel.org>,
	Cyrill Gorcunov <gorcunov@gmail.com>,
	Asias He <asias.hejun@gmail.com>,
	Prasad Joshi <prasadjoshi124@gmail.com>
Subject: KVM_GET_SUPPORTED_CPUID returning -E2BIG
Date: Sun, 08 May 2011 08:15:43 +0300	[thread overview]
Message-ID: <1304831743.10534.28.camel@lappy> (raw)

Hello,

I'm seeing a case where KVM tools occasionally fails with the following
error message: "KVM_GET_SUPPORTED_CPUID failed: Argument list too long",
which means that we get -E2BIG back from KVM_GET_SUPPORTED_CPUID.

Why would it happen if we pass KVM_MAX_CPUID_ENTRIES as the max number
of entries (in the nent field of struct kvm_cpuid2)?

Also, Why would it happen randomly and not each time the code is run?

-- 

Sasha.


             reply	other threads:[~2011-05-08  5:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08  5:15 Sasha Levin [this message]
2011-05-08  8:56 ` KVM_GET_SUPPORTED_CPUID returning -E2BIG 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=1304831743.10534.28.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=prasadjoshi124@gmail.com \
    /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.