search for: bhyve

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good morning, I am not sure if this is a known issue or if I should raise as a bug. When using libvirt 1.2.11 on FreeBSD 10.1-RELEASE with bhyve, I have notice that a machine which defines: <interface type='bridge'> <mac address='52:54:00:88:44:08'/> <source bridge='bridge10'/> <model type='virtio'/> <address type='pci' domain='0x0000' bu...

...all device implementations which conform to the spec just work. One implementation that comes to mind is virtualbox. But from a quick look at the source, it seems that it sets the ISR bit always, too. And it uses qemu's subsystem vendor id. But there are other implementations. For example bhyve. > AFAIK a subsystem vendor id does not cost money to register, but > only pci sig members can do this, and membership costs $3000. > Maybe we should combine all this with checking subsystem vendor id, > and only implement the optimization if it matches qemu, for now. > This needs...

...all device implementations which conform to the spec just work. One implementation that comes to mind is virtualbox. But from a quick look at the source, it seems that it sets the ISR bit always, too. And it uses qemu's subsystem vendor id. But there are other implementations. For example bhyve. > AFAIK a subsystem vendor id does not cost money to register, but > only pci sig members can do this, and membership costs $3000. > Maybe we should combine all this with checking subsystem vendor id, > and only implement the optimization if it matches qemu, for now. > This needs...

...onform to the > spec just work. > > One implementation that comes to mind is virtualbox. But from a quick > look at the source, it seems that it sets the ISR bit always, too. And > it uses qemu's subsystem vendor id. > > But there are other implementations. For example bhyve. I couldn't find any code in bhyve that sets VTCFG_ISR_CONF_CHANGED. Maybe it doesn't generate config changed interrupts? bhyve sets subsystem vendor to 0 apparently? We could use that to detect it. But maybe we should just make it a 1.0 only feature. > > > AFAIK a subsystem v...

...regularly. This is one of those ?bags of changes? I referred to above. Sometimes I want the Linux bag, and sometimes I want the FreeBSD bag, and I know going into the decision that each bag implies a future bag of changes I?ll have to deal with. > It was the OS running the metal for multiple BHyve virtual machines Ah, more change. Bhyve only goes back to FreeBSD 10, so if you were using FreeBSD prior to that, you?d have had to either drag forward whatever VM manager you were using or migrate to bhyve. > given we use ZFS in FreeBSD, and that we snapshot regularly, getting > back to 1...

On Sat, October 14, 2017 14:33, Andrew Bartlett wrote: > > I remain ever thankful to those who are willing to test new Samba > versions, particularly Samba release candidates. > We have a FreeBSD-11 BHyve virtual machine spun up and awaiting a working SAMBA past v4.3+ to trial. So whenever this port gets to the point of requiring FreeBSD testers just drop me a note. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachme...

...ts of suitable crontab entries. To obtain these sort of things from a Linux distro would require a considerable effort just to establish the infrastructure. Not to mention separate hardware, which needs to be twinned here and at our offsite location. And only then would I get to deal with Samba. Bhyve was tried as a VM hypervisor on FreeBSD; and while it worked well in 10.4 and 11.x, and still does support our actual MS AD-DC, changes to Bhyve and to ZFS resulted in a seriously unpleasant experience with vm lockups following the upgrade of the host to 12.0. These were ultimately resolved by movi...

...--sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-runstatedir=/run --with-qemu --without-openvz --without-lxc --without-vbox --without-libxl --with-sasl --with-polkit --with-libvirtd --without-phyp --with-esx --without-hyperv --without-vmware --without-vz --without-bhyve --with-remote-default-mode=legacy --with-interface --with-network --with-storage-fs --with-storage-lvm --with-storage-iscsi --with-storage-iscsi-direct --with-storage-scsi --with-storage-disk --with-storage-mpath --with-storage-rbd --without-storage-sheepdog --with-storage-gluster --without-storage...

...yes configure: UML: yes configure: OpenVZ: yes configure: VMware: yes configure: VBox: yes configure: XenAPI: no configure: xenlight: no configure: LXC: yes configure: PHYP: no configure: ESX: no configure: Hyper-V: no configure: Parallels: yes configure: Bhyve: no configure: Test: yes configure: Remote: yes configure: Network: yes configure: Libvirtd: yes configure: Interface: yes configure: macvtap: yes configure: virtport: yes configure: configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure:...

Good day, would like to install the latest version of libvirt collected from sources for use bhyve. Download ftp://libvirt.org/libvirt/libvirt-1.2.9.tar.gz, system... uname -a FreeBSD vmserver 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64 my actions: ./configure make sudo make install next... make a...

