[libvirt-users] Libvirt 1.2.5/Qemu woes

[andy zerger]

I understand about it being tough to support over a self-build issue - I
suppose I can only offer reassurance this node is about my twentieth
self-build in my farm right now and all are done according to a script with
the same options. (This is the first one that refused to run. It's sister
server (also an old Dell 2950,) is having the exact same problem, and even
on the CentOS provided builds.) I'm also making sure 1.7.1 / 2.0.0 are
working with my build (they are, on a Poweredge 610, with the same
options.) I am utterly convinced that these two servers are haunted, as the
iDracs on these things also flatly don't work.

Thanks for your response - much appreciated.


On Mon, Jun 16, 2014 at 12:53 PM, Eric Blake <eblake at redhat.com> wrote:

> On 06/16/2014 08:25 AM, andy zerger wrote:
> > Hi all -
> >
> > I'm dealing with a libvirt 1.2.5 and Qemu-1.7.1 also Qemu-2.0 (all source
> > compile,) which somehow isn't seeing any hypervisors when connected to
> via
> > virt-manager.
>
> A good thing to try is whether 'virsh -c qemu:///system list --all'
> shows anything; debugging a command-line test can be easier than
> debugging a gui not listing anything.
>
> >
> > I'm sure I must be doing something wrong but cannot figure out what. My
> > basic config and current state here in pastebin:
> > http://pastebin.com/m5M8PfFC
>
> pastebin is not permanent.  When your posting expires, someone
> revisiting this thread in the mail list archives will have no idea what
> you were seeing.  So I'm reproducing it here:
>
> > ./configure --target-list=x86_64-linux-user --enable-kvm
> --sysconfdir=/etc/libvirt --localstatedir=/var;
>
> This is not the same set of configure options as what is used by the rpm
> package shipped in CentOS.  As a result, if you have any mismatch
> between the distro build and your self-build, things tend not to connect
> to the right server.
>
> Libvirt's autogen.sh has a --system flag that sets up the following
> configure arguments, which tends to work better out-of-the-box for
> replacing a Fedora-based distro build with a self-build:
>
>   if test "x$1" = "x--system"; then
>     shift
>     prefix=/usr
>     libdir=$prefix/lib
>     sysconfdir=/etc
>     localstatedir=/var
>     if [ -d /usr/lib64 ]; then
>       libdir=$prefix/lib64
>     fi
>     EXTRA_ARGS="--prefix=$prefix --sysconfdir=$sysconfdir
> --localstatedir=$localstatedir --libdir=$libdir"
>
>
> >
> > [root at 10-3-1-35 qemu_images]# lsmod
> > Module                  Size  Used by
> > kvm_amd                41702  0
> > kvm                   316506  1 kvm_amd
> >
> > [root at 10-3-1-35 qemu_images]# ls -l /dev/kvm
> > crw-rw----. 1 root root 10, 232 Jun 16 09:13 /dev/kvm
>
> This looks fishy; /dev/kvm should be 0666, not 0660.
>
> >
> > [root at 10-3-1-35 qemu-1.7.1]# which qemu-x86_64
> > /usr/local/bin/qemu-x86_64
>
> Again, an issue of self-built binaries not being in the same location as
> the distro defaults, so I'm not sure if you have configured everything
> to work well with this location.
>
> >
> > [root at 10-3-1-35 qemu_images]# qemu-x86_64
> > usage: qemu-x86_64 [options] program [arguments...]
> > Linux CPU emulator (compiled for x86_64 emulation)
> >
> > [root at 10-3-1-35 qemu-1.7.1]# cat /etc/redhat-release
> > CentOS release 6.5 (Final)
>
> --
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20140616/a5eabd3d/attachment.htm>