The v9fs code has been a <i>major</i> source of bugs. Hopefully no one's using that in production...<p><a href="https://www.cvedetails.com/vulnerability-list.php?vendor_id=7506&product_id=&version_id=&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&month=0&cweid=0&order=1&trc=159&sha=6055b0330a499f6aed7620adb79dc0cc143e50bc" rel="nofollow">https://www.cvedetails.com/vulnerability-list.php?vendor_id=...</a>
Virtfs is a cluster fuck. Using rsync over it creates hundreds of thousands of file handles that never close. Reported to Ubuntu months ago, nothing fixed. Red Hat had the better idea of going nowhere near it. Canonical produce so much shovelware that they don't support, I won't get bit by this again.<p><a href="https://bugs.launchpad.net/qemu/+bug/1336794" rel="nofollow">https://bugs.launchpad.net/qemu/+bug/1336794</a>
Semi hopping on the QEMU bashing train but recall Google ripped it out for GCE.<p><a href="https://cloudplatform.googleblog.com/2017/01/7-ways-we-harden-our-KVM-hypervisor-at-Google-Cloud-security-in-plaintext.html" rel="nofollow">https://cloudplatform.googleblog.com/2017/01/7-ways-we-harde...</a>
From the title I understood this was a feature that had arrived in QEMU, seems like it could have it's place on development machines/etc where the only reason you're using a VM is to get access to some alt. architecture.
Um, silly question. Does this affect people using QEMU to run ReactOS, FreeDOS, and their proprietary counterparts to play old games and use old programs that don't work as well in DOSBox?