Re: Need X-server to run in bhyve guest

[Lars Engels]

On Sun, Dec 08, 2019 at 06:23:16PM +0700, Victor Sudakov wrote:
> Rodney W. Grimes wrote:
> > > 
> > > Now I'd like to concentrate on the question how to start a graphical
> > > desktop environment in a bhyve guest.
> > 
> > Ok, found the issue, or atleast a work around... scfb is not probing 
> > correctly,
> > so create:
> > /usr/local/etc/X11/xorg.conf.d/driver-scfb.conf
> > With this in it:
> > 
> > Section "Device"
> >  Identifier"Card0"
> >  Driver"scfb"
> > EndSection
> > 
> > Your x11 should then work fine  I tested with xfce
> 
> Great, it works! I confirm it working with xfce and gdm (from gnome3).
> 
> Had to set xhci_mouse="no", which means that the mouse pointer in the VM
> is not quite in sync with the real mouse pointer, but the GUI starts all
> right!
> 
> Thank you, I think I can start testing various DEs. I've created a small
> how-to in Russian: https://victor-sudakov.dreamwidth.org/487181.html

Deepl.com did a great job translating it:

Installing FreeBSD with a graphical interface in bhyve
Dec. 8th, 2019 06:14 pm
victor_sudakov
May be useful, for example, for testing graphical desktop environments.
Sysutils/vm-bhyve is used as a shell to bhyve, net/tightvnc as a VNC client.

Since the framebuffer console is only available when booting the guest
operating system in UEFI mode (and not in bhyveload mode), you must install the
FreeBSD guest in UEFI mode.

I. The configuration of the new VM must contain the following parameters
Loader="uefi"
graphics="yes"
graphics_wait="auto"
graphics_res="1280x720"
xhci_mouse="no"

II. We start the installation as usual for UEFI guests:
vm install test1 FreeBSD-12.1-RELEASE-amd64-disc1.iso
vncviewer 192.168.1.1:5900

In the EFI console, wait for the FreeBSD boot menu, then press 3 (Escape to
loader prompt). In the loader console

set boot_serial=NO
boot

When installing Auto (ZFS), you must select "Partition Scheme GPT(UEFI)",
bsdinstall will create an EFI partition and place the loader there. When
installing on UFS, you will have to manually create an EFI partition and fill
it with content from /boot/boot1.efifat.

III. On the last step of the installation (Manual Configuration):
echo 'boot_serial="NO" >> /boot/loader.conf

IV. Install the X's and the required desktop environment:
pkg install xorg gnome3

V. In /usr/local/etc/X11/xorg.conf.d/driver-scfb.conf add a section:
Section "Device"
Identifier "Card0"
Driver "scfb"
EndSection

This is important! Unless you add it, X-server will not find a framebuffer
console.

VI. Run the right graphics environment
sysrc dbus_enable=YES
sysrc hald_enable=YES
sysrc gdm_enable=YES
apply "service %1 start" dbus hald gdm

Sources:
https://wiki.freebsd.org/bhyve/UEFI
Tread at 
https://lists.freebsd.org/pipermail/freebsd-virtualization/2019-December/007944.html

___
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. Unable install Windows 7/Server 2008R2

[Lars Engels]

On Tue, Dec 05, 2017 at 04:49:45AM -0800, Rodney W. Grimes wrote:
> > Hi,
> > 
> > >   bhyve -c 2 -s 0,hostbridge -s 
> > > 3,ahci-hd,/dev/zvol/my_zroot/VM/img/win7/disk0
> > 
> >   For win7/2k8*, the sector size presented to the guest has to be forced 
> > to 512 bytes i.e. for the ahci-cd slot, the config would look like:
> > 
> >   -s 3,ahci-hd,/dev/zvol/my_zroot/VM/img/win7/disk0,sectorsize=512
> 
> Should we start a wiki page on "Guest Quirks"?

Please do.

-- 
Lars
___
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: Windows XP

[Lars Engels]

On Wed, Feb 22, 2017 at 09:59:57AM +, Frank Leonhardt wrote:
> Can anyone help me running Windows 5.1 (XP) as a VM under FreeBSD?
> 
> bhyve doesn't support anything older than Vista, and I'm unclear as to 
> whether it supports 32-bit versions of that. I tried compiling 
> Virtualbox a while back, but after a few days it was still going so I 
> put it on the back burner. It wasn't clear how I'd get a Windows XP 
> image on it anyway.
> 
> So what's the best way to do this? I need it to run various Windows 
> 32-bit utilities, USB related (e.g. dongle servers, USB connected 
> hardware &c). I do have site-licensed Windows XP disks. Not to mention 
> DOS software!
> 

Why didn't you use the virtualbox packages?


pgpBpkW5zaQmb.pgp
Description: PGP signature

Re: Booting 9front on bhyve

[Lars Engels]

On Sun, Jan 08, 2017 at 08:10:13PM -0700, Trent Thompson wrote:
> Piotr,
> Thanks to work from Peter G, bhyve has been patched[1] to fix the PS/2
> mouse issue in 9front. With this fixed, I was able to get 9front installed
> and running from a bhyve virtual machine using virtio-blk emulation.  I was
> even able to set up networking[2] with virtio-net. Using ahci-hd and Intel
> 1000 emulation did not work for me. I'd also like to note that I had better
> success with partitioning the virtual hard drive as MBR in the installer,
> over GPT. I have heard of GPT working for some people, though. I uploaded a
> simple script to Gist[3] that I used to get this done, but as long as you
> use Virtio drivers you should be fine.
> 
> [1] https://svnweb.freebsd.org/base?view=revision&revision=311699
> [2] https://twitter.com/pr1ntf/status/817895393824382976/
> [3] https://gist.github.com/pr1ntf/fb62e316b3007f55590d2397a08b0e52
> 

Will you incorporate all your OS testing in iohyve? :)


pgpm9k6nss8ZZ.pgp
Description: PGP signature

Re: UEFI bhyve and EFI shell at boot

[Lars Engels]

On Mon, Sep 26, 2016 at 05:56:59AM +, Justin Holcomb wrote:
> > From: owner-freebsd-virtualizat...@freebsd.org 
> >  on behalf of Stephan CHEDLIVILI 
> > 
> > Sent: Saturday, September 24, 2016 12:50 AM
> > To: freebsd-virtualization@freebsd.org
> > Subject: UEFI bhyve and EFI shell at boot
> >     
> > Hi gents,
> > 
> > I was giving a try to the UEFI-GOP on a FreeBSD 11.0-RC3. Launching the 
> > install of, let's say a Debian works fine and I can attach a VNC viewer for 
> > the 
> > progress.
> > 
> > All is fine , even rebooting after the installation is finished I can log 
> > in 
> > Debian.
> > 
> > However, when I do a bhyvectl --destroy --vm=xxx and I try to reboot 
> > the 
> > VM and it greets me with the error message "Boot failed, EFI Harddrive" at 
> > boot and sends me to the EFI shell. 
> > 
> > I then have to manually use the shell menu to launch the boot via the 
> > ad-hoc 
> > file (/boot/efi/efi/debian/grubx64.efi) and it boot flawlessly.
> > 
> > And of course, the same error happens after I reboot the FreeBSD host 
> > machine
> > 
> > Is there somethign I am missing here ? 
> > 
> > Thanks for this admirable piece of work !
> > 
> > -Stephan
> 
> Stephan,
> 
> I have also experienced this as well. My scriptable work around was to start 
> the
> guest with a rEFInd ISO[1] instead a 'null.iso'. rEFInd sees the Debian
> installation on the image/volume and will boot from it after the 15 seconds
> timeout elapses.
> 
> As for the why... my rudimentary understanding is the Debian installation
> creates and relies on the UEFI boot entry it creates during installation.
> However that entry is forgotten once the guest's VMM resources are reclaimed 
> as
> the UEFI environment is not saved and is reloaded exactly from the UEFI ROM
> file (not from the previous state).
> 
> -Justin D Holcomb
> 
> [1] http://www.rodsbooks.com/refind/getting.html

That's also true for Ubuntu 16.04


pgp62RA69OnkE.pgp
Description: PGP signature

Re: Network unreachable in bhyve

[Lars Engels]

On Mon, Sep 12, 2016 at 12:21:48PM +, Grzegorz Junka wrote:
> I am following the official guide:
> 
> https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html
> 
> After installing Centos6 and starting the guest there is no network 
> inside the VM:
> 
> [root@localhost ~]# ping 8.8.8.8
> connect: Network is unreachable
> [root@localhost ~]# ifconfig
> loLink encap:Local Loopback
>inet addr:127.0.0.1  Mask:255.0.0.0
>inet6 addr: ::1/128 Scope:Host
>UP LOOPBACK RUNNING  MTU:65536  Metric:1
>RX packets:4 errors:0 dropped:0 overruns:0 frame:0
>TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>collisions:0 txqueuelen:0
>RX bytes:260 (260.0 b)  TX bytes:260 (260.0 b)
> 
> On the host:
> 
> root@ultrabook:~ # ifconfig
> ath0: flags=8843 metric 0 mtu 2290
>  ether 74:2f:68:cb:d6:2a
>  nd6 options=21
>  media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
>  status: associated
> lo0: flags=8049 metric 0 mtu 16384
>  options=63
>  inet6 ::1 prefixlen 128
>  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
>  inet 127.0.0.1 netmask 0xff00
>  nd6 options=21
> bridge0: flags=8843 metric 0 mtu 1500
>  ether 02:6c:a7:69:c7:00
>  nd6 options=9
>  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: tap0 flags=143
>  ifmaxaddr 0 port 4 priority 128 path cost 200
>  member: wlan0 flags=143
>  ifmaxaddr 0 port 5 priority 128 path cost 6
> tap0: flags=8943 metric 0 mtu 
> 1500
>  options=8
>  ether 00:bd:b1:16:00:00
>  nd6 options=29
>  media: Ethernet autoselect
>  status: active
>  Opened by PID 1918
> wlan0: flags=8943 metric 0 
> mtu 1500
>  ether 74:2f:68:cb:d6:2a
>  inet 192.168.8.101 netmask 0xff00 broadcast 192.168.8.255
>  nd6 options=29
>  media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
>  status: associated
>  ssid HUAWEI-7DC4 channel 1 (2412 MHz 11g ht/20) bssid 
> 94:fe:22:5c:7d:c4
>  regdomain 96 indoor ecm authmode WPA2/802.11i privacy ON
>  deftxkey UNDEF AES-CCM 2:128-bit txpower 20 bmiss 7 scanvalid 60
>  protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst
>  roaming MANUAL
> 
> I am using the following commands to load the kernel:
> 
>grub-bhyve -m device.map -r hd0,msdos1 -M 2048 centos
>ls (hd0,msdos1)/
>linux (hd0,msdos1)/vmlinuz-2.6.32-642.el6.x86_64 
> root=/dev/mapper/VolGroup-lv_root
>initrd (hd0,msdos1)/initramfs-2.6.32-642.el6.x86_64.img
>boot
> 
> and start the guest:
> 
>bhyve -c 4 -m 2048M -A -H -P \
>   -s 0:0,hostbridge \
>   -s 1:0,lpc \
>   -s 2:0,virtio-net,tap0 \
>   -s 3:0,virtio-blk,/dev/zvol/tank4/centos6v \
>   -l com1,stdio \
>   centos
> 
> The following has been added to /etc/rc.conf:
> 
> cloned_interfaces="bridge0 tap0"
> ifconfig_bridge0="addm wlan0 addm tap0"
> 
> /boot/loader.conf
> 
> vmm_load="YES"
> nmdm_load="YES"
> if_bridge_load="YES"
> if_tap_load="YES"
> 
> What I am missing?

You cannot bridge the tap and wlan device.
This only works with fixed ethernet devices. What you can do is set up
NATing with pf / ipfw so your bhyve VMs are "behind" your host.


pgpMNTzBybyUA.pgp
Description: PGP signature

Re: Bhyve tests and findings

[Lars Engels]

On Fri, Aug 05, 2016 at 01:59:45PM +0700, Victor Sudakov wrote:
> Lars Engels wrote:
> > > > 
> > > > uefi="yes"
> > > > graphics="yes"
> > > 
> > > Dear Colleagues,
> > > 
> > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > 
> > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> > on 10.3.
> 
> I'm not sure how to compile something from a different branch without
> compiling the whole world. make what?

For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run

make depend; make obj; make; make install. 


pgp4n7um3bsJ4.pgp
Description: PGP signature

Re: Bhyve tests and findings

[Lars Engels]

On Fri, Aug 05, 2016 at 08:31:02AM +0700, Victor Sudakov wrote:
> > 
> > uefi="yes"
> > graphics="yes"
> 
> Dear Colleagues,
> 
> Can I enjoy and test all those nice "UEFI-GOP" features on a
> 10.3-RELEASE system, or do I have to install CURRENT for that?

AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
on 10.3.


pgpjuLGPrDS8h.pgp
Description: PGP signature

Re: bhyve coredump on 11.0-ALPHA6

[Lars Engels]

On Sat, Jul 09, 2016 at 02:46:32PM -0700, Peter Grehan wrote:
> > Yes, without that line it boots. But the vnc cursor speed does not match
> > the host cursor speed.
> 
>   That's the classic problem with VNC - most o/s's implement cursor 
> acceleration, while VNC only reports absolute cursor position, and the 
> ps2 mouse only reports relative cursor position :(
> 
>   The advantage of the usb tablet is that it reports absolute position, 
> so the VNC and rendered cursor are identical. Agitate on FreeBSD support 
> for that :)

I know. Now if someone could implement this... ;-)


pgp2ggz4W3OJF.pgp
Description: PGP signature

Re: bhyve coredump on 11.0-ALPHA6

[Lars Engels]

On Sat, Jul 09, 2016 at 01:54:18PM -0700, Peter Grehan wrote:
> Hi Lars,
> 
> > Found the problematic argument:
> >
> >> -s 30,xhci \
> >
> > I removed ",tablet" from that line. But I guess bhyve should better not
> > segfault but give an error message.
> 
>   Yes, that can be added.
> 
>   Not sure if the tablet works on FreeBSD though - you may have to drop 
> that config line and fall back to the ps2 mouse.

Yes, without that line it boots. But the vnc cursor speed does not match
the host cursor speed.


pgp2u75Z139rD.pgp
Description: PGP signature

Re: bhyve coredump on 11.0-ALPHA6

[Lars Engels]

On Sat, Jul 09, 2016 at 10:22:57PM +0200, Lars Engels wrote:
> 
[..]
Found the problematic argument:

> -s 30,xhci \

I removed ",tablet" from that line. But I guess bhyve should better not
segfault but give an error message.




pgpSx7pi0_qwp.pgp
Description: PGP signature

bhyve coredump on 11.0-ALPHA6

[Lars Engels]

I wanted to give TrueOS Desktop a try using the new GOP bhyve.
When I start the virtual machine and connect with tightvnc bhyve
crashes:

/bhyve/TrueOSDesktop > gdb /usr/sbin/bhyve bhyve.core

