From: Alex Davis <alex14641@yahoo.com>
To: avi@qumranet.com
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: Second KVM process hangs eating 80-100% CPU on host during startup
Date: Fri, 18 Apr 2008 15:44:23 -0700 (PDT) [thread overview]
Message-ID: <431451.51764.qm@web50201.mail.re2.yahoo.com> (raw)
In-Reply-To: <4808C889.9060902@qumranet.com>
--- On Fri, 4/18/08, Avi Kivity <avi@qumranet.com> wrote:
> From: Avi Kivity <avi@qumranet.com>
> Subject: Re: [kvm-devel] Second KVM process hangs eating 80-100% CPU on host during startup
> To: "Alex Davis" <alex14641@yahoo.com>
> Cc: kvm-devel@lists.sourceforge.net
> Date: Friday, April 18, 2008, 12:12 PM
> Alex Davis wrote:
> > Host software:
> > Linux 2.6.24.4
> > KVM 65 (I am using the kernel modules from this
> release).
> > X11 7.2 from Xorg
> > SDL 1.2.13
> > GCC 4.1.1
> > Glibc 2.4
> >
> > Host hardware:
> > Asus P5B Deluxe (P965 chipset based) motherboard
> > 4 GB RAM
> > Intel E6700 CPU
> >
> > Guest software:
> > Slackware 12.0 installed from CD-ROM.
> >
> > Command used to first KVM instance:
> > /usr/local/bin/qemu-system-x86_64 -hda
> /spare/vdisk1.img -cdrom /dev/cdrom -boot c -m 384 -net
> > nic,macaddr=DE:AD:BE:EF:11:29 -net
> tap,ifname=tap0,script=no &
> >
> > Command used to start second KVM instance:
> > /usr/local/bin/qemu-system-x86_64 -hda
> /spare/vdisk2.img -cdrom /dev/cdrom -boot c -m 384 -net
> > nic,macaddr=DE:AD:BE:EF:11:30 -net
> tap,ifname=tap1,script=no &
> >
> > tap0 and tap1 are bridged on the host. The guest OS
> was installed on /spare/vdisk1.img,
> > which was initially created by /usr/local/bin/qemu-img
> create -f qcow /spare/vdisk.img 10G
> > After the guest installation completed, vdisk1 was
> copied to vdisk2.
> >
> > The second instance always stops after printing
> > Checking if the processor honours the WP bit even in
> supervisor mode... Ok.
> > It stays hung until I press the return key in the
> first instance; sometimes clicking in another X
> > window will wake it up as well.
> >
> > This is a test machine so I can test patches (almost)
> at will.
> >
> >
>
> Strange. Does pinning each guest to a different cpu help
> (use 'taskset
> 1 qemu ... vdisk1.img & ', taskset 2 qemu ...
> vdisk2.img)
>
>
taskset made no difference. Upgrading to kvm-66 didn't help either.
> Any sufficiently difficult bug is indistinguishable from a
> feature.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-18 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 16:30 Second KVM process hangs eating 80-100% CPU on host during startup Alex Davis
2008-04-18 16:12 ` Avi Kivity
2008-04-18 22:44 ` Alex Davis [this message]
2008-04-19 4:19 ` Alex Davis
2008-04-19 22:47 ` Alex Davis
2008-04-19 23:11 ` Marcelo Tosatti
2008-04-20 0:08 ` Alex Davis
-- strict thread matches above, loose matches on Subject: below --
2008-04-16 19:52 Alex Davis
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=431451.51764.qm@web50201.mail.re2.yahoo.com \
--to=alex14641@yahoo.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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