From: lijuan.tu@intel.com
To: dts@dpdk.org,ohilyard@iol.unh.edu
Cc: Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [PATCH] vm_images: Update to handle additional host configurations
Date: 23 Mar 2022 01:13:44 -0700 [thread overview]
Message-ID: <746b4b$gmq07h@orsmga008-auth.jf.intel.com> (raw)
In-Reply-To: <20220302170637.24095-1-ohilyard@iol.unh.edu>
On Wed, 2 Mar 2022 12:06:37 -0500, ohilyard@iol.unh.edu wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> While doing testing on UNH's ARM system, there were a few edge cases. Namely
> that docker must be run in privileged mode. This is not due to ARM but
> SeLinux/AppArmor getting the way of accessing some of kvm's resources
> while in an unprivileged namespace. Issues with passing through the
> hardware clock resulted in both the addition of chronyd and trusting the
> ssl certificates on python's pip repositories while installing meson due
> to issues with SSL and the VM time starting at Jan 1, 1970.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
Applied, thanks
prev parent reply other threads:[~2022-03-23 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 17:06 ohilyard
2022-03-23 8:13 ` 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='746b4b$gmq07h@orsmga008-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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).