Bug 36359 - virsh SEGV during virsh define
Summary: virsh SEGV during virsh define
Status: CLOSED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Virtualization - Xen
Version: UCS 3.2
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-31 07:26 CET by Tim Petersen
Modified: 2023-06-28 10:46 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID: 00026
Max CVSS v3 score:


Attachments
Backtrace with dbg for virsh and gnutls26 (5.44 KB, text/plain)
2014-10-31 07:27 CET, Tim Petersen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Petersen univentionstaff 2014-10-31 07:26:36 CET
Core was generated by `virsh define /<pathtoxml>'

Program terminated with signal 11, Segmentation fault.
#0  0x00007fdc653d91f4 in ?? () from /usr/lib/libgnutls.so.26
Comment 1 Tim Petersen univentionstaff 2014-10-31 07:27:46 CET
Created attachment 6267 [details]
Backtrace with dbg for virsh and gnutls26

3.10.0-ucs81-amd64

Whole USI at 2014102921000291
Comment 2 Stefan Gohmann univentionstaff 2014-12-03 13:30:02 CET
Is it reproducible with the same XML file?
Comment 3 Philipp Hahn univentionstaff 2014-12-03 14:31:29 CET
Most probably a duplicate of Bug #31032: "virsh -c xen:/// define" by-passes the running Xend and directly communicates with Xend. It also monitors /var/lib/xend/domains/ using inotify, which has a race-condition: As "virsh define" is very short-lived, the connection is already closed when the inotify event occurs , leading to the already closed connection being used again, which often leads to a crash inside a (unrelated) called function.

By using "virsh -c xen+unix:/// define" the running libvirtd is used, which so far has not shown the bug.
Comment 4 Philipp Hahn univentionstaff 2017-04-24 11:57:01 CEST
This was a Bug with Xen; as Xen is deprecated since UCS-4.x → WONTFIX