[SOLVED] Problem booting Puppy Linux in Virtualbox
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In order for me to get started with Linux, I downloaded & installed Virtualbox (V3.2.10) on my WinXP machine, and downloaded the Puppy Linux image from as per http://virtualboximages.com/GettingStarted.
When I start up the VM, I get a GRUB menu allowing me to boot
Quote:
Linux (on /dev/hda1)
Install GRUB to floppy disk (on /dev/fd0)
Install GRUB to Linux partition (on /dev/hda1)
I tried the first option, which results in
Quote:
Booting 'Linux (on /dev/hda1)'
root (hd0, 0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
[Linux-bzImage, setup=0x1c00, size=0x1b4cd8]
Uncompressing Linux... Ok, booting the kernel.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)
I then tried installing GRUB to the Linux partition, which seems to work, but when I try to boot Linux, I get the same problem.
OK, I solved it:
Uninstalled VirtualBox and installed V2.04, and everything works like a charm. Would it be a good idea to go up in version numbers until I find out where it breaks?
I hope to use this setup to prepare for LPIC1, so expect more braindead question from me in the near future.
I haven't lurked here long enough to know what the general feeling regarding Oracle is, so I apologize in advance if I'm starting a flame war. Having said that, there has been reports that VirtualBox has been getting buggier since Oracle's take-over of Sun.
The article is hardly scientific, but my experience certainly corroborates it in some small way. I am still trying to find the time and motivation to find out precisely where VBox starts breaking.
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,669
Rep:
I'm confused as to why you were playing around with Grub!
I've only played with Virtualbox and have V3.2.10 sitting on an Ubuntu host. (V3.2.10 appears to acknowledge USB drives where older versions don't!) I've only got a single instance of Mint 7 as a Virtual system loaded but it works fine. It didn't have any mention of Grub though? Assuming I had multiple VMs loaded within VirtualBox, I'd just have to select each one and hit "Start" to run them up.
Soadyheid,
I assume GRUB was loaded on the virtual appliance when it was created. If you like, you can download the image I played with from the link in the first post in the thread - its only about 70MB if memory serves. I would actually appreciate it if somebody tried to reproduce what I saw.
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,669
Rep:
JohanB,
Ah.... I can't quite remember how I loaded up my Mint virtual machine. I think I just hit "New" and pointed at either a live CD or an ISO image I'd downloaded - probably the former. Grub may be lurking under the bonnet (hood) but I can't remember it being mentioned during the install. Interesting...
Wary Puppy 5.1.3 installs correctly on Oracle Virtual Box 4.1.1
Use a LiveCD ISO file. Insert it in the VM CD drive and alt-ctrl-del the VM from the VM menu bar.
X windows is not available with Wary Puppy 5.1.3
VBox requires an S3 Trio or VESA 2.0 video driver.
Puppy command line appears to work corrrectly. Not tested beyond verifying that it was a working copy of Puppy as I am trying for a VM with X Windows that will allow me to use internet on host and guest simultaneously.
VBox hijacks my Belkin Wireless adapter preventing the Host OS from using it.
Just completed a Puppy install on VMWare Player.
Under VMWare Player Wary Puppy 5.1.3 installs with no problems (LiveCD again) shares the network connection with the host and runs X Windows (using XVESA at the moment)
Reviving an old thread, but I would have been very happy to have this info a few days ago
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.