100 karma · joined December 31, 2010
Possibly one of the most trustworthy pieces of software there is.
QEMU is an emulator, it isn't by itself capable of doing virtualization. It can allow a hypervisor to do CPU (and some I/O) virtualization in lieu of QEMU doing binary translation/emulation. In that case QEMUs purpose is mainly I/O emulation. 'Virtualization' as a name and concept predates QEMU by several decades.
> KVM is merely the kernel infrastructure that enables ring-0 access for faster hardware access. For many years it was called qemu-kmod; to this day the actual process that you run is called 'kvm-qemu.'
kqemu and KVM are technologically unrelated.
> You are overstating the difference between 'virtualization' and 'emulation.' There really isn't one. What used to be called 'emulation' is nowadays called 'full-virtualization' as opposed to 'paravirtualization.' QEMU, KVM, and XenKVM are full-virt, while traditional Xen is paravirt.
Para-Virtualization is the concept where the guest OS is aware that it is being run on a hypervisor. For example using hypervisor hypercalls to create new address spaces rather than setting up hardware page tables. "Full" or hardware level virtualization happens when the guest OS does not need to be aware of this fact. Neither is related to emulation.
> KVM is not a hypervisor;
It is.
> libvirt is.
This one isn't.
> Xen blurs the line between virtualization platform and hypervisor because both pieces ship within the same project. Either libvirt or Xen can act as hypervisor for QEMU or KVM.
"hypervisor":"virtualization platform" ~ "kernel":"operating system". KVM and Xen can act as hypervisor for Qemu managed by libvirt.
Well, yes. That's how you assemble space stations :)
What do you compare it with? I have one too (but currently dead due to infamous reset loop bug) and I think it is the worst ThinkPad I have owned. The screen is horrible, lackluster build quality and fit'n'finish, so so Linux support and the underside of the keyboard needed to be stuffed with cardboard to type properly. Given the budget price point I don't think it should carry a ThinkPad label at all, it tarnishes the brand.
Edit: I have the AMD Fusion, not the Intel variant.
Unless you have a virtually indexed cache I don't see why an OS would want to do that.
http://www.kosmos-shop.de/Experimentierkasten-640132/Kosmos-...
I only had the electronic sets as a kid, so I don't know how much the chemical ones have been dumbed down since.
Edit: Seems to work in Parallels.
Edit 2: Boots in Parallels but is not very usable. Hangs very often, Parallels Tools do not work. Now trying in VirtualBox.
Edit 3: VirtualBox works as good or bad as Parallels. Native install seems to be the best option. Did someone try to install onto an external drive?
No, disabling WP in CR0 is only relevant for privileged code. Writes to write protected pages in user mode will still trap. It might mess up some in-kernel COW stuff though.
My decision to work in the US wasn't based in any way on expected compensation but rather on the excitingness of the job. Still, it's nice to be treated well as an employee.