4000 Linux VT Solutions: Difference between revisions

 
 
(8 intermediate revisions by 2 users not shown)
Line 2: Line 2:


* KVM/Qemu - I dig [[KVM]]. Always have. It slapped an open kernel module between cheap COTS [[4000_Linux_VT_Solutions#VT_Hardware|VT hardware]] and the open, feature-rich qemu frontend, fixed and stabilized aforementioned frontend, and has been pretty awesome for years.
* KVM/Qemu - I dig [[KVM]]. Always have. It slapped an open kernel module between cheap COTS [[4000_Linux_VT_Solutions#VT_Hardware|VT hardware]] and the open, feature-rich qemu frontend, fixed and stabilized aforementioned frontend, and has been pretty awesome for years.
** If you have [[VT]], use kvm. Otherwise, qemu's closed-source hoopajoop module can provide a bit better performance than unaccelerated kvm/qemu. You'll want to set up a large tmpfs ''FIXME import from researchwiki''...
** If you have VT, use kvm. Otherwise, qemu's closed-source hoopajoop module can provide a bit better performance than unaccelerated kvm/qemu. You'll want to set up a large tmpfs ''FIXME import from researchwiki''...
** There's GUIs for these, but they're uglier than they're worth.
** There's GUIs for these, but they're uglier than they're worth.
* Xen - A juggernaut -- the Oracle to these 4000 solutions' fractured MySQL and postfreshSQL communities. I've ignored it almost completely, largely out of spite and contrarianism.
* Xen - A juggernaut -- the Oracle to these 4000 solutions' fractured MySQL and postfreshSQL communities. I've ignored it almost completely, largely out of spite and contrarianism.
Line 33: Line 33:
If stymied in your search for expected VT, inspect your BIOS to ensure it hasn't been disabled there.
If stymied in your search for expected VT, inspect your BIOS to ensure it hasn't been disabled there.


==I just need a VPS mang!==
==[[FreeBSD]] guests==
I have chartered a [http://www.1and1.com 1and1] Linux VPS since 2009-01-01, and find it pretty damn reasonable.
* On FreeBSD11+, the <tt>vt</tt> driver has replaced the <tt>sc</tt> console driver. So far as I am aware, the latter is necessary to use <tt>vidcontrol</tt> to change virtual screen resolution. Once <tt>kern.vty=sc</tt> is added to <tt>/boot/loader.conf</tt>, qemu using the <tt>-vga std</tt> arguments ought be able to do high resolution with e.g. <tt>vidcontrol MODE_401</tt> (1920x1080x24). Once the mode is verified, it can be set on boot by adding an e.g. <tt>allscreens_flags="MODE_401"</tt> line to <tt>/etc/rc.conf</tt>.
 
* If your boot locks up, ensure you've provided <tt>-serial stdio</tt>. See [https://docs.netgate.com/pfsense/en/latest/troubleshooting/boot-issues.html#Booting_with_an_alternate_console Booting with an alternate console] at NetGate and [https://www.digitalocean.com/community/tutorials/how-to-recover-from-file-system-corruption-using-freebsd-s-single-user-mode Recovering File System Corruption] from DigitalOcean.
 
==See also==
* [[SR-IOV]]