THANKS for responding, I have had my head spinning lately, so this one sorta slipped away... let me respond within (vastly snipped) > ##xen is pretty linux specific.. You better off > asking Solaris > dom0 questions on #solaris-xen on oftc.net.
Thanks, I have joined there. I probably just missed where that was listed ;) ----- > No, Solaris uses a different blktap implementation > based > on the VirtualBox disk code. (tap:vdisk vs tap:aio) > The VirtualBox code has much better support for vmdk, > vhd, and > vdi files.. vdiskadm also provides zfs like snapshot, > rollback, > etc functionality for file based disks. You can also > use it to > move between block, and file based disks. > > You can also move a file from VirtualBox or VMWare > and use it on > Solaris on Xen (assuming the OS is somewhat flexible > with the H/W > emulation used). > > tap:vdisk works fine over NFS.. Remember that > everything has > to be read/writeable by user xvm. We do need to > improve the > performance some more though. Is the WIKI still correct that tap:vdisk with VMDK format is the "best peforming" (and most compatible)? > > Although, if your looking towards a production'ish > environment, > I would suggest using iscsi. We also have some > modifications > which makes it possible to easily migrated a guest on > an iscsi > disk. > > phy:iscsi:/alias/<lun>/<iscsi-alias> > phy:iscsi:/static/<server IP>/<lun>/<target id> > phy:iscsi:/discover/<lun>/<alias or target id> We will look at iscsi, but past experience has not been real good with it. Our NAS backend is a 7410c, which does appear to support iscsi, so its something we can certainly look at trying again. I am looking for something that is network based for (live) migration compatibility. > . > > virt-install -p -n nevada -l /export/snv108.iso > --nographics \ > --noautoconsole -r 1024 \ > --disk > path=/static/192.168.0.70/0/iqn.1986-03.com.sun:02:d5 > b1c26-0a7a-c6b4-98f8-d6d267eb2561,driver=phy,subdriver > =iscsi Wow, thats nearly as obnoxious looking as FC WWNs ;) > > virsh attach-disk nevada > /static/10.6.70.64/0/iqn.1986-03.com.sun:02:01accb27- > 5a3-e45f-882d-dc4e48c5685d xvdb --driver phy > --subdriver iscsi Thanks. > > > > > > *** Next question: How do I find out what "drivers" > are supported > > for disks for example. There are a couple > examples on the wiki, > > but I didn't see anything in the man pages, I > didn't see any help > > or list option to tell me what it would support. > It seems like > > there should be a list somewhere that lists > driver/subdriver and > > maybe some description. At the very least maybe > there is a way to > > list a library directory or something? > > For file based disks, you should use tap:vdisk. OK, but that still doesn't explain the most basic question of how to get the list of drivers, sub drivers and how to use them... maybe a wiki page suggestion? :) (snipped virt-manager stuff, thanks) > > *** Next question: does XEN on OS support virtual > fiber channel? > > If you mean npiv, then yes... You can see the hotplug > script > /usr/lib/xen/scripts/vbd-npiv > r some details.. I don't have any H/W which supports > it > so I don't know that much about it. > Yes, I have been going round and round with NPIV. That is a whole separate thread :) see bug id # 6900002 :) ~tommy -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
