)]}'
{"specs/juno/hyper-v-generation-2-vms.rst":[{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"6a78d16d17c897e481d69fe9076cde1487613360","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Operating systems supporting generation 2:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Windows Server 2012 / Windows 8 and above"},{"line_number":34,"context_line":"* Newer Linux kernels"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"The image must be in VHDX format."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_0cb13c8f","line":34,"updated":"2014-07-02 09:48:29.000000000","message":"What happens if you enable  generation 2 for an operating system that does not support it. Will the guest OS fallback to just using gen 2 features, or will it crash \u0026 burn. eg I\u0027m trying to understand if we can just enable gen 2 by default out of the box on a new enough hyperv host.","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":3185,"name":"Alessandro Pilotti","email":"apilotti@cloudbasesolutions.com","username":"alexpilotti"},"change_message_id":"09bb25059717b36c273216cbe17d7bf6173f411f","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Operating systems supporting generation 2:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Windows Server 2012 / Windows 8 and above"},{"line_number":34,"context_line":"* Newer Linux kernels"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"The image must be in VHDX format."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_81ec2e91","line":34,"in_reply_to":"baada198_0cb13c8f","updated":"2014-07-02 12:28:13.000000000","message":"\"crash and burn\" is a fairly accurate definition, that\u0027s the reason for suggesting generation 1 by default. This app;lies also to Windows \u003c\u003d 2008 R2 / 7","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":3185,"name":"Alessandro Pilotti","email":"apilotti@cloudbasesolutions.com","username":"alexpilotti"},"change_message_id":"ea9b88f67a51663f5e02b5333fe0758db356438e","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Operating systems supporting generation 2:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Windows Server 2012 / Windows 8 and above"},{"line_number":34,"context_line":"* Newer Linux kernels"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"The image must be in VHDX format."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_4cbecdd5","line":34,"in_reply_to":"baada198_6ccb91a5","updated":"2014-07-02 12:38:33.000000000","message":"Done","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"954f7867da88f8d6058b42129b1039ef5fdece6c","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Operating systems supporting generation 2:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Windows Server 2012 / Windows 8 and above"},{"line_number":34,"context_line":"* Newer Linux kernels"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"The image must be in VHDX format."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_6ccb91a5","line":34,"in_reply_to":"baada198_81ec2e91","updated":"2014-07-02 12:36:33.000000000","message":"Ok, can you mention in this behaviour in the spec as the reason why we use v1 by default","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"6a78d16d17c897e481d69fe9076cde1487613360","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"The Hyper-V compute driver creates a generation 2 VM based on a property"},{"line_number":42,"context_line":"defined in the instance image, defaulting to generation 1."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The compute driver reverts to generation 1 if the image format is VHD,"},{"line_number":45,"context_line":"generating a warning."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_8c962cef","line":42,"updated":"2014-07-02 09:48:29.000000000","message":"Multiple drivers have a concept of different versions of the guest ABI, so I think we need to come up with a consistent approach to this across drivers.  VMWare has the vmx version number, libvirt has a \u0027machine type\u0027 which applies across all HVs it manages.\n\nSo rather than defining a property which is a HyperV version number, I think we should define a more general string based name to represent guest ABIs.  eg we could allow  hw_machine_type\u003d{hyperv-gen1,hyperv-gen2} for this.","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"954f7867da88f8d6058b42129b1039ef5fdece6c","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"The Hyper-V compute driver creates a generation 2 VM based on a property"},{"line_number":42,"context_line":"defined in the instance image, defaulting to generation 1."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The compute driver reverts to generation 1 if the image format is VHD,"},{"line_number":45,"context_line":"generating a warning."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_ccbf3dfb","line":42,"in_reply_to":"baada198_81a34e4e","updated":"2014-07-02 12:36:33.000000000","message":"Ok, lets go for hw_machine_type as I suggested.","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":3185,"name":"Alessandro Pilotti","email":"apilotti@cloudbasesolutions.com","username":"alexpilotti"},"change_message_id":"09bb25059717b36c273216cbe17d7bf6173f411f","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"The Hyper-V compute driver creates a generation 2 VM based on a property"},{"line_number":42,"context_line":"defined in the instance image, defaulting to generation 1."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The compute driver reverts to generation 1 if the image format is VHD,"},{"line_number":45,"context_line":"generating a warning."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_81a34e4e","line":42,"in_reply_to":"baada198_8c962cef","updated":"2014-07-02 12:28:13.000000000","message":"I\u0027m fine with it. Should we confirm hw_machine_type as property name?","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":3185,"name":"Alessandro Pilotti","email":"apilotti@cloudbasesolutions.com","username":"alexpilotti"},"change_message_id":"ea9b88f67a51663f5e02b5333fe0758db356438e","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"The Hyper-V compute driver creates a generation 2 VM based on a property"},{"line_number":42,"context_line":"defined in the instance image, defaulting to generation 1."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The compute driver reverts to generation 1 if the image format is VHD,"},{"line_number":45,"context_line":"generating a warning."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_8cb8e5e6","line":42,"in_reply_to":"baada198_ccbf3dfb","updated":"2014-07-02 12:38:33.000000000","message":"Done","commit_id":"b35803af96b5b2e97c5004077ede3a713f7e5176"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"8460f6f44e8385b2a3696c0d32519ffc5dccc985","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Testing"},{"line_number":128,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Unit tests. Hyper-V specific Tempest tests can be added as well."},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Documentation Impact"},{"line_number":133,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_a853b537","line":130,"updated":"2014-07-11 00:06:40.000000000","message":"hyperv CI will cover this as well?\n\nI don\u0027t think we want to add backend specific tempest tests.","commit_id":"c5cb56d71353b465c8417ee3c1ff84e23e867012"},{"author":{"_account_id":3185,"name":"Alessandro Pilotti","email":"apilotti@cloudbasesolutions.com","username":"alexpilotti"},"change_message_id":"638dba2380f91b9ab3cb1b05e56e0a4307e32282","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Testing"},{"line_number":128,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Unit tests. Hyper-V specific Tempest tests can be added as well."},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Documentation Impact"},{"line_number":133,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_ff097e84","line":130,"in_reply_to":"baada198_451edbbc","updated":"2014-07-21 19:42:21.000000000","message":"Yes, It will be tested on the Hyper-V CI. Adding an esplicit note.","commit_id":"c5cb56d71353b465c8417ee3c1ff84e23e867012"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"ba6713324e2cf8adb2e616b110c7351e31f69bed","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Testing"},{"line_number":128,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Unit tests. Hyper-V specific Tempest tests can be added as well."},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Documentation Impact"},{"line_number":133,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_451edbbc","line":130,"in_reply_to":"baada198_a853b537","updated":"2014-07-16 08:47:18.000000000","message":"+1 to jogo\u0027s comment","commit_id":"c5cb56d71353b465c8417ee3c1ff84e23e867012"}]}
