Timeline for qemu with kvm guest OS is slow
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 9, 2015 at 23:56 | history | migrated | from serverfault.com (revisions) | ||
| Nov 9, 2015 at 21:06 | comment | added | Bendy | Here's some info about NTFS. I dont know alot about it personally. Using an SSD won't change the logical bottlenecks, but it does give you a lot more i/o to brute force through the bottlenecks. For an OS with a GUI, I think SSD disk speeds are a must. | |
| Nov 9, 2015 at 21:05 | comment | added | Bendy | The goal should be getting the host operating system out of the way - so if the encryption done by host's kernel, that's another performance hit. The host kernel is running the virtualization software and running a filesystem under the guest OS, and doing the decryption on the fly for the guest OS. Using an LVM volume isolates the disk operations, leaving the host to just run the virt process. | |
| Nov 9, 2015 at 20:32 | comment | added | user312344 | I can try using a LVM volume. Would using LUKs encryption on the LVM in turn repeat the same bottle neck or would it work a bit faster than having an encrypted file volume mounted? As for encrypting the data on the Windows side what kind of software should I look into for protecting the data? Would this bottleneck be relieved if I were to place the encrypted container on an ssd? | |
| Nov 9, 2015 at 19:33 | history | answered | Bendy | CC BY-SA 3.0 |