Core was generated by `bhyve'.
Program terminated with signal 11, Segmentation fault.

#0  0x0042c41e in pci_xhci_reset_slot (sc=0x801b3c000, slot=1) at 
/usr/src/usr.sbin/bhyve/pci_xhci.c:707
707 dev = XHCI_SLOTDEV_PTR(sc, slot);
(gdb) bt full
#0  0x0042c41e in pci_xhci_reset_slot (sc=0x801b3c000, slot=1) at 
/usr/src/usr.sbin/bhyve/pci_xhci.c:707
dev = (struct pci_xhci_dev_emu *) 0x0
#1  0x0042a693 in pci_xhci_reset (sc=0x801b3c000) at 
/usr/src/usr.sbin/bhyve/pci_xhci.c:359
i = 1
#2  0x00429c91 in pci_xhci_init (ctx=0x801a1b080, pi=0x801a42c80, 
opts=0x0) at /usr/src/usr.sbin/bhyve/pci_xhci.c:2779
sc = (struct pci_xhci_softc *) 0x801b3c000
error = 0
#3  0x0041c28b in pci_emul_init (ctx=0x801a1b080, pde=0x654f90, bus=0, 
slot=30, func=0, fi=0x801a21c70) at /usr/src/usr.sbin/bhyve/pci_emul.c:749
pdi = (struct pci_devinst *) 0x801a42c80
err = 0
#4  0x0041bd49 in init_pci (ctx=0x801a1b080) at 
/usr/src/usr.sbin/bhyve/pci_emul.c:1109
mr = {name = 0x9 , flags = 9, handler = 
0x650bf36715e07822, arg1 = 0x0, arg2 = 140737488348512, base = 4389931, size = 
0}
pde = (struct pci_devemu *) 0x654f90
bi = (struct businfo *) 0x801a2
si = (struct slotinfo *) 0x801a21c40
fi = (struct funcinfo *) 0x801a21c70
lowmem = 18446735284888420640
bus = 0
slot = 30
func = 0
error = 0
#5  0x0040a715 in main (argc=1, argv=0x7fffe778) at 
/usr/src/usr.sbin/bhyve/bhyverun.c:913
c = -1
error = 0
gdb_port = 0
err = 0
bvmcons = 0
max_vcpus = 16
mptgen = 1
memflags = 0
rtc_localtime = 1
ctx = (struct vmctx *) 0x801a1b080
rip = 26
memsize = 4294967296
optstr = 0x446057 "abehuwxACHIPSWYp:g:c:s:m:l:U:"
Current language:  auto; currently minimal
(gdb) 


The command I used to start was:

bhyve -c 2 -m 4096 -w -H \
-s 0,hostbridge \
-s 
3,ahci-cd,/ISOs/TrueOS-Desktop-11.0-CURRENTJULY2016-07-08-2016-x64-DVD.iso \
-s 4,ahci-hd,disk0.img \
-s 5,virtio-net,tap0 \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
-s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait \
-s 30,xhci \
-s 31,lpc -l com1,stdio \
vm0




pgpXU6EcygH0x.pgp
Description: PGP signature

Re: bhyve graphics support

[Lars Engels]

On Fri, May 27, 2016 at 09:11:16PM +1000, Jason Tubnor wrote:
> On 27 May 2016 8:44 PM, "Lars Engels"  wrote:
> >
> >
> > downloading the UEFI image I start Ubuntu like this:
> >
> > grub-bhyve -m device.map -r hd0,msdos1 -M 4G ubuntu
> > ~lars/dev/bhyve_graphics/bhyve \
> > -s 0:0,hostbridge \
> > -s 1:0,lpc \
> > -s 2:0,virtio-net,tap1 \
> > -s 3:0,virtio-blk,./ubuntu-hd.img \
> > -s 11,fbuf,tcp=0.0.0.0:5900,w=1280,h=720,wait \
> > -s 20,xhci,tablet \
> > -l bootrom,/home/lars/dev/bhyve_graphics/BHYVE_UEFI_20160526.fd \
> > -c 4 \
> > -m 4G \
> > ubuntu
> >
> >
> > Then I connect with vncviewer but only see this message:
> >
> > "Boot failed. EFI misc device"
> 
> I don't think you need the grub shim with uefi.

That might be, but removing the grug-bhyve call doesn't change the error
message.


pgpe4RiZj1Vhh.pgp
Description: PGP signature

Re: bhyve graphics support

[Lars Engels]

On Fri, May 27, 2016 at 01:33:42AM -0700, Peter Grehan wrote:
> As of r300829, support for graphic output has been checked into the 
> projects/bhyve_graphics branch. This is just the usr.sbin/bhyve 
> executable, so is quick and easy to build from source.
> 
> Assuming a reasonably current source tree is in /usr/src,
>svn co http://svn.freebsd.org/base/projects/bhyve_graphics path/to/dir
>cd path/to/dir
>make BHYVE_SYSDIR=/usr/src -m /usr/src/share/mk
> 
> UEFI GOP support has been checked into the freebsd/edk2 repo:
>  
> https://github.com/freebsd/uefi-edk2/commit/a36132939e259df79b16699c03c6f1d63c7454b9
> 
> A pre-built bhyve/UEFI binary image with GOP support is available at:
>https://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20160526.fd
> 
> The new bhyve executable supports some new devices. An example of using 
> them for Windows10 is:
> 
> bhyve \
> -c 2 \
> -s 3,ahci-cd,/images/win10_install.iso \
> -s 4,ahci-hd,/images/win10.img \
> -s 11,fbuf,tcp=0.0.0.0:5900,w=1600,h=900,wait \
> -s 20,xhci,tablet \
> -s 31,lpc \
> -l bootrom,/images/BHYVE_UEFI_20160526.fd \
> -m 2G -H -w \
> windows

Thanks for your work on this!

With Ubuntu 16.04 I was not successful so far. After compiling bhyve and
downloading the UEFI image I start Ubuntu like this:

grub-bhyve -m device.map -r hd0,msdos1 -M 4G ubuntu
~lars/dev/bhyve_graphics/bhyve \
-s 0:0,hostbridge \
-s 1:0,lpc \
-s 2:0,virtio-net,tap1 \
-s 3:0,virtio-blk,./ubuntu-hd.img \
-s 11,fbuf,tcp=0.0.0.0:5900,w=1280,h=720,wait \
-s 20,xhci,tablet \
-l bootrom,/home/lars/dev/bhyve_graphics/BHYVE_UEFI_20160526.fd \
-c 4 \
-m 4G \
ubuntu


Then I connect with vncviewer but only see this message:

"Boot failed. EFI misc device"

Is there anything I can try?


pgpZDByStLQd2.pgp
Description: PGP signature

Re: MFC of bhyve UEFI / Windows support?

[Lars Engels]

On Tue, Jan 12, 2016 at 01:34:03PM +0100, Yamagi Burmeister wrote:
> Hello,
> just a small question: Is a MFC of the bhyve UEFI / Windows support
> planed in time for FreeBSD 10.3? I've been running several Windows 10
> instances under a patched 10-STABLE for some time now and at least for
> me they're totally stable and without any problems. Nevertheless having
> a regular release with bhyve UEFI / Windows support would be nice.
> 
> My 10-STABLE branch has the following revisions merged from HEAD:
>  - 284539
>  - 284630
>  - 284688
>  - 285217
>  - 286837
>  - 286838
>  - 288470
>  - 288522
>  - 288524
>  - 288826
>  - 289001

+1 for this suggestion! 


pgpEBR5Mj84l4.pgp
Description: PGP signature

Re: [regression] bhyve stopped working

[Lars Engels]

On Fri, Oct 03, 2014 at 10:28:13AM -0700, Peter Grehan wrote:
> HI Lars,
> 
> > I just upgraded to r272468 and bhyve stopped working. When I start a VM
> > (Ubuntu or FreeBSD) byhve dumps core:
> 
>   Should be fixed in r272481.
> 

Yes, I can confirm that.

Thank you!

Lars


pgp7NdN3eK_xQ.pgp
Description: PGP signature

[regression] bhyve stopped working

[Lars Engels]

I just upgraded to r272468 and bhyve stopped working. When I start a VM
(Ubuntu or FreeBSD) byhve dumps core:

/boot/kernel/kernel text=0xfbecf0 data=0x129e30+0x6068a0 
syms=[0x8+0x141630+0x8+0x15c538]
Booting...
Error6010 - Internal compiler error Found NULL field - Field name "Sleep 
Status Register" needed
Error6126 -  Could not compile input file
/tmp/bhyve.wp2hqCk 88: [0008]   FACS Address : 000F27C0
Error6302 -  Flag value is too large ^  (Maximum 1 bit)
/tmp/bhyve.wp2hqCk 89: [0008]   DSDT Address : 000F2800
Error6302 -  Flag value is too large ^  (Maximum 1 bit)
/tmp/bhyve.wp2hqCk 95: [0008]   Address : 0400
Error6303 - ^ Integer too large for target 
(0400 - max 1 bytes)
/tmp/bhyve.wp2hqCk109: [0008]   Address : 0404
Error6303 - ^ Integer too large for target 
(0404 - max 1 bytes)
/tmp/bhyve.wp2hqCk130: [0008]   Address : 0408
Error6303 - ^ Integer too large for target 
(0408 - max 1 bytes)
Assertion failed: (error == 0), function main, file 
/usr/src/usr.sbin/bhyve/bhyverun.c, line 849.
Abort trap (core dumped)
Exit 99


===

root@pts/1 # gdb /usr/sbin/bhyve bhyve.core
GNU gdb (GDB) 7.8 [GDB v7.8 for FreeBSD]
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd11.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/bhyve...done.
[New process 101724]
[New process 101750]
[New Thread 801c06c00 (LWP 101750)]
[New Thread 801c06400 (LWP 101724)]
Core was generated by `bhyve'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00080110d49a in thr_kill () from /lib/libc.so.7
(gdb) bt full
#0  0x00080110d49a in thr_kill () from /lib/libc.so.7
No symbol table info available.
#1  0x0008011e3af9 in abort () from /lib/libc.so.7
No symbol table info available.
#2  0x0008011c58a1 in __assert () from /lib/libc.so.7
No symbol table info available.
#3  0x004089c8 in main (argc=1, argv=0x7fffe850) at 
/usr/src/usr.sbin/bhyve/bhyverun.c:849
c = -1
error = 65280
gdb_port = 0
err = 0
bvmcons = 0
dump_guest_memory = 0
max_vcpus = 16
mptgen = 1
ctx = 0x801c16080
rip = 16777216
memsize = 1073741824



