Hi,
On 02/10/2011 11:29 AM, Stefan Bühler wrote:
Package: imvirt
Version: 0.9.0-2
Without pciutils i got the following error on a xen guest:
# imvirt
Can't exec "lspci": No such file or directory at
/usr/share/perl5/ImVirt/Utils/pcidevs.pm line 68.
Error loading ImVirt::VMD::KVM: Cannot exec lspci: No such file or
directory
Compilation failed in require at /usr/share/perl5/ImVirt/VMD/KVM.pm line
35.
BEGIN failed--compilation aborted at /usr/share/perl5/ImVirt/VMD/KVM.pm
line 35.
Compilation failed in require at (eval 16) line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.
Compilation failed in require at /usr/bin/imvirt line 31.
BEGIN failed--compilation aborted at /usr/bin/imvirt line 31.
Xen PV 3.2
So either it shouldn't handle missing lspci or depend on pciutils.
IMHO imvirt should not depend on pciutils (I would prefer a Suggests or
Recommends) as this might be useless for some virtualization containers.
The upstream fix is:
Index: perl/lib/ImVirt/Utils/pcidevs.pm
===================================================================
--- perl/lib/ImVirt/Utils/pcidevs.pm (revision 521)
+++ perl/lib/ImVirt/Utils/pcidevs.pm (working copy)
@@ -67,7 +67,7 @@
exec('lspci', '-m');
- die("Cannot exec lspci: $!\n");
+ exit;
}
sub pcidevs_get() {
HTH,
Thomas
- stefan
--
[email protected] Tel. +49 351 477 77 30
www.ibh.de Fax +49 351 477 77 39
-----------------------------------------------------------------------
Dipl.-Ing. Thomas Liske
Netzwerk- und System-Design
IBH IT-Service GmbH Amtsgericht Dresden
Gostritzer Str. 67a HRB 13626
D-01217 Dresden GF: Prof. Dr. Thomas Horn
Germany VAT DE182302907
-----------------------------------------------------------------------
Ihr Partner für: LAN, WAN IP-Quality, Security, VoIP, SAN, Backup, USV
-----------------------------------------------------------------------
professioneller IT-Service - kompetent und zuverlässig
-----------------------------------------------------------------------
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
