KVM VM does not respond well after loading from snapshot

  • Thread starter Thread starter ilan
  • Start date Start date
I

ilan

Guest
Hi,

I have few machines that run proxmox, I am using a NFS share to place in my base images so I can validate that all my images are pretty much identical.

When bringing an image up from a snapshot (args: -loadvm SNAP_NAME) I sometimes get the image in a semi-hung state, mouse does not follow well my mouse (on Windows images), usually network is down and most executables do not respond.

In some cases, doing an additional snapshot on top of the first one (loading the image without a snapshot and setting a new snapshot, loading from it) rectify the situation, not always, some time starting the image again helps, but it is not consistents.

All my machines have very similar hardware.
In addition, if someone can tell me what pve-qemu-kvm version supports the snapshots feature well - that would be great (plus what packages should be most suitable).

The snapshots feature is critical to my use case, please advise.

Ilan
Here are some samples of my machines pveversions:
###############################################
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3
###############################################
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3
###############################################
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-7-pve: 2.6.24-11
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3
###############################################
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3
 
Can you try with the latest version, (based on 2.6.32)?
 
Hi Tom,
I have updated the server to this:

Code: 
kanga-proxmox:/# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-3-pve
proxmox-ve-2.6.32: 1.6-14
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-8
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-7
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4
I have take a snapshot from my Windows Server 2003 image, but when I tried to load the VM from the snapshot I get "stucked" image [when I open VNC console I see no mouse movement, no time ticking, looks like screenshot and not like snapshot ;) ]
In addition, I have notice that the CPU Utialization is 95% or higher, when usually it is between 10% to 30%.

Any ideas?
 
Last edited by a moderator:
I also tried snapshots from the proxmox 1.6 iso and snapshots got hung
If you can tell me what pve-qemu-kvm version supports the snapshots feature well or give me a matrix of recommended pairs of pve-qemu-kvm and pve-kernel, that would be very helpful
 
dietmar, I am not doing much, you can break what I do to these actions:
  • create a windows xp image
  • open some program on the image (like explorer) and create a snapshot, let us call it my_snap
  • set the .conf file to load that snapshot automatically, i.e. in 101.conf file add: args: -loadvm my_snap and make a change (open a browser or whatever)
  • stop the image (using for example: qm stopall 10 && qm wait 101)
  • start the image (using for example:qm start 101) - it takes about a minute for the image to become alive.
  • repeat the stop and start 'till you see in the built in vnc console that the image mouse is not tracking your mouse well
  • Usually by the time you reach the 5th iteration in that sort of a test you will see the anomaly
Do you have any data regarding any known compatibility issues between different pve-qemu-kvm and pve-kernel ? I did not see any comment on that by anyone.
Can you guide to a forum/link where I can find such data?
Thanks,
Ilan
 
ilan said:
Do you have any data regarding any known compatibility issues between different pve-qemu-kvm and pve-kernel ? I did not see any comment on that by anyone.
Click to expand...

pve-qemu-kvm 0.12.5-1 should work with our 2.6.24 and 2.6.32 kernels.
pve-qemu-kvm-2.6.18 is for the 2.6.18 kernel.
 
I also managed to see this on RHELx64, but since I disabled the GUI by default, it is harder to "see" it
(on RHEL the symptom I stumble upon is that connectivity to the server on some ports is not existent)

Which does make me think of a question:
When a snapshot is taken, does it save all the packets in the network card (when the image comes back, will it try sending/processing old packets)?
 
ilan said:
When a snapshot is taken, does it save all the packets in the network card (when the image comes back, will it try sending/processing old packets)?
Click to expand...

AFAIK yes. But I guess you should ask that on the kvm development list.
 
My server is set up and packages look like this:
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-19
pve-kernel-2.6.32-4-pve: 2.6.32-19
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4

On first attempt, I created one snapshot and the snapshot image came up frozen CPU at 98%
On my second attempt I created a mock snapshot and then the one I want to use (I had 2 snapshots and I load from the latest - since we have seen cases where it helped) and got the same result.

Reverting to :
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-19
pve-kernel-2.6.32-4-pve: 2.6.32-19
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-4

Works BUT image acts funny once in a while (on my thierd stop-start mouse was not tracking my mouse)
Please advise what is incompatible in my packages and how to correct it.
 
Last edited by a moderator:
You must log in or register to reply here.
Top Bottom