@l1c I am not 100% sure but can you check your grub.cfg and see if the pciback.hide is still there?

/boot/efi/EFI/xenserver/grub.cfg

If it is there remove the text xen-pciback.hide=(xx:xx.X) . (assuming your system uses EFI)

But use this for the last resort, I am sure someone here will have better solution.

@olivierlambert said in increase 24 hour timeout-limit on backup/copy:

You are welcome Our docs (XO and XCP-ng) are in a relatively good shape now, so that should be the first step when you search something!

And if it's not there, you can easily contribute to add it!

sure I will try to contribute and I did not expect the documentation was this great. Cheers!

@olivierlambert Awesome. The solution was in front of my nose. I did google search but it was all old and xen-server related.
Thank you

Is there any way to increase server timeout after 24 hours.

I want to use Continuous Replication on my VM. The backup destination is off-site so I am stuck with 8 Mbps upload limit, and it roughly will take 30hours to complete initial backup.

Thank you.

 transfer
Start: Aug 30, 2020, 9:32:58 AM
End: Aug 31, 2020, 9:33:40 AM
Duration: a day
Error: task has been destroyed before completion

@olivierlambert said in Stuck at copying Continuous Replicated VM:

In order to CR to continue after "booting it", you must use a copy.

In case of you lost your origin VM, then it doesn't matter if you boot the replicated VM directly.

I don't know why full clone doesn't work on this SR.

I give up for now
I have no idea why it did not work. No error messages on the logs also. It just stuck. anyways thank you @olivierlambert for your time.

I created a new VM and attach the copied VDI 1 to it. The second VDI cannot be attached so I delete it and will copy from the source server. Looks like it is working.

I have one more VM to process and this time I will double check the steps and share any progress here.

@olivierlambert Yes I have 1 running VM (created by this server).

I tried many ways still stuck at 0%.
I will try to copy VDIs indivudally and crate a new VM. Or should I create a new VM and use existing VDIs?

by the way fast clone works. instantly I have a clone up and running.

just saw on XO tasks it shows the status.

@olivierlambert said in Stuck at copying Continuous Replicated VM:

Okay feel free to try with xe vm-copy command directly on the host, maybe we'll have more chance to know what's going on.

sure.
just executed
xe vm-copy new-name-label=newVM vm=copiedVM
no messages/output yet, will leave it and check back.

@olivierlambert nope no replication nor any backup task running. will try couple of times. and see if I can get an error message.

I want to move my VM from server A to B by using continuous replication. Servers are identical. I choose CR because I will have the latest copy available to create the new VM (it is a zimbra mail server so 5 minute down time is important, BTW thank you so much for XO team for giving this feature free for us)

I did a CR backup of a VM from A server to B server. After successfully replicating, On the B server when I hit the copy VM to the same SR of B, it stuck at 0% and never continues.
**How should I diagnose this problem. **

Server has 4 times more storage than the VM.

@stormi said in XCP-ng 8.1.0 beta now available!:

@onur said in XCP-ng 8.1.0 beta now available!:

type ( RO): ext

As expected. The ext type has no information of the FS version in its name.
already created bug for XCP-ng center, but it looks like system is not reporting ext type

@olivierlambert said in XCP-ng 8.1.0 beta now available!:

What's the info reported by xe sr-param-list uuid=<UUID OF THIS SR>?

xe sr-param-list uuid=3fe64d91-5349-ac86-d9b7-aa9dcf813cea
uuid ( RO)                    : 3fe64d91-5349-ac86-d9b7-aa9dcf813cea
              name-label ( RW): ssd240Toshiba
        name-description ( RW):
                    host ( RO): OB1
      allowed-operations (SRO): VDI.enable_cbt; VDI.list_changed_blocks; unplug; plug; PBD.create; VDI.disable_cbt; update; PBD.destroy; VDI.resize; VDI.clone; VDI.data_destroy; scan; VDI.snapshot; VDI.mirror; VDI.create; VDI.destroy; VDI.set_on_boot
      current-operations (SRO):
                    VDIs (SRO): 5da0c967-657f-43f2-8e4a-7cb80b7938ef; 2dd44491-b458-4119-a024-a48ace2a23e3; 05910aa1-8c5e-4af7-8ffc-11dbdcae5116; 60a7602d-ec61-4ef4-9db1-0f3fdbcd43f9
                    PBDs (SRO): 96e685a7-f5cc-32fa-8289-b10e4a8ea4f5
      virtual-allocation ( RO): 481036337152
    physical-utilisation ( RO): 153255415808
           physical-size ( RO): 192280748032
                    type ( RO): ext
            content-type ( RO): user
                  shared ( RW): false
           introduced-by ( RO): <not in database>
             is-tools-sr ( RO): false
            other-config (MRW): i18n-original-value-name_label: Local storage; i18n-key: local-storage
               sm-config (MRO): devserial: scsi-3500080dc0133cdc2
                   blobs ( RO):
     local-cache-enabled ( RO): true
                    tags (SRW):
               clustered ( RO): false

