QEMU Launcher + 32 bit QEMU pet and sfs

Virtual machines, emulation, etc.
Message
Author
Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#91 Post by Gobbi »

gcmartin wrote: Is there a 64bit ARM processor "generally available" to the public? or is this still pre-release for all except Apple? If the virtual guest code is available, maybe @MikeB can provide in the next release.
You have a good point here ... In Fatdog's 700 repo both qemu packages are for 64bit of both architectures so for now, FD 630 would do fine .

Also interesting : http://en.wikibooks.org/wiki/Multiterminal_with_Xephyr .

Edit : I think I was hasty :oops: naming the Fatdog's 700 package just by copy/paste from nluug.nl site . In the meta files of those packages the platforms are named : arm/x86_64 :!:

And yes - getting out from qemu-kvm with the mouse works with Ctrl+Alt+G .

Many thank's @mikeb , @gcmartin and @Whitesnow :!:

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#92 Post by mikeb »

Is there a 64bit ARM processor "generally available" to the public? or is this still pre-release for all except Apple? If the virtual guest code is available, maybe @MikeB can provide in the next release.
If a binary for such is in the QEMU build then the launcher should automatically add it to the list

Interesting discussion on the multiple user idea.... alternative twist on the multiuser client setup. I have little to contribute unfortunately so you all probably know more than I do. Since linux can allocate multiple input devices I assume its a case of pointing those at a specific application...my only thought was could using vnc help in some way? Also to me it inherently suggests multiple monitors.

mike

User avatar
neerajkolte
Posts: 516
Joined: Mon 10 Feb 2014, 07:05
Location: Pune, India.

#93 Post by neerajkolte »

Gobbi wrote:A second user didn' cross my mind . It could be an option but there is indeed the risk that my wife accidentally mess up somthing because all she does is browsing and now and then something happens ...
Hi Gobbi, I had a similar problem, (you could find my exact problem by going HERE),
Jamesbond has given me answer HERE and HERE.

This method doesn't use KVM though, but uses sandboxing inbuilt in Fatdog. As it's sandboxing I don't think anything done in it will harm your system.
I was unable to get extra set of input devices. But still it works.

Thanks.

- Neeraj.
"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.

Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#94 Post by Gobbi »

Than's @neraajkolte :!:
I shall study the answers and when I'll get home ( a week or more ...) I hope to solve the issue .

stemsee

#95 Post by stemsee »

EmSeeV2.2 32bit also comes kvm working with your launcher built in. I also have a 64bit kernel which boots EmSeeV2.2 32bit OS and this allows you to run 64bit iso with qemu on 32bit platform.

Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#96 Post by Gobbi »

Thank's for for the suggestion @stemsee :!:

However EmSee it is too big for me . It has a LOT of programs that I shall never use . By the way I love the uninstalling option that came with Fatdog64 700 :D .

stemsee

#97 Post by stemsee »

Gobbi wrote: By the way I love the uninstalling option that came with Fatdog64 700 :D .
EmSeeV2.2 has 'remove builtin packages' also it is a remaster with many packages installed with 'synaptic' and 'ppm' that can also be removed by said package managers! Also you can use 'Pfind Find Files' To get rid of anything and simply use one of the remaster programs installed.

I intend to reduce the overall iso size in V3 by at least 1GB. Either by making specialist music apps and QQ (500mb) as sfs addons; WebbQQ works great anyway! However my goal is to include everything I normally use!

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#98 Post by mikeb »

reduce by 1GB!!!!!

Yes sfs for modules much tidier... can you load many.?..I normally have around 20-25 loaded and add rarely used software as needed.

By the way is this painfully off topic :D

mike

stemsee

#99 Post by stemsee »

Yes, sorry, it is off topic a bit!

Curiously if you usually have 20 -25 sfs files loaded, why don't you remaster with your crucial apps and then have only one sfs? I rarely load any sfs modules, occassionally for testing an app before i install the pet.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#100 Post by mikeb »

Well each machine tends to have a different set of apps , loading extra is quick and easy and it keeps the core small to make a ram booting fixit on a usb...not that I ever seem to need that. Also means the base iso sits at around 100MB... faster up/download.

Bleeding slow remaster too..and you can guarantee a mistake along the way...keeping things modularised avoids too many eggs in one basket.

Oh yes testing but very importantly UPDATES...who wants to remaster a GB for just one tiny app?

Its my topic..I can drift as much as I like...ooo the power

Mike the almighty.....

gcmartin

#101 Post by gcmartin »

Hi Mike.

Questions
  • Will there be updates?
  • Will this expand to both 32 and 64bit to keep all in a single place?
  • And, would installation of your QEMU PETs include the Launcher as a builtin feature of the offering this thread presents to ease knowledge to use?
Great little system you have created for all of us.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#102 Post by mikeb »

Hmm well Whitesnow http://www.murga-linux.com/puppy/viewtopic.php?t=88604 was actually putting together QEMU itself...I just threw in the 32 bit one for a newer version to fill the gap. It also seems no puppies support 32 bit KVM.
In other words I am unclear what to do plus i don't have a 64 bit compiling environment on tap.

mike

stemsee

#103 Post by stemsee »

It is the kernel which supplies kvm not the puppy! EmSeeV2.2 has both 32bit and 64bit kernels both with kvm support.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#104 Post by mikeb »

Ok well 'puppy' implies the kernel it comes with...something the user normally would not change.

So only one particular puplet then and no mainstream releases it seems and 'pet' implies we are dealing with puppy.

Thing is I only use QEMU 0.9 and kqemu.ko, so the latest releases are not exactly something I use myself or have the means to fully test....its would be better if said package builder could actually test his or her packages.

mike

gcmartin

#105 Post by gcmartin »

I think what @StemSee is getting at, is one of the primary reason for any user to use QEMU and your Launcher. Here is one case example (AND I DO recognize that some/many 32bit PCs may or may not have the KVM feature for processor acceleration). So for this case, let's assume for the moment that the user has a PC which has CPU virtualizatioin acceleration built-in.

This allows QEMU launch of a virtual PC with a 32bit processor, a virtual PC with a ARM processor, a virtual PC with a 64bit processor, or a virtual PC with any of the various CPU types manufactured in the world without ever having any of them. In other words, if you have a 32bit PC, this thread's stuff allows any user to "MASQUERADE" as any other kind of PC to boot and run a workload.

Of course, I know you already know this, but, any other user reading those recent post may not know that these tools, you present, allow them to do all kinds of running without having to go out and buy another platform to test, compile, build, or run. Thus even with a 32bit platform, one can run and get very good performance in the virtual machine, too.

Hope this helps readers see this as merely one of the many advantages of the Virtual Machine subsystem you provide us via your product mix.

Thus, compiling a 64bit QEMU is a reasonable accomplishment even on a 32bit PC using your Puppy tools.

Here to help

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#106 Post by mikeb »

Well I was basically mentioning that I am not in the best position to support this.

I have an atom machine...I can run lighthouse and build the 64 bit version but not test KVM....but that macine is normally the one my partner uses.
I can build the 32 bit but the lenovo needs a bios flash for KVM so again cannot test it.

Even the gui needs a little second guessing for the above reasons.

mike

stemsee

#107 Post by stemsee »

You enjoy a challenge!!

gcmartin

#108 Post by gcmartin »

BTW for QEMU, version 2.1 is available since month's beginning. Also, version 2.0.2

@MikeB - (I ask because I do NOT have a PC that does NOT have KVM acceleration feature)
Does the Launch utility checkbox for KVM feature, tell the user it is missing should they try to execute the Launcher with the KVM box checked?

Curious

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#109 Post by mikeb »

Does the Launch utility checkbox for KVM feature, tell the user it is missing should they try to execute the Launcher with the KVM box checked?
The arrangement is that the checkbox ONLY appears if KVM is available ... so it's only giving the option of what is actually possible if that makes sense.
You enjoy a challenge!!
The last person that said that to me I made sure I never did any work for him again.
It tended to imply 'here is something everyone else has had a go at trying to sort and made a mess off so now you can sort it out usually for not enough money' :D

mike

gcmartin

#110 Post by gcmartin »

Thanks @MikeB. Excellent, as I remembered you did take KVM implentation into account with the Launcher utility. EXCELLENT!

Post Reply