Then this sentence, recommendation should be rewritten. There’s no
reason to not copy the files if doing it the proper way preserving
--sparse-always.
This page seems centered around VBox for all aspects. It would be too much to duplicate for all KVM related instructions. Anyhow, the user base for KVM is already much more knowledgeable that such instructions would be overkill. Not out of elitism, but the install process itself is unfortunately a major filter for those who wouldn’t know how to set RAM to begin with.
1 Like
OK corrected
1 Like
That wiki page has been improved just now. It is now using a tab controller which makes it easy to switch the virtualizer which shows/hides the other virtualizer.
Shouldn’t be duplicated but would be good to shorten wiki/KVM by moving into the proper specialized wiki pages.
@HulaHoop is this still true? meaning if LVM used we can rely on it without spice? does this as well improve other hypervisors like Virtualbox?
1 Like
How is LVM related to spice?
LVM is a disk partitioning tool, while spice is a graphics/media transfer protocol. There is a RAW disk mode in KVM where underlying disk storage is accessed directly without isolation, but the security consequences and data confidentiality violations are pretty evident.
Malware could recover deleted files from the host disk or inject malicious IO commands to the hardware.
2 Likes
Current KVM page looks like this.
Fixed it by removing thumb description:
<code>Unofficial logo re-creation for the [https://www.linux-kvm.org KVM] virtualizer</code>
No idea how to reback it while keeping the page looks nice.
1 Like
Well i thought the vt-x is the issue, but i checked the BIOS and the vt-x is actually enabled, i also thought my PC is old and the vt-x is just not working anymore, but i tried another VMs in KVM and so as Virtualbox = working?!
So i think investigation need to be done, im happy to provide any further logs (my ticket is the first one).
1 Like
Try a Debian VM.
VirtualBox used to work without hardware virtualization support with good speed too. This feature might not be deprecated.
KVM cannot do that. QEMU maybe but dunno speed.
You cannot have VirtualBox and KVM installed at the same time. This might cause the same error message.
1 Like
First time i hear this, since when?
Dunno when. I think old feature before hardware virtualization was invented? The when isn’t important.
https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/features-overview.html
No hardware virtualization required. For many scenarios, Oracle VM VirtualBox does not require the processor features built into current hardware, such as Intel VT-x or AMD-V. As opposed to many other virtualization solutions, you can therefore use Oracle VM VirtualBox even on older hardware where these features are not present. See Hardware vs. Software Virtualization.
Compare the xml files of VMs that you can use versus not use.
1 Like
QEMU would probably work but unsupported.
related:
Not sure how that works.
https://docs.oracle.com/en/virtualization/virtualbox/6.0/admin/hwvirt.html
Oracle VM VirtualBox’s 64-bit guest and multiprocessing (SMP) support both require hardware virtualization to be enabled. This is not much of a limitation since the vast majority of 64-bit and multicore CPUs ship with hardware virtualization. The exceptions to this rule are some legacy Intel and AMD CPUs.
Since Whonix downloadable images are for 64-bit (32-bit or 64-bit?), this shouldn’t work. But since @nurmagoz confirmed VirtualBox works, seems VirtualBox has somewhat better out of the box legacy hardware support.
1 Like
Figured out this issue, this is seems to be Debian (or Kernel) VS my PC issue:
If TPM activated from the BIOS:
It will appear at the beginning of the OS booting (quickly disappear):
kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
To solve it one need to disable TPM feature:
Dunno if this is reported upstream or not.
1 Like
1 Like
Can you test some KVM with EFI please? @HulaHoop
KVM EFI support might have considerably improved meanwhile. For example, Debian nowadays can be easily installed on EFI and even SecureBoot enabled systems.
Therefore would be good to test both, EFI and SecureBoot.
Then making any changes to the Whonix libvirt KVM config files to support EFI, SecureBoot.
Yet to be decided if EFI (and maybe later SecureBoot) will become the new default for Whonix VMs as per:
1 Like
If there is anything that needs help with or requires testing please do let me know
1 Like
Btw please Follow Whonix Developments for news. If there are major testers wanted announcements, these will be posted in the news forums.
1 Like