I have been running my T1000 for almost a year on a config generated with
(I think) OBDS6.3.
I upgraded to 6.6 current on the day before it was released (2 October?).
I built a new config with minor changes (names of guest vdisks, and number
of CPUs allocated
to the primary - several had been unused previously).
On attempting to reboot with the new config, I get:
{0} ok boot
SC Alert: Host System has Reset
ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b5
Sun Fire(TM) T1000, No Keyboard
Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.30.4.d, 2048 MB memory available, Serial #77558134.
Ethernet address 0:14:4f:9f:71:76, Host ID: 849f7176.
Boot device: net File and args:
ERROR: boot-read fail
Evaluating:
Can't locate boot device
---
After this, my device tree is empty.
resetting to factory-default recovers the device tree, and the system will
boot.
I rebuilt the config reducing the amount of ram used by the last guest
(this has solved problems in the past). Downloaded it, and the problem
persists.
Does anyone know what the error means?
Are there non-obvious constraints on configs?
I think my pci is @7c0, not 780. I got the factory defaults by dumping the
factory default
config when I set the machine up before. The strings inside it seem to say
7c0.
Why would the newly compiled configs have a different root for the device
tree, and is there a way I can fix this?
