To clarify: this only fixes one of numerous "issues" that could cause this behaviour, and is addressed in XenSource's bugzilla (http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=950). A more appropriate solution may be to rehash the xen-scripts to be more ubuntu specific (at the very least give more useful error output). I will look into putting together a batch of pre-run tests to optionally add to the xen-scripts and attach to this ticket.
-- xen guest domains won't start Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified https://bugs.launchpad.net/bugs/132117 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
