When will vbox 6.X have a working port?

[Aryeh Friedman]

I have tried every patch I can find in bug.freebsd.org for 6.0.12 and 6.1X
they all fail to compile and/or mess my graphics up even more than 5.2
(with all it's really strange rendering).   So when is the port going to be
usable by mere mortals?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: AMD-V is being used by another hypervisor (VERR_SVM_IN_USE).

[Aryeh Friedman]

On Thu, Jun 25, 2020 at 5:57 PM Brandon helsley 
wrote:

> I am trying to start virtualbox but every time I try to load the iso the
> GUI displays that another VM is running and that I need to stop it to start
> virtualbox.
>

Are you using bhyve or qemu in another process?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

On Sun, May 24, 2020 at 3:17 PM Brandon helsley 
wrote:

> Which sysctl do you use, I didn't see it above. I will send you kldstat
>

sysctl net.link.tap.up_on_open=1
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

On some motherboards and AMD processors you need to load the modules at
boot time (bug?) for example on my MSI B450 Tomahawk w/ a Ryzen 5 2600x it
refused to work unless I put the kernel modules in /boot/loader.conf and
the above sysctl into /etc/sysctl.conf.

What is the output of kldstat?

On Sun, May 24, 2020 at 2:19 PM Brandon helsley 
wrote:

> # *ifconfig tap0 create*# *sysctl net.link.tap.up_on_open=1*
> net.link.tap.up_on_open: 0 -> 1# *ifconfig bridge0 create*# *ifconfig bridge0 
> addm igb0 addm tap0*# *ifconfig bridge0 up*
>
>
> # *truncate -s 16G guest.img*
>
> # *fetch 
> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso
>  
> *
>
> # *sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d guest.img 
> -i -I FreeBSD-10.0-RELEASE-amd64-bootonly.iso guestname*
>
> I'm on freebsd 12.1 p5
>
> Sent from Outlook Mobile 
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

On Sun, May 24, 2020 at 1:58 PM Brandon helsley 
wrote:

> What does bhyve command line mean? Like what commands I used to set up
> bhyve? I will send you name and ifconfig -a now
>

Yes in general command line means the command you typed

>
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
>
> ------
> *From:* Aryeh Friedman 
> *Sent:* Sunday, May 24, 2020 11:53:40 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Booting multi user mode in bhyve
>
> It sounds like you made no tap interface even if the kernel module is
> loaded what does ifconfig -a say?
>
> On Sun, May 24, 2020 at 1:33 PM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> I followed the handbook exactly and when trying to boot multi user the
> exact error message is  "loading configured modules... Can't find
> /boot/entropy open of /dev/tap0 failed device emulation initialization
> error: No such file or directory"
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
>
>
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

It sounds like you made no tap interface even if the kernel module is
loaded what does ifconfig -a say?

On Sun, May 24, 2020 at 1:33 PM Brandon helsley 
wrote:

> I followed the handbook exactly and when trying to boot multi user the
> exact error message is  "loading configured modules... Can't find
> /boot/entropy open of /dev/tap0 failed device emulation initialization
> error: No such file or directory"
>
> Sent from Outlook Mobile 
>
>

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

Can you send the complete command line your using, the exact error and the
output of dmesg?

On Sun, May 24, 2020 at 12:33 PM Brandon helsley <
brandon.hels...@hotmail.com> wrote:

> Yes, they are.
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
>
> ------
> *From:* Aryeh Friedman 
> *Sent:* Sunday, May 24, 2020 1:23:33 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Booting multi user mode in bhyve
>
> Are the vmm, if_tap, if_bridge and nmdm kernel modules loaded?
>
> On Sun, May 24, 2020 at 12:56 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> I'm trying to boot multi user in bhyve and it says "loading configured
> modules... Can't find /boot/entropy open of /dev/tap0 failed device
> emulation initialization error: No such file or directory?
>
> Sent from Outlook Mobile<https://aka.ms/blhgte>
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
>
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Booting multi user mode in bhyve

[Aryeh Friedman]

Are the vmm, if_tap, if_bridge and nmdm kernel modules loaded?

On Sun, May 24, 2020 at 12:56 AM Brandon helsley <
brandon.hels...@hotmail.com> wrote:

> I'm trying to boot multi user in bhyve and it says "loading configured
> modules... Can't find /boot/entropy open of /dev/tap0 failed device
> emulation initialization error: No such file or directory?
>
> Sent from Outlook Mobile
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve iso

[Aryeh Friedman]

On Wed, May 13, 2020 at 11:05 AM Brandon helsley <
brandon.hels...@hotmail.com> wrote:

> So a script is a list of commands? I looked at petite cloud and wasn't
> sure what it is. Does it generate a script that is a list of commands?
>

Yes a script, in its simplest form (Unix shell scripts are Turing complete
and thus in theory can do anything is possible to do on a general purpose
computer), is a list of commands.

PetiteCloud is a web (and as soon I get back to it in any serious way API
frontend) to bhyve and other hypervisors.   In order to do it's work it
generates scripts and runs them (this was a purposeful design decision so
the user can customize the script later and it also off loads as much of
the work as possible onto the underlaying OS, thus the name petite).  In
the jargon of the web page this is the cloud foundation layer on which you
can layer higher level cloud computing services on.

>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> ------
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 9:13:12 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 11:00 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> What does script mean?
>
>
> Refer to the man pages for each command.   The 10,000 ft view of the
> script though is the first call to bhyve does the install and the second
> one restarts the machine after the install.   The way each iteration is
> done is basically as follows:
>
> 1. Stop/destroy any existing running instances of the machine
> (Install only 1a. Create the file(s) needed to back the virtual hard
> drive(s))
> 2. Set up the networking needed connect the VM into the external LAN with
> a valid/routable connection
> 3. Run bhyve
> 4. Do any additional book keeping needed to allow PetiteCloud (the program
> that generated the script) to manage the VM instance from it's web interface
>
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 8:05:59 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 9:45 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> What is option for adding another drive? Ahci is under -s but I don't see
> anything relevant.
>
>
> Here is an example script for install FreeBSD and then rebooting the VM
> after the install:
>
> #!/bin/sh
> #
> # Generated by PetiteCloud 0.2.6
> #
>
> truncate -s 750G /vms/pri/dfdebf870cff2e43
> ifconfig tap6 destroy
> ifconfig tap6 create
> ifconfig tap6 up
> sleep 5
> ifconfig bridge0 addm tap6 up
> bhyvectl --destroy --vm=adda5345720edee1
> /usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
> 1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43 -s
> 3,ahci-cd,/vms/cds/FreeBSD-12.1-RELEASE-amd64-dvd1.iso -s 29,fbuf,tcp=
> 0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,stdio -l
> bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd adda5345720edee1
> echo $!>/var/run/petitecloud/adda5345720edee1
> sleep 10
> ifconfig tap6 destroy
> ifconfig tap6 create
> ifconfig tap6 up
> sleep 5
> ifconfig bridge0 addm tap6 up
> bhyvectl --destroy --vm=adda5345720edee1
> /usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
> 1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43  -s 29,fbuf,tcp=
> 0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,/dev/nmdm6B
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
> adda5345720edee1&>/dev/null
> echo $!>/var/run/petitecloud/adda5345720edee1
> sleep 10
>
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 7:32:23 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 9:26 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> In setting up bhyve today, or at least learning how, and I'm stuck at the
> part after I create with truncate the device map image. I'm supposed to put
> an iso with the devicemap.img and then boot from grub. How do I complete
> this last step with the iso? Could someone please help?
>
>
> See man page for bhyve but basically what you do is you add an other

Re: Bhyve iso

[Aryeh Friedman]

On Mon, May 11, 2020 at 11:00 AM Brandon helsley <
brandon.hels...@hotmail.com> wrote:

> What does script mean?
>

Refer to the man pages for each command.   The 10,000 ft view of the script
though is the first call to bhyve does the install and the second one
restarts the machine after the install.   The way each iteration is done is
basically as follows:

1. Stop/destroy any existing running instances of the machine
(Install only 1a. Create the file(s) needed to back the virtual hard
drive(s))
2. Set up the networking needed connect the VM into the external LAN with a
valid/routable connection
3. Run bhyve
4. Do any additional book keeping needed to allow PetiteCloud (the program
that generated the script) to manage the VM instance from it's web interface


> Sent from Outlook Mobile <https://aka.ms/blhgte>
> ------
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 8:05:59 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 9:45 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> What is option for adding another drive? Ahci is under -s but I don't see
> anything relevant.
>
>
> Here is an example script for install FreeBSD and then rebooting the VM
> after the install:
>
> #!/bin/sh
> #
> # Generated by PetiteCloud 0.2.6
> #
>
> truncate -s 750G /vms/pri/dfdebf870cff2e43
> ifconfig tap6 destroy
> ifconfig tap6 create
> ifconfig tap6 up
> sleep 5
> ifconfig bridge0 addm tap6 up
> bhyvectl --destroy --vm=adda5345720edee1
> /usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
> 1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43 -s
> 3,ahci-cd,/vms/cds/FreeBSD-12.1-RELEASE-amd64-dvd1.iso -s 29,fbuf,tcp=
> 0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,stdio -l
> bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd adda5345720edee1
> echo $!>/var/run/petitecloud/adda5345720edee1
> sleep 10
> ifconfig tap6 destroy
> ifconfig tap6 create
> ifconfig tap6 up
> sleep 5
> ifconfig bridge0 addm tap6 up
> bhyvectl --destroy --vm=adda5345720edee1
> /usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
> 1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43  -s 29,fbuf,tcp=
> 0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,/dev/nmdm6B
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
> adda5345720edee1&>/dev/null
> echo $!>/var/run/petitecloud/adda5345720edee1
> sleep 10
>
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 7:32:23 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 9:26 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> In setting up bhyve today, or at least learning how, and I'm stuck at the
> part after I create with truncate the device map image. I'm supposed to put
> an iso with the devicemap.img and then boot from grub. How do I complete
> this last step with the iso? Could someone please help?
>
>
> See man page for bhyve but basically what you do is you add an other drive
> like you do the disks but instead of saying the block device is AHCI-HD or
> VirtIOBlk you say it is AHCI-CD.
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>
>
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve iso

[Aryeh Friedman]

On Mon, May 11, 2020 at 9:45 AM Brandon helsley 
wrote:

> What is option for adding another drive? Ahci is under -s but I don't see
> anything relevant.
>

Here is an example script for install FreeBSD and then rebooting the VM
after the install:

#!/bin/sh
#
# Generated by PetiteCloud 0.2.6
#

truncate -s 750G /vms/pri/dfdebf870cff2e43
ifconfig tap6 destroy
ifconfig tap6 create
ifconfig tap6 up
sleep 5
ifconfig bridge0 addm tap6 up
bhyvectl --destroy --vm=adda5345720edee1
/usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43 -s
3,ahci-cd,/vms/cds/FreeBSD-12.1-RELEASE-amd64-dvd1.iso -s 29,fbuf,tcp=
0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,stdio -l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd adda5345720edee1
echo $!>/var/run/petitecloud/adda5345720edee1
sleep 10
ifconfig tap6 destroy
ifconfig tap6 create
ifconfig tap6 up
sleep 5
ifconfig bridge0 addm tap6 up
bhyvectl --destroy --vm=adda5345720edee1
/usr/sbin/bhyve -c cores=4 -m 8192 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
1,virtio-net,tap6 -s 2,ahci-hd,/vms/pri/dfdebf870cff2e43  -s 29,fbuf,tcp=
0.0.0.0:5906,w=800,h=600 -s 30,xhci,tablet  -s 31,lpc -l com1,/dev/nmdm6B
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
adda5345720edee1&>/dev/null
echo $!>/var/run/petitecloud/adda5345720edee1
sleep 10

>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Monday, May 11, 2020 7:32:23 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>
> *Subject:* Re: Bhyve iso
>
>
>
> On Mon, May 11, 2020 at 9:26 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> In setting up bhyve today, or at least learning how, and I'm stuck at the
> part after I create with truncate the device map image. I'm supposed to put
> an iso with the devicemap.img and then boot from grub. How do I complete
> this last step with the iso? Could someone please help?
>
>
> See man page for bhyve but basically what you do is you add an other drive
> like you do the disks but instead of saying the block device is AHCI-HD or
> VirtIOBlk you say it is AHCI-CD.
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve iso

[Aryeh Friedman]

On Mon, May 11, 2020 at 9:26 AM Brandon helsley 
wrote:

> In setting up bhyve today, or at least learning how, and I'm stuck at the
> part after I create with truncate the device map image. I'm supposed to put
> an iso with the devicemap.img and then boot from grub. How do I complete
> this last step with the iso? Could someone please help?
>

See man page for bhyve but basically what you do is you add an other drive
like you do the disks but instead of saying the block device is AHCI-HD or
VirtIOBlk you say it is AHCI-CD.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve help

[Aryeh Friedman]

When setting up a VM you also need to add the tap it is on to the bridge as
well your physical NIC

On Tue, May 5, 2020 at 6:28 PM Brandon helsley 
wrote:

> Bhyve gets me to Network installation: "some installation files were not
> found on the boot volume. The next few screens will allow you to configure
> networking so that they can be downloaded from the internet." This happens
> after system components.
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Tuesday, May 5, 2020 4:08:10 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>; Robert Crowston <
> crows...@protonmail.com>
> *Subject:* Re: Bhyve help
>
>
>
> On Tue, May 5, 2020 at 6:00 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> The handbook only says vmm doesn't it. I got bhyve to start without virtio
> kernel module as well as the if_tap but with vmm modules.
>
>
> The handbook section on virtualization (FreeBSD host) is at best awful and
> misleading your best guide is the bhyve man page (especially the examples
> there) here is the modules I load for the same set up I recommended you try
> as a advanced beginners lesson in virtualization and networking.   And an
> example script for using them:
>
> /boot/loader.conf:
>
> kern.geom.label.disk_ident.enable="0"
> kern.geom.label.gptid.enable="0"
> opensolaris_load="YES"
> zfs_load="YES"
> ipfw_load="YES"
>
> ipdivert_load="YES"
> linux_load="YES"
>
> In the real /boot/loader.conf the following are commented out because
> PetiteCloud takes care of them when it loads but unless you want to get
> into more advanced stuff (like how to install non-standard ports) you
> should uncomment them.
>
> vmm_load="YES"
> if_tap_load="YES"
> nmdm_load="YES"
>
> The script to load the file server VM:
>
> #!/bin/sh
> #
> # Generated by PetiteCloud 0.2.6
> #
>
> ifconfig tap12 destroy
> ifconfig tap12 create
> ifconfig tap12 up
> sleep 5
> ifconfig bridge0 addm tap12 up
> bhyvectl --destroy --vm=b829e56e9b4289a1
> /usr/sbin/bhyve -c cores=4 -m 4096 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
> 1,virtio-net,tap12 -s 2,ahci-hd,/vms/import/win10  -s 29,fbuf,tcp=
> 0.0.0.0:5912,w=1920,h=1080 -s 30,xhci,tablet  -s 31,lpc -l
> com1,/dev/nmdm12B -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
> b829e56e9b4289a1&>/dev/null
> echo $!>/var/run/petitecloud/b829e56e9b4289a1
> sleep 10
>
>
> I'm at this screen:please choose the appropriate terminal type for your
> system.common console types are: ansi, vt100, xterm, cons25w.
>
> Console type [vt100]:
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Tuesday, May 5, 2020 3:52:26 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>; Robert Crowston <
> crows...@protonmail.com>
> *Subject:* Re: Bhyve help
>
>
>
> On Tue, May 5, 2020 at 5:21 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> I have re0 but the ip address is under wlan0 with my CenturyLink
>
>
> In order to use vtnet and bridging (both required for bhyve networking)
> you need to load the load the virtio kernel module as well as the if_tap
> and vmm modules (the first one provides the host side of the virtual NIC
> and the second loads the hypervisor components)
>
>
> Sent from Outlook Mobile<https://aka.ms/blhgte>
>
> 
> From: Robert Crowston 
> Sent: Tuesday, May 5, 2020 3:14:43 AM
> To: Brandon helsley ;
> freebsd-virtualization@freebsd.org 
> Subject: Re: Bhyve help
>
> What are your network interfaces called on your machine? You probably have
> to change igb0 in the example to em0 (an Intel card) or re0 (a Realtek
> card). Type “ifconfig” to list all the interfaces, and look for ones with
> an ip address to figure it out.
>
> On Tue, May 5, 2020 at 10:10, Brandon helsley  <mailto:brandon.hels...@hotmail.com>> wrote:
> I'm trying to set up bhyve like the example to learn and when doing the
> physical interface interface get the result no such file or directory the
> command is:
>
> ifconfig bridge0 addm igb0 addm tap0
>
> "In this example, the physical interface is igb0"
>
>
> Sent from Outlook Mobile<https://aka.ms/blhgte>
> ___
> freebsd-virtualization@freebsd.org mailing

Re: Bhyve help

[Aryeh Friedman]

On Tue, May 5, 2020 at 6:00 AM Brandon helsley 
wrote:

> The handbook only says vmm doesn't it. I got bhyve to start without virtio
> kernel module as well as the if_tap but with vmm modules.
>

The handbook section on virtualization (FreeBSD host) is at best awful and
misleading your best guide is the bhyve man page (especially the examples
there) here is the modules I load for the same set up I recommended you try
as a advanced beginners lesson in virtualization and networking.   And an
example script for using them:

/boot/loader.conf:

kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
opensolaris_load="YES"
zfs_load="YES"
ipfw_load="YES"

ipdivert_load="YES"
linux_load="YES"

In the real /boot/loader.conf the following are commented out because
PetiteCloud takes care of them when it loads but unless you want to get
into more advanced stuff (like how to install non-standard ports) you
should uncomment them.

vmm_load="YES"
if_tap_load="YES"
nmdm_load="YES"

The script to load the file server VM:

#!/bin/sh
#
# Generated by PetiteCloud 0.2.6
#

ifconfig tap12 destroy
ifconfig tap12 create
ifconfig tap12 up
sleep 5
ifconfig bridge0 addm tap12 up
bhyvectl --destroy --vm=b829e56e9b4289a1
/usr/sbin/bhyve -c cores=4 -m 4096 -AI -H -P -w -g 0 -s 0:0,hostbridge -s
1,virtio-net,tap12 -s 2,ahci-hd,/vms/import/win10  -s 29,fbuf,tcp=
0.0.0.0:5912,w=1920,h=1080 -s 30,xhci,tablet  -s 31,lpc -l
com1,/dev/nmdm12B -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
b829e56e9b4289a1&>/dev/null
echo $!>/var/run/petitecloud/b829e56e9b4289a1
sleep 10

>
> I'm at this screen:please choose the appropriate terminal type for your
> system.common console types are: ansi, vt100, xterm, cons25w.
>
> Console type [vt100]:
>
> Sent from Outlook Mobile <https://aka.ms/blhgte>
> --
> *From:* Aryeh Friedman 
> *Sent:* Tuesday, May 5, 2020 3:52:26 AM
> *To:* Brandon helsley 
> *Cc:* freebsd-virtualization@freebsd.org <
> freebsd-virtualization@freebsd.org>; Robert Crowston <
> crows...@protonmail.com>
> *Subject:* Re: Bhyve help
>
>
>
> On Tue, May 5, 2020 at 5:21 AM Brandon helsley <
> brandon.hels...@hotmail.com> wrote:
>
> I have re0 but the ip address is under wlan0 with my CenturyLink
>
>
> In order to use vtnet and bridging (both required for bhyve networking)
> you need to load the load the virtio kernel module as well as the if_tap
> and vmm modules (the first one provides the host side of the virtual NIC
> and the second loads the hypervisor components)
>
>
> Sent from Outlook Mobile<https://aka.ms/blhgte>
>
> 
> From: Robert Crowston 
> Sent: Tuesday, May 5, 2020 3:14:43 AM
> To: Brandon helsley ;
> freebsd-virtualization@freebsd.org 
> Subject: Re: Bhyve help
>
> What are your network interfaces called on your machine? You probably have
> to change igb0 in the example to em0 (an Intel card) or re0 (a Realtek
> card). Type “ifconfig” to list all the interfaces, and look for ones with
> an ip address to figure it out.
>
> On Tue, May 5, 2020 at 10:10, Brandon helsley  <mailto:brandon.hels...@hotmail.com>> wrote:
> I'm trying to set up bhyve like the example to learn and when doing the
> physical interface interface get the result no such file or directory the
> command is:
>
> ifconfig bridge0 addm igb0 addm tap0
>
> "In this example, the physical interface is igb0"
>
>
> Sent from Outlook Mobile<https://aka.ms/blhgte>
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
>
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve help

[Aryeh Friedman]

On Tue, May 5, 2020 at 5:21 AM Brandon helsley 
wrote:

> I have re0 but the ip address is under wlan0 with my CenturyLink
>

In order to use vtnet and bridging (both required for bhyve networking) you
need to load the load the virtio kernel module as well as the if_tap and
vmm modules (the first one provides the host side of the virtual NIC and
the second loads the hypervisor components)

>
> Sent from Outlook Mobile
>
> 
> From: Robert Crowston 
> Sent: Tuesday, May 5, 2020 3:14:43 AM
> To: Brandon helsley ;
> freebsd-virtualization@freebsd.org 
> Subject: Re: Bhyve help
>
> What are your network interfaces called on your machine? You probably have
> to change igb0 in the example to em0 (an Intel card) or re0 (a Realtek
> card). Type “ifconfig” to list all the interfaces, and look for ones with
> an ip address to figure it out.
>
> On Tue, May 5, 2020 at 10:10, Brandon helsley  > wrote:
> I'm trying to set up bhyve like the example to learn and when doing the
> physical interface interface get the result no such file or directory the
> command is:
>
> ifconfig bridge0 addm igb0 addm tap0
>
> "In this example, the physical interface is igb0"
>
>
> Sent from Outlook Mobile
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570

[Aryeh Friedman]

On Mon, Apr 27, 2020 at 2:58 AM Anish  wrote:

> Hi Christian,
>
> This looks like BIOS issue, BIOS must not set Bit4/SVMDIS in VM_CR MSR
> (0xC001_0114) if SVM is enabled. Bhyve checks for this bit before
> enabling SVM. You can read it using the following steps:
> $kldload cpuctl
>
>
> $ cpucontrol -m 0xc0010114 /dev/cpuctlX <- Read VM_CR MSR
> MSR 0xc0010114: 0x 0x0008
>
> X is any CPU core number.
>

Again it is likely not a BIOS issues since the OP and me have nearly
identical setups (same MB manufacturer/same product line for both the CPU
and MB as well the same BIOS in most likely hood) and I get the following
(which works):

root@neomarx:~ # kldload cpuctl
root@neomarx:~ # cpucontrol -m 0xc0010114 /dev/cpuctl0
MSR 0xc0010114: 0x 0x0008

My BIOS: 7C02v1D 2019-11-11
OP BIOS: 7C35v18 2020-01-16

So if anything his should work and mine not work.

@OP do you have IOMMU support on or to auto (that is the one possible
setting you didn't state in your initial post -- mine is auto)



>
> On my AMD/Ryzen system, bit4 is clear and I can load bhyve. I have attached
> a screenshot from AMD SDM Vol2, which you may find useful.
>
> [image: Screen Shot 2020-04-26 at 12.01.14 PM.png]
>
> -Anish
>
>
>
> On Sun, Apr 26, 2020 at 6:27 AM Christian Jeannot 
> wrote:
>
> > I have checked MSI support page. The latest BIOS version is already
> > installed.
> >
> > Regards
> >
> > --Christian
> >
> > Am 26.04.20 um 15:11 schrieb M. Eisenhardt:
> > > I would suggest to update your bios.
> > > Kind regards
> > > Michael
> > >
> > >> Am 26.04.2020 um 14:00 schrieb
> > freebsd-virtualization-requ...@freebsd.org:
> > >>
> > >> Send freebsd-virtualization mailing list submissions to
> > >> freebsd-virtualization@freebsd.org
> > >>
> > >> To subscribe or unsubscribe via the World Wide Web, visit
> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > >> or, via email, send a message with subject or body 'help' to
> > >> freebsd-virtualization-requ...@freebsd.org
> > >>
> > >> You can reach the person managing the list at
> > >> freebsd-virtualization-ow...@freebsd.org
> > >>
> > >> When replying, please edit your Subject line so it is more specific
> > >> than "Re: Contents of freebsd-virtualization digest..."
> > >>
> > >>
> > >> Today's Topics:
> > >>
> > >>1. bhyve with AMD Ryzen 3900X and MSI MEG ACE X570
> > >>   (Christian Jeannot)
> > >>2. Re: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570
> > >>   (Aryeh Friedman)
> > >>3. Re: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570
> > >>   (Christian Jeannot)
> > >>
> > >>
> > >> --
> > >>
> > >> Message: 1
> > >> Date: Sun, 26 Apr 2020 10:57:50 +0200
> > >> From: Christian Jeannot 
> > >> To: freebsd-virtualization@freebsd.org
> > >> Subject: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570
> > >> Message-ID: <2535c7f2-ef59-467e-779b-6c9c6db82...@os-plus.org>
> > >> Content-Type: text/plain; charset=utf-8; format=flowed
> > >>
> > >> Hi Community,
> > >>
> > >> I am testing bhyve from FreeBSD 12.1 RELEASE.
> > >>
> > >> My environment:
> > >> - CPU: AMD Ryze 3900X
> > >> - Mainboard: MSI MEG ACE X570, Default settings, latest BIOS 7C35v18
> > >> - RAM: G.Skill RipJaws V DIMM Kit 64GB, DDR4-3200, CL16-18-18-38
> > >> - GPU: Sapphire Nitro RX 5700XT
> > >>
> > >> I checked the settings in the BIOS. Virtualization options are
> enabled.
> > >> SVM is enabled.
> > >>
> > >> I follow the instruction from the FreeBSD handbook ?21.7. FreeBSD as a
> > >> Host with bhyve?.
> > >>
> > >> When I run
> > >>  kldload vmm
> > >> I got an output that SVM is disabled by BIOS. When I check the BIOS it
> > >> is enabled.
> > >>
> > >> When I try to start the VM with the example script I got the output
> > >>  vm_create device not configured
> > >>
> > >> Did I miss something to configure?
> > >>
> > >> Does anyone has a Ryzen CPU and a actual MSI mainboard successfully
> run
> > >

Re: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570

[Aryeh Friedman]

On Sun, Apr 26, 2020 at 3:26 PM Anish  wrote:

> [Resending without screenshot to reduce message size]
>
> Hi Christian,
>
> This looks like BIOS issue, BIOS must not set Bit4/SVMDIS in VM_CR MSR
>

It is likely not a BIOS issue per se because I have a near identical setup
and the BIOS (AMI) set stuff correctly (default BIOS settings except for
turning on SVM)...
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: bhyve with AMD Ryzen 3900X and MSI MEG ACE X570

[Aryeh Friedman]

On Sun, Apr 26, 2020 at 4:57 AM Christian Jeannot  wrote:

> Hi Community,
>
> I am testing bhyve from FreeBSD 12.1 RELEASE.
>
> My environment:
> - CPU: AMD Ryze 3900X
> - Mainboard: MSI MEG ACE X570, Default settings, latest BIOS 7C35v18
> - RAM: G.Skill RipJaws V DIMM Kit 64GB, DDR4-3200, CL16-18-18-38
> - GPU: Sapphire Nitro RX 5700XT
>
> I checked the settings in the BIOS. Virtualization options are enabled.
> SVM is enabled.
>
> I follow the instruction from the FreeBSD handbook „21.7. FreeBSD as a
> Host with bhyve“.
>
> When I run
>  kldload vmm
> I got an output that SVM is disabled by BIOS. When I check the BIOS it
> is enabled.
>

What happens if you load it from /boot/load.conf

Also you shouldn't have to turn on kvm (I do have it turned on but it
should not be required).

Bhyve has a upper limit of 16 vm's that it can run at once but I don't
think this is based on core count of the processor.


> When I try to start the VM with the example script I got the output
>  vm_create device not configured
>
> Did I miss something to configure?
>
> Does anyone has a Ryzen CPU and a actual MSI mainboard successfully run
> bhyve?
>

I have two Ryzen 5 2600X/MSI machines as far I can tell looking at the
specs (and what I remember when I was deciding to get a 3900X or 2600X)
there is no practical difference, except for core count, from the point of
view of virtualization/bhyve.  One machine is a MSI B450 Tomahawk and the
other is MSI B450 Gaming Pro.   Both machines run bhyve with out any
problem (one of them is my main home office server with 3 vm's on it
[windows and 2 FreeBSD]) and the other is my primary desktop machine and
used for R on PetiteCloud (which is a web interface to bhyve and qemu).

Best regards
>
> —Christian
> --
> --
> christian jeannot
> vogelmauer 17
> 86152 augsburg
> +49 821 81552861
> i...@os-plus.org
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Running dual boot windows inside of bhyve

[Aryeh Friedman]

On Wed, Dec 27, 2017 at 11:17 AM, Joe Nosay <superbisq...@gmail.com> wrote:

> I'm curious as to why you would choose a lesser reliable system as the
> guest.
>

Since I have several other VM's also running on it (they are where I do the
torture testing of a webapp I maintain as well as browser compatibility
[the reason for win 7/IE 11.0 is the client's largest customer uses that
and *REFUSES* to upgrade/switch {doctors are even more stubborn then
programmers} to a better/newer browser/os).   Thus I often need to run two
VM's at once on it (one is a copy of FBSD that can repeately be blown up in
testing and the other is a copy of the OS we are having browser/client
issues with at the moment).



