QEMU Launcher + 32 bit QEMU pet and sfs
QEMU Launcher + 32 bit QEMU pet and sfs
This provides a simple light front end to Qemu.
It includes the most commonly used parameters for use with or without kernel acceleration.
A work in progress so feedback is welcome.
You can find a guide to QEMU usage here
http://www.murga-linux.com/puppy/viewto ... 447#775447
Updated to v0.7
Note... due to the simplicity of this pet its safe to simply install over the top of an older version.
Merged the launcher with a 32 bit build of QEMU 2.0.0 with the launcher and made a sfs and pet . Not sure what 32 bit pups have KVM included or whether it could be built independantly...slax 7 does but thats not much use here.
https://www.dropbox.com/s/2z7eu45p5096r ... 4.sfs?dl=1
https://www.dropbox.com/s/m01td6ns8rf16 ... 0.pet?dl=1
If your pup lacks libcurl-gnutls and your full repository also does then ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl-gnutls.so.4 might get you happy...after all its not like gnutls is actually as safe as once considered
Mike
It includes the most commonly used parameters for use with or without kernel acceleration.
A work in progress so feedback is welcome.
You can find a guide to QEMU usage here
http://www.murga-linux.com/puppy/viewto ... 447#775447
Updated to v0.7
Note... due to the simplicity of this pet its safe to simply install over the top of an older version.
Merged the launcher with a 32 bit build of QEMU 2.0.0 with the launcher and made a sfs and pet . Not sure what 32 bit pups have KVM included or whether it could be built independantly...slax 7 does but thats not much use here.
https://www.dropbox.com/s/2z7eu45p5096r ... 4.sfs?dl=1
https://www.dropbox.com/s/m01td6ns8rf16 ... 0.pet?dl=1
If your pup lacks libcurl-gnutls and your full repository also does then ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl-gnutls.so.4 might get you happy...after all its not like gnutls is actually as safe as once considered
Mike
- Attachments
-
- qemugui.png
- (63.81 KiB) Downloaded 1869 times
-
- Qemu_Control_Center-0.7.pet
- (7.95 KiB) Downloaded 1208 times
Last edited by mikeb on Wed 20 May 2015, 12:16, edited 14 times in total.
Hi, mikeb.
I'm an ignoramus when it comes to QEMU. A few questions, if I may:
* What's so good about it?
* How does it compare to DOSBox?
* Is there a manual or how-to somewhere?
* What's your context? I mean: why did you feel the need to "knock up" this script?
Thanks in advance.
musher0
I'm an ignoramus when it comes to QEMU. A few questions, if I may:
* What's so good about it?
* How does it compare to DOSBox?
* Is there a manual or how-to somewhere?
* What's your context? I mean: why did you feel the need to "knock up" this script?
Thanks in advance.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Installed Launcher on LightHOuse64-602 (LH64). Menu>Utility>QEMU Launcher to desktop as shown below. I left if on desktop for several minutes and when I returned I got an authority request as shown below.
Clues why the Launcher sitting empty on the desktop would cause this message to occur with no activity from keyboard/mouse? Also, message refuses to die, an immediately regenerates when killed from HTOP. The killer of this was to stop the desktop (Ctrl-Alt-Bksp) and restart.
Reconnection to LAN and simple restarting the Launcher as the ONLY desktop activity, I am NOT able to recreate the problem. Any ideas pro/con would be helpful.
Thanks in advance for any guidance.
Edit: I have been able to have this problem resurface. It seems that there may be something happening when the browsers are open when this occurs. I am still trying to gather more information.
Clues why the Launcher sitting empty on the desktop would cause this message to occur with no activity from keyboard/mouse? Also, message refuses to die, an immediately regenerates when killed from HTOP. The killer of this was to stop the desktop (Ctrl-Alt-Bksp) and restart.
Reconnection to LAN and simple restarting the Launcher as the ONLY desktop activity, I am NOT able to recreate the problem. Any ideas pro/con would be helpful.
Thanks in advance for any guidance.
Edit: I have been able to have this problem resurface. It seems that there may be something happening when the browsers are open when this occurs. I am still trying to gather more information.
- Attachments
-
- Error message pops minutes after Launcher sits open on desktop.png
- Erroneous message pop-up. Unable to kill it!!!
- (8.53 KiB) Downloaded 3738 times
-
- QEMU sits open on LH64 desktop.png
- Launcher sitting with NO desktop changes or user touches
- (43.82 KiB) Downloaded 3548 times
QEMU is a subsystem for describing a PC virtually for running on your desktop. It describes PCs...NOT distros. With a virtual PC you can boot any distro you choose.
QEMU tells your system what that virtual PC is to look like by providing mandatory and optional items used in a PC. The mandatory description is the type CPU (32/64/AMD), amount of RAM, and the LAN card. The optional items are the DVD, the HDD, and etc. Once defined, QEMU Launcher will initiate the sequence you specify so that the virtual PC boots in a window (the virtual PC display) on your desktop
Here's a diagram useful as an example in understanding the kind of service QEMU sets up where it has not one but 2 virtual PCs active with their own PUP distros, along side your running PUPPY desktop.
Image: Compliments of Puppy member @Rufwoof
Here to help
QEMU tells your system what that virtual PC is to look like by providing mandatory and optional items used in a PC. The mandatory description is the type CPU (32/64/AMD), amount of RAM, and the LAN card. The optional items are the DVD, the HDD, and etc. Once defined, QEMU Launcher will initiate the sequence you specify so that the virtual PC boots in a window (the virtual PC display) on your desktop
Here's a diagram useful as an example in understanding the kind of service QEMU sets up where it has not one but 2 virtual PCs active with their own PUP distros, along side your running PUPPY desktop.
Image: Compliments of Puppy member @Rufwoof
Here to help
Last edited by gcmartin on Thu 01 May 2014, 23:14, edited 3 times in total.
that drive manager ...is it a barry thing or gnome?
Qemu uses /dev/shm so the gui alters the size of that to suit the size of virtual ram .. only thing that might cause a warning that I can think of but then again it may be unrelated. Also of course if you request 1GB virtual ram and there is only 512MB that could pose a problem....
Could also be the USE of /dev/shm conflicting with another app...
interesting questions....
Nothing to do with DOSbox... I prefer DOSemu by the way
Manual...well I suppose the QEMU website might help...this is just an add on for QEMU users so I assume they would already be familiar or have a suitable reference.
I knocked up the script as I often do to make it easier to use rather than remembering/creating a long command line which is the usual way QEMU is used so making it hopefully more user friendly like Virtual Box is.
Context...gcmartin requested I made a thread of it as he thinks I should and to perhaps help develop it which seemed a good idea.
Hope that makes sense
mike
Qemu uses /dev/shm so the gui alters the size of that to suit the size of virtual ram .. only thing that might cause a warning that I can think of but then again it may be unrelated. Also of course if you request 1GB virtual ram and there is only 512MB that could pose a problem....
Could also be the USE of /dev/shm conflicting with another app...
interesting questions....
QEMU is a virtual; machine emulator in the same way that virtual box is. QEMU is pretty simple in use though it might be a case of who came first. Might be faster but I am not sure on that.* What's so good about it?
* How does it compare to DOSBox?
* Is there a manual or how-to somewhere?
* What's your context? I mean: why did you feel the need to "knock up" this script?
Nothing to do with DOSbox... I prefer DOSemu by the way
Manual...well I suppose the QEMU website might help...this is just an add on for QEMU users so I assume they would already be familiar or have a suitable reference.
I knocked up the script as I often do to make it easier to use rather than remembering/creating a long command line which is the usual way QEMU is used so making it hopefully more user friendly like Virtual Box is.
Context...gcmartin requested I made a thread of it as he thinks I should and to perhaps help develop it which seemed a good idea.
Hope that makes sense
mike
@Musher0 poses a good question. And the diagram I provided, although at the time seemed like a good picture, could probably be adjusted to give a little better reflection of what this Launcher makes representing a PC's hardware, virtually.
Edit: I added additional info to assist understanding what the Launcher does for any user....below, here. Its one manner of viewing its benefit.
Launcher makes "visual" what is contained in a QEMU command-line (cli) setup of any virtual PC. Another one of its benefit is to reduce cli typos that are often made when typing any long command. And, it makes easier for anyone to understand what they do to setup and boot another distro while the main distro is running.
Hope this is helpful
Edit: I added additional info to assist understanding what the Launcher does for any user....below, here. Its one manner of viewing its benefit.
Launcher makes "visual" what is contained in a QEMU command-line (cli) setup of any virtual PC. Another one of its benefit is to reduce cli typos that are often made when typing any long command. And, it makes easier for anyone to understand what they do to setup and boot another distro while the main distro is running.
Hope this is helpful
QEMU Launcher tested
Thanks @MikeB for this utility
QEMU Launcher tested in the following LiveDVD booted-running systems:
Here to help
QEMU Launcher tested in the following LiveDVD booted-running systems:
- FATDOG where I booted Slacko570 ISO in a guest (vPC)
- LightHouse64 where I booted Slacko570 ISO in a vPC
- Slacko64 where I booted Slacko570 ISO in a vPC
- Real PC
- AMD X2
4GB RAM
Single LAN housing a 8 year old NAS containing the Slacko570 ISO
- AMD X2
- Virtual PCs
- 8GB Swap partition on the local HDD
Guest assigned 512MB when booted
No vHDD assigned to guest for any testing. All guest operations run in its RAM
- 8GB Swap partition on the local HDD
Here to help
- neerajkolte
- Posts: 516
- Joined: Mon 10 Feb 2014, 07:05
- Location: Pune, India.
Hi mikeb,
Just downloaded and installed the pet but couldn't run qemu.
So replaced /usr/bin/qemu_nim script with the hacked one given by you on other thread by Pentium44. It works nicely.
Comparing both script I could see the original uses kqemu while hacked one uses kvm.
My question is can those two scripts be combined so that they can work with both systems, either which have kqemu module or which have kvm support built in kernel and uses qemu.
Just downloaded and installed the pet but couldn't run qemu.
So replaced /usr/bin/qemu_nim script with the hacked one given by you on other thread by Pentium44. It works nicely.
Comparing both script I could see the original uses kqemu while hacked one uses kvm.
My question is can those two scripts be combined so that they can work with both systems, either which have kqemu module or which have kvm support built in kernel and uses qemu.
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
well that is partially the idea ...just at the testing stage for now.My question is can those two scripts be combined so that they can work with both systems, either which have kqemu module or which have kvm support built in kernel and uses qemu.
Not sure about the older qemu / kqemu if no one is using it though its not a major headache to include both.
The pet just adds a convenient menu entry so we will be testing just the script for now...once finalised a fresh pet will be made.
mike
Why not simply use this
https://packages.debian.org/squeeze/qemu-launcher
after all size is not an issue here since 90% of the qemu package is redundant on puppy why not add a few hundred k for the official gui?
mike
https://packages.debian.org/squeeze/qemu-launcher
after all size is not an issue here since 90% of the qemu package is redundant on puppy why not add a few hundred k for the official gui?
mike
Run different PUPs on yur desktop without ever shutting down
The Puppy Linux QEMU Launcher is great utility providing a simple function to boot other PUPs while running your main PUP. It disappears from RAM after its use. It is a quite simple tool.
A guide showing its use, in action, can be found here.
The debian tool is a fuller offering, yet a good representation to ALSO get subsequent distro booting on the PC while running the main distro.
Maybe this implementation can be termed "Light for Puppy" while Debian is "Full" (assuming the name in this thread's title remains).
Thx @MikeB for what you have done to assist multiple distro operations on a PUP desktop using the Linux Kernel Virtualization Mechanism.
A guide showing its use, in action, can be found here.
The debian tool is a fuller offering, yet a good representation to ALSO get subsequent distro booting on the PC while running the main distro.
Maybe this implementation can be termed "Light for Puppy" while Debian is "Full" (assuming the name in this thread's title remains).
Thx @MikeB for what you have done to assist multiple distro operations on a PUP desktop using the Linux Kernel Virtualization Mechanism.
Well a package built especially for the job might in this case make more sense plus I am a little out on a limb here not being able to test current qemu for whatever reason. I could still see what I can do as is...
Main thing with the debian/ubuntu set might be if puppies cut down perl is sufficient enough.... from a quick look I don't think the result would be too large.
mike
Main thing with the debian/ubuntu set might be if puppies cut down perl is sufficient enough.... from a quick look I don't think the result would be too large.
mike
Ok well life has allowed me to do a bit on this...
Here is an update to test out....
Changes include
mike
edit...removed thee totally buggy efforts
Here is an update to test out....
Changes include
- determination of qemu binary...its assumed that if 64 is present its a 64 bit system....some packages throw in the lot so gets a bit silly...
Adjusted KVM detection and selection... if kvm is not present option is disabled and enabled with option if available.
Silently boots from optical drive if no hard drive image is present.
Added 2048 virtual memory for the big boys
Added version number to avoid mixups.
Slight gui rearrangement.
Renamed to qemu_gui
mike
edit...removed thee totally buggy efforts
Last edited by mikeb on Sat 10 May 2014, 17:22, edited 2 times in total.
Without uninstalling the existing PET, I moved the qemu_gui from /root/spot to /usr/bin. Here are the results:Editing the file and removing the "=" signs, it immediately goes directly to booting a virtual PC without any apparent parameters....twice! before returning to original terminal window.
Launching from the Menu>Utility>QEMU ... continues to execute the old version window with window titlebar and options in the window, still showing same as before.
Need review.
Code: Select all
bash-4.1# which qemu_gui
/usr/bin/qemu_gui
<root> ~
bash-4.1# qemu_gui
/usr/bin/qemu_gui: line 4: =/usr/bin/qemu-system-i386: No such file or directory
/usr/bin/qemu_gui: line 5: =/usr/bin/qemu-system-x86_64: No such file or directory
<root> ~
bash-4.1# echo "edit both lines 4-5 removing the '=' signs"
edit both lines 4-5 removing the '=' signs
<root> ~
bash-4.1# qemu_gui
<root> ~
bash-4.1#echo "No messages, BUT, no Menu. AND the utility opens a virtual PC without parameters. When guest is closed, a 2nd guest is opened. Closing a 2nd, returns to terminal."
No messages, BUT, no Menu. AND the utility opens a virtual PC without parameters. When guest is closed, a 2nd guest is opened. Closing a 2nd, returns to terminal.
<root> ~
bash-4.1#
Launching from the Menu>Utility>QEMU ... continues to execute the old version window with window titlebar and options in the window, still showing same as before.
Need review.
Problem with latest version 0.2:
- Downloaded Launcher
- extracted Launcher
- moved Launcher to /usr/bin
- Open terminal and typed /usr/bin/qemu_gui
- filled in the ISO name, selected RAM, and clicked to run.
- Error without booting ISO (see below)
- Attachments
-
- Latest Launcher GUI.png
- Line 18 errors out
- (184.59 KiB) Downloaded 633 times
Right then .. no mysterious bugs going on so I have a clear head...helps a lot.
Made a logical blunder with qemu binary detection...2 for 2
While I was in there I redid the /dev/shm setup especially as most pups now have it anyway.
Now its only created if there is none and its only resized if not sufficient for the virtual ram requested.
This and a couple of other things should stop any bogus error messages,
Since its modded it gets a new number and hopefully THIS TIME all runs and we can progress to other matters and make a fresh pet of it
if not I wish to move to a deserted island and write my memoirs
Also I think incorporating kqemu and kvm in the same gui might get confusing so will probably keep separate.
mike
Made a logical blunder with qemu binary detection...2 for 2
While I was in there I redid the /dev/shm setup especially as most pups now have it anyway.
Now its only created if there is none and its only resized if not sufficient for the virtual ram requested.
This and a couple of other things should stop any bogus error messages,
Since its modded it gets a new number and hopefully THIS TIME all runs and we can progress to other matters and make a fresh pet of it
if not I wish to move to a deserted island and write my memoirs
Also I think incorporating kqemu and kvm in the same gui might get confusing so will probably keep separate.
mike
- Attachments
-
- qemu_gui-0.2.1.tar.gz
- (1.75 KiB) Downloaded 549 times
Last edited by mikeb on Sun 11 May 2014, 12:43, edited 1 time in total.