Deploy an iSCSI target on the Pendium D machine and run your VM on the other Hyper-V capable box with the disk targeted being the iSCSI you just deployed? Very kludgy but it could work.
---- Jack Kramer Computer Systems Specialist University Relations, Michigan State University w: 517-884-1231 / c: 248-635-4955 From: David Lum <david....@nwea.org<mailto:david....@nwea.org>> Reply-To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>> Date: Thu, 18 Nov 2010 10:28:27 -0500 To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>> Subject: RE: You guys ever do this? It’s a PowerEdge 840 with a Pentium D CPU. Some of them came with Xeon’s which would have met the requirements. Plan B is use an older server to have 2003 on it, put 2008 R2 on the newer box and migrate functions off the 2003 box as time allows. The 2008 system is now their file/print and the 2003 is DC/DNS/DHCP. Their other system that can run Hyper-V doesn’t have the disk subsystem to support 17 users (SATA), what I want a 2nd Hyper-V system for is simply failover, as their existing SBS server is a Hyper-V VM. It doesn’t have to be super fast on the failover system, just operable while I would be resolving whatever blew up the original host. Mainly I feel like an idiot for asking about 2008 R2 and not specifically Hyper-V. I am fortunate that the geekage I was attempting is not as important to my client as it is to me. They see it as their server got a currently-supported OS so they’re better off now than they had been. Dave From: Andrew S. Baker [mailto:asbz...@gmail.com] Sent: Thursday, November 18, 2010 7:13 AM To: NT System Admin Issues Subject: Re: You guys ever do this? What CPU is it? You need to have hardware virtualization assistance, and it must be enabled. Plan B: Put Windows 2003 back on the server you flattened, install VirtualBox on that server and run the VHD image you have. http://www.virtualbox.org/wiki/Downloads Then put 2008 R2 on the other box that is more capable. ASB (My XeeSM Profile)<http://XeeSM.com/AndrewBaker> Exploiting Technology for Business Advantage... On Thu, Nov 18, 2010 at 10:03 AM, David Lum <david....@nwea.org<mailto:david....@nwea.org>> wrote: Back story: As I have discussed here earlier, I have a client that I was going to effectively P2V a server onto itself, and one tool I was pointed at was DISK2VHD…in tests I managed to get everything to look good, the DISK2VHD system worked fine on a different Hyper-V host, but what I couldn’t test was Hyper-V on the system itself before blowing away the existing 2K3 OS. Here’s my oops: Back in April I contacted Dell and asked “hey can this S/N PowerEdge run 2008 R2?”. They replied “yep, just update the firmware”. Last Friday I flatten the machine, install 2008 R2 with no issues, but when I got to add the Hyper-V role….the CPU does not support it, DAMN ME! What I did was ASSumed that being able to run 2008 R2 also meant it could run Hyper-V, but it can’t...(insert forehead slapping “DUH” icon here). In my head I had asked them about Hyper-V but looking back at my e-mails I only asked about R2 and not Hyper-V. Anyone here do something like that, and how did you remedy it? I had been prepared for almost anything - including this - so the client is operating fine but I didn’t gain the 2nd Hyper-V host server I was hoping for. They DO have another server that is Hyper-V capable but I’m not about to ask them to fork out $700 more for ANOTHER 2008 Server OS, so I am seeing if I can find it cheap (and legally) somewhere and out-of-pocket it. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ 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<mailto: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<mailto: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
