From: Stuart Sheldon <stu@actusa.net>
To: kvm-devel@lists.sourceforge.net
Subject: Stupid Newbee Questions...
Date: Tue, 22 Apr 2008 16:50:03 -0700 [thread overview]
Message-ID: <480E79AB.9050107@actusa.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've looked around but can't seem to find these answers.
I'm using KVM to run multiple servers on the same hardware, but it seems
that most of the documentation written is for desktop use.
I'm currently running KVM-66 on a 2.6.24.4 kernel and using the KVM
provided modules. This is sitting on a Debian Lenny install with Intel
hardware.
Here are my questions:
1) Is there a way to give one virtual host priority over another? Would
I just add -cpu 2 on the host I want to give priority?
2) When I started writing the management scripts to start and stop the
guests from the command line, I was using KVM-63 which allowed me to
send a "system_powerdown" to the console, this would send a PWR to the
guest's acpid that would bring the guest down gracefully. This stopped
working in kvm-64 and is still not working in kvm-66. Is there a better
way to do this? How can the host bring down a guest without messing with
it's open programs?
3) Are there any statistics available from to the host os that can be
monitored, such as something in /sys or /proc?
Thanks in advance to all that answer!
Stu
- --
Open up the window Let some air into this room I think I'm almost
chokin' From the smell of stale perfume And that cigarette you're
smoking 'Bout scared me half to death Open up the window, sucker
Let me catch my breath
-- Three Dog Night - "Mama Told Me Not to Come - Lyrics"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIDnmrK69Y+xPZrWYRAp5yAKCev9Y6nDjILy4/z9hYGWnAFVUoTgCePAB6
esRDa/IPy3vb27KL13WKZBw=
=UHPE
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
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 reply other threads:[~2008-04-22 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 23:50 Stuart Sheldon [this message]
2008-04-23 5:54 ` Stupid Newbee Questions Amit Shah
2008-04-23 6:24 ` Avi Kivity
2008-04-23 10:07 ` Avi Kivity
2008-04-23 19:23 ` Stuart Sheldon
2008-04-23 21:15 ` 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=480E79AB.9050107@actusa.net \
--to=stu@actusa.net \
--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