Re: SBS 2003 Only Boots in Safe Mode
Ok so taking a cue from our proc discussion, I switched the CPU type from the default of kvm64 to kvm32 - and guess what? It works!!! I guess the reason being that the SBS server software itself was 32 bit? Makes sense to me.. thanks for all your assistance...
Re: SBS 2003 Only Boots in Safe Mode
Hmm.. well I double checked and the system I'm using doesn't have VT-d capabilities. Also I verified that I already have 1 CPU, 1 Core, KVM disabled and ACPI enabled, but it still only boots in safe mode, with a permanent gray bar at the bottom of a black...
Re: SBS 2003 Only Boots in Safe Mode
Oh ok gotcha - I will say that I downloaded it about a week ago so I believe so, but I have everything powered down since it still isn't working, and I'm at work, so I will check it tonight and let you know. Thanks!
Re: SBS 2003 Only Boots in Safe Mode
I have no problem using the console, I guess what I don't get is what this command does? Is this a permanent change which will apply even if I shut the ProxMox server down?
I'm not really worried about the speed; this server has very basic utilization and...
Re: SBS 2003 Only Boots in Safe Mode
Where do I enter that first command? Is this something added to ProxMox as it boots, or set into the VM's conf file?
The system I'm using doesn't support KVM anyway so I have that turned off. Anyway I haven't been able to find it in the BIOS yet, although...
Re: SBS 2003 Only Boots in Safe Mode
Thanks again for the suggestions but unfortunately nothing has worked. I even went back and started the process over by:
1. Verified my VMWare VM would still boot.
2. Re-installed the registry hack file.
3. Re-copied the VMDK to the ProxMox store.
4...
Re: SBS 2003 Only Boots in Safe Mode
Also recently I had been working with the original vmdk file, but just to be thorough I re-converted it to a qcow2 and tried it again with ACPI off.. but the problem remains.
Hello,
I recently installed ProxMox on a system and am having trouble getting my SBS 2003 vm to run. This server was already virtualized and was running as a VMDK under VMware Player. I followed the standard instructions for converting to qcow2, although once I started having problems I tried...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.