Ok, another update. I was finally able to a guest domain installed by "hacking" my N1 System Manager Server install so that it could be used as a standard jumpstart server. By default, the N1 System Manager "provisions" the OS install, but it is dependent on being able to "discover" the ALOM interface on the physical server. As there is no physical connection of that nature pertaining to a guest domain, it can not be discovered and therefore, you can't use the typical provisioning mechanism.
In reality though, N1 System Manager is simply a front end ( as far as provisioning is concerned ) to a jumpstart server install that get's put there during the N1 install. When you perform a "create os" command under N1, it mounts the ISO, and runs the install_server scripts in the same fashion as you would with a standard jumpstart install. The add_install_client scripts is in fact put in the image area, but has the protection changed to non-execute. So... chmod 744 the script and run it based on the MAC address of the guest domain, and it will boot over the network to the jumpstart server just fine. As for the tagged connection.. here's my current configuration e1000g0 -> primary-vsw0 -> vnet0 at ldg1 -> subnet 1 ( backup network ) e1000g1 -> primary-vsw1 -> vnet1 at ldg1 -> subnet 2 ( management network ) e1000g2 -> primary-vsw2 -> vnet2 at ldg1 -> tagged VNIC ( vnet3002 = subnet 3 ) Based on this model, I was successful in getting the guest domain to function as far as the network using the VNIC entity with one exception thus far. Standard connection occur cleanly, but when I attempt to initiate an SFTP or FTP transfer, the transfer immediately hangs. It initially connects fine and I'm able to issue "ls" and "pwd" style commands, but as soon as I issue "get filename", the local copy get's created, but the data transfer stalls. Even stranger is that if I try to connect to it in the reverse direction, ie, logon to a different server and sftp to the guest domain, I can issue a "put filename" and it works cleanly with good performance..! As you can see, this at least has taken care of the core functionality of items 2, 3 & 4 of my original post ( 3 is misnumbered by accident ). As for the first point, I have updated to V1.0.1, which now allows me to at least reconfigure the control domain without having to remove and re-create the "initial" configuration, but in some instances, I still need to reboot the control domain for the changes to take affect. The ability for the guest domains to do "queued I/O's" also means that only a reboot can be done, not a halt of the control domain, unless you have configured a alternate "service domain", which I have not been able to test yet ( that's next ). Please let me know if anyone has seen the SFTP/FTP anomaly I described Tks again for all your feedback Dan -- This message was posted from opensolaris.org
