How to image Server 2008?
in [Windows Servers]
|
Prev: windows home server
Next: Mix SAS and SATA Drives
From: Matija Kapraljevic [Revenger] on 9 Mar 2010 17:29 On Tue, 9 Mar 2010 10:08:58 -0700, kj [SBS MVP] wrote: > Hyper-V V2 (2008 R2) supports 8 physical processors and up to 64 logical > processors. I'm looking at the tables and it's always confusing me: How many processors can you assign per virtual machine? Hyper-V on Windows Server 2008 could assign 4 CPUs max... > Many of the issues with virtualizing DB servers (like Exchange and SQL) have > been around I/O, both disk and network. Yes, but, I/O overhead with passthrough disks is less than 10 percent, and I'd suggest that the physical host be packed with NICs, dedicate one to physical host only, and the others to virtual server(s) ...
From: kj [SBS MVP] on 9 Mar 2010 17:57
Matija Kapraljevic [Revenger] wrote: > On Tue, 9 Mar 2010 10:08:58 -0700, kj [SBS MVP] wrote: > >> Hyper-V V2 (2008 R2) supports 8 physical processors and up to 64 >> logical processors. > > I'm looking at the tables and it's always confusing me: > How many processors can you assign per virtual machine? > Hyper-V on Windows Server 2008 could assign 4 CPUs max... Ah, yes, *per virtual machine* it's still 4 "virtual" processors per virtual machine. - But Hyper-V supports the higher number of physical processors and higher number of virtual processors per Hyper-V host. Perhaps I took your original statment in the wrong context. > >> Many of the issues with virtualizing DB servers (like Exchange and >> SQL) have been around I/O, both disk and network. > > Yes, but, I/O overhead with passthrough disks is less than 10 > percent, and I'd suggest that the physical host be packed with NICs, > dedicate one to physical host only, and the others to virtual > server(s) ... Agreed. virtualization IO issues can be "non issues" with proper hardware and virtualization configurations even for demanding applications. -- /kj |