From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] Kvm: Qemu: save nvram
Date: Tue, 02 Dec 2008 13:01:20 +0000 [thread overview]
Message-ID: <493531A0.2040501@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F14021760D4@pdsmsx502.ccr.corp.intel.com>
Daniel P. Berrange wrote:
> On Tue, Dec 02, 2008 at 10:25:49AM +0800, Zhang, Yang wrote:
>
>> This patch to save the nvram. It save the nvram by specify the arg of
>> -name.And the saved file named by the arg. If do not specify the arg,
>> it will not save the nvram
>>
>
> I think we might be better off having an explicit command line arg for nvram
> path rather than hardcoding the directory, because there may well be times
> where you want to have nvram saved, but don't want to specify -name, and
> vica-verca.
>
> -nvram foo.data
>
> could prepend a default directory of $localstatedir/lib/qemu/nvram, where
> $localstatedir is set from 'configure' script, or
>
> -nvram /some/path/foo.data
>
> would use the explicit path given.
>
I prefer current directory if relative path is given. Since we
encourage running qemu as an unprivileged user, and we don't want a
world-writable directory, each user will have to provide a private
storage location.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Zhang, Yang" <yang.zhang@intel.com>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"avi@readhat.com" <avi@readhat.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] Kvm: Qemu: save nvram
Date: Tue, 02 Dec 2008 15:01:20 +0200 [thread overview]
Message-ID: <493531A0.2040501@redhat.com> (raw)
In-Reply-To: <20081202103145.GC25599@redhat.com>
Daniel P. Berrange wrote:
> On Tue, Dec 02, 2008 at 10:25:49AM +0800, Zhang, Yang wrote:
>
>> This patch to save the nvram. It save the nvram by specify the arg of
>> -name.And the saved file named by the arg. If do not specify the arg,
>> it will not save the nvram
>>
>
> I think we might be better off having an explicit command line arg for nvram
> path rather than hardcoding the directory, because there may well be times
> where you want to have nvram saved, but don't want to specify -name, and
> vica-verca.
>
> -nvram foo.data
>
> could prepend a default directory of $localstatedir/lib/qemu/nvram, where
> $localstatedir is set from 'configure' script, or
>
> -nvram /some/path/foo.data
>
> would use the explicit path given.
>
I prefer current directory if relative path is given. Since we
encourage running qemu as an unprivileged user, and we don't want a
world-writable directory, each user will have to provide a private
storage location.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-02 13:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 2:25 [PATCH] Kvm: Qemu: save nvram Zhang, Yang
2008-12-02 2:25 ` Zhang, Yang
2008-12-02 5:27 ` Zhang, Yang
2008-12-02 5:27 ` Zhang, Yang
2008-12-02 10:31 ` Daniel P. Berrange
2008-12-02 10:31 ` Daniel P. Berrange
2008-12-02 13:01 ` Avi Kivity [this message]
2008-12-02 13:01 ` Avi Kivity
2008-12-02 13:10 ` Daniel P. Berrange
2008-12-02 13:10 ` Daniel P. Berrange
2008-12-03 6:02 ` Zhang, Xiantao
2008-12-03 6:02 ` Zhang, Xiantao
2008-12-03 6:12 ` Zhang, Yang
2008-12-03 6:12 ` Zhang, Yang
2008-12-16 9:21 ` Zhang, Yang
2008-12-16 9:21 ` Zhang, Yang
2008-12-17 18:39 ` Charles Duffy
2008-12-18 5:30 ` Zhang, Xiantao
2008-12-18 18:00 ` Charles Duffy
2008-12-19 1:56 ` Zhang, Yang
2008-12-24 5:27 ` Zhang, Yang
2008-12-24 5:27 ` Zhang, Yang
2008-12-24 5:34 ` Zhang, Yang
2008-12-24 5:34 ` Zhang, Yang
2009-01-15 6:57 ` FW: " Zhang, Yang
2009-01-15 6:57 ` Zhang, Yang
2009-01-15 9:57 ` Avi Kivity
2009-01-15 9:57 ` Avi Kivity
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=493531A0.2040501@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.