I have a Z840 that has a single 24 core processor, 92 GB ECC DRAM, a 4.2 TB RAIDZ2 pool and a 3.6 TB RAIDZ1 pool on four 4 TB SATA drives. I'd like to share the RAIDZ1 pool with Win 7, Debian 12 and Solaris 10_u8 instances, potentially with all 4 system images running at the same time.
I recently upgraded to Hipster 2024.10 vi pkg which went very smoothly. Kudos to the folks who worked on that. The install ISO was less friendly when I tested it. I've created a Debian 12.9 instance using VirtualBox but haven't been able to sort out sharing a folder from the host OI system yet. That's more annoyance than concern as I've done it before. I'm most concerned about my old Solaris 10_u8 instance. I have a lot of software on it I do not feel like rebuilding. So I'd like to run that also, but not keen on a VM for that. IIRC there is a formula using zones and/or containers that will let me run OI and u8 on the same system. But I've never done that and the state of the documentation is a bit of a mess. I have all the books I know of and the Oracle docs, but it's a daunting set of tools with many permutations. Where do I look first? I'd like to be able to open windows on all 4 systems and access a shared filesystem so I can move data among applications easily without using NFS or CIFS. Goal: Hipster as base system managing hardware and normal UI system on RAIDZ2 pool Solaris 10_u8 image running I *think* in a container on Hipster ??? Debian and Windows running in VirtualBox on Hipster host 3.6 TB RAIDZ1 pool shared among all the OS instances, such that any OS instance can R/W the RAIDZ1 pool with owner OS sticky bit, but are completely isolated from each other as guests of Hipster on the RAIDZ2 pool. I've not done any more than the most minimal admin for a long time, so I have a real mess spread across 5 OS instances to consolidate and almost no surviving skills and no coworkers to talk to. I very much need someone to point me in the right direction. As I understand it a zone is a filesystem level access control tool and a container is a processor access control tool similar to a VM, but with less overhead because containers are designed to run similar processor management structures, i.e. instances of Solaris. Reading list desired. Thanks. Have Fun! Reg _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
