From: jiangyd <1700380@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1700380] [NEW] commit snapshot image got Permission denied error
Date: Sun, 25 Jun 2017 16:09:27 -0000 [thread overview]
Message-ID: <149840696740.3624.10086547691536237734.malonedeb@gac.canonical.com> (raw)
Public bug reported:
qemu 2.9.0, adm64, start image with -snapshot param, make some changes
in the image, then:
$telnet localhost 7000
(qemu) commit virtio0
'commit' error for 'virtio0': Permission denied
Nerver met this problem before, commit is ok. I recently compiled
v2.9.0, so is there some new param in qemu-qemu-system-x86_64 to avoid
commit Permission denied?
Regards.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1700380
Title:
commit snapshot image got Permission denied error
Status in QEMU:
New
Bug description:
qemu 2.9.0, adm64, start image with -snapshot param, make some changes
in the image, then:
$telnet localhost 7000
(qemu) commit virtio0
'commit' error for 'virtio0': Permission denied
Nerver met this problem before, commit is ok. I recently compiled
v2.9.0, so is there some new param in qemu-qemu-system-x86_64 to avoid
commit Permission denied?
Regards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1700380/+subscriptions
next reply other threads:[~2017-06-25 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 16:09 jiangyd [this message]
2017-06-26 2:32 ` [Qemu-devel] [Bug 1700380] Re: commit snapshot image got Permission denied error jiangyd
2017-06-26 2:54 ` jiangyd
2017-06-29 9:04 ` Thomas Huth
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=149840696740.3624.10086547691536237734.malonedeb@gac.canonical.com \
--to=1700380@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.