@FN-GM - don't suppose you know what ver of esx 5 that was? Looking at doing the same with ESX 5.1 this summer.
What problems are you having with sccm hyper and 2012?
Interested as that's what I'm starting on next week :-)
Not sure if its my lab and that I have about 7 VMs on one 2TB Drive ona 2008 R2 Hyper-V Host
Soon as I flipped SCCM back to running on a 2008 R2 Guest OS, everything has been fine
It is annoying as my DC is 2012 Core and running absolutely fine
Did it go back to normal after you removed the sccm service?
Didin't actually remove SCCM service per say
If you logged on immediately after boot it was perfect for about 5 mins
I changed the NICs once from Network Adapter to "Legacy" - and it was fine - only becuase 2012 didn't detect the legacy vNIC drivers - so the VM was running iwth no NICs
Was it the host of VMs that the performance was bad on?
It was the guest itself - it became unusable, and the other VMs suffered some performance degradation, though not as badly as the SCCM server was. I couldn't RDP to it, and even RPC calls (Event Viewer and Services) were hit and miss for that VM.
Soon as I powered it down everything was fine.
I'm guessing its something about SCCM on Server 2012 as they both work perfectly when running separately..
What are you guys doing for SQL Server? ie are you/have setup a dedicated virtual server or Installing SQL Server on the sever that requires it. I'm thinking of setting up two SQL Servers in Cluster, is this the right move? or is a Cluster too much? Im only thing of updates/maintance, might make it easier in a cluster right? Only thing we have left on the curriculum network is our TMG server. We have brought UAG now. This works in 2012 now right? and needs to be on two different networks right? (two different subnets)
Good to know, I've built a 2 host cluster with HyperV on Windows 2012 that I want to manage with SCCM later so will make sure I test it before I let it lose on a production server :-)
Ok I'll take it slowly :-)
synaesthesia (23rd June 2013)
Hohum. Time to do some real thorough testing with it first then! Cheers for the heads up.
Performance Best Practices for vSphere 5.1 « VMware
VMware also offers the VMXNET family of paravirtualized network adapters, however, that provide better performance than these default adapters and should be used for optimal performance within any guest operating system for which they are available.
The paravirtualized network adapters in the VMXNET family implement an idealized network interface that passes network traffic between the virtual machine and the physical network interface cards with minimal overhead. The VMXNET virtual network adapters (particularly VMXNET3) also offer performance features not found in the other virtual network adapters. Drivers for VMXNET-family adapters are available for most guest operating systems supported by ESXi.
The VMXNET family contains VMXNET, Enhanced VMXNET (available since ESX/ESXi 3.5), and VMXNET Generation 3 (VMXNET3; available since ESX/ESXi 4.0).The VMXNET3 adapter is the next generation of Para virtualized NIC designed for performance. The VMXNET3 network adapter is a 10Gb virtual NIC. Drivers are shipped with the VMware tools and most OSs are supported. VMXNET3 is much faster than e1000 or e1000e. VMXNET3 has less CPU overhead compared to e1000 or e1000e. VMXNET3 is more stable than e1000 or e1000e. (Source)
There are currently 1 users browsing this thread. (0 members and 1 guests)