RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 838724 - libvirt update crashes my vm's
Summary: libvirt update crashes my vm's
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-09 23:24 UTC by Todd
Modified: 2012-07-13 08:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-10 09:27:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
my domains (xml's) (6.25 KB, application/octet-stream)
2012-07-10 02:43 UTC, Todd 		no flags Details
View All

Description Todd 2012-07-09 23:24:44 UTC 
Hi All,

I am coming from the "Community": Scientific Linux 6.2, 64 bit.  Would one of our interpret heroes at Red hat please fix this for me?

This morning, according to /var/log/yum.log, I got an automatic (meaning unauthorized) update to libvirt: libvirt-0.9.4-23.el6.x86_64.  This unwanted update hosed my KVM virtual machines very big time.

Symptoms:

When I fired up my KVM Virtual Machine Manager (virt-manager) this morning, four of my seven virtual machines disappeared, including the one I desperately needed.

Firing up the three that remain, I get the following error message:

     Error starting domain: unsupported configuration: spice
     TLS port set in XML configuration, but TLS is disabled
     in qemu.conf 

"virsh edit" on the missing VM's, give:
   # virsh edit KVM-WinXP
   error: failed to get domain 'KVM-WinXP'
   error: Domain not found: no domain with matching name 'KVM-WinXP'

The following work around fixed my problem:

# yum downgrade libvirt  libvirt-client  libvirt-python
Loaded plugins: priorities, refresh-packagekit, security
Setting up Downgrade Process
18 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package libvirt.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt.x86_64 0:0.9.10-21.el6 will be erased
---> Package libvirt-client.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt-client.x86_64 0:0.9.10-21.el6 will be erased
---> Package libvirt-python.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt-python.x86_64 0:0.9.10-21.el6 will be erased
--> Finished Dependency Resolution 

Now to figure out how to turn off those back ground updates.  (flash-plugin updated too.  Did not want that one either.)

Many thanks,
-T
Comment 2 Dave Allan 2012-07-10 02:25:38 UTC 
Hi Todd,

Thanks for your forthrightness about your distro.  :)

Please provide:

The exact sequence of events: can you set up a test system and reproduce the problem?

What version was running before and after the upgrade?

The domain XML that reproduces the problem.

What OS was running in the guest.

Dave
Comment 3 Todd 2012-07-10 02:43:07 UTC 
(In reply to comment #2)
> Hi Todd,
> 
> Thanks for your forthrightness about your distro.  :)

I am an honest beggar

> 
> Please provide:
> 
> The exact sequence of events: can you set up a test system and reproduce the
> problem?

1) turned the computer on

2) /var/log/yum.log:
    Jul 09 11:18:50 Updated: libvirt-0.9.10-21.el6.x86_64

I have since turned off yum-autoupdater

> 
> What version was running before and after the upgrade?

Before: libvirt.x86_64 0:0.9.4-23.el6
After: libvirt-0.9.4-23.el6.x86_64


> 
> The domain XML that reproduces the problem.

None of the domains (VMs) would actually run.  I will tar them all up for your.  Only W8, W7 and fedora 32 would actually show in list.


> 
> What OS was running in the guest.

See the attachment

> 
> Dave
Comment 4 Todd 2012-07-10 02:43:57 UTC 
Created attachment 597194 [details]
my domains (xml's)
Comment 6 Daniel Berrangé 2012-07-10 09:27:47 UTC 
As indicated by the error message you quoted, you have requested that SPICE listen on a TLS  port:

    <graphics type='spice' port='5905' tlsPort='5905' autoport='no' listen='127.0.0.1'>

but you have not configured TLS in /etc/libvirt/qemu.conf.  Previously this config error was not diagnosed, but now it is. Even if you did configure TLS in qemu.conf, your config is still broken because you have given the same port number for both plain & TLS ports.  If you fix your XML files in /etc/libvirt/qemu and reload libvirtd, things will work as expected.
Note You need to log in before you can comment on or make changes to this bug.