that's a matter of terminology. i'd argue that what you describe as "host" is rather a management vm which is allowed to talk directly to the hypervisor. thoug

that's a matter of terminology. i'd argue that what you describe as "host" is rather a management vm which is allowed to talk directly to the hypervisor. though, through this privilege is most likely able to compromise it and all other guests. but this doesn't really matter as the attack vector we are talking about already has dma and does not care about any of that.