We are running ESX 5. To conserve SAN storage, we provision virtuals with the bare minimum needed disk space because it is so easy to extend disks later (extend the VMDK in VMWare, extend in Windows, done). No down time, and no wasted disk. We don't have to spend a lot of time trying to anticipate how big the disks will get and wasting disk if we guess too high.
In HyperV, you can't extend disks without shutting down the virtual - seriously. I can't for the life of me figure out why MS isn't fixing this instead of adding silly features like 4TB of guest RAM. And, I also wonder why HyperV users aren't howling about this. -----Original Message----- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Monday, January 07, 2013 9:43 AM To: NT System Admin Issues Subject: Re: Time sync On Mon, Jan 7, 2013 at 8:31 AM, Ken Cornetet <ken.corne...@kimball.com> wrote: > Lol, how many times do you need 64 vCPUs or 4TB of guest Ram versus > needing to extend a disk? I run VMware ESXi 5.0, and I know I have had to extend a disk any number of times. And Win2008 makes extending the boot disk so much easier, too. My largest VM has 16G of RAM, and I was even leery of that. And I have 6 hosts with 512G RAM each ... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
