I have a working T2000 partitioned to have a primary and seven guest domains, all running obsd6.7. It has been running live with 5 of the guests live for several months with OBSD 6.7. Each guest has two vdisks with the OS on one and app specific data on the other.
I decided to try out 6.8 on one of the spare guests (that is what they are there for). do do this, I stop the guest (if running), unlink the app specific data file, and replace it with a link to miniroot68.img, and then do > ldomctl start -c guest6 the result is what you expect if the baud rate or parity is set wrong - garbled text. It looks like it is trying to boot from the first vdisk - which has not been prepared (probably all zeros), and the boot eventually fails, so then it presumably goes on to try netbooting. I am unable to stop the broken boot process, and would not know how to reset the baud rate, if that is what is required. Is this a 6.7/6.8 compatibility issue? a hardware problem? an uninitialised variable? What should I do? Is there a way to set the cmos params of a guest from the primary? (eg to stop auto-boot?) eg "ldomctl set auto-boot? false" I have seen similar issues (looks like wrong baud rate) a long time ago with a T1000, and AFAICR, the problem went away after cleaning it - but the T1000 ran hot when dirty, and the T2000 is not hot. Andrew
