From: Jared Rhine <jared@wordzoo.com>
To: xen-devel@lists.sourceforge.net
Subject: XenCD xm save problem
Date: Thu, 10 Feb 2005 14:50:08 -0800 [thread overview]
Message-ID: <87hdkk2fof.wl@badger.wordzoo.com> (raw)
In-Reply-To: <874qglcm9t.wl@badger.wordzoo.com>
[Jared == jared@wordzoo.com on Wed, 09 Feb 2005 16:05:18 -0800]
Jared> I can duplicate the problem that xm save does not work on
Jared> XenCD.
Others have reported success after switching to Xen 2.0.4, but my
XenCD save problem still exists with a 2.0.4-built snapshot.
From my last email:
-- begin --
Possibilities:
Do I need to patch sarge's udev to create a /dev/loop device?
Should I be digging into xend code to see how it uses /dev/loop? I'm
still wrapping my head around xend and I can't find "loop" in a grep
of the tree.
Is there something about tmpfs that makes xm save work for others but
not XenCD? XenCD's Xen installation is as absolutely vanilla as I can
make it, other than tmpfs. And ttylinux is running on a loopback
ext2.
Apologies if I'm missing something obvious.
-- end --
Details available in my last message.
-- jared@wordzoo.com
"Better to be of a rare breed than a long line." -- TDK
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
next prev parent reply other threads:[~2005-02-10 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 0:05 XenCD xm save problem Jared Rhine
2005-02-10 22:50 ` Jared Rhine [this message]
2005-02-10 23:31 ` Arthur Bergman
2005-02-11 0:40 ` Jared Rhine
2005-02-11 8:13 ` Arthur Bergman
2005-02-12 7:56 ` XenCD xm save problem: solved by 2.0.4 Jared Rhine
2005-02-14 13:32 ` Arthur Bergman
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=87hdkk2fof.wl@badger.wordzoo.com \
--to=jared@wordzoo.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.