Hi all,
I have a Cobbler (2.6.6) instance on a host that's currently connected to one
network. It was a Cobbler testing system that has now proved its worth to us :)
Now I'd like to promote it to the production Cobbler system at our site, and
in doing that, would need to change the hostname
Good to hear to you find Cobbler useful ;-).
From a Cobbler perspective; I think moving should not be more work than
adjusting the server entry in /etc/cobbler/settings en running 'cobbler
sync'.
Good luck!
On Wed, Mar 25, 2015 at 3:59 PM, Will Dennis wden...@nec-labs.com wrote:
Hi all,
Meanwhile I found that there is no crashdump, because the host is a QEMU
virtualized machine, the virtualisation engine takes over this memory dump,
qemu did dump cores however.
From: Joost Ringoot joost.ring...@meteo.be
To: cobbler mailing list cobbler@lists.fedorahosted.org
Sent: Tuesday,
It appears that the virtualisation host reboots the guest because it fails to
grow the QCOW2 volume, so rather a QEMU issue than a cobbler issue:
from tail -f /var/log/libvirt/qemu/mycobblerserver.log, during the critical
event:
qemu-kvm:
