On 12/04/18 11:54, mpho raffiki wrote:
> Hi Milan
>
> The issue is that debian does not have the proper symbolic link of the
> kernel device /dev/vport2p1. another issue for it not to work; is that
> when you look at the device attributes for vport2p1 the attribute name
> is something else under
Hi Milan
The issue is that debian does not have the proper symbolic link of the
kernel device /dev/vport2p1. another issue for it not to work; is that when
you look at the device attributes for vport2p1 the attribute name is
something else under debian stretch (ATTR{name}=="ovirt-guest-agent.0" )
Package: ovirt-guest-agent
Version: 1.0.13.dfsg-2
ovirt-guest-agent 1.0.12.2.dfsg-2 doesn't work with oVirt 4.2 due to
changed paths. But when one upgrades to 1.0.13.dfsg-2, the agent still
doesn't start and it's necessary to reboot the system or to trigger the
necessary changes manually:
3 matches
Mail list logo
