-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Milestone
Description
ISSUE TYPE
- Bug Report
COMPONENT NAME
systemVM image 4.11 for XenServer
CLOUDSTACK VERSION
4.11.1
CONFIGURATION
- 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
N/A
SUMMARY
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.
root@v-2158-VM:~# /usr/lib/x86_64-linux-gnu/virt-what-cpuid-helper
Microsoft HvSo, virt-what returns the following on Xen HVM SystemVMs:
root@v-2158-VM:~# virt-what
hyperv
xen
xen-domUIn 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
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
hypervisor: xen-domU
systemvm type : empty
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
khos2ow and yadvr
Metadata
Metadata
Assignees
Labels
No labels