All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Danny ter Haar <dth@dth.net>
Cc: kvm@vger.kernel.org
Subject: Re: kvm problems on new hardware
Date: Tue, 27 Oct 2009 11:45:10 +0200	[thread overview]
Message-ID: <4AE6C126.5030803@redhat.com> (raw)
In-Reply-To: <20091026100651.GA15566@dth.net>

On 10/26/2009 12:06 PM, Danny ter Haar wrote:
> Hello,
> I have a KVM virtualization problem.
> I've put together new hardware (supermicro) server with 2 E5530 cpu's
> and memory&  disk to start experimenting with virtualization.
>
> I intend to use the www.proxmox.com system/setup.
> I installed proxmox and started stress testing the hardware:
> parallel kernel compiles in a loop (concurrency_level=32)&
> memtest86+ during the night etc.
> The hardware/os performs rocksolid when i stress test it, but the moment
> i start a virtual guest (eg debian netinstall) i get the first screen of the
> installation procedure in a vnc screen. I choose either normal install or
> expert install , the guest screen goes blank with only a cursor and the
> kvm process prints an error on the console and starts to eat cpu cycles.
> So the host OS is not barfing, only the kvm process is giving problems and the
> guest is frozen.
>
>    

Does this happen for all guests (different OSes), or just this one?

Please provide a link to the install media.

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


  reply	other threads:[~2009-10-27  9:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 10:06 kvm problems on new hardware Danny ter Haar
2009-10-27  9:45 ` Avi Kivity [this message]
2009-10-27  9:58   ` Danny ter Haar
2009-10-27 10:27   ` Danny ter Haar
2009-10-27 10:34     ` Avi Kivity
2009-10-27 10:47       ` Danny ter Haar
2009-10-29 18:37       ` Danny ter Haar
2009-10-29 22:07         ` Ryan Harper
2009-10-30  0:23           ` Danny ter Haar
2009-10-30  8:10           ` Chris Lalancette
2009-10-30  8:54             ` Danny ter Haar
2009-11-04 10:43         ` 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=4AE6C126.5030803@redhat.com \
    --to=avi@redhat.com \
    --cc=dth@dth.net \
    --cc=kvm@vger.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 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.