nasheayahu

@olivierlambert said:

Start the VM with xe vm-start uuid=<VM UUID> and see the error message there.

Thanks , I believe I found the problem:

[17:19 xcp-server1 ~]# xe vm-start uuid=4ba7c16c-f850-6001-830b-bf0f51e52a40
There are no suitable hosts to start this VM on.
The following table provides per-host reasons for why the VM could not be started:
xcp-server1    : Cannot start here [VM requires access to SR: da59d7a1-b08f-dd81-1258-65a380bd77d8 (Iso)]
There were no servers available to complete the specified operation.

I made changes to my Iso storage folder path:

from:

to:

and when I tried to start my NTP VM, because I wanted to reinstall the OS is when I get the error message:

Can you put the correct error message from the cli here instead of this generic one, because it causes far to much trouble shooting time? I knew directly where to go after seeing this part of the cli message:

The following table provides per-host reasons for why the VM could not be started:
xcp-server1    : Cannot start here [VM requires access to SR: da59d7a1-b08f-dd81-1258-65a380bd77d8 (Iso)]

Also, I can start the NTP VM without the .iso as normal. However, I did find out why I lost control of the OSs as stated above. Since the latest updates, the keyboard does not work properly. I will come back with more details later.

For now, my question is, is there a way to modify/edit the path to my Iso Storage without removing and redefining it, like you can with Cockpit, if not is/can this be a future feature added?:

@probain said:

Last time I saw that error. The resources on the host weren't enough to start the additional VM.

I believe your right, but here is the states of what was running before I started the idM and NTP VMs:

Here is the settings for the IdM (started first):

Here is the settings for the NTP (started second):

after losing control of the NTP, then I just discovered I lost control of the IdM, and my pfSenseLab console:

however, I still have control over the pfSenseLab WebGUI via Remmina,

UPDATE: but I can not (I did have ssh enable) I can ssh into the console from my Workstation:

All the other VMs still have functionality.

Afternoon, I have not started this VMs for a long while, but after login, I basically had no control of the OS, I tried "hostnamectl" and got this messages:

failed to connect to system scope bus via local transport: Connection refused?

then a moment later the OS freezes up, then I did a force-shutdown, but when trying to start it again, I get this messages:

How do I trouble shot and fix this?

Thanks!...

@Danp said:

Smart Reboot option found on the host's Advanced tab does what you are asking

Very nice!

@olivierlambert Sorry it I did not explain it well, what I wanted to know is, after a patch update, I get the message:

and I have 14 VMs running:

If I do the reboot, will XCP-ng save the State and Restore or Shutdown the VMs? I was hoping it would save the State and Restore like you can with KVM.

Question, will XCP-ng save the state of the running VMs and restart all of them (some I have Auto power on enabled) or do I have to stop them manually?

Afternoon, my session timed out and I do get the normal login page, but when I login I get this UiAlert Message:

import{B as e,C as t,St as n,U as r,X as i,_ as a,g as o,h as s,m as c,t as l,x as u,xt as d}from"./_plugin-vue_export-helper-DqPMJZfB.js";import{n as f,t as p}from"./VtsIcon-BoVekVkM.js";import{t as m}from"./use-mapper-M_HHKN3j.js";import{t as h}from"./UiButtonIcon-Df9Z1TJo.js";var g={class:`content`},_={class:`alert typo-body-regular-small`},v={key:0},y=l(t({__name:`UiAlert`,props:{accent:{},close:{type:Boolean}},emits:[`close`],setup(t,{emit:l}){let y=l,b=i(),x=m(()=>t.accent,{info:`status:info-circle`,success:`status:success-circle`,warning:`status:warning-circle`,danger:`status:danger-circle`},`info`);return(i,l)=>(e(),a(`div`,{class:n([d(f)({accent:t.accent}),`ui-alert`])},[c(`div`,g,[u(p,{class:`information-icon`,name:d(x),size:`current`},null,8,[`name`]),c(`div`,_,[c(`div`,null,[r(i.$slots,`default`,{},void 0,!0)]),b.description?(e(),a(`div`,v,[r(i.$slots,`description`,{},void 0,!0)])):o(``,!0)]),t.close?(e(),s(h,{key:0,class:`close-button`,icon:`fa:xmark`,accent:`brand`,size:`small`,onClick:l[0]||=e=>y(`close`)})):o(``,!0)])],2))}}),[[`__scopeId`,`data-v-5b9f5cdd`]]);export{y as t};

... and after back-paging, I was able to login normally.

@florent said:

where does this disk comes from

From my Redhat 10

@florent said:

if you have access to your SR from the outside, you can also put the qcow2 file directly

I create a VM to be a NFS to access the 3 HDs, the qcow disks are on the Redhat 10 that I was trying to import from. Do you mean I put the qcow disks on one of the HDs and access them when I create a VM?

@julienXOvates said:

so you're actually trying to import those QCOW2 VDIs, not creating them, right ?

Yes...

@julienXOvates said:

You'll have to wait for the import feature for QCOW2 which is coming soon.
You should be able to create a brand new SR with QCOW2, but be aware of the known issue on ZFS with large VDIs

Okay...

@julienXOvates said:

Did you install ZFS on your host ?

I installed XCP-ng using the defaults and recommended settings, I do not remember if ZFS was a default:

[09:28 xcp-kbbn ~]# df -Th
Filesystem                                                                                                Type      Size  Used Avail Use% Mounted on
devtmpfs                                                                                                  devtmpfs  3.6G   16K  3.6G   1% /dev
tmpfs                                                                                                     tmpfs     3.6G  316K  3.6G   1% /dev/shm
tmpfs                                                                                                     tmpfs     3.6G  9.3M  3.6G   1% /run
tmpfs                                                                                                     tmpfs     3.6G     0  3.6G   0% /sys/fs/cgroup
/dev/sdb1                                                                                                 ext3       18G  2.1G   15G  13% /
/dev/sdb4                                                                                                 vfat      512M  3.3M  509M   1% /boot/efi
/dev/sdb5                                                                                                 ext3      3.9G   88M  3.6G   3% /var/log
192.168.130.102:/media/KbbnNFS04/ITDocuments/ITDocuments/Iso                                              nfs       1.9T  259G  1.6T  14% /run/sr-mount/d7f0d912-ddc4-ab46-6693-39a6b0d49a14
/dev/mapper/XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4      2.6T   30G  2.5T   2% /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e
tmpfs                                                                                                     tmpfs     731M     0  731M   0% /run/user/0

[09:28 xcp-kbbn ~]# lsblk -f
NAME                                                                        FSTYPE      LABEL       UUID                                   MOUNTPOINT
sdf                                                                         LVM2_member             nl8bHb-caA4-aw3k-S1c2-rm3h-zfXc-4urbyC 
└─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e
                                                                            ext4                    9cf95f7d-249b-45e3-9584-a02f1b2a367a   /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e
sdd                                                                         xfs         KbbnNFS03   3ff0be13-df43-455f-8af5-bb5278378279   
sdb                                                                                                                                        
├─sdb4                                                                      vfat        BOOT-TZOZOJ 1B19-9FAC                              /boot/efi
├─sdb2                                                                                                                                     
├─sdb5                                                                      ext3        logs-tzozoj d09535b9-cd49-4bac-8aeb-17872bda910e   /var/log
├─sdb3                                                                      LVM2_member             0kSCqD-PNaB-0E2Q-xJ1o-rvTW-NAC0-zEzM6D 
│ └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e
                                                                            ext4                    9cf95f7d-249b-45e3-9584-a02f1b2a367a   /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e
├─sdb1                                                                      ext3        root-tzozoj 70792b7e-b92d-4913-a2cc-4ed6f8fe014e   /
└─sdb6                                                                      swap        swap-tzozoj 46d5a332-2728-452e-9c30-1e837fb6cf25   [SWAP]
tdc                                                                                                                                        
tda                                                                                                                                        
sde                                                                         LVM2_member             xRwg78-m9o1-mGki-KfO7-MSY3-gLjD-UKZjQo 
└─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e
                                                                            ext4                    9cf95f7d-249b-45e3-9584-a02f1b2a367a   /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e
sdc                                                                         xfs         KbbnNFS02   765ca566-c434-45a5-9b9f-f066c770a7d4   
sda                                                                         xfs         KbbnNFS01   a91987c0-1c2e-4e88-bcf6-fe7662e77cb6   
tdd                                                                                                                                        
tdb    

but you can see sd(a,d,c) are from the 3 HDs I did not include in the install are ZFS, I attached them as SRs so I can move the data later to a Storage Device using the methods by your help from Attach a Physical HD to a VM?.

Both systems (well be converting the other one later) are Redhat 10s formatted with ZFS, and was importing from the other Redhat. Will this be and/or the reason for the import failure?

@julienXOvates said:

1/ are you running the latest XO from source ?

Yes, I used the Xen Orchestra Installer / Updater on a Debian 13.

@julienXOvates said:

2/ did you follow this to create the ZFS volume => https://docs.xcp-ng.org/storage/#zfs ?

No, I have 3 extra 2TB HDs I did not include in the install, because I have data on them I want to move to a Storage Device first.

@julienXOvates said:

3/ did you try with "ext" type instead ? or your requirement is QCOW2 with ZFS ?

I just tried it, but it requires an another device I don't have available as stated above. The QCOWS are coming from the two Redhat 10 Server/Workstations, 1) I just converted to XCO-ng, 2) the other Redhat will convert soon after solving other setup tasks with the first.