@stormi said in XCP-ng 8.1.0 beta now available!:

@onur said in XCP-ng 8.1.0 beta now available!:

/dev/mapper/XSLocalEXT--3fe64d91--5349--ac86--d9b7--aa9dcf813cea-3fe64d91--5349--ac86--d9b7--aa9dcf813cea on /run/sr-mount/3fe64d91-5349-ac86-d9b7-aa9dcf813cea type ext4 (rw,relatime)

It's ok, the SR is mounted as ext4 so this means it was created as ext4.

great thank you very much @stormi . As you suspected, XCP-ng Center shows wrong format (I guess here is a bug for XCP-ng center devs)

here is the output. So I assume ext4 should be default when selecting EXT on the setup.

@stormi said in XCP-ng 8.1.0 beta now available!:

I don't think you should trust XCP-ng Center on this. What do you think @borzel?

Check the output of mount instead.

 mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=1270132k,nr_inodes=317533,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
configfs on /sys/kernel/config type configfs (rw,relatime)

/dev/sda1 on / type ext3 (rw,relatime)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
xenfs on /proc/xen type xenfs (rw,relatime)
xenstore on /var/lib/xenstored type tmpfs (rw,relatime,mode=755)

/dev/sda5 on /var/log type ext3 (rw,relatime)

/dev/mapper/XSLocalEXT--3fe64d91--5349--ac86--d9b7--aa9dcf813cea-3fe64d91--5349--ac86--d9b7--aa9dcf813cea on /run/sr-mount/3fe64d91-5349-ac86-d9b7-aa9dcf813cea type ext4 (rw,relatime)

tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=256416k,mode=700)

@olivierlambert said in XCP-ng 8.1.0 beta now available!:

What do you mean? SR file system or root filesystem?

The Local Storage for VM.

last week I installed a new server XCP-ng 8.1. But the filesystem is still Ext3. (by the way XO connects without problem but you need XCP-ng Center Development build to access)
Today I will install a new server, what should I do to get ext4 in the filesystem?
Thanks

Thank you very much borzel. I am daily using XCP-ng Center to manage VM of 3 servers. I use XO for backup and migrate cases. Both are great tools. Thanks again for your time for providing and keep updating the release.

@olivierlambert said in Continuous Replication fails with VDI_IO_ERROR(Device I/O errors) on fresh XOA install after XenServer 7.2 -> XCP-ng 8.0 upgrade:

To your config file, yes. Where this config file is depends on where do you installed Xen Orchestra (I suppose from the sources, so I can't guess where do you installed, could be anyware )

edit: I think it's fixed now and integrated by default in the config

Great, this fix already is in the new version.
I was having this problem (Error: VDI_IO_ERROR(Device I/O errors)) and was not be able to do CR of my VMs but now CR works.
Thank you

PS: BTW that was my config file

@olivierlambert said in Continuous Replication fails with VDI_IO_ERROR(Device I/O errors) on fresh XOA install after XenServer 7.2 -> XCP-ng 8.0 upgrade:

Xen Orchestra configuration

should I add "guessVhdSizeOnImport: true" to /opt/xen-orchestra/packages/xo-server/config.toml

Windows 10 x64 Pro version 1903 and the beta tools works 100% now.

Here is the summary of what I did (as mentioned in this discussion)

1-) Install beta tools 8.2.1
2-) When it fails at the end don't worry just reboot.
3-) As ruskofd suggests: --> Launch the following command in the C:\Program Files\XCP-ng\XenTools folder with an Administrative prompt : InstallAgent.exe DEFAULT
4-) Install beta tools 8.2.1 again with REPAIR.
5-) Accept driver confirmation
6-) Reboot
7-) Now in my case two drivers XN0002 XENBUS VBD and XN0002 XENBUS VIF were not installed, so I used borzel's suggestion: --> you have to install the drivers then manually ... point the driver install dialog from windows to c:\programe files\xcp-ng\drivers (don't forget to tell him to search also in subfolders)
8-) Reboot
9-) Check all the drivers are working. In my case VIF was not installed so one more time install driver manually
10-) Finish

Thank you all for suggestions.