Joseph Mocker wrote: > Thanks Mark, for verifying syntax. Seems like that was my problem. > > Now onto attempting to import a zpool from the device. ZFS is not happy > about doing so, weird.
OH, what problems do you see. It should just work? > My real goal is to try to build a virtual machine with VirtualBox, and > deploy and start it as an xVM Domain. Should this be possible? Depends on the guest.. You'll need to use ide on vbox. Also, you will have to reconfigure the NIC. For Solaris and Linux, this does work though. > And then, really what I want to do is copy the vdi or vmdk image to an > iSCSI LUN. I'm guessing a simple dd would not work. No, we are currently working on import/export, and convert functionality to be able to move back and forth between zvols, disks, vdi, vmdk, vhd, etc.. Susan should have the preliminary code ready by Feb 20th'ish. MRJ > --joe > > Mark Johnson wrote: >> >> Joseph Mocker wrote: >>> Hello, >>> >>> I can't get this to work. I tried lots of permutations of virsh >>> attach-disk and xm block-attach but neither resulted in attaching a >>> disk the domain that it would recognize. Format would always show, >>> something to the effect of >>> >>> AVAILABLE DISK SELECTIONS: >>> 0. c3d3 <drive type unknown> >>> /xpvd/x...@3 >>> 1. c3t0d0 <DEFAULT cyl 12531 alt 0 hd 255 sec 63> >>> /xpvd/x...@51712 >> Is this a PV or HVM guest? >> >> >> >>> I as attempting to attach a sparse vdi image of Nevada 105 I just >>> installed through Virtual Box this morning. Dom0 is running 105 as >>> well. I tried >>> >>> xm block-attach dse:odevtst-1 /export/home/mock/Nevada105.vdi 3 w >> This one is wrong. Should be >> xm block-attach dse:odevtst-1 >> tap:vdisk:/export/home/mock/Nevada105.vdi 3 w >> >> >>> xm block-attach dse:odevtst-1 /export/home/mock/test-vdi 3 w >> See above. >> >> >>> virsh attach-disk dse:odevtst-1 /export/home/mock/Nevada105.vdi >>> hdb --driver tap --subdriver vdisk >>> virsh attach-disk dse:odevtst-1 /export/home/mock/test-vdi hdb >>> --driver tap --subdriver vdisk >> >> These should have worked.. Can you look at /var/log/xen/xpvd-* towards >> the end of the log and see if you see any "ERROR" message from tap? >> >> also, do a "ps -ef | grep vdisk" to see if the tap application >> is running. >> >> >> >> >>> I even tried using vdiskadm create to create an image and then copy >>> my vdi over the existing vdi file. >> Don't need to do this. What you did should work.. I have >> done it a bunch of times. >> >> >> >> MRJ >> >> >> >> >>> I did scp the image from another system, but the file size is the >>> same so I wouldn't think that it would be a problem. >>> >>> Thoughts? >>> >>> --joe >>> >>> Mark Johnson wrote: >>>> Arik Fishbein wrote: >>>> >>>>> I was wondering if it's possible to create guest using existing >>>>> VirtualBox created image. Which version of OpenSolaris supports VDI >>>>> format? >>>>> Arik. >>>>> >>>> Yes. vdi support was integrated in b101. See the >>>> following for more info.. >>>> >>>> http://opensolaris.org/jive/message.jspa?messageID=299626 >>>> >>>> In b102, you can reference a vdi file directly.. >>>> e.g.. >>>> >>>> xm block-attach snv105 tap:vdisk:/tank/guests/nevada/disk3.vdi 3 w >>>> >>>> >>>> >>>> MRJ >>>> >>>> >>>> >>>> >>>>> Mark Johnson wrote: >>>>> >>>>>> Arik Fishbein wrote: >>>>>> >>>>>>> Hi. I wonder whether it's possible to use VMDK file cloned from >>>>>>> VirtualBox's VDI file as an image file. >>>>>>> >>>>>> Yes.. You can also just use the vdi file. What >>>>>> exactly are you trying to do and we can tell >>>>>> you the best way to do it. >>>>>> >>>>>> >>>>>> >>>>>> MRJ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Thanks, Arik. >>>>>>> _______________________________________________ >>>>>>> xen-discuss mailing list >>>>>>> [email protected] >>>>>>> >>>>>> _______________________________________________ >>>>>> xen-discuss mailing list >>>>>> [email protected] >>>>>> >>>> _______________________________________________ >>>> xen-discuss mailing list >>>> [email protected] >>>> > > _______________________________________________ > xen-discuss mailing list > [email protected] _______________________________________________ xen-discuss mailing list [email protected]
