You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to manage my existing VMs with Archipel, the following happens:
High CPU usage on browser
Login gets kicked off forcing to log back in
Hypervisor now causes high CPU usage on browser when I click on the Virtual Machines section of the hypervisor
This slowness does not stop until I remove the new VMs and the hypervisor from ejabberd and restart the agent.
While it appears that no errors are occurring and ejabberd creates the XMPP profiles for the VMs properly and Archipel sees my existing VMs, this happens whenever I attempt to manage a VM with Archipel, this includes making a new one.
I am currently running Archipel on an ArchLinux host with an existing KVM/QEMU hypervisor that I manage through virt-manager.
The text was updated successfully, but these errors were encountered:
I'm running into the same problem, did you ever find a workaround ?
I've just installed Archipel, managed to add my hypervisor, and since I tried to create a VM from Archipel that menu just keeps crashing my browser tabs, over and over. Tried both firefox and chrome, just in case, but doesn't look like it's usable at all :(
Okay, I figured it out. For some reason my /var/lib/archipel/avatars was empty, and it looks like that makes the vCard creation process fail. Apparently no-one ever planned for that, the web interface goes crazy as soon as there is a "failed" VM. To solve that I killed archipel and the central agent, unregistered the VM from ejabberd and downloaded the missing jpegs. Then I re-started archipel and the central agent, and they re-created the user with the vCard correctly, and everything started working.
When attempting to manage my existing VMs with Archipel, the following happens:
While it appears that no errors are occurring and ejabberd creates the XMPP profiles for the VMs properly and Archipel sees my existing VMs, this happens whenever I attempt to manage a VM with Archipel, this includes making a new one.
I am currently running Archipel on an ArchLinux host with an existing KVM/QEMU hypervisor that I manage through virt-manager.
The text was updated successfully, but these errors were encountered: