DagSonsteboSB opened a new issue #3087: XCP-ng hypervisor version issues
URL: https://github.com/apache/cloudstack/issues/3087
 
 
   ##### ISSUE TYPE
    * Improvement Request
   
   ##### COMPONENT NAME
   *XCP-ng 7.x 
   
   ~~~
   
   ##### CLOUDSTACK VERSION
   * CloudStack 4.11.x
   
   ##### CONFIGURATION
   * all
   
   
   ##### OS / ENVIRONMENT
   * N/A
   
   
   ##### SUMMARY
   * The host table uses the same version for XenServers and XCP-ng hosts
   * As a result the guest_os_hypervisor table needs to reflect the same 
hypervisor version - without distinguishing XCP-ng or Xenserver
   * Decision needs to be made whether to:
   ** Distinguish XCP-ng hosts with a different hypervisor version, OR
   ** Create a new hypervisor TYPE for XCP-ng
   * Refer to https://github.com/apache/cloudstack/issues/3086
   ** As per this ticket the hypervisor version in the host table needs to 
match the hypervisor version in the guest_os_hypervisor table to ensure the 
compute host recognises the correct Xen side template to use - which in turn 
determines PV or HVM. If the version doesn't match the fallback is an "other" 
template on Xen side, which always boots as HVM.
   * Depending on the outcome of this the existing code base in 
https://github.com/apache/cloudstack/blob/1d05fead49f5c856257a741b07122f5633d2e359/engine/schema/src/main/resources/META-INF/db/schema-41100to41110.sql
 is most likely wrong, since the existing code will simply assume as version of 
"7.4.0" rather than "XCP-ng 7.4.0". Since XenServer was already in there with a 
"7.4.0" version the XCP-ng hosts would actually use this entry rather than the 
added new entries.
   
   
   ##### STEPS TO REPRODUCE
   * N/A
   
   ##### EXPECTED RESULTS
   * No hypervisor version issues between XCP-ng and XS
   
   ##### ACTUAL RESULTS
   * N/A

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to