Reaction score: 144
Do not expect using USB 2/3 devices with VirtualBox guests since the Extension Pack (which provides USB passing-through) is not supported in FreeBSD.I'm thinking of installing VirtualBox and wondered if anyone could offer opinions/advice
It performs very well if your hardware supports virtualization and it's enabled (check you BIOS: VT-x or AMD-V).how well would a guest OS such as Windows 7 perform?
What's so special about OpenSuSE?
Yes, exactly, thanks scottroscottro said:my impression is that they meant that OpenSUse in their machine, as a VirtualBox guest, runs so well that if they didn't know it was a VBox guest, they would think it's bare metal
Yes, sorry for not having pointed that out. Actually balanga Vt-x is required only for 64-bit guests, but in any case, with Vt-x enabled, performance boost is relevant and couldn't be more evident, and I wouldn't run a modern graphical guest If I hadn't a UEFI with Vt-x support. Virtualization for I/O, Vt-d, is supported by Virtualbox as well, but I've never tried doing something related to it in Vbox (like VGA passthrough), whereas had it enabled under bhyve in order to passthrough my PCIe Wireless Internal NIC.aragats said:It performs very well if your hardware supports virtualization and it's enabled (check you BIOS: VT-x or AMD-V)
To check whether CPU supports Vt-x or not, you can look into dmesg:Is there a FreeBSD equivalent to `cat /proc/cpuinfo` from the Linux world?
cat /var/run/dmesg.boot | egrep CPU. If available, there should be a string dedicated to VT-x support, while eventual EPT availability should be listed under "features"
sysctl machdep.cpu.features, but I don't know if such a machdep variable is available under FreeBSD
You could try sysutils/lscpu. For my system, the output isIs there a FreeBSD equivalent to `cat /proc/cpuinfo` from the Linux world?
Architecture: amd64 Byte Order: Little Endian Total CPU(s): 8 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 Vendor: GenuineIntel CPU family: 6 Model: 94 Model name: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Stepping: 3 L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8M Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 cflsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline aes xsave osxsave avx f16c rdrnd fsgsbase tsc_adjust sgx bmi1 hle avx2 smep bmi2 erms invpcid rtm fpcsds mpx rdseed adx smap clflushopt intel_pt syscall nx pdpe1gb rdtscp lm lahf_lm lzcnt
grepas suggested by Sensucht94 is probably sufficient.
Reaction score: 1,161
dmesg | grep Feature
The lines are "broken", you should add
-A1(1 line after as well):
dmesg | grep -A1 Feature
dmesg | grep -A1 Feature
Features=0xbfebfbff<FPU,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=0x1fbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX> AMD Features=0x28100000<NX,RDTSCP,LM> AMD Features2=0x1<LAHF> XSAVE Features=0x1<XSAVEOPT> VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID
It works very well on my system. I forget when I put my current system together, but it's years old at this point. Just make sure you've got plenty of RAM and give it a processor core or two. At this point having enough RAM to give to the VM and have available to the system is probably a bigger issue than processing power is.I'm thinking of installing VirtualBox and wondered if anyone could offer opinions/advice on how easy it is to set up and use, what are the hardware requirements and how well would a guest OS such as Windows 7 perform?
If you have Bhyve enabled, you'll need to unload its kernel module or VirtualBox won't start a VM:
kldunload vmm. You might then need to load VirtualBox's modules:
kldload vboxdrv vboxnet. Or you can simply make the /etc/rc.conf mods listed in the Handbook, comment out the /boot/loader.conf line loading vmm.ko, and reboot.
Reaction score: 330
Just in case your question is about installing Vbox on a T420...This is on a ThinkPad T420.
I been using Virtualbox since learning how to install it (it took a year after it was invented for FreeBSD). From that that I never had a issue with it. I even installed the official Windows 7- Upgrade DVD inside a empty Virtualbox … it took as a full RELEASE of Windows-7I'm thinking of installing VirtualBox and wondered if anyone could offer opinions/advice on how easy it is to set up and use, what are the hardware requirements and how well would a guest OS such as Windows 7 perform?
dd if=/dev/ada0s14 of=/dev/ada1s14 bs=64k - backing up FBSD-2
272-Active 236-Inactive 5892-Wired 404-Buf 9011M-Free FreeBSD vBox Running 12-Active 2-Inactive 16-Wired 0-Buf 10G-Free Memory retain after shutdown
I don’t think I understand the question correctly. The only way to safely move a VM is to DD the entire partition. For me the only hope would be if I had Windows-7 already in a Virtualbox somewhere on the same hard drive IN IT’S OWN PARTITION, I would get another hard-drive … partition it off the way I need it to be (a brand new everything, might as well) but when you get to the one that is in the same LOCATION as the other one … I would partition it to the exact size or larger and dd the Windows-7 partitions to that location on the new hard drive. Understand, this location would be the guest of whatever, wherever the new host will be.Given the positive feedback about how well Windows performs under VirtualBox, I think I need to give it a try... So how should I set about 'moving' Windows 7 from my 256GB mSata drive to being a guest under VirtualBox on the same drive?
sda1 FreeBSD sda2 Linux sda3 Windows sda5 D:/ my stuff sda6 E:/ more stuff sda7 F:/ virtualbox-FreeBSD-8.2 sda8 G:/ virtualbox-Linux sda9 H:/ virtualbox-Windows-7 sda10 I/ . . .