From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xen on new install reboots by itself
Date: Fri, 24 Apr 2015 13:33:06 +0200 [thread overview]
Message-ID: <8883663.cXMf2ByXNq@andromeda> (raw)
In-Reply-To: <87vbgmblsv.fsf@heimdali.yagibdah.de>
On Thursday, April 23, 2015 11:02:24 PM lee wrote:
> hydra <hydrapolic@gmail.com> writes:
> > You mean the documentation at Gentoo about Xen sucks or the upstream
> >
> > documentation? What information are you missing from there? Maybe we can
> > add the missing pieces for Xen being more accessible and easier to use,
> > what do you think? :)
>
> I mean the documentation they have on their wiki. It's a confusing mess
> referring to various version with which things are being done
> differently.
The problem here is the different "implementations" that exist:
- Xen (install and configure yourself, toolset: 'xl' , 'xm' is deprecated)
- Citrix and XCP (pre-configured, install on dedicated server, toolset: 'xcp')
- OVM (Oracle's implementation, not sure which toolset they use)
> Could you add missing pieces about why power management --- as in
> frequency scaling --- doesn't work
What doesn't work with this?
The following seems quite detailed:
http://wiki.xen.org/wiki/Xen_power_management
And the commands listed there (for the hypervisor based option) work on my
server.
> and what to do about keeping the time
> in sync between all VMs when you find out that this doesn't work as the
> documentation would have you think it does?
In what way doesn't it work?
The clocks are all synchronized and I don't need to use anything like 'ntpd'
--
Joost
next prev parent reply other threads:[~2015-04-24 11:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 23:07 [gentoo-user] xen on new install reboots by itself symack
2015-03-31 5:43 ` hydra
2015-04-01 1:52 ` symack
2015-04-01 10:08 ` hydra
2015-04-01 12:52 ` symack
2015-04-01 16:07 ` hydra
2015-04-01 16:24 ` symack
2015-04-02 4:53 ` hydra
2015-04-02 6:20 ` J. Roeleveld
2015-04-05 5:17 ` hydra
2015-04-04 13:20 ` lee
2015-04-05 5:19 ` hydra
2015-04-08 21:43 ` lee
2015-04-15 3:59 ` hydra
2015-04-23 21:02 ` lee
2015-04-24 11:33 ` J. Roeleveld [this message]
2015-04-24 20:24 ` lee
2015-04-25 11:34 ` J. Roeleveld
2015-04-28 22:34 ` symack
2015-04-29 3:38 ` J. Roeleveld
2015-04-29 5:11 ` hydra
2015-04-29 9:42 ` J. Roeleveld
2015-04-29 12:37 ` symack
2015-04-29 18:34 ` hydra
2015-05-01 10:02 ` lee
2015-04-16 14:12 ` J. Roeleveld
2015-04-16 22:38 ` symack
2015-04-24 11:47 ` J. Roeleveld
2015-04-23 21:03 ` lee
2015-04-24 11:37 ` J. Roeleveld
2015-04-24 20:23 ` lee
2015-04-25 10:12 ` J. Roeleveld
2015-05-01 11:27 ` lee
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=8883663.cXMf2ByXNq@andromeda \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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