(old)Puppy Linux Discussion Forum

I have tried Precise Puppy 5.7.1 on three further configurations, all failed to boot & were stuck just before the 'depmod' message should have been displayed.

NB The single core allocated to the VM was maxed out at 100% until the VM was closed:

The 3 configurations were:

1) HP XW6200 (Dual XEON 3.2GHz HT enabled, NO VT-x, 4GB ram),
Win 7 Ultimate 64 bit, VB 4.3.6

2) HP XW6400 (Single XEON 2GHz Quad core, VT-x, 6GB ram),
Win 7 Enterprise 64 bit, VB 4.3.6

3) HP XW6400 (Single XEON 2GHz Quad core, VT-x, 6GB ram),
Linux Mint 13 Cinnamon 64 bit, VB 2.10

[Note each configuration had all the latest OS updates applied.]

This disproves my previous assertion that a system having VT-x enabled with the latest VB 4.3.6 makes the difference. It patently does not & would still seem to be highly dependent upon the actual processor in each configuration.

I have this problem as well. I have this working in my laptop with virtualization support enabled and check on enable vt for direct i/o (rebooted twice). I would like this working on my desktop however using the same ubuntu 12.04 64bit virtualbox but no bios for virtualization support.

Puppy 5.7.1 does not boot for me and I do not have the virtualization flag enabled. It very well could be CPU specific, but my curiosity is why just Puppy Linux. Puppy Linux is the only Linux Distribution I have run into with this problem. The newest releases of Debian, Ubuntu, TinyCore, and Lubuntu have no problems booting. Were the most recent versions of Puppy Linux built with some kind of optimization for virtualization?