This Question is Answered
2 "helpful" answers available (6 pts)
ewwww. Thank you for pointing that one out. One more reboot and I would have had to remount and edit again. Guess I should read the whole thead but I will claim the noob hat.
Still reading this stuff as I had to see where advanced was.
Thanks again!
i've done the same thing, i edit the boot.cfg on both partitio. but everytime you restart you need to edit again.
I'll try what Dave.Mishchenko said later.
But any idea on why it wont boot to USB and cannot create Windows 2008 64-bit?
What im planning to do with this server is to install ESXi and host our main DC here, but i guess if it's not that stable it's a pretty bad idea...
Anyone using this server on production with ESXi???
Thanks again!
Ok now i got my ESXi running on DL160 G5.
I edit the boot.cfg and add the acpi=off on both partition. bootbank and altbootbank.
First try same problem, when you reboot it will get stuck again.
Second try i uncheck the acpi option on VI client. and it seems to work fine.
Now everytime i reboot i dont need to edit the boot.cfg BUT.... there's always a but hehehehe
when you reboot or shutdown a pink screen shows up... so you need to manually hard reboot the server.
right now i just ignore it and continue to install guest OS.
First install works fine with Windows 2008 Standard 32-bit with 2 processors. (every time i put 4 core it just hangs...)
was able to install, snapshot and update fine.
Second Install - Windows 2008 Standard 64-bit with 2 processors.
This it it took sometime, and when it reaches around 50-60% of the installl my vi client got disconnected. I check the console and it cannot ping anything so i need to force reboot again.
Still testing other OS versions....
I'm loosing confidence to put this server as an esxi production that will hold the maid DC and Sharepoint...
if that happen this will be an overkill for exchange 2007 with 15-20 people, but anyway let see...
I edit the boot.cfg and add the acpi=off on both partition. bootbank and altbootbank.
First try same problem, when you reboot it will get stuck again.
Second try i uncheck the acpi option on VI client. and it seems to work fine.
Now everytime i reboot i dont need to edit the boot.cfg BUT.... there's always a but hehehehe
when you reboot or shutdown a pink screen shows up... so you need to manually hard reboot the server.
right now i just ignore it and continue to install guest OS.
First install works fine with Windows 2008 Standard 32-bit with 2 processors. (every time i put 4 core it just hangs...)
was able to install, snapshot and update fine.
Second Install - Windows 2008 Standard 64-bit with 2 processors.
This it it took sometime, and when it reaches around 50-60% of the installl my vi client got disconnected. I check the console and it cannot ping anything so i need to force reboot again.
Still testing other OS versions....
I'm loosing confidence to put this server as an esxi production that will hold the maid DC and Sharepoint...
if that happen this will be an overkill for exchange 2007 with 15-20 people, but anyway let see...
Just an update...
I just finish reinstalling ESXi on DL 160 G5 with the latest build *"build-**123629"* and Wow!!!
It's a breeze, i mean it only took me less than 5 minutes to install and it's up and running right away!
you dont need to put acpi=off on the boot and you dont need to edit the boot.cfg or uncheck VMkernel.Boot.ACPI!!
Now im on the process on creating guest os. i hope this will be a good sign...
Thanks!
