AMD-64 Build 0718 Won't ReBoot on ESXi
-
Hi,
I just tried installing the AMD-64 version on an ESXi Virtual Machine. I tried both the Quick and Custom option, to build the disk, but both failed the same way. I used the non-SMP kernel. The setup completes normally, but then on rebooting, I get the error below.
My VM hardware settings are identical to my current 1.2.3 setup.
Also, when booting, after the message: acp10: <intel 440bx="">on motherboard, the system "hangs" for quite a while, before continuing. This only happens on the AMD-64 version.
I also tried the 0924, 32-bit build, and that installs and reboots without any issues.
Cheers.
P.S. Just a minor niggle, having done a few re-installs recently. The 2.0 wizard asks for the WAN and then the LAN interfaces, which is the opposite way to 1.2.3. That caught me out the first time, as I just typed them in, without really reading the text. I know, RTFText.
</intel>
-
I've had the same problem with several 64-bit builds on my ESXi box - I now stick to the 32-bit ones, which work flawlessly.
Out of interest, what CPU does your box have?
-
A couple of Opterons, which is what they are reported as to guests.
All the other 64-bit guests I have work flawlessly.
Cheers.
-
I'm not sure if this helps, or not. But, I am able to reproduce this, booting from the CD, with NO disk attached to the VM.
Selecting option 2, "No acpi", firstly doesn't have the "hang" following the "acpi0: <intel 440bx="">on motherboard" message, assuming that it's output, because it's scrolling too fast to read at that point.
But, more importantly, I get the exact same error, when it tries to mount the CD.
Cheers.
</intel>
-
As I was having trouble with the pfSense image, I thought I'd try a "clean" FreeBSD instead, to see if it's an issue in the underlying OS, as opposed to how it's been tailored.
Booting the FreeBSD DVD, with option 1, Default, it boots into the installer. Just like pfSense.
Booting the DVD, with option 2, Disable acpi, it hangs, at the point it's trying to mount the image. This is exactly the same place as with pfSense, but no messages. It just hangs. Image below.
After doing a minimal install, to disk, I tried booting from that.
With option 2, Disable acpi, I get EXACTLY the same results as trying to boot pfSense.
But, with the Default, option 1, it boots into the OS cleanly.
So, booting with acpi disabled, it looks like even a "vanilla" FreeBSD can't cope.
But, for a normal boot, it looks like something in the tailoring, for pfSense, is the issue.
Cheers.
-
Most of these are FreeBSD issues, you'll need to replicate with a stock FreeBSD 8.0 and report to the appropriate FreeBSD list for the issues to be resolved.
Not sure what the deal is with the mountroot failure, I'm seeing that on ESX as well.
P.S. Just a minor niggle, having done a few re-installs recently. The 2.0 wizard asks for the WAN and then the LAN interfaces, which is the opposite way to 1.2.3. That caught me out the first time, as I just typed them in, without really reading the text. I know, RTFText.
Because LAN is optional now.
-
With option 2, Disable acpi, I get EXACTLY the same results as trying to boot pfSense.
So, booting with acpi disabled, it looks like even a "vanilla" FreeBSD can't cope.
Agreed, that one should be pursued with FreeBSD.
But, with the Default, option 1, it boots into the OS cleanly.
But, for a normal boot, it looks like something in the tailoring, for pfSense, is the issue.
I think this one belongs to pfSense.
Cheers.