oVirt 3.5 on RHEL 6.6 hyperv enabled breaks Windows VMs
https://bugzilla.redhat.com/show_bug.cgi?id=1110305 This enabled the hv_relaxed flag on all my Windows VMs, causing them to no longer boot. The same thing would happen if I simply booted from the Windows install media. I would get a screen with a stop error: Your PC needs to restart. Please hold down the power button. Error Code: 0x0000001E Parameters: 0xFFFFFFFFC0000096 0xFFFFF802C4044EA4 0x00000000000000000 0x00000000000000000 I created a file called /etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line: os.windows_xp.devices.hyperv.enabled.value = false I restarted ovirt-engine and now I can start my Windows VMs. Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is there something else I'm doing wrong? I would like to not need this workaround. Thanks. Charles
------=_NextPartTM-000-4ada0c12-79cc-410d-9056-5d8bf2bfc8bf Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD1735867619FEXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735867619FEXCHANGEcollogi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, we are running the hyperv flags since months in our Win7 VMs without any is= sue. As we are still on OVirt 3.4 FC20 infrastructure we set them with hook= s (and really depend on them). Maybe RHEL related? Markus Am 24.10.2014 18:22 schrieb Charles Gruener <cgruener@gruener.us>: https://bugzilla.redhat.com/show_bug.cgi?id=3D1110305 This enabled the hv_relaxed flag on all my Windows VMs, causing them to no = longer boot. The same thing would happen if I simply booted from the Windo= ws install media. I would get a screen with a stop error: Your PC needs to restart. Please hold down the power button. Error Code: 0x0000001E Parameters: 0xFFFFFFFFC0000096 0xFFFFF802C4044EA4 0x00000000000000000 0x00000000000000000 I created a file called /etc/ovirt-engine/osinfo.conf.d/01-windows.properti= es that had one line: os.windows_xp.devices.hyperv.enabled.value =3D false I restarted ovirt-engine and now I can start my Windows VMs. Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is there s= omething else I'm doing wrong? I would like to not need this workaround. = Thanks. Charles --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735867619FEXCHANGEcollogi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
</head> <body> <p dir=3D"ltr">Hi,</p> <p dir=3D"ltr">we are running the hyperv flags since months in our Win7 VMs= without any issue. As we are still on OVirt 3.4 FC20 infrastructure we set= them with hooks (and really depend on them).</p> <p dir=3D"ltr">Maybe RHEL related?</p> <p dir=3D"ltr">Markus</p> <div class=3D"quote">Am 24.10.2014 18:22 schrieb Charles Gruener <cgruen= er@gruener.us>:<br type=3D"attribution"> </div> <div> <div dir=3D"ltr"> <div><a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1110305">http= s://bugzilla.redhat.com/show_bug.cgi?id=3D1110305</a></div> <div><br> </div> <div>This enabled the hv_relaxed flag on all my Windows VMs, causing them t= o no longer boot. The same thing would happen if I simply booted from= the Windows install media. I would get a screen with a stop error:</= div> <div><br> </div> <div>Your PC needs to restart.</div> <div>Please hold down the power button.</div> <div>Error Code: 0x0000001E</div> <div>Parameters:</div> <div>0xFFFFFFFFC0000096</div> <div>0xFFFFF802C4044EA4</div> <div>0x00000000000000000</div> <div>0x00000000000000000</div> <div><br> </div> <div>I created a file called /etc/ovirt-engine/osinfo.conf.d/01-windows.pro= perties that had one line:</div> <div><br> </div> <div>os.windows_xp.devices.hyperv.enabled.value =3D false</div> <div><br> </div> <div>I restarted ovirt-engine and now I can start my Windows VMs.</div> <div><br> </div> <div>Why does this occur? Is it because I upgraded from 3.4 to 3.5?&n= bsp; Is there something else I'm doing wrong? I would like to not nee= d this workaround. Thanks.</div> <div><br> </div> <div>Charles</div> </div> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735867619FEXCHANGEcollogi_-- ------=_NextPartTM-000-4ada0c12-79cc-410d-9056-5d8bf2bfc8bf Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-4ada0c12-79cc-410d-9056-5d8bf2bfc8bf--
--Apple-Mail=_FBF7C6DC-FCAB-400F-846B-7D9CCE82886E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 Oct 2014, at 18:43, Markus Stockhausen wrote:
Hi, =20 we are running the hyperv flags since months in our Win7 VMs without = any issue. As we are still on OVirt 3.4 FC20 infrastructure we set them = with hooks (and really depend on them). =20 Maybe RHEL related? =20 It might be. What's running on your host?
Markus =20 Am 24.10.2014 18:22 schrieb Charles Gruener <cgruener@gruener.us>: https://bugzilla.redhat.com/show_bug.cgi?id=3D1110305 =20 This enabled the hv_relaxed flag on all my Windows VMs, causing them = to no longer boot. The same thing would happen if I simply booted from =
=20 Your PC needs to restart. Please hold down the power button. Error Code: 0x0000001E Parameters: 0xFFFFFFFFC0000096 0xFFFFF802C4044EA4 0x00000000000000000 0x00000000000000000 =20 I created a file called = /etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line: =20 os.windows_xp.devices.hyperv.enabled.value =3D false =20 I restarted ovirt-engine and now I can start my Windows VMs. =20 Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is =
Did you see the same problem with anything newer than Windows XP? Thanks, michal the Windows install media. I would get a screen with a stop error: there something else I'm doing wrong? I would like to not need this = workaround. Thanks.
=20 Charles = <InterScan_Disclaimer.txt>_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_FBF7C6DC-FCAB-400F-846B-7D9CCE82886E Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii <html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 24 Oct 2014, at 18:43, Markus Stockhausen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <div><p dir="ltr">Hi,</p><p dir="ltr">we are running the hyperv flags since months in our Win7 VMs without any issue. As we are still on OVirt 3.4 FC20 infrastructure we set them with hooks (and really depend on them).</p><p dir="ltr">Maybe RHEL related?</p></div></blockquote>It might be. What's running on your host?</div><div><br></div><div>Did you see the same problem with anything newer than Windows XP?</div><div><br></div><div>Thanks,</div><div>michal</div><div><blockquote type="cite"><div><p dir="ltr">Markus</p> <div class="quote">Am 24.10.2014 18:22 schrieb Charles Gruener <<a href="mailto:cgruener@gruener.us">cgruener@gruener.us</a>>:<br type="attribution"> </div> <div> <div dir="ltr"> <div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1110305">https://bugzilla.redhat.com/show_bug.cgi?id=1110305</a></div> <div><br> </div> <div>This enabled the hv_relaxed flag on all my Windows VMs, causing them to no longer boot. The same thing would happen if I simply booted from the Windows install media. I would get a screen with a stop error:</div> <div><br> </div> <div>Your PC needs to restart.</div> <div>Please hold down the power button.</div> <div>Error Code: 0x0000001E</div> <div>Parameters:</div> <div>0xFFFFFFFFC0000096</div> <div>0xFFFFF802C4044EA4</div> <div>0x00000000000000000</div> <div>0x00000000000000000</div> <div><br> </div> <div>I created a file called /etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line:</div> <div><br> </div> <div>os.windows_xp.devices.hyperv.enabled.value = false</div> <div><br> </div> <div>I restarted ovirt-engine and now I can start my Windows VMs.</div> <div><br> </div> <div>Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is there something else I'm doing wrong? I would like to not need this workaround. Thanks.</div> <div><br> </div> <div>Charles</div> </div> </div> </div> <span><InterScan_Disclaimer.txt></span>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>http://lists.ovirt.org/mailman/listinfo/users<br></blockquote></div><br></body></html> --Apple-Mail=_FBF7C6DC-FCAB-400F-846B-7D9CCE82886E--
The three Windows VMs I tried were Windows 7, Windows 8.1, and Windows Server 2012 R2. All experienced the stop error. On Mon, Oct 27, 2014 at 8:21 AM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 24 Oct 2014, at 18:43, Markus Stockhausen wrote:
Hi,
we are running the hyperv flags since months in our Win7 VMs without any issue. As we are still on OVirt 3.4 FC20 infrastructure we set them with hooks (and really depend on them).
Maybe RHEL related?
It might be. What's running on your host?
Did you see the same problem with anything newer than Windows XP?
Thanks, michal
Markus Am 24.10.2014 18:22 schrieb Charles Gruener <cgruener@gruener.us>: https://bugzilla.redhat.com/show_bug.cgi?id=1110305
This enabled the hv_relaxed flag on all my Windows VMs, causing them to no longer boot. The same thing would happen if I simply booted from the Windows install media. I would get a screen with a stop error:
Your PC needs to restart. Please hold down the power button. Error Code: 0x0000001E Parameters: 0xFFFFFFFFC0000096 0xFFFFF802C4044EA4 0x00000000000000000 0x00000000000000000
I created a file called /etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line:
os.windows_xp.devices.hyperv.enabled.value = false
I restarted ovirt-engine and now I can start my Windows VMs.
Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is there something else I'm doing wrong? I would like to not need this workaround. Thanks.
Charles <InterScan_Disclaimer.txt> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
------=_Part_331445_181910974.1414413405719 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit ----- Original Message -----
From: "Charles Gruener" <cgruener@gruener.us> To: "Michal Skrivanek" <michal.skrivanek@redhat.com> Cc: "users@ovirt.org Users" <users@ovirt.org> Sent: Monday, October 27, 2014 1:32:50 PM Subject: Re: [ovirt-users] oVirt 3.5 on RHEL 6.6 hyperv enabled breaks Windows VMs
The three Windows VMs I tried were Windows 7, Windows 8.1, and Windows Server 2012 R2. All experienced the stop error.
</blockquote><div><br></div><div>This is quite interesting because the hv_= relaxed thing was supposed to _improve_ stability for windows 7 onwards.<br= </div><div>I was expecting troubles with older windows (XP), not with newe= r ones.<br></div><div><br></div><div>Can you share what is running on your = hypervisors? versions of libvirt and qemu.<br></div><div>Moreover, qemu and=
This is quite interesting because the hv_relaxed thing was supposed to _improve_ stability for windows 7 onwards. I was expecting troubles with older windows (XP), not with newer ones. Can you share what is running on your hypervisors? versions of libvirt and qemu. Moreover, qemu and libvirt logs would help. Thanks, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani ------=_Part_331445_181910974.1414413405719 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: times new roman, new york, times, se= rif; font-size: 12pt; color: #000000"><div><br></div><hr id=3D"zwchr"><bloc= kquote style=3D"border-left:2px solid #1010FF;margin-left:5px;padding-left:= 5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;fo= nt-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Charles= Gruener" <cgruener@gruener.us><br><b>To: </b>"Michal Skrivanek" <= michal.skrivanek@redhat.com><br><b>Cc: </b>"users@ovirt.org Users" <u= sers@ovirt.org><br><b>Sent: </b>Monday, October 27, 2014 1:32:50 PM<br><= b>Subject: </b>Re: [ovirt-users] oVirt 3.5 on RHEL 6.6 hyperv enabled break= s Windows VMs<br><div><br></= div><div dir=3D"ltr">The three Windows VMs I tried were Windows 7, Windows = 8.1, and Windows Server 2012 R2. All experienced the stop error.</div= libvirt logs would help.<br></div><div><br></div><div>Thanks,<br></div><di= v><br></div><div><br></div><div>-- <br></div><div><span name=3D"x"></span>F= rancesco Romani<br>RedHat Engineering Virtualization R & D<br>Phone: 82= 61328<br>IRC: fromani<span name=3D"x"></span><br></div></div></body></html> ------=_Part_331445_181910974.1414413405719--
Here's what's installed on one of my hypervisors: gpxe-roms-qemu.noarch 0.9.7-6.12.el6 @rhel-x86_64-server-6 libvirt.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 libvirt-client.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 libvirt-lock-sanlock.x86_64 0.10.2-46.el6 @rhel-x86_64-server-optional-6 libvirt-python.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 ovirt-release35.noarch 001-1 @/ovirt-release35 qemu-img-rhev.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5 qemu-kvm-rhev.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5 qemu-kvm-rhev-tools.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5 vdsm.x86_64 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-cli.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-jsonrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-python.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-python-zombiereaper.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-xmlrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 vdsm-yajsonrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5 virt-what.x86_64 1.11-1.2.el6 @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4 I noticed the machines do not have the qemu-kvm package installed, only qemu-kvm-rhev. What's the difference in those two packages? When I try to manually install qemu-kvm, it won't and lets me know that: "Package 2:qemu-kvm-0.12.1.2-2.445.el6.x86_64 is obsoleted by 2:qemu-kvm-rhev-0.12.1.2-2.415.el6_5.14.x86_64 which is already installed" I've also noticed that I can't live snapshot machines because it says my underlying qemu doesn't support it and thought that might be a related issue. The machines have Intel(R) Xeon(R) CPU E5-2670 CPUs, if it makes any difference. Charles On Mon, Oct 27, 2014 at 8:36 AM, Francesco Romani <fromani@redhat.com> wrote:
------------------------------
*From: *"Charles Gruener" <cgruener@gruener.us> *To: *"Michal Skrivanek" <michal.skrivanek@redhat.com> *Cc: *"users@ovirt.org Users" <users@ovirt.org> *Sent: *Monday, October 27, 2014 1:32:50 PM *Subject: *Re: [ovirt-users] oVirt 3.5 on RHEL 6.6 hyperv enabled breaks Windows VMs
The three Windows VMs I tried were Windows 7, Windows 8.1, and Windows Server 2012 R2. All experienced the stop error.
This is quite interesting because the hv_relaxed thing was supposed to _improve_ stability for windows 7 onwards. I was expecting troubles with older windows (XP), not with newer ones.
Can you share what is running on your hypervisors? versions of libvirt and qemu. Moreover, qemu and libvirt logs would help.
Thanks,
-- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
----- Original Message -----
From: "Charles Gruener" <cgruener@gruener.us> To: "Francesco Romani" <fromani@redhat.com> Cc: "Michal Skrivanek" <michal.skrivanek@redhat.com>, "users@ovirt.org Users" <users@ovirt.org> Sent: Monday, October 27, 2014 3:56:00 PM Subject: Re: [ovirt-users] oVirt 3.5 on RHEL 6.6 hyperv enabled breaks Windows VMs
Here's what's installed on one of my hypervisors:
gpxe-roms-qemu.noarch 0.9.7-6.12.el6 @rhel-x86_64-server-6 libvirt.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 libvirt-client.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 libvirt-lock-sanlock.x86_64 0.10.2-46.el6 @rhel-x86_64-server-optional-6 libvirt-python.x86_64 0.10.2-46.el6 @rhel-x86_64-server-6 ovirt-release35.noarch 001-1 @/ovirt-release35 qemu-img-rhev.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5
qemu-kvm-rhev.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5
qemu-kvm-rhev-tools.x86_64 2:0.12.1.2-2.415.el6_5.14 @ovirt-3.5
vdsm.x86_64 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-cli.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-jsonrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-python.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-python-zombiereaper.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-xmlrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
vdsm-yajsonrpc.noarch 4.16.7-1.gitdb83943.el6 @ovirt-3.5
virt-what.x86_64 1.11-1.2.el6 @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
OK, seems a stock RHEL 6.6. I wonder if the recommended hv settings are really supported on old QEMUs. Need to check about this: will do and will report. If you'll be the most welcome to file a bug against oVirt for this issue, and set target release to 3.5.1, so we can track this issue.
I noticed the machines do not have the qemu-kvm package installed, only qemu-kvm-rhev. What's the difference in those two packages? When I try to manually install qemu-kvm, it won't and lets me know that:
"Package 2:qemu-kvm-0.12.1.2-2.445.el6.x86_64 is obsoleted by 2:qemu-kvm-rhev-0.12.1.2-2.415.el6_5.14.x86_64 which is already installed"
This is totally expected. qemu-kvm-rhev provides additional facilities and it is better to use it.
I've also noticed that I can't live snapshot machines because it says my underlying qemu doesn't support it and thought that might be a related issue.
This is known and different issue: https://bugzilla.redhat.com/show_bug.cgi?id=1149667 hopefully the fix will be available soon
The machines have Intel(R) Xeon(R) CPU E5-2670 CPUs, if it makes any difference.
Charles
Thanks! -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
OK, seems a stock RHEL 6.6. I wonder if the recommended hv settings are really supported on old QEMUs. Need to check about this: will do and will report.
If you'll be the most welcome to file a bug against oVirt for this issue, and set target release to 3.5.1, so we can track this issue.
Looks like I need to search RedHat bugzilla a bit better. Issues for this
already exist: https://bugzilla.redhat.com/show_bug.cgi?id=1063124 https://bugzilla.redhat.com/show_bug.cgi?id=1069082 Charles
On Mon, Oct 27, 2014 at 4:40 PM, Francesco Romani <fromani@redhat.com> wrote:
I've also noticed that I can't live snapshot machines because it says my underlying qemu doesn't support it and thought that might be a related issue.
This is known and different issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1149667
hopefully the fix will be available soon
It seems errata was released in 6.6 for this problem with libvirt: https://rhn.redhat.com/rhn/errata/details/Details.do?eid=28512 package is libvirt-0.10.2-46.el6_6.1.x86_64.rpm Not tested yet at my side. Gianluca
On 27/10/14 15:56, Charles Gruener wrote:
I noticed the machines do not have the qemu-kvm package installed, only qemu-kvm-rhev. What's the difference in those two packages? When I try to manually install qemu-kvm, it won't and lets me know that:
"Package 2:qemu-kvm-0.12.1.2-2.445.el6.x86_64 is obsoleted by 2:qemu-kvm-rhev-0.12.1.2-2.415.el6_5.14.x86_64 which is already installed"
I've also noticed that I can't live snapshot machines because it says my underlying qemu doesn't support it and thought that might be a related issue.
This is weird, the only functionality qemu-kvm-rhev provides which is not in qemu-kvm on el6/7 is live snapshots. So this really should work. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On Mon, Oct 27, 2014 at 4:47 PM, Sven Kieske <s.kieske@mittwald.de> wrote:
This is weird,
the only functionality qemu-kvm-rhev provides which is not in qemu-kvm on el6/7 is live snapshots. So this really should work.
The bug indicated by Francesco is specificaly against RHEL 6.6 " In Red Hat Enterprise Linux 6.6, support was added for libvirt to report whether QEMU is capable of creating snapshots. However, libvirt did not probe for the snapshot capability properly. As a consequence, the snapshot capability of KVM Guest Image in VDSM was reported as unavailable even when it was available, and creating a disk snapshot in some cases failed. With this update, libvirt no longer reports QEMU snapshot capability, and therefore does not cause the described problem. " Sven, you want a too simple life (and me too... ;-) Gianluca
participants (6)
-
Charles Gruener -
Francesco Romani -
Gianluca Cecchi -
Markus Stockhausen -
Michal Skrivanek -
Sven Kieske