Interesting, I didn't know about the need of that stdio_handler.
But still the issue is solved then - great.
I'll set the status to invalid then to reflect that (we have no closed).
Thanks Stefan!
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: cloud-archive
Hi,
I found the problem with my setup:
I tried to use case B.
But at /etc/libvirtd/qemu.conf I had an entry 'stdio_handler = "file"'. This
was needed to run my setup with libvirt 1.3 and case A.
Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Bug
You log contains:
qemu-system-x86_64: -chardev
pty,id=charserial0,logfile=/var/lib/nova/instances/2691027e-9d67-4f78-841f-01e6c809e8fc/console.log,logappend=off
Which is the older style where qemu itself opens the file instead of the
more modern example I posted above where it is pre-opened and
For the libvirt 1.3.1 setup i have installed:
libvirt-bin 1.3.1-1ubuntu10.21
libvirt0:amd641.3.1-1ubuntu10.21
python-libvirt1.3.1-1ubuntu1.1
To your previous commend:
The qemu arguments for console log and the instance xml looks good.
I can't provide the instance with openstack an
I can't get libvirt 1.3.1 to accept the format of the xml that you posted
(serial/console).
So please when you add the other data add some info (dpkg -l) about used
packages in your case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Thanks for your reply.
Actually I use libvirt 1.3. There an entry for the instance console.log is
createt at apparmor.d.
/etc/apparmor.d/libvirt/libvirt-4612b952-1df7-4f30-a6af-8af2616b41a4.files:
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
"/var/log/libvirt/**/instance-000
Ok thanks for the data.
That looks like the "normal" openstack double console entry to have an
attachable console that logs to a file at the same time.
I made a new dir:
$ mkdir -p /var/lib/nova/instances/testlp1762769
And added the following to a libvirt 3.6 guest
Hi,
thanks for your answer. Here the files (id of instance has changed
because of reproduction).
/etc/apparmor.d/libvirt/libvirt-88917d0e-c873-4a73-9ec1-a458d64a1df9 :
#
# This profile is for the domain whose UUID matches this file.
#
#include
profile libvirt-88917d0e-c873-4a73-9ec1-a458d64a1
Hi,
can you share your guest XML (via virsh dumpxml ) and your apparmor
file (cat
/etc/apparmor.d/libvirt/libvirt-f146b809-e393-48c9-b325-5c2ae6c20e39.files or
whatever file is appropriate then).
The id in the name is the UUID from "virsh dominfo "
With those two I can try to recreate and see w
