Returning obsolete or wrong settings for VMs and Container

[batesman73]

Hi there,

 

maybe I didn't search the right way but I couldn't find the answer although I'm sure not to be the only one having such issues.

Anyhow ....

 

VMs

I'm using debian (and ROON ROCK what seems to be based on debian) for my VMs and can't get them up without changing the network to "e1000-82545em". Every time I do a modification on those machines I have to change the network settings again manually in the ".xml"

 

Docker

I have some containers which have additional default settings I don't need (for example "transmission-openvpn"). But I need to remove them to get the container running properly. Here again ... everytime there's an update on those containers or i modify them the same old settings appear again.

 

This is a very annoying behaviour. Is there a way to solve that issue ?

 

BTW: Can someone explain why my system (Ryzen 3900x, Gigabyte Aorus elite, several disks and a dvb card) draws nearly 80W in idle while under Proxmox the same setup needs only a bit more than 60W.

[itimpi]

There is a known issue For some time where once you have made changes in XML view can no longer use the form view without losing changes made in XML view.

[batesman73]

I already read that about VMs and was hoping for a solution.

But what about these docker issues ?