Tag Info

Hot answers tagged


Like chanting Bloody Mary into a darkly-lit bathroom mirror, let's see if we can get Jake Oshins to show up... Gang scheduling is also referred to as co-scheduling. I think VMware prefers the term co-scheduling to gang scheduling. In ESX versions prior to version 3.x, VMware used "strict" co-scheduling, which had the synchronization drawbacks. In ESX 3.x ...


You really, really want to be able to easily identify which files belong to which virtual machine. Even if you lose access to the Hyper-V console. This comes up when trying to restore a VM from backups. Or when Hyper-V forgets about all of your VMs and you need to import them. Or the VM config files are corrupt, and you have to recreate the VM and point ...


The term you are looking for is VDI - Virtual Desktop Infrastructure. It's a pretty wide topic - there are entire books written about it. But knowing that term should get you started on finding the appropriate guides.


Okay, Ryan, you made my day. I don't read this forum as much as I used to, but I happened to check in. Red888, you should know up front that I'm a software architect who works on Hyper-V at Microsoft. I assume most people reading this are perfectly capable of clicking on my name link below this and discovering that, or even Googling me, but for this ...


Instead of creating static reservations, why not set mac restrictions to get a normal DHCP address? http://technet.microsoft.com/en-us/magazine/ff521761.aspx MAC address filtering (aka link-layer filtering) is a feature for IPv4 addresses that allows you to include or exclude computers and devices based on their MAC address.


Beefy hardware! There's nothing necessarily wrong with this setup, though. I use similar configurations on the VMware side, but can't add any Hyper-V specific information to this. These days, you're safe virtualizing everything. I'm curious about the consolidation ratio. Why only run 1-2 systems (VMs) on each host? You should be able to achieve more than ...


I don't have enough rep to comment, so I'll just put this here. After using several hypervisors, Hyper V, VMWare, Xen, I'd suggest saving yourself some trouble and not converting at all. If you have the tooling in place you would be much better off just building your environment again. This way you can also be sure that none of the VMs have the same ...


A couple of things spring to mind here: When we converted, we used System Centre Virtual Machine Manager (hereafter referred to as SCVMM as life's too short) to take care of this. If you're serious about HyperV and you currently use vCenter to manage a VMware farm (rather than just having a couple of ESXi hosts that don't do much together) then I do ...


I like none. Because none of your templates is stable in case you move a VM. I would - and I do that myself - use a folder structure identical to the one you get when you mvoe a VM between hosts. That way nothing changes when - you move a VM between hosts.


How long is a piece of string? Generally: Hyper-V is slower than bare metal, but just a couple of percent. The critical point pretty much always is IO. For SQL Server also. Hyper-V will not magically fix a bad disc layout. I run a high performance SQL Server happily on Hyper-V, but it has 10 SSD and some HD attached ONLY to it (via pass through) to ...


Provided that it is a VHDX file, try those commands: Resize-VHD –Path c:\Disk.vhdx –SizeBytes 80GB If that throws an error try: Resize-VHD –Path c:\Disk.vhdx –ToMinimumSize You cannot shrink a VHDX to less than its minimum size. To get the minimum size: (Get-VHD .\disk.vhdx).MinimumSize


I tend to error on the side of caution, but I have HyperV servers running DCs all the time... The hypervisor is joined to the domain for convenience, but that is all...

Only top voted, non community-wiki answers of a minimum length are eligible