If it's possible to over-subscribe vCPU's: What do vCPU's really represent - A weighted average of CPU cycles that will be allocated to the guest?
e.g., If a host has eight CPU cores with hyperthreading enabled and all four guests are allocated 16 vCPU's: What benefit will the four guests see over what they would experience if they had each been allocated 2 vCPU's?
TIA,
Eric Pretorious
Reno, Nevada
@olivierlambert Refreshing the status log and updating a second time retrieves/installs more updates.
After that: The '+ New' menu button appears in the menu on the left side of the window!
Thank you!
Eric P.
Reno, Nevada
What does @tjkreidl have to say about bootstrapping an HVM guest using only XAPI on the CLI?
Eric P.
Reno, Nevada
@olivierlambert said in Creating a VM using only the XAPI CLI...:
You'll need a better client to do that.
I don't understand. Would you please elaborate?
TIA,
Eric P.
Reno, Nevada
@olivierlambert Is there any way to bootstrap an HVM guest using only XAPI on the CLI?
TIA,
Eric P.
Reno, Nevada
If it's possible to over-subscribe vCPU's: What do vCPU's really represent - A weighted average of CPU cycles that will be allocated to the guest?
e.g., If a host has eight CPU cores with hyperthreading enabled and all four guests are allocated 16 vCPU's: What benefit will the four guests see over what they would experience if they had each been allocated 2 vCPU's?
TIA,
Eric Pretorious
Reno, Nevada
@olivierlambert Thanks. But I'm not looking for the most current method of installing a guest - I'm looking for the simplest method of installing a guest using XAPI on the command-line interface (CLI).
The "Citrix XenServer 7.2 Virtual Machine User's Guide" includes a method to do that using the CLI:
xe vm-install template=<template> new-name-label=<name_for_vm> sr-uuid=<storage_repository_uuid>
xe vif-create vm-uuid=<vm_uuid> network-uuid=<network_uuid> mac=random device=0
xe vm-param-set uuid=<vm_uuid> other-config:install-repository=<network_repository>
xe vm-start uuid=<vm_uuid>
But obviously it's missing something!
Have you got any suggestions about what might be missing from those four simple steps?
TIA,
Eric P.
Reno, Nevada
@olivierlambert I don't understand. Would you please elaborate?
TIA,
Eric P.
Reno, Nevada
FWIW: These are the contents of the remote package repository (nfs://192.168.0.95/srv/pkgs/ISO)
# mount -t nfs 192.168.0.95:/srv/pkgs/ISO /mnt
# ll /mnt
total 110
-rw-rw-r-- 1 root root 14 Sep 9 2019 CentOS_BuildTag
drwxr-xr-x 3 root root 2048 Sep 6 2019 EFI
-rw-rw-r-- 1 root root 227 Aug 30 2017 EULA
-rw-rw-r-- 1 root root 18009 Dec 9 2015 GPL
drwxr-xr-x 3 root root 2048 Sep 9 2019 images
drwxr-xr-x 2 root root 2048 Sep 9 2019 isolinux
drwxr-xr-x 2 root root 2048 Sep 6 2019 LiveOS
drwxrwxr-x 2 root root 73728 Sep 11 2019 Packages
drwxrwxr-x 2 root root 4096 Sep 11 2019 repodata
-rw-rw-r-- 1 root root 1690 Dec 9 2015 RPM-GPG-KEY-CentOS-7
-rw-rw-r-- 1 root root 1690 Dec 9 2015 RPM-GPG-KEY-CentOS-Testing-7
-r--r--r-- 1 root root 2883 Sep 11 2019 TRANS.TBL
HTH,
Eric P.
Reno, Nevada
FWIW: The result seems to be the same whether I use an ISO image on a remote NFS server (nfs://192.168.0.95/srv/images/ISO/CentOS-7.7-x86_64-Minimal.iso) or I use a remote package repository (nfs://192.168.0.95/srv/pkgs/ISO) for installation:
# VM_UUID=$(xe vm-install template=CentOS\ 7 new-name-label=CentOS7-2)
# echo $VM_UUID
c9c66b15-e618-dc12-0f93-8e39af102c8b
# VIF_UUID=$(xe vif-create mac=random device=0 vm-uuid=$VM_UUID network-uuid=$NET_UUID)
# echo $VIF_UUID
de6b51ec-54ed-fa0c-0ba2-7da732e8fa05
# xe vm-param-set uuid=$VM_UUID other-config:install-repository=nfs://192.168.0.95/srv/pkgs/ISO
# xe vm-start uuid=$VM_UUID
# xe console uuid=$VM_UUID
No text console available
# xe vm-param-list uuid=$VM_UUID | grep dom-id
dom-id ( RO): 8
# xenstore-ls /local/domain/8
xenstore-ls: xs_directory (/local/domain/8): No such file or directory
What am I doing wrong?
TIA,
Eric P.
Reno, Nevada
I'm attempting to create a CentOS-7 VM from the CLI using modified instructions from the "Citrix XenServer 7.2 Virtual Machine User's Guide":
# NET_UUID=$(xe network-list bridge=xenbr0 params=uuid | awk '{ print $5 }')
# echo $NET_UUID
47a6223e-74d0-b75d-bec3-0ca6324b498c
# VM_UUID=$(xe vm-install template=CentOS\ 7 new-name-label=CentOS7-1)
# echo $VM_UUID
26859adf-f2f9-77d6-3f3c-719ecd885535
# VIF_UUID=$(xe vif-create mac=random device=0 vm-uuid=$VM_UUID network-uuid=$NET_UUID)
# echo $VIF_UUID
decb158e-2961-7448-8b7c-4c2707298604
# xe vm-param-set uuid=$VM_UUID other-config:install-repository=nfs://192.168.0.95/srv/images/ISO/CentOS-7.7-x86_64-Minimal.iso
# xe vm-start uuid=$VM_UUID
But when I use the console command in order to complete the installation of the operating system: I get this...
# xe console uuid=$VM_UUID
No text console available
And when I search Xenstore for the VNC-port information I get this:
# xe vm-param-list uuid=$VM_UUID | grep dom-id
dom-id ( RO): -1
What have I done wrong? How can I determine the root cause of the failure?
TIA,
Eric Pretorious
Reno, Nevada