Lol I did strawbale as well and that was my first choice for my land even got my Strawbale book signed by the Author and toured mulitple houses under construction in central Texas..
Got the bales for a small started cabin and came down with a persistent flu like problems and had a series of tests and learned I was very allergy to a type of mold commonly found in straw. That dream gone so I turned to earthblock had my soil tested ( really good for this use ) and took classes there I talked to the guy about the roof method I am going to use. Since he taught classes for that in Mexico. But I also have a rare type of soil ( earthblock guy said was around here ) that reacted violently when exposed to water.. Mentos in diet soda like.
Dream not totally busted I can still use the earthblocks inside and the natural color was very beautiful would make a fireplace and accent wall out of the earthblocks.
QEMU Launcher + 32 bit QEMU pet and sfs
http://pc.blogspot.com/2010/12/chapel-l ... felix.html
this is a link to type of Mexican roof I speak. The methods are the same but for smaller scale and far less costly materials I wrote software to model these forms of roofs with puppylinux and know fatdog64
this is a link to type of Mexican roof I speak. The methods are the same but for smaller scale and far less costly materials I wrote software to model these forms of roofs with puppylinux and know fatdog64
-
gcmartin
Launcher simple instructions
Hello @Ted Dog and anyone who find this a useful approach. Tested with LH64 & FD.
Quick Steps: With your LH64 all you really need to do with this
Edit: Insure that the KVM checkbox is checked!
Here to help
Quick Steps: With your LH64 all you really need to do with this
- Install the QEMU Pet of your choice
- Install this Launcher
- Launch
- Give an ISO path, set RAM, Run ...
Edit: Insure that the KVM checkbox is checked!
Here to help
Last edited by gcmartin on Mon 12 May 2014, 22:22, edited 4 times in total.
Ok this is not over yert.
Firstly retried with LHP on the atom.
The output of free lacks the Total: output ...this buggers loading an sfs to tmpfs for my loader and I suspect also for sfs load which also failed.
This is the scenario with an sfs downloaded to say /root and then loaded...it has to be moved to either ram or a device to be inserted..I usually go for ram.
So a time waster there but this time it got truly loaded manually....yay it tries to run now.
I tested the launcher which failed the first time ... although kvm.ko loaded apparently it also requires kvm-amd or kvm-intel to work. Since the atom apparently does not support kvm this fails... I did however get it to run but of course booting Lucid was a slow custard stirring operation which takes about 5 to 10 minutes to boot...lol. I do have a kvm supporting 32 bit netbook and if slax 7 supports kvm I might still get the joy of KVM ...note kqemu flies on the same machines...but i lament.
Point here is I did get some real testing done which brings up some changes needed.
1.... i cannot confirm if the kvm-intel or kvm-amd load automatically when kvm does...someone needs to confirm the behavior as I may not be able to .
It definitely means I need to alter the test for valid kvm.
2....The kill session needs modding to handle the various potential binary in use..easy peasy.
As for sfs loading on lighthouse into ram... well that's its buggy combination...out of my domain
Once 1. is verified I will make a fresh pet..
mike
Firstly retried with LHP on the atom.
The output of free lacks the Total: output ...this buggers loading an sfs to tmpfs for my loader and I suspect also for sfs load which also failed.
This is the scenario with an sfs downloaded to say /root and then loaded...it has to be moved to either ram or a device to be inserted..I usually go for ram.
So a time waster there but this time it got truly loaded manually....yay it tries to run now.
I tested the launcher which failed the first time ... although kvm.ko loaded apparently it also requires kvm-amd or kvm-intel to work. Since the atom apparently does not support kvm this fails... I did however get it to run but of course booting Lucid was a slow custard stirring operation which takes about 5 to 10 minutes to boot...lol. I do have a kvm supporting 32 bit netbook and if slax 7 supports kvm I might still get the joy of KVM ...note kqemu flies on the same machines...but i lament.
Point here is I did get some real testing done which brings up some changes needed.
1.... i cannot confirm if the kvm-intel or kvm-amd load automatically when kvm does...someone needs to confirm the behavior as I may not be able to .
It definitely means I need to alter the test for valid kvm.
2....The kill session needs modding to handle the various potential binary in use..easy peasy.
As for sfs loading on lighthouse into ram... well that's its buggy combination...out of my domain
Once 1. is verified I will make a fresh pet..
mike
-
gcmartin
HI @MikeB
For example: I have LH64 running. I open Menu>Multimedia>IsoMaster to a LH64 ISO. In its top pane, I navigate and select the SFS I want to Add and click Add where it shows up now in the bottom pane. Close-Save creates a new ISO. Booting that ISO, Live, I am presented during boot the option to have any/all SFSs added into my desktop system automatically without any user intervention, at all.
The Atom, Yes, in those, Intel decided not to include virtualization to cut cost of production. They also did not include hyperthreading in many, as well.
Virtualization support once system boots. I have ONLY AMD processors. When I boot FD/LH64, I have found that the kvm modules are loaded..."yeh". So, several weeks ago, I stopped tested for the presence (# lsmod | grep kvm).
Hope this helps
For LH64 use: If you have placed the SFS in the ISO's root ("/", not "/root"), you should have seen it at pristine boot time along with any other SFS that are present.... The output of free lacks the Total: output ...this buggers loading an sfs to tmpfs for my loader and I suspect also for sfs load which also failed.
This is the scenario with an sfs downloaded to say /root and then loaded...it has to be moved to either ram or a device to be inserted..I usually go for ram.
So a time waster there but this time it got truly loaded manually....yay it tries to run now. ...
For example: I have LH64 running. I open Menu>Multimedia>IsoMaster to a LH64 ISO. In its top pane, I navigate and select the SFS I want to Add and click Add where it shows up now in the bottom pane. Close-Save creates a new ISO. Booting that ISO, Live, I am presented during boot the option to have any/all SFSs added into my desktop system automatically without any user intervention, at all.
The Atom, Yes, in those, Intel decided not to include virtualization to cut cost of production. They also did not include hyperthreading in many, as well.
Virtualization support once system boots. I have ONLY AMD processors. When I boot FD/LH64, I have found that the kvm modules are loaded..."yeh". So, several weeks ago, I stopped tested for the presence (# lsmod | grep kvm).
Hope this helps
Last edited by gcmartin on Tue 13 May 2014, 21:00, edited 1 time in total.
kqemu flies
are you going to be able to put this in .. My AMD laptop has the 'support' turned off in bios but exists in hardware ( I checked before buy, but did not expect W8 said to force it off )
How soon till new update.. I am working on getting visualization running and heard VB ignores bios flags if hardware checks linux and QEMU with kvm does not. If kqemu still works that would be nice.
are you going to be able to put this in .. My AMD laptop has the 'support' turned off in bios but exists in hardware ( I checked before buy, but did not expect W8 said to force it off )
How soon till new update.. I am working on getting visualization running and heard VB ignores bios flags if hardware checks linux and QEMU with kvm does not. If kqemu still works that would be nice.
-
gcmartin
Hi @Ted Dog
My lappie is older than yours and cannot imagine why MS would demand it be turned off??? They are BIG on Hyper-V, just as we are on KVM. Find the feature (sound like you already have) and turn it on:, your VM guest will make good use in performance.
If there is something misleading or inaccurate in the Guide, please share to improve for others.
KVM, QEMU and this Puppy Linux utility makes everyone who follows to test and support the Puppy development community who build their distros for community use. Any discrepancies your report would be helpful
Here to help
I have a AMD X2 laptop. The information in the Guide was verified using that laptop. VM guest fly! Just use those instructions; only 3 steps no matter which Approach you select. I recommend the Launcher Approach.Ted Dog wrote:... My AMD laptop has the 'support' turned off in bios but exists in hardware ...
My lappie is older than yours and cannot imagine why MS would demand it be turned off??? They are BIG on Hyper-V, just as we are on KVM. Find the feature (sound like you already have) and turn it on:, your VM guest will make good use in performance.
If there is something misleading or inaccurate in the Guide, please share to improve for others.
KVM, QEMU and this Puppy Linux utility makes everyone who follows to test and support the Puppy development community who build their distros for community use. Any discrepancies your report would be helpful
Here to help
can't be turned on without hacking boot firmware.. I checked and have the haxor but not willing to fudge with it if all it takes is to ignore it on linux side. VBox workaround was just to comfirm hardware and not trust bios flag. W8 had it turn off on all manufacturers who would sale the preinstalled laptops. If would wa t to do this by the machines designed and upsale w8 server crap.
Ok kqemu was a kernel module that could execute some of the emulators functions directly on the real cpu thus providing significant speedup.
Kvm if i understand it is a kernel module that can use virtualization functions added to some cpu. Since they are working differently one is not really a substitute for the other.
It also appears that once kvm was supported then kqemu was dropped loosing acceleration for non kvm machines so the only way to use it is to use a pre kvm build of qemu. Kqemu is just another module built from source for the kernel in question. The source itself was a bit dependent on the version of qemu.
My qemu is version 0.9 and I have acceleration for kernels 2.6.28 thru 2.6.33 on any machine for example which is good for testing and the odd ugly encounters with IE demanding software.
Hope that clarifies things. The gui is only a front end...it up to the system/package as to what works and does not.
and yes without kvm support or a kqemu module then things tend to run like cold custard.
Ok going to see if I can get 32 bit kvm working on this centrino duo to hone the detection.
mike
Kvm if i understand it is a kernel module that can use virtualization functions added to some cpu. Since they are working differently one is not really a substitute for the other.
It also appears that once kvm was supported then kqemu was dropped loosing acceleration for non kvm machines so the only way to use it is to use a pre kvm build of qemu. Kqemu is just another module built from source for the kernel in question. The source itself was a bit dependent on the version of qemu.
My qemu is version 0.9 and I have acceleration for kernels 2.6.28 thru 2.6.33 on any machine for example which is good for testing and the odd ugly encounters with IE demanding software.
Hope that clarifies things. The gui is only a front end...it up to the system/package as to what works and does not.
and yes without kvm support or a kqemu module then things tend to run like cold custard.
Ok going to see if I can get 32 bit kvm working on this centrino duo to hone the detection.
mike
-
gcmartin
@Ted Dog
What did the Guide's command show before you tested?
Can you post results to this:No vmx or svm flag means there is no virtualization present for system to use. This in turn, means that the QEMU-KVM will not work.
Thus, KQEMU is one of the other features from QEMU group that can be employed for improving virtual PC performance when the CPU does NOT provide virtualization. Seem that I remember that some other QEMU features, also, may be used when virtualization hardware is not present.
Here to help
What did the Guide's command show before you tested?
Can you post results to this:
Code: Select all
# egrep --color=always '(vmx|svm)' /proc/cpuinfo
and this
# egrep flags --color=always /proc/cpuinfo
Thus, KQEMU is one of the other features from QEMU group that can be employed for improving virtual PC performance when the CPU does NOT provide virtualization. Seem that I remember that some other QEMU features, also, may be used when virtualization hardware is not present.
Here to help
ok I even readup on that months prior to your writeup. so I read it twice up the cpu does support svm even when firmware misreported the lack of support. That is my real issue. There is a way someone used to pull firmware flip the bit and reflash changed firmware but I do not think that is wise.
People are reporting older versions of QEMU with kqemu work well. Have yet to find 64 version of such with modern kernel.
People are reporting older versions of QEMU with kqemu work well. Have yet to find 64 version of such with modern kernel.
-
gcmartin
Steps to run a virtual PC in a Virtual PC on a Real PUPPY PC
Happy to report running a HOST test that I've just concluded to see its behavior. I am running a VM Guest in a VM Guest with the latter giving great performance.
This was done using Approach #2 in the Guide
Scenario
The benefit to this test is that I can test package installation on a guest and see if that impacts another guest's operation. Or I could remaster a Guest and test the remaster inside the Guest. There are, of course, other possibilities for test, too.
All running rather well
Others may see value and ideas for their own personal needs/usage with the flexibility this provides.
Here to help
This was done using Approach #2 in the Guide
Scenario
- Running LH64-602b with QEMU V2.0 and QEMU Launcher V0.2.2
- On the above HOST, I Launched a VM Guest PC running Slacko64 and a SWAP partition
- Added QEMU V2.0 and QEMU Launcher V0.2.2 PETs to Slacko64
- In the above Guest, I Launched a VM Guest PC running FATDOG
The benefit to this test is that I can test package installation on a guest and see if that impacts another guest's operation. Or I could remaster a Guest and test the remaster inside the Guest. There are, of course, other possibilities for test, too.
All running rather well
Others may see value and ideas for their own personal needs/usage with the flexibility this provides.
Here to help
OK the lenovo needs a bios update to enable its kvm support.. not something I tend to rush into doing.
It does appear then kwm and the associated cpu module is loaded automatically so will simply change it to detect those. KVM did load itself in slax 7 even though bios support was missing so kvm-intel failed.
Would be interesting to see the current state of using kqemu since kvm is limited to certain hardware....friendly bios...system built to include kvm (what is the windows situation...I have qemu and kqemu running on that no problem? After all windows users might be more interested in testing or running linux virtually rather than existing linux users.)
Will update the pet later today.
mike
It does appear then kwm and the associated cpu module is loaded automatically so will simply change it to detect those. KVM did load itself in slax 7 even though bios support was missing so kvm-intel failed.
Would be interesting to see the current state of using kqemu since kvm is limited to certain hardware....friendly bios...system built to include kvm (what is the windows situation...I have qemu and kqemu running on that no problem? After all windows users might be more interested in testing or running linux virtually rather than existing linux users.)
Will update the pet later today.
mike
Ok pet updated to 0.3
only shows kvm if kvm_intel or kvm_amd are loaded and assumes this happens automatically if support is present.
If not acceleration is available the gui offers to make a cup of coffee and a roll for the user while he or she waits for the guest to boot.
fixed the kill session function.
added choice of how many cpu cores to use
Since I get the feeling kqemu may return to the equation I will see about adding it back in in hopefully a non confusing way so end up with a one gui does all result.
But first needs testing with current changes
Mike
only shows kvm if kvm_intel or kvm_amd are loaded and assumes this happens automatically if support is present.
If not acceleration is available the gui offers to make a cup of coffee and a roll for the user while he or she waits for the guest to boot.
fixed the kill session function.
added choice of how many cpu cores to use
Since I get the feeling kqemu may return to the equation I will see about adding it back in in hopefully a non confusing way so end up with a one gui does all result.
But first needs testing with current changes
Mike
-
gcmartin
Hummm,... I have no way of evaluating either the Intel nor the EFI issues reported as I have neither in my arsenal of 64bit laps and desktops. But I am wondering if there is something consistent that could be recommended to users of such. You and @Ted Dog are certainly opening an area of concern where a thread discussion should be opened to address what is going on. This has to be going on for others with this technology as well. As I have read the comments from each of you, I wonder if there is a doorway created for, in this case, Microsoft which exposes the BIOS for OS manipulation when necessary???.
If I had either of these, I would start that discussion, but in the absence ...
Here to help
If I had either of these, I would start that discussion, but in the absence ...
Here to help
Well appears to be something that needs enabling in bios OR a bios update needed in some cases for older hardware.
Cannot comment on UEFI issues though obviously being able to boot other operating systems is not microsoft policy.
I did read of instances where enabling kvm abilities affects other things like sound.
I did try -smp with kqemu but that lost the full acceleration in that case and reverted to having 2 generic pentiums with partial speedup. By the sounds of it kvm gives the full monty.
mike
Cannot comment on UEFI issues though obviously being able to boot other operating systems is not microsoft policy.
I did read of instances where enabling kvm abilities affects other things like sound.
I did try -smp with kqemu but that lost the full acceleration in that case and reverted to having 2 generic pentiums with partial speedup. By the sounds of it kvm gives the full monty.
mike
I have just completed a quick test of version 3 on a Core Duo 2.4 GHz with 4GB RAM running FatDog64 631, kvm_intel, Qemu2.0 pet virtualizing 8GB vHDD, 2 cores, 2048MB memory, L.A.S.S.I.E.2.0 (a Precise 5.7.1 derivative). Everything went well and performance is snappy. Host CPU varies from 20% to 80+%. Inside the VM I tested web surfing, wget, ROX, sfs loading, Desktop Globe app. Didn't test audio/video.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]