Bug 811872 - inspection fails on ubuntu 10.04 guest with encrypted swap
Summary: inspection fails on ubuntu 10.04 guest with encrypted swap
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libguestfs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-12 08:02 UTC by Mike Cao
Modified: 2012-04-13 18:28 UTC (History)
6 users (show)

Fixed In Version: libguestfs-1.16.18-2.el6
Clone Of:
Environment:
Last Closed: 2012-04-12 09:28:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Cao 2012-04-12 08:02:30 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.virt-inspector -a /home/mike/image/ubuntu-10.04-amd64.qcow2   >> a.txt

2.
3.
  
Actual results:
it prompts libguestfs: error: lvm_canonical_lv_name: lvm_canonical_lv_name_stub: /dev/mapper/cryptswap1: No such file or directory

Expected results:
no error should prompts

Additional info:
1.Tried w/ ubuntu 10.04-32 bit guest ,did not hit this issue 
2.cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/vda1 during installation
UUID=336fbf44-8f80-4826-9234-5247e3848f31 /               ext4    errors=remount-ro 0       1
# swap was on /dev/vda5 during installation
#UUID=f0b68c8d-0dc5-40b3-a3a5-959ef22cf4d0 none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0

><fs> vfs-type /dev/vda2 

><fs> vfs-type /dev/vda5

Comment 2 Richard W.M. Jones 2012-04-12 09:28:02 UTC
Fixed upstream.  The fix will appear
in 1.17.29 / 1.16.18.


Note You need to log in before you can comment on or make changes to this bug.