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'? -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
