[libvirt] [Libvirt-announce] Entering freeze for libvirt-1.1.3

Justin Clift jclift at redhat.com
Thu Sep 26 09:43:34 UTC 2013


On 26/09/2013, at 10:05 AM, Michal Privoznik wrote:
> On 26.09.2013 10:59, Justin Clift wrote:
>> On 26/09/2013, at 6:30 AM, Daniel Veillard wrote:
>> <snip>
>>> I will probably make rc2 during the w.e. and depending on news push on
>>> Tuesday next week or a bit later the final 1.1.3
>> 
>> Compiles ok on MacOS 10.7.  virsh starts ok too.
>> 
>> One weirdness noted from inside virsh (not connected to a
>> hypervisor):
>> 
>>  virsh # version
>>  error: failed to connect to the hypervisor
>>  error: no valid connection
>>  error: Failed to find user record for uid '32766'
>> 
>> Not sure what the "32766" comes from, since that's not the id of
>> my user:
> 
> Isn't it a PID of the virsh process? I think we fail to get identity for
> the virsh process and mislead users by wrong error message.

Doesn't seem like it.  Just started virsh again, but the pid of that
process doesn't match the # given this time (which did change though).

Terminal window 1:

  virsh # version
  error: failed to connect to the hypervisor
  error: no valid connection
  error: Failed to find user record for uid '32706'

Terminal window 2: (virsh still open in #1)

  $ ps -ef|grep -i virsh
    501 35262 35252   0 10:38am ttys000    0:00.03 virsh
  $ ps -ef|grep -i 32706
  $

Not seeing anything in the "327xx" range, and new pid's
are (atm) in the "353xx" range.

Not sure where it's picking up the "uid" value from, and haven't
really tried tracing it.  I wonder if it's just an OSX thing, or
if maybe *BSD is showing something similar...

+ Justin

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift




More information about the libvir-list mailing list