[libvirt-users] Can I update libvirt while KVM guest os are running
Hello I have a simple question. Can I update libvirt RPM while KVM guest OS on RHEL5 is running. Background When I run rhn_register, then rhn-virtualization-host RPM was installed by RHN. And then libvirt-python was also installed from the RHN. The libvirt-python RPM has a dependency with libvirt. And the dependency was not only the RPM file name, and also specific RPM versions as well. # rpm -qR libvirt-python /usr/bin/python (snip) libssl.so.6()(64bit) libvirt = 0.8.2-15.el5 <== libvirt.so.0()(64bit) So the libvirt from RHEL5.5 was updated to libvirt from RHEL5.6 by this accident. If nothing was happen, I don't care. But after the force libvirt update, I couldn't do attach-disk. error : Failed to attach disk error : internal error missing disk device alias name for hdc Now I would like to confirm from the authority that libvirt update while running guest os is supported or not. If supported, then these messages indicated something going wrong. If not, I can ignore it. Regards, Masanari
On Fri, Apr 1, 2011 at 7:11 PM, Masanari Iida <standby24x7@gmail.com> wrote:
Hello I have a simple question. Can I update libvirt RPM while KVM guest OS on RHEL5 is running.
I am still searching for this answer. As far as I have seen on FAQ, restarting libvirtd may not affect the virtual machine.
Will restarting the libvirt daemon stop my virtual machines?
NO, as of version 0.6.0 (Jan 2009). Versions older than this will kill VMs if the libvirtd daemon is stopped, so beware.
My case was libvirt update from 0.6.3 to 0.8.2 and then restart libvirtd while running the guest os. Regards, Masanari
Answer to myself. Troubleshooted the symptom with my colleague and found the root cause. In case of libvirt update from 0.6.3 to 0.8.2, I had to restart my Guest OS. Otherwise I got an error when I execute attached-disk with libvirt 0.8.2.
error: Failed to attach disk error: internal error missing disk device alias name for hdc
It was because virDomainDeviceInfo info in struct _virDomainDiskDef was NOT exist in 0.6.3. After update, libvirt 0.8.2 does origdisk->info.alias, and it causes this error message. I believe there are many changes between 2 versions. So I conclude that it is safe to stop Guest OS when libvirtd is updated. Thanks Masanari
participants (1)
-
Masanari Iida