> The first thing you need to do is copy the partition to another drive.
>

Impractical since all bays are used.


> On Mon, Dec 25, 2017 at 7:12 PM, Aryeh Friedman <aryeh.fried...@gmail.com>
> wrote:
>
>> Cross posted to virtualization@, hackers@ and questions.
>>
>> I have a dual boot machine (windows 7 64 bit and fbsd 11.1-RELEASE
>> [amd64])
>> and want to run the windows partition as a vm in bhyve how would I go
>> about
>> this.   Bonus if the process is standalone scriptable so I can add it as a
>> feature of PetiteCloud.
>>
>> --
>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>> ___
>> freebsd-hack...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org
>> "
>>
>
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Running dual boot windows inside of bhyve

[Aryeh Friedman]

Cross posted to virtualization@, hackers@ and questions.

I have a dual boot machine (windows 7 64 bit and fbsd 11.1-RELEASE [amd64])
and want to run the windows partition as a vm in bhyve how would I go about
this.   Bonus if the process is standalone scriptable so I can add it as a
feature of PetiteCloud.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

VBox freezes on 11.0-RELEASE on a AMD processor

[Aryeh Friedman]

When I run vbox with windows 10 (install CD) and allocate 2 cores/4 GB (out
of 4 cores and 8 GB) it runs fine until some other non-trivial task (like
java or libreoffice) starts and then both vbox and the new task lock up (a
hard reboot is needed)

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Multiple bhyve Guests, Single bridge/tap?

[Aryeh Friedman]

On Thu, Dec 29, 2016 at 10:19 AM, Vincent Olivier  wrote:

> Hi!
>
> > Use the same bridge but a different tap (each tap represents the virtual
> equivalent of a NIC where the bridge is the virtual equivalent of a hub)
>
>
> Thanks! This is very clear. For extra isolation, could I use a new bridge
> too or is that useless?
>

Yes but it only makes sense in a multi-tenant (aka cloud provider) setup
because any attacker on a VM should be assumed to able to get into the host
due to knowing your password (which typically is not all that different on
the two machines unless you randomly generated it).

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Multiple bhyve Guests, Single bridge/tap?

[Aryeh Friedman]

On Thu, Dec 29, 2016 at 9:50 AM, Vincent Olivier  wrote:

> Hi,
>
> I have my first arch linux virtual machine running fine on FreeBSD 11. Now
> I want to make another one. Should I create a new bridge? A new tap too? It
> is not clear from the documentation if these steps are required for
> multiple guests on a single host…
>
>
Use the same bridge but a different tap (each tap represents the virtual
equivalent of a NIC where the bridge is the virtual equivalent of a hub)


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

11-STABLE guest under bhyve is unstable on a 11-STABLE host

[Aryeh Friedman]

After a month or so of experimenting with running 11-STABLE guests on a
11-STABLE host (upgraded from 10.3 host and guests) I have found that the
guests crash/freeze for no apparent reason (leaving no kernel panic log).
But if I do 10.3 guests on the 11-STABLE host it is very stable.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: svm/amd-v not working after upgrade from 10.3 to 11

[Aryeh Friedman]

Does not clear bit 4:

root@lilith:~ # kldunload vmm
kldunload: can't find file vmm
root@lilith:~ # kldload cpuctl
root@lilith:~ # cpucontrol -m 0xc0010114 /dev/cpuctl0
MSR 0xc0010114: 0x 0x0018
root@lilith:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl0
root@lilith:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl1
root@lilith:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl2
root@lilith:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl3
root@lilith:~ # cpucontrol -m 0xc0010114 /dev/cpuctl0
MSR 0xc0010114: 0x 0x0018


On Wed, Oct 26, 2016 at 12:46 AM, Anish Gupta <akgu...@gmail.com> wrote:

> You can give this a shot, doesn't look like it will work as per spec but I
> don't see any harm. Power cycling the system will clear all errors.
>
> Unload vmm
>
> $kldunload vmm
>
> $kldload cpuctl << To read/write MSR
>
> Check VM_CR MSR[0xC001_0114] MSR Bit4, must be clear.
>
> $cpucontrol -m 0xc0010114 /dev/cpuctl0
> MSR 0xc0010114: 0x 0x0008 << Bit4 clear on my AMD box
>
> If not, write to clear it.
>
> root@svmhost:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl0
>
> If you read and its changed, repeat on all cores.
>
> root@svmhost:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl1
> root@svmhost:~ # cpucontrol -m 0xc0010114=0x8 /dev/cpuctl2
> ...
>
> Now load vmm.ko module. If write was successful, SVM might work.
>
> Looks like its not possible to change bit4/SVMDIS of VM_CR,  as per APM2
>
>
>-
>
>SVMDIS—Bit 4. When this bit is set, writes to EFER treat the SVME bit
>as MBZ. When this bit is clear, EFER.SVME can be written normally. This bit
>does not prevent CPUID from reporting that SVM is available. Setting SVMDIS
>while EFER.SVME is 1 generates a #GP fault, regardless of the current state
>of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT
>when LOCK is cleared to 0; otherwise, it is not affected.
>
> -Anish
> On 10/25/16 7:37 PM, Aryeh Friedman wrote:
>
> On Tue, Oct 25, 2016 at 10:34 PM, Allan Jude <allanj...@freebsd.org> 
> <allanj...@freebsd.org> wrote:
>
>
> The file /var/run/dmesg.boot will have a copy of dmesg from when the
> machine booted.
>
>
>
> It was even smaller then normal dmesg output here is the file:
>
> root@lilith:/usr/src # more /var/run/dmesg.boot
> uhub7: 4 ports with 4 removable, self powered
> ugen1.3:  at usbus1
> ugen1.4:  at usbus1
> ukbd0 on uhub7
> ukbd0:  on usbus1
> kbd2 at ukbd0
> re0: link state changed to UP
> ums0 on uhub7
> ums0:  on usbus1
> ums0: 3 buttons and [XYZ] coordinates ID=0
>
>
>
>
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: svm/amd-v not working after upgrade from 10.3 to 11

[Aryeh Friedman]

On Tue, Oct 25, 2016 at 10:34 PM, Allan Jude  wrote:

>
> The file /var/run/dmesg.boot will have a copy of dmesg from when the
> machine booted.
>
>
It was even smaller then normal dmesg output here is the file:

