This has been fixed for feisty.
** Changed in: xen-3.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
xend has open port
https://launchpad.net/bugs/71789
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fixed in feisty. Dont know if this will be fixed in edgy.
** Changed in: xen-3.0 (Ubuntu)
Status: Confirmed => Fix Committed
--
xend has open port
https://launchpad.net/bugs/71789
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Okay, thanks. I've flipped it back to "confirmed". (You can change a
bug's status by clicking on the "Affects: xen-3.0 (Ubuntu)" link and
then changing the Status.)
** Changed in: xen-3.0 (Ubuntu)
Status: Rejected => Confirmed
--
xend has open port
https://launchpad.net/bugs/71789
--
Who is expecting this?
I personally don't expect that my xen Domains are able to be managed from
somewhere else in the internet by connecting to the management port.
For clarification:
The command line tools from xen (xm) use TCP ICP mechanism (its XML and SOAP
like)
to issue the commands to xe
Hi! Thank you for the report. As I understand it, this is the expected
behavior of the xen package. If not, please feel free to reopen this
report.
Thanks!
** Changed in: xen-3.0 (Ubuntu)
Status: Unconfirmed => Rejected
--
xend has open port
https://launchpad.net/bugs/71789
--
ubunt
