[RFC] [Kimchi] #1092: Allow to set disk performance options per guest and template
Propose: allow user to edit cache, io and bus for each disk Make cache and io part was easy, but i got big trouble to change bus Questions: 1) How we are going to change the bus? Got some issues aroud: A) How to determine available bus? I know there is a function, but is it works with vms with different buses? B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
On 02/27/2017 03:34 PM, Ramon Medeiros wrote:
Propose: allow user to edit cache, io and bus for each disk
Make cache and io part was easy, but i got big trouble to change bus
Questions:
1) How we are going to change the bus? Got some issues aroud:
A) How to determine available bus? I know there is a function, but is it works with vms with different buses?
Probably, yes! But I encourage you to do as many tests as you can do.
B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
Not sure I got your question. The user will update the driver on guest/template edit. The guest/template creation keeps the same.
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 02/28/2017 11:51 AM, Aline Manera wrote:
On 02/27/2017 03:34 PM, Ramon Medeiros wrote:
Propose: allow user to edit cache, io and bus for each disk
Make cache and io part was easy, but i got big trouble to change bus
Questions:
1) How we are going to change the bus? Got some issues aroud:
A) How to determine available bus? I know there is a function, but is it works with vms with different buses?
Probably, yes! But I encourage you to do as many tests as you can do.
B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
Not sure I got your question. The user will update the driver on guest/template edit. The guest/template creation keeps the same.
That's not my question. But, in this case: 1) Got a Fedora running on vda 2) Change to sda 3) Fedora will boot? What is going to happen?
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 02/28/2017 03:35 PM, Ramon Medeiros wrote:
On 02/28/2017 11:51 AM, Aline Manera wrote:
On 02/27/2017 03:34 PM, Ramon Medeiros wrote:
Propose: allow user to edit cache, io and bus for each disk
Make cache and io part was easy, but i got big trouble to change bus
Questions:
1) How we are going to change the bus? Got some issues aroud:
A) How to determine available bus? I know there is a function, but is it works with vms with different buses?
Probably, yes! But I encourage you to do as many tests as you can do.
B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
Not sure I got your question. The user will update the driver on guest/template edit. The guest/template creation keeps the same.
That's not my question. But, in this case:
1) Got a Fedora running on vda 2) Change to sda 3) Fedora will boot?
What is going to happen?
The main question is: by changing the device name, can kimchi do something to help the user to deal with this change?
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 02/28/2017 03:50 PM, Ramon Medeiros wrote:
On 02/28/2017 03:35 PM, Ramon Medeiros wrote:
On 02/28/2017 11:51 AM, Aline Manera wrote:
On 02/27/2017 03:34 PM, Ramon Medeiros wrote:
Propose: allow user to edit cache, io and bus for each disk
Make cache and io part was easy, but i got big trouble to change bus
Questions:
1) How we are going to change the bus? Got some issues aroud:
A) How to determine available bus? I know there is a function, but is it works with vms with different buses?
Probably, yes! But I encourage you to do as many tests as you can do.
B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
Not sure I got your question. The user will update the driver on guest/template edit. The guest/template creation keeps the same.
That's not my question. But, in this case:
1) Got a Fedora running on vda 2) Change to sda 3) Fedora will boot?
What is going to happen?
The main question is: by changing the device name, can kimchi do something to help the user to deal with this change?
The device name is a map in the running system. Kimchi or libvirt can do nothing on that area. From what I remember, the OS uses the device uuid to avoid problems with the device name as it is not guaranteed to have the same device name on boot (at least with multipath devices)
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 02/28/2017 03:52 PM, Aline Manera wrote:
On 02/28/2017 03:50 PM, Ramon Medeiros wrote:
On 02/28/2017 03:35 PM, Ramon Medeiros wrote:
On 02/28/2017 11:51 AM, Aline Manera wrote:
On 02/27/2017 03:34 PM, Ramon Medeiros wrote:
Propose: allow user to edit cache, io and bus for each disk
Make cache and io part was easy, but i got big trouble to change bus
Questions:
1) How we are going to change the bus? Got some issues aroud:
A) How to determine available bus? I know there is a function, but is it works with vms with different buses?
Probably, yes! But I encourage you to do as many tests as you can do.
B) From OS perspective? How can we deal? Only let the user choose the driver on creation, not update?
Not sure I got your question. The user will update the driver on guest/template edit. The guest/template creation keeps the same.
That's not my question. But, in this case:
1) Got a Fedora running on vda 2) Change to sda 3) Fedora will boot?
What is going to happen?
The main question is: by changing the device name, can kimchi do something to help the user to deal with this change?
The device name is a map in the running system. Kimchi or libvirt can do nothing on that area. From what I remember, the OS uses the device uuid to avoid problems with the device name as it is not guaranteed to have the same device name on boot (at least with multipath devices)
But again, do as many tests as you can and if needed, we can restrict the driver change for templates to avoid problems on VMs.
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
participants (2)
-
Aline Manera -
Ramon Medeiros