Opened 18 years ago
Closed 16 years ago
#800 closed defect (worksforme)
Network regression (Linux host, W2003 Server guest)
Reported by: | ugemkow | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 1.5.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
When upgrading from 1.5.0 to 1.5.2, networking no longer works in our configuration. Going back to 1.5.0 solved the problem.
The guest (Windows 2003 server) was not able to send packets, it seemed it was able to receive packets.
Attachments (2)
Change History (12)
by , 18 years ago
follow-up: 2 comment:1 by , 18 years ago
According to your VM configuration you should have already created and configured (and accessible by user) 'tapv3' interface on the host, correct?
Tried same configuration, works fine.
comment:2 by , 18 years ago
Replying to Lelik:
According to your VM configuration you should have already created and configured (and accessible by user) 'tapv3' interface on the host, correct?
This is correct. All is done by scripts which also start the VM. These scripts are unmodified between 1.5.0 and 1.5.2 and run automatically, so I am pretty sure that the same configuration is used with 1.5.0 and 1.5.2.
Tried same configuration, works fine.
Our configuration is a little bit special as it uses routing (not bridging). I will try to debug a little bit and get more insight in the problem and come back to this (have to wait for the weekend, it is a production system)
Thanks so far
comment:3 by , 17 years ago
I now checked once again carefully and the problem remains:
When starting my vm with 1.5.0, all works fine, the guest is reachable through the network. When updating to 1.5.2 and performing exactly the same steps as with 1.5.0 (I am sure - this is completely script based) the guest is not reachable.
We use a somehow unusual networking config (routed)
Unfortunately it is rather difficult for me to debug this, this is a production system which I can stop only for short periods of time.
comment:4 by , 17 years ago
There is a regression in 1.5.2 where network send did stop after a snapshot was created. Could this be your issue, that is, are you working with snapshots?
comment:5 by , 17 years ago
Thanks for the answer. Unfortunately I do not use snapshots, so this is not the problem.
comment:8 by , 17 years ago
The same regression remains in 1.5.6 (and also the reported problem that reverting to an older version of vbox in the same release does not work because of changes in the xml-description file)
comment:9 by , 17 years ago
Component: | other → network |
---|
comment:10 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Retry with a 2.1.2 and reopen if required please.
Machine description file