Hi all Centos 7.0.1406, 3.10.0-123.el7.x86_64 Configure libvirt-1.2.7 as: ./configure --prefix=/usr --with-xen=no --with-qemu=no --with-openvz=no --with-vmware=no --with-esx=no --with-parallels=no --with-bhyve=no --with-uml=no --with-vbox=no --with-selinux=no make ... make[3]: Entering directory `/usr/local/src/libvirt-1.2.7/daemon' CC libvirtd-remote.o CCLD libvirtd libvirtd-remote.o: In function `remoteRelayDomainEventCheckACL': /usr/local/src/libvirt-1.2.7/daemon/remote.c:157: u...

...mplementing it for Linux > > is in their best interest. > > Do you know any of them who should be cc'd? > No, not anyone in particular. git log arch/x86/kernel/cpu/vmware.c may help. But VMware is an elephant in the room here. There are other hypervisors out there. VirtualBox, bhyve... -- Gleb.

...mplementing it for Linux > > is in their best interest. > > Do you know any of them who should be cc'd? > No, not anyone in particular. git log arch/x86/kernel/cpu/vmware.c may help. But VMware is an elephant in the room here. There are other hypervisors out there. VirtualBox, bhyve... -- Gleb.

...e number of cases here are supposed to be pretty small. Apparently there have been some Coverity rules developed to help look for these, but we are still evaluating what can be done here. The other half of Spectre, variant 2 (CVE-2017-5715) is a bit trickier as it affects both normal processes and bhyve. There is a proposed patch for LLVM (https://reviews.llvm.org/D41723) that introduces a concept called 'retpoline' which mitigates this issue. We are likely to pull this into HEAD and 11-STABLE once it hits the LLVM tree. Unfortunately, the currently supported FreeBSD releases are using old...

...e number of cases here are supposed to be pretty small. Apparently there have been some Coverity rules developed to help look for these, but we are still evaluating what can be done here. The other half of Spectre, variant 2 (CVE-2017-5715) is a bit trickier as it affects both normal processes and bhyve. There is a proposed patch for LLVM (https://reviews.llvm.org/D41723) that introduces a concept called 'retpoline' which mitigates this issue. We are likely to pull this into HEAD and 11-STABLE once it hits the LLVM tree. Unfortunately, the currently supported FreeBSD releases are using old...

...red in accomplishing what amounts to maintaining the status quo. We just upgraded a FreeBSD host from 10.3 to 11.0 in situ without problem; and with very little downtime (three reboots in the space of 30 minutes). This was no standalone device either. It was the OS running the metal for multiple BHyve virtual machines, themselves running various operating systems (but mainly FreeBSD-11). One of said vms being our Samba-4 AD-DC. And, had it all gone south then, given we use ZFS in FreeBSD, and that we snapshot regularly, getting back to 10.3 would have been, and still could be, nearly instantan...

On 04/26/2016 07:44 AM, mxs kolo wrote: > Now reporduced with 100% > 1) create contrainer with memory limit 1Gb > 2) run inside simple memory test allocator: > #include <malloc.h> > #include <unistd.h> > #include <memory.h> > #define MB 1024 * 1024 > int main() { > int total = 0; > while (1) { > void *p = malloc( 100*MB ); >

On Thu, July 23, 2020 16:50, Rowland penny wrote: > Port 137 should only be used by Samba nmb, so has nmbd somehow > been started ? No. The error is not caused by anything else listening on 137. [root at smb4-2 ~ (master)]# netstat -an | grep -i listen tcp4 0 0 192.168.18.162.22 *.* LISTEN tcp4 0 0 192.168.216.162.22 *.*

...issue with that version Sorry, I miss version and another details. Test make on CentOS Linux release 7.2.1511 (Core) and libvirt 1.3.2, build from sources with next options: --without qemu \ --without xen \ --without openvz \ --without vmware \ --without esx \ --without parallels \ --without bhyve \ --without uml \ --without vbox \ --without selinux \ --with lxc \ --with macvtap \ --without storage-rbd \ --with capng Kernel 3.10.0-327.13.1.el7.x86_64 With version 1.2.18 we had 2 problem - negative value in "used" column and 8Ptb in "total" column. In 1.3.2 &qu...

...and another details. > Test make on CentOS Linux release 7.2.1511 (Core) > and libvirt 1.3.2, build from sources with next options: > --without qemu \ > --without xen \ > --without openvz \ > --without vmware \ > --without esx \ > --without parallels \ > --without bhyve \ > --without uml \ > --without vbox \ > --without selinux \ > --with lxc \ > --with macvtap \ > --without storage-rbd \ > --with capng > > Kernel 3.10.0-327.13.1.el7.x86_64 > With version 1.2.18 we had 2 problem - negative value in "used" column...