root@lilith:/usr/src # more /var/run/dmesg.boot
uhub7: 4 ports with 4 removable, self powered
ugen1.3:  at usbus1
ugen1.4:  at usbus1
ukbd0 on uhub7
ukbd0:  on usbus1
kbd2 at ukbd0
re0: link state changed to UP
ums0 on uhub7
ums0:  on usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: svm/amd-v not working after upgrade from 10.3 to 11

[Aryeh Friedman]

For some reason dmesg is incomplete but here is what it does give me:

aryehl@lilith:/home/aryehl% dmesg
uhub7: 4 ports with 4 removable, self powered
ugen1.3:  at usbus1
ugen1.4:  at usbus1
ukbd0 on uhub7
ukbd0:  on usbus1
kbd2 at ukbd0
re0: link state changed to UP
ums0 on uhub7
ums0:  on usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0
interface hv_kvp.1 already present in the KLD 'kernel'!
linker_load_file: Unsupported file type
nvidia-modeset: Allocated GPU:0 (GPU-c309822d-608d-4d8a-6ab7-11d49570c3c6)
@ PCI::01:00.0
vboxdrv: 83434020 VMMR0.r0
ugen1.2:  at usbus1 (disconnected)
uhub7: at uhub5, port 3, addr 2 (disconnected)
ugen1.3:  at usbus1 (disconnected)
ums0: at uhub7, port 1, addr 3 (disconnected)
ums0: detached
ugen1.4:  at usbus1 (disconnected)
ukbd0: at uhub7, port 4, addr 4 (disconnected)
ukbd0: detached
uhub7: detached
ugen1.2:  at usbus1
uhub7 on uhub5
uhub7:  on
usbus1
uhub7: 4 ports with 4 removable, self powered
ugen1.3:  at usbus1
ums0 on uhub7
ums0:  on usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen1.4:  at usbus1
ukbd0 on uhub7
ukbd0:  on usbus1
kbd2 at ukbd0
ugen1.3:  at usbus1 (disconnected)
ums0: at uhub7, port 1, addr 3 (disconnected)
ums0: detached
ugen1.3:  at usbus1
ums0 on uhub7
ums0:  on usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0


On Tue, Oct 25, 2016 at 3:31 PM, Anish <akgu...@gmail.com> wrote:

> Please share dmesg output. I have not run into this, will give you some
> patch to try.
>
> -Anish
>
> Sent from my iPhone
>
> > On Oct 24, 2016, at 9:00 PM, Aryeh Friedman <aryeh.fried...@gmail.com>
> wrote:
> >
> > After I did a clean install of 11 on a machine, HP Pavilion p7-1234, that
> > used to have 10.3 on it vmm and virtualbox both claim that svm/amd-v are
> > turned off in the BIOS.   The BIOS has no settings for virtualization
> (and
> > no BIOS upgrades are available from HP).
> >
> > How do I force svm/amd-v to be used?
> >
> > --
> > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
> > ___
> > freebsd-virtualization@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "freebsd-virtualization-
> unsubscr...@freebsd.org"
>



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

svm/amd-v not working after upgrade from 10.3 to 11

[Aryeh Friedman]

After I did a clean install of 11 on a machine, HP Pavilion p7-1234, that
used to have 10.3 on it vmm and virtualbox both claim that svm/amd-v are
turned off in the BIOS.   The BIOS has no settings for virtualization (and
no BIOS upgrades are available from HP).

How do I force svm/amd-v to be used?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

does FreeBSD 10.3 bhyve support windows guests?

[Aryeh Friedman]

Or is this support only in -CURRENT?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

odd output from bhyve

[Aryeh Friedman]

