Problem migrating VM from 2.6.18 to 2.6.32 node

[stef1777]

Hello!


I have strange problem discovered yesterday.


I'm using a promox 1.8 system with 2.6.32 kernel nodes and one node using kernel 2.6.18.


I have many openvz VMs using Debian Lenny or Squeeze running on theses nodes.


When I migrate the VMs running on the 2.6.18 node to another 2.6.32 node, the VMs start to have problems.


I got this kind of message with dmeg on the VM:


ioctl32(mount:8382): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfd730d8) on /


and syslog don't show all common message and have new strange message. Some binaries crash after a while.


As well other VMs built and used on 2.6.32 node work fine.


If I use vzrestore to migrate to the 2.6.32 node, I got the same problem. Don't seems to be a problem of migrate feature.


Any idea?

 

[tom]

check your logs and do more tests. can you define a re-producible testcase?

 

[stef1777]

Hello Tom!

I mounted a copy of one of the VM on a 2.6.32 node.

Logs seems fine. I checked kern.log, init.log, syslog.

These Debian Lenny 32bits VMs where built on 2.6.18 when kernel 2.6.32 was not working with NFS mount.

For the moment, I only found that dmesg send this message:

ioctl32(mount:5061): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfc557e8) on /
ioctl32(mount:5061): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfc557f0) on /
ioctl32(mount:5061): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfc557cc) on /
ioctl32(mount:5061): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfc557e8) on /
ioctl32(mount:5061): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfc557f0) on /
ioctl32(mount:5061): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfc557cc) on /

On the 2.6.32 node, dmesg send nothing as usual.

Memory used by the same VM on the 2.6.32 is 719M and 1.2G on the 2.6.18 node. All process seems launched and working.

This VM only run Flash Media Server 3 from Adobe with a NFS mount to access a NAS. FMS3 crash randonly.

May be appart the problem with dmesg, this version of FMS3 have a problem with kernel 2.6.32.

I'll try to investigate more later this week.