Figuring out how pve gui works behind the scene with different architectures

[samip537]

Hi,

I would like to know how does the gui work when you edit the /etc/pve/qemu-server/<vmid>.conf and set it to like aarch64, how does it know how to emulate it?
I have compiled my own version of pve-qemu-kvm deb package, with support for multiple architectures so I would like to know how I can also get the GUI to understand it.

 

[t.lamprecht]

Hi,

The GUI has not really a part in this directly, it's mostly just displaying and providing inputs for the backend.
Most parts of VMs are handled in the qemu-server package, which has already some support for aarch64
Cehckout the git repo and search for aarch64 in PVE/QemuServer.pm to see some details about different handling between x86 and arm: https://git.proxmox.com/?p=qemu-server.git;a=summary

I have compiled my own version of pve-qemu-kvm deb package, with support for multiple architectures so I would like to know how I can also get the GUI to understand it.

Ours ships already support for aarch64 so what other would you need?
And what do you mean when you say "make the GUI understand it", every VM feature would need first support in the backend before the GUI comes into play..

 

[samip537]

Hi,

The GUI has not really a part in this directly, it's mostly just displaying and providing inputs for the backend.
Most parts of VMs are handled in the qemu-server package, which has already some support for aarch64
Cehckout the git repo and search for aarch64 in PVE/QemuServer.pm to see some details about different handling between x86 and arm: https://git.proxmox.com/?p=qemu-server.git;a=summary


Ours ships already support for aarch64 so what other would you need?
And what do you mean when you say "make the GUI understand it", every VM feature would need first support in the backend before the GUI comes into play..

Is the backend the GUI talks to the one you linked as in the qemu-server package?
I need support for mips64 which has been disabled in the pve-qemu-kvm package that's shipped with Promox 6 and that's why I have compiled my own.

 

[t.lamprecht]

Is the backend the GUI talks to the one you linked as in the qemu-server package?

That is part of it, yeah, and for the VM stuff it the main one, there are other packages/repositories for storage management/api, container management/api, ... A full blown hyper-visor with advanced features like Proxmox VE tends to be rather complex, so there's not a single "backend package/repo". In pve-manager all comes together though, it hosts the central API entry points and is the link between all other domain-specific backend code. Further, it hosts the most parts of the PVE webinterface.