Stas Sergeev

It is not difficult to allow dosemu to use slirp. We just need to implement popen2()-alike function that uses forkpty() instead of fork() and hook that into ser_init.c. You can...

https://libvirt.org/formatdomain.html#elementsNICSSlirp This of course does not mean libvirt uses slirp. It likely just supports configuring qemu to use slirp.

Not for user as he won't be able to do that by only altering the config. By the way, I see no reason in the use of autoexec for this...

There is no port before you created it with socat! So believe me its a problem.

> I mailed a bit with the Slirp maintainer. With what maintainer? > I understand qemu's code is much uglier than vde though. vde just ported some earlier qemu code....

> I would think that qemu could drop its internal implementation if vde would be supported. And google thinks qemu already supports vde.

> Would you know the name of the shim driver in the newer stack? I really think there is either none or maybe in a form of vxd. Why people...

I don't think its *too* difficult, but definitely quite difficult to not get that before a beta. I think you mostly need to store memory content and mapping patterns, CPU...

So the basic impl is possible, but it will trigger the infinite amount of nasty bug reports.

Does dosbox have such?