in reply to Roland Häder🇩🇪

friendica (DFRN) - Link to source

Roland Häder🇩🇪

@verita84 @Rock DJ 
$ ./occ app:update --all
calendar new version available: 5.5.5
calendar updated
previewgenerator new version available: 5.10.0
previewgenerator updated
notes new version available: 4.12.3
notes updated
integration_tmdb new version available: 2.2.1
integration_tmdb updated
twofactor_email new version available: 2.8.2
twofactor_email updated
mail new version available: 5.5.5
mail updated
oidc new version available: 1.9.0
oidc updated
bookmarks new version available: 15.2.0
bookmarks updated
passwords new version available: 2025.9.10
passwords updated
quota_warning new version available: 1.22.0
quota_warning updated
event_update_notification new version available: 2.7.0
event_update_notification updated
contacts new version available: 7.3.2
contacts updated
$
@verita84 @Rock DJ
Unknown parent

gharab-tzereq - Link to source

🎃Jester-Abyss-ephEmeral-333🎃™

@dcc

the reason you run kvm's is either for software that can't be updated with the main system, or to use another os like windoze.


sure, that's two use-cases but there's quite a few more. for example.

  • workload/machine isolation
  • increase of compute density
  • ease of bootstrapping infrastructure via code (terraform/pulumi/raw sdk-api)
  • potential for ha/clustering of kvm hosts (proxmox and other t1 hypervisors can do this)
  • load-balancing workloads (proxmox-lb)
  • easy throw-away targets for new configurations/automations (i.e. ansible or chef)
  • separation of concerns (ie client machines vs hobby machines)

now before you say something like, "i don't do this on my server" or "i run slackware". that's great! but not everyone wants to compute like that.

@✙ dcc
⇧