From: graham <the_ether@lycos.co.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: App virtualisation, not OS virtualisation
Date: Thu, 27 Oct 2005 20:01:54 +0100 [thread overview]
Message-ID: <43612422.7010702@lycos.co.uk> (raw)
In-Reply-To: <2ec03a9d0510271155l2bef543gf83241bfa077ce93@mail.gmail.com>
>>>e OS.
>>>
>>>
>>Not really: Xen is extremely oriented towards encapsulating operating systems.
>>Encapsulating an application (whilst useful) is too "high level" for Xen;
>>it's really a separate problem space, since it'd basically share no code in
>>common with Xens current functionality.
>>
>>
>
>On a sort of related note, I was wondering if it was on any roadmap to
>support RAM sharing between OS instances -- like with VMware's clone
>feature (or something like that), I think if you had two very similar
>VMs, they would actually use less RAM and disk than each have, they
>would just diverge where they are different (some sort of
>copy-on-write scheme).
>
>Thanks
>
>
Yes, that would solve my concern about wasted resource of having
multiple copies of the same OS when all I want to do is run multiple apps.
In my case, I don't mind waiting 6 months for the virtualisation-enabled
AMD or Intel processors to be available.
BTW, in my case I intend using Windows XP embedded which, amongst other
things, will allow me to reduce the footprint of the Windows OS. I am
assuming that there shouldn't be any problems with that with the current
plans for Xen supporting Windows (?).
g.
next prev parent reply other threads:[~2005-10-27 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 0:55 App virtualisation, not OS virtualisation graham
2005-10-20 18:51 ` Nicholas Lee
2005-10-20 19:09 ` graham
2005-10-21 9:52 ` Nicholas Lee
2005-10-21 14:20 ` Mark Williamson
2005-10-27 18:55 ` John Levin
2005-10-27 19:01 ` graham [this message]
2005-10-27 19:02 ` Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 1:45 Ian Pratt
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=43612422.7010702@lycos.co.uk \
--to=the_ether@lycos.co.uk \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.