Sponsored Content
Full Discussion: QEMU performance?
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing QEMU performance? Post 302930185 by sea on Wednesday 31st of December 2014 05:12:34 AM
Old 12-31-2014
Computer QEMU performance?

Heyas

So, i like doing custom a LiveImage of my OS.
Using Redhats kickstart/livecd-creator method.

Anyway, so i would like to test the liveimages...
AND also, i WOULD like to install FreeBSD, Solaris, or whatever, onto a Virtual Machine.

I used to use Oracles Virtualbox, but eversince i'm booting with SecureBoot enabled, i'm no longer able to start it, so i had to change to QEMU.

Now, to just 'test' if the fresh generated iso is 'working' or not, QEMU is just fine.
But if i ever want to actualy do in QEMU, like, switching desktop, or changing the folder in pcmanfm inside QEMU, it needs patience out of this world...

I'm running my ISO's like this:
Code:
#!/bin/bash
# isotest
# Description:	Simply boots an iso file with qemu.
# ------------------------------------------------------
#
#	Variables
#
	DEFAULT_ARCH=x86_64
	DEFAULT_ARCH=$(uname -m)
	DEFAULT_RAM=$(( 4 * 1024 ))
	DEFAULT_CORES=4
	DEFAULT_VGA=vmware
	DEFAULT_FORMAT=qcow2
	DEFAULT_SIZE=5G
	DEFAULT_IMAGE_DIR=$HOME/Virtual_Machine_Images
	DEFAULT_IMAGE_FILE=isotest.img
#
#	Display & Action
#
	qemu-system-$DEFAULT_ARCH \
		-smp $DEFAULT_CORES \
		-m $DEFAULT_RAM \
		-cdrom "$1"

And to 'install' or run an intalled image i execute:
Code:
#!/bin/bash
# distrotest
# Description:	Simply boots an OS file with qemu.
# ------------------------------------------------------
#
#	Variables
#
	DEFAULT_ARCH=x86_64
	DEFAULT_ARCH=$(uname -m)
	DEFAULT_RAM=$(( 4 * 1024 ))
	DEFAULT_CORES=4
	DEFAULT_VGA=vmware
	DEFAULT_FORMAT=qcow2
	DEFAULT_SIZE=5G
	DEFAULT_IMAGE_DIR=$HOME/Virtual_Machine_Images
	DEFAULT_IMAGE_FILE=distrotest.img
#
#	Functions
#
	DEFAULT_IMAGE="$DEFAULT_IMAGE_DIR/$DEFAULT_IMAGE_FILE"
	[[ -f "$1" ]] || exit 1
	if [[ ! -f "$DEFAULT_IMAGE" ]]
	then	# We just need an image to boot an iso, this can be quite small.
		qemu-img create -f "$DEFAULT_FORMAT" "$DEFAULT_IMAGE" $DEFAULT_SIZE
	fi
#
#	Display & Action
#
	qemu-system-$DEFAULT_ARCH \
		-smp $DEFAULT_CORES \
		-m $DEFAULT_RAM \
		-cdrom "$1" \
		-hda "$DEFAULT_IMAGE"
# 		-full-screen \

As you see, i'm quite, sharing?, with my hardware for qemu...
4 Cores and 4 GB of ram, but booting an ISO (same for installed) takes up to ~7mins, when with O-VB it was as low as ~1min -- using 768mb ram and 70% of 1 core....

Doing a mouse click and wait for like 20 secs for ANYTHING to happen, is just annoying.

Any ideas or advices please?
Thank you in advance
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Anyone ever used qemu and networked it ?

hi i got a virtual linux machine running on qemu my problem is connecting it to the internet im a bit confused weather i have to make a virtual network card in qemu and than tun tap it? can anyone thats done it before help me out? (1 Reply)
Discussion started by: russian460
1 Replies

2. Filesystems, Disks and Memory

QEMU not booting my image

hello all, I have been trying to boot an image (.IMG) using qemu, for quite some time now and i can't seem to get it to work. I've been able to boot from the Windows XP CD, the Debian iso image, etc, so I know qemu is configured properly and is working. But when it come to booting an image that I... (34 Replies)
Discussion started by: neur0n
34 Replies

3. Programming

Qemu + gdb

Hi, I got: host machine: RedHat (RHEL6) virtual machine: RedHat (RHEL6) I run (on host machine): qemu-system-x86_64 ...... -S -s after that i run (on host machine): gdb target remote localhost:1234 set architecture i386:x86-64 and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies

4. AIX

IBM AIX and QEMU Emulator?

Hi friends, I am a UNIX lover. I have tried several unix flavors including linux, solaris(x86) and FreeBSD, all these are the unices which can be installed on x86 hardware. Now to use the IBM AIX, I searched and googled alot, finally I came across QEME, which emulates the PowerPC platorm to turn... (9 Replies)
Discussion started by: gabam
9 Replies

5. Programming

Running c code in ARM QEMU

I created and Compiled a C program to run in QEMU for ARM. When I run the program using the command #qemu-arm -L /home/arm-2010.09/arm-none-linux-gnueabi/libc ./test it gives me the following error: If 'qemu-arm' is not a typo you can use command-not-found to lookup the package that contains... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

6. Red Hat

help about qemu-kvm boot with initrd

I used the redhat RHEL6 boot with initrd but it failed, can sb help me # /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram... (4 Replies)
Discussion started by: yanglei_fage
4 Replies

7. IP Networking

Create a Bridge for Qemu using only loopback

