Tree: a8a3ca5102

master

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

001

002

003

004

005

006

007

008

009

010

011

012

013

014

015

016

017

018

019

020

021

022

023

024

025

026

027

028

029

030

031

032

033

033-502

034

035

036

037

038

039

040

041

042

043

044

045

046

047

048

049

050

051

052

053

054

055

056

RHEL-7.1

RHEL-7.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'a8a3ca5102'

${ noResults }

Commit Graph

5 Commits (a8a3ca51026a017cb561458d7566477e03a421a2)

Author	SHA1	Message	Date
Harald Hoyer	2f692e8ff8	silently run qemu	16 years ago
Harald Hoyer	008bb4f22c	/dev/kvm is a char device	16 years ago
Harald Hoyer	2281815799	set u+x for run-qemu	16 years ago
Andreas Thienemann	8a4b60d9b2	Support different virtualization technologies for run-qemu. ... If the host supports kvm, use is. If this is not the case but the kqemu module is loaded, run qemu with kqemu optimization. Otherwise fall-back to pure usermode qemu.	16 years ago
Victor Lowther	ac6da96cc8	Make running qemu a little more generic ... Also create the root filesystem from within the virtual env, this way there will be no nasty suprises w.r.t interactions with the host machine. This is important when we test booting to LVM, LUKS, and mdraid.	16 years ago