linux-kernel - Re: Kernel testing in a VM good idea?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e9e943910906290132odfb89c7t57ab1aca7203b476@mail.gmail.com>
Date:	Mon, 29 Jun 2009 09:32:16 +0100
From:	Duane Griffin <duaneg@...da.com>
To:	James Dolan <jamesdolan@...ar.net.nz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Kernel testing in a VM good idea?

2009/6/27 James Dolan <jamesdolan@...ar.net.nz>:
> Are there any disadvantages to testing/developing a kernel in a VM ? (i
> luck the availability of hardware)

To start with the obvious, with a VM you don't need extra hardware. If
you make a silly mistake and trash the filesystem all you need to do
is copy a file, not reinstall a whole system. The hack/install/test
cycle can be as quick and easy as "make && ./test.sh", instead of
requiring you to copy files across to another machine, reboot, etc.
You can easily script tests, e.g. to create and boot from a COW image,
drive the VM through its console, then run checks within the VM and
externally for whatever it is you testing. You can give those scripts
and images to others to use, too.

Cheers,
Duane.

-- 
"I never could learn to drink that blood and call it wine" - Bob Dylan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/