From: lijuan.tu@intel.com
To: dts@dpdk.org,Daxue Gao <daxuex.gao@intel.com>
Cc: Daxue Gao <daxuex.gao@intel.com>
Subject: [PATCH v2] framework: fix container vm port conflict
Date: 24 May 2023 19:32:53 -0700 [thread overview]
Message-ID: <da3a9c$uqrc3a@fmsmga005-auth.fm.intel.com> (raw)
In-Reply-To: <20230522083117.8835-1-daxuex.gao@intel.com>
On Mon, 22 May 2023 16:31:17 +0800, Daxue Gao <daxuex.gao@intel.com> wrote:
> Fix the problem that the container vm port conflict causes the vm to fail to start.
> Capture the port conflict by exception, and assign a new port number to start the vm.
> The port conflict includes tcp forward/vnc/telnet/migrate port.
>
> Signed-off-by: Daxue Gao <daxuex.gao@intel.com>
Reviewed-by: Lijuan Tu <lijuan.tu@intel.com>
Applied, thanks
prev parent reply other threads:[~2023-05-25 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:31 Daxue Gao
2023-05-25 2:32 ` lijuan.tu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='da3a9c$uqrc3a@fmsmga005-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=daxuex.gao@intel.com \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).