Categories

  • All news regarding Xen and XCP-ng ecosystem

    141 Topics
    4k Posts
    P
    @Thiago_FS_Dantas hi, did you check NESTED VIRTUALISATION in the advanced tab of your VM ? [image: 1767872120619-3f93e473-b1eb-4a92-aca7-a684ff9a23ae-112fdd1c-a3bf-4636-81a9-f24aecd818f7.png]
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    R
    @andSmv I definitely think it would be nice with support even though i repurposed my M2 Coral for other uses. But one thing to keep in mind regarding resources is that the product would appear to be heading to https://killedbygoogle.com coral.ai redirects to their new NPU offering and no updates have been made from google to the driver since 2022... Mouser still has plenty of stock though. Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either.
  • 3k Topics
    27k Posts
    cbaguzmanC
    Hello @olivierlambert, @bastien-nollet, Hello Everyone !! I used vhd-cli with its new arguments and it worked ok. vhd-cli check --chain 'file:///run/xo-server/mounts/11934fec-f3a1-4f7f-a78d-00eeb1b39654?useVhdDirectory=true&encryptionKey=%22O1xt1ZTRE%5Qq%3X%3D1NZ%26%3ZZQo8%2DD%29s5xt%3OOko%22' 'xo-vm-backups/abc3e130-923e-619e-4fdc-59bcda088586/vdis/cecc4489-722a-4f79-b5e6-c050f63f2761/d489173c-028a-46f0-b712-f4a7c5594c8f/20260108T160552Z.alias.vhd' ok: xo-vm-backups/abc3e130-923e-619e-4fdc-59bcda088586/vdis/cecc4489-722a-4f79-b5e6-c050f63f2761/d489173c-028a-46f0-b712-f4a7c5594c8f/20260108T160552Z.alias.vhd But I discovered that using vhd-cli in this way only checks the physical structure of the alias.vhd file. It doesn't check the integrity of the blocks or the total number of blocks to detect a missing block. (It doesn't work like it does with huge monolithic .vhd files, where it detects errors with the slightest modification.) So I opted to split the solution: I check the integrity of the filesystem where the files are stored (using btrfs scrub). I verify that the number of blocks written in the backup is correct (that no blocks are missing). I verify that the written blocks haven't been modified since they were written. For point 2, I found (AI) that I could use "vhd-cli info" to find out the total number of blocks in the backup (I don't have much information about it), but when I run it, I get the following error. I suspect it doesn't work with (Encrypt all new data sent to this remote): vhd-cli info --chain 'file:///run/xo-server/mounts/11934fec-f3a1-4f7f-a78d-00eeb1b39654?useVhdDirectory=true&encryptionKey=%22O1xt1ZTRE%5Qq%3X%3D1NZ%26%3ZZQo8%2DD%29s5xt%3OOko%22' 'xo-vm-backups/abc3e130-923e-619e-4fdc-59bcda088586/vdis/cecc4489-722a-4f79-b5e 6-c050f63f2761/d489173c-028a-46f0-b712-f4a7c5594c8f/20260108T160552Z.alias.vhd' ✖ Unhandled remote type Error: Unhandled remote type at getHandler (/usr/lib/node_modules/vhd-cli/node_modules/@xen-orchestra/fs/dist/index.js:48:11) at getSyncedHandler (/usr/lib/node_modules/vhd-cli/node_modules/@xen-orchestra/fs/dist/index.js:54:19) at Object.info (/usr/lib/node_modules/vhd-cli/commands/info.js:98:24) at Object.runCommand (/usr/lib/node_modules/vhd-cli/index.js:32:13) at /usr/lib/node_modules/vhd-cli/node_modules/exec-promise/index.js:57:13 at new Promise (<anonymous>) at execPromise (/usr/lib/node_modules/vhd-cli/node_modules/exec-promise/index.js:56:10) at Object.<anonymous> (/usr/lib/node_modules/vhd-cli/index.js:41:1) at Module._compile (node:internal/modules/cjs/loader:1706:14) at Object..js (node:internal/modules/cjs/loader:1839:10) Could you please help me with this? I'm not sure if I'm on the right track. Perhaps there are other ways I'm missing.
  • Our hyperconverged storage solution

    39 Topics
    705 Posts
    I
    @Pilow does SR.scan checks only keep-alive or do any kind of write operation or anything else? cc: @nikade @olivierlambert
  • 31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related