summary refs log tree commit diff stats
path: root/results/classifier/108/other/1777293
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/1777293')
-rw-r--r--results/classifier/108/other/177729328
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/108/other/1777293 b/results/classifier/108/other/1777293
new file mode 100644
index 000000000..fe1e22bd9
--- /dev/null
+++ b/results/classifier/108/other/1777293
@@ -0,0 +1,28 @@
+semantic: 0.716
+graphic: 0.516
+device: 0.344
+other: 0.318
+performance: 0.258
+permissions: 0.171
+debug: 0.123
+boot: 0.104
+network: 0.101
+vnc: 0.068
+PID: 0.062
+files: 0.028
+socket: 0.025
+KVM: 0.018
+
+[REQUEST] SHARING MEMORY WITH HOST
+
+Instead of a preallocated memory heap I would like for QEMU to share memory using shm. 
+
+Example: Instead of using 16gb out of 32gb of ram to run Windows 10, there would be no option to allocate it, but to share the hosts resources; ie giving the host full access to the entire ram stack
+
+
+I'm not a great programmer but I'm pretty sure QEMU's team could find this useful
+
+Sorry, but I have a hard to to imagine what you exactly mean here. Do you mean a possibility for one application in the guest and one in the host to share a piece of memory? Or do you mean that the operating systems in the host and guest should somehow share the memory (why?)? Or do you just look for a possibility to avoid that the guest has a lot of memory allocated to it when it does not need it? In the latter case, there is already virtio-balloon, so you should have a look at the virtio drivers if you need something like this.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+