10-20-2018
Best tuning for qemu windows guest(windows 7)
In your opinion,which is the best tuning for windows 7 guest?
I use
cpu: host
mem: at least 2G,better 4G
disk: this is the most important,without "unsafe" cache is really slow and apply a 1G "service pack" can take 3 hours,with unsafe is really fast,actually I use
cache=unsafe
io=threads
discard mode=unmap
detect zeroes=unmap
network:virtio
controller:all virtio
Any suggestion,opinions?Thanks
4 More Discussions You Might Find Interesting
1. Solaris
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies
2. UNIX for Dummies Questions & Answers
As the title suggests I ran into a little problem trying to create a virtual machine of Kali Linux usign Qemu inside OpenBSD. I edited the example Kali Linux gave on their website here to the following for BSD:
qemu-system-i386 -hda ./kali.qcow2 -boot d -cdrom ./kali-linux-1.0.5-i386.iso -m... (0 Replies)
Discussion started by: Azrael
0 Replies
3. Linux
Hello, I installed FreeBSD 10.3 on AQEMU. I can't connect to internet in none
of the modes of "Default, User-Mode Networking" and "TUN/TAP Networking".
I am able to ping my host in the TAP networking mode (192.168.1.33 which is my
IP addr in guest), but getting 'no route to host' for any... (1 Reply)
Discussion started by: temp-usr
1 Replies
4. Red Hat
So we have a RHEL 7.6 workstation with 128 gigs of ram. The OS sees all the ram and 80 cors (40 HT)
We have 1 guest with 8 CPUs and 32gigs of ram running RHEL 7.6 workstation as well. We are trying to create another guest with 64 CPUs and 80 gigs of ram. We setup the system using... (0 Replies)
Discussion started by: joeg1484
0 Replies
VIOMB(4) BSD Kernel Interfaces Manual VIOMB(4)
NAME
viomb -- VirtIO memory ballooning driver
SYNOPSIS
virtio* at pci? dev ? function ?
viomb* at virtio?
DESCRIPTION
virtio(4) defines an interface for efficient, standard, and extensible I/O between the hypervisor and the virtual machine. The viomb driver
supports the virtio-compliant memory ballooning device.
Memory ballooning works as follows:
1. The host operator requests a guest to return some amount of memory to the host (via e.g. Qemu monitor balloon command).
2. The hypervisor sends the request via VirtIO memory ballooning device.
3. The guest viomb driver requests allocation of that amount of physical memory from the NetBSD memory management system.
4. The viomb device tells the hypervisor the guest physical memory address of the allocated memory via VirtIO memory ballooning device.
The sysctl node hw.viomb.npages shows the requested number of memory pages to return to the hypervisor, while hw.viomb.actual shows the
actual number of memory pages that are already returned to the hypervisor.
SEE ALSO
virtio(4), sysctl(8)
Rusty Russell, IBM Corporation, Virtio PCI Card Specification, http://ozlabs.org/~rusty/virtio-spec/.
HISTORY
The viomb device driver appeared in NetBSD 6.0.
BUGS
The userland interface should be same as the Xen ballooning device.
BSD
November 26, 2011 BSD