On Mon, Feb 21, 2011 at 12:50:26PM -0500, William L. Thomson Jr. wrote:
> I have been running Xen for a while, but only recently started
> attempting live migration. Which thus far has not worked for a variety
> of reasons.
> I am curious to know if anyone has built a domU kernel from source,
> using non-distro specific sources, that is capable of live migration. I
> have tried 2.6.36 and 2.3.37 sources without success. If anyone has
> compiled a kernel from either of those sources and it is capable of live
> migration, I would really like to see the config file. I also would not
> mind seeing the config file for the dom0 as well. Might be missing some
> stuff there.
Did you try exactly 18.104.22.168 and 22.214.171.124 ?
Later updates to those have many bugfixes.
> I also tried xen sources 2.6.34 for the domU kernel, but for some reason
> the nfs root would only come up ro and I could not get it to be rw.
> Hopefully the domU kernel does not have to be built using xen sources,
> for domU live migration. Probably could have live migrated that, but
> with the ro vs rw issue, system wasn't really usable in a practical
> sense even if it could live migrate.
I'd recommend you to try 126.96.36.199 aswell.
> Now some what unrelated I have a major problem with 2.6.37, where there
> are issues with PMU. Which prevents networking from working, and the
> system from mounting nfs root. This is not related to live migration,
> just preventing me from trying newer sources that might be capable of
> live migration. Likely a upstream issue not xen related, not sure.
> On 2.6.36 I get the following for PMU
> AMD PMU driver.
> ... version: 0
> ... bit width: 48
> ... generic registers: 4
> ... value mask: 0000ffffffffffff
> ... max period: 00007fffffffffff
> ... fixed-purpose events: 0
> ... event mask: 000000000000000f
> I use the same config from 2.6.36, but in 2.6.37 and now get
> Broken PMU hardware detected, software events only.
> Open to any feedback, comments, suggestions etc, thanks!
What kernel cmdline options are you using?
You should have "console=hvc0 earlyprintk=xen" at least.
Xen-users mailing list