Re: [libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Abbas
On 11/17/2012 02:47 AM, Frank Shi wrote:
> Thanks much Abbas for your prompt response. Right, I have fixed all the
> dependency issues. It compiled but failed during running test cases. I
> prefer building from src-rpm is because I need to install the package onto
> other machines. Building from src-rpm can generate rpm so it makes
> future deploy easier.
Then the start off point will be CentOS' srpms. You might still need to
do some patchwork and testing before you get a working rpm (a reason why
there's no third party repo for latest kvm and libvirt). Installing on
multiple machines sounds like you tend towards stability and Fedora's
packages won't do that job anyway!
> Anyway, follow your recommendation, I downloaded the source tar and tried
> to compile it from source. This time I am seeing following problems. What
> could be the problem?
>
> Thanks, Frank
>
> ===============
> $ tar xvf libvirt-1.0.0-rc1.tar.gz
> $ libvirt-1.0.0
> $ ./configure
Try using the supplied autogen script first.
> libxl/libxl_conf.c:471: error: 'libxl_domain_build_info'
It's a missing dep error.
Quick time-savers for latest KVM and Libvirt (on latest CentOS 6.3):
# qemu-kvm deps
yum install gcc pkgconfig SDL-devel zlib-devel alsa-lib-devel
pciutils-devel gnutls-devel glib glib2-devel
./configure --prefix=/usr --sysconfdir=/etc
make && make install
# libvirt deps
yum install git python-devel libtool patch libxml2 libxml2-devel
yajl-devel device-mapper-devel libnl-devel
./autogen-sh --system
make && make install
# packages to remove
qemu-img
qemu-kvm
libvirt
libvirt-client
virt-top
The kvm_intel manually loaded of course!
------
bassu
11 years, 8 months
[libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Frank Shi
Hi, List,
I am seeing following problems when building libvirt-1.0.0-1.fc17.src.rpm.
The first failed test case is xml2sexprtest as you can see below.
$ sudo rpmbuild -ba SPECS/libvirt.spec
+ make check
TEST: virshtest
........................................ 40
........... 51 OK
TEST: sockettest
...................................... 38 OK
TEST: virbuftest
.... 4 OK
TEST: commandtest
..................... 21 OK
TEST: virhashtest
.............. 14 OK
TEST: virnetmessagetest
..... 5 OK
TEST: virnetsockettest
............... 15 OK
TEST: viratomictest
.. 2 OK
TEST: utiltest
... 3 OK
TEST: virnettlscontexttest
........................................ 40
........ 48 OK
TEST: shunloadtest
. 1 OK
TEST: virtimetest
............... 15 OK
TEST: viruritest
.................. 18 OK
TEST: virkeyfiletest
. 1 OK
TEST: virauthconfigtest
...... 6 OK
TEST: virbitmaptest
...... 6 OK
TEST: virlockspacetest
....... 7 OK
TEST: securityselinuxtest
TEST: virdrivermoduletest
....... 7 OK
TEST: xml2sexprtest
.!.!!.....................!..!!!!.!!!!!! 40
!!!!!!!!!!... 53 FAIL
TEST: sexpr2xmltest
........................................ 40
........... 51 OK
TEST: xmconfigtest
..............!.!.!.!.!.!.!.!.!.!.!.!.!. 40
!.!.!.!.!.!.!.!.!...!.!.!. 66 FAIL
TEST: xencapstest
.......... 10 OK
TEST: statstest
TEST: reconnect
TEST: qemuxml2argvtest
........................................ 40
........................................ 80
........................................ 120
........................................ 160
........................................ 200
........................................ 240
...... 246 OK
TEST: qemuxml2xmltest
........................................ 40
........................................ 80
................................... 115 OK
TEST: qemuxmlnstest
....... 7 OK
TEST: qemuargv2xmltest
........................................ 40
................................... 75 OK
TEST: qemuhelptest
................ 16 OK
TEST: domainsnapshotxml2xmltest
....... 7 OK
TEST: qemumonitortest
.. 2 OK
TEST: qemumonitorjsontest
!!!!! 5 FAIL
TEST: esxutilstest
.... 4 OK
TEST: vmx2xmltest
........................................ 40
.......... 50 OK
TEST: xml2vmxtest
........................................ 40
..... 45 OK
TEST: networkxml2xmltest
................ 16 OK
TEST: networkxml2argvtest
......... 9 OK
TEST: nwfilterxml2xmltest
........................................ 40
. 41 OK
TEST: storagevolxml2xmltest
....... 7 OK
TEST: storagepoolxml2xmltest
............. 13 OK
TEST: nodedevxml2xmltest
............. 13 OK
TEST: interfacexml2xmltest
................... 19 OK
TEST: cputest
........................................ 40
.......................... 66 OK
TEST: eventtest
............... 15 OK
TEST: libvirtdconftest
....................................... 39 OK
make[1]: *** [check-TESTS] Error 1
make: *** [check-am] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check)
Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check)
Not sure whether the failures are related to xml. Anyway, following is a
list of xml packages installed,
python-lxml-2.2.3-1.1.el6.x86_64
xmldb-api-sdk-0.1-0.4.20011111cvs.1.5.el6.noarch
xmlto-0.0.23-3.el6.x86_64
xmlrpc-c-1.16.24-1209.1840.el6.x86_64
xml-commons-resolver-1.1-4.18.el6.x86_64
xmlrpc-c-client-1.16.24-1209.1840.el6.x86_64
xmldb-api-0.1-0.4.20011111cvs.1.5.el6.noarch
xmlrpc3-client-3.0-4.15.el6.noarch
xmlgraphics-commons-1.3.1-1.1.el6.noarch
libxml2-devel-2.7.6-4.el6_2.4.x86_64
libxml2-2.7.6-4.el6_2.4.x86_64
xml-common-0.6.3-32.el6.noarch
perl-libxml-perl-0.08-10.el6.noarch
libxml2-python-2.7.6-4.el6_2.4.x86_64
xml-commons-apis-1.3.04-3.6.el6.x86_64
# cat /proc/version
Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)c6b9.bsys.dev.centos.org)
(gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22
12:19:21 UTC 2012
Thanks, Frank
11 years, 8 months
[libvirt-users] authentication failed, but why?
by huancong deng
I set the me into the group libvirt and write the config for libvirtd:
==================================================
listen_tls = 0
listen_tcp = 0
auth_tcp = "none"
mdns_adv = 0
unix_sock_group = "libvirt"
unix_sock_ro_perms = "0770"
unix_sock_rw_perms = "0770"
unix_sock_dir = "/var/run/libvirt"
log_filters = "1:libvirt 1:util 1:qemu"
log_output = "1:file:/var/log/libvirt/libvirtd.log"
max_clients = 500
min_workers = 10
max_workers = 50
max_requests = 50
max_client_requests = 8
===========================================
but I can't login the libvirt:
[xxxxxx@u70 ~]$ virsh
error : authentication failed: Authorization requires authentication but no
agent is available.
who can tell me why? thanks a lot.
:)
11 years, 8 months
[libvirt-users] Handling connection closes in (older) Sys::Virt
by Henrik Ahlgren
I hope this is the correct mailing list for discussing the Sys::Virt
Perl module.
It appears that the most recent version has a new method called
register_close_callback that, I believe, can be used to catch errors
when the connection to libvirt is closed, e.g. due to libvirt restart
or a network related issue. (I've been testing this simply by killing
the the SSH process in the libvirt server.)
However, Debian still ships libvirt 0.9.12 in stable backports and
testing, as probably do many other mainstream distributions. The
latest Perl bindings that can be installed from CPAN is thus 0.9.12
and it does not have support for close callbacks. Not only that, when
a Perl program loses the (ssh) connection to libvirt, Perl just
crashes:
Program received signal SIGPIPE, Broken pipe.
0x00007ffff73de0d0 in __write_nocancel () from /lib/libpthread.so.0
Setting a $SIG{PIPE} handler does not seem to help. Is there any
possibility of a Perl program surviving and gracefully handling a
closed libvirt connection with libvirt version 0.9.12 or
older?
Henrik
11 years, 8 months
[libvirt-users] Virt-io Kernels for older RHEL/CentOS versions
by Chandana De Silva
All,
I need to run a number of guests which user older distributions of RHEL
and CentOS on an RHEL 6.3 host. The versions are;
4.8 - i386
5.1 - i386
5.2 - x86_64
5.3 - i386
Currently I am running these with the E1000 network driver and the IDE
driver. Where can I find kernels (or modules) for virtio for these OS's ?
Thanks in advance
Chandana
11 years, 8 months
[libvirt-users] virt-install kickstart local file
by Joe Linoff
Hi Everybody:
I am trying to get virt-install to work with a kickstart file that is on
the local file system.
I tried using the --initrd-inject="/tmp"
--extra-args="ks=file:/myks.cfg" but I got this error message:
ERROR --extra-args only work if specified with --location.
Here is the basic command:
virt-install \
--accelerate \
--cdrom /tools/iso/CentOS-6.3-x86_64-bin-DVD1.iso \
--disk device=disk,path="/var/lib/libvirt/images/myguest.img" \
--graphics vnc \
--name myguest \
--os-type linux \
--os-variant rhel6 \
--ram 2048 \
--vpcus 1,maxvcpus=4 \
--initrd-inject "/tmp" \
--extra-args "ks=file:/myks.cfg"
Why do I need the location? I thought that was only used when
installatiing from a distribution tree. I am using a DVD ISO image. If I
have to use it, how would I specify it?
If this approach won't work, I could move the ks.cfg file to an NFS
mounted file system but I am not sure what the syntax is for that.
I am running this on a CentOS 6.3 system.
libvirt: 0.9.10
qemu: 0.12.1
Thank you,
Joe
11 years, 8 months
[libvirt-users] virt-viewer X forwarding through ssh broken since FC17 upgrade?
by Ken Coar
Ever since I upgraded my laptop from FC15 to FC17, I've been
getting this message when I ssh to some RHEL6 hosts inside Red Hat.
In particular, I'm trying to do this:
virt-viewer --connect \
qemu+ssh://kvm11.devlab.phx1.redhat.com/system \
bork-s01.candlepin.dev.devlab.phx1.redhat.com
This is the message I get:
X11 forwarding request failed on channel 0
A viewer window pops up for a fraction of a second and then
goes away.
Using -vvvv on the local ssh command gives a few possibly
related messages:
debug2: x11_get_proto: /usr/bin/xauth list :0.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 1
debug1: Requesting authentication agent forwarding.
debug2: channel 0: request auth-agent-req(a)openssh.com confirm 0
:
debug1: Remote: No xauth program; cannot forward with spoofing.
This is new, and, not being an X maven, largely opaque to me.
xauth is provided by package xorg-x11-xauth, which is typically
*not* installed. Installing it on the system to which I'm
trying to ssh gets rid of the message, but doesn't change the
up-down behaviour of the viewer window.
Temporarily moving my local /usr/bin/xauth leads to this
message in addition:
Warning: No xauth data; using fake authentication data for X11 forwarding.
X11 forwarding request failed on channel 0
Since there's a window popping up at all, I doubt this is directly
related to the problem getting the viewer to run. However, on
systems *with* xauth installed 'echo $DISPLAY' shows a value, but
on those *without* xauth, $DISPLAY is null. (So why am I getting
any sort of X popup at all in that case?)
Has anyone else seen this, and hopefully have a solution? The
problem is actually two-fold:
1. Why 'X11 forwarding failed' and how to get rid of it/revert to
behaviour in previous versions; and
2. Why is virt-viewer dying and how to keep it alive. (Again, how
to revert to 'it *used* to work' conditions. ;-) )
Thanks!
--
#ken B-)}
Ken Coar, RHCE, RHCSA, Sanagendamgagwedweinini
IT Engineering Tower, Red Hat/RDU
"Millennium hand and shrimp!"
11 years, 8 months
[libvirt-users] the acl mode of files created by libvirtd
by Hao.Zhang
Hi, all
I use virsh save command to dump a domain, the mode is 0600,
and belongs to "root", how can i change the mode?
Thanks.
William
--
That night, I thanked God for seeing me thought the day of days and prayed
I would make it through tomorrow. I also promised that if some day I could
get home again, I would find a nice peaceful town and spend rest of my life
in peace.
11 years, 8 months
