[GH-ISSUE #433] BEST DESIGN SCENARIO FOR WEBVIRT AND ITS VIRTUAL MACHINES #326

New issue

Closed

opened 2026-02-27 16:38:53 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 16:38:53 +03:00

Owner

Originally created by @chamambom on GitHub (Sep 15, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/433

I going full force operational into KVM and having tested webvirt in what it can do i have completely fallen in love with it ..... and i have one simple final question that im sure is simple to many

1 ) is it a good design scenario to install it on the host itself or
2 ) to install it on one of the VM that will be residing on the host ....remember on the host thats where the VMs will be residing so technically the webvirtmgr VM will be managing the host it will be sitting on ..

Originally created by @chamambom on GitHub (Sep 15, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/433 I going full force operational into KVM and having tested webvirt in what it can do i have completely fallen in love with it ..... and i have one simple final question that im sure is simple to many 1 ) is it a good design scenario to install it on the host itself or 2 ) to install it on one of the VM that will be residing on the host ....remember on the host thats where the VMs will be residing so technically the webvirtmgr VM will be managing the host it will be sitting on ..

kerem closed this issue

2026-02-27 16:38:53 +03:00

kerem commented

2026-02-27 16:38:53 +03:00

Author

Owner

@michelkaeser commented on GitHub (Sep 15, 2014):

The 2nd one seems quite common (e.g. ConVirture ships its control panel as an appliance...and I guess it's not the only one).

Benefits are:

Easy to backup/restore
Easy to migrate to another host
"Separation" as the node stays clean

If I'd be absolutely sure I am not going to add other HW nodes, I'd stick with the "simpler" 1st approach however maybe

@michelkaeser commented on GitHub (Sep 15, 2014): The 2nd one seems quite common (e.g. ConVirture ships its control panel as an appliance...and I guess it's not the only one). Benefits are: - Easy to backup/restore - Easy to migrate to another host - "Separation" as the node stays clean If I'd be absolutely sure I am not going to add other HW nodes, I'd stick with the "simpler" 1st approach however maybe

kerem commented

2026-02-27 16:38:53 +03:00

Author

Owner

@chamambom commented on GitHub (Sep 16, 2014):

Your argument makes sense and i think i am gonna go with the second option.

@chamambom commented on GitHub (Sep 16, 2014): Your argument makes sense and i think i am gonna go with the second option.

kerem referenced this issue

2026-02-27 16:39:55 +03:00

[PR #326] [CLOSED] Don't show shutdown VMs on the infrastructure page #621