Hello, today after getting my first T1000 installed with obsd I investigated the internet and discovered with deep pleasure that oraclevm was not needed to run ldoms on this beautiful jewel machine.
I found the article http://undeadly.org/cgi?action=article&sid=20121214153413 which was an enlightenment :) First of all huge thanks and CONGRATULATIONS to the devs for making this cool stuff come true, you really rock guys!!! Then I would like to ask for some advice as the procedure is still fresh and not much documented (the same man page of ldomctl does not list the commands used in the article, plus sparc@ and misc@ do not almost talk about this). I am running 5.3-release on a T1000 with 4GB ram and two 72GB SAS disks; the box sports all latest fw. I have defined a couple of vm with both 1GB ram. 1. normally I use minicom to send breaks (Meta-F), as on the Italian keyboard no tilde is present to easily send breaks with cu; anyway minicom seems not to like ttyV[0-1] (e.g.: minicom -p ttyV0 -> not a pseudo tty error), so I am forced to use either cu or tip; even copying in the terminal with the mouse 3rd button the break key combination ~# does not work (why?), so, in order to get the "ok" prompt I gotta wait for timeouts which is really annoying; any clues to send breaks easily through cu or tip??? 2. when I create virtual disks, I have no idea which permissions/ownership these files should have; theorically all is done by root so root rw should be enough for them to work wherever they are; I have created /root/vm[1-2]/vdisk[0-1] files, with vdisk0 the real root and vdisk1 the miniroot as specified; nonetheless the OBP does not "communicate" with them even if they are found: {0} ok show-disks a) /virtual-devices@100/channel-devices@200/disk@1 b) /virtual-devices@100/channel-devices@200/disk@0 q) NO SELECTION Enter Selection, q to quit: b /virtual-devices@100/channel-devices@200/disk@0 has been selected. Type ^Y ( Control-Y ) to insert it in the command line. e.g. ok nvalias mydev ^Y for creating devalias mydev for /virtual-devices@100 /channel-devices@200/disk@0 {0} ok boot /virtual-devices@100/channel-devices@200/disk@0 Boot device: /virtual-devices@100/channel-devices@200/disk@0 File and args: WARNING: /virtual-devices@100/channel-devices@200/disk@0: Communication error with Virtual Disk Server using Port 0. Retrying. [...till timeout] The same happens if I choose /virtual-devices@100/channel-devices@200/disk@1, nothing is being loaded. Could this possibly be a permission/ownership problem or what else? 3. Why do virtual NICs not have a MAC address? Is there any way to give a MAC to them? I would like to avoid using IPv6 whenever possible (this machine ought to be integrated in an IPv4 network). What would happen if I would just give the VNICs an IPv4 address and then, inside guests, provide an arbitrary MAC to them? 4. considering that ttyV? is the way to admin vm, ssh would be the main entrance to them for work; should I need X in a vm, even though the T1000 comes without video card, is there any hope to run ssh -X/-Y and having a result on a client (bsd/linux)? Any experience about this? That's all for now, thank you in advance and thanks again for the beautiful work. Paolo