/tmp/bhyve.WwKTaeP 84:   Name (PPRT, Package ()
   Remark   2095 -
Effective AML package length is zero ^


   vm_run error -1, errno 6


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: odd output from bhyve

[Aryeh Friedman]

PetiteCloud generated it I took it off for debugging reasons (same
error with or without)

On Sat, Apr 4, 2015 at 3:24 PM, Allan Jude allanj...@freebsd.org wrote:
 On 2015-04-04 15:04, Aryeh Friedman wrote:
 FreeBSD prometheus 10.1-RELEASE-p8 FreeBSD 10.1-RELEASE-p8 #0 r281026:
 Fri Apr  3 14:24:14 EDT 2015
 root@prometheus:/usr/obj/usr/src/sys/GENERIC  amd64



 #!/bin/sh
 #
 # Generated by PetiteCloud 0.2.6
 #

 ifconfig tap56 destroy
 ifconfig tap56 create
 ifconfig tap56 up
 sleep 5
 ifconfig bridge0 addm tap56 up
 bhyvectl --destroy --vm=hjtm24l65
 /usr/sbin/bhyveload -m 4096 -d /data/pri/4miq904k2q hjtm24l65
 /usr/sbin/bhyve -c 2 -m 4096 -AI -H -P -g 0 -s 0:0,hostbridge -s
 1,virtio-net,tap56 -s 2,virtio-blk,/data/pri/4miq904k2q  -s 31,uart
 hjtm24l65
 echo $!/var/run/petitecloud/hjtm24l65

 On Sat, Apr 4, 2015 at 1:02 PM, Allan Jude allanj...@freebsd.org wrote:
 On 2015-04-04 12:55, Aryeh Friedman wrote:
 /tmp/bhyve.WwKTaeP 84:   Name (PPRT, Package ()
Remark   2095 -
 Effective AML package length is zero ^


vm_run error -1, errno 6



 This was the output of what command? What version of FreeBSD?

 There is too much missing context here to help you with the error.

 --
 Allan Jude





 You are missing a space before the ampersand at the end of your bhyve
 invocation

 --
 Allan Jude




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: bhyve VM crashed

[Aryeh Friedman]

What was the guest OS?


On Tue, Apr 8, 2014 at 2:28 PM, Steve Wills swi...@freebsd.org wrote:

 Hi,

 I experienced a bhyve VM crash with this message:

 vm exit[1]
 reason  VMX
 rip 0x80c7490b
 inst_length 3
 status  0
 exit_reason 2
 qualification   0x
 inst_type   0
 inst_error  0

 Not sure what that means, anyone have any ideas? This VM is running FreeBSD
 10.0-RELEASE, 64bit. Let me know what other info would be helpful.

 Thanks,
 Steve

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

correctly putting all bhyve vm's on the same internal networtk

[Aryeh Friedman]

Setting up a ineternal network on the bridge nic seems to now allow guests
to communicate (see below for failed attempt transcript)

root@lilith:/tmp # ifconfig bridge0 192.168.0.1
...
Install an instance and put it on 192.168.0.2
...
Host:

root@lilith:/tmp # netstat -nr
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use  Netif Expire
default10.0.10.1  UGS 00re0
10.0.10.0/24   link#2 U   0   107642re0
10.0.10.20 link#2 UHS 00lo0
127.0.0.1  link#3 UH  04lo0
192.168.0.0/24 link#4 U   0  316 bridge
192.168.0.1link#4 UHS 0   68lo0
...

ral0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290
ether 20:10:7a:58:b9:29
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1500

options=82099RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE
ether e8:40:f2:97:38:d1
inet 10.0.10.20 netmask 0xff00 broadcast 10.0.10.255
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (1000baseT full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
1500
ether 02:66:19:ad:68:00
inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
nd6 options=1PERFORMNUD
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: tap8 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 6 priority 128 path cost 200
member: tap3 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 5 priority 128 path cost 200
member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 2 priority 128 path cost 2
tap3: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8LINKSTATE
ether 00:bd:1a:4b:06:03
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
media: Ethernet autoselect
status: no carrier
tap8: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1500
options=8LINKSTATE
ether 00:bd:65:09:16:08
inet6 fe80::2bd:65ff:fe09:1608%tap8 prefixlen 64 scopeid 0x6
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
media: Ethernet autoselect
status: active
Opened by PID 1362
root@lilith:/tmp # ifconfig
ral0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290
ether 20:10:7a:58:b9:29
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1500

options=82099RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE
ether e8:40:f2:97:38:d1
inet 10.0.10.20 netmask 0xff00 broadcast 10.0.10.255
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (1000baseT full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
1500
ether 02:66:19:ad:68:00
inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
nd6 options=1PERFORMNUD
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: tap8 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 6 priority 128 path cost 200
member: tap3 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 5 priority 128 path cost 200
member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
ifmaxaddr 0 port 2 priority 128 path cost 2
tap3: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8LINKSTATE
ether 00:bd:1a:4b:06:03
nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
media: Ethernet autoselect
status: no carrier
tap8: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1500
options=8LINKSTATE
ether 00:bd:65:09:16:08
inet6 fe80::2bd:65ff:fe09:1608%tap8 

Re: correctly putting all bhyve vm's on the same internal networtk

[Aryeh Friedman]

Forgot that net.inet.ip.forwarding=1


On Mon, Feb 24, 2014 at 8:20 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 Setting up a ineternal network on the bridge nic seems to now allow guests
 to communicate (see below for failed attempt transcript)

 root@lilith:/tmp # ifconfig bridge0 192.168.0.1
 ...
 Install an instance and put it on 192.168.0.2
 ...
 Host:

 root@lilith:/tmp # netstat -nr
 Routing tables

 Internet:
 DestinationGatewayFlagsRefs  Use  Netif Expire
 default10.0.10.1  UGS 00re0
 10.0.10.0/24   link#2 U   0   107642re0
 10.0.10.20 link#2 UHS 00lo0
 127.0.0.1  link#3 UH  04lo0
 192.168.0.0/24 link#4 U   0  316 bridge
 192.168.0.1link#4 UHS 0   68lo0
 ...

 ral0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290
 ether 20:10:7a:58:b9:29
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
 status: no carrier
 re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
 mtu 1500

 options=82099RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE
 ether e8:40:f2:97:38:d1
 inet 10.0.10.20 netmask 0xff00 broadcast 10.0.10.255
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
 media: Ethernet autoselect (1000baseT full-duplex)
 status: active
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
 inet6 ::1 prefixlen 128
 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
 inet 127.0.0.1 netmask 0xff00
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
 1500
 ether 02:66:19:ad:68:00
 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
 nd6 options=1PERFORMNUD
 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
 member: tap8 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 6 priority 128 path cost 200
 member: tap3 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 5 priority 128 path cost 200
 member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 2 priority 128 path cost 2
 tap3: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500
 options=8LINKSTATE
 ether 00:bd:1a:4b:06:03
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 media: Ethernet autoselect
 status: no carrier
 tap8: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
 mtu 1500
 options=8LINKSTATE
 ether 00:bd:65:09:16:08
 inet6 fe80::2bd:65ff:fe09:1608%tap8 prefixlen 64 scopeid 0x6
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 media: Ethernet autoselect
 status: active
 Opened by PID 1362
 root@lilith:/tmp # ifconfig
 ral0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290
 ether 20:10:7a:58:b9:29
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
 status: no carrier
 re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
 mtu 1500

 options=82099RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE
 ether e8:40:f2:97:38:d1
 inet 10.0.10.20 netmask 0xff00 broadcast 10.0.10.255
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
 media: Ethernet autoselect (1000baseT full-duplex)
 status: active
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6
 inet6 ::1 prefixlen 128
 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
 inet 127.0.0.1 netmask 0xff00
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL
 bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
 1500
 ether 02:66:19:ad:68:00
 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
 nd6 options=1PERFORMNUD
 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
 member: tap8 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 6 priority 128 path cost 200
 member: tap3 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 5 priority 128 path cost 200
 member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
 ifmaxaddr 0 port 2 priority 128 path cost 2
 tap3: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500
 options=8LINKSTATE
 ether 00:bd:1a:4b:06:03
 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL

Re: Bhyve and booting a ZFS-on-root system

[Aryeh Friedman]

On Sun, Feb 23, 2014 at 9:57 AM, Craig Rodrigues rodr...@crodrigues.orgwrote:

 On Feb 23, 2014 2:59 AM, Willem Jan Withagen w...@digiware.nl wrote:
 
 
 
  Op 22 feb. 2014 om 22:28 heeft Craig Rodrigues rodr...@freebsd.org het
 volgende geschreven:
 
  On Sat, Feb 22, 2014 at 12:16 PM, Willem Jan Withagen w...@digiware.nl
 wrote:
 
  Hi,
 
  Just for the fun of it, I tried my build zfs-system scripts in a
 bhyve-vm.
 
  I use the 10.0-RELEASE iso to get to a shell, config and interface and
  download my script. Installing does work, and on a regular system we
 can
  go and boot into a ZFS-on-Root system.
 
 
  ZFS on Root inside a BHyve VM was not working until
  today.  If you you have a FreeBSD-CURRENT system and then update
  to this revision:
 
 http://lists.freebsd.org/pipermail/svn-src-all/2014-February/081210.html
 
  then you can try it out.
 
 
  I'm running the amdsrc tree, so just upgrading current will probably not
 work.
  Peter suggested that he would upgrade the amdsrc-tree shortly.
  so I'll wait just for that.
 
  I'm also looking into running a Ubuntu vm. i want to test/use zoneminder,
 and all my FreeBSD attempts run into trouble.
  So I'm also still looking for grub-bhyve.

 grub2-bhyve is in ports: http://www.freshports.org/sysutils/grub2-bhyve/

 If you do a web search, you'll find several HOWTO articles for using it.
 Recently, Rudy wrote a nice one:

 http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-February/002305.html


Also keep in  mind most automation at this point is  nothing but generating
scripts designed for immediate use or user modifiction... (don't start with
our current ones because they are being debugged)... if you want a
scattered but very detailed discussion on what is required for these
scripts see
http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/001979.html
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and Ubuntu booting

[Aryeh Friedman]

 And I've seen discussions in other threads about reading/writing cpu
 registers where some bits should be 0, but trap when being set
 (Or something close to this...???)

 So it could again be due to the amdsrc tree differences?

 --WjW

 And again this is running on my AMD-board.
 /dev/zvol/zfsroot/ubuntu is a 10G zvol
 tap3 is created and up
 and ./ubuntu-13.10.iso is the ubuntu server ISO suggested by Rudy.


12.04.3 runs perfectly on the amd patch with no modification.  are you
setting up the device map dir correctly?


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and booting a ZFS-on-root system

[Aryeh Friedman]

You need a special branch of bhyve to work on AMD (see recent thread on the
topic)


On Sat, Feb 22, 2014 at 3:16 PM, Willem Jan Withagen w...@digiware.nlwrote:

 Hi,

 Just for the fun of it, I tried my build zfs-system scripts in a bhyve-vm.

 I use the 10.0-RELEASE iso to get to a shell, config and interface and
 download my script. Installing does work, and on a regular system we can
 go and boot into a ZFS-on-Root system.

 In bhyve I get the following, on reboot:
 -
 freetest# vmrun.sh -d test10zfs -t tap1 -m 2048 test10zfs
 Launching virtual machine test10zfs ...
 Consoles: userboot

 FreeBSD/amd64 User boot, Revision 1.1
 (r...@freetest.digiware.nl, Tue Feb 11 10:03:58 CET 2014)
 \
 can't load 'kernel'

 Type '?' for a list of commands, 'help' for more detailed help.
 OK
 --

 And there is no known way (to me) to educate the loader to understand
 zfs disks

 Which loader is is used in booting?
 a special bhyve-loader
 the bootloader in the boot-partition.

 It seems this is the first one.

 If so I'm wondering if the grub-bhyve would be a trick to boot the
 Root-on-ZFS system

 But then the first question is:
 where do I find grub-bhyve

 Any suggestion is welcome...

 BTW: this is on a AMD system.

 BTW2: I read that there could be interest for a dedicated opteron-server
 to do bhyve development on
 I'm more than willing to put my test server in a slot in our datacenter
 for people to do testing on.
 
 CPU: AMD Phenom(tm) II X6 1075T Processor (3013.84-MHz K8-class CPU)
   Origin = AuthenticAMD  Id = 0x100fa0  Family = 0x10  Model = 0xa
 Stepping = 0

 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
 Features2=0x802009SSE3,MON,CX16,POPCNT

 AMDFeatures=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!

 AMDFeatures2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT

 --WjW

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and booting a ZFS-on-root system

[Aryeh Friedman]

On Sat, Feb 22, 2014 at 4:43 PM, Craig Rodrigues rodr...@freebsd.orgwrote:

 On Sat, Feb 22, 2014 at 12:16 PM, Willem Jan Withagen w...@digiware.nl
 wrote:

 
  CPU: AMD Phenom(tm) II X6 1075T Processor (3013.84-MHz K8-class CPU)
Origin = AuthenticAMD  Id = 0x100fa0  Family = 0x10  Model = 0xa
 

 Also, as Aryeh has pointed out,
 you cannot run BHyve on an AMD processor unless you check out the
 code from a special branch.  Michael Dexter has provided a snapshot
 from the branch:


 http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-February/002227.html

 but that snapshot doesn't have the ZFS on Root change.


Even though I have not tried the patch looks compatible with SVM branch
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: bhyve AMD snapshot

[Aryeh Friedman]

Just to let people know destroying it does work... now I do not need to
test PC on a production host thanks (just saved hours or headache with
this about $2k in money)


On Thu, Feb 20, 2014 at 1:44 AM, Anish Gupta akgu...@gmail.com wrote:

 Hi Aryeh,

  You need to destroy the VM before creating  new one with same name,  so
 between bhyve and bhyveload, you should use bhyvectl --destroy --vm=vm
 name=t4n1ustl23. This fixed the problem Fatal trap 30: reserved (unknown)
 fault while in kernel mode which I was able to reproduce on my Phenom box.

 bhyveload.vm1
 bhyve.vm1
 ...
 bhyvectl --destroy --vm=vm1 
 bhyveload ...vm1
 bhyve.vm1
 

 Thanks for your help in testing bhyve_svm and bhyve.

 -Anish

 On Feb 17, 2014, at 8:27 PM, Aryeh Friedman aryeh.fried...@gmail.com
 wrote:

  Sorry for taking so long (forgot to say orginally this is the guest)
 
 
  On Wed, Feb 12, 2014 at 10:30 AM, Peter Grehan gre...@freebsd.org
 wrote:
 
  Hi Aryeh,
 
  kernel panic during boot
 
 
  Can you post a verbose boot log with the panic (i.e. boot -v from the
  loader prompt) ?OK boot -v
  Booting...
  SMAP type=01 base= len=000a
  SMAP type=01 base=0010 len=1ff0
  Table 'APIC' at 0xf0500
  APIC: Found table at 0xf0500
  APIC: Using the MADT enumerator.
  MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
  SMP: Added CPU 0 (AP)
  Copyright (c) 1992-2014 The FreeBSD Project.
  Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
  FreeBSD is a registered trademark of The FreeBSD Foundation.
  FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
  FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
  Preloaded elf kernel /boot/kernel/kernel at 0x817f2000.
  Hypervisor: Origin = bhyve bhyve 
  Calibrating TSC clock ... TSC clock: 2595069727 Hz
  CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.07-MHz K8-class
 CPU)
   Origin = AuthenticAMD  Id = 0x300f10  Family = 0x12  Model = 0x1
  Stepping = 0
 
 
 Features=0x783ab7fFPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2
   Features2=0x80a02001SSE3,CX16,x2APIC,POPCNT,HV
   AMD
 
 Features=0xe6505880s7,SYSCALL,s12,s14,NX,MMX+,FFXSR,Page1GB,LM,3DNow!+,3DNow!
   AMD
 
 Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT
   TSC: P-state invariant
  L1 2MB data TLB: 48 entries, fully associative
  L1 2MB instruction TLB: 16 entries, fully associative
  L1 4KB data TLB: 48 entries, fully associative
  L1 4KB instruction TLB: 32 entries, fully associative
  L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
  L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way
  associative
  L2 2MB data TLB: 128 entries, 2-way associative
  L2 2MB instruction TLB: 0 entries, 2-way associative
  L2 4KB data TLB: 1024 entries, 4-way associative
  L2 4KB instruction TLB: 1024 entries, 4-way associative
  L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way
  associative
  real memory  = 536870912 (512 MB)
  Physical memory chunk(s):
  0x1000 - 0x0009bfff, 634880 bytes (155 pages)
  0x0010 - 0x001f, 1048576 bytes (256 pages)
  0x0181a000 - 0x1f29, 497573888 bytes (121478 pages)
  avail memory = 492273664 (469 MB)
  Event timer LAPIC quality 400
  ACPI APIC Table: BHYVE  BVMADT  
  APIC: CPU 0 has ACPI ID 0
  x86bios:  IVT 0x00-0x0004ff at 0xf800
  x86bios: SSEG 0x001000-0x001fff at 0xfe002c174000
  x86bios:  ROM 0x0a-0x0fefff at 0xf80a
  XEN: CPU 0 has VCPU ID 0
  random device not loaded; using insecure entropy
  ULE: setup cpu 0
  ACPI: RSDP 0xf0400 00024 (v02 BHYVE )
  ACPI: XSDT 0xf0480 0003C (v01 BHYVE  BVXSDT   0001 INTL 20130823)
  ACPI: APIC 0xf0500 00054 (v01 BHYVE  BVMADT   0001 INTL 20130823)
  ACPI: FACP 0xf0600 0010C (v05 BHYVE  BVFACP   0001 INTL 20130823)
  ACPI: DSDT 0xf0800 0012F (v02 BHYVE  BVDSDT   0001 INTL 20130823)
  ACPI: FACS 0xf0780 00040
  ACPI: HPET 0xf0740 00038 (v01 BHYVE  BVHPET   0001 INTL 20130823)
  MADT: Found IO APIC ID 0, Interrupt 0 at 0xfec0
  ioapic0: Routing external 8259A's - intpin 0
  MADT: Interrupt override: source 0, irq 2
  ioapic0: Routing IRQ 0 - intpin 2
  MADT: Interrupt override: source 9, irq 9
  ioapic0: intpin 9 trigger: level
  ioapic0: intpin 9 polarity: low
  ioapic0 Version 1.1 irqs 0-23 on motherboard
  cpu0 BSP:
  ID: 0x   VER: 0x0011 LDR: 0x DFR: 0x
   lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff
   timer: 0x000100ef therm: 0x0001 err: 0x00f0
  wlan: 802.11 Link Layer
  snd_unit_init() u=0x00ff8000 [512] d=0x7c00 [32] c=0x03ff [1024]
  feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5

Re: Fwd: CFT: bhyve AMD snapshot

[Aryeh Friedman]

Sorry for taking so long (forgot to say orginally this is the guest)


On Wed, Feb 12, 2014 at 10:30 AM, Peter Grehan gre...@freebsd.org wrote:

 Hi Aryeh,

  kernel panic during boot


  Can you post a verbose boot log with the panic (i.e. boot -v from the
 loader prompt) ?OK boot -v
 Booting...
 SMAP type=01 base= len=000a
 SMAP type=01 base=0010 len=1ff0
 Table 'APIC' at 0xf0500
 APIC: Found table at 0xf0500
 APIC: Using the MADT enumerator.
 MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
 SMP: Added CPU 0 (AP)
 Copyright (c) 1992-2014 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
 FreeBSD is a registered trademark of The FreeBSD Foundation.
 FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
 Preloaded elf kernel /boot/kernel/kernel at 0x817f2000.
 Hypervisor: Origin = bhyve bhyve 
 Calibrating TSC clock ... TSC clock: 2595069727 Hz
 CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.07-MHz K8-class CPU)
   Origin = AuthenticAMD  Id = 0x300f10  Family = 0x12  Model = 0x1
 Stepping = 0

 Features=0x783ab7fFPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2
   Features2=0x80a02001SSE3,CX16,x2APIC,POPCNT,HV
   AMD
 Features=0xe6505880s7,SYSCALL,s12,s14,NX,MMX+,FFXSR,Page1GB,LM,3DNow!+,3DNow!
   AMD
 Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT
   TSC: P-state invariant
 L1 2MB data TLB: 48 entries, fully associative
 L1 2MB instruction TLB: 16 entries, fully associative
 L1 4KB data TLB: 48 entries, fully associative
 L1 4KB instruction TLB: 32 entries, fully associative
 L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
 L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way
 associative
 L2 2MB data TLB: 128 entries, 2-way associative
 L2 2MB instruction TLB: 0 entries, 2-way associative
 L2 4KB data TLB: 1024 entries, 4-way associative
 L2 4KB instruction TLB: 1024 entries, 4-way associative
 L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way
 associative
 real memory  = 536870912 (512 MB)
 Physical memory chunk(s):
 0x1000 - 0x0009bfff, 634880 bytes (155 pages)
 0x0010 - 0x001f, 1048576 bytes (256 pages)
 0x0181a000 - 0x1f29, 497573888 bytes (121478 pages)
 avail memory = 492273664 (469 MB)
 Event timer LAPIC quality 400
 ACPI APIC Table: BHYVE  BVMADT  
 APIC: CPU 0 has ACPI ID 0
 x86bios:  IVT 0x00-0x0004ff at 0xf800
 x86bios: SSEG 0x001000-0x001fff at 0xfe002c174000
 x86bios:  ROM 0x0a-0x0fefff at 0xf80a
 XEN: CPU 0 has VCPU ID 0
 random device not loaded; using insecure entropy
 ULE: setup cpu 0
 ACPI: RSDP 0xf0400 00024 (v02 BHYVE )
 ACPI: XSDT 0xf0480 0003C (v01 BHYVE  BVXSDT   0001 INTL 20130823)
 ACPI: APIC 0xf0500 00054 (v01 BHYVE  BVMADT   0001 INTL 20130823)
 ACPI: FACP 0xf0600 0010C (v05 BHYVE  BVFACP   0001 INTL 20130823)
 ACPI: DSDT 0xf0800 0012F (v02 BHYVE  BVDSDT   0001 INTL 20130823)
 ACPI: FACS 0xf0780 00040
 ACPI: HPET 0xf0740 00038 (v01 BHYVE  BVHPET   0001 INTL 20130823)
 MADT: Found IO APIC ID 0, Interrupt 0 at 0xfec0
 ioapic0: Routing external 8259A's - intpin 0
 MADT: Interrupt override: source 0, irq 2
 ioapic0: Routing IRQ 0 - intpin 2
 MADT: Interrupt override: source 9, irq 9
 ioapic0: intpin 9 trigger: level
 ioapic0: intpin 9 polarity: low
 ioapic0 Version 1.1 irqs 0-23 on motherboard
 cpu0 BSP:
  ID: 0x   VER: 0x0011 LDR: 0x DFR: 0x
   lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff
   timer: 0x000100ef therm: 0x0001 err: 0x00f0
 wlan: 802.11 Link Layer
 snd_unit_init() u=0x00ff8000 [512] d=0x7c00 [32] c=0x03ff [1024]
 feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5
 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25
 Hardware, Intel IvyBridge+ RNG: RDRAND is not present
 Hardware, VIA Nehemiah Padlock RNG: VIA Padlock RNG not present
 kbd0 at kbdmux0
 mem: memory
 null: null device, zero device
 nfslock: pseudo-device
 Falling back to Software, Yarrow random adaptor
 random: Software, Yarrow initialized
 module_register_init: MOD_LOAD (vesa, 0x80cfa5e0, 0) error 19
 io: I/O
 VMBUS: load
 hptnr: R750/DC7280 controller driver v1.0
 hpt27xx: RocketRAID 27xx controller driver v1.1
 hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2


 Fatal trap 30: reserved (unknown) fault while in kernel mode
 cpuid = 0; apic id = 00
 instruction pointer= 0x20:0x80d1d3af
 stack pointer= 0x28:0x817f6b10
 frame pointer= 0x28:0x817f6b40
 code segment= base 0x0, limit 0xf, type 

Re: emulators/petitecloud 0.2.1 available

[Aryeh Friedman]

Either apply the patch (see site) to a unmodified ports tree or move both
UIDs and GIDs from the port dir to /usr/ports  note the released 0.2.5
we had last night had a small but critical bug the current download fixes
it (0.2.6) [it was not possible to create instances with less then all 5
drives slots filled in] please direct ALL followups to this to
petitecloud-gene...@lists.petitecloud.nyclocal.net (the subscription link
is under resources on the site)


On Thu, Feb 13, 2014 at 2:50 PM, Jason Garrett kinged...@gmail.com wrote:

 Trying to build 0.2.5 via your instructions on petitecloud.org I get the
 following error during make install...

 === Creating users and/or groups.
 ** Cannot find any information about group `petitecloud' in
 /usr/ports/GIDs.
 *** Error code 1

 Stop.
 make: stopped in /usr/ports/emulators/petitecloud

 Any help is appreciated.


 On Wed, Jan 22, 2014 at 9:30 PM, Aryeh Friedman 
 aryeh.fried...@gmail.comwrote:

  This is correct behavior since there are no long lived processes all
  running the rc.d does is do some quick system wide inits needed to run
 vm's
  correctly (currently it loads vmm, if_tap and aio and also creates the
  bridge that vm's will be using).   This is true for all PetiteCloud
  commands, namely they do whatever action they need to perform and then
 die
  (no long living processes if you don't count the hyperv's or tomcat).
 
 
 Forgot to mention you will also need a cd image to install from that is
 kept in where ever your cdPrefix is (/vms/cds by default but settable in
 the settings screen or /usr/local/etc/petitecloud/settings.cfg)


 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org





-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

PetiteCloud 0.2.5 released

[Aryeh Friedman]

What's new:

* Ability to use physical disks as backing stores
* Multiple NIC's
* Multiple backing stores (1 primary and upto 5 secondary)
* Advanced settings


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Detect of BHyve VM was powered off or rebooted?

[Aryeh Friedman]

On Wed, Feb 12, 2014 at 4:28 AM, Craig Rodrigues rodr...@freebsd.orgwrote:

 On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu neeln...@gmail.com wrote:

 
  
  
  
   One question, if bhyve exits, do I have to call bhyveload again
 before
   calling bhyve?
 
  Yes, that is correct. You will also need to destroy the VM after bhyve
  exits.
 


 Why can't bhyve clean up after itself as the bhyve process exits
 and destroy the VM?

 It seems pointless to me for the user to have to explictly
 destroy the VM.  Once the bhyve process exits, I doesn't seem that I can
 use
 the VM again anyways.  To run the VM again, I seem to need to call:
   - bhyvectl to destroy the VM
   - bhyveload to load
   - bhyve to run the VM

 Aryeh has pointed out to me that it is the responsibility of the
 user to explictly destroy and tap and bridge devices used by the
 bhyve process after it exits.  Is this right?

 What if I have a  single bridge0 device, and 10 tap devices,
 one per VM?  If one VM exits and needs to be restarted, do
 I need to tear down all the taps and bridge?


Yes you do.   It gets really harry when you have multple vm's and taps per
instance that need to start and stop at arbitrary times.   We are currently
disccusing this issue on the petitecloud mailing list it might be off topic
here to get into too much detail.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Fwd: CFT: bhyve AMD snapshot

[Aryeh Friedman]

On Tue, Feb 11, 2014 at 7:08 PM, Peter Grehan gre...@freebsd.org wrote:

 Hi Aryeh,


root@:/home/aryeh # uname -a

 FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11
 03:19:01
 EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC  amd64


   This isn't the revision of the bhyve_svm branch - did you possibly do a
 sync before building this ?


 svn switch


  Would you be able to retry with a fresh checkout of the branch e.g.

 svn co svn://svn.freebsd.org/base/projects/bhyve_svm/ .

 later,



kernel panic during boot

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Detect of BHyve VM was powered off or rebooted?

[Aryeh Friedman]

On Wed, Feb 12, 2014 at 10:28 AM, Peter Grehan gre...@freebsd.org wrote:

  No - leave them there. Think of the tap interfaces as ports on a switch,
 and the bhyve processes as being plugged/unplugged from the ports.


Every time I have tried this it has lead to bricking the bridge if done in
the wrong order and/or there was a packet in transit on the bridge while
you have open end points

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: bhyve AMD snapshot

[Aryeh Friedman]

On Tue, Feb 11, 2014 at 3:07 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 It seems like the patch fails to acquire a DHCP address (or use the net in
 any other way with the following which works fine on intel):

 #!/bin/sh
 #
 # Generated by PetiteCloud 0.2.5
 #

 truncate -s 10G /vms/pri/nq6g103n9
 ifconfig tap1 destroy
 ifconfig tap1 create
 ifconfig tap1 up
 sleep 5
 ifconfig bridge0 addm tap1 up

 /usr/sbin/bhyveload -m 512 -d
 /vms/cds/FreeBSD-10.0-RELEASE-amd64-disc1.iso t4n1ustl23
 /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s
 1,virtio-net,tap1 -s 2,virtio-blk,/vms/pri/nq6g103n9 -s
 3,ahci-cd,/vms/cds/FreeBSD-10.0-RELEASE-amd64-disc1.iso -S 31,uart,stdio
 t4n1ustl23
 echo $!/var/run/petitecloud/t4n1ustl23
 ifconfig tap1 destroy
 ifconfig tap1 create
 ifconfig tap1 up
 sleep 5
 ifconfig bridge0 addm tap1 up

 /usr/sbin/bhyveload -m 512 -d /vms/pri/nq6g103n9 t4n1ustl23
 /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s
 1,virtio-net,tap1 -s 2,virtio-blk,/vms/pri/nq6g103n9  -S 31,uart,stdio
 t4n1ustl23
 echo $!/var/run/petitecloud/t4n1ustl23


Booting...
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.08-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x300f10  Family = 0x12  Model = 0x1
Stepping = 0

Features=0x783ab7fFPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2
  Features2=0x80a02001SSE3,CX16,x2APIC,POPCNT,HV
  AMD
Features=0xe6505880s7,SYSCALL,s12,s14,NX,MMX+,FFXSR,Page1GB,LM,3DNow!+,3DNow!
  AMD
Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT
  TSC: P-state invariant
real memory  = 536870912 (512 MB)
avail memory = 492273664 (469 MB)
Event timer LAPIC quality 400
ACPI APIC Table: BHYVE  BVMADT  
random device not loaded; using insecure entropy
ioapic0 Version 1.1 irqs 0-23 on motherboard
kbd0 at kbdmux0
random: Software, Yarrow initialized
module_register_init: MOD_LOAD (vesa, 0x80cfa5e0, 0) error 19


Fatal trap 30: reserved (unknown) fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer= 0x20:0x80d1d3af
stack pointer= 0x28:0x817f6b10
frame pointer= 0x28:0x817f6b40
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process= 0 (swapper)
trap number= 30
panic: reserved (unknown) fault
cpuid = 0
KDB: stack backtrace:
#0 0x808e7dd0 at kdb_backtrace+0x60
#1 0x808af8b5 at panic+0x155
#2 0x80c8e692 at trap_fatal+0x3a2
#3 0x80c8e2cf at trap+0x7bf
#4 0x80c75392 at calltrap+0x8
#5 0x80d1e59e at vmbus_identify+0xe
#6 0x808e02d7 at bus_generic_probe+0x77
#7 0x80c7314a at nexus_acpi_attach+0x1a
#8 0x808df242 at device_attach+0x3a2
#9 0x808e07b9 at bus_generic_new_pass+0xe9
#10 0x808dd0af at bus_set_pass+0x8f
#11 0x80c7472a at configure+0xa
#12 0x80861238 at mi_startup+0x118
#13 0x802d3e0c at btext+0x2c
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...

Host:

root@:/home/aryeh # uname -a
FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01
EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC  amd64

CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.33-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x300f10  Family = 0x12  Model = 0x1
Stepping = 0

Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x802009SSE3,MON,CX16,POPCNT
  AMD
Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!
  AMD
Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 7732641792 (7374 MB)
Event timer LAPIC quality 400
ACPI APIC Table: HPQOEM SLIC-CPC
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

CFT: PetiteCloud 0.2.5

[Aryeh Friedman]

Whats new:

* Ability to use physical disks as backing stores

* Multiple NIC's

* Advanced settings


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

reminder to PetiteCloud users

[Aryeh Friedman]

Please ask all issues related to PetiteCloud on our mailing list (on the
site)

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: bhyve AMD snapshot

[Aryeh Friedman]

On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter
edi...@callfortesting.orgwrote:


 I opted to build world with -j4 and kernel on -j2 on a dual-core system
 as per Glen Barber's suggestion of how he is building the official
 releases.


What, if anything, do the parameters to make world have to do with
***VIRTUALIZATION***?  Please keep your comments on the topic of this
list;-)   Namely the ***RESULTS*** of the test you asked people to
perform.
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Fwd: CFT: bhyve AMD snapshot

[Aryeh Friedman]

-- Forwarded message --
From: Aryeh Friedman aryeh.fried...@gmail.com
Date: Tue, Feb 11, 2014 at 7:04 PM
Subject: Re: CFT: bhyve AMD snapshot
To: Peter Grehan gre...@freebsd.org



 root@:/home/aryeh # uname -a
 FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01
 EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC  amd64


  This isn't the revision of the bhyve_svm branch - did you possibly do a
 sync before building this ?


svn switch


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: bhyve AMD snapshot

[Aryeh Friedman]

On Mon, Feb 10, 2014 at 8:50 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:



 On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter edi...@callfortesting.org
  wrote:


 Willem,

 On 2/10/14 7:14 AM, Willem Jan Withagen wrote:
  I usually prefer to build my onw. So I tried that from a both basic
  10-stable as well as the svn-url I got from Peter some time ago. But
  - building 10-stable did not give the amd svm stuff
  - building the previous svn-url on my 10-stable bombs out due to some
  missing net/ files. Need to rerun, to get the exact error.

 The snapshot was built from the SVM projects branch:

 http://svnweb.freebsd.org/base/projects/bhyve_svm/

 I opted to build world with -j4 and kernel on -j2 on a dual-core system
 as per Glen Barber's suggestion of how he is building the official
 releases.


 Attempting to install this right now will let you know how it goes.


Still setting things up but am noticing a significant number of lock
reversals on your branch in areas that have nothing to do with
virtualization (like building devel/subversion)

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Detect of BHyve VM was powered off or rebooted?

[Aryeh Friedman]

On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues rodr...@freebsd.org wrote:

 Hi,

 I posted some rc.d scripts that I am using to boot a BHyve VM
 and send the output to a serial console using the /dev/nmdm
 driver:


 http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html

 It works quite well.  There is some things I would like to improve,
 and would like some advice on the best way to do it.

 (1)  If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME},
   then I do not want to automatically restart the VM in the script.
   User should manually:  service bhyvevm start

 (2)  If the VM was powered down, via shutdown -p, or halt -p,
then in my script I do not want to restart the VM in the script.
User should manually:  service bhyvevm start

 (3)   If the VM was rebooted via reboot or shutdown -r,
then I *do* want the script to restart the VM.

 I think if I change my start_vm.sh script to do something like:



 (
  while [ -e /dev/vmm/${VM} ]; do
 /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc
 -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}
  done

 )  


 then this might cover cases (1) and (3), but what will cover
 case (2)?

 Thanks for any advice.


The options you gave (which are really the only ones available) do not
distinguish between the reason for the termination of the instance of bhyve
pointing to /dev/vmm/XXX  (it just does a normal termination).   In my
playing with this for almost a month the only solution seems to be put a
trigger on instance shutdown via whatever method to leave a cookie file
behind on the host (note I have not nor plan to do this in any of my own
work).  An other question is it wise to auto-reboot regardless of reason of
the hypervisor termination?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Detect of BHyve VM was powered off or rebooted?

[Aryeh Friedman]

On Sun, Feb 9, 2014 at 5:18 PM, Craig Rodrigues rodr...@freebsd.org wrote:




 On Sun, Feb 9, 2014 at 1:32 PM, Aryeh Friedman 
 aryeh.fried...@gmail.comwrote:




 On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues rodr...@freebsd.orgwrote:

 Hi,

 I posted some rc.d scripts that I am using to boot a BHyve VM
 and send the output to a serial console using the /dev/nmdm
 driver:


 http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html

 It works quite well.  There is some things I would like to improve,
 and would like some advice on the best way to do it.

 (1)  If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME},
   then I do not want to automatically restart the VM in the script.
   User should manually:  service bhyvevm start

 (2)  If the VM was powered down, via shutdown -p, or halt -p,
then in my script I do not want to restart the VM in the script.
User should manually:  service bhyvevm start

 (3)   If the VM was rebooted via reboot or shutdown -r,
then I *do* want the script to restart the VM.

 I think if I change my start_vm.sh script to do something like:



 (
  while [ -e /dev/vmm/${VM} ]; do
 /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s
 1:0,lpc
 -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A}
 ${VM}
  done

 )  


 then this might cover cases (1) and (3), but what will cover
 case (2)?

 Thanks for any advice.


 The options you gave (which are really the only ones available) do not
 distinguish between the reason for the termination of the instance of bhyve
 pointing to /dev/vmm/XXX  (it just does a normal termination).


 Did you play with any of these flags to bhyvectl?

[--get-vmcs-exit-ctls]
[--get-vmcs-exit-reason]
[--get-vmcs-exit-qualification]
[--get-vmcs-exit-interruption-info]

 If I do:
 bhyvectl --get-vmcs-exit-reason --vm vm1

 I get:
 vmcs_exit_reason[0] 0x001e

 If I look at:


 http://svnweb.freebsd.org/base/head/sys/amd64/vmm/intel/vmcs.h?view=markup#l310

 we have:
 #define EXIT_REASON_INOUT 30


You will likely need to detect the following ones also (all for different
reasons that may or may not have anything to do with an issue with the VM
instead of some host [OS or hardware] issue):

#define EXIT_REASON_EXT_INTR 1
#define EXIT_REASON_INIT 3
#define EXIT_REASON_HLT 12
#define EXIT_REASON_CPUID 10
#define EXIT_REASON_VMLAUNCH 20


 Linux has this stuff also:
 http://lxr.free-electrons.com/source/arch/x86/include/asm/vmx.h?v=3.1#L250

 so I guess these values are defined in some Intel manual.



 In my playing with this for almost a month the only solution seems to be
 put a trigger on instance shutdown via whatever method to leave a cookie
 file behind on the host (note I have not nor plan to do this in any of my
 own work).


 Yes, I can see why this might need to be done.  I might need to do that
 myself.  However, if bhyvectl can be used to provide adequate status
 information as to why the VM exited, I might be able to avoid this.

 It would be nicer though if /usr/sbin/bhyve returned
 the EXIT_REASON in its status code.




   An other question is it wise to auto-reboot regardless of reason of the
 hypervisor termination?


 I think the answer is it depends.  If someone
 does reboot or shutdown -r, I think it is reasonable to restart the
 VM.  If someone does halt -p or shutdown -p, I think it is reasonable
 to not restart the VM.  For any other error condition, I think it is
 reasonable to not restart the VM.

 I think that there is no  single answer for all users and all applications.
 In my case, I am running BHyve VM's as headless which
 I access via the /dev/nmdm driver.  If the VM reboots normally, I want it
 to restart.


It seems almost any boot failure would be host side for example if there is
no SSH access (which if the instance is never logged into then it is likely
a host issue) then it is highly unlikely the VM is in bootable form (this
is after a manual reboot of it)... an other reason (just learned the
hardway) is the user uses a mismatch between backing file formats (my case
using raw images with ahci-hd)
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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 size.


 But can I truncate an already existing image disk (downloaded nanobsd image
 as example) ?


You can increase the size but not lower it.   If your using raw format you
just scp it over and it will work fine. (bhyve only supports raw format)



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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


 The reported size would be identical so I don't see what the problem is.


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 use sparse allocation [i.e. attempting to read into the
middle with guest OS control will result in potentially seeing host data])


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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 in namely
 all you gain is a few seconds of startup time (matter of fact I think
 truncate might use sparse allocation [i.e. attempting to read into the
 middle with guest OS control will result in potentially seeing host data])


 If this is true then there is a *critical* security issue.

 Using sparse files isn't to gain performance, it's to conserve disk space.
  Using md devices backed by sparse images would accomplish this.  If the
 sparsify app works on FreeBSD, then there should be no problem using those
 type of volumes.


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?).   devel/qemu (not sure about -dev) uses qcow2 as a default and
when playing with it on other OS's I found that it seemed to default to
that also.  It is my understand that most of the open source cloud
platforms use qcow2 as their default also (I remember this from an attempt
to install openstack grizzly last summer... I have not checked havana
though... can any of the freebsd-openstack confirm this?).

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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 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 use sparse allocation [i.e. attempting to read into the
 middle with guest OS control will result in potentially seeing host data])


 If this is true then there is a *critical* security issue.

 Using sparse files isn't to gain performance, it's to conserve disk
 space.  Using md devices backed by sparse images would accomplish this.  If
 the sparsify app works on FreeBSD, then there should be no problem using
 those type of volumes.


 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?).   devel/qemu (not sure about -dev) uses qcow2 as a default and
 when playing with it on other OS's I found that it seemed to default to
 that also.  It is my understand that most of the open source cloud
 platforms use qcow2 as their default also (I remember this from an attempt
 to install openstack grizzly last summer... I have not checked havana
 though... can any of the freebsd-openstack confirm this?).


Forgot to mention that the host OS's disk scheduling also gives a brief
window of opportunity during the time after the inode is made and the old
contents wiped due to the size of the file


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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 aryeh.fried...@gmail.com
  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 use sparse allocation [i.e. attempting to read into
 the middle with guest OS control will result in potentially seeing host
 data])


 If this is true then there is a *critical* security issue.

 Using sparse files isn't to gain performance, it's to conserve disk
 space.  Using md devices backed by sparse images would accomplish this.  If
 the sparsify app works on FreeBSD, then there should be no problem using
 those type of volumes.


 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?).   devel/qemu (not sure about -dev) uses qcow2 as a default and
 when playing with it on other OS's I found that it seemed to default to
 that also.  It is my understand that most of the open source cloud
 platforms use qcow2 as their default also (I remember this from an attempt
 to install openstack grizzly last summer... I have not checked havana
 though... can any of the freebsd-openstack confirm this?).


 Forgot to mention that the host OS's disk scheduling also gives a brief
 window of opportunity during the time after the inode is made and the old
 contents wiped due to the size of the file


My short memory must be going the main point I meant to make in the second
reply is as far I know *ALL* hypervisors have the same blind read/write
(remember they see what ever is acting as the disk as (from the VM's POV) a
real disk and in order to maintain that illusion blind writes/reads are
necessary)
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[Aryeh Friedman]

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 aryeh.fried...@gmail.com
  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?).   devel/qemu (not sure about -dev) uses qcow2 as a
 default and when playing with it on other OS's I found that it seemed to
 default to that also.  It is my understand that most of the open source
 cloud platforms use qcow2 as their default also (I remember this from an
 attempt to install openstack grizzly last summer... I have not checked
 havana though... can any of the freebsd-openstack confirm this?).


 I don't consider it a huge win because the possibility of using an
 insecure device precludes it.  Someone high on the tree bhyve needs to
 confirm or deny this otherwise it is unsafe to recommend bhyve
 or petitecloud.  No offense intended, I really hope it succeeds and will
 likely use it if it does.  I cannot use anything which leaves the host
 open.  I am also unclear on how bhyve bypasses GEOM which *should* prevent
 any of the symptoms discussed.


 The point was that raw has no issue and this is the default for both
 bhyve and petitecloud (to avoid certain list politics I didn't mention it
 by name before).   Sparse is the issue and thus qemu, openstack and
 cloudstack (as well as likely vbox) are a problem.


 Yes but bhyve *supports* other backing devices than raw correct?   Then
 this really bad.

 I don't want a politics game either, just saying you won't get adoption
 until security is clear.  I have no problem with you mentioning
 petitecloud.  Indeed I think you should but others may disagree.  In your
 opinion are ZVOL's a good option?


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 block device to be used (it is up to the host
admin how they want to attach it all petitecloud will need is a /dev/ entry
or a backing file [some remote storage solutions do present this way not
just disk image files])... we do not preannounce features normally but
since this is security related we felt it was important to answer with
specific plans (no specific due date though since that is our primary
reason for not preannouncing is avoiding missing promised dates)... long
term see the draft of a white paper I posted a week or so here


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Report of my virtual network lab migrated from virtualbox to bhyve

[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 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?).   devel/qemu (not sure about -dev) uses qcow2 as a default and
 when playing with it on other OS's I found that it seemed to default to
 that also.  It is my understand that most of the open source cloud
 platforms use qcow2 as their default also (I remember this from an attempt
 to install openstack grizzly last summer... I have not checked havana
 though... can any of the freebsd-openstack confirm this?).


 I don't consider it a huge win because the possibility of using an
 insecure device precludes it.  Someone high on the tree bhyve needs to
 confirm or deny this otherwise it is unsafe to recommend bhyve
 or petitecloud.  No offense intended, I really hope it succeeds and will
 likely use it if it does.  I cannot use anything which leaves the host
 open.  I am also unclear on how bhyve bypasses GEOM which *should* prevent
 any of the symptoms discussed.


 The point was that raw has no issue and this is the default for both bhyve
 and petitecloud (to avoid certain list politics I didn't mention it by name
 before).   Sparse is the issue and thus qemu, openstack and cloudstack (as
 well as likely vbox) are a problem.


I should say in all the sparse format cases I do not consider it a flaw
(per se) that they picked because if your not considering sceurity qcow2 is
a very good format.   If PetiteCloud had not started with bhyve as our
first hypervisor instead of say qemu it is almost certain we would of
fallen into the same trap.   It is easy to over look the obvious also like
for example until this thread I didn't see how image format could effect
security (assuming that it was not crypted of course)


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host)

[Aryeh Friedman]

On Thu, Feb 6, 2014 at 11:21 AM, Kurt Lidl l...@pix.net wrote:

1. We'll be creating our own mailing list as soon as we can solve these

technical issues:

a. Mailman (under apache22) seems to insist on being on port
 80.
 We have no machine that is on the public internet that has 80 not used by
 tomcat. Any ideas on how to fix this? (Both machines are at RootBSD and
 have 9.2-RELEASE on them.)


 This part is easy.

 You run a reverse proxy on your external IP address, and then you have
 it pass stuff for one virtual host to the server running tomcat,
 and have it pass requests for the mailman host to the server running
 apache22.

 Those servers could just be processes on the same machine, bound to
 different ports, or they could be complete virtual machines.  It's
 entirely up to you as to how to implement and run it to best serve
 your interests.


Due to scheduling reasons we decided to spin up a third instance at RootBSD
dedicated to mail and our non open source work.   We should have everything
set up and ready to go in the next few days. But since I am always looking
out for new tricks, thanks.


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host)

[Aryeh Friedman]

Michael Dexter wrote:

 Please hesitate before you write and determine if this is the

 correct list and your post is in accordance with the above

 policies.



   1.

   We still have not received any guidance on what sort of CFT's (if any)
   are allowed on -virtualization@ for open-source projects that aim to be
   FreeBSD ports.



   1.

   The actual message you were taking issue with above was primarily a
   public thanks to someone for giving us a possible solution to a problem we
   had. I also made the off-topic announcement you objected to for the
   purpose of updating the -virtualization@ list on our progress in
   creating our own alternative to using -virtualization@ as our preferred
   communication channel as requested by you and John Baldwin.


  and my personal favorite, a request for a bhyve developer to sign

 an NDA to see these.


 The NDA request was NOT posted on the -virtualization@ list; that was in a
private email from Aryeh Friedman to Peter Grehan and him alone, way back
in early August 2013. Peter immediately rejected all private communication
and directed Aryeh to post everything to the -virtualization@ list. We
concluded that Peter was right that everything should be open knowledge.


 Anyhow, we agree that -virtualization@ should not be the place for
discussion of cloud computing because it crosses so many disciplines it
does not fully fit into any currently-existing FreeBSD list. For that
reason, we again suggest making a -cloud@ list. Until then,
-virtualization@seems to us to be the closest-to-suitable option,
though far from a perfect
fit.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and network virtualization

[Aryeh Friedman]

On Wed, Feb 5, 2014 at 12:59 PM, Kevin Bowling kevin.bowl...@kev009.comwrote:

 Has anyone used VALE with bhyve yet?  It's in 10.0-RELEASE
 http://info.iet.unipi.it/~luigi/vale/


Just a general question on virtual network how encapsulatable (ability to
wrap standardized wrappers around them) to do the different things... the
reason for this is when I added the support for whatever networking
solution(s) we choose I want to add them in the same way we did hypervisors
(a stripped down plugin model [which will be expanded in future versions to
be more complete])... does anyone see any reason why this model could not
be used?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host)

[Aryeh Friedman]

On Wed, Feb 5, 2014 at 1:00 PM, John Baldwin j...@freebsd.org wrote:

 On Tuesday, February 04, 2014 09:55:13 AM Michael Dexter wrote:
  May I suggest you take this all to a personal blog?

 I agree.  You can use a blog on petitecloud.org if you wish, but the
 purpose
 of this list is discussing virtualization techniques FreeBSD supports
 including
 jails/vimage, hypervisors (bhyve), and accelerated guest support (e.g. Xen
 HVM
 and Hyper-V drivers).  An occasional note about petitecloud may be
 warranted,
 but the current volume is excessive.  Also, this list is not suitable for
 use
 as a support forum for a commercial product.  It is certainly appropriate
 for
 bug reports in the aforementioned list of topics (e.g. bhyve bugs or bhyve
 performance testing results) that may come out of downstream bug reports.



   1.

   We'll be creating our own mailing list as soon as we can solve these
   technical issues:

   a. Mailman (under apache22) seems to insist on being on port 80.
We have no machine that is on the public internet that has 80 not used by
tomcat. Any ideas on how to fix this? (Both machines are at RootBSD and
have 9.2-RELEASE on them.)

   b. The way our internal build system works, updating
petitecloud.org also triggers a snapshot release of PetiteCloud and it is
currently in a state that is not releasable (massive security issues on the
Linux end [FreeBSD has no such issues])

  2. You seem to be under the impression that PetiteCloud is a
commercial product. It is in fact 100% Free Open Source (BSD license) and
Open Knowledge. We do plan to sell products that are ENABLED by PetiteCloud
but are NOT REQUIRED by PetiteCloud in any way. (Thus there will be no
enterprise edition, secret sauce, high-priced training, etc.) Also we
eventually plan, once there is enough interest, to form a foundation on the
FreeBSD/Apache model and transfer PetiteCloud completely over to it. The
reason for this is that we do not see any honest way to make money from
PetiteCloud itself, but only from various types of products it enables. We
will also encourage anyone who wants to build products or open source (also
hopefully open knowledge) projects on top of PetiteCloud (even if they are
direct competitors of our commerical products)

  3. Yes the comments on why we now have support for a non-FreeBSD host
(as well as for FreeBSD, our preferred OS) really belong on a different
forum. Since we have not yet created said forum, for the temporary
technical reasons mentioned above, -virtualization@ seemed the only
appropriate place to post our announcement, since the actual announcement
was only a CFT and 100% of our users are FreeBSD.

  4. Currently the only available place to discuss cloud computing at
all on FreeBSD is -virtualization@. A -cloud@ list might make more sense if
there was one. We would strongly urge the creation of such a list, because
we consider FreeBSD to be, without question, the best operating system for
truly stable and robust cloud computing, and we would strongly encourage
the FreeBSD Foundation to emphasize this in its advocacy. In the meantime,
please note that PetiteCloud is not yet a full-fledged cloud platform, but
currently is little more than just a front end for various hypervisors
including bhyve (our preferred hypervisor

  5.. We would appreciate clarification on what kinds of announcements
are appropriate here. For example, we've been posting calls for testing of
new versions of PetiteCloud for almost five months with no objection from
anyone (except for an early question from Michael Dexter about how truly
open-source we were) until we added support for a non-FreeBSD host. May we
continue to post CFT's that contain FreeBSD-related issues (including
making sure we didn't break anything related to our FreeBSD support when
adding features required by other OS's).

 6. Since we purposely do not collect user email addresses at any point
in the download and/or install, we will have no other quick way, besides
-virtualization@ itself, to tell users where to ask questions about
PetiteCloud now that -virtualization@ is no longer the correct place to
send things. Thus we will need to make at least one more purely
administrative/support oriented post before the move is complete

 7. Miscellaneous

  a. We will sending the $50 we had offered to give someone on
-emulation@ to the FreeBSD foundation, earmarked for work on virtualization
and cloud computing. (The person to whom we offered the $50, for a solution
to a problem we had been struggling with, told us to keep it.)

 b. As soon the appropriate person at the FreeBSD foundation
contacts us, we will arrange to transfer freebsd-openstack.org to the
foundation, if the FreeBSD foundation desires to be in charge of such a
portal. We do want to keep editorial control until we can put a basic
content management system in place and populate it with some initial
content.
-- 
Aryeh M. Friedman, 

Re: Bhyve and network virtualization

[Aryeh Friedman]

On Wed, Feb 5, 2014 at 2:12 AM, Craig Rodrigues rodr...@freebsd.org wrote:

 On Sat, Feb 1, 2014 at 1:03 AM, Frédéric Alix frederic.a...@fredalix.com
 wrote:

  Now, i need a tool for build a virtual network, like crossbow in Illumos.
 

 Well, it is not a graphical tool, but if
 you are OK with doing things from the command-line,
 you can create a bridge network device and create
 tap interfaces for each BHyve VM.  Then inside your BHyve VM,
 you can use the vtnet driver (part of virtio) to access the network.


PC 0.3 is going to focus on networking we should have something simple (and
www text based) soon that will include this... Craig I will have some
questions in doing this (see my thoughts on storage)

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Current problem reports assigned to freebsd-virtualization@FreeBSD.org

[Aryeh Friedman]

By now we have made enough progress in runninng FB as a VM on FB why are we
still putting out devlopement instances for various providers.  Wouldn't it
be easier to just put the raw disk images up (as far I know these will work
with all frontend/hyperv [vmrun, petitecloud, raw hyperv calls, etc.]
except for openstack [which is not currently supported on FB])


On Mon, Feb 3, 2014 at 6:06 AM, FreeBSD bugmaster bugmas...@freebsd.orgwrote:

 Note: to view an individual PR, use:
   http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

 The following is a listing of current problems submitted by FreeBSD users.
 These represent problem reports covering all versions including
 experimental development code and obsolete releases.


 S Tracker  Resp.  Description

 
 o kern/165252  virtualization[vimage] [pf] [panic] kernel panics with
 VIMAGE and PF
 o kern/161094  virtualization[vimage] [pf] [panic] kernel panic with pf +
 VIMAGE wh
 o kern/160541  virtualization[vimage][pf][patch] panic: userret: Returning
 on td 0x
 o kern/160496  virtualization[vimage] [pf] [patch] kernel panic with pf +
 VIMAGE
 o kern/148155  virtualization[vimage] [pf] Kernel panic with PF + VIMAGE
 kernel opt
 a kern/147950  virtualization[vimage] [carp] VIMAGE + CARP = kernel crash
 s kern/143808  virtualization[pf] pf does not work inside jail

 7 problems total.

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: some interesting observations on the relative performance of kvm vs. bhyve

[Aryeh Friedman]

Note on cachemodes it seems to make very little real world difference in
which one you pick.


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

looking for a quick and dirty remote vnc solution

[Aryeh Friedman]

Use case:

1. I am out of the office (the entire office except for one petitelcoud
instance is behind a firewall) without any ability to poke holes (something
petitecloud will handle soon)

2. The way to install a non-bhyve hyperv instance (kvm in this case)

3. I am installing an QEMU instance (console via VNC) on one of the hosts
(behind the FW)

4. Is there any easy way to connect to the QEMU on the FW'ed host

P.S. Since it is pretty obvious that all my work is leading to Linux as a
host for PetiteCloud I will be releasing a very rough release (hand build
with warnings [but no outright errors]) for testing in an hour or so (over
the next few days I will  work on making it end user usable).   This way we
do not violate our no preannounce policy (the reason for this policy is we
have found in our consulting work that the minute you preannounce something
the client will insist on having it even if you decide it is a bad idea
before final release).

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

OT: How best to market FreeBSD's innate strengths as a cloud host?

[Aryeh Friedman]

After dealing with linux for the last few days the difference between it
and FreeBSD are glaring when it comes to suitability as a cloud the host OS
of a cloud node/host.   Most of these strengths come from it's
fundimentally sound design and design process.   Namely it is rock solid
because it was designed to be rock solid (linux can not say this).  This
rock solidiness is what is needed for a cloud host because it is often the
most likely point of failure in a cloud environment.

How do we best market this?   This might be just the route that FreeBSD as
a whole has been looking for to get onto the radar of Corporate America
upper management.  One way I see to start is turning
freebsd-openstack.orginto the portal we promised when we got it.
Right now the only content I
see for it is the series of tutorials I mentioned.   The only other thing I
can think of is a logo gallery of companies that use FreeBSD for cloud
computing like services (internally or externally) and/or provide them.
For example I think NetApp should be on the list (FNWE would be willing but
we don't think we are big enough yet to make any difference).

Any other content ideas?   Also it would be nice to know who all is using
FreeBSD for cloud computing so we can see how to populate logo gallery
(looking at the logs for petitecloud.org I see some *VERY* big names but am
wondering why some of them have not stepped forward)

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and network virtualization

[Aryeh Friedman]

On Sat, Feb 1, 2014 at 5:35 AM, Frédéric Alix frederic.a...@fredalix.comwrote:

 Few minutes ago i read this:


 http://www.freebsd.org/news/status/report-2013-10-2013-12.html#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail

 Hum... OpenContrail port .. :p
 I am not interesting by OpenStack but OpenContrail, of course !

 After a little search, i found this:
 http://opencontrail.org/opencontrail-weekly-meeting/
 https://blueprints.launchpad.net/opencontrail/+spec/freebsd-vrouter


I am also looking into this but I think you will find the FB has almost
everything you need right out of the box






-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and network virtualization

[Aryeh Friedman]

Just a small tip if your new to FreeBSD you might surprised that 90% of the
real action happens in mailling lists not web based things.   Namely
-virtualization@ is likely your best long term resource as you learn.


On Sat, Feb 1, 2014 at 5:44 AM, Frédéric Alix frederic.a...@fredalix.comwrote:

 | I am also looking into this but I think you will find the FB has almost
 everything you need right out of the box

 yes, you should right. I am reading the FB handbook and many blogs for
 learn how run *BSD
 After 13 years in Solaris world, it's a big change to me.
 I very like bhyve and the new iSCSI seem to be great too. The ZFS
 integration in FB is just perfect !
 One thing miss me in Solaris and OmniOS, the virtual network stack,
 Crossbow. But i'm sure after few days of studies, i'll be the most happy of
 sysadmin of the world :-D

 fax


 2014-02-01 Aryeh Friedman aryeh.fried...@gmail.com:

 
 
 
  On Sat, Feb 1, 2014 at 5:35 AM, Frédéric Alix 
 frederic.a...@fredalix.comwrote:
 
  Few minutes ago i read this:
 
 
 
 http://www.freebsd.org/news/status/report-2013-10-2013-12.html#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail
 
  Hum... OpenContrail port .. :p
  I am not interesting by OpenStack but OpenContrail, of course !
 
  After a little search, i found this:
  http://opencontrail.org/opencontrail-weekly-meeting/
  https://blueprints.launchpad.net/opencontrail/+spec/freebsd-vrouter
 
 
  I am also looking into this but I think you will find the FB has almost
  everything you need right out of the box
 
 
 
 
 
 
  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
 
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Bhyve and network virtualization

[Aryeh Friedman]

Just an example of this then I will be quiet and take my frustration out on
inanimate objects which what kind of hair brained unix like OS would not
come with a working C compiler (ubuntu does not come with one)


On Sat, Feb 1, 2014 at 7:41 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 I forgot how frustrating Linux can be (FB really spoils you) until just
 today when I started to really play with it for petitecloud development
 reasons instead of making cute toys like the how to install DevStack
 tutorial


 On Sat, Feb 1, 2014 at 7:33 AM, Frédéric Alix 
 frederic.a...@fredalix.comwrote:

 Yes, i saw this two days ago. I read it and take many notes.


 2014-02-01 Aryeh Friedman aryeh.fried...@gmail.com:

 Just a small tip if your new to FreeBSD you might surprised that 90% of
 the real action happens in mailling lists not web based things.   Namely
 -virtualization@ is likely your best long term resource as you learn.


 On Sat, Feb 1, 2014 at 5:44 AM, Frédéric Alix 
 frederic.a...@fredalix.com wrote:

 | I am also looking into this but I think you will find the FB has
 almost
 everything you need right out of the box

 yes, you should right. I am reading the FB handbook and many blogs for
 learn how run *BSD
 After 13 years in Solaris world, it's a big change to me.
 I very like bhyve and the new iSCSI seem to be great too. The ZFS
 integration in FB is just perfect !
 One thing miss me in Solaris and OmniOS, the virtual network stack,
 Crossbow. But i'm sure after few days of studies, i'll be the most
 happy of
 sysadmin of the world :-D

 fax


 2014-02-01 Aryeh Friedman aryeh.fried...@gmail.com:

 
 
 
  On Sat, Feb 1, 2014 at 5:35 AM, Frédéric Alix 
 frederic.a...@fredalix.comwrote:
 
  Few minutes ago i read this:
 
 
 
 http://www.freebsd.org/news/status/report-2013-10-2013-12.html#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail
 
  Hum... OpenContrail port .. :p
  I am not interesting by OpenStack but OpenContrail, of course !
 
  After a little search, i found this:
  http://opencontrail.org/opencontrail-weekly-meeting/
  https://blueprints.launchpad.net/opencontrail/+spec/freebsd-vrouter
 
 
  I am also looking into this but I think you will find the FB has
 almost
  everything you need right out of the box
 
 
 
 
 
 
  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
 
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org





 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

some interesting observations on the relative performance of kvm vs. bhyve

[Aryeh Friedman]

I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve
seems to be atleast 3 or 4 times faster with disk I/O then kvm using the
most stripped down command lines I can come up with.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: some interesting observations on the relative performance of kvm vs. bhyve

[Aryeh Friedman]

On Sat, Feb 1, 2014 at 10:16 PM, Peter Grehan gre...@freebsd.org wrote:

  I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve

 seems to be atleast 3 or 4 times faster with disk I/O then kvm using the
 most stripped down command lines I can come up with.


  I'm guessing that the default cache mode for qemu in that release is
 none. You may want to switch it to writeback, which is what bhyve does
 by default (it can be changed with AHCI, see bhyve(8)).


Is this also true of emulators/qemu (without kqemu)?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: some interesting observations on the relative performance of kvm vs. bhyve

[Aryeh Friedman]

On Sat, Feb 1, 2014 at 10:16 PM, Peter Grehan gre...@freebsd.org wrote:

  I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve

 seems to be atleast 3 or 4 times faster with disk I/O then kvm using the
 most stripped down command lines I can come up with.


  I'm guessing that the default cache mode for qemu in that release is
 none. You may want to switch it to writeback, which is what bhyve does
 by default (it can be changed with AHCI, see bhyve(8)).


Does this bring up the same power failure scenario issues mentioned in the
link you provided?It seems like the only way to get reasonable
performance is to be essentially unsafe in guest writes to the host disk?
A question does the ability of FreeBSD to be able to better handle power
failure in general better then linux (it seems like every time there is a
unscheduled reboot on linux it messes up)?   This seems to be at odds with
my personal observations of bhyve via petitecloud which I routinely very
abruptly start/stop (petitecloud's stop is nothing more then killing the
hyperv and any cleanup needed) and except for the occasional need for a
fsck have not had an issue.   But it does not seem to be at odds with
OpenStack's experience
http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_nova-disaster-recovery-process


  Lots of info on the web about Qemu block i/o cache modes e.g.


 http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaat%
 2Fliaatbpkvmguestcache.htm

 later,

 Peter.




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RFC: hyperv disk i/o performance vs. data integrity

[Aryeh Friedman]

Disclaimer: This is more of a thinking out loud then it is an definative
set of suggestions on the matter.   Also a cleaned up version of this will
likely become PetiteCloud's white paper on storage and disaster recovery.
I do not make any promises to when any of it might be implemented and/or if
it will be implemented in the manner described here.

Looking at the link Peter provided in an other thread:

http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaat%2Fliaatbpkvmguestcache.htm

I at first did my standard OpenStack got it wrong and PetiteCloud got it
right reaction to it.   I then read deeper and saw that every last
modethat offered reasonable performance also was considered to be
untrustworthy especially in the case of a power failure.   The one
exception seems to be if your going straight to physical disk then if you
can use none and get reasonable performance without the issues associated
with abrupt disconnects like power failure or the sudden death of the
hyperv process.

So it seems we are stuck with sucky disk performance.   That is until we
make an other interesting observation that TCP offers the guarantee of
never been more then a few packets out of sync and being 100% reliable if
the network is functioning properly.   At first it might not seem that a
network would ever be faster then disk.  We forget though that we are
talking virtualization and not real networks here so there is no reason why
we can not form networks between instances on the same host and no matter
how inefficent the packet drivers are they are surely faster then any disk
if we only consider transport on the host's motherboard and not between
hosts.

Craig Rodrigues and the FreeNAS team have done a fantastic job already (I
have not personally tried FreeNAS yet but I have heard nothing but good
things about it) and making it so it can run on a bhyve instance.   Given
that the following local machine only archicture might make sense to act as
a solution to the performance vs. safety problem in the hyperv's:


Host +-- Storage (both local and remote)
|
+-- FreeNAS instance (as little RAM and VCPU's as possible)
|
+-- Production instances

The FreeNAS node would distribute it's storage via iSCSI or the equiv.
Setting the rule that all primary iSCSI sessions/devices be local (in
case vs. on rack or somewhere else in the data center) would eliminate the
power failure nightmare that OpenStack seems to have
http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_nova-disaster-recovery-processwithout
killing performance (in many cases increasing it).   The reason is
it is not an issue since we isolated all the remote disk sessions to one
instance we have used the blast wall capability of virtualization.
Namely if FreeNAS blows up we just swap in an other FreeNAS instance with
the same devices attached and the using normal OS (host and guest)
facilities it should be trivial to reconnect the device to the guest (you
will just have to give up the idea of a session that outlives the devices
power cycle though) and do basic recovery.   Now that we have offloaded the
storage from the hyperv all the other aspects of backup/recovery can be
done using normal OS facilities instead of the cloud platform.

(Real) network storage will need to use a completely different model likely
though if you allow it to be passed to the guest OS.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

CFT: Procedure for installing DevStack on FreeBSD using PetiteCloud

[Aryeh Friedman]

Can people look at the instructions/tutorial on how to install DevStack on
FreeBSD at http://www.freebsd-openstack.org and let us know if anything is
confusing, misleading or just outright wrong in it? (Note the domain is
brand new so there might be some DNS jitter)


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Procedure for installing DevStack on FreeBSD using PetiteCloud

[Aryeh Friedman]

We are planning to make the domain it self (within the next few weeks) a) a
portal for everything openstack (or cloud related) on the *BSD's run by the
*COMMUNITY* not us [as it says on the petitecloud site and as asked about a
few days ago we want all communication about petitecloud and related
projects to be cared out on -virtualization@ with the evenual business goal
of turning both projects completely over to their respective communities
for maintaince, growth and evulation [see note]) and b) be a set of
tutorials I will be writing on how to make a complete open stack
installation [real and virtual] from the ground up without any need for
expensive training or other material from anyone [including us].

Note: Our business model calls for making both projects 100% open source
and getting as wide of community support for them as possible and we will
*NEVER* attempt to commercialize the purely open source parts of our work
and/or make any of our work dependent on any closed sourced software or
knowledge.   The reason for this is we plan to be making a set of
commerical products that depend on the type of cloud computing we see
petitecloud becoming but are *NOT* required for petitecloud to function at
it's full capabilities or is in any other way crippled.   To this end in
order to make petitecloud what we need it to be we need to get as much help
as we can from the community.   After all we are just two programmers
attempting to make a living compared to OpenStack that has almost all of
corporate america behind them


On Fri, Jan 31, 2014 at 3:51 AM, Kevin Bowling kevin.bowl...@kev009.comwrote:

 On 1/31/2014 1:20 AM, Aryeh Friedman wrote:

 Can people look at the instructions/tutorial on how to install DevStack on
 FreeBSD at http://www.freebsd-openstack.org and let us know if anything
 is
 confusing, misleading or just outright wrong in it? (Note the domain is
 brand new so there might be some DNS jitter)


 Um, this is thinly veiled marketing gimmick at best and domain squatting
 at worst.

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization-
 unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Procedure for installing DevStack on FreeBSD using PetiteCloud

[Aryeh Friedman]

 I agree as you are really installing devstack on ubuntu within petiteCloud.
 Also sending reply again as I forgot to reply all.


All good tutorials are basically how to take existing tools and combine
them into something new.   Also as far I know *NO ONE* [at least
publically] has ever gotten any OpenStack component to run on FreeBSD in
any form and thus we see this as a very useful PR trick (as you call it)
for the entire FreeBSD community not just us.
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: CFT: Procedure for installing DevStack on FreeBSD using PetiteCloud

[Aryeh Friedman]

We feel that openstack is not quiet robust enough to run out side of the
data center on bare metal.  Thus one of the potential uses of petitecloud
as we see it is as blast wall for when it does blow up.   It also allows
people who are studying for their OpenStack certification to have a machine
they can blow up over and over again.   We fully support native OpenStack
on FreeBSD and feel that all efforts in this area should move forward.  We
are offering the OpenStack community a way of doing experiments without
blowing real machines up.   Namely once they get what they want virtually
they will move it over to a native install that does not include
petirecloud.


On Fri, Jan 31, 2014 at 4:36 AM, Michał Dubiel m...@semihalf.com wrote:

 Aryeh,

 Actually we have already a working OpenStack on FreeBSD. More precisely
 the Nova compute node running directly on FreeBSD host, which spawns guest
 VMs using bhyve hypervisor. It is in very early stage and currently it uses
 our prototype bhyve driver for the Nova compute. We have been putting now
 some effort to bring the bhyve into Nova via libvirt library as it is
 strongly favored by the OpenStack community. We had some discussions with
 maintainers of the Nova component and they clearly suggested that the
 libvirt path is the one that can be eventually integrated into the Nova
 code. One of our colleagues is currently putting together a wiki page that
 will explain how to set it all up, it should be available soon. If you are
 also interested in bringing the OpenStack into the FreeBSD world, perhaps
 it would make a sense to join forces and make it happen sooner.

 Regards,
 Michal.


 On 31 January 2014 10:28, Aryeh Friedman aryeh.fried...@gmail.com wrote:

  I agree as you are really installing devstack on ubuntu within
 petiteCloud.
  Also sending reply again as I forgot to reply all.
 

 All good tutorials are basically how to take existing tools and combine
 them into something new.   Also as far I know *NO ONE* [at least
 publically] has ever gotten any OpenStack component to run on FreeBSD in
 any form and thus we see this as a very useful PR trick (as you call it)
 for the entire FreeBSD community not just us.
 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org





-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: ports/185362: [NEW PORT] emulators/petitecloud (resubmittal after many flaws fixed)

[Aryeh Friedman]

Looks like the formating got messed up you can always find the latest patch
at http://www.petitecloud.org/downloads/patch.tar.gz


On Fri, Jan 31, 2014 at 1:30 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 The following reply was made to PR ports/185362; it has been noted by
 GNATS.

 From: Aryeh Friedman aryeh.fried...@gmail.com
 To: bug-follo...@freebsd.org, aryeh.fried...@gmail.com,
 freebsd-virtualization@freebsd.org 
 freebsd-virtualization@freebsd.org
 Cc:
 Subject: Re: ports/185362: [NEW PORT] emulators/petitecloud (resubmittal
 after
  many flaws fixed)
 Date: Fri, 31 Jan 2014 13:22:03 -0500

  --047d7b6dcdcc2f576504f148407e
  Content-Type: multipart/alternative; boundary=047d7b6dcdcc2f576104f148407c

  --047d7b6dcdcc2f576104f148407c
  Content-Type: text/plain; charset=ISO-8859-1

  Attached is the final working copy of the patch (there have been about 30
  downloads without any complaints) please commit it

  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

  --047d7b6dcdcc2f576104f148407c
  Content-Type: text/html; charset=ISO-8859-1
  Content-Transfer-Encoding: quoted-printable

  div dir=3DltrAttached is the final working copy of the patch (there
 hav=
  e been about 30 downloads without any complaints) please commit itbr
 clear=
  =3Dalldivbr-- brdiv dir=3DltrAryeh M. Friedman, Lead
 Developer=
  , a href=3Dhttp://www.PetiteCloud.org; target=3D_blank
 http://www.Petit=
  eCloud.org/abr
  /div
  /div/div

  --047d7b6dcdcc2f576104f148407c--
  --047d7b6dcdcc2f576504f148407e
  Content-Type: text/plain; charset=US-ASCII; name=port-patch.txt
  Content-Disposition: attachment; filename=port-patch.txt
  Content-Transfer-Encoding: base64
  X-Attachment-Id: f_hr3s3ot20


  KioqIC9kZXYvbnVsbAlXZWQgSmFuIDI5IDIxOjM0OjUwIDIwMTQKLS0tIHNjcmFwL3BvcnQvcGtn

  LWRlc2NyCVdlZCBKYW4gMjkgMTk6NDA6NDAgMjAxNAoqKioqKioqKioqKioqKioKKioqIDAgKioq

  KgotLS0gMSwxNyAtLS0tCisgUGV0aXRlQ2xvdWQgaXMgYSBIeXBlclZpc29yIGZyb250ZW5kIGZv

  ciBCU0QuIEl0IGhhcyB0aGUgZm9sbG93aW5nIGZlYXR1cmVzOgorIAorICAgICAqIFN1cHBvcnQg

  Zm9yIGJoeXZlIGFuZCBRRU1VLgorIAorICAgICAqIEFueSB4ODYgT1MgYXMgYSBndWVzdCAodGVz

  dGVkIG9ubHkgb24gUUVNVSkKKyAKKyAgICAgKiBJbnN0YWxsLCBpbXBvcnQsIHN0YXJ0LCBzdG9w

  IGFuZCByZWJvb3QgaW5zdGFuY2VzIHNhZmVseSAoZ3Vlc3QgT1MgbmVlZHMgdG8gYmUgY29udHJv

  bGxlZCBpbmRlcGVuZGVudGx5KQorIAorICAgICAqIENsb25lLCBiYWNrdXAvZXhwb3J0LCBkZWxl

  dGUgc3RvcHBlZCBpbnN0YW5jZXMgMTAwJSBzYWZlbHkKKyAKKyAgICAgKiBLZWVwIHRyYWNrIG9m

  IGFsbCB5b3VyIGluc3RhbmNlcyBvbiBvbmUgc2NyZWVuCisgCisgICAgICogQWxsIHRyYW5zYWN0

  aW9ucyB0aGF0IGNoYW5nZSBpbnN0YW5jZSBzdGF0ZSBhcmUgcGFzc3dvcmQgcHJvdGVjdGVkIGF0

  IGFsbCBjcml0aWNhbCBzdGFnZXMKKyAKKyAgICAgKiBBIGdyb3dpbmcgbnVtYmVyIG9mIGdlbmVy

  YWwgcHVycG9zZSBhbmQgc3BlY2lhbGl6ZWQgaW5zdGFuY2VzL2FwcGxpY2F0aW9ucyBhcmUgYXZh

  aWxhYmxlIGZvciBQZXRpdGVDbG91ZAorIAorIFdXVzogaHR0cDovL3d3dy5wZXRpdGVjbG91ZC5v

  cmcKKioqIC9kZXYvbnVsbAlXZWQgSmFuIDI5IDIxOjM0OjUwIDIwMTQKLS0tIHNjcmFwL3BvcnQv

  cGtnLWluc3RhbGwJV2VkIEphbiAyOSAxOTo0MDo0MSAyMDE0CioqKioqKioqKioqKioqKgoqKiog

  MCAqKioqCi0tLSAxLDE3IC0tLS0KKyBlY2hvICcgJ3wgcHcgdXNlcm1vZCBwZXRpdGVjbG91ZCAt

  aCAwIDI+JjEKKyBwdyBsb2NrIHBldGl0ZWNsb3VkCisgcHcgZ3JvdXBtb2Qgd3d3IC1tIHBldGl0

  ZWNsb3VkCisgcHcgZ3JvdXBtb2Qgd2hlZWwgLW0gcGV0aXRlY2xvdWQKKyBwdyBncm91cG1vZCBw

  ZXRpdGVjbG91ZCAtbSB3d3cKKyBwdyBncm91cG1vZCB3aGVlbCAtbSB3d3cKKyBta2RpciAtcCAv

  dm1zL2NkcworIG1rZGlyIC1wIC92bXMvcHJpCisgbWtkaXIgLXAgL3Ztcy9pbXBvcnQKKyBta2Rp

  ciAtcCAvdm1zL3RtcAorIGNob3duIC1SIHBldGl0ZWNsb3VkOnBldGl0ZWNsb3VkIC92bXMKKyBt

  a2RpciAtcCAvdXNyL2xvY2FsL2V0Yy9wZXRpdGVjbG91ZC9jb3VudGVycworIGVjaG8gMCA+IC91

  c3IvbG9jYWwvZXRjL3BldGl0ZWNsb3VkL2NvdW50ZXJzL2luc3RhbmNlcy5jbnQKKyBjaG93biAt

  UiB3d3c6d3d3IC91c3IvbG9jYWwvZXRjL3BldGl0ZWNsb3VkCisgY2htb2QgNzc3IC91c3IvbG9j

  YWwvZXRjL3BldGl0ZWNsb3VkL2NvdW50ZXJzL2luc3RhbmNlcy5jbnQKKyBjaG1vZCAtUiA3Nzcg

  L3Ztcy8KKyBjaG1vZCA3NzcgL3ZtcwoqKiogL2Rldi9udWxsCVdlZCBKYW4gMjkgMjE6MzQ6NTAg

  MjAxNAotLS0gc2NyYXAvcG9ydC9NYWtlZmlsZQlXZWQgSmFuIDI5IDE5OjQwOjQzIDIwMTQKKioq

  KioqKioqKioqKioqCioqKiAwICoqKioKLS0tIDEsMTggLS0tLQorIENBVEVHT1JJRVM9ZGV2ZWwK

  KyBQT1JUTkFNRT1zcmMtcGV0aXRlY2xvdWQtYXJ5ZWgKKyBQT1JUVkVSU0lPTj0wLjIuMworIENP

  TU1FTlQ9YnVpbGRzeXN0ZW0KKyBMSUNFTlNFPUJTRAorIAorIE1BU1RFUl9TSVRFUz0gICBmdHA6

  Ly9mdHAucGV0aXRlY2xvdWQub3JnL3BldGl0ZWNsb3VkLzAuMi4zL2FyeWVoLworIAorIEJVSUxE

  X0RFUEVORFM9ICAke0xPQ0FMQkFTRX0vYmluL2Nvb2s6JHtQT1JUU0RJUn0vZGV2ZWwvY29vayBc

  CisgCQkke0xPQ0FMQkFTRX0vb3BlbmpkazcvYmluL2phdmE6JHtQT1JUU0RJUn0vamF2YS9vcGVu

  amRrNyBcCisgCQkke0xPQ0FMQkFTRX0vYXBhY2hlLXRvbWNhdC03LjAvYmluL2NhdGFsaW5hLnNo

  OiR7UE9SVFNESVJ9L3d3dy90b21jYXQ3IFwKKyAJCSR7TE9DQUxCQVNFfS9iaW4vcWVtdS1zeXN0

  ZW0teDg2XzY0OiR7UE9SVFNESVJ9L2VtdWxhdG9ycy9xZW11LWRldmVsIFwKKyAJCSR7TE9DQUxC

  QVNFfS9zYmluL2dydWItYmh5dmU6JHtQT1JUU0RJUn0vc3lzdXRpbHMvZ3J1YjItYmh5dmUKKyAK

  KyBVU0VSUz0gcGV0aXRlY2xvdWQgCisgR1JPVVBTPSBwZXRpdGVjbG91ZAorIAorIC5pbmNsdWRl

  IDxic2QucG9ydC5taz4KKioqIC9kZXYvbnVsbAlXZWQgSmFuIDI5IDIxOjM0OjUwIDIwMTQKLS0t

Re: best way to add www to wheel

[Aryeh Friedman]

So something like this in pkg-install?

cat -  EOF  /usr/local/etc/sudoers.d/petitecloud
Cmnd_Alias PETITECLOUD = /usr/sbin/service petitecloud stop,
/usr/sbin/service petitecloud start, /usr/sbin/service petitecloud restart
www ALL=(ALL) NOPASSWD: PETITECLOUD
EOF

note this will be 0.2.4 which I am planning some other changes for also
like making the petitecloud account and /usr/local/etc/rc.d optoinal and
will need to ask (on the right list this time ;-)) how to do that best


On Thu, Jan 30, 2014 at 5:00 AM, Lars Engels lars.eng...@0x20.net wrote:

 Am 2014-01-29 23:05, schrieb Aryeh Friedman:

  Only issue with that is when I asked a few months ago how to -ports@ how
 to
 make the port edit sudoers the idea was universally shot down (then it was
 to add it to do it for the default %WHEEL NOPASSWD entry and it was before
 petitecloud was password protected [it is this criticism that lead to the
 password protection in the first place)



 You can add a new file in /usr/local/etc/sudoers.d/
 No need to edit sudoers itself.

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization-
 unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: best way to add www to wheel

[Aryeh Friedman]

It was my understanding with staging that doing stuff like that was
officially discouraged


On Thu, Jan 30, 2014 at 5:40 AM, Lars Engels lars.eng...@0x20.net wrote:

 Am 2014-01-30 11:21, schrieb Aryeh Friedman:

  So something like this in pkg-install?

 cat -  EOF  /usr/local/etc/sudoers.d/petitecloud
 Cmnd_Alias PETITECLOUD = /usr/sbin/service petitecloud stop,
  /usr/sbin/service petitecloud start, /usr/sbin/service petitecloud
 restart
  www ALL=(ALL) NOPASSWD: PETITECLOUD
 EOF

 note this will be 0.2.4 which I am planning some other changes for
 also like making the petitecloud account and /usr/local/etc/rc.d
 optoinal and will need to ask (on the right list this time ;-)) how to
 do that best



 I'd rather create the file as files/petitecloud.in and manually install it
 with the post-install: target.





-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: best way to add www to wheel

[Aryeh Friedman]

Speaking of stuff being officially discouraged I want to move most of whats
in pkg-install back to where it should belong (pkg-plist) but don't know
enough plist syntax to do it


On Thu, Jan 30, 2014 at 6:04 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 It was my understanding with staging that doing stuff like that was
 officially discouraged


 On Thu, Jan 30, 2014 at 5:40 AM, Lars Engels lars.eng...@0x20.net wrote:

 Am 2014-01-30 11:21, schrieb Aryeh Friedman:

  So something like this in pkg-install?

 cat -  EOF  /usr/local/etc/sudoers.d/petitecloud
 Cmnd_Alias PETITECLOUD = /usr/sbin/service petitecloud stop,
  /usr/sbin/service petitecloud start, /usr/sbin/service petitecloud
 restart
  www ALL=(ALL) NOPASSWD: PETITECLOUD
 EOF

 note this will be 0.2.4 which I am planning some other changes for
 also like making the petitecloud account and /usr/local/etc/rc.d
 optoinal and will need to ask (on the right list this time ;-)) how to
 do that best



 I'd rather create the file as files/petitecloud.in and manually install
 it
 with the post-install: target.





 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

does grub-bhyve limit guest ram?

[Aryeh Friedman]

When I try to run a guest with 4G it fails but with 2GB it works

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Linux on BHyVe in 10.0-RELEASE

[Aryeh Friedman]

 I use bare grub-bhyve/bhyve/bhyvectl, wrapped in a shell script in the
 manner of vmrun.sh, although fitted to my needs, nothing special. I
 didn't have a chance to use petitecloud yet.


Got it worked out and after a fix a few other small bugs (like the webui
start/stop working inconsistently) I will post a version boots linux as a
guest (later tonight likely when I get back from work) as a CFT



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

best way to add www to wheel

[Aryeh Friedman]

I have the following line in my pkg-install:

pw groupmod wheel -m www

The reason is I have files that are created by a user account that also
gets made but are modified using it or tomcat... these particular files are
shell scripts that must run as root (they are for controlling bhyve and
other hyperv's as well as other rootly things like setting up and tarring
down nic's) keep in mind also since almost all user level commands
(including those that trigger rootly actions) are run via the web and that
the data (except actual web content) should not be owned by www

My gut says that the above while it works is almost certainly not the right
way to do it.
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: best way to add www to wheel

[Aryeh Friedman]

Cross post on purpose because people on -virtualization@ are likely more
familur with bhyve and it's requirements as well knowing what petitecloud
is and what it needs to do (the whole issue is without adding www to wheel
start/stop do not work from the webui)


On Wed, Jan 29, 2014 at 4:23 PM, Michael Dexter
edi...@callfortesting.orgwrote:


 Wrong mailing list?

 Michael

 On 1/29/14 1:20 PM, Aryeh Friedman wrote:
  I have the following line in my pkg-install:
 
  pw groupmod wheel -m www
 
  The reason is I have files that are created by a user account that also
  gets made but are modified using it or tomcat... these particular files
 are
  shell scripts that must run as root (they are for controlling bhyve and
  other hyperv's as well as other rootly things like setting up and tarring
  down nic's) keep in mind also since almost all user level commands
  (including those that trigger rootly actions) are run via the web and
 that
  the data (except actual web content) should not be owned by www
 
  My gut says that the above while it works is almost certainly not the
 right
  way to do it.
 

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: best way to add www to wheel

[Aryeh Friedman]

Only issue with that is when I asked a few months ago how to -ports@ how to
make the port edit sudoers the idea was universally shot down (then it was
to add it to do it for the default %WHEEL NOPASSWD entry and it was before
petitecloud was password protected [it is this criticism that lead to the
password protection in the first place)


On Wed, Jan 29, 2014 at 4:41 PM, Łukasz Wąsikowski luk...@wasikowski.netwrote:

 W dniu 2014-01-29 22:26, Aryeh Friedman pisze:

  Cross post on purpose because people on -virtualization@ are likely more
  familur with bhyve and it's requirements as well knowing what petitecloud
  is and what it needs to do (the whole issue is without adding www to
 wheel
  start/stop do not work from the webui)

 Use security/sudo, maybe with config similar to this this:

 Cmnd_Alias PETITECLOUD = /usr/sbin/service petitecloud stop,
 /usr/sbin/service petitecloud start, /usr/sbin/service petitecloud restart
 www ALL=(ALL) NOPASSWD: PETITECLOUD

 This way user www can run sudo /usr/sbin/service petitecloud
 (stop|start|restart) as root (and only those exact commands with those
 exact parameters). It's a little bit safer than your approach which is
 huge security hole.

 --
 best regards,
 Lukasz Wasikowski




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: best way to add www to wheel

[Aryeh Friedman]

Forgot to mention there are more then just those commands but the idea is
still valid (about 6 commands currently need to be setuid but the list may
grow)


On Wed, Jan 29, 2014 at 5:05 PM, Aryeh Friedman aryeh.fried...@gmail.comwrote:

 Only issue with that is when I asked a few months ago how to -ports@ how
 to make the port edit sudoers the idea was universally shot down (then it
 was to add it to do it for the default %WHEEL NOPASSWD entry and it was
 before petitecloud was password protected [it is this criticism that lead
 to the password protection in the first place)


 On Wed, Jan 29, 2014 at 4:41 PM, Łukasz Wąsikowski 
 luk...@wasikowski.netwrote:

 W dniu 2014-01-29 22:26, Aryeh Friedman pisze:

  Cross post on purpose because people on -virtualization@ are likely
 more
  familur with bhyve and it's requirements as well knowing what
 petitecloud
  is and what it needs to do (the whole issue is without adding www to
 wheel
  start/stop do not work from the webui)

 Use security/sudo, maybe with config similar to this this:

 Cmnd_Alias PETITECLOUD = /usr/sbin/service petitecloud stop,
 /usr/sbin/service petitecloud start, /usr/sbin/service petitecloud restart
 www ALL=(ALL) NOPASSWD: PETITECLOUD

 This way user www can run sudo /usr/sbin/service petitecloud
 (stop|start|restart) as root (and only those exact commands with those
 exact parameters). It's a little bit safer than your approach which is
 huge security hole.

 --
 best regards,
 Lukasz Wasikowski




 --
 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

using -virtualization@ as the preferred support channel for petitecloud?

[Aryeh Friedman]

We are in the process of updating PetiteCloud.org in preparation for our
upcoming release of 0.2.3 (which will include support for Linux as a guest,
though still with FreeBSD as the only host and bhyve the only hypervisor
that currently runs in hardware virtualization mode).  We're wondering if
it is ok if we update the resources page to say that all support questions
should go to -virtualization@?

We've already been doing this unofficially for quite some time, and
PetiteCloud does not currently have a large enough user base to justify a
mailing list of its own.  If/when questions about PetiteCloud become too
high volume here, we will then, of course, start our own mailing list.

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Linux on BHyVe in 10.0-RELEASE

[Aryeh Friedman]

Seems like it is a processor motherboard combo thing (see other thread)


On Sun, Jan 26, 2014 at 9:26 AM, Markiyan Kushnir 
markiyan.kush...@gmail.com wrote:

 yes, once I posted it I realized that these sysctls are not relevant
 at this stage.

 There was a segfault, was that bhyvectl? May be it makes sense for
 someone (a bhyve dev) to inspect it?

 --
 Markiyan.


 2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com:
 
 
 
  On Sun, Jan 26, 2014 at 8:46 AM, Markiyan Kushnir
  markiyan.kush...@gmail.com wrote:
 
  hmm...
 
  15:45:test-bhyve# md5 ubuntu-12.04.3-server-amd64.iso
  MD5 (ubuntu-12.04.3-server-amd64.iso) = 2cbe868812a871242cdcdd8f2fd6feb9
 
 
  # md5 ubuntu/ubuntu.iso
  MD5 (ubuntu/ubuntu.iso) = 2cbe868812a871242cdcdd8f2fd6feb9
 
  doing the sysctl does no good
 
  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: BHyVe - ESXi comparison

[Aryeh Friedman]

On Tue, Jan 28, 2014 at 11:10 AM, Peter Grehan gre...@freebsd.org wrote:

 Hi Andrea,


  We did a very rough comparison betweend BHyVe and VMWare ESXi. Maybe
 you want to give it a read and let me know if I did write a bunch of
 sh!t :-)


  Looks good to me :) Thanks for running the tests.

  Would you be able to list the command options you used with bhyve when
 running these tests ?

  What I couldn't really understand (but that's something not related
 to bhyve or VMWare) is how a multiprocessor machine is slower than a
 singleprocessor machine in doing the compilation... any idea?


  Is hyper-threading enabled on your system ? If not, then with a host only
 having 2 CPUs and a 2 vCPU guest, there isn't as much opportunity to
 overlap host i/o threads with vCPU threads.


Depends on how your setting up bhyve for example PetiteCloud limits it to
no more then a 1 to 1 ratio of real to virtual cpu (after playing with
something I will be posting about later today [me and Dee have the policy
of no pronouncements] I am seriously thinking making this n vcpu to 1 real
cpu... what do people think the best way to implement and the right ration
for this is...)


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: BHyVe - ESXi comparison

[Aryeh Friedman]

It would be interesting to know to how much and what extent various
fronends (openstack, cloudstack, petitecloud, etc.) effect performence... I
suspect that even though bhyve is slower then VMWare that VMWare's front
end is the cause and not VMWare itself for example I suspect that bhyve
with petitecloud on top would be much faster then vmware or qemu with
openstack or cloudstack.


On Tue, Jan 28, 2014 at 6:18 AM, Andrea Brancatelli 
abrancate...@schema31.it wrote:

 Hello everybody.

 We did a very rough comparison betweend BHyVe and VMWare ESXi. Maybe you
 want to give it a read and let me know if I did write a bunch of sh!t :-)


 http://andrea.brancatelli.it/2014/01/28/freebsd-10-0-bhyve-vmware-esxi-5-5-comparison/

 I must say I'm very pleased with BHyVe performances! Very good work!!

 Thanks for your time.

 --




 *Andrea BrancatelliSchema 31 S.r.l. - Socio UnicoResponsabile ITROMA -
 FIRENZE - PALERMO ITALYTel: +39. 06.98.358.472*

 *Cell: +39 331.2488468Fax: +39. 055.71.880.466Società del Gruppo SC31
 ITALIA*
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: BHyVe - ESXi comparison

[Aryeh Friedman]

I have observed Ubuntu 12.04 LTS runs faster as a VM under bhyve the in
does on bare metal (networking seems to be one of the key areas here as
well as disk access)


On Tue, Jan 28, 2014 at 9:57 AM, Lars Engels lars.eng...@0x20.net wrote:

 Am 2014-01-28 13:21, schrieb Andrea Brancatelli:

 Fixed, thanks.


 Could you also compare two instances of Linux inside bhyve and VMware?

 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization-
 unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Linux on BHyVe in 10.0-RELEASE

[Aryeh Friedman]

Where did you get the orignial starter script for this from was it from
vmrun or the petitecloud sample script I posted... 2 reasons for asking:

1. It is turning out to be annoying inflexible in-terms of the values of
various parameters (I can compensate for most of this in my personal
playing with it to make it fit into petitecloud)
2. It uses a non-existent option (-I)

Both are characterstics of petitecloud scripts but not so much of vmrun.sh
(the main reason I do not recommend using petitecloud scripts except as
nothing but barebone starter scripts if you use them to make your own).

The reason for bringing all the above up is I am having a very hard time
getting it to work and if it is from petitecloud can you please kindly walk
me through how you went from my script to yours... the main issue I am
attempting to over come is currently PC assumes that there is a single
disk that represents the instance (a running instance is nothing more
then loading it into RAM and wrapping a hyperv around it) [e.g. something
like /vms/import/ubu.img] and that it contains *ALL* the data that is
needed to boot (i.e. no other files are needed)... so far it appears (and I
hope I am wrong) there is no way to force a linux instance into this model
because you have to have the disk, the cd and the device map in the same
dir but kept as separate files namely something like this:

linux/
   device.map
   disk.img
   cd.img

seems to be the only model grub2-bhyve will be able to boot (symlinks at
least on the surface seem to be a no go also...)...  there are the
following problems with this model though when doing mass VM's:

* You have to copy the CD repeatedly to the boot dir (this is likely why
openstack does not support cd based installs)
* It makes for a really messy when attempting to make sure you completely
nuke a vm when you delete it (currently pettiecloud does not delete the
disk when the instance is deleted but this will be an option soon an likely
the default)


Of course the long term solution is unified off disk (vs. off loader)
booting but until then any good work arounds?


On Tue, Jan 28, 2014 at 6:23 AM, Markiyan Kushnir 
markiyan.kush...@gmail.com wrote:

 2014-01-28 Aryeh Friedman aryeh.fried...@gmail.com:
  Seems like it is a processor motherboard combo thing (see other thread)
 

 ah, ok. good to know :)

 --
 Markiyan.

 
  On Sun, Jan 26, 2014 at 9:26 AM, Markiyan Kushnir
  markiyan.kush...@gmail.com wrote:
 
  yes, once I posted it I realized that these sysctls are not relevant
  at this stage.
 
  There was a segfault, was that bhyvectl? May be it makes sense for
  someone (a bhyve dev) to inspect it?
 
  --
  Markiyan.
 
 
  2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com:
  
  
  
   On Sun, Jan 26, 2014 at 8:46 AM, Markiyan Kushnir
   markiyan.kush...@gmail.com wrote:
  
   hmm...
  
   15:45:test-bhyve# md5 ubuntu-12.04.3-server-amd64.iso
   MD5 (ubuntu-12.04.3-server-amd64.iso) =
   2cbe868812a871242cdcdd8f2fd6feb9
  
  
   # md5 ubuntu/ubuntu.iso
   MD5 (ubuntu/ubuntu.iso) = 2cbe868812a871242cdcdd8f2fd6feb9
  
   doing the sysctl does no good
  
   --
   Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
 
 
 
 
  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

petitecloud port files

[Aryeh Friedman]

I am thinking about making the final submission of the first port version
(ideally I would like to make it so a update PR is part of the automatic
release script) and need to know if anyone has had problems with installing
the one currently on peitecloud.org

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

strange behavior out of a supported bhyve CPU

[Aryeh Friedman]

CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (2998.33-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x306c3  Family = 0x6  Model = 0x3c
Stepping = 3

Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE

Features2=0x7ffafbbfSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND
  AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM
  AMD Features2=0x21LAHF,ABM
  Standard Extended
Features=0x27abGSFSBASE,TSCADJ,BMI1,AVX2,SMEP,BMI2,ENHMOVSB,INVPCID
  TSC: P-state invariant, performance statistics

#!/bin/sh

ifconfig tap9 destroy
ifconfig tap9 create
ifconfig tap9 up
sleep 5
ifconfig bridge0 addm tap9 up

/usr/sbin/bhyveload -m 512 -d /vms/import/backupInstance 8e2nt39puc
/usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s
1:0,virtio-net,tap9 -s 2:0,virtio-blk,/vms/import/backupInstance -S 31,uart
8e2nt39puc
echo $!/var/run/petitecloud/8e2nt39puc

  __      _ _
 |  | |  _ \ / |  __ \
 | |___ _ __ ___  ___ | |_) | (___ | |  | |
 |  ___| '__/ _ \/ _ \|  _  \___ \| |  | |
 | |   | | |  __/  __/| |_) |) | |__| |
 | |   | | |||| |  |  |
 |_|   |_|  \___|\___||/|_/|_/````
 s` `.---...--.```   -/
 +Welcome to FreeBSD---+ +o   .--` /y:`  +.
 | |  yo`:.:o  `+-
 |  1. Boot Multi User [Enter] |   y/   -/`   -o/
 |  2. Boot [S]ingle User  |  .-  ::/sy+:.
 |  3. [Esc]ape to loader prompt   |  / `--  /
 |  4. Reboot  | `:  :`
 | | `:  :`
 |  Options:   |  /  /
 |  5. Configure Boot [O]ptions... |  .--.
 | |   --  -.
 | |`:`  `:`
 | |  .-- `--.
 | | .---..
 +-+


Booting...
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-BETA2 #0 r257166: Sat Oct 26 19:23:22 UTC 2013
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (2998.05-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x306c3  Family = 0x6  Model = 0x3c
Stepping = 3

Features=0x8f83ab7fFPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,PBE

Features2=0xe2fa7a17SSE3,PCLMULQDQ,DTES64,DS_CPL,SSSE3,b11,FMA,CX16,xTPR,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AESNI,F16C,RDRAND,HV
  AMD Features=0x24100800SYSCALL,NX,Page1GB,LM
  AMD Features2=0x21LAHF,ABM
  Standard Extended Features=0x400INVPCID
  TSC: P-state invariant
real memory  = 536870912 (512 MB)
avail memory = 492277760 (469 MB)
Event timer LAPIC quality 400
ACPI APIC Table: BHYVE  BVMADT  
random device not loaded; using insecure entropy
ioapic0 Version 1.1 irqs 0-23 on motherboard
kbd0 at kbdmux0
random: Software, Yarrow initialized
module_register_init: MOD_LOAD (vesa, 0x80cf9cf0, 0) error 19
acpi0: BHYVE BVXSDT on motherboard
acpi0: Power Button (fixed)
atrtc0: AT realtime clock port 0x70-0x71,0x72-0x77 irq 8 on acpi0
Event timer RTC frequency 32768 Hz quality 0
hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 1000 Hz quality 950
Event timer HPET frequency 1000 Hz quality 550
Event timer HPET1 frequency 1000 Hz quality 450
Event timer HPET2 frequency 1000 Hz quality 450
Event timer HPET3 frequency 1000 Hz quality 450
Event timer HPET4 frequency 1000 Hz quality 450
Event timer HPET5 frequency 1000 Hz quality 450
Event timer HPET6 frequency 1000 Hz quality 450
Event timer HPET7 frequency 1000 Hz quality 450
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 32-bit timer at 3.579545MHz port 0x408-0x40b on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib0: no PRT entry for 0.31.INTA
virtio_pci0: VirtIO PCI Network adapter port 0x2000-0x201f mem
0xc000-0xc0001fff at device 1.0 on pci0
vtnet0: VirtIO Networking Adapter on virtio_pci0
virtio_pci0: host features: 0x1018020
NotifyOnEmpty,Status,MrgRxBuf,MacAddress

Re: Linux on BHyVe in 10.0-RELEASE

[Aryeh Friedman]

On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir 
markiyan.kush...@gmail.com wrote:

 2014/1/26 Aryeh Friedman aryeh.fried...@gmail.com:
  mkdir ubuntu
  ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
  create the file ubuntu/device.map with the following content (2 lines):
  (hd0) ./ubuntu/ubuntu.img
  (cd0) ./ubuntu/ubuntu.iso
 
  truncate -s 8G ubuntu/ubuntu.img
 
  grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu


I narrowed it down to this line.. namely any time I touch the cd it does
that weird staff... btw it also seg faults if you type anything... I am
using 12.04.3 LTS


 Aryeh, could you please clarify what did you do and what you wanted to
 achieve (is your screen shot an X session?). I managed to successfully
 install and run Ubuntu Server 13.10 as a bhyve instance as Jonas
 described, without X of course.

 Aside form that, I found that disk partitioning with LVM (one of
 options during Ubuntu install) didn't work for me.

 --
 Markiyan.

 
  --
  Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
  ___
  freebsd-virtualization@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
  To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Linux on BHyVe in 10.0-RELEASE

[Aryeh Friedman]

# ls
ubuntu.iso
# kldstat
Id Refs AddressSize Name
 17 0x8020 16167b0  kernel
 21 0x81a12000 2a44 uhid.ko
 31 0x81a15000 34d3 ums.ko
# kldload vmm
# kldload if_tap
# kldload bridgestp
# kldload if_bridge
# ifconfig tap0 create
# ifconfig bridge0 create
# ifconfig bridge0 up
# ifconfig bridge0 addm tap0 addm re0
# mkdir ubuntu
# mv ubuntu.iso ubuntu
# cat -  EOF  ubuntu/device.map
? (hd0) ./ubuntu/ubuntu.img
? (cd0) ./ubuntu/ubuntu.iso
? EOF
# more ubuntu/device.map
(hd0) ./ubuntu/ubuntu.img
(cd0) ./ubuntu/ubuntu.iso
# truncate -s 8G ubuntu/ubuntu.img
# grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu

 :







































uninitializing+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+=
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+
=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+===
===++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=
==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+=
==+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+==
=++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===
===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+==
=+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
==+=+==+===++===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+=
=++==++===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
===+=+==+==+=+==+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+=
==+++==+==+==+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
=++==+==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+==
==+=+==+=+==+=+=+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
=+++===+==+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+=
===+=+==+=+==+===+=+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
==+++==+=+=+===+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+
=+===+=+==+==+=+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+===
==+=+==+==+=+===+==+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=
=++==+=+=+===++=+=+++==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
===+=+==+==+===+=+==+=+===+==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+=
==++===+=+===+==+==+=+=++==+===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+==
=+++===+=+=+=+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+
==+=+==+=+==++===+=+=+=+=+=+==+===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+===
=+++==+=+==+==+===+==+=+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=
===+=+==+=++==+==+==+===+=+=+=+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+==
==+++=+=+=+===+=+==+==+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+