On Thu, Aug 23, 2012 at 01:55:59PM -0400, Shawn Furrow wrote:
> Will (and all other users),
>
> So I think I figured out what my issue is but I'm not certain where and how to
> fix it. As I stated before when I run "sudo virsh -c qemu:///system list" I get
> these errors:
>
> error: Failed to connect socket to '/usr/local/var/run/libvirt/libvirt-sock':
> Permission denied
> error: failed to connect to the hypervisor
>
> Well interesting enough, when I start the daemon and run "lsof | grep
> libvirt-sock" it returns this path:
>
> libvirtd 5598 shawn 11u unix 0xffff88042192d050 0t0 39057 /
> home/users/shawn/.cache/libvirt/libvirt-sock
>
> So if I'm not mistaken, it appears that the daemon is creating the socket at "/
> home/users/shawn/.cache/libvirt" but the virsh command is trying to connect at
> "/usr/local/var/run/libvirt". I figured that changing the unix_sock_dir
> variable in "/usr/local/etc/libvirt/libvirtd.conf" to be set to "/usr/local/var
> /run/libvirt" would fix it but it doesn't. The daemon still creates the
> libvirt-sock socket at "/home/users/shawn/.cache/libvirt/libvirt-sock".
>
> Do you happen to know where or how to set daemon's default location for
> creating the libvirt-sock?
>
> Shawn
>
> On Thu, Aug 23, 2012 at 12:52 PM, Whit Blauvelt <
whit.virt@transpect.com>
> wrote:
>
> Shawn,
>
> First off, nobody would call me an expert at this. Fumbling like you are.
> But it's working for me.
>
> Are you sure you killed all libvirtd processes before starting libvirtd?
> You
> might check for them with "ps aux | grep libvirtd". I recall a tendency for
> them to hang around short of explicitly killing them.
>
> Which user did you start libvirtd as? I'd doing that as root.
>
> Speaking of users, there's another step I took, and I'm not sure if it was
> essential or not. In /usr/local/etc/libvirt/qemu.conf I set the qemu user
> and group to the Ubuntu defaults:
>
> # The user ID for QEMU processes run by the system instance.
> #user = "root"
> user = "libvirt-qemu"
>
> # The group ID for QEMU processes run by the system instance.
> #group = "root"
> group = "kvm"
>
> Did that while I was fumbling. Not sure if it was critical.
>
> Whit
>
>
>
>
> On Thu, Aug 23, 2012 at 12:27:01PM -0400, Shawn Furrow wrote:
> > Whit,
> >
> > I was able to get around the library problem by simply uninstalling the
> > xsltproc distribution package. The docs are not made but the installation
> > finishes. (Let me know if you think this is a bad idea or if it will mess
> up
> > the running of libvirt somehow)
> >
> > I tried your suggestion and I can run the libvirt daemon from the
> location you
> > suggested. However, when I cannot seem to connect to the libvirt-sock
> socket or
> > the qemu hypervisor. When I run the command "sudo virsh -c qemu:///system
> list"
> > I get the follow error messages:
> >
> > error: Failed to connect socket to '/usr/local/var/run/libvirt/
> libvirt-sock':
> > Connection refused
> > error: failed to connect to the hypervisor
> >
> > Any ideas how to get this working. I've been running into this problem
> for
> > several combinations of installs except for when I use the distro
> packages for
> > both qemu-kvm and libvirt.
> >
> > Thanks,
> > Shawn
> >
> >
> >
> > On Wed, Aug 22, 2012 at 4:20 PM, Whit Blauvelt <
whit.virt@transpect.com>
> wrote:
> >
> > What works for me (Ubuntu 10.10):
> >
> > Stop the old version.
> >
> > Start the new one with:
> >
> > /usr/local/sbin/libvirtd -d
> >
> > That's assuming that you did a "make install" and let it go to the
> default
> > location, which that is. Now, if it's all default (both the original
> and
> > your builds), then replace /usr/local/etc/libvirt/qemu with a symlink
> to
> > /etc/libvirt/qemu before starting.
> >
> > Also, if you've built qemu-kvm to replace the distro version, then
> > /usr/bin/kvm should be a symlink to /usr/local/bin/qemu-system-x86_64
> > rather
> > than the distro's /usr/bin/qemu-system-x86_64.
> >
> > There's also another daemon or two that you may or may not need
> running
> > according to how you're handling the VM interfaces. Since I'm
> bridging
> > them,
> > I haven't concerned myself with that.
> >
> > In recent versions Ubuntu has omitted a proper /etc/init.d script in
> favor
> > of upstart (which I hate; YMMV). There's still a decent init.d script
> for
> > libvirt in Debian, which can be edited to work with a
> built-from-source
> > version. Of course, Ubuntu will replace that whenever you do updates,
> if it
> > still thinks that libvirt is something it should update.
> >
> > BTW, what did you do to get around the library problem?
> >
> > Whit
> >
> > On Wed, Aug 22, 2012 at 03:50:12PM -0400, Shawn Furrow wrote:
> > > Daniel (and all others),
> > >
> > > I have been able to get past the libvirt installation but I cannot
> start
> > the
> > > libvirtd daemon. For ubuntu, what is the best way to start the
> libvirtd
> > daemon?
> > > "sudo make install" did not put libvirtd in /etc/init.d so the only
> place
> > I see
> > > it is in libvirt-0.10.0/daemon/. I have looked up this issue online
> and
> > the
> > > best I have seen is to install the distribution package and replace
> the
> > daemon
> > > with the one I build from source. Does anyone know anything about
> this?
> > >
> > > Thanks,
> > > Shawn
> > >
> > > On Wed, Aug 22, 2012 at 10:40 AM, Shawn Furrow <
sfurrow@vt.edu>
> wrote:
> > >
> > > If I run xmllint --noout docs/
news.html.in inside the
> libvirt-0.10.0
> > > directory I get no output.
> > >
> > > Shawn
> > >
> > >
> > > On Wed, Aug 22, 2012 at 10:33 AM, Daniel Veillard <
> >
veillard@redhat.com>
> > > wrote:
> > >
> > > On Wed, Aug 22, 2012 at 10:02:53AM -0400, Shawn Furrow
> wrote:
> > > > Daniel,
> > > >
> > > > I tried re-installing all of those libraries and I still
> get
> > the same
> > > > segfault. Here are the outputs you requested:
> > > >
> > > > *xsltproc --version*
> > > > Using libxml 20706, libxslt 10126 and libexslt 815
> > > > xsltproc was compiled against libxml 20706, libxslt 10126
> and
> > > libexslt 815
> > > > libxslt 10126 was compiled against libxml 20706
> > > > libexslt 815 was compiled against libxml 20706
> > > >
> > > > *xmllint --version*
> > > > xmllint: using libxml version 20706
> > > > compiled with: Threads Tree Output Push Reader
> Patterns
> > Writer
> > > SAXv1 FTP
> > > > HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer
> XInclude
> > Iconv
> > > > ISO8859X Unicode Regexps Automata Expr Schemas Schematron
> > Modules
> > > Debug Zlib
> > >
> > > what does xmllint --noout docs/
news.html.in gives within
> > libvirt ?
> > > if it crashes then check which libz is used by
> > > ldd /usr/bin/xmllint
> > > and check where that library comes from, it's very likely a
> > problem
> > > like that, xsltproc should not crash
> > >
> > > Daniel
> > >
> > > --
> > > Daniel Veillard | libxml Gnome XML XSLT toolkit http:
> //
> > >
xmlsoft.org/
> > >
daniel@veillard.com | Rpmfind RPM search engine http://
> >
rpmfind.net/
> > >
http://veillard.com/ | virtualization library http://
>
libvirt.org
> > /
> > >
> > >
> > >
> > >
> > > --
> > > Virginia Tech
> > > Bradley Department of Electrical and Computer Engineering
> > > B.S. Electrical Engineering
> > > B.S. Computer Engineering
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Virginia Tech
> > > Bradley Department of Electrical and Computer Engineering
> > > B.S. Electrical Engineering
> > > B.S. Computer Engineering
> > >
> >
> > > _______________________________________________
> > > libvirt-users mailing list
> > >
libvirt-users@redhat.com
> > >
https://www.redhat.com/mailman/listinfo/libvirt-users
> >
> >
> >
> >
> >
> > --
> > Virginia Tech
> > Bradley Department of Electrical and Computer Engineering
> > B.S. Electrical Engineering
> > B.S. Computer Engineering
> >
>
>
>
>
> --
> Virginia Tech
> Bradley Department of Electrical and Computer Engineering
> B.S. Electrical Engineering
> B.S. Computer Engineering
>