Hello,
I need to optimize a Linux program running under qemu-system-i386. qemu is
compiled with KVM support. File /proc/cpuinfo in the guest shows that SSE2
is supported.
If SSE2 is backed with host hardware, using SSE2 may improve my program's
performance significantly. The host is x86_64 Linux.
On 7/30/2014 9:14 AM, 邓尧 wrote:
Hello,
I need to optimize a Linux program running under qemu-system-i386. qemu
is compiled with KVM support. File /proc/cpuinfo in the guest shows that
SSE2 is supported.
If SSE2 is backed with host hardware, using SSE2 may improve my
program's performance signifi
Hi
I am trying to increase the speed at which a guest runs in Qemu, so that I
can run a regression test on software within the guest OS in a shorter
amount of time. Hopefully this would allow a test that would take 6 hours
normally take less when run inside qemu. Is this possible using qemu or
oth
> From: "graff zeltner"
> Date: Wed, 30 Jul 2014 08:56:59 +0200
>
> I was pleasantly surprised to find a plethora of options in the
> latest qemu version 2.0.95. I have spent a couple of hours reading
> the documentation, and unfortunately was not able to run the program
> to see if everything wo
> From: chester tinemas
>
> I am trying to increase the speed at which a guest runs in Qemu, so that I
> can run a regression test on software within the guest OS in a shorter
> amount of time. Hopefully this would allow a test that would take 6 hours
> normally take less when run inside qemu. Is
Hi,
I've built version 2.0.95 with the following sequence of steps:
'git clone git://git.qemu-project.org/qemu.git'
'./configure' halted on missing libfdt, so used
'git submodule update --init dtc' to fix missing dependency
'./configure --prefix=/home/graf/test/qemu --target-list="i386-linux-user
On 07/30/2014 12:21 PM, graff zeltner wrote:
Hi,
I've built version 2.0.95 with the following sequence of steps:
'git clone git://git.qemu-project.org/qemu.git'
'./configure' halted on missing libfdt, so used
'git submodule update --init dtc' to fix missing dependency
'./configure --prefix=/home
If your main objective is performance, I don't think that there is
any question you should be considering LXC to eliminate overhead.
The reason why LXC is the ultimate in performance is because the
Guests run in a bare metal environment, resources are not virtualized
but simply isolated from other
Hi,
Running the command 'which qemu-i386' and 'which qemu-system-x86_64' produces two different versions on my system. I am running Linux kernel 3.14. qemu-i386 resides in /usr/bin and is version 1.70 Debian, and qemu-system-x86_64 in /usr/local/bin is version 1.7.50 which I built from sources abo
On 07/30/2014 04:54 PM, graff zeltner wrote:
Running the command 'which qemu-i386' and 'which qemu-system-x86_64'
produces two different versions on my system. I am running Linux
kernel 3.14. qemu-i386 resides in /usr/bin and is version 1.70 Debian,
and qemu-system-x86_64 in /usr/local/bin is v
Hi,
I've been using Linux 3.0.21-tinycore with qemu 1.7.0 and 1.7.50 and it was very slow, like it was stuck in the mud. I have now successfully built the latest 2.0.95 version and running with -kvm-enable option. I cannot tell the difference between the live system and the emulated one.
g
IMO, you should refactor your test. If regression test needs as long as 6
hours to complete, the test itself is a problem.
A simple and intuitive approach is to split the test cases into multiple
groups, and run the groups in parallel on different servers/VMs
On Thu, Jul 31, 2014 at 6:09 AM, Ton
12 matches
Mail list logo
