Qemu/kvm as a tool for handling 7.4.2 install from ISO

[utu]

I have 3.5 Gb ram to work-with.
Is this enough to successfully treat DVD-size isos using this process?
TIA.

I appreciate the posting of this helpful idea, however...

Many forum users won't be able to use this idea because their cpu(s) aren't capable
of doing the necessary virtualization. The Intel site below may help some figure this out.

The process I went through was as follows:
1. egrep '(vmx|svm)' --color=always /proc/cpuinfo gives a null result; not encouraging.
2. virtualization (may?) require 64-bit cpu(s) & OS; we have that, anyway.
3. my bios material gives NO clue whether my cpu(s) are capable of virtualization or not; also not encouraging.
4. Intel spec sheets let you know whether your cpu(s) are capable of vt-x virtualization; mine aren't. See, for example:
http://ark.intel.com/products/37253/...=t4300+pentium

One needs to substitute their own cpu designation, of course.
My rig is dual T4300s.

[Capricorny]

I appreciate the posting of this helpful idea, however...

Many forum users won't be able to use this idea because their cpu(s) aren't capable
of doing the necessary virtualization. The Intel site below may help some figure this out.

The process I went through was as follows:
1. egrep '(vmx|svm)' --color=always /proc/cpuinfo gives a null result; not encouraging.
2. virtualization (may?) require 64-bit cpu(s) & OS; we have that, anyway.
3. my bios material gives NO clue whether my cpu(s) are capable of virtualization or not; also not encouraging.
4. Intel spec sheets let you know whether your cpu(s) are capable of vt-x virtualization; mine aren't. See, for example:
http://ark.intel.com/products/37253/...=t4300+pentium

One needs to substitute their own cpu designation, of course.
My rig is dual T4300s.

For the simple kind of use I mentioned, you don't really need virtualization. If kvm doesn't work, it's just to omit the -machine parameter. It will run slowly, but the job will be done - and I'm not sure about the resulting amount of lag in I/O-operations, which is the time-consuming part in this case.
The modprobe (with AMD CPUs, use kvm-amd instead of kvm-intel) should fail if kvm doesn't work, and the simple command

lsmod | grep kvm

will tell if kvm is loaded.
(I also wonder how many use virtualization-resistent CPUs these days.)
Seems that 3 GB RAM will work - but the -m parameter may have to be be reduced from 1024.