Changes between Version 2 and Version 3 of Ticket #11649, comment 29
- Timestamp:
- Jan 9, 2014 12:14:58 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11649, comment 29
v2 v3 3 3 However, when creating a vagrant box out of it and running 'vagrant up', the crash occurs again! So my wild guess is that vagrant is setting some weird option, which causes the system to crash! 4 4 5 Regarding the NAT setup, one of the differences I've found was, that the 'vagrant box' (the crashing one) sets the NAT ip twice while the 'native vm' (the one not crashing) doesn't do that: 5 Maybe a diff on those two can help you identifying the issue. 6 6 7 vagrant box: 8 {{{ 9 00:00:06.572194 NAT: IPv6 not supported 10 00:00:06.597630 NAT: DNS#0: 192.168.178.1 11 00:00:06.597646 NAT: DHCP offered IP address 10.0.2.15 12 00:00:07.317803 NAT: DHCP offered IP address 10.0.2.15 13 00:00:10.663877 NAT: link up 14 }}} 7 I've added two logfiles: 15 8 16 native vm: 17 {{{ 18 00:00:12.603407 NAT: DNS#0: 192.168.178.1 19 00:00:12.603427 NAT: DHCP offered IP address 10.0.2.15 20 00:00:12.603449 NAT: IPv6 not supported 21 00:00:15.363994 NAT: link up 22 }}} 9 * VM not crashing 10 * Vagrant VM based on the non crashing VM 23 11 24 Maybe a diff on those two can help you identifying the issue. 12 The first logfile is the one, I've setup manually - this one doesn't crash with 'npm install' 13 14 The second logfile is a VM setup by vagrant. It uses the image of the 'VM not crashing' VM. This one crashes when executing 'npm install'