hello networking folks, i have 3 virtual machines that need to talk to each other How can i create a bridge to loopback ? -net tap,vlan=0,ifname=tap1 where tap1 is connected to lo:1 , tap2 is connected to lo:2 etc thx (0 Replies)
Discussion started by: TwiceDone
0 Replies

8. BSD

How to install Ultrix 4.2 on Qemu?

Hi Problem changed. I've got a message showing on the screen which says Guest has not initialized the display (yet) Any how I can fix this? Thanks Jack (4 Replies)
Discussion started by: lucky7456969
4 Replies
libguestfs-test-tool(1) 				      Virtualization Support					   libguestfs-test-tool(1)

NAME
libguestfs-test-tool - Diagnostics for libguestfs SYNOPSIS
libguestfs-test-tool [--options] DESCRIPTION
libguestfs-test-tool is a test program shipped with libguestfs to allow you to check basic libguestfs functionality is working. This is needed because libguestfs occasionally breaks for reasons beyond our control: usually because of changes in the underlying qemu or kernel packages, or the host environment. If you suspect a problem in libguestfs, then just run: libguestfs-test-tool It will print lots of diagnostic messages. If it runs to completion successfully, you will see this near the end: ===== TEST FINISHED OK ===== and the test tool will exit with code 0. If it fails (and/or exits with non-zero error code), please paste the complete, unedited output of the test tool into a bug report. More information about reporting bugs can be found on the http://libguestfs.org/ website. OPTIONS
--help Display short usage information and exit. --qemu qemu_binary If you have downloaded another qemu binary, point this option at the full path of the binary to try it. --qemudir qemu_source_dir If you have compiled qemu from source, point this option at the source directory to try it. -t N --timeout N Set the launch timeout to "N" seconds. The default is 600 seconds (10 minutes) which does not usually need to be adjusted. -V --version Display the libguestfs version number and exit. TRYING OUT A DIFFERENT VERSION OF QEMU
If you have compiled another version of qemu from source and would like to try that, then you can use the --qemudir option to point to the qemu source directory. If you have downloaded a qemu binary from somewhere, use the --qemu option to point to the binary. Note when using these options, you can ignore the business of qemu wrapper scripts ("QEMU WRAPPERS" in guestfs(3)), since libguestfs-test- tool writes a wrapper script for you if one is needed. TRYING OUT A DIFFERENT KERNEL
If you are using supermin / febootstrap >= 3.8 then you can select which kernel libguestfs tries. You do this by setting the environment variables "SUPERMIN_KERNEL" and/or "SUPERMIN_MODULES" ("FEBOOTSTRAP_KERNEL" and "FEBOOTSTRAP_MODULES" if still using the old febootstrap 3.21 program). Refer to "ENVIRONMENT VARIABLES" in supermin-helper(8) for further information. TRYING OUT A DIFFERENT VERSION OF LIBVIRT
To find out which backend is the default in your libguestfs package, do: unset LIBGUESTFS_BACKEND guestfish get-backend If you are using the libvirt backend, then you can try out a different (eg. upstream) version of libvirt by running these commands (not as root): killall libvirtd lt-libvirtd ~/path/to/libvirt/run libguestfs-test-tool The first command kills any session "libvirtd" process(es) that may be running on the machine. The second command uses libvirt's "run" script (in the top-level libvirt build directory) to set some environment variables so that the alternate version of libvirt is used to run the program. TRYING OUT WITH
/ WITHOUT LIBVIRT To find out which backend is the default in your libguestfs package, do: unset LIBGUESTFS_BACKEND guestfish get-backend If you are using the libvirt backend, you can try without (ie. libguestfs directly launching qemu) by doing: export LIBGUESTFS_BACKEND=direct Or if you are using the default (direct) backend, then you can try libvirt: export LIBGUESTFS_BACKEND=libvirt or with libvirt and a specific libvirt URI: export LIBGUESTFS_BACKEND=libvirt:qemu:///session TRYING OUT DIFFERENT SELINUX SETTINGS
To find out which backend is the default in your libguestfs package, do: unset LIBGUESTFS_BACKEND guestfish get-backend To find out if SELinux is being used, do: getenforce If you are using libvirt, SELinux and sVirt, then you can try to see if changing SELinux to "permissive" mode makes any difference. Use this command as root: setenforce Permissive If this makes a difference, look in the audit logs for recent failures ("AVCs"): ausearch -m avc -ts recent You can convert AVCs into suggested SELinux policy rules using tools like audit2allow(1). For more information, see the "Security Enhanced Linux User Guide". To reenable SELinux and sVirt, do: setenforce Enforcing SELF-DIAGNOSIS Refer to "APPLIANCE BOOT PROCESS" in guestfs(3) to understand the messages produced by libguestfs-test-tool and/or possible errors. EXIT STATUS
libguestfs-test-tool returns 0 if the tests completed without error, or 1 if there was an error. ENVIRONMENT VARIABLES
For the full list of environment variables which may affect libguestfs, please see the guestfs(3) manual page. SEE ALSO
guestfs(3), http://libguestfs.org/, http://qemu.org/. AUTHORS
Richard W.M. Jones ("rjones at redhat dot com") COPYRIGHT
Copyright (C) 2009-2013 Red Hat Inc. LICENSE
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. BUGS
To get a list of bugs against libguestfs, use this link: https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools To report a new bug against libguestfs, use this link: https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools When reporting a bug, please supply: o The version of libguestfs. o Where you got libguestfs (eg. which Linux distro, compiled from source, etc) o Describe the bug accurately and give a way to reproduce it. o Run libguestfs-test-tool(1) and paste the complete, unedited output into the bug report. libguestfs-1.22.6 2013-08-24 libguestfs-test-tool(1)
All times are GMT -4. The time now is 03:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy