VirtualBox

Changes between Version 1 and Version 2 of Ticket #11649, comment 29


Ignore:
Timestamp:
Jan 9, 2014 12:11:42 PM (10 years ago)
Author:
machete143

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11649, comment 29

    v1 v2  
    1 I've now also added a logfile with a VM I've set up manually (not through vagrant). This VM''' *does not crash*''' when executing 'npm install'. 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!
     1I've now also added a logfile with a VM I've set up ''manually (not through vagrant)''. This VM '''*does not crash*''' when executing 'npm install'.
     2
     3However, 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!
    24
    35Regarding 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:
     
    192100:00:15.363994 NAT: link up
    2022}}}
     23
     24Maybe a diff on those two can help you identifying the issue.

© 2023 Oracle
ContactPrivacy policyTerms of Use