[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Trouble with cryptsetup

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 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.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.