Bug 1009604 - virsh -c vbox:///session fails on OSX
Summary: virsh -c vbox:///session fails on OSX
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Mac OS
unspecified
high
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 17:07 UTC by tonycpsu
Modified: 2016-05-02 14:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-02 14:25:50 UTC


Attachments (Terms of Use)

Description tonycpsu 2013-09-18 17:07:40 UTC
Description of problem:

Using libvirt 1.1.2, connecting to vbox:///session URIs fails with the following error:

virsh -c vbox:///session
2013-09-18 17:01:53.569+0000: 18446744073709551615: error : virGetUserEnt:698 : Failed to find user record for uid '32671': Success
error: failed to connect to the hypervisor
error: Failed to find user record for uid '32671': Success

The first line is a log message that comes from libvirtd on stdout or stderr.  I don't know where these strange uid numbers are coming from, but this problem is something others have noticed, to wit:

http://comments.gmane.org/gmane.comp.emulators.libvirt.user/4925

Also, see Doug Goldstein's comments in response to my question about this bug on libvirt-users:

https://www.redhat.com/archives/libvirt-users/2013-June/msg00112.html

It does appear as if the error message itself was tweaked in this commit:

http://libvirt.org/git/?p=libvirt.git;a=commit;h=4c7d1eab6e0d5fca56a0d7e2c67ee9e71836f111

but there's no indication as to where the uid problem itself is coming from on OS X.


Version-Release number of selected component (if applicable): 1.1.2


How reproducible:

Every time

Steps to Reproduce:
1. Install libvirt on OS X (brew install libvirt)
2. run libvirtd
3. run virsh -c vbox:///session

Actual results:

See above

Expected results:

See above

Additional info:

Comment 1 tonycpsu 2013-11-08 02:20:52 UTC
Problem persists as of libvirt 1.1.4.

Comment 2 Cole Robinson 2016-04-10 14:47:19 UTC
Sorry this never received a timely response... Tony (or anyone else), is this still relevant with recent libvirt versions? If so please post the latest error message

Comment 3 Cole Robinson 2016-05-02 14:25:50 UTC
Since there's no response, closing as DEFERRED. But if anyone is still affected with newer libvirt versions, please re-open and we can triage from there


Note You need to log in before you can comment on or make changes to this bug.