qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Li, Zhijian" <lizhijian@cn.fujitsu.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
	"quintela@redhat.com" <quintela@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PULL 0/7] Migration.next patches
Date: Fri, 10 Sep 2021 21:10:32 +0800	[thread overview]
Message-ID: <67d6411e-341b-b3d6-c395-1e69b0a6a3d0@cn.fujitsu.com> (raw)
In-Reply-To: <b5b57f82-4dba-53ca-ba18-51f0f6386c44@redhat.com>


on 2021/9/10 20:55, Philippe Mathieu-Daudé wrote:
>> BTW: Does QEMU provide any mean to set http(s)_proxy to building vm ? Currently, i have to
>> hack the code like:
>>
>> -        self.ssh_root_check("pkg install -y %s\n" % " ".join(self.pkgs))
>> +        self.ssh_root_check("setenv HTTP_PROXY http://myproxy; setenv HTTPS_PROXY http://myproxy; pkg install -y %s\n" % " ".join(self.pkgs))
> This is supported since commit b08ba163aaa ("tests/vm: send proxy
> environment variables over ssh"). Maybe we only pass lower case
> variables and should consider upper case too?

Great, I'm glad to know this. Thank you.
Lower case variables also work well on FreeBSD, so it's sufficient i think.


Thanks
Zhijian





  reply	other threads:[~2021-09-10 13:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 10:33 [PULL 0/7] Migration.next patches Juan Quintela
2021-09-09 10:33 ` [PULL 1/7] multifd: Implement yank for multifd send side Juan Quintela
2021-09-09 10:33 ` [PULL 2/7] multifd: Unconditionally unregister yank function Juan Quintela
2021-09-09 10:33 ` [PULL 3/7] migration/rdma: Try to register On-Demand Paging memory region Juan Quintela
2021-09-09 10:33 ` [PULL 4/7] migration/rdma: advise prefetch write for ODP region Juan Quintela
2021-09-09 10:33 ` [PULL 5/7] migration/ram: Don't passs RAMState to migration_clear_memory_region_dirty_bitmap_*() Juan Quintela
2021-09-09 10:33 ` [PULL 6/7] migration: allow multifd for socket protocol only Juan Quintela
2021-09-09 10:33 ` [PULL 7/7] migration: allow enabling mutilfd for specific " Juan Quintela
2021-09-09 13:42 ` [PULL 0/7] Migration.next patches Peter Maydell
2021-09-09 14:48   ` Li, Zhijian
2021-09-09 14:59     ` Peter Maydell
2021-09-09 15:23     ` Juan Quintela
2021-09-09 15:36       ` Peter Maydell
2021-09-09 16:10     ` Juan Quintela
2021-09-10  5:20       ` lizhijian
2021-09-10  5:27         ` lizhijian
2021-09-10  7:00           ` Juan Quintela
2021-09-10  8:52             ` lizhijian
2021-09-10 12:55           ` Philippe Mathieu-Daudé
2021-09-10 13:10             ` Li, Zhijian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-19  9:29 Juan Quintela
2021-10-19 16:55 ` Richard Henderson

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=67d6411e-341b-b3d6-c395-1e69b0a6a3d0@cn.fujitsu.com \
    --to=lizhijian@cn.fujitsu.com \
    --cc=alex.bennee@linaro.org \
    --cc=dgilbert@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lizhijian@fujitsu.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).