From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nazar 'Anesth' <anesth@unixway.org.ua>
Cc: xen-devel@lists.xensource.com
Subject: Re: Trouble with cryptsetup
Date: Tue, 4 May 2010 10:41:17 -0400 [thread overview]
Message-ID: <20100504144117.GA15544@phenom.dumpdata.com> (raw)
In-Reply-To: <201004241447.14447.anesth@unixway.org.ua>
On Sat, Apr 24, 2010 at 02:47:05PM +0300, Nazar 'Anesth' wrote:
> Hi there rocking Xen.
>
> When I'm trying to boot xen 4.0.0 with latest 2.6.32.10-pvops dom0 kernel
> (i686+PAE) on LUKS-enabled system, cryptsetup utility doesn't work if running
> from init (for root fs) or rc.d scripts:
Does it work if you boot the 2.6.32-10-pvops without Xen?
>
> device-mapper: resume ioctl failed: No such device or address
> device-mapper: remove ioctl failed: No such device or address
That really points to an invalid name. Do the devices mentioned in
/etc/crypttab exist?
> Failed to revert device creation
> Failed to setup dm-crypt key mapping for device /dev/sdb1
> Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more
> info)
> Failed to read from key storage
>
> And root device cannot be opened. When escape to initrd's rescue shell and run
> cryptsetup by hands, result is exactly the same. But if I run cryptsetup
> with --debug, it opens all the encrypted devices.
And what is the output shown to you when you it with --debug?
Does it mount if from /dev/sdb1 or is it another name?
>
> I have all neccessary for LUKS options compiled statically into the kernel,
> especially, the dm-mod, dm-crypt, aes-cbc-essiv, sha256 and so on. Regular
> kernel with this config (attached) or xen-capable kernel from my distro
> (2.6.32-r1 from gentoo portage) are working ok. But, unfortunately, I can't
> use gentoo xen kernel due to broken KMS.
prev parent reply other threads:[~2010-05-04 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 11:47 Trouble with cryptsetup Nazar 'Anesth'
2010-05-04 14:41 ` Konrad Rzeszutek Wilk [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=20100504144117.GA15544@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=anesth@unixway.org.ua \
--cc=xen-devel@lists.xensource.com \
/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).