public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: hydra <hydrapolic@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xen on new install reboots by itself
Date: Wed, 15 Apr 2015 05:59:30 +0200	[thread overview]
Message-ID: <CAG6MAzT14SEvu9kDSpHus8ZbAfHuqnNNq_69Tu98v=KZyC6MGg@mail.gmail.com> (raw)
In-Reply-To: <87wq1mjnyx.fsf@heimdali.yagibdah.de>

[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]

On Wed, Apr 8, 2015 at 11:43 PM, lee <lee@yagibdah.de> wrote:

> hydra <hydrapolic@gmail.com> writes:
>
> > On Sat, Apr 4, 2015 at 3:20 PM, lee <lee@yagibdah.de> wrote:
> >
> >> symack <symack@gmail.com> writes:
> >>
> >> Other than that, unless you really do need full virtualization: I'm
> >> finding Linux containers to be far more manageable than virtual
> >> machines, and much more efficient.
> >>
> >>
> > Can you please post some more details?
>
> About containers?
>
> There's very useful documentation about them like
> https://wiki.gentoo.org/wiki/LXC ...
>
> What can I say?  Virtualization with xen is like juggling with a set of
> black boxes each of which aren't exactly accessible; the
> documentation sucks, it's hard work to get it running and likewise hard
> to maintain.
>
> Virtualization with containers is basically as simple as running just
> another daemon.
>
> Which the "better" tool, or combination of tools is, depends on what you
> want to accomplish.  You could use containers in a VM, too, or use
> virtualbox along with containers to run the odd VMs that require full
> virtualzation.
>
>
> --
> Again we must be afraid of speaking of daemons for fear that daemons
> might swallow us.  Finally, this fear has become reasonable.
>
>
 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? :)

[-- Attachment #2: Type: text/html, Size: 2317 bytes --]

  reply	other threads:[~2015-04-15  3:59 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 [this message]
2015-04-23 21:02         ` lee
2015-04-24 11:33           ` J. Roeleveld
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='CAG6MAzT14SEvu9kDSpHus8ZbAfHuqnNNq_69Tu98v=KZyC6MGg@mail.gmail.com' \
    --to=hydrapolic@gmail.com \
    --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