From: Matthew Finkel <matthew.finkel@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT virtual stuff] gentoo vm appliance
Date: Wed, 22 Jun 2011 21:31:17 -0400 [thread overview]
Message-ID: <4E029765.9060903@gmail.com> (raw)
In-Reply-To: <1308787916.71397.4.camel@localhost.localdomain>
On 06/22/11 20:11, Albert Hopkins wrote:
>
> On Wednesday, June 22 at 16:52 (-0500), Harry Putnam said:
>
>> The times I've tried to get a recent gentoo version running in a vm on
>> windows turned out to be labor taking days to get right.
>>
>> Does anyone know if there is a fairly current gentoo appliance
>> somewhere that I can just install and then update or customize?
>>
>> I'd prefer to run it with vbox but if the appliance is vmware created
>> that's ok too. I do have a license up to 6.5.
>>
>> If that isn't available maybe someone has a fairly current kernel
>> config that is known to boot on a windows host with guest gentoo.
>>
>> As I recall from my efforts, there were always problems with something
>> to do with scuzzi drivers or whatnot.
> I have a program that I use to create Gentoo VM appliances. I have no
> idea if it works with vbox or vmware as I run KVM, but I think it
> *should* work. Anyway if you want to try it you can or, if you want, it
> also builds stage4 tarballs, so I can build you a stage4 tarball of a
> base Gentoo install pretty easily (including kernel). The stage4
> (excluding portage) would be ~90MB (bz2). The disk image (compressed
> QCOW is about 120MB)
The only issue with qcow2 is that in order to use it with VB, IIRC you
need to convert it to raw before you can import it.
next prev parent reply other threads:[~2011-06-23 1:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:52 [gentoo-user] [OT virtual stuff] gentoo vm appliance Harry Putnam
2011-06-22 22:32 ` Mark Knecht
2011-06-22 23:58 ` [gentoo-user] " Harry Putnam
2011-06-22 22:49 ` [gentoo-user] " kashani
2011-06-22 23:59 ` [gentoo-user] " Harry Putnam
2011-06-23 0:11 ` [gentoo-user] " Albert Hopkins
2011-06-23 1:31 ` Matthew Finkel [this message]
2011-06-23 2:14 ` Albert Hopkins
2011-06-23 4:35 ` Matthew Finkel
2011-06-23 11:15 ` Albert Hopkins
2011-06-23 16:32 ` Matthew Finkel
2011-06-23 16:52 ` Albert Hopkins
2011-06-25 17:10 ` Albert Hopkins
2011-06-27 23:47 ` James Wall
2011-06-28 0:46 ` Albert Hopkins
2011-06-28 3:44 ` James Wall
2011-06-28 13:07 ` Albert Hopkins
2011-06-28 14:32 ` James Wall
2011-06-28 14:57 ` Albert Hopkins
2011-06-28 16:19 ` Albert Hopkins
2011-07-01 15:36 ` [gentoo-user] " Harry Putnam
2011-07-01 15:50 ` Harry Putnam
2011-07-01 15:55 ` Albert Hopkins
2011-07-01 16:06 ` Albert Hopkins
2011-07-01 16:42 ` Harry Putnam
2011-07-01 17:56 ` Albert Hopkins
2011-07-01 19:10 ` Harry Putnam
2011-07-01 20:01 ` Alex Schuster
2011-07-01 20:02 ` Albert Hopkins
2011-07-01 22:44 ` James Wall
2011-07-01 23:23 ` Albert Hopkins
2011-07-02 0:22 ` Harry Putnam
2011-07-02 0:37 ` Albert Hopkins
2011-07-01 17:59 ` Albert Hopkins
-- strict thread matches above, loose matches on Subject: below --
2011-06-23 1:16 [gentoo-user] " Pandu Poluan
2011-06-23 2:16 ` Albert Hopkins
2011-06-23 7:54 ` Joost Roeleveld
2011-06-23 11:18 ` Albert Hopkins
2011-06-23 11:45 ` Joost Roeleveld
2011-06-23 13:12 ` Albert Hopkins
2011-06-23 14:13 ` Pandu Poluan
2011-06-23 16:49 ` Joost Roeleveld
2011-06-23 14:11 ` Pandu Poluan
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=4E029765.9060903@gmail.com \
--to=matthew.finkel@gmail.com \
--cc=gentoo-user@lists.gentoo.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