@julien-f

I have created a new backup job in XOA and it worked fine. I will just destroy the current backup job in my XO and create a new job. Thanks again for the help.

@olivierlambert

Apologies for the late reply, yes it did.

@olivierlambert

Thanks for sharing that information.

@olivierlambert

thanks for the reply, I am trying to check the ovs command and what would be the best parameter to use to simulate this.

Also if possible maybe this can be added as feature request in future release for XO. This will help when trying to do some test on certain application and also for studies (like in my case trying to learn wireshark). This is a great to have feature.

Hi, Everyone.

Does XCP-NG or Xen Orchestra have an option to simulate a network cable disconnect? Because in Xen Orchestra, if I go to the VM Guest and go to the network tab and press disconnect on the VIF. It removes the network interface on the VMGuest, so any software that requires a network interface (in my case wireshark), the software just errors out or won't work.

@olivierlambert

I do not understand wha t you mean by "You probably need to transform the disk in a "regular" and not snapshot". Not sure on how to do that, please provide the steps or if you have SOP ready, please point me to the SOP document.

@olivierlambert

Is there a way to make the HD visible in XO? If not what is the command to fail it over to different storage in xcp-ng?

@olivierlambert

I took a snapshot of the vm last 3 Feb 2023, it is still there and I have not deleted it. Is this the reason why encounter this problem?

@olivierlambert

Not recently, I have used Xen admin Center initially when I was starting just to deploy Xen Orchestra and after that it is all Xen Orchestra.

@olivierlambert

Not sure what do you mean by client. the way I created this is using a template that I created:

Please let me know if this not what you needed, and how should I get that information?

@olivierlambert

You are right it looks like it is snapshot:

[22:53 home-hypervisor ~]# xe vdi-param-list uuid=d549c8cb-614f-4784-8a54-0b7780ebb192
uuid ( RO)                    : d549c8cb-614f-4784-8a54-0b7780ebb192
              name-label ( RW): Wireshark Lab
        name-description ( RW): Created by XO
           is-a-snapshot ( RO): true
             snapshot-of ( RO): d549c8cb-614f-4784-8a54-0b7780ebb192
               snapshots ( RO): 609538d7-8bd8-4370-8857-d307ba1174e3; d549c8cb-614f-4784-8a54-0b7780ebb192
           snapshot-time ( RO): 20230216T22:29:04Z
      allowed-operations (SRO): snapshot; clone
      current-operations (SRO):
                 sr-uuid ( RO): c98879ee-5f45-6d49-de86-45117298ad02
           sr-name-label ( RO): 1522 NFS share
               vbd-uuids (SRO): 13c4c5ba-a00e-9552-294d-acfd124c03b3
         crashdump-uuids (SRO):
            virtual-size ( RO): 85899345920
    physical-utilisation ( RO): 25722097664
                location ( RO): d549c8cb-614f-4784-8a54-0b7780ebb192
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): true
     parent ( RO) [DEPRECATED]: <not in database>
                 missing ( RO): false
            is-tools-iso ( RO): false
            other-config (MRW):
           xenstore-data (MRO):
               sm-config (MRO): host_OpaqueRef:3d1b578a-ed85-4986-87de-e46435b3811b: RW; read-caching-enabled-on-2e7b3b4e-fd2a-4013-a859-96209b772873: true; vhd-parent: 063dd2f1-6581-4206-b47e-04fe84acf9ad
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): <not in database>
                    tags (SRW):
             cbt-enabled ( RO): false

But I created this image from template. Is that the reason why it is a snapshot and not an actual disk?

@olivierlambert

Hi, Olivier

Apologies for that, here are some of the details you need: the XO was from source with commit "8dceb". The VMGuest was a Windows 10 image, the issue started when trying to migrate the VM from a Synology 1522+ to Synology 920+. Both are configured to use NFS.

To double check, I have created another XO from source in VMWare Workstation installed on my workstation, it still cannot see the disk that is associated with the VMguest. If I reboot the VM it was able to reboot without any problem.