|
They're inherently the same ... undoable disks ...
they're just easier to work with (as is the whole product in my entirely VMware
biased opinion).
-- http://msetechnology.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Sent: Monday, October 10, 2005 3:29 PM To: [email protected] Subject: RE: [ActiveDir] [OT] Movement in licensing over Virtual Instances at MS. VMWare
Workstation I think starting with 5.0 has a similar concept to differencing
disks. Usually these things endup in the GSX platform, it just takes a while.
ESX has a differencing disks type story, I forget what its called, though.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe One thing that seems a
bit silly to me is if I have my new 64 bit server, GOLIATH, and he’s running 10
VMs with Windows, then he’s running 10 W2K3 kernels, 10 HALs, 10 __________
(fill in the blank). There was a concept, sort of filled by NTVDM, that
you could run something in there and if it crashed it didn’t take down the
OS. What if you could run an instance of Exchange in one of those?
Or a DC? VMs are now sort of like having CD images on the network were for
a while – 15 copies of NT4 SP6a, 12 copies of NT4 Option Pack, 25 copies of
Adobe Reader, 20 copies of IE5, 15 copies of IE4… you see what I mean. Run
10 VMs and you have maybe 15 GB of duplicate info on disk. I hear ESX can
mitigate that somewhat… but MS wrote the Windows code, who could do it better
than them? Or maybe I’m way off base here. ??
Well with this, you can
use differencing disks. I do it now after Dean talked about it. I build one
server and then spin up Differencing disks off of it and it drammatically
reduces my disk use. As for everything else,
you are describing running everything on a single machine with virtualization up
at the subsystem level which isn't really virtualization in the same terms of
the hardware virtualization. You still have a single registry and source for
device drivers, etc. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Rich
Milburn I’m a bit confused as
to what she was trying to say… in the quote below, she says four VMs, but she
doesn’t say four instances of
Windows… and she says that they’ll only charge for virtual images of Windows
actually running. I take that to mean that if I have a box with 10 virtual
machines defined but only 4 running at a time, that I only have to pay for
4? Unless I start a 5th one before I bring one of the others
down? Does it mean that currently I’d have to pay for 10? Or is it
that if I am only running 4 I can run them on top of one purchased copy of
Windows Server 2003 R2 EE? One thing that seems a
bit silly to me is if I have my new 64 bit server, GOLIATH, and he’s running 10
VMs with Windows, then he’s running 10 W2K3 kernels, 10 HALs, 10 __________
(fill in the blank). There was a concept, sort of filled by NTVDM, that
you could run something in there and if it crashed it didn’t take down the
OS. What if you could run an instance of Exchange in one of those?
Or a DC? VMs are now sort of like having CD images on the network were for
a while – 15 copies of NT4 SP6a, 12 copies of NT4 Option Pack, 25 copies of
Adobe Reader, 20 copies of IE5, 15 copies of IE4… you see what I mean. Run
10 VMs and you have maybe 15 GB of duplicate info on disk. I hear ESX can
mitigate that somewhat… but MS wrote the Windows code, who could do it better
than them? Or maybe I’m way off base here. ??
--------------------------------------------------------------------------- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe Virtual
Windows License Simplified <QUOTE> Microsoft also will
allow customers to have four virtual machines running on top of Windows Server
2003 R2 Enterprise Edition and Windows Server "Longhorn" Datacenter Edition at
no extra cost, Kelly said. </QUOTE> -------APPLEBEE'S
INTERNATIONAL, INC. CONFIDENTIALITY
NOTICE------- |
- RE: [ActiveDir] [OT] Movement in licensing over Virtual Instanc... Dean Wells
