Comment 42 for bug 218126

rehi,

the "domain already present"-thing was a configuration fault of mine... I had a on_crash=reboot in the configuration of that domain.
so the server tried to start it repeatedly...

@russel:
I already tried a 32bit-hardy-system with gutsy-xen-kernel as domU with no luck.
the bootprocess stucks at "setting system clock". the mentioned workaround for that isn't working for me either

ps: why isn't a domain that shows up as "paused" in 'xm list' not visible in 'xm top'?