search for: qva

...vgchange >> > doesn't even have a 'partial' option, so I'm not sure how to >> > troubleshoot it. Here is the filesystem layout for this system: > > Which version of libguestfs, and where did you install it from? It was installed via yum on fedora18: # rpm -qva|grep guest libguestfs-tools-c-1.20.9-1.fc18.x86_64 libguestfs-tools-1.20.9-1.fc18.x86_64 libguestfs-1.20.9-1.fc18.x86_64 Thanks so much, Alex

...d in the compilation process. How could I explicitely indicate where to find it ? I use a Red Hat 8.0 system. I checked the FAQ which says readline-devel is also needed, but I have it already installed. Perhaps should I add the configure option --with-readline=path/to/readline ? >> rpm -qva | grep readline readline-4.3-4 readline-devel-4.3-4 readline41-4.1-14 Is there a problem with that readline41 version ? Thanks in advance, Laurent

...age to make the configure script satisfied about readline. I found in R archives that readline-devel should be present too. I downloaded it, indeed the configure script is now OK with readline. But I still have no command-line facilities enabled under R. Why ? [laurent at localhost home]# rpm -qva | grep readline readline-4.3-3 readline-devel-4.3-3 readline41-4.1-14 Thanks for any help. Laurent

...#39; option, so I'm not sure how to >> >> > troubleshoot it. Here is the filesystem layout for this system: >> > >> > Which version of libguestfs, and where did you install it from? >> >> It was installed via yum on fedora18: >> >> # rpm -qva|grep guest >> libguestfs-tools-c-1.20.9-1.fc18.x86_64 >> libguestfs-tools-1.20.9-1.fc18.x86_64 >> libguestfs-1.20.9-1.fc18.x86_64 > > OK, in that case it's (unfortunately) not what I was thinking it was :-( > > If you set: > > export LIBGUESTFS_DEBUG=1 >...

...May 25 16:39:33 sage libvirtd: 16:39:33.525: error : remoteDispatchAuthPolkit:3846 : Policy kit denied action org.libvirt.unix.manage from pid 27509, uid 500, result: 512 I can manually start the kvm guest using virsh, but why can't virt-manager start them? This is on fedora14 x86_64: # rpm -qva|egrep 'virt|polkit|qemu' polkit-qt-0.99.0-2.fc14.x86_64 qemu-img-0.13.0-1.fc14.x86_64 python-virtkey-0.50-8.fc14.x86_64 qemu-kvm-0.13.0-1.fc14.x86_64 polkit-0.98-5.fc14.x86_64 polkit-gnome-0.97-4.fc14.x86_64 libvirt-python-0.8.3-9.fc14.x86_64 virt-viewer-0.2.1-1.fc13.x86_64 gpxe-roms-qemu-1...

