I have a couple Sun T1000 servers that I have been trying to get logical domains setup on. It's a hardware layer virtualization and it is supported in openbsd. See ldomctl, and ldomd for more info. I was running into issues getting my ldom's created. The service console was refusing to install my configuration because it said I had overbooked the physical resources. My machine has 8 cores and 8GB of ram. This is what my configuration looked like:
domain tester {
          vcpu 2
          memory 2G
          vdisk "/storage/ldom/tester/vdisk0"
          vdisk "/storage/ldom/tester/vdisk1"
          vnet
  }

I created the virtual disks as follows:
dd if=/dev/zero of=/storage/ldom/tester/vdisk0 bs=1m count=8192
cp miniroot55.fs /storage/ldom/tester/vdisk1

Once this was done, I tried to initialize my ldoms using the config I had created. You'll need to get the factor-default config first. 
ldomctl init-system ldom.conf

Then I had to download that configuration to the service processor. 
ldomctl download openbsd

A quick confirmation that things worked:
 ldomctl list
  factory-default [current]
  openbsd [next]

Then I halted the primary domain I was in and reset the service processor. 
sc> reset -c

This is where things went wrong. 
ERROR: Physical resources required by LDoms configuration: openbsd not available. Falling back to default set

Apparently, with certain hardware/firmware combinations you need to specify your primary ldom. I edited my ldom.conf to reflect the number of cpu's and memory needed for the primary domain:
# cat openbsd/ldom.conf                                                        
domain primary {
        vcpu 12
        memory 4G
}

domain tester {
        vcpu 2
        memory 256M
        vdisk "/storage/ldom/tester/vdisk0"
        vdisk "/storage/ldom/tester/vdisk1"
        vnet
}

Once I installed this configuration and reset the service processor again, the primary domain booted right up. Now top reveals that there are 12 processors and 4GB of memory available. Hopefully this is useful to someone else as well. I'll see about updating the documentation as well. Cheers! 

p.s. I was then able to perform an openbsd install to the ldom after plumbing up the networking and booting the miniroot on the second disk through the serial console. 
# cu -l /dev/ttyV0
~~~#       (I was ssh'd in and ssh'd to the host)
ok boot disk1

Voila, install! 
Shared publiclyView activity