KVM : VM freezes after online migration

P

PEB

New Member
May 17, 2013
11
1
3
Hello,

I saw many threads about this problem, but I'm actually unable to solve my own, so I make a new thread.

I'd like to know if this link could explain that I meet some migration problems from a host under CPU 1, 2 or 4 to one with the CPU 3 in the list : http://ark.intel.com/compare/75790,37103,33083,52275 . (the big difference is VT-d and VT-x extended features, which are not available on Xeon E5450)
Thanks a lot.

--
PEB
 
Last edited:
Hi Marco,

All VM can be started successfully on each node.

The thing is, the host "fy" (with Xeon E5450) cannot receive any vm from another host if this vm was not started by itself. If a vm started by node "kdell" arrives, fy receives it, and after, the vm freezes and the kvm process uses 100% of a CPU. I have to migrate back to kdell in order to recover the vm.

At the opposite, if I run a vm with fy, and migrate it, all goes fine. I can also migrate it back to fy without any problem.

So, I thought it could be because of VT-d and VT-x extended features, which are not on fy's core, and are on others hosts.
 
Reply to myself : I checked with some tools, and it seems that the missing VT-x extended is responsible of these problems.

I suggest to document it.
 
I am more reluctant to think that the problem is missing EPT with VT-x[FONT=tahoma, helvetica, sans-serif].[/FONT] Missing VT-d will only cause problems for pass-thrue devices which does not constitute a problem since VM's with pass-thrue devices will not be migrateable anyway.
 
Hi mir,

Yeah, that was my point in my last post. :)

Thanks for your accuracy !
 
You must log in or register to reply here.
Top Bottom