[Discuss] Virt-Manager

[markw at mohawksoft.com]

Generally speaking, VMware, HyperV, XEN, and QEMU (KVM) do not emulate the
CPU. The later processors have a mode where they can set up an environment
that is a hardened "sandbox." The software in the sandbox do not really
know that they are in a sandbox. All instructions seem to operate as
expected except for those instructions that think they are dealing with
privileged access. When this happens, the processor traps execution and
jumps to an emulation routine in the hypervisor that manipulates the state
of the VM.

If you are running ARM code on an x86_64 system, you are absolutely
emulating each instruction.

Containers are different, think of them as "chroot" processes with OS hooks.


> Should have gone to the list. Sorry.
>
> On 10/21/21 4:02 PM, Edward wrote:
>> On 10/20/21 22:34, markw at mohawksoft.com wrote:
>>
>>> KVM/QEMU has completely changed how I do software development. I almost
>>> *never* run make in my "work station" environment. I am always
>>> compiling
>>> in a specific VM.
>>>
>>> Anyway, have fun. Virtualization is a little heavier than containers,
>>> but
>>> well worth getting to know better.
>>
>> I was successful installing the LXQt flavors of Lubuntu and PCLinuxOS
>> (PCLOS) into virtual machines and they work well. With PCLOS, the
>> desktop kept repeatedly flashing running it from the live image, so
>> once rebooted but selecting the safe graphics mode at boot, the
>> desktop was then fine and it apparently installed using that same
>> mode, but the desktop resolution is limited to 1600x900. If I select
>> anything wider or larger, it cuts off the bottom of the window. I
>> could move the LXQtPpanel to the top of the screen, but I am used to
>> using it at the bottom.
>>
>> I question whether the VM software emulates a /virtual/ CPU?? In
>> PCLOS, running neofetch in a terminal, displayed the CPU as an AMD
>> Opteron 23xx (Gen 3 Class Opteron) (2) @ 3.199GHz. The actual on-board
>> CPU is an AMD Athlon II X2 260 (2) @ 3.200GHz.
>>
>> I also installed Fedora's LXQt Spin, which took the least amount of VM
>> configuring before the installation, however Fedora 34 did not have
>> the latest LXQt packages (had 0.16, latest is 0.17, next version may
>> be version 1.0) and some of the menus were actually missing their
>> icons./If it were me, I would not have released it with missing icons.
>> /So I deleted the Fedora VM, wasn't happy with it.
>>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>