Puppy linux with virtualbox

Puppy Linux News

Puppy Linux in Virtual Machine

Puppy Linux 4.3.1rc2 in VirtualBox runs well, see the Forum article by playdayz.

. useful for those running Windows, so they might have a Puppy on their desktop.

. needs a physical machine with 1GB ram for VirtualBox and Puppy to run in Windows safely (or at least 768MB. )

1) download and install VirtualBox;
2) download and unpack this zip archive; the archive is 254MB and the unzipped folder is 274MB (the [size] increase over Puppy 4.3.1 is to install the VirtualBox services in order that all features will work; check download with md5sum = ee06f7ac6959b31e012aa8b352e9b849);
3) open VirtualBox and «File -> Import Appliance» and select the ovf file inside the folder Puppy431rc2. When it has been imported, select that virtual machine in VirtualBox and click Start. (Testing in XP, I had to manually enable some of the options such as USB and Network—just look at the list of options when you select Puppy 4.3.1 and click each option and then click the Enable box.)

See also vmPuppy 2.14X (Puppy with kernel 2.6.18 updated by ttuuxxx and running in VMWare).

Added by raffy October 15, 2009 (3:30PM)

stray77 on January 3, 2010 (5:09PM)

Elder Geek,
A battery backup would probably solve your problem about 99% of the time. Just a thought.

Glen on January 2, 2010 (5:14PM)

I am having some trouble with optimal configuration. First, off I cannot get puppy to fill the entire height and width of my screen in fullscreen mode. When I try xorgwizard it just sits there on an empty black screen after saying it may take a while to probe hardware. If I wait long X just restarts itself.

Also when I boot up I get the following message, even though xp is configured for 32 bit color:

edyar on December 26, 2009 (10:00PM)

is there a puppy remaster iso with all the virtualbox things included?
i have a dialup modem.(edimax) it is useless in puppy. so can someone upload his compiled version?

Elder Geek on December 18, 2009 (8:03PM)

I have a VMWare image of Puppy 4.1 that I have set up to act as an OpenVPN server. The only problem it has when it is not shut down properly. Upon the next boot it will not boot to a graphic login screen and has to be shutdown and restarted properly before it will work.

I thought it had to do with me installing to an ext2 partition but it does the same thing even when I changed from ext2 to ext3.

It is just a minor inconvenience. After a power outage someone has to log into the vmware image and restart it properly a second time to get it working. And you can’t do that remotely because OpenVPN is not running.

mark on November 28, 2009 (6:06PM)

OK. Regarding post above. never mind. I was able to get back on after resetting and the system said I didn’t close down X properly last time. I had been closing down using the Machine menu option and «close.» Instead, I am using the lower left Menu option and «shutdown, then power off.» That seems to have solved the problem. I guess I was shutting down VirtualBox and not Puppy Linux first.

mark on November 28, 2009 (2:25PM)

Can you offer some help?

I loaded Virtual Machine on Win XP and successfully loaded Puppy Linux. I followed instructions from here: http://www.virtualboximages.com/GettingStarted

Everything worked fine. until I tried to reboot the session. After I shut down, it won’t boot up again. Get’s hung up during boot process and doesn’t complete the script. I thought it was corrupted so I deleted and downloaded a completely new setup again. And it worked fine again on initial load but it will not reboot after it’s been shutdown.

I’d like to continue experimentation but I don’t know where to start troubleshooting.

As a side note, I loaded an ISO image of another Linux distribution and it worked fine. So because of that I think the problem is in Puppy vs. Virtual Box. Any ideas or thoughts?

Dan on November 13, 2009 (1:27PM)

On the bottom of the VirtualBox window is an icon that looks like a folder, and is for connecting shared host folders with the VB guest.

With the Puppy guest running, add a folder and it’s icon will appear on the desktop or in the Puppy Mount tool. Click on it. It’s mounted.

A 2GB SDA is a portable flash drive.

Wognath on November 11, 2009 (1:16PM)

Can you tell me how to mount the NTFS drive from the virtual Puppy? And can you explain what and where the 2GB sda1 is?
Thanks! I’m going to enjoy this.

raffy on October 17, 2009 (12:15AM)

You can use Puppy Linux search for VirtualBox, an example find is here. That uses Puppy version 2.17, whose kernel is new enough to handle dual-core PCs. There is also Erik Veenstra’s QEMU-Puppy. That also uses Puppy version 2.17.

gcmartin on October 16, 2009 (9:35PM)

Was VirtualBox installed on a Puppy distro.

Sounds like Puppy could be a great VM host (with VirtualBox added), because its so small and fast.

Источник

How to install Puppy Linux In Virtual Box

Hello guys! Today I’m going to tell and show you (using images) how to install Puppy Linux in Virtual Box. If you are a regular visitor then you definitely going to ask why Puppy Linux? then here is your answer and if you’ re not then you are here for this only =)).

This is not the only thing- «to show you how to install Puppy Linux on Virtual Box» but I’m also experimenting with my blog by doing it LIVE.

As I do any step I’ll update this post. Those who saw this post incomplete don’t worry by the end of the day you’ll find it completed (actually it doesn’t going to take that much time :P).

HOW TO INSTALL PUPPY LINUX IN VIRTUAL BOX

1. All you need Virtual Box ( Download it from here ) and ISO Image of Puppy Linux ( Download it from here ).
2. Install Virtual Box in your machine.
3. Click on New Button ->Write Name, select Operating System and Linux Version.
4. Click Next -> On Memory select how much RAM you want you want to allocate to the VM (Virtual Machine).
5. Click Next-> keep the option default -> again Click Next-> New window open «create a new virtual hard disk (VHD)» then again click next-> select which type of storage you want. Dynamic or fixed storage. Here I chooses fixed one.
6. Again Click next. Now you have to set the location and the size of your VHD.
7. Click next and click on finish button. In the end you’ll see summary then again click finish.
8. If you think that’s the end.. its not. Till now we have only create VHD, set RAM for our Puppy Linux but haven’t install it. Now that’s what we need to do.
9. Click on Setting Tab on the top. now click on storage.
10. Click on Empty-> click on folder type icon on the right to open Virtual Media Manager.
11. Click on Add button. Browse and attach Puppy Linux ISO image. Click on Select Button
12. Click On OK button.
13. You are done! Click on Start button.
14. Screen shots coming your way … stay tuned.

Updated

All formatting done!

Keep Linux ready on your machine may be coming software’s, tips and tricks based on Linux and don’t forget to share your ideas, problem with us 🙂

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Linux Hosts
• Change font size
• Print view

• FAQ
• Login

INSTALL VIRTUALBOX ON PUPPY 2.17

INSTALL VIRTUALBOX ON PUPPY 2.17

by puppy-linux » 25. Aug 2007, 21:26

Puppy linux 2.17 missing linux kernel headers in it’s devx_217.sfs ?
Virtualbox won’t compile?

First install libsdl-1.2.9.pet and qt-3.3.6.pet from the pet installer.

download/copy devx_217.sfs and kernel-source_217.sfs to your /mnt/home directory (same folder as pup_save.2fs).

Add the devx_217.sfs and kernel-source_217.sfs files to your boot manager: START — SYSTEM — BOOTMANAGER

in a console type:

and you should get:
cc: no input files

In this case -congrats. — GCC is installed!

Next:
download the any linux distribution from the Virtualbox website:
http://www.virtualbox.org/download/1.4. . ux_x86.run

Next:
issue from a terminal (assuming you downloaded to your /root/my-documents folder):

After install has completed, the installer will recommend a change to your rc.d — do it

Next:
edit the /etc/rc.d/rc.vboxdrv as text and delete the lines 159 to 164:

chown :$groupname $dev || <
rmmod $modname
fail «Cannot change owner $groupname for device $dev»
>

Next: start up virtualbox driver

Finally:
You can now start virtualbox at the command prompt:
# VirtualBox

I have to start the driver again after a reboot:
Start up virtualbox driver:

Puppy / VirtualBox — Next Problem

by puppy-linux » 26. Aug 2007, 13:18

The instructions I added earlier will install VirtualBox onto puppy, however I have no function from the guest network (NAT) at this stage.

Setting to Host Network brings up -3100 error.

Am I missing something?

Puppy Linux 2.17
VirtualBox 1.4.0

by mn_kthompson » 27. Aug 2007, 01:39

What did you do to set up host networking? I’m not familiar with puppy so I can’t promise you any kind of result.

Am I understanding correctly that NAT is working for you, but host networking is not? To set up host networking you’re going to have to create a bridge to your ethernet interface.

Puppy Bridge

by puppy-linux » 28. Aug 2007, 02:40

The problem is almost certainly on my side:
1) My internet is shared in an odd way here — no dhcp
2) I’m fairly new to linux and have problems installing new software to puppy (no apt-get in my version).
3) No uml-utilities in .pup form!

I’ll post the details if I ever get it going.

by Technologov » 28. Aug 2007, 10:37

Puppy is very problematic platform to use as a VirtualBox Host.

It lacks a LOT of packages, including:
-bridge-utils
-uml utils
-Qt
-SDL
-.
-kernel may lack required modules. (TAP, USB DEVICEFS, etc. )

I consider Puppy a toy, not a serious OS.

Puppy may work as Guest.

Puppy as guest

by puppy-linux » 29. Aug 2007, 05:20

I can confirm that puppy makes a good guest os.

What I’m looking for is a simple linux that will host VirtualBox VM’s — puppy is a good candidate because of the 2.6 kernel.

I am still exploring the additional tap tools that innotek provide for non compliant linuxes.

by mn_kthompson » 29. Aug 2007, 14:15

Why does your host operating system need to be so simple? Are you concerned about performance if you use a more full featured host operating system? Are you using older hardware?

I haven’t done any benchmarking, but I feel pretty confident that if you’re running server-level hardware then you should be able to host multiple virtual machines with just about any linux distribution for the host OS. Ubuntu is very full featured, and you can always run the server software which has no gui and leaves off a ton of packages that you wouldn’t need if you were running a dedicated VirtualBox hosting machine.

On my workstation right now I’m running Ubuntu as the host operating system, and I’m running three VMs (one Vista and two XP). If performance is your concern I would say that your biggest bottleneck is going to be RAM, not the host operating system.

by puppy-linux » 30. Aug 2007, 04:14

Keeping it small and simple.

I run good harware, and don’t want it clogged with a gzillion redundant packaged that I dont use or understand.

I’ve looked at Ubuntu and yes — nice enough to want to keep, but too long to install and configure for my purposes.

Puppy has seen me closest to where I want to be ‘out of the box’, runs off a usb key and . rocks . on my home hardware at least.

by dWLkR » 19. Feb 2008, 21:48

i´m also searching for a small hostOS like puppy.

to be honest i´m searching for 2 years by now.

i´ve checked out:
— DSL
— puppy
— feather linux

all awesome small and promising lightweight linux distributions with great hw-detection — that could be very well used as a hostOS for hosting VMs (i.e. vmwareplayer, virtualbox)

i´ve asked many guys hanging around in those forums — asking for their help — but. i never received a «good» reply.

seemingly my idea isn´t worth it :/

my idea is having a very very small linux distribution. no apps included BUT vmwareplayer or virtualbox. the result is the already very well working lightweight linux distribution much smaller and so a perfect platform for hosting VMs. [in kiosk mode]

y don´t i do it myself? hm. well quite simple answer here: my linux-skills are very poor.

so annyone here who is able and willing helping me out here?

just imagine the massive possibilities one would have.

just think of the life of an administrator. his life would be come much much easier.
he would be able to create a perfect VM and run it on almost ANY hardware due to the lightweight linux hostOS.

ok. any volunteers? come on.

by stefan.becker » 19. Feb 2008, 22:06

by dWLkR » 19. Feb 2008, 22:50

another forum — another language — same reply.

Re: Puppy as guest

by ShellyCat » 20. Feb 2008, 07:04

Well, simple is relative.

You might not want a lot of time-wasting (+ space-wasting) apps, but obviously if your machine has a purpose(to run VirtualBox), you must make sure you have the requirements for it.

Smaller Linuxes take less space and are easy (from a newbie standpoint) to install and administer. assuming you have what you need. However, almost all larger Linuxes allow you to choose your installation method, from «just install everything» and «let me choose every little, last detail», somehow.

Personally, I find Slackware 12 http://www.slackware.com (docs at http://www.slackbook.org) the best balance for me. I ike the install the best — except you don’t have a back button during the package selection process . (Hence, the first time I installed it, I reinstalled the next day.) There are a couple of reasons I would recommend it:

1) It uses the 2.6.21.5 kernel (better performance with a VM),

2) Packages are divided into several large, related groups called «series» — for example games. Want no games? Tell the installer in one click!

3) Of the series you have chosen, you can further refine by package — for example, if you want the KDE (K Desktop Environment) but don’t want many of the apps that run on it.

4) It allows you to chose the «Prompting Mode» ( after you select series, which is nice) :
* Full — install every package in the series you selected
* Menu (aka Expert) — select/deselect packages in each selected series’ list
* Newbie — shows you 1 package at a time, with a paragraph or two of description, for you to install or not, from each series you selected

I used Newbie the first time I installed it, could decide what I needed and learn which network utilities were insecure. Newbie takes the longest, but you understand (for the most part) what the heck you’re installing!

So, the first time I installed Slackware I used the «Newbie» prompting mode, whereas during subsequent installations (my laptop, my drive at school) I have used «Menu» or «Full».

Slackware has good hardware support. I haven’t needed any packages not on the DVD except some software I wanted and VirtualBox. For example, I downloaded Avast! Anti-virus for Linux because it will prevent Windows viruses from getting into my Linux system and infecting my Windows VM (otherwise you don’t need an anti-virus on Linux).

With more packages to wade through, Slackware’s installation media can be burned to 1 DVD or multiple CDs, and will take longer to install than puppy, certainly. However, this is balanced by the hours not expended and frustration not experienced by a new user to manually identify, download, install, and configure a bunch of needed packages and dependencies. And Slack is sweetened by the nice menu system and prompting modes in the install routine.

I would bet that even using «Newbie» mode (which I definitely recommend to a Newbie), though it may take a couple hours, is lightyears faster than manually identifying, locating, downloading, installing, and configuring just what you are missing. (And believe it or not, «Full» is actually pretty darn quick. just did it today at school.)

Now people will tell you that you have this great flexibility on all Linuxes (or nearly so), and they’re right! But which packages are on the CD or DVD, and the quality of the configuration and installation menus, really sweeten or sour the deal.

. my opinion happens to be that Slackware has the best blend.

NimbleX, anyone?

by leemathews » 28. Sep 2008, 05:45

Maybe this isn’t as well known as I thought, but NimbleX is a LiveCD distro that weighs in around 200MB and comes with VirtualBox installed.

There are other apps, but it’s pretty lightweight, and the smallest I’ve seen with VBox integrated.

by greenpossum » 28. Sep 2008, 09:10

In practice if you just run a kernel and the bare minimum of services, any server oriented distro can be a minimal host OS for Vbox. I have seen footprints as low as 16MB with a install that doesn’t include X. You would have to manage the VMs using the CLI or RDP but that’s the price. I would say that Puppy’s running an X server will not be able to beat this. (Yes I do know Puppy, I just played with 4.1RC1 a moment ago.)

Then again even if you do run X, VMs for things like XP or Vista which need hundreds of MB, will make the cost of an X server insignificant.

So just because Puppy comes in an ISO greenpossum Volunteer Posts: 98 Joined: 11. Jul 2008, 08:10

Can Puppy Linux be a bootable 2GB Host for my VirtualBox.vdi

by dinooz » 5. Nov 2008, 06:46

Источник