public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT virtual stuff] gentoo vm appliance
Date: Thu, 23 Jun 2011 18:49:19 +0200	[thread overview]
Message-ID: <14709927.3KDTlEEv4W@eve> (raw)
In-Reply-To: <1308834735.3657.5.camel@stretch>

On Thursday 23 June 2011 09:12:15 Albert Hopkins wrote:
> On Thursday, June 23 at 13:45 (+0200), Joost Roeleveld said:
> > > Yes the stage4 should work similarly.  However Pandu was asking
> > 
> > about
> > 
> > > building ".xva" which I know nothing about, unless an .xva is
> > 
> > similar
> > 
> > > to/same as a stage4 (I have no idea)?
> > 
> > .xva is a format specifically for Citrix Xen.
> > 
> > There are tools to convert "classic" Xen VMs to "xva" files:
> > http://www.xen.org/files/xva/README
> > 
> > I would be willing to assist in getting this tool to work with your
> > program.
> > All I'd need is a copy of your program along with assistance from
> > Pandu Poluan
> > to test the resulting XVA files.
> > 
> > I do not run Citrix XenServer and have no need for it as Xen itself
> > works fine
> > for me.
> 
> Thank you. I downloaded the xva.py script and created a target to
> create .xva files.  The script appeared to run fine.  No errors, but I
> cannot verify that the .xva is good.  I used hvm and converted the raw
> image.  The .xva is 4.1G whereras the original raw image is only 414MB
> (sparse).  The .xva appears to be a tar file, but I guess w/o the -S
> flag passed to gnu tar.

Yes, that's what I read on the web as well. A tar-file filled with silly-named 
files and an XML-file containing the configuration. :)

> My program is hosted on bitbucket[1].  The documentation for it is
> outdated.
> 
> -a
> 
> [1] https://bitbucket.org/marduk/virtual-appliance/wiki/Home

I'll have a look at it later.

-- 
Joost



  parent reply	other threads:[~2011-06-23 16:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  1:16 [gentoo-user] [OT virtual stuff] gentoo vm appliance 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 [this message]
2011-06-23 14:11     ` Pandu Poluan
  -- strict thread matches above, loose matches on Subject: below --
2011-06-22 21:52 Harry Putnam
2011-06-22 22:32 ` Mark Knecht
2011-06-22 22:49 ` kashani
2011-06-23  0:11 ` Albert Hopkins
2011-06-23  1:31   ` Matthew Finkel
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

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=14709927.3KDTlEEv4W@eve \
    --to=joost@antarean.org \
    --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