At that point your data integrity is only as good as the filesystem on the host OS (NTFS) , where your OI ZFS drives are stored as files. ZFS can't protect you from much there, even though this can be improved a little if you put each virtual drive on a different disk on the host.
That's why I'd prefer doing it backwards, with an OI host and windows guests. At that point, all your data is on a ZFS filesystem and you also have less driver issues (as long as OI supports the hardware you're running on) since Windows only has to deal with the VM drivers as a guest. Bryan Sent from my BlackBerry 10 smartphone. Original Message From: Harry Putnam Sent: Thursday, July 10, 2014 08:17 To: openindiana-discuss@openindiana.org Reply To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] a question of oi OS on ssd Harry wrote: > > And in that case it would be virtual drives being created on SSD > > hardware. > > Will that setup be likely to be more problematic than a non-virtual > > install of oi on that hardware? Bryan N Iotti <ironsides.med...@runbox.com> writes: > At that point, OI doesn't see the real disks, so no configuration and > no possible issues (other than unforeseen surprises in the VBox guest > additions). > > Still, why OI if you can't benefit from ZFS? I'm not sure I get your meaning there... why would I not be able to benefit from zfs? Does what I described as one possible way to go: (In brief: 2x xeon - 32 gb ram > OS windows 7 >vbox vm > OS oi) Can you expand on your meaning regarding not benefiting from ZFS in that scenario? I'm such a light weight skill/experience wise... I'm probably missing something fundemental... _______________________________________________ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss