IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The string on which we were calling c_str() was a temporary, so the C
string returned would no longer be valid. This issue was detected by a
Coverity scan.
Signed-off-by: Zane Bitter <zbitter@redhat.com>
Reviewed-by: Lon Hohberger <lon@users.sourceforge.net>
libvirt-qmf has replaced libvirt-qpid. It performs the same functions, but
has a slightly different schema. It is also a matahari agent, so the
default port to connect to is now matahari-brokerd's port, not qpidd's.
When a host is in one or more groups, present only other VMs that
VM may fence according to its group assignments in fence_virt.conf
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
We were treating 'no path' as 'never match', breaking
fence_virtd's monitoring of VM channel sockets.
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
- never giving up on an invalid domain
- returning failure from reboot (always)
- returning failure from off/on operation when
the domain was in the requested state (e.g. 'on' when
vm was running should succeed, not fail)
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
This allows fencing requests with the appropriate
key file to control VMs assigned to the same
group.
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
- Add cmdline processing for channel_ip
- Allow 'port' to be used in fence_virt mode
- Allow configuration of vmchannel mode for fence_virtd
serial plugin
- Remove serial port default from fence_virt.
It must now be specified or else VM Channel mode
is used. Note that to use VM Channel mode, you need:
qemu 0.12.1 or later
libvirt 0.7.3 or later
- Update man pages
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
Some backends (not yet implemented) which talk to management
layers will have mappings for what VMs can control what other
VMs. So, the source VM UUID of the original request needs to
be sent along with the target VM UUID to the management layer
for arbitration.
Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
