<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Dan,</div>
<div><br>
</div>
<div>One of the technical guys here at Cisco asked me a really good technical question about libvirt upgrades in containers which I was unable to answer. My suspicion is the linux VM system just sorts it out, but I wanted to get your input.</div>
<div><br>
</div>
<div>Assume libvirt version 1 is running in a container. We kill the container, qemu processes go to the main pid space as detailed in my blog[1] using the —pid=host feature you developed. Now version #2 of qemu is started during an atomic upgrade (pull,
stop, start of the container) to libvirt version 2. How does the operating system know to keep a copy of version #1 around until the system reboots?</div>
<div><br>
</div>
<div>Thanks</div>
<div>-steve</div>
<div><br>
</div>
<div>[1] <a href="http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/">http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/</a></div>
</body>
</html>