>> I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1),
>> and direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the
>> other host via iperf tool, top tool result on VM shown that the %si is too
>> high, approximately 95% ~ 100%, but from the view of host, the
I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1),
and direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the
other host via iperf tool, top tool result on VM shown that the %si is too
high, approximately 95% ~ 100%, but from the view of host, the VM's
> I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1), and
> direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the other
> host via iperf tool, top tool result on VM shown that the %si is too high,
> approximately 95% ~ 100%, but from the view of host, the VM's
I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1), and
direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the other
host via iperf tool, top tool result on VM shown that the %si is too high,
approximately 95% ~ 100%, but from the view of host, the VM's
I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1), and
direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the other
host via iperf tool, top tool result on VM shown that the %si is too high,
approximately 95% ~ 100%, but from the view of host, the VM's total
I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1), and
direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the other
host via iperf tool, top tool result on VM shown that the %si is too high,
approximately 95% ~ 100%, but from the view of host, the VM's total
>> >> >> On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
>> >> >>> I start 10 VMs(windows xp), then running geekbench tool on
>> >> >>> them, about 2 days, one of them was reset, I found the reset
>&
On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
I start 10 VMs(windows xp), then running geekbench tool on
them, about 2 days, one of them was reset, I found the reset
operation is done by int kvm_cpu_exec(CPUArchState *env) {
...
switch (run
>> >> On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
>> >>> I start 10 VMs(windows xp), then running geekbench tool on them,
>> >>> about 2 days, one of them was reset, I found the reset operation
>> &
On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
I start 10 VMs(windows xp), then running geekbench tool on them,
about 2 days, one of them was reset, I found the reset operation
is done by int kvm_cpu_exec(CPUArchState *env) {
...
switch (run-exit_reason
>> On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
>>> I start 10 VMs(windows xp), then running geekbench tool on them,
>>> about 2 days, one of them was reset, I found the reset operation is
>>> done by int kvm_cpu_exec(CPUArchState *env) {
> > On Mon, Apr 08, 2013 at 12:27:06PM +, Zhanghaoyu (A) wrote:
> >> On Sun, Apr 07, 2013 at 04:58:07AM +0000, Zhanghaoyu (A) wrote:
> >>>>>> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
> >>>>>> qemu progra
On Mon, Apr 08, 2013 at 12:27:06PM +, Zhanghaoyu (A) wrote:
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
qemu program crashed during starting period, received signal SIGABRT.
Trying about 20
On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
I start 10 VMs(windows xp), then running geekbench tool on them,
about 2 days, one of them was reset, I found the reset operation is
done by int kvm_cpu_exec(CPUArchState *env) {
...
switch (run-exit_reason
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
> >>> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
> >>> qemu program crashed during starting period, received signal SIGABRT.
> >>> Trying about 20 times, this cr
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
qemu program crashed during starting period, received signal SIGABRT.
Trying about 20 times, this crash may be reproduced.
I guess the cause memory
16 matches
Mail list logo
