Perryg wrote:I am no MAC expert but the log that shows this error is the MAC log correct?
yes it is the hosts log file
If so you also need to look at the VBox guest log and see if it is indicating anything there.
Also look for power management features that may be shutting down the Net adapter on the MAC if it detects no communication for a period of time. Screen savers on the guest may also cause this I think. You can test this by setting up a periodic request on the guest to see if it continues to stay functional like email checks every 5 minutes ETC.
i did another test this night, with one ping from the host to the guest per minute over a bridged adapter. the only thing i found in power management of the host was to disable monitor power save to disable, everything else was already off.
the result was: after approx 40 minutes of operation the interface began to stutter and after 3 more hours it went offine completely. see the sections of the log generated the the ping-script:
So 13 Sep 2009 00:51:13 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=1.098 ms
So 13 Sep 2009 00:52:13 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=0.457 ms
So 13 Sep 2009 00:53:13 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=0.422 ms
...
So 13 Sep 2009 01:27:14 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=0.422 ms
So 13 Sep 2009 01:28:14 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=0.414 ms
So 13 Sep 2009 01:29:14 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=0.423 ms
So 13 Sep 2009 01:30:14 CEST:
So 13 Sep 2009 01:31:25 CEST:
So 13 Sep 2009 01:32:36 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=3625.693 ms
So 13 Sep 2009 01:33:40 CEST:
So 13 Sep 2009 01:34:51 CEST:
So 13 Sep 2009 01:36:02 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=7961.489 ms
So 13 Sep 2009 01:37:10 CEST:
So 13 Sep 2009 01:38:21 CEST:
So 13 Sep 2009 01:39:32 CEST:
So 13 Sep 2009 01:40:43 CEST:
So 13 Sep 2009 01:41:54 CEST:
So 13 Sep 2009 01:43:05 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=4924.311 ms
So 13 Sep 2009 01:44:10 CEST:
So 13 Sep 2009 01:45:21 CEST:
...
So 13 Sep 2009 04:25:09 CEST:
So 13 Sep 2009 04:26:20 CEST:
So 13 Sep 2009 04:27:31 CEST: 64 bytes from 192.168.1.4: icmp_seq=0 ttl=64 time=7963.771 ms
So 13 Sep 2009 04:28:39 CEST:
So 13 Sep 2009 04:29:50 CEST:
So 13 Sep 2009 04:31:01 CEST: ping: cannot resolve pilot.lan.petroni.cc: Unknown host
So 13 Sep 2009 04:32:01 CEST: ping: cannot resolve pilot.lan.petroni.cc: Unknown host
So 13 Sep 2009 04:33:01 CEST: ping: cannot resolve pilot.lan.petroni.cc: Unknown host
So 13 Sep 2009 04:34:01 CEST: ping: cannot resolve pilot.lan.petroni.cc: Unknown host
the guests logfile shows exactly nothing:
00:00:27.950 PCNet#0: Init: ss32=1 GCRDRA=0x1f8c8000[32] GCTDRA=0x1f93a000[16]
00:01:27.646 PCNet#0: Init: ss32=1 GCRDRA=0x1f8c8000[32] GCTDRA=0x1f93a000[16]
08:39:35.289 Entering S5 (power down)
08:39:35.289 ****************** Guest state at power off ******************
08:39:35.289 Guest CPUM (VCPU 0) state: se
it's rather weird, isn't it?
thx & rg.
michael