From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Trouble with cryptsetup Date: Tue, 4 May 2010 10:41:17 -0400 Message-ID: <20100504144117.GA15544@phenom.dumpdata.com> References: <201004241447.14447.anesth@unixway.org.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <201004241447.14447.anesth@unixway.org.ua> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nazar 'Anesth' Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.