Bug 770645 - [libvirt] rpm-build fails when running on virtual machine - WARNING: no socket to connect to
Summary: [libvirt] rpm-build fails when running on virtual machine - WARNING: no socke...
Keywords:
Status: CLOSED DUPLICATE of bug 782725
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eric Blake
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-28 08:22 UTC by Haim
Modified: 2014-01-13 00:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-19 02:19:09 UTC
Embargoed:

Attachments (Terms of Use)
libvirt logs. (15.10 KB, application/octet-stream)
2011-12-28 08:22 UTC, Haim 		no flags Details
View All

Description Haim 2011-12-28 08:22:42 UTC 
Created attachment 549798 [details]
libvirt logs.

Description of problem:

case: 
#####

- trying to run rpmbuild fails running libvirt tests:

--- exp-err	2011-12-28 09:21:06.718002447 +0200
+++ err	2011-12-28 09:21:06.744002447 +0200
@@ -1 +1,2 @@
+WARNING: no socket to connect to
 error: this function is not supported by the connection driver: virDomainQemuMonitorCommand
FAIL: virsh-optparse
--- exp-err	2011-12-28 09:21:06.774002447 +0200
+++ err	2011-12-28 09:21:06.800002447 +0200
@@ -1 +1,2 @@
+WARNING: no socket to connect to
 error: invalid scheduler option: j=k
FAIL: virsh-schedinfo
WARNING: no socket to connect to

- tests are failing as mu build machine runs on a virtual machine without virt support.

see attached logs.

git commit: 1f24ddf6bfde0f0c24865f29e59ea017f6f8d6b6
Comment 1 Haim 2011-12-28 08:23:42 UTC 
command I run: 

- ./autogen --system
- make
- make dist
- rpmbuild -ba libvirt.spec
Comment 2 Eric Blake 2012-01-19 00:27:52 UTC 
see also bug 768473 for another instance of this bug.
Comment 3 Eric Blake 2012-01-19 02:19:09 UTC 

*** This bug has been marked as a duplicate of bug 782725 ***
Note You need to log in before you can comment on or make changes to this bug.