Hi Olivier,
If you create a sparse file for the bhyve raw disk (e.g. with
truncate -s), du will show the actual blocks used rather than the
total size.
But can I truncate an already existing image disk (downloaded nanobsd
image as example) ?
Not without some processing. One wa
On 2/8/14, 2:35 AM, Olivier Cochard-Labbé wrote:
Hi,
just a report of my migration to bhyve.
I was using VirtualBox for generate full-meshed network lab of multiple VM
(essentially nanobsd based) and have migrated my script to bhyve.
My original script is resumed to this kind of usage:
./lab-s
Trying this again. First attempt went only to Sami.
I think it's awesome that there are projects using FreeBSD technology.
However, this list is for discussions related to virtualization in FreeBSD.
IMO, there has been a lot of off-topic posts on this list lately, mostly by
Aryeh. If I wanted this
On 2/8/14 11:25 PM, Sami Halabi wrote:
> As long as its practical and related to the virtualizationn I think its
> okay.
Correct but this has unfortunately not been the case.
> At least he provides a lot of info through his discussions.
Off topic is off topic in accordance with the stated FreeBS
As long as its practical and related to the virtualizationn I think its
okay.
At least he provides a lot of info through his discussions.
Sami
בתאריך 9 בפבר 2014 01:28, "Michael Dexter" כתב:
>
> For the curious, Aryeh posted 67 out of January's 276 messages to the
> list with the next highest po
For the curious, Aryeh posted 67 out of January's 276 messages to the
list with the next highest poster coming in at 21.
This is not the proper use of this list.
Michael Dexter
bhyve volunteer
___
freebsd-virtualization@freebsd.org mailing list
http://
On 2/8/14 1:57 PM, Aryeh Friedman wrote:
> Starting tomorrow (now that I got the evil empire OS out of the way) I am
> going to be adding both networking and storage... in that order but I plan
> to handle some "low hanging" things in storage before getting deep into
> networking like allowing any
On Sat, Feb 8, 2014 at 3:57 PM, Aryeh Friedman wrote:
>
>
>
> On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote:
>
>>
>> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
>> wrote:
>>
>>>
>>> It sounds almost identical to the qcow2 security issue being discussed
>>> on qemu-de...@qemu.org recent
On Sat, Feb 8, 2014 at 4:07 PM, Adam Vande More wrote:
>
> On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman
> wrote:
>
>>
>>
>>
>> On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote:
>>
>>>
>>> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman >> > wrote:
>>>
It sounds almost identical to
On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman wrote:
>
>
>
> On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote:
>
>>
>> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
>> wrote:
>>
>>>
>>> It sounds almost identical to the qcow2 security issue being discussed
>>> on qemu-de...@qemu.org recent
On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote:
>
> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
> wrote:
>
>>
>> It sounds almost identical to the qcow2 security issue being discussed on
>> qemu-de...@qemu.org recently. This might be a *HUGE* win for bhyve
>> then in considering that
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote:
>
>
> It sounds almost identical to the qcow2 security issue being discussed on
> qemu-de...@qemu.org recently. This might be a *HUGE* win for bhyve then
> in considering that it's default format is raw (should ahci-hdd be the
> default?). d
On Sat, Feb 8, 2014 at 3:19 PM, Aryeh Friedman wrote:
>
>
>
> On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman
> wrote:
>
>>
>>
>>
>> On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote:
>>
>>>
>>> On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman >> > wrote:
bhyve blindly read/writes into
On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman wrote:
>
>
>
> On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote:
>
>>
>> On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman
>> wrote:
>>>
>>> bhyve blindly read/writes into the middle of the file without consulting
>>> the filesystem and thus bypass
On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote:
>
> On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman
> wrote:
>>
>> bhyve blindly read/writes into the middle of the file without consulting
>> the filesystem and thus bypassing any things like sparse fill in namely
>> all you gain is a few
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman wrote:
>
> bhyve blindly read/writes into the middle of the file without consulting
> the filesystem and thus bypassing any things like sparse fill in namely
> all you gain is a few seconds of startup time (matter of fact I think
> truncate might u
On Sat, Feb 8, 2014 at 7:34 AM, Adam Vande More wrote:
>
> On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman
> wrote:
>>
>> bhyve (as far I know) disks must be one solid file (md backed) or a /dev
>> block device... therefore it is unlikely the above would work
>>
>
> The reported size would be iden
On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman wrote:
>
> bhyve (as far I know) disks must be one solid file (md backed) or a /dev
> block device... therefore it is unlikely the above would work
>
The reported size would be identical so I don't see what the problem is.
--
Adam
__
On Sat, Feb 8, 2014 at 6:39 AM, Adam Vande More wrote:
> On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labbé >wrote:
>
> > On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote:
> >
> > >
> > >
> > > If you create a sparse file for the bhyve raw disk (e.g. with truncate
> > > -s), du will show t
On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labbé wrote:
> On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote:
>
> >
> >
> > If you create a sparse file for the bhyve raw disk (e.g. with truncate
> > -s), du will show the actual blocks used rather than the total size.
>
>
> But can I truncat
On Sat, Feb 8, 2014 at 6:20 AM, Olivier Cochard-Labbé wrote:
> On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote:
>
> >
> >
> > If you create a sparse file for the bhyve raw disk (e.g. with truncate
> > -s), du will show the actual blocks used rather than the total size.
>
>
> But can I truncat
On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote:
>
>
> If you create a sparse file for the bhyve raw disk (e.g. with truncate
> -s), du will show the actual blocks used rather than the total size.
But can I truncate an already existing image disk (downloaded nanobsd image
as example) ?
>
- Original Message -
> Hi Olivier,
> > just a report of my migration to bhyve.
>
> Yeah !!!
>
> > First remark comparing the disk format: With an original nanobsd disk image
> > of 488MB.
> > - Virtualbox format disk size: 133M
> > - bhyve raw disk size: 488M
>
> If you create a sp
Hi Olivier,
just a report of my migration to bhyve.
Yeah !!!
First remark comparing the disk format: With an original nanobsd disk image
of 488MB.
- Virtualbox format disk size: 133M
- bhyve raw disk size: 488M
If you create a sparse file for the bhyve raw disk (e.g. with truncate
-s), d
On Fri, 7 Feb 2014, Olivier Cochard-Labbé wrote:
First remark comparing the disk format: With an original nanobsd disk image
of 488MB.
- Virtualbox format disk size: 133M
- bhyve raw disk size: 488M
Can bhyve use sparse files for disk images?
Thank you for posting the comparison!
Hi,
just a report of my migration to bhyve.
I was using VirtualBox for generate full-meshed network lab of multiple VM
(essentially nanobsd based) and have migrated my script to bhyve.
My original script is resumed to this kind of usage:
./lab-script.sh -i FreeBSD-image-disk -n number-of-vm -l n
26 matches
Mail list logo
