[GitHub] dpassante opened a new issue #2760: SystemVMs running in Xen HVM mode are not configured

[GitBox <gi...@apache.org>]

dpassante opened a new issue #2760: SystemVMs running in Xen HVM mode are not configured
URL: https://github.com/apache/cloudstack/issues/2760
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   systemVM image 4.11 for XenServer
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.11.1
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   * Cloudstack 4.11.1
   * XenServer 7.1.1
   * SystemVM 4.11.1 Fri Jun 22 07:52:17 UTC 2018 running in HVM mode
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   N/A
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Newly created system VMs are not configured.
   
   Related to #2561 
   
   virt-what cpuid helper detects Xen HVM guests with viridian extension enabled as hyperV guests.
   
   ~~~bash
   root@v-2158-VM:~# /usr/lib/x86_64-linux-gnu/virt-what-cpuid-helper
   Microsoft Hv
   ~~~
   
   So, virt-what returns the following on Xen HVM SystemVMs:
   
   ~~~bash
   root@v-2158-VM:~# virt-what
   hyperv
   xen
   xen-domU
   ~~~
   
   In this case, the ```/opt/cloud/bin/setup/cloud-early-config``` script assumes that we're running on a paravirtualized guest and fails to get boot args.
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   hypervisor: xen-hvm
   systemvm type: should be detected.
   
   ~~~
   Sun Jul 22 03:18:28 UTC 2018 Executing cloud-early-config
   Sun Jul 22 03:18:28 UTC 2018 Detected that we are running inside xen-hvm
   Sun Jul 22 03:18:28 UTC 2018 Scripts checksum detected: oldmd5=76c6bbddfc1d55d1b212ad8ca07190d4 newmd5=76c6bbddfc1d55d1b212ad8ca07190d4
   Sun Jul 22 03:18:28 UTC 2018 Configuring systemvm type=consoleproxy
   Sun Jul 22 03:18:29 UTC 2018 Setting up console proxy system vm
   ...
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   hypervisor: xen-domU
   systemvm type : empty
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   root@systemvm:~# cat /var/log/cloud.log
   Fri Jul 20 12:55:19 UTC 2018 Executing cloud-early-config
   Fri Jul 20 12:55:19 UTC 2018 Detected that we are running inside xen-domU
   Fri Jul 20 12:55:19 UTC 2018 Scripts checksum detected: oldmd5=76c6bbddfc1d55d1b212ad8ca07190d4 newmd5=76c6bbddfc1d55d1b212ad8ca07190d4
   Fri Jul 20 12:55:19 UTC 2018 Configuring systemvm type=
   Fri Jul 20 12:55:19 UTC 2018 Finished setting up systemvm
   ~~~
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services