...even have a 'partial' option, so I'm not sure how to > >> > troubleshoot it. Here is the filesystem layout for this system: > > > > Which version of libguestfs, and where did you install it from? > > It was installed via yum on fedora18: > > # rpm -qva|grep guest > libguestfs-tools-c-1.20.9-1.fc18.x86_64 > libguestfs-tools-1.20.9-1.fc18.x86_64 > libguestfs-1.20.9-1.fc18.x86_64 OK, in that case it's (unfortunately) not what I was thinking it was :-( If you set: export LIBGUESTFS_DEBUG=1 before running virt-resize then you will g...

...w to > >> >> > troubleshoot it. Here is the filesystem layout for this system: > >> > > >> > Which version of libguestfs, and where did you install it from? > >> > >> It was installed via yum on fedora18: > >> > >> # rpm -qva|grep guest > >> libguestfs-tools-c-1.20.9-1.fc18.x86_64 > >> libguestfs-tools-1.20.9-1.fc18.x86_64 > >> libguestfs-1.20.9-1.fc18.x86_64 > > > > OK, in that case it's (unfortunately) not what I was thinking it was :-( > > > > If you set: > &g...

...;block' instead of 'file' for the device, but had to abandon that idea because it didn't work and I had to concentrate on this problem. Could disabling the cache (cache=none) cause this? I've included some info below, in hopes someone could guide me towards a solution. # rpm -qva|egrep 'kvm|libvirt|kernel|qemu' libvirt-python-0.8.8-7.fc15.x86_64 kernel-2.6.40.6-0.fc15.x86_64 qemu-img-0.14.0-8.fc15.x86_64 gpxe-roms-qemu-1.0.1-4.fc15.noarch kernel-2.6.40.4-5.fc15.x86_64 qemu-system-x86-0.14.0-8.fc15.x86_64 libvirt-0.8.8-7.fc15.x86_64 libvirt-client-0.8.8-7.fc15.x86_64...

...;block' instead of 'file' for the device, but had to abandon that idea because it didn't work and I had to concentrate on this problem. Could disabling the cache (cache=none) cause this? I've included some info below, in hopes someone could guide me towards a solution. # rpm -qva|egrep 'kvm|libvirt|kernel|qemu' libvirt-python-0.8.8-7.fc15.x86_64 kernel-2.6.40.6-0.fc15.x86_64 qemu-img-0.14.0-8.fc15.x86_64 gpxe-roms-qemu-1.0.1-4.fc15.noarch kernel-2.6.40.4-5.fc15.x86_64 qemu-system-x86-0.14.0-8.fc15.x86_64 libvirt-0.8.8-7.fc15.x86_64 libvirt-client-0.8.8-7.fc15.x86_64...

On 07/21/2013 07:01 PM, Alex wrote: > Hi, > > I have an fc18 system and trying to resize an LVM partition with an > ext4 filesystem and receiving the following message from virt-resize: virt-resize is part of libguestfs, which is layered on top of libvirt. As such, I'm redirecting this mail to the libguestfs mailing list. > > # virt-resize -d --expand /dev/sda1

On Thu, Oct 10, 2013 at 08:08:08PM -0400, Fred Smith wrote: > Gang: > > I'm puzzled... > > I rebooted a while ago (and in between the down and up, I installed Fedora > 20 Beta on a USB hard drive, making sure it wouldn't mess with my Centos > system). The install went fine, but afterwards, when I reboot Centos, it > comes up with a black screen and a clock as the

Hi CentOS experts,* Short Version* I would like to produce a weekly report in HTML for each CentOS 5.x server we have indicating configuration compliance with some industry benchmark. I am looking for a tool or tools to implement this, I am happy to use 3rd party proprietary stuff if necessary. * Long(er) Version* Current Situation.. I have a client with many (200x) CentOS 5.x servers

...j$nMHwXfE|JBvbS#lpNS!+idz3oIg)NUthZ6HA#ew9Zs0E9lfXT|^MU(P z>;dpefrouLTt4E#=zlEfPk_JjKLsogJOf-Dcn)|V at S?Arr!SGY9^j>Qy`O&L6>@6= zubukdNcnD%ssr7K3tRoe(K*NbB{?`h1cv4C=45z|bMFSygTM&Di-EEn`Q<xoAYS@; zIUVO8nIpqlIT!nR?=se30eqUj60jst1^6;BDu;vg=p4D;=ioT!9}D``z<fAjrGH$G zBC7nnTY2supX03QVA|!Mm?Ov2q#S2IGubJdg0h+ZYACqluK{cgOa-hAOat5#m<~82 zFaxkTPz$&)PzN|BFw+s9h0OjyeGcCt&X$d70OeGmQQF4Wg<Je{Kso21D{Y=9Jux4Y z<$(pLc(H#W at K=FFz}NVjfS>g*&f$Jp;#9CShySuW-~Mg%(;qC$k+)eGuJir$r^~^9 z!@nX&K8eKQae#;LN)RsvngLe^R<X~5tDR=AL8d;imW>Il%i$@oK1WWr4Nmz+n6Svd z$*Fd;Q?v!#a{...

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *