As I constanly have troubles with network-bridging in Parallels 2204, I would like to use a different setup.
Host: Ubuntu-Feisty 2.6.20
Guest: Warp 4.5
Starting up the Guest in Parallels quite often kills my servers running on the host, like:
portmap
nfsd
cups-lpd
Also OS/2 freqently crashes with 'trap e in SOCKETS'
This instabilities began with Linux-hosts and kernels > 2.6.18 and it's getting worse and worse.
My idea ist that it is related to the Parallels-module 'vm-bridge'.
Since I am also testing with VirtualBox on Debian-Lenny and Ubuntu-Hardy (amd64 versions) I easily created a permanent software-bridge (br0) on the host system with a virtual tap-device and I can smoothly connect my VM's directly to that tap0. That's great, it uses the Linux based bridge-utils and uml-tools to grant user-access and runs absolutely stable!
Therefore I want to know how to avoid Paralles to load it's own bridge-module and instead directly connect to the virtual tap0 on the host.
This should drastically improve stability.
At least in VirtualBox I was able to set up OS/2-guests with host-based-networking as well and they run already more reliable than in Parallels. So VBox is going to be improved for OS/2 and - most important - also available for amd64-achitecture (with NAT out of the box as well).
Best regards,
Ingo
Last edited: Feb 27, 2008