Hi Everyone,
I am not sure what I did wrong but after update the version of libvirt
I cannot see the options Hypervisor under settings menu.
Has anyone ever seen it before ?
Thanks,
Raquel.
Hi Everyone,
I am not sure what I did wrong but after update the version of libvirt
I cannot see the options Hypervisor under settings menu.
Has anyone ever seen it before ?
Thanks,
Raquel.
> Hi Everyone,
>
> I am not sure what I did wrong but after update the version of libvirt
> I cannot see the options Hypervisor under settings menu.
>
> Has anyone ever seen it before ?
Foreman checks if the ruby-libvirt gem/packages are installed, make
sure they still do.
note that you would need to restart foreman afterwards.
Ohad
Hello,
I am seeing an issue where when I start the foreman service and access
the webUI on port 3000 the hypervisor tab/option is present if I turn
off the service and access the site via a passenger configured vhost I
cannot see the hypervisor tab/option at all. Has anyone else seen
this ? Is there a workaround?
Regards,
Luke
>
>> > Hi Everyone,
>>
>> > I am not sure what I did wrong but after update the version of libvirt
>> > I cannot see the options Hypervisor under settings menu.
>>
>> > Has anyone ever seen it before ?
>>
>> Foreman checks if the ruby-libvirt gem/packages are installed, make
>> sure they still do.
>>
>> note that you would need to restart foreman afterwards.
>>
>> Ohad
>>
>
>
> Hello,
> I am seeing an issue where when I start the foreman service and access
> the webUI on port 3000 the hypervisor tab/option is present if I turn
> off the service and access the site via a passenger configured vhost I
> cannot see the hypervisor tab/option at all. Has anyone else seen
> this ? Is there a workaround?
I'm guessing that you are not running as the same user when you run
passenger, and you have a different set of gems.
in general, foreman detects if the ruby-libvirt gem is installed, if
it is, it enables the hypervisors management.
Ohad
Thanks Ohad for pointing me in the right direction. The idea of this being a UID issue hadn't occurred to me at that point in time.
As it turns out, when I installed the system I installed an rpm version of ruby-libvirt ( my env is RHEL5 x86_64). I took a punt
and installed the ruby-libvirt gem and voila hypervisor options available via passenger.
Luke
On Fri, Sep 23, 2011 at 3:12 AM, luke@kearney.jp luke@kearney.jp wrote:
On Sep 6, 12:03 am, Ohad Levy ohadl...@gmail.com wrote:
On Mon, Sep 5, 2011 at 5:42 PM, queca quelribe...@gmail.com wrote:
Hi Everyone,
I am not sure what I did wrong but after update the version of libvirt
I cannot see the options Hypervisor under settings menu.Has anyone ever seen it before ?
Foreman checks if the ruby-libvirt gem/packages are installed, make
sure they still do.note that you would need to restart foreman afterwards.
Ohad
Hello,
I am seeing an issue where when I start the foreman service and access
the webUI on port 3000 the hypervisor tab/option is present if I turn
off the service and access the site via a passenger configured vhost I
cannot see the hypervisor tab/option at all. Has anyone else seen
this ? Is there a workaround?I’m guessing that you are not running as the same user when you run
passenger, and you have a different set of gems.
in general, foreman detects if the ruby-libvirt gem is installed, if
it is, it enables the hypervisors management.Ohad