Hello

So i watched @lawrencesystems video of Xen and KVM difference inspired by a write up from @olivierlambert. Great video by the way. On a personnel not i still feel its silly that some people are go beyond fanboy-ism for lack of a better phrase that one is better than the other. I think Jay for Learn Linux put it best when he said that if one was better than the other we would all use that. But in the real world its as most things are depends on your use case and preferences. Me i wanted to learn something different and use a different interface. XCP-ng just began to fit my use case more and more specifically the many to one relationship of XenOrchestra.

Long story short Yes i love XCP-ng but im not going to force using it down someones throught if it doesn't fit there use case or if they don't want to use it. Thats whats great about opensource if you want KVM go for it i wont stop you if you want to use Xen go ahead. But please lets just be kind and support one another we all a community driving the software and whole industry forward.

@abufrejoval Hello with regard to the warning of proprietary code in xen server I believe that is only if you want to use VGPU on NVIDIA cards. What im talking about is pure pcie pass-through. What im focused on i better support for pcie pass-through of say usb or network card. and let it be esaly stubbed and then assigned to vms in XO. With regard to the k80 im using it not just for gaming but gpu accelerated containers and Kubernetes

Hello

I was finally been able to get cloud-init working. But i have a question that i can seem to find and answer to

Must the cloud config drive be permanently attached to the VM to preserve Network configurations? As my custom template applies the network config but when i remove the drive it defaults back to DHCP

Ive removed removed the network configurations in the /etc/network/interfaces file except for the eth0 hotplug and well as details in the hosts file

This is my cloud config

#Cloud-config
users:
   - default

disable_root: true

#Set hostname
preserve_hostname: false
hostname: debian-localhost
manage_resolv_conf: true
manage_etc_hosts: true
apt_preserve_sources_list: true

cloud_init_modules:
 - migrator
 - seed_random
 - bootcmd
 - write-files
 - growpart
 - resizefs
 - disk_setup
 - mounts
 - set_hostname
 - update_hostname
 - update_etc_hosts
 - ca-certs
 - rsyslog
 - users-groups
 - ssh

cloud_config_modules:
 - emit_upstart
 - ssh-import-id
 - locale
 - set-passwords
 - grub-dpkg
 - apt-pipelining
 - apt-configure
 - ntp
 - timezone
 - disable-ec2-metadata
 - runcmd
 - byobu

cloud_final_modules:
 - package-update-upgrade-install
 - fan
 - puppet
 - chef
 - salt-minion
 - mcollective
 - rightscale_userdata
 - scripts-vendor
 - scripts-per-once
 - scripts-per-boot
 - scripts-per-instance
 - scripts-user
 - ssh-authkey-fingerprints
 - keys-to-console
 - phone-home
 - final-message
 - power-state-change

#Install packages
package_update: true
package_upgrade: true
packages:
 - curl
 - sudo
 - unattended-upgrades
 - open-iscsi
 - nfs-common
 - cifs-utils
 - htop
 - net-tools
 - nftables
 - fail2ban
 - unzip
 - rsyslog

#Set date of server creation
bootcmd:
 - date > /etc/birth_certificate

datasource_list: [ NoCloud, None ]
datasource:
    NoCloud:
        fs_label: cidata

system_info:
   distro: debian
   default_user:
     name: serveradmin
     lock_passwd: True
     gecos: serveradmin
     groups: [adm, audio, cdrom, dialout, dip, floppy, netdev, plugdev, sudo, video]
     sudo: ["ALL=(ALL) NOPASSWD:ALL"]
     shell: /bin/bash
     ssh_authorized_keys:
      - ssh-rsa xxxxxxxx
   paths:
      cloud_dir: /var/lib/cloud/
      templates_dir: /etc/cloud/templates/
      upstart_dir: /etc/init/
   package_mirrors:
     - arches: [default]
       failsafe:
         primary: http://deb.debian.org/debian
         security: http://security.debian.org/
   ssh_svcname: ssh

this is my 99-fake_cloud.cfg

# configure cloud-init for NoCloud
datasource_list: [ NoCloud, None ]
datasource:
    NoCloud:
        fs_label: cidata

Im using Debain 11.7

Any ideas.

thanks

@olivierlambert

Roger Roger

@olivierlambert

Conversion in Xen orchestra works with the clone of the VM and the guest iso installed

@olivierlambert Morning i will clone the same VM and try to conversion with an iso installed.

Will update this post in the next few hours

Hello

Ive created a VM that Im converting to a template in Xen Orchestra (xo-server 5.113.0) but i get the following error.

The storage of the vm disk is an nfs share from TrueNAS scale mounted to a 3 node XCP-ng 8.2 cluster

I will note that i can convert to template in XCP-ng Center with no error.

My logs for the error is as follows

vm.convertToTemplate
{
  "id": "e6b3db34-f90f-5a9d-16cf-aeaeaf27c55c"
}
{
  "code": "VBD_IS_EMPTY",
  "params": [
    "OpaqueRef:713ee863-59c8-464e-b9d3-2a5371c76c70"
  ],
  "task": {
    "uuid": "ce2df32b-d7d6-ff50-f484-78e51d81fde7",
    "name_label": "Async.VBD.eject",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20230502T09:29:59Z",
    "finished": "20230502T09:29:59Z",
    "status": "failure",
    "resident_on": "OpaqueRef:b2fad3ee-05d6-474b-a3ec-47534ffb3627",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "VBD_IS_EMPTY",
      "OpaqueRef:713ee863-59c8-464e-b9d3-2a5371c76c70"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vbd_helpers.ml)(line 308))((process xapi)(filename ocaml/xapi/xapi_vbd_helpers.ml)(line 317))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 5190))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 199))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 203))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 233))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 104)))"
  },
  "message": "VBD_IS_EMPTY(OpaqueRef:713ee863-59c8-464e-b9d3-2a5371c76c70)",
  "name": "XapiError",
  "stack": "XapiError: VBD_IS_EMPTY(OpaqueRef:713ee863-59c8-464e-b9d3-2a5371c76c70)
    at Function.wrap (/home/serveradmin/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)
    at _default (/home/serveradmin/xen-orchestra/packages/xen-api/src/_getTaskResult.js:11:29)
    at Xapi._addRecordToCache (/home/serveradmin/xen-orchestra/packages/xen-api/src/index.js:998:37)
    at forEach (/home/serveradmin/xen-orchestra/packages/xen-api/src/index.js:1032:14)
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (/home/serveradmin/xen-orchestra/packages/xen-api/src/index.js:1022:12)
    at Xapi._watchEvents (/home/serveradmin/xen-orchestra/packages/xen-api/src/index.js:1195:14)"
}

@fred974

also see if this script is available on the last host that has the controller which we can assume is the host that failed the first time. Maybe it has some data on why the controller isn't initializing

@fred974

Maybe also post in the XOSTOR thread
A controller failure should be on the radar for possible failure scenarios.
https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview

@fred974

ok so thats our problem the lunstor controller is not running on any node so XOSTOR has no way to initialize. Im going to do some reading and see what comes up

@fred974

So we know its not running to that host as the command is targeting a single hosts uuid.

have you run it on all your XCP-ng servers to confirm if the controller is running on any of them. perhaps check to make sure the lunstor controller is available on any host

@fred974 it looks like the logs say it cant find the controller can you confirm if it is running on any of your hosts.

im no expert but its a start