On Tuesday, June 23, 2020 3:11 AM, Klemens Nanni <[email protected]> wrote:
> That is still on 6.7-stable, right?
> Is the machine's firmware up to date? Recent firmware on my T4-2 looks
> like this:
>
> -> show /HOST hypervisor_version obp_version sysfw_version
>
> /HOST
> Properties:
> hypervisor_version = Hypervisor 1.15.16 2018/11/28 07:41
> obp_version = OpenBoot 4.38.16 2018/11/28 07:24
> sysfw_version = Sun System Firmware 8.9.11 2018/11/28 07:59
Yes, it's still the same 6.7-stable, no change except for your patch and
recompiled ldomd.
The firmware version is this:
-> show /HOST hypervisor_version obp_version sysfw_version
/HOST
Properties:
hypervisor_version = Hypervisor 1.10.1.b 2011/09/12 09:56
obp_version = OpenBoot 4.33.1 2011/08/03 10:34
sysfw_version = Sun System Firmware 8.1.1.c 2011/09/12 10:53
(I got this machine from a liquidation sale so I haven't been able to get the
firmware update files, sadly.)
> Did you assign any PCIe devices to guest domains with `iodevice'?
No.
> Did you start with a fresh copy of the factory-default dump?
Yes.
> Please show the exact ldom.conf file you used.
It's the same as in the previous mail, I'm just starting out on this machine.
domain "primary" {
vcpu 4
memory 4G
}
domain "obsd" {
vcpu 2
memory 2G
vdisk "/storage/vmimages/obsd.img"
vnet
}
> Install the sysutils/mdprint package show the output of
> `mdprint -q -g frag_space,frag_mblock hv.md', this will show us the amount of
> memory ldomd is trying to allocate (in multiple fragments like size=24 as seen
> in the backtrace). Again: I never saw this on any machine, my T4-2 just works
> with it. Perhaps you have a bogus machine description? I vaguely remember
> `ldomctl init-system' behaving differently/crashing when *.md files
> existed already, so best to always run it with nothing but a clean copy
> of the "factory-default" dump and a ldom.conf text file.
This is the output of the command, both for the factory-default hv.md and the
"openbsd" hv.md:
# mdprint -q -g frag_space,frag_mblock factory-default/hv.md
frag_space (node 0x5de) {
bak <-- root (node 0x0)
fwd --> frag_mblock (node 0x5e2)
}
frag_mblock (node 0x5e2) {
base = 0x2a00000 /* 44040192 */
size = 0x6000000 /* 100663296 */
bak <-- frag_space (node 0x5de)
}
# mdprint -q -g frag_space,frag_mblock openbsd/hv.md
frag_space (node 0x12) {
fragsize = 0x800000 /* 8388608 */
bak <-- root (node 0x0)
fwd --> frag_mblock (node 0x17)
}
frag_mblock (node 0x17) {
base = 0x2a00000 /* 44040192 */
size = 0x6000000 /* 100663296 */
bak <-- frag_space (node 0x12)
}
> Can you try to reproduce this on recent snapshots?
I'll try to. I'll report back after upgrading to the latest snapshot.