From: yue-kvm <kvmluck@163.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] 2 errors of vnet and snapshot.
Date: Sat, 25 May 2013 21:15:55 +0800 (CST) [thread overview]
Message-ID: <383ca2b2.8a2a.13edbd4c890.Coremail.kvmluck@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
hi,all
i encounterd 2 errors . qemu 1.5(source code build), libvirt libvirt-0.10.2-18.el6_4.2.x86_64.
1. in guest, i can ping out, but get no answers. even throught i ping HOST ip.
May 25 20:50:59 ovirtdev NetworkManager[2370]: <warn> /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
2. permissive selinux. and give all permission to everyone .
root@ovirtdev images]# virsh snapshot-create-as linux snapshot1 "snapshot1" --disk-only --atomic
error: internal error unable to execute QEMU command 'transaction': /var/lib/libvirt/images/test.snapshot1: error while creating qcow2: Permission denied
[-- Attachment #2: Type: text/html, Size: 942 bytes --]
next reply other threads:[~2013-05-25 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 13:15 yue-kvm [this message]
2013-05-25 15:54 ` [Qemu-devel] 2 errors of vnet and snapshot Eric Blake
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=383ca2b2.8a2a.13edbd4c890.Coremail.kvmluck@163.com \
--to=kvmluck@163.com \
--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 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).