361
Applications / Re: VirtualBox 5.0.6 First Impressions
« on: November 12, 2016, 02:36:31 am »
2Doug Bissett:
I don't know what is the VBOX_USER_HOME variable. Never used it. VBox global config is in %HOME%/.config/VirtualBox. Also, older VBox versions used %HOME%/.VirtualBox for that. New VBox can take the older VBox config directory, if it sees it. Also note that the format of XML files has changed, since the old version. And Vbox may convert them to the new format, so then older VBox will not understand them. Virtual machines are located by default in the %HOME%/VirtualBox VMs. Probably, you have left references to old VM dir in global config. You may try to delete the global config, change the path to a VMs dir in it, or change the VM's path in File->Settings->General->Folder for VMs by default.
As I tried TAP in older VBox, it just worked. Never tested its performance, but yes, people said it was very bad. But now it does not work at all.
I mean that ping/tracerte doesn't work as it is in windows or linux. I did not changed anythying specifically for OS/2 host to break it, compared to Linux/Windows. Network code is the same.
Quote
It also appears that the VBOX_USER_HOME environment variable is used in some places, but ignored in others (I HATE using that %HOME% directory). However, that isn't what is causing the problem. I deleted the whole directory from the old VBOX setup, and it still wants to use it. More work to be done there.
I don't know what is the VBOX_USER_HOME variable. Never used it. VBox global config is in %HOME%/.config/VirtualBox. Also, older VBox versions used %HOME%/.VirtualBox for that. New VBox can take the older VBox config directory, if it sees it. Also note that the format of XML files has changed, since the old version. And Vbox may convert them to the new format, so then older VBox will not understand them. Virtual machines are located by default in the %HOME%/VirtualBox VMs. Probably, you have left references to old VM dir in global config. You may try to delete the global config, change the path to a VMs dir in it, or change the VM's path in File->Settings->General->Folder for VMs by default.
Quote
Quote2Andi B.: Network is just the same as it was in older version. NAT just works, as previously. But TAPOS2 is broken -- needs to be repaired. Ping/tracerte not working -- yes.
TAP has been badly broken, forever. It worked, with the old VBox but killed machine (host and guest) network performance. NAT worked fine.
As I tried TAP in older VBox, it just worked. Never tested its performance, but yes, people said it was very bad. But now it does not work at all.
Quote
QuoteBut I suspect it is the same as on Windows an Linux hosts.
I don't understand what you mean by this. TAP is not used with windows, or Linux (AFAIK). There is Bridged network support, which works fine (in windows host, at least).
I mean that ping/tracerte doesn't work as it is in windows or linux. I did not changed anythying specifically for OS/2 host to break it, compared to Linux/Windows. Network code is the same.