kvm virtual disk errors on luks container/lvm combo

[inode77]

Upon trying to provide a lvm storage container for kvm virtualization it worked but got I/O errors inside the guest after a short period of time.

Setup: SSD with primary partition > luks dm-crypt container > lvm pv > kvm guests

Jun 9 13:16:18 sonus kernel: [ 0.702849] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
Jun 9 13:16:18 sonus kernel: [ 0.884851] Adding 575484k swap on /dev/vda2. Priority:-1 extents:1 across:575484k
Jun 9 13:16:18 sonus kernel: [ 0.904298] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Jun 9 13:16:18 sonus kernel: [ 1.497796] end_request: I/O error, dev vda, sector 4992576
Jun 9 13:16:18 sonus kernel: [ 1.498668] end_request: I/O error, dev vda, sector 4992576
Jun 9 13:16:18 sonus kernel: [ 1.499204] end_request: I/O error, dev vda, sector 4992576

I checked the ssd an tried with another guest but got the same result.

After changing the setup from lvm to image file on the same ssd everything started to work.
Setup: SSD with primary partition > luks dm-crypt container > ext4 > kvm guests

Only error pointing in this direction is a lvm boundary exposure error which was corrected a long time ago.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libvirt-bin 1.0.2-0ubuntu11.13.04.1
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sun Jun 9 23:54:10 2013
InstallationDate: Installed on 2013-06-08 (1 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug. Could you please provide some more
details about the luks and lvm container (configuration files with
any keys starred out) and libvirt xml?

Marking as affecting the kernel due to the end-request errors.

 affects: linux

[Kelvin Middleton (kelvin-middleton)]

Hi, think I have the same issue but am not encrypting, just straight forward kvm guest creation onto an LVM. Shall I register against this bug report or open a separate one due to the encryption difference?

[Serge Hallyn (serge-hallyn)]

@Kelvin,

I suspect yours is the same issue, but please do create a new bug - it's easier to merge them later than to split them up.