Displaying 5 results from an estimated 5 matches for "inspector2".
Did you mean:
inspector
2012 Aug 01
1
libguestfs question - multiple partitions in the guest
...d, Aug 01, 2012 at 11:47:14AM -0500, Shawn Kennedy wrote:
> Problem:
> When trying to inspect the guest using a command like 'virt-ls', we
> get back:
>
> ~]# virt-ls -d guest /path
> virt-ls: multi-boot operating systems are not supported by the -i option
What does virt-inspector2 [this is RHEL 6] display for this guest?
virt-inspector2 -d guest
virt-ls fundamentally doesn't work with multi-boot guests. However
that doesn't mean to say you can't use libguestfs, you just need to
use some lower level tools or write a Perl/Python/whatever script
against the API...
2014 Jan 17
2
Re: LVM mounting issue
-----Original Message-----
From: Richard W.M. Jones [mailto:rjones@redhat.com]
Sent: Friday, January 17, 2014 4:40 PM
To: Исаев Виталий Анатольевич
Cc: libguestfs@redhat.com
Subject: Re: [Libguestfs] LVM mounting issue
On Fri, Jan 17, 2014 at 09:45:34AM +0000, Исаев Виталий Анатольевич wrote:
> Be sure, that “unknown device” was not written by me :)
>
> I use libguestfs 1.16.34:
2010 Nov 18
0
[RHEL 6.1] libguestfs test packages available
...lt on RHEL 6.0 and should install directly on top of RHEL 6.0.
Some highlights:
- Based on the upstream stable 1.6 branch.
- Much better performance.
- Many new features, see: http://libguestfs.org/RELEASE-NOTES.txt
- virt-inspector is the RHEL 6.0 virt-inspector (deprecated upstream)
- virt-inspector2 is the new upstream virt-inspector
They should be completely source and binary compatible with the RHEL
6.0 packages, except for new features. So a program or script that
you wrote against libguestfs 1.2.7 in RHEL 6.0 should work unchanged
against these new packages.
Note these packages are not...
2014 Jan 17
0
Re: LVM mounting issue
...cc6e4400--7c98--4170--9075--5f5790dfcff3 -> ../dm-40
>
> 6. So I have no choice and I try to open /dev/dm-40 with libguestfs or guestfish. What's next, you already know.
You definitely do have a choice. Don't open /dev/dm-40. Open one of
the other paths instead, eg:
virt-inspector2 -v -x -a /var/lib/stateless/writable/rhev/data-center/mnt/blockSD/1a9aa971-f81f-4ad8-932f-607034c924fc/images/8a3e02de-d8ab-4357-ba8c-490f3ba3e85c/cc6e4400-7c98-4170-9075-5f5790dfcff3
It makes a big difference to qemu which path you use, because it
searches for backing disks relative to the path o...
2011 Dec 26
1
Another virt-p2v blew up
One day I'm going to run a virt-p2v that works to completion. But evidently not today.
The source physical machine is Windows 2003. This one copied the whole system drive and then died at the end and deleted the virtual disk it made. Here is the top and bottom of the trace log file on the conversion server. If the email garbles what I'm pasting in below, I can email the log as an