Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    A
    @semarie sorry for the delay. @semarie said: your /var/log/sdn-controller-plugin.log file (on the host) in order to check the parameter passed by XO. MASTER_sdn-controller-plugin.txt @semarie said: output of xe network-param-list uuid=$UUID (for the network concerned) or xe network-list params=all (if uuid is unknown) uuid ( RO) : 250cec4e-d7af-23c5-be1c-391186bde2f4 name-label ( RW): VLAN VDI INT - 102 name-description ( RW): VLAN Rede VDI Interna VMs VIF-uuids (SRO): 9f23be5a-a6f5-f64d-e004-4a432aded733; b9f85e54-cfd0-6546-edac-ba1573f00bc5; 16bfa5e3-4022-7c9e-ef43-735599b9b5f2; 418fc7cb-ab9c-23db-8bad-7854cb16cbcb; b9dfc5b9-560e-38ac-941a-f744b0d741d8; af16b830-1d31-c664-d70c-a6d1c7ce3056; 3596ec8a-d0ee-2468-d6ae-16b66c745d03; 181808cf-1c42-ddcb-13b5-3bf5f4483a3f; 0c576952-b1f1-95db-1a7e-fc8f581a46e3; b2b8da93-f07f-32a4-1ae1-ae2eac13da08; 9c96d442-e782-774a-ac98-858fcce36607; f512706b-f1a3-767d-6941-ed0f6c926291; c5f2e0b1-a8d2-4846-521a-54b790d6d849; 82b9789c-cf69-6382-e6cc-95ef67b0ba2e; 967ecb88-a141-cd17-c45f-9f5a779efbca; 7445be42-7b30-7a61-f3a1-6aadb725be6a; aa2e03aa-dc9c-aff3-d8cb-5c652af62958; dd596564-a3b4-e15f-69cf-2af5d128a8c2; 767a2bae-8ff0-45fd-339f-56a955ed1ada; e5c85ad8-4bc1-f8b6-6c31-ca6f48604920; d30dfed6-ba5c-04f8-bbc6-ddc18414737e; cddb92fd-da90-cce1-620c-c31469dccada; da4421fa-0bb5-525b-544e-f03e6fbce04b; 947932f8-4bf6-204f-d112-0b251ac4abae; b5bdddd6-2908-ec1f-4a2d-a2b12cf36ee8; 0601ff52-51c9-72de-7dba-071d016473fd; 49739db0-2055-9a4b-fe22-027f5b7ceac0; e0e7fa88-1d3c-05f3-1cc9-cf6e08aa8294; 82b7a17e-2164-caec-90ba-2640a737897b; bda96371-0222-2919-d128-94f1e118a411; ca3e3dee-40da-b1c3-77ce-9b4640511151; 8241bab2-ab2a-228e-24ca-914a80d1cacc PIF-uuids (SRO): fef83dfe-5a02-50b6-12a3-0fed1189acaf; de48ed20-e0d2-ab4d-c2b3-7857110e0f6a; 4014506f-75ff-800b-3bde-d49196f39bf7; 29d6c11e-d149-b54a-6cf5-d41af778cd50; c064f9cb-018d-d5a3-12d1-29a6050118d8; 4dffbd1d-2bcb-1d85-b029-1bc4366ef4ad; f81b260a-88ed-2c7f-b87d-ea1bcb830e69; 5deeb719-799b-2752-a1dd-5788b94c0f21; 5d7761a3-8ebd-fb60-8568-6a7129bef180; 74943f3a-bacc-bfb3-3efa-b66423fa0604; c4b64326-3c78-c7ac-0535-22aa0e2b0e62; d2f68f7a-a32a-f84d-9162-71f18d7b35ec MTU ( RW): 1500 bridge ( RO): xapi3 managed ( RO): true other-config (MRW): xo:sdn-controller:of-rules: ["{"allow":true,"protocol":"IP","ipRange":"172.22.146.126/32","direction":"from/to","cookie":"0xd3d2533ed26a8151"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.119/32","direction":"from/to","cookie":"0xa9b47fab93762ad1"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.120/30","direction":"from/to","cookie":"0x20b7928056a3e208"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.124/32","direction":"from/to","cookie":"0x67d0c4dc2d9fd8a9"}","{"allow":false,"protocol":"IP","ipRange":"0.0.0.0/0","direction":"from/to","cookie":"0xd191b1374733bc1a"}"]; automatic: false blobs ( RO): tags (SRW): default-locking-mode ( RW): unlocked purpose (SRW): @semarie said: output of xe pool-list params=other-config (for xo:sdn-controller:* elements) xo:sdn-controller:of-method: xapi-plugin; xo:sdn-controller:of-format: xapi-plugin; auto_poweron: true; @semarie said: output of xe vif-list params=uuid,network-uuid,other-config (for xo:sdn-controller:* elements) this output is pointless because our current rules are on network, not on VIF anymore.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    Then, my earlier suggestion about upgrading was wrong, sorry, better to say so before you spend an evening on it. I went and read the RPU code (it's about time!): shutdownPinnedVms only handles VM_HAS_PCI_ATTACHED, VM_HAS_VGPU and VM_HAS_SRIOV_VIF, and when anything else turns up, it hands back to XAPI's CANNOT_EVACUATE_HOST on purpose. VM_REQUIRES_SR is not in that list, so an upgrade will not move you past it. On the Rolling Pool Update side, the docs say all VM disks have to be on shared storage (https://docs.xcp-ng.org/management/updates), and the host reboot guide defines an agile VM as one not tied to local storage or local devices (https://docs.xcp-ng.org/guides/host-reboot). With everything on local NVMe, that reads to me like RPU is closed to you by design rather than by bug. The route the docs give for your case is the manual one: disable the host, shut the VMs down or migrate them, then reboot. The Smart Reboot message looks like a separate problem. In XO's smartReboot a VM counts as suspend blocked in two different cases, either when blocked_operations.suspend is set, or when XAPI itself refuses VM.assert_operation_valid for suspend. The message only describes the first, which might be why clearing the protection changed nothing. These two will show which one you are in: xe vm-list is-control-domain=false params=name-label,blocked-operations xe vm-list is-control-domain=false power-state=running params=name-label,allowed-operations If suspend is missing from allowed-operations, then XAPI is refusing it rather than a flag you set. I ran both on 8.3, so I know they print something per VM. I have not tested any of this on a two-host pool, though, so the VM_REQUIRES_SR part is my reading of the code rather than something I reproduced.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    olivierlambertO
    Question for @Team-XO-Backend

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    135 Posts
    AtaxyaNetworkA
    Pour l'ISO montée deux fois : My bad, j'ai ajouter un truc en trop sur mon précédent fix. Une PR est en cours pour corriger ça. Pour le problème principal : J'ai identifié la cause, mais je n'ai pas encore de solution. Sans les drivers Xen (non initialisés avant l'installation), une VM est limitée à 4 périphériques. La séquence de boot ne peut donc pas détecter le second disque contenant le fichier Kickstart (ks). Côté Packer, on semble être bloqués par cette contrainte XCP-ng. Les seules alternatives actuelles seraient de se limiter à : 2 disques + 2 CD ou 3 disques + 1 CD + HTTP (Note : L'installation manuelle fonctionne car l'installateur démarre directement, avec le driver xen_blkfront, alors qu'avec Packer, l'injection de notre fichier interrompt le flux de démarrage classique). Je vais fouiller encore un peu, mais sans certitude d'un contournement possible. (et je regarde pour ajouter le CDlabel)