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
On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan gre...@freebsd.org 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
On Sat, Feb 8, 2014 at 6:20 AM, Olivier Cochard-Labbé oliv...@cochard.mewrote:
On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan gre...@freebsd.org 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
On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labbé oliv...@cochard.mewrote:
On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan gre...@freebsd.org 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
On Sat, Feb 8, 2014 at 7:34 AM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
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
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
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
On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
bhyve blindly read/writes into the middle of the file without consulting
the filesystem and thus bypassing any things like sparse fill
On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
bhyve blindly read/writes into the middle of the file
On Sat, Feb 8, 2014 at 3:19 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
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
On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
It sounds almost identical to the qcow2 security
On Sat, Feb 8, 2014 at 4:07 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
On Sat, Feb 8, 2014 at 3:57 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:
On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More amvandem...@gmail.comwrote:
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
It sounds almost identical to the qcow2 security
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 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 FreeBSD
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
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),
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!
- 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 sparse file for
19 matches
Mail list logo
