virtualbox.org

Probabably something in the environment causes my virtual box to chash every weekend.

Can somebody help me isolate the issue from the log?

The crash seems to be related to an intermittent network connection.

Code: Select all

00:01:11.223938 NAT: DHCP offered IP address 10.0.2.15
00:10:16.558321 NAT: DHCP offered IP address 10.0.2.15
12:00:12.348218 NAT: DHCP offered IP address 10.0.2.15
18:06:38.833303 NAT: Link up
20:59:01.705976 NAT: DHCP offered IP address 10.0.2.15
20:59:04.702601 NAT: DHCP offered IP address 10.0.2.15
21:00:17.259119 NAT: DHCP offered IP address 10.0.2.15
21:00:21.262802 NAT: DHCP offered IP address 10.0.2.15
21:01:33.832454 NAT: DHCP offered IP address 10.0.2.15
21:01:37.833051 NAT: DHCP offered IP address 10.0.2.15
21:02:51.391980 NAT: DHCP offered IP address 10.0.2.15
21:02:55.395066 NAT: DHCP offered IP address 10.0.2.15
21:04:07.965772 NAT: DHCP offered IP address 10.0.2.15
21:04:10.963620 NAT: DHCP offered IP address 10.0.2.15
21:05:24.530758 NAT: DHCP offered IP address 10.0.2.15
21:05:28.534184 NAT: DHCP offered IP address 10.0.2.15
21:15:38.237458 NAT: Link up
24:05:24.155199 NAT: DHCP offered IP address 10.0.2.15
24:05:27.150249 NAT: DHCP offered IP address 10.0.2.15
24:06:39.707382 NAT: DHCP offered IP address 10.0.2.15
24:06:43.711718 NAT: DHCP offered IP address 10.0.2.15
24:07:56.275253 NAT: DHCP offered IP address 10.0.2.15
24:08:01.281787 NAT: DHCP offered IP address 10.0.2.15
24:09:13.841253 NAT: DHCP offered IP address 10.0.2.15
24:09:16.840370 NAT: DHCP offered IP address 10.0.2.15
24:10:29.404476 NAT: DHCP offered IP address 10.0.2.15
24:10:32.408970 NAT: DHCP offered IP address 10.0.2.15
24:11:45.968191 NAT: DHCP offered IP address 10.0.2.15
24:11:49.970453 NAT: DHCP offered IP address 10.0.2.15
24:13:03.228319 NAT: DHCP offered IP address 10.0.2.15
24:13:07.231913 NAT: DHCP offered IP address 10.0.2.15
26:06:41.867198 NAT: DHCP offered IP address 10.0.2.15
28:30:24.698315 NAT: DHCP offered IP address 10.0.2.15
39:14:46.750867 NAT: Link up
39:23:16.535259 NAT: Link up
44:14:06.693263 NAT: Link up
44:19:20.194383 NAT: Link up
44:20:45.367124 NAT: Link up
44:22:48.604496 NAT: Link up
44:25:55.927801 NAT: Link up
44:28:01.156367 NAT: Link up
44:29:26.325942 NAT: Link up
44:31:05.508733 NAT: Link up
44:36:14.993135 NAT: Link up
44:38:06.193194 NAT: Link up
44:41:57.565837 NAT: Link up
44:43:54.774700 NAT: Link up
44:45:09.912723 NAT: Link up
44:47:07.110899 NAT: Link up
44:48:56.297747 NAT: Link up
44:50:25.459110 NAT: Link up
44:51:54.614924 NAT: Link up
44:52:43.715237 NAT: Link up
44:53:56.851946 NAT: Link up
44:55:40.030203 NAT: Link up
44:56:51.160602 NAT: Link up
45:00:06.462661 NAT: Link up
45:00:38.882425 NAT: DHCP offered IP address 10.0.2.15
45:00:43.890184 NAT: DHCP offered IP address 10.0.2.15
45:00:50.889459 NAT: DHCP offered IP address 10.0.2.15
45:01:47.627182 NAT: Link up
45:07:55.176496 NAT: Link up
45:11:54.540567 NAT: Link up
45:13:39.711722 NAT: Link up
45:15:16.871282 NAT: Link up
45:16:58.036499 NAT: Link up
45:18:09.158269 NAT: Link up
45:19:32.297512 NAT: Link up
45:21:53.521525 NAT: Link up
45:23:37.813245 
45:23:37.813246 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000005c34!!!
45:23:37.813284 
45:23:37.813284 ExceptionCode=0xc0000094 ExceptionFlags=0x00000000 ExceptionAddress=00007fff1a22a29b

Some of these "Link up" notifications are only minutes apart. Presumably the link went down in between. You could try a bridged networking connection perhaps.

I notice that your Guest Additions have not been updated since 5.2.22, but the ISO is still mounted in the virtual drive.

20MB graphics RAM doesn't seem like enough for an XP guest running FullHD graphics. I would max this out (128MB).

I don't think it is a good idea to put a xp box in the networkwithout a (NAT) firewall in 2019, so not bridging this.
to proof that point: microsoft_com: CVE-2019-0708

I increased the RAM (20MB is the minimal green amount in the gui) of the VGA to 128, and upgrade the client libraries. I will see what this leads to.

Thank you for your advice.

The point was to try a test to determine if the problem is with the NAT code in VirtualBox. Nobody said that the change should be permanent.

leukhe wrote:I increased the RAM (20MB is the minimal green amount in the gui)

VirtualBox has no idea which display size you will eventually choose in the guest OS, so it's up to you to configure it according to your needs.

virtualbox.org

Chrash of virutalbox after weekend. help me read the log.

Chrash of virutalbox after weekend. help me read the log.

Re: Chrash of virutalbox after weekend. help me read the log.

Re: Chrash of virutalbox after weekend. help me read the log.

Re: Chrash of virutalbox after weekend. help me read the log.