Re: virtualbox tips for performance specific to FreeBSD-10 hosts
On Sat, Feb 8, 2014 at 10:51 AM, John freebsd-li...@potato.growveg.org wrote: Hello list, As subject, can anyone recommend any tips for getting optimum performance from various guests on a freebsd-10-R host? I've looked at the page about changing polling interval but that only applies to freebsd guests. I'm looking advice specifically for linux guests on this host. Guests are ubuntu and opensuse. Machine is a Xeon E5-2650L @ 1.80GHz with 32 cores, 192GB RAM and 10TB available storage on zfs. I would not recommend using VirtualBox on such a box. VirtualBox is a Desktop Virtualisation product and that specs are too high to make good use of them. One issue you will run into is ZFS ARC - with that amount of memory it will take quite some time to fill up but ZFS ARC and VirtualBox wired memory will start fighting each other. So I recommend limiting ZFS ARC to some sane amount. (32GB?) VirtualBox has quite a bit more overhead than all the other server grade virtualisation products out there and that is especially true for I/O. With FreeBSD 10 you should already use AHCI on the host and the linux guests will likely use an SATA controller and AHCI too. That should be the minimum and is also what we have already written down in the vbox tuning notes: https://wiki.freebsd.org/VirtualBox/Tuning No issues sofar freebsd on freebsd. Just looking for advice linux guest on freebsd with virtualbox. Or perhaps there's something better than virtualbox? Basically all guests need to be isolated from one another. It makes backing up and restoring systems pain-free. So far this are the mainstream candidates: BSD: - BHyVe Linux: - KVM - Xen Proprietary: - VMware ESXi - XenServer I have had a look at a server virtualisation product myself some months ago and came to the conclusion that there is no painfree server virtualisation product that is focused on ONE machine with a proper webinterface with a reasonable easy installation and for free. VMware ESXi came close but it fails badly with the webinterface (no I don't consider the required 8-16GB RAM for the webinterface appropriate). RedHats oVirt also made a good impression but I broke it within half an hour and the webinterface never detected the nodes properly. Also oVirt really wants you to have a dedicated storage box which I wanted to avoid. Running it all on one machine is on their todo for years. No I don't want to run 3 boxes for two VMs. OpenStack was just a mess and I gave up because all the different components didn't fit into my small head. This really looks like you want to build your own cloud with 1000+ nodes. There are quite a few more KVM based products out there which I didn't try just because I gave up at that point and went with the free ESXi and a windows VM with vSphere Client. The ones that I remember were also appropriate candiates for my search were Ubuntu 12.04 LTS with KVM + convirt2, Proxmox or a simple Linux distribution and shell. So VirtualBox + phpvirtualbox does a few things very very good and I love it for that on small boxes with light load but it's not a proper server virtualisation product. What I would really like to see is a FreeNAS like appliance for virtualisation with a webinterface and based on BHyVe. The Linux KVM stuff is not quite there yet when it comes to painless. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-emulation@FreeBSD.org
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 ports/184404 emulation [patch] emulators/linux_base-f10: no terminal database o kern/183615 emulation [linprocfs] [patch] emulate /proc/sys/kernel/random/uu o ports/183247 emulation emulators/linux_base-f10 does not build locale archive o ports/183120 emulation x11-toolkits/linux-f10-pango fails to build o kern/182884 emulation [hyper-v] FreeBSD HVMPV domU networking does not work o kern/181012 emulation [linux] [patch] Implemented linux system call fstatfs6 o ports/180790 emulation devel/linux_kdump prints BSD descriptions of errno nam o kern/177743 emulation [kvm] [panic] kernel panic during `portsnap update` on o ports/177722 emulation Change request: Add terminfo database to linux_base-* o kern/174933 emulation [linux] if_nameindex fail in linuxulator enviroment o kern/174908 emulation [vmware] unsupportable block size 0 after upgrading o kern/174238 emulation [qemu] FreeBSD 9.0 doesn't boot under QEMU due to ACPI o ports/169896 emulation [patch] audio/linux-f10-alsa-lib: use OSS plugin by de o kern/169814 emulation [linux] ptrace is broken in Linux emulation o kern/169805 emulation [linux] utime() syscall does not work in linuxulator o kern/159646 emulation [linux] [patch] bump Linux version in linuxulator f kern/156691 emulation [vmware] [panic] panic when using hard disks as RAW de o kern/156353 emulation [ibcs2] ibcs2 binaries that execute on 4.x not working o kern/155577 emulation [boot] BTX halted after install. Reboot during install o kern/155040 emulation [linux] [patch] Linux recvfrom doesn't handle proto fa o kern/153990 emulation [hyper-v]: Will not install into Hyper-V on Server 200 o kern/153887 emulation [linux] Linux emulator not understand STB_GNU_UNIQUE b o kern/153243 emulation [ibcs2] Seg fault whne running COFF binary using iBCS2 o kern/151714 emulation [linux] print/acroread9 not usable due to lack of supp a bin/150262 emulation [patch] truss(1) -f doesn't follow descendants of the a kern/150186 emulation [parallels] [panic] Parallels Desktop: CDROM disconnec o ports/148097 emulation [patch] suggested addition to linux_base-* packages to o ports/148096 emulation emulators/linux_base-* can not be built from ports on o kern/147793 emulation [vmware] [panic] cdrom handling, panic, possible race o kern/146237 emulation [linux] Linux binaries not reading directories mounted p kern/144584 emulation [linprocfs][patch] bogus values in linprocfs o ports/142837 emulation [patch] emulators/linux_base-* packages fails to insta o kern/140156 emulation [linux] cdparanoia fails to read drive data f kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage s kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/86619 emulation [linux] linux emulator interacts oddly with cp a kern/72920 emulation [linux] path prefixing is not done on unix domain so o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/36952 emulation [patch] [linux] ldd(1) command of linux does not work o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 44 problems total. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Current problem reports assigned to emulat...@freebsd.org
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 ports/186232 emulation x11-fonts/linux-f10-fontconfig/Makefile add -f to ln s 1 problem total. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Current problem reports assigned to v...@freebsd.org
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 ports/184964 vbox [patch] emulators/virtualbox-ose-additions: does not b o ports/183739 vbox emulators/virtualbox-ose-kmod fails to build on freebs o ports/182787 vbox emulators/virtualbox-ose-additions: fix VBoxClient pat o ports/182471 vbox emulators/virtualbox-ose gets SIGBUS with VNC o ports/182469 vbox emulators/virtualbox-ose VNC extension has incorrect p o ports/182468 vbox [patch] lang/gcc builds unrunnable emulators/virtualbo o ports/182320 vbox emulators/virtualbox-ose-additions will not compile on o ports/179507 vbox devel/kBuild won't compile on current o ports/177202 vbox [PATCH] emulators/virtualbox-ose option to skip buildi o ports/175411 vbox [PATCH] emulators/virtualbox-ose 4.2.6: popcnt bug o ports/175288 vbox emulators/virtualbox-ose: FreeBSD VirtualBox guest una o ports/175221 vbox emulators/virtualbox-ose: Cannot Resume VirtualBox VMs o ports/174975 vbox Latest emulators/virtualbox-ose-kmod 4.2.6 commit (309 o ports/174968 vbox emulators/virtualbox-ose: CAM lockup when using more t o ports/173925 vbox emulators/virtualbox-ose-additions 4.1.22 VBoxService o ports/173672 vbox emulators/virtualbox-ose: VirtualBox and bridge proble o ports/167720 vbox emulators/virtualbox-ose: VirtualBox 4.1.14- Guest: Fr o ports/163142 vbox emulators/virtualbox-ose: virtualbox doesn't work on n o kern/140453 vbox [sound] [vbox] No sound inside Virtualbox on 50% volum 19 problems total. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: CFT: Re: linux libusb again, I made an updated port...
On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote: On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote: On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote: On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote: On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote: On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote: Hi! This came up on irc so I tried to build a linux libusb port (before I learned about ports/146895), mine uses linux_base-gentoo-stage3 like linux_kdump with a src/lib/libusb head snapshot so it's more up to date than wkoszek's build (ports/146895), and it's really easy to update it again. Also maybe it can be used as linux libusb-1.0.so too; I didn't actually test it tho. Should this be committed? Is wkoszek's version better since it also builds on 10.x? Comments welcome... wkoszek's version: http://www.freebsd.org/cgi/query-pr.cgi?pr=146895 Mine: http://people.freebsd.org/~nox/tmp/linux_libusb.shar Distfile: http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2 10/amd64 package: http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz (built via: poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb - btw for some reason the dependency emulators/linux_base-gentoo-stage3 doesn't build for 10i386 in poudriere bulk, I get a pkg segfault. bapt Cc'd...) Juergen, Hi! What would be the reason for this update? My stuff may be out of date, but it was all tested and working. I verified it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which this stuff was written. I was just thinking an updated version may be useful, but if it's already working for everyone maybe less so... Or would it work as a linux libusb-1.0.so too? I know the libusb 1.0 stuff added some functions since 9.x at least... maybe hps would know (Cc'd.) Juergen, I think this package is useful and is looking for maintainer, so if you have time and energy, I'm OK with upgrading it, but I suggest testing it first. Bjoern might be interested too. You mean bz@ ? Cc'd. I tried testing lsusb from debian sid but it printed nothing, neither with my nor with your older version, but maybe it's just `too new' for our current linuxolator. I assume you have at least 1 USB device while trying this. I don't remember exactly, but while trying within Linuxolator, you may need devfs/procfs to be mounted under Linuxolator's root directory. My understanding and from looking at trace is that if we cannot find it in /compat/linux we ale search in /; so no need for an extra mount unless maybe you run chrooted. So you'll have to figure this out. Does it return with 0 exit code? If not, lsusb should be simple enough to let you place printf() all over the place and understand out when it's failing. For me the problem was a clock_gettime() call in the libusb which my glibc did not provide. That made all things fail (silently) until I used linux “rtld tracing to see the unresolved symbol from libusb/the commercial 3rd party software dynamically loading libusb. — Bjoern A. Zeeb ? ??? ??? ??: '??? ??? ?? ??? ?? ?? ??? ??? ??? ? ? ?? ?? ? ', ? ?, ??? ? ?? ?, ?.??? ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: CFT: Re: linux libusb again, I made an updated port...
On Mon, Feb 10, 2014 at 11:06:27AM +, Bjoern A. Zeeb wrote: On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote: On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote: On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote: On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote: On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote: On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote: Hi! This came up on irc so I tried to build a linux libusb port (before I learned about ports/146895), mine uses linux_base-gentoo-stage3 like linux_kdump with a src/lib/libusb head snapshot so it's more up to date than wkoszek's build (ports/146895), and it's really easy to update it again. Also maybe it can be used as linux libusb-1.0.so too; I didn't actually test it tho. Should this be committed? Is wkoszek's version better since it also builds on 10.x? Comments welcome... wkoszek's version: http://www.freebsd.org/cgi/query-pr.cgi?pr=146895 Mine: http://people.freebsd.org/~nox/tmp/linux_libusb.shar Distfile: http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2 10/amd64 package: http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz (built via: poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb - btw for some reason the dependency emulators/linux_base-gentoo-stage3 doesn't build for 10i386 in poudriere bulk, I get a pkg segfault. bapt Cc'd...) Juergen, Hi! What would be the reason for this update? My stuff may be out of date, but it was all tested and working. I verified it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which this stuff was written. I was just thinking an updated version may be useful, but if it's already working for everyone maybe less so... Or would it work as a linux libusb-1.0.so too? I know the libusb 1.0 stuff added some functions since 9.x at least... maybe hps would know (Cc'd.) Juergen, I think this package is useful and is looking for maintainer, so if you have time and energy, I'm OK with upgrading it, but I suggest testing it first. Bjoern might be interested too. You mean bz@ ? Cc'd. I tried testing lsusb from debian sid but it printed nothing, neither with my nor with your older version, but maybe it's just `too new' for our current linuxolator. I assume you have at least 1 USB device while trying this. I don't remember exactly, but while trying within Linuxolator, you may need devfs/procfs to be mounted under Linuxolator's root directory. My understanding and from looking at trace is that if we cannot find it in /compat/linux we ale search in /; so no need for an extra mount unless maybe you run chrooted. So you'll have to figure this out. Does it return with 0 exit code? If not, lsusb should be simple enough to let you place printf() all over the place and understand out when it's failing. For me the problem was a clock_gettime() call in the libusb which my glibc did not provide. That made all things fail (silently) until I used linux ?rtld tracing to see the unresolved symbol from libusb/the commercial 3rd party software dynamically loading libusb. And my linux_kdump ends like this: 35607 lsusbCALL munmap(0x28247000,0x8000) 35607 lsusbRET munmap 0 35607 lsusbCALL linux_open(0x28090c31,0,0x28081e00) 35607 lsusbNAMI /compat/linux/dev/usbctl 35607 lsusbNAMI /dev/usbctl 35607 lsusbRET linux_open 3 35607 lsusbCALL linux_ioctl(0x3,0xffe5 ,0xc5d8) 35607 lsusbRET linux_ioctl 0 35607 lsusbCALL close(0x3) 35607 lsusbRET close 0 35607 lsusbCALL linux_exit_group(0x1) 35607 lsusbUNKNOWN(11) and the exit code is 1, so I guess it's failing on an unhandled syscall or something like that. Juergen ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
