public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Jones <chris@rassalon.org>
To: kvm@vger.kernel.org
Subject: Hangs
Date: Fri, 14 Nov 2008 15:34:57 +0000 (UTC)	[thread overview]
Message-ID: <loom.20081114T151509-596@post.gmane.org> (raw)

I've have setup a couple virtual machines and they work great... for anywhere
between 2-24 hours.  But then, for no reason I can determine, they just go 100%
busy and stop responding.

My basic setup is:
   Ubuntu 8.10 server running on both host and guests.
   kvm version is the one from the Ubuntu distribution (kvm-72)
   Kernel is Ubuntu 8.10 kernel (2.6.27-7-server)
   
The two VMs are both run like:
     kvm -daemonize \
     -hda Imgs/ndev_root.img \
     -m 1024 -cdrom ISOs/ubuntu-8.10-server-amd64.iso      \
     -vnc :1 -net nic,macaddr=DE:AD:BE:EF:04:04,model=e1000 \
     -net tap,ifname=tap1,script=/home/chris/kvm/qemu-ifup.sh 

(With different disk imgs, vnc addresses and macaddrs)

The disk images are raw format:
    qemu-img create -f raw 80G Imgs/ndev_root.img

I've tried running with these options, and in different combos:

    -no-kvm-pit 
    -no-kvm-irqchip
    -no-acpi 

They don't seem to help much.  If anything, -no-kvm-irqchip seems to cause more
troubles.

I tried running with -no-kvm and it won't boot at all.

I also built my own 2.6.27.4 kernel, from kernel.org, and built my own version
of kvm-78, but saw the same behavior.

Anyone have any advice how I can resolve these hangs?  When the setup works,
it's a beautiful setup and I love kvm.  But with the 100% busy hangs I can't
really continue with it.

Thanks!
Chris



             reply	other threads:[~2008-11-14 15:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 15:34 Chris Jones [this message]
2008-11-16 16:36 ` Hangs Chris Jones
2008-11-18 21:34 ` Hangs Marcelo Tosatti
2008-11-19 10:57   ` Hangs Roland Lammel
2008-11-19 21:53     ` Hangs Roland Lammel
     [not found]       ` <20081120015600.GB10846@dmt.cnet>
2008-11-21 15:55         ` Hangs Glauber Costa
2008-11-21 20:29           ` Hangs Roland Lammel
2008-11-21 21:01             ` Hangs Daniel P. Berrange
2008-11-21 23:46               ` Hangs Roland Lammel
2008-12-06 23:18                 ` Hangs Roland Lammel
2008-12-09  0:34                   ` Hangs xming
  -- strict thread matches above, loose matches on Subject: below --
2008-11-19 22:43 Hangs chris
2008-11-20 17:10 ` Hangs chris
2008-11-21 19:32   ` Hangs Marcelo Tosatti
2008-11-21 23:43     ` Hangs Roland Lammel
2008-11-22 17:54     ` Hangs chris
     [not found]       ` <519a8b110811280305v764fade1w9d02f5c9188f56e5@mail.gmail.com>
2008-11-28 12:35         ` Hangs xming
2008-12-02 10:47           ` Hangs xming
2008-12-02 12:09             ` Hangs Avi Kivity
2008-12-02 20:58               ` Hangs chris
2008-12-02 23:01                 ` Hangs xming
2008-12-03  1:20                   ` Hangs chris
2008-12-03  9:13                     ` Hangs xming
2008-12-03 10:44                 ` Hangs Avi Kivity
2008-12-03 17:49                   ` Hangs chris
2008-12-18 18:05                     ` Hangs chris

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=loom.20081114T151509-596@post.gmane.org \
    --to=chris@rassalon.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox