QEMU Launcher + 32 bit QEMU pet and sfs

[mikeb]

ah ok...sounds lke something gtk2 related and probably just ignored as incomplete...after all its being called via dbus so not a hard dependancy.
Its gnomes mechanism for showing networked drives in the interface which I am pretty sure is not supported on puppy.

mike

[Gobbi]

I gave a try using Quemu Launcher in Fatdog64 630 . It launches Quemu 1.5.3 .
I make this experiment on my brother in law's machine an HP G6 laptop - last night my old Fujitsu Siemens had a heart ( CPU ) attack . Too much work in a warm enviroment , I guess . After seeing the BIOS a few seconds the screen turns black . And I'm far from home , so no main computer available...
I tried an booted with no hdd : Siltaz , Carolite1.2 and CompizPup 14.03. All of them slow , then I remembered to take a look in the BIOS to enable virtualisation . Indeed they all booted fast, very fast , the broswser opened at once the homepage .
One thing I noticed : the usb optical mouse I used was showing a lag , like when you have sometimes in VirtualBox. Instead , from the touch pad the speed of the cursor was much bigger even that the native one ( the host's one ).
My old laptop , was the one I had given to my wife for browsing... Now , since at home I have 2 monitors and 2 wireless input sistems it would be something if , by being able to edit xinit start files , to give separate command to one of the Logitech input sistems for Qemu . I don't think I can doi by myself , but it sure worth trying...

Question if KVM is checked ( it was ) that mean it is actually running from the launcher ?

[mikeb]

Hmm not sure on the mouse lag issue... others may have a clue or perhaps the QEMU site may have somewhere like a forum to ask.

Question if KVM is checked ( it was ) that mean it is actually running from the launcher ?

If a KVM option is showing it means that KVM is available...if its ticked then it will be used. At least thats the idea Faster execution is yer usual clue.

Mike

[Illutorium]

I gave a try using Quemu Launcher in Fatdog64 630 . It launches Quemu 1.5.3 .
I make this experiment on my brother in law's machine an HP G6 laptop - last night my old Fujitsu Siemens had a heart ( CPU ) attack . Too much work in a warm enviroment , I guess . After seeing the BIOS a few seconds the screen turns black . And I'm far from home , so no main computer available...
I tried an booted with no hdd : Siltaz , Carolite1.2 and CompizPup 14.03. All of them slow , then I remembered to take a look in the BIOS to enable virtualisation . Indeed they all booted fast, very fast , the broswser opened at once the homepage .
One thing I noticed : the usb optical mouse I used was showing a lag , like when you have sometimes in VirtualBox. Instead , from the touch pad the speed of the cursor was much bigger even that the native one ( the host's one ).
My old laptop , was the one I had given to my wife for browsing... Now , since at home I have 2 monitors and 2 wireless input sistems it would be something if , by being able to edit xinit start files , to give separate command to one of the Logitech input sistems for Qemu . I don't think I can doi by myself , but it sure worth trying...

Question if KVM is checked ( it was ) that mean it is actually running from the launcher ?

When if you have a 64bit... That's not even depend a 32bit QEMU (max. 4GB)... When Try Download a 64bit QEMU instead...

[gcmartin]

Hello @Illutorium.

This QEMU Launcher merely sets up a "Virtual computer" which your ISO/image will boot into. Most PCs/Laptops over the past 8 years are 64bit PC, so the default used is the one you see. You can freely elect to choose another PC type via that selection box. When that image boots, it will see something which looks like the PC you choose.

Next, in understanding: You can freely boot any 32bit ISO/image on any 64bit PC, just as you can on any real PC. BUT, just as on any real PC, you cannot boot a 64bit ISO/image on a 32bit PC. Further, in the past, it has been shown that there is no performance penalty in operating a 32bit OS on, either, a 32bit PC or on a 64bit PC. So, either way, you should expect you VM guest to behave the same no matter which selection you make. (But, it would be interesting to check this via Hardinfo for some validation data. There may be some surprises lurking in the virtual operation that would not be seen from equivalent clock-speed real PCs.)

So, please remember, that the QEMU Launcher merely is to create a PC of your selection for your ISO/image to run in, virtually (thereby, it creates a VM guest). And remember KVM, a feature of Linux, just takes advantage of your real CPU's hardware to accelerate the VM guest to full CPU speed.

Hope this helps in understanding.

[gcmartin]

Hello @Gobbi

I think that you may have seen the reference to KVM in the prior post.

You post a very interesting request that I would like to zoom upon. Are you asking:

• Can 1 person be working on the main monitor with keyboard and mouse (the VM host) AND have a 2nd keyboard and mouse being used with a VM guest showing on a 2nd monitor? Thus, this would allow 2 people to be using the same PC at the same time in the same room.
  
  >>>>> OR <<<<<
• Can you have 1 person running on the VM host while another is running the VM guest from across the LAN?

Mind you, that I know NOT how to do this, but am trying to properly frame your request.

[Gobbi]

Hi, @gcmartin

It is the first option which would be very interesting and practical in my ( domestic ) case . The second it is an expanding ( valuable too )which go further , but I don't use a LAN network at home.
Maybe pcma kers are not too happy about these arguments...

[gcmartin]

OK, the issue here is how to have a PC which has a 2nd set of keyboard+mouse which can be allocated to a running VM guest.

If there IS a way to allocate these resources then one could start a 2nd ID running on the PC where it would use the 2nd set AND the 2nd Monitor for its desktop. There, the 2nd user could do anything you allow it to do. But, I would be careful with 2 root users (namely 2 different people with Admin authority running on the same PC at the same time) . Thus, I can see the advantage you seek by isolating the 2nd person to a VM guest where their authority would ONLY exist within the Guest.

I do know how to allocate a 2nd user desktop (per @Kirk/@JameBond years ago), but I don't know how to have the session start with the capture of the physical resources that the user would use. To run a 2nd-separate user desktop see the attached script to do so (this has been used in, both, FD64 and LH64)

ANYONE know how these resources can be isolated for allocation?

[Gobbi]

Thank's for tying @gcmartin

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 ...
A qemu-kvm solution has already solved networking , desktop and for what I am concerned a bit of safety .
I also found this : http://automseat.sourceforge.net/ but I only have a card ( good enough , yeah ) , and their solution needs more than one ... But I think it could be a good start for searching a good solution .

I shall also take a look here : http://www.x.org/wiki/Development/Docum ... Multiseat/


On the other hand - using @Whitesnow's Qemu 2.0.0 x86_64 pet and sfs with Qemu Launcher solved the problem of mouse or touch pad speed but once grabbed by the Guest , I couldn't regain control of the cursor for the Host system with Ctrl + Alt .

A quemu launcher for qemu-arm-x86_64-2.1.0-x86_64-1 package of Fatdog 700 would really help ...

[gcmartin]

... On the other hand - using @Whitesnow's Qemu 2.0.0 x86_64 pet and sfs with Qemu Launcher solved the problem of mouse or touch pad speed ...

Great, I have only used V2 of recent too.

... but once grabbed by the Guest , I couldn't regain control of the cursor for the Host system with Ctrl + Alt ...

That should be "Ctrl + Alt + G"

... A Qemu Launcher for qemu-arm-x86_64-2.1.0-x86_64- ...

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.

Hope this helps

[Gobbi]

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 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

[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

[neerajkolte]

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.

[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]

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]

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 .

[stemsee]

By the way I love the uninstalling option that came with Fatdog64 700 .

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!

[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

mike

[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.

[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.....