7:42 a.m.
On Sun, Sep 15, 2013 at 01:59:29PM +0200, Gianluca Cecchi wrote:
On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote:
and
[root@tekkaman ~]# chgrp kvm /var/lib/libvirt/images/testvm.img
[root@tekkaman ~]# ll /var/lib/libvirt/images/testvm.img
-rw-rw----. 1 vdsm kvm 197120 Sep 15 12:24 /var/lib/libvirt/images/testvm.img
[root@tekkaman ~]# virsh undefine testvm2
Please enter your authentication name: virshuser
Please enter your password:
Domain testvm2 has been undefined
[root@tekkaman ~]# virsh define /tmp/testvm2.xml
Please enter your authentication name: virshuser
Please enter your password:
Domain testvm2 defined from /tmp/testvm2.xml
[root@tekkaman ~]# virsh start testvm2
Please enter your authentication name: virshuser
Please enter your password:
error: Failed to start domain testvm2
error: internal error Process exited while reading console log output:
char device redirected to /dev/pts/2
qemu-kvm: -drive
file=/var/lib/libvirt/images//testvm.img,if=none,id=drive-virtio-disk0,format=qcow2:
could not open disk image /var/lib/libvirt/images//testvm.img:
Permission denied
Gianluca, due to all the twists of this thread, I no longer recall which
libvirt version you are using. Would you remind us?
All signs show that it starts up qemu without setting its auxiliary
group properly (Assuming that your
# groups qemu
qemu : qemu kvm
is just as mine)
I've added libvir-list so the fine folks there could check why qemu
cannot read/write files group-owned by kvm.
Dan.
8:55 a.m.
New subject: [libvirt] [Users] Starting VM Error
On Sun, Sep 15, 2013 at 2:42 PM, Dan Kenigsberg wrote:
On Sun, Sep 15, 2013 at 01:59:29PM +0200, Gianluca Cecchi wrote:
> On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote:
Gianluca, due to all the twists of this thread, I no longer recall
which
libvirt version you are using. Would you remind us?
All signs show that it starts up qemu without setting its auxiliary
group properly (Assuming that your
# groups qemu
qemu : qemu kvm
is just as mine)
I've added libvir-list so the fine folks there could check why qemu
cannot read/write files group-owned by kvm.
Dan.
I'm using what stock f18 repo gives today:
[root@tekkaman ~]# rpm -q libvirt
libvirt-0.10.2.7-1.fc18.x86_64
[root@tekkaman ~]# groups qemu
qemu : qemu kvm
[root@tekkaman ~]# grep libvirt-0 /var/log/yum.log
Jan 07 00:12:13 Installed: libvirt-0.10.2.2-3.fc18.x86_64
Feb 09 17:17:30 Updated: libvirt-0.10.2.3-1.fc18.x86_64
Apr 18 19:44:58 Updated: libvirt-0.10.2.4-1.fc18.x86_64
May 29 20:45:26 Updated: libvirt-0.10.2.5-1.fc18.x86_64
Jun 27 20:05:24 Updated: libvirt-0.10.2.6-1.fc18.x86_64
Aug 18 19:09:52 Updated: libvirt-0.10.2.7-1.fc18.x86_64
I'm not using consistently this all-in-one system for ovirt.
For sure in July it worked ok.
Only today when I wanted to run one of its vms, I saw the error and I
found this reference in the list.
Gianluca
8:41 a.m.
New subject: [libvirt] [Users] Starting VM Error
On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
I'm using what stock f18 repo gives today:
[root@tekkaman ~]# rpm -q libvirt
libvirt-0.10.2.7-1.fc18.x86_64
Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8
to be released.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
9:12 a.m.
New subject: [libvirt] [Users] Starting VM Error
On Mon, Sep 16, 2013 at 3:41 PM, Eric Blake wrote:
On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
> I'm using what stock f18 repo gives today:
> [root@tekkaman ~]# rpm -q libvirt
> libvirt-0.10.2.7-1.fc18.x86_64
Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8
to be released.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
thanks.
Uhm, not so easy. It seems it wants to downgrade to 0.10.2.2-3 (why?)
and not 0.10.2.6 and vdsm complains about that....
Where to eventually find intermediate updates? I only found latest
ones (so the broken ones...) on mirrors?
On my system
[g.cecchi@tekkaman ~]$ sudo yum downgrade
libvirt-daemon-driver-storage libvirt-daemon-driver-lxc
libvirt-daemon-driver-qemu libvirt-daemon-kvm
libvirt-daemon-driver-network libvirt-daemon-driver-uml
libvirt-lock-sanlock libvirt libvirt-python
libvirt-daemon-driver-nwfilter libvirt-daemon-driver-libxl
libvirt-client libvirt-daemon-driver-secret
libvirt-daemon-config-nwfilter libvirt-daemon-driver-nodedev
libvirt-daemon-config-network libvirt-daemon
libvirt-daemon-driver-interface libvirt-daemon-driver-xen
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit,
versionlock
Loading mirror speeds from cached hostfile
* fedora: mirror.switch.ch
* livna: ftp-stud.fht-esslingen.de
* rpmfusion-free: mirror.switch.ch
* rpmfusion-free-updates: mirror.switch.ch
* rpmfusion-nonfree: mirror.switch.ch
* rpmfusion-nonfree-updates: mirror.switch.ch
* updates: mirror.switch.ch
Resolving Dependencies
--> Running transaction check
---> Package libvirt.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-client.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt-client.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt-daemon.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon-config-network.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-config-network.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-interface.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-interface.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-libxl.x86_64 0:0.10.2.7-1.fc18 will
be obsoleted
---> Package libvirt-daemon-driver-lxc.x86_64 0:0.10.2.2-3.fc18 will
be a downgrade
---> Package libvirt-daemon-driver-lxc.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon-driver-network.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-network.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-qemu.x86_64 0:0.10.2.2-3.fc18 will
be a downgrade
---> Package libvirt-daemon-driver-qemu.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon-driver-secret.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-secret.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-storage.x86_64 0:0.10.2.2-3.fc18
will be a downgrade
---> Package libvirt-daemon-driver-storage.x86_64 0:0.10.2.7-1.fc18
will be erased
---> Package libvirt-daemon-driver-uml.x86_64 0:0.10.2.2-3.fc18 will
be a downgrade
---> Package libvirt-daemon-driver-uml.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon-driver-xen.x86_64 0:0.10.2.2-3.fc18 will
be a downgrade
---> Package libvirt-daemon-driver-xen.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-daemon-kvm.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt-daemon-kvm.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-lock-sanlock.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt-lock-sanlock.x86_64 0:0.10.2.7-1.fc18 will be erased
---> Package libvirt-python.x86_64 0:0.10.2.2-3.fc18 will be a downgrade
---> Package libvirt-python.x86_64 0:0.10.2.7-1.fc18 will be erased
--> Finished Dependency Resolution
Error: Package: vdsm-4.10.3-17.fc18.x86_64 (@ovirt-stable)
Requires: libvirt >= 0.10.2.4-1
Removing: libvirt-0.10.2.7-1.fc18.x86_64 (@updates)
libvirt = 0.10.2.7-1.fc18
Downgraded By: libvirt-0.10.2.2-3.fc18.x86_64 (fedora)
libvirt = 0.10.2.2-3.fc18
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
12:50 a.m.
New subject: [libvirt] [Users] Starting VM Error
On Mon, Sep 16, 2013 at 4:12 PM, Gianluca Cecchi wrote:
On Mon, Sep 16, 2013 at 3:41 PM, Eric Blake wrote:
> On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
>> I'm using what stock f18 repo gives today:
>> [root@tekkaman ~]# rpm -q libvirt
>> libvirt-0.10.2.7-1.fc18.x86_64
>
> Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8
> to be released.
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
thanks.
Uhm, not so easy. It seems it wants to downgrade to 0.10.2.2-3 (why?)
and not 0.10.2.6 and vdsm complains about that....
Where to eventually find intermediate updates? I only found latest
ones (so the broken ones...) on mirrors?
Just to notice that what worked for me online, without need of reboot
of my all-in one f18 system was
take notice of packages to downgrade, just for reference:
rpm -qa | grep libvirt|grep 0.10.2.7-1
mkdir libvirt_downgrade
cd libvirt_downgrade
LIST=$(rpm -qa | grep libvirt|grep 0.10.2.7-1 | sed "s/0.10.2.7-1/0.10.2.6-1/")
SITE="http://kojipkgs.fedoraproject.org/packages/libvirt/0.10.2.6/1....
(note that it is indeed a "/" in 0.10.2.6/1 and not a "-")
for pack in $LIST
do
wget ${SITE}${pack}.rpm
done
sudo rpm -Uvh --force *rpm
connect to webadmin and start one of my WinXP VMs --> ok
Gianluca
1:52 a.m.
New subject: [libvirt] [Users] Starting VM Error
On Thu, Sep 19, 2013 at 7:50 AM, Gianluca Cecchi wrote:
Just to notice that what worked for me online, without need of
reboot
of my all-in one f18 system was
take notice of packages to downgrade, just for reference:
rpm -qa | grep libvirt|grep 0.10.2.7-1
mkdir libvirt_downgrade
cd libvirt_downgrade
LIST=$(rpm -qa | grep libvirt|grep 0.10.2.7-1 | sed
"s/0.10.2.7-1/0.10.2.6-1/")
SITE="http://kojipkgs.fedoraproject.org/packages/libvirt/0.10.2.6/1....
(note that it is indeed a "/" in 0.10.2.6/1 and not a "-")
for pack in $LIST
do
wget ${SITE}${pack}.rpm
done
sudo rpm -Uvh --force *rpm
connect to webadmin and start one of my WinXP VMs --> ok
Gianluca
I've put a note on bugzilla too
https://bugzilla.redhat.com/show_bug.cgi?id=1006394
I previously reverted to 0.10.2.6-1 and oVirt worked again.
Now it works with 0.10.2.8-1 in updates-testing repo:
[g.cecchi@tekkaman ~]$ sudo yum --enablerepo=updates-testing update libvirt
Updated:
libvirt.x86_64 0:0.10.2.8-1.fc18
Dependency Updated:
libvirt-client.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-config-network.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-interface.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-libxl.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-lxc.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-network.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-qemu.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-secret.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-storage.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-uml.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-driver-xen.x86_64 0:0.10.2.8-1.fc18
libvirt-daemon-kvm.x86_64 0:0.10.2.8-1.fc18
libvirt-lock-sanlock.x86_64 0:0.10.2.8-1.fc18
libvirt-python.x86_64 0:0.10.2.8-1.fc18
4080
days inactive
4087
days old
5 comments
3 participants
participants (3)
-
Dan Kenigsberg -
Eric Blake -
Gianluca Cecchi