Re:QEMU: virtfs permits guest to access entire host filesystem
by theamk on Tuesday February 28, 2017 @11:30AM
(#13754937)
Well, Google rightfully said that GCE does not need most QEMU features, so they have made a simplified version. Is is sad they did not release it.
On the other hand, there are people who need QEMU features: we have a QEMU-based test script for boot images which actually uses a few more exotic features to simulate the target environment.
Re:QEMU: virtfs permits guest to access entire host filesystem
by sphix on Tuesday February 28, 2017 @11:51AM
(#13755101)
The Google version is supposedly coupled heavily to their infrastructure and therefore would give little benefit to opensource without also open sourcing a large portion of their infrastructure.
Re:QEMU: virtfs permits guest to access entire host filesystem
by kuschku on Tuesday February 28, 2017 @02:34PM
(#13757029)
> without also open sourcing a large portion of their infrastructure.
Well, that’d not necessarily be bad for the dev community.
Re:QEMU: virtfs permits guest to access entire host filesystem
by bonzini on Tuesday February 28, 2017 @11:39AM
(#13754998)
Red Hat also rips virtfs out of QEMU in RHEL, for what it's worth.
Re:QEMU: virtfs permits guest to access entire host filesystem
by sofaofthedamned on Tuesday February 28, 2017 @03:03PM
(#13757316)
Exactly. Ubuntu didn't and it wasted weeks of development for me.
Re:QEMU: virtfs permits guest to access entire host filesystem
by dward on Tuesday February 28, 2017 @11:05AM
(#13754719)
Ripped it out implies that at one point they used it.
Re:QEMU: virtfs permits guest to access entire host filesystem
by stonogo on Tuesday February 28, 2017 @11:48AM
(#13755077)
No, it means they run binaries compiled with source code from which this feature set has been removed.
Re:QEMU: virtfs permits guest to access entire host filesystem
by brandon on Tuesday February 28, 2017 @11:56AM
(#13755141)
That's not a correct interpretation either; it's noted in the linked article that GCE uses a proprietary VMM instead of QEMU which itself was "ripped out" of the standard KVM+QEMU arrangement.
I probably would have chosen gentler phrasing.
https://cloudplatform.googleblog.com/2017/01/7-ways-we-harde...