Re: Using VBox created VMDK

Mark Johnson
2009-02-04T00:00:40Z

Joseph Mocker wrote:
> Mark Johnson wrote:
>>
>>
>> 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?
> Trying to do a zpool import (zpool import 6545049493936246812 npool)
> results in
>      cannot import ''rpool'': pool is formatted using a
newer ZFS version


The solaris version you created the disk with is newer
that the solaris version of the guest you are trying
to import it on... Upgrade the guest.



MRJ


> I was also getting strange messages just checking to see if there are
> any pools available to import. Note it shows "rpool",
>
> # zpool import
>  pool: rpool
>    id: 6545049493936246812
> state: UNAVAIL
> status: The pool was last accessed by another system.
> action: The pool cannot be imported due to damaged devices or data.
>   see: http://www.sun.com/msg/ZFS-8000-EY
> config:
>
>        rpool       UNAVAIL  newer version
>          c3d3s0    ONLINE
>
>>
>>
>>> 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.
> Yeah, Solaris would be the main guest. Nothing HVM
>>
>>
>>
>>> 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.
>
> Can''t wait!
>
>  --joe