Launchpad has imported 25 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=757382.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Oneiric)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Oneiric)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
When will that bugfix be available in Oneiric?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding in oneiric
To manage notifications about this bug go to:
** Summary changed:
- libvirtd stops responding
+ libvirtd stops responding in oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding in oneiric
To manage
Marking confirmed based on the fedora bug.
Per comment 21 in the fedora bug, we should cherrypick these four
patches to oneiric:
3ec12898
32d3ec74
a8bb75a3
b265beda
** Bug watch added: Red Hat Bugzilla #757382
https://bugzilla.redhat.com/show_bug.cgi?id=757382
** Also affects: libvirt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Oneiric)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Unfortunately those patches don't apply cleanly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding
To manage notifications about this bug go to:
Sorry, for version numbering reasons I had to put the package in ppa
:serge-hallyn/libvirt-mav.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding
To manage
I've done by best to backport the patches. The gist is to get rid of
localtime_r usage. A package with the backported patches should soon be
building in ppa:serge-hallyn/virt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding
To manage notifications about this bug go to:
** Attachment added: requested output
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/+attachment/2738411/+files/903212.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
The second libvirtd is a child of the first, so I suspect it's actually
fine.
User PID PPID
root 30895 1 0 Feb13 ?00:02:05 /usr/sbin/libvirtd -d
root 20389 30895 0 13:04 ?00:00:00 /usr/sbin/libvirtd -d
Chuck, would it be possible to try reproducing this on
Chuck, is there anything nova could be doing to manually start its own
seconnd libvirtd without going through upstart?
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting. Thanks for the information.
One libvirtd task appears to be on its own, while the other has all the
expected threads.
Which pid is reported by 'status libvirt-bin' ?
(I realize you've probably reconfigured this machine by now, and we'll
need to wait for the next time this happens.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd stops responding
To manage notifications about this bug go to:
We encountered this again. There appear to be two separate libvirtd
processes running on the machine, which I have a feeling makes this a
pathological case, but I captured the first part of the information
you're looking for. When we see this again, I'll grab the same info
plus the various
I have verified on a machine in this state and I can start a kvm
instance by hand when libvirtd is not responding. Is there any further
diagnosis that I can do?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First please attach the output of:
ps -ef
find /var/lib/libvirt
x=`pidof libvirtd`
for y in `/bin/ls /proc/$x/task/`; do
echo $y
cat /proc/$y/status
done
Now, this is a bit of a big stick, but you could trace all libvirtd
processes at once:
x=`pidof libvirtd`
for y in `/bin/ls
Attached virsh.debug
** Attachment added: virsh.debug
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/+attachment/2639493/+files/virsh.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had to prune the libvirt.log as it is ~5GB.
Attached is the libvirtd.log when the above virsh command was run. If
you need more I may be able to trim the non-unique log lines.
** Attachment added: libvirtd.log
Thanks for that info. Is there anything helpful in
/var/log/libvirt/qemu/xp1.log?
Are you able to run kvm or qemu by hand?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903212
Title:
libvirtd
@Serge:
None of the machines that are experiencing this problem have a
/var/log/libvirt/qemu/xp1.log log file.
These are Openstack nova-compute nodes running KVM and (un)fortunately I
do not have a node that is currently not responding. One I do, I will
attempt to run KVM manually.
--
You
Thanks for taking the time to report this bug.
To get some extra debugging information, could you please edit
/etc/libvirt/libvirtd.conf and add the line
log_level = 1
Then restart libvirtd. Then, when this reoccurs, do
strace -f -ovirsh.debug virsh list
then attach both the
24 matches
Mail list logo
