Ah, that's a new one. Either way, it should work!
If the CPU is quite new, and you have Intel VT or the amd equivalent enabled on bios (check the computer manual) you should be able to boot a 64 bit vm on a 32 bit laptop As a side note, if the VM doesn't boot, you can always use the Virtualbox gui to turn the VM on (or tell vagrant vb.gui = true in a virtualbox block) to display there is where will be a clear error on VT/64 Bits issue. Thanks for sharing back your own solution! Alvaro. On Sun, Apr 26, 2015 at 9:55 PM, tolerious <[email protected]> wrote: > Hello Alvaro, I just found the problem, I packaged my vagrant box on my > Mac and it is 64-bit system, but my windows machine is 32-bit system, so > this can not work, I have found the solution in > this thread > *https://groups.google.com/forum/#!searchin/vagrant-up/starting/vagrant-up/TUH7sjBYudU/ZvffTdUs1hMJ > <https://groups.google.com/forum/#!searchin/vagrant-up/starting/vagrant-up/TUH7sjBYudU/ZvffTdUs1hMJ>.* > > Alvaro, very very thank you for your patience and good answers. ^.^ > > On Sunday, April 26, 2015 at 5:44:29 PM UTC+8, Alvaro Miranda Aguilera > wrote: >> >> Hello Tolerious >> >> What's the guest operating system? >> >> if it's some sort of RedHat or derivate you need to do this: >> >> for nic in /etc/sysconfig/network-scripts/ifcfg-eth*; do sed -i >> /HWADDR/d $nic; done >> >> rm /etc/udev/rules.d/70-persistent-net.rules >> >> >> For non Redhat, if the file /etc/udev/rules.d/70-persistent-net.rules >> exist, you need to delete it >> >> >> and finally, if before packaging the box you did kernel upgrade, you need >> to do: >> >> /etc/init.d/vboxadd setup >> >> >> Packer.io is a tool to build boxes automatically, in case you want to >> automate that process. >> >> >> Thanks, >> >> Alvaro. >> >> >> >> On Sun, Apr 26, 2015 at 9:36 PM, tolerious <[email protected]> wrote: >> >>> * First of all, I have setted up my whole developing environment on my >>> Mac vagrant environment >>> * Second, I run `vagrant package` then generated a box named package.box >>> on my Mac stay with the `Vagrantfile` >>> * Third, I copy the `package.box` to my Windows environment >>> * Running `vagrant init tolerious package.box` command, then I run >>> `vagrant up`,but I got this error as follows, >>> >>> >>> <https://lh3.googleusercontent.com/-I5m2HMhAojM/VTyxcDgMyzI/AAAAAAAAAFQ/7jwfXX2bWLk/s1600/QQ%E6%88%AA%E5%9C%9620150426171734.png> >>> >>> >>> >>> I have checked the `vagrant global-status` output, there is a valid id >>> displayed in the list. And I also run the command`vagrant box list`, there >>> is also a valid box added successfully. Anyone has ideas about this error? >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
