I did found several suggestions here:
http://forum.proxmox.com/threads/19309-Windows-KVM-frequent-restarts
Then i'll try when i will be front of the servers ....
----- Original Message -----
From: Daniel Hunsaker
To: Cesar Peschiera ; Lindsay Mathieson ; pve-devel@pve.proxmox.com
Sent: Sunday, November 30, 2014 4:47 AM
Subject: Re: [pve-devel] Error in PVE with win2008r2 and 256GB RAM
Sounds like a boot time RAM test... Though whether by the OS or the BIOS is
hard to say. I tend not to let Windows have near that much RAM to play with.
On Sat, Nov 29, 2014, 22:36 Cesar Peschiera <br...@click.com.py> wrote:
Into the VM (Win Server 2008R2), the only process that is consuming lots
of CPU is:
Image Name: System
User Name: System
CPU: 99%
memory (Private workspace): 52 KB
Description: NT Kernel & System
All other processes are consuming 0% of CPU
----- Original Message -----
From: Daniel Hunsaker
To: Cesar Peschiera ; Lindsay Mathieson ; pve-devel@pve.proxmox.com
Sent: Sunday, November 30, 2014 1:30 AM
Subject: Re: [pve-devel] Error in PVE with win2008r2 and 256GB RAM
Any OS is composed of various processes. You'll still have one process
or another (or perhaps a small handful) responsible for the usage unless the
boot process has not yet reached the OS. In the case where the OS is not yet
running, the virtualized hardware is to blame, most likely the BIOS. Either
way, the resolution requires knowledge of the cause, and that requires data
about what is running inside the VM at the time.
On Sat, Nov 29, 2014, 21:06 Cesar Peschiera <br...@click.com.py> wrote:
Hi Daniel
Many thanks for answer me.
The VM is newly installed, has no other program installed. But soon will
should have MS-SQL server 2008 Standard installed.
What can i do to fix my problem?
----- Original Message -----
From: Daniel Hunsaker
To: Cesar Peschiera ; Lindsay Mathieson ; pve-devel@pve.proxmox.com
Sent: Sunday, November 30, 2014 12:56 AM
Subject: Re: [pve-devel] Error in PVE with win2008r2 and 256GB RAM
What about inside the VM? It's expected that the VM itself will consume
all
CPU since that's the reported issue, and `/usr/bin/kvm` is the process
the
host runs the VM in.
On Sat, Nov 29, 2014, 19:53 Cesar Peschiera <br...@click.com.py> wrote:
Hi Lindsay
Many thanks for answer me.... :-)
>What processes in the VM are hogging the CPU?
htop is showing me that the process that consume all processor
available is:
/usr/bin/kvm/ -id 109 -chardev socket, id=qmp,
path=/var/run/qemu-server/109.qmp, server,nowait.... etc (a line very
long)
But in my case, each line of "/usr/bin/kvm/ -id 109 ..." to 100% of
consume
of processor is repetitive for each core that i configured previously
before
of startup the VM.
>Is the VM memory fixed or ballon allocated?
Fixed, the VM has the ballon driver installed, but PVE don't have this
option enabled, and PVE have only a VM installed and nothing more.
----- Original Message -----
From: "Lindsay Mathieson" <lindsay.mathie...@gmail.com>
To: <pve-devel@pve.proxmox.com>
Sent: Saturday, November 29, 2014 11:12 PM
Subject: Re: [pve-devel] Error in PVE with win2008r2 and 256GB RAM
> _______________________________________________
> pve-devel mailing list
> pve-devel@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
