@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.

@dthenot said:

you will also likely need to give the host-uuid of the host the disk is on

Thanks, and I'm assuming this UUID or Machine ID from:

[14:45 xcp-kbbn NAS]# dmidecode --type SYSTEM
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
# SMBIOS implementations newer than version 3.0 are not
# fully supported by this version of dmidecode.

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: ASUS
        Product Name: System Product Name
        Version: System Version
        Serial Number: System Serial Number
        UUID: E7AE9723-CB08-A278-5C45-7C10C9473BD0
        Wake-up Type: Power Switch
        SKU Number: SKU
        Family: To be filled by O.E.M.

OR

[12:46 xcp-kbbn NAS]# hostnamectl
   Static hostname: xcp-kbbn
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: c668f529e66c42b9815fe12f3401df82
           Boot ID: dd70b200b25341c688aee9fbc58d20a2
    Virtualization: xen
  Operating System: XCP-ng 8.3
            Kernel: Linux 4.19.0+1
      Architecture: x86-64

the command would look like this correct:

xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0 or c668f529e66c42b9815fe12f3401df82

UPDATE: I tried the new command but I got these error messages:

[14:45 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0
The uuid you supplied was invalid.
type: host
uuid: E7AE9723-CB08-A278-5C45-7C10C9473BD0
[15:14 xcp-kbbn NAS]# ls
[15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=c668f529e66c42b9815fe12f3401df82
The uuid you supplied was invalid.
type: host
uuid: c668f529e66c42b9815fe12f3401df82

then I was successful (I believe with you confirmation) when I left our the host-uuid param:

[15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks"
b802722e-67ac-5aba-8d6c-e565d2d7fa0d

and then it was listed as a SR:

now to the next task command:

xe sr-scan uuid=b802722e-67ac-5aba-8d6c-e565d2d7fa0d

was successful, but I have another Question, the size of the device is not showing, is this normal being that it was done this way?

UPDATE 2.0: I just discovered the xe command:

[15:27 xcp-kbbn NAS]# xe host-list
uuid ( RO)                : 9a5e5bb3-bdb9-41ea-9505-6f6fe630f369
          name-label ( RW): xcp-kbbn

the uuid does not match the ones provided above, do I need to remove the SR and do it over again using this uuid? I will give it a try using another folder....

UPDATE 2.1: I executed the command using the above uuid:

[15:35 xcp-kbbn srv]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369
6fc531a0-19a0-b9c1-c78e-c687fce5ff84

and was successful, but now my question for the device size, is it normal or not due to creating it this way?

UPDATE 2.2: I forgot to do:

ln -s /dev/sda /srv/NAS/sda #although it might be better to use a stable identifier if you have multiple disks
xe sr-scan uuid=<UUID of the udev SR>

be right back.....

UPDATE 3.0: Success, I have all HDs attached to my VM, access all files and the sizes are reported! :

List of attached disks:

The VM:

Thanks for your help!...

@dthenot

UPDATE: I get this error -

[11:03 xcp-kbbn NAS]# xe sr-create type=udev sm-config:location=/srv/NAS name-label="NAS Disks"
Error code: SR_BACKEND_FAILURE_94
Error parameters: , The request is missing the location parameter, 

I inquired help on the command,

Command name            : sr-create
        reqd params     : name-label, type
        optional params : host-uuid, device-config:, shared, physical-size, content-type, sm-config:
        description     : Create an SR, also a PBD. the device-config parameters can be specified by e.g. device-config:foo=baa.

..but I don't understand how to properly execute this to accomplish the task... There must or have a hidden character in the command that causing the error? I copy/pasted your command in Kate to remove any special char's, but I still the error...

Evening, my setting to create a SR for importing my .qcow2 is:

but when I try to create the SR I get this:

I hover over the (i) for the information for the preferred type:

I've read this QCOW2 FAQ, so my question is, if I have to install this on the host, where is the instruction or the plug-in for this feature?

I attempted to import my .qcow2 in the Default SR:

For a moment is appears to be importing:

Then I get this error message:

I try to import it again and I get his error message:

After this is when I attempted to create the qcow2 SR. My XOA is located on my Redhat 10 Server/Workstation as a VM.

Thanks!...

Afternoon, I converted my Red hat 10 desktop server/workstation to the XCP-ng, it had:

• 1x NVMe SSD 1TB (XCP-ng default install + VMs)
• 2x SSD 1TB (SR for VMs)
• 3x WD 2TB (It was used for storage via NFS)

I want to create a NSF VM to manage those WD 2TB HDs. I'm assuming it possible, any cons doing it this would be welcome, I can not find instructions how to attach a drive to a VM in the XCP-ng docs. I don't want to destroy the data on these drives until I get a storage device to transfer them too.

The need to do it this way for now is, I don't have the equipment to setup a full blown network infrastructure. So I want to simulate one until I do. The purpose is to learn and master XCP-ng and Networking. The VMs will be simulating servers, so when I get all the needed equipment, I would know how to setup my network infrastructure.

I have another Redhat 10 server/workstation setup similar and will convert this one a well. It has:

• 1x NVMe SSD 1TB (default install for XCP-ng + VMs)
• 2x SSD 500GB (for VMs)
• 2x ST 2TB (used for storage as well, currently uploading to cloud storage to use for VMs as well)

I will be managing both XCP-ng severs from another workstation (Windows 10 Pro).

Thanks for your feedback!

Evening, I've created a five NIC Bond, 4 from the card, 1 from the intergraded board. Need to remove the intergraded to use for another project. I can not find where you can edit the settings or this has to be done cli and if so do you a guide showing how to do this?

I hoping I don't have to delete the bond and recreate it?

@olivierlambert said in XCP-ng - mount.nfs: access denied by server while mounting:

Can you show the incorrect and the correct config used to make it even more clear?

openSUSE 15.4 NFS Setup:

Permission for /run/media/XCP-ng/WebServer/Production (Note: this is a mounted internal HD)

drwxrwxr-x 2 root nobody 4096 Jul 22 21:38 Production

Folder settings in /etc/export

/run/media/XCP-ng/WebServer/Production 10.60.70.0/24(rw,root_squash,sync,no_subtree_check) 10.70.70.0/24(rw,root_squash,sync,no_subtree_check)

To make sure the proper NFS RPC-based services are enabled for rpcbind, use the following

command: sudo rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  55952  status
    100024    1   tcp  43101  status
    100005    1   udp  20048  mountd
    100005    1   tcp  20048  mountd
    100005    2   udp  20048  mountd
    100005    2   tcp  20048  mountd
    100005    3   udp  20048  mountd
    100005    3   tcp  20048  mountd
    100003    3   tcp   2049  nfs
    100227    3   tcp   2049  nfs_acl
    100003    3   udp   2049  nfs
    100227    3   udp   2049  nfs_acl
    100021    1   udp  57533  nlockmgr
    100021    3   udp  57533  nlockmgr
    100021    4   udp  57533  nlockmgr
    100021    1   tcp  39073  nlockmgr
    100021    3   tcp  39073  nlockmgr
    100021    4   tcp  39073  nlockmgr

If one of the NFS services does not start up correctly, rpcbind will be unable to map RPC requests from clients for that service to the correct port.

To allow clients to access NFS shares behind a firewall, configure the firewall by running the following commands on the NFS server:

firewall-cmd --permanent --add-service mountd
firewall-cmd --permanent --add-service rpc-bind
firewall-cmd --permanent --add-service nfs
firewall-cmd --permanent --add-port=<mountd-port>/tcp
firewall-cmd --permanent --add-port=<mountd-port>/udp
firewall-cmd --reload

Note: I used firewall-config to do the port settings.

XCP-ng / Remote Settings:

New file system remote
Type

• NFS
• Backup Production Wev Servers
• ..
• 10.60.70.15
• leave port empty
• /run/media/XCP-ng/WebServer/Production
• ..

Note: Make sure you can do this on both systems

[19:48 xcp-pro ~]# showmount --exports 10.60.70.15
Export list for 10.60.70.15:
..
...
/run/media/XCP-ng/WebServer/Production  10.70.70.0/24,10.60.70.0/24
...
..
.

@olivierlambert said in XCP-ng - mount.nfs: access denied by server while mounting:

Thanks for the feedback!

For sure, anytime to help make XCP-ng the best!

This is a new discovery during the Solved "NFS ISO: Cannot read property 'Export' of undefined" in creating a NFS Remote for backups.

Since I'm using openSUSE Leap 15.4 as a SR and Backups, I posted on there forum "XCP-ng - mount.nfs: access denied by server while mounting" first to get the solution and it was solved moments later, and to my delight it was a very simple fix, so I'm posting here just in case anyone else has this problem.

Leap was denying access for XCP-ng backup test, everything on Leap was configured correctly, but I had to remove the Port number on the XCP-ng Remote setting and now it works.

@olivierlambert said in NFS ISO: Cannot read property 'Export' of undefined:

Let's consider this thread fixed by adding the correct NFS configuration on the server side and create a new one describing your issue.

@ravenet said in Manually Mount A HD When Needed From XCP-ng?:

You can script mount and umount commands as part of jobs or as part of backup jobs.

Hang on, the recent post deals with Settings / Remotes, got off track by watching "Tutorial: Configuring Backups For XCP NG Using Xen Orchestra 2021" but, in doing so the posted change correct the initial problem, so I'm able to create a SR / {VDI, ISO} NFS.

So now dealing with the Remotes configuration, I would like to fix this so I can can configure for backups. Do I need to create a new post or can we continue from here?