From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Test Hardware
Date: Sat, 30 Aug 2014 21:01:11 -0400 [thread overview]
Message-ID: <540273D7.6000706@gmail.com> (raw)
In-Reply-To: <20140830231759.GA8419@amelia.carfax.org.uk>
On 14-08-30 07:17 PM, Hugo Mills wrote:
> On Sat, Aug 30, 2014 at 04:47:07PM -0400, nick wrote:
>> Hey Guys,
>> I am wondering what test system(s)/hardware specs I need for testing btrfs code as I am wondering
>> due to thinking about a future budget for it.
>
> If your current hardware can do virtualisation, and you have a few
> (tens of) gigabytes of free disk space, then you don't need anything
> more. You can set up a virtual machine with a single disk image for
> the OS files, install a Linux distribution of your choice on it, and
> then create a bunch of sparse disk images:
>
> $ truncate -s 10G test-image.{1,2,3,4}
>
> Pass those to the VM as disk images, and you'll have four 10G disks
> in the VM to run xfstests on.
>
> I recommend using qemu for this, because once you've done the base
> install, you can use the -kernel, -append and -initrd options to the
> qemu-system-x86_64 command to pass your test kernel directly to the
> VM. This bypasses the BIOS emulation, and speeds up the boot process
> by a few seconds.
>
> The other thing I recommend doing is taking a copy of the base disk
> image after you've done the basic OS install -- that way, if something
> goes wrong, you can just delete the original and restore from the
> backup.
>
> If your machine doesn't have virtualisation support (and most
> machines made in the last few years do), then you can still do the
> above, but it'll just run rather more slowly.
>
> The above will take a few hours of fiddling and reading through
> qemu options, but once it's done, you can write a one-liner shell
> script to start your test VM, and you're all ready to run.
>
> Hugo.
>
>> Cheers Nick
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Thanks Hugo,
I really appreciate your answer :). Seems I need to pick up a new hard drive , how big is good? I am thinking of 2 TB because price is only 100 dollars and seems good if I need to use the disk later for other things.
Cheers Nick
prev parent reply other threads:[~2014-08-31 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 20:47 Test Hardware nick
2014-08-30 23:17 ` Hugo Mills
2014-08-31 1:01 ` nick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540273D7.6000706@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).