pgp2MZ_qQzeGz.pgp
Description: PGP signature

Re: best way to add www to wheel

[Lars Engels]

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.


___
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

[Lars Engels]

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"

Re: BHyVe - ESXi comparison

[Lars Engels]

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"

Re: Public Service Announcement: The name is "bhyve"

[Lars Engels]

Am 2014-01-24 11:18, schrieb Michael Dexter:

Hello all,

It was "BHyVe" and Neel and Peter mercifully simplified it to "bhyve".

It was never "BHyve" and how they came up with "byhyve" and "byhve" in
the same article I do not know:

http://www.serverwatch.com/server-news/open-source-freebsd-10-takes-on-virtualization.html

Haters gonna hate?




Don't forget "Beehyve":

http://www.admin-magazin.de/News/FreeBSD-10.0-fertiggestellt/%28language%29/ger-DE

But don't confuse it with Beehive:

https://stbeehive.oracle.com/bcentral/


:-)
___
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

[Lars Engels]

Am 2014-01-23 12:58, schrieb Jonas Bülow:

/dev/mapper/c--182--181--143--31--vg-root 960.4M936.1M 0 
100% /target


--> The created partition for / is too small.
___
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

[Lars Engels]

Am 2014-01-23 11:53, schrieb Jonas Bülow:

FWIW, I extracted the syslog for the failing ubuntu installation. The
failing grub install shows up as:

Jan 23 10:51:08 grub-installer: info: architecture: amd64/generic
Jan 23 10:51:08 in-target: Reading package lists...
Jan 23 10:51:08 in-target: Reading package lists...
Jan 23 10:51:08 in-target:
Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on 
device)

Jan 23 10:51:08 in-target: E: Can't mmap an empty file
Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9:
Bad file descriptor)
Jan 23 10:51:08 in-target: E: The package lists or status file could
not be parsed or opened.
Jan 23 10:51:08 grub-installer: info: Identified partition label for
/dev/vda1: msdos
Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute
'grub-probe': No such file or directory
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
space left on device
Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute
'grub-probe': No such file or directory
Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3
(pipe:[7196]) leaked on lvdisplay invocation.
Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735: 
/bin/sh

Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4
(/dev/ttyS0) leaked on lvdisplay invocation.
Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735: 
/bin/sh

Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5
(/dev/ttyS0) leaked on lvdisplay invocation.
Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735: 
/bin/sh

Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6
(/dev/ttyS0) leaked on lvdisplay invocation.
Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735: 
/bin/sh

Jan 23 10:51:08 main-menu[211]: (process:18530):
Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group "vda" not 
found

Jan 23 10:51:08 main-menu[211]: (process:18530):
Jan 23 10:51:08 main-menu[211]: (process:18530):
Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group 
vda

Jan 23 10:51:08 main-menu[211]: (process:18530):
Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver
"config": could not write /var/cache/debconf/config.dat-new: No space
left on device
Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring
'grub-installer' failed with error code 1
Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer' 
failed.

Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit
from 'medium' to 'low'
Jan 23 10:51:09 debconf: Setting debconf/priority to low
Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected





Normally you can switch to another virtual console with Alt+F1 to F4 
(IIRC), I don't know if

that's also possible in bhyve.
If it works, please open a shell and see with "df" which filesystem is 
full.

___
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: emulators/petitecloud 0.2.1 available

[Lars Engels]

On Fri, Jan 17, 2014 at 09:36:27PM -0500, Aryeh Friedman wrote:
> On Fri, Jan 17, 2014 at 7:25 PM, Aryeh Friedman 
> wrote:
> 
> >
> >
> >
> > On Fri, Jan 17, 2014 at 7:11 PM, Mark Martinec <
> > mark.martinec+free...@ijs.si> wrote:
> >
> >> http://www.PetiteCloud.org
> >>> --> http://www.petitecloud.org/downloads/port.tar.gz
> >>>
> >>
> >> # make
> >> ===>   src-petitecloud-aegis-0.2.1 depends on file: /usr/local/sbin/pkg -
> >> found
> >> => src-petitecloud-aegis-0.2.1.tar.gz doesn't seem to exist in
> >> /usr/ports/distfiles/.
> >> => Attempting to fetch
> >>   ftp://ftp.petitecloud.org/petitecloud/0.2.1/aegis/src-
> >> petitecloud-aegis-0.2.1.tar.gz
> >> fetch: ftp://ftp.petitecloud.org/petitecloud/0.2.1/aegis/src-
> >> petitecloud-aegis-0.2.1.tar.gz:
> >>   File unavailable (e.g., file not found, no access)
> >>
> >> There is no directory 'aegis' there, but there is an 'aryeh'.
> >> Also there is no src-petitecloud-aegis-0.2.1.tar.gz in it.
> >> URL should probably be:
> >>   ftp://ftp.petitecloud.org/petitecloud/0.2.1/aryeh/src-
> >> petitecloud-aryeh-0.2.1.tar.gz
> >>
> >>
> > Will look into this... for now just use aegis... you will need to modify
> > the Makefile... since the Makefile itself is autogenerated we will post new
> > port files later tonight with the fix in them btw if you're interested
> > in helping with development you will also need devel/aegis in addition to
> > the port's dependencies
> >
> >
> Fixed and posted new port files to petitecloud.org...  side question should
> I update the PR for the port or create a new one?

Please update the existing one.


pgpXGUKPYzGvg.pgp
Description: PGP signature

Re: very rough draft of handbook entry for bhyve

[Lars Engels]

Am 16.09.2013 11:52, schrieb Aryeh Friedman:

We are in middle of switching nameservers so give it time or restart
your nameserver... from the logs about a 100 people have made it
through so I don't think it is our end




Today it's working.
___
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: very rough draft of handbook entry for bhyve

[Lars Engels]

Am 16.09.2013 07:39, schrieb Aryeh Friedman:

I have posted a cleaned up version of it at the same url




... which is still not resolvable.
___
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"