From: Avi Kivity <avi@redhat.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: KVM SMP guests won't work (2.6.35-rc2+)
Date: Thu, 10 Jun 2010 21:44:07 +0300 [thread overview]
Message-ID: <4C113277.3020500@redhat.com> (raw)
In-Reply-To: <20100610112848.00ce4c1e@nehalam>
On 06/10/2010 09:28 PM, Stephen Hemminger wrote:
> With current 2.6.35-rc2 and following configuration, my build guest VM will
> not start (it was working previously).
>
> "Error starting domain: monitor socket did not show up: Connection refused"
>
> Surprisingly, other guests work fine. The one difference is that the build
> VM has 4 virtual CPU's.
>
Looks unrelated to kvm itself. Can you start the guest without
libvirt? An strace will show if it created the monitor socket or not.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-06-10 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:28 KVM SMP guests won't work (2.6.35-rc2+) Stephen Hemminger
2010-06-10 18:44 ` Avi Kivity [this message]
2010-06-10 20:06 ` Stephen Hemminger
2012-07-29 0:59 ` joe
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=4C113277.3020500@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).