XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. bc-23
    B
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 6
    • Best 2
    • Controversial 0
    • Groups 0

    bc-23

    @bc-23

    4
    Reputation
    33
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    bc-23 Unfollow Follow

    Best posts made by bc-23

    • RE: RunX: tech preview

      @ronan-a I have seen there are updated packages, thanks 🙂
      After the update I'm able to start the container/VM 🙂

      posted in News
      B
      bc-23
    • RE: Ceph (qemu-dp) in XCP-ng 7.6

      I'm looking forward for the SMAPIv3 integration. I already took a look on the concept and I really like the separation of volume and datapath plugin. I think this will make a lot of things easier in the future.

      posted in Development
      B
      bc-23

    Latest posts made by bc-23

    • RE: RunX: tech preview

      @ronan-a I have seen there are updated packages, thanks 🙂
      After the update I'm able to start the container/VM 🙂

      posted in News
      B
      bc-23
    • RE: RunX: tech preview

      @ronan-a The server is still running on 8.2

      [11:21 fraxcp04 ~]# rpm -qa | grep xenops
      xenopsd-0.150.5.1-1.1.xcpng8.2.x86_64
      xenopsd-xc-0.150.5.1-1.1.xcpng8.2.x86_64
      xenopsd-cli-0.150.5.1-1.1.xcpng8.2.x86_64
      

      Are the patches for this version?

      posted in News
      B
      bc-23
    • RE: RunX: tech preview

      Hi,

      I have started to play around with this feature. I think it's a great idea 🙂
      At the moment I'm running into issue on container start:

      message: xenopsd internal error: Could not find BlockDevice, File, or Nbd implementation: {"implementations":[["XenDisk",{"backend_type":"9pfs","extra":{},"params":"vdi:80a85063-9b59-4fda-82c9-017be0fe967a share_dir none ///srv/runx-sr/1"}]]}
      

      I have created the SR as described above:

      uuid ( RO)                    : 968d0b84-213e-a269-3a7a-355cd54f1a1c
                    name-label ( RW): runx-sr
              name-description ( RW): 
                          host ( RO): fraxcp04
            allowed-operations (SRO): VDI.introduce; unplug; plug; PBD.create; update; PBD.destroy; VDI.resize; VDI.clone; scan; VDI.snapshot; VDI.create; VDI.destroy; VDI.set_on_boot
            current-operations (SRO): 
                          VDIs (SRO): 80a85063-9b59-4fda-82c9-017be0fe967a
                          PBDs (SRO): 0d4ca926-5906-b137-a192-8b55c5b2acb6
            virtual-allocation ( RO): 0
          physical-utilisation ( RO): -1
                 physical-size ( RO): -1
                          type ( RO): fsp
                  content-type ( RO): 
                        shared ( RW): false
                 introduced-by ( RO): <not in database>
                   is-tools-sr ( RO): false
                  other-config (MRW): 
                     sm-config (MRO): 
                         blobs ( RO): 
           local-cache-enabled ( RO): false
                          tags (SRW): 
                     clustered ( RO): false
      
      
      # xe pbd-param-list uuid=0d4ca926-5906-b137-a192-8b55c5b2acb6
      uuid ( RO)                  : 0d4ca926-5906-b137-a192-8b55c5b2acb6
           host ( RO) [DEPRECATED]: a6ec002d-b7c3-47d1-a9f2-18614565dd6c
                   host-uuid ( RO): a6ec002d-b7c3-47d1-a9f2-18614565dd6c
             host-name-label ( RO): fraxcp04
                     sr-uuid ( RO): 968d0b84-213e-a269-3a7a-355cd54f1a1c
               sr-name-label ( RO): runx-sr
               device-config (MRO): file-uri: /srv/runx-sr
          currently-attached ( RO): true
                other-config (MRW): storage_driver_domain: OpaqueRef:a194af9f-fd9e-4cb1-a99f-3ee8ad54b624
      
      

      I see also that in /srv/runx-sr a symlink 1 is created, pointing to a overlay image.

      The VM is in stated paused after the error above.

      The template I used was a old debian PV template, where I removed the PV-bootloader and install-* attributes from other-config. What template would you recommend to use?

      Any idea what could cause the error above?

      Thanks,
      Florian

      posted in News
      B
      bc-23
    • RE: Ceph (qemu-dp) in XCP-ng 7.6

      I'm looking forward for the SMAPIv3 integration. I already took a look on the concept and I really like the separation of volume and datapath plugin. I think this will make a lot of things easier in the future.

      posted in Development
      B
      bc-23
    • RE: Ceph (qemu-dp) in XCP-ng 7.6

      Thanks for the update. Then I will go with a LVMoRBDSR as a workaround at the moment. Maybe I find some time to build a development environment and do some tests with the smapiv3-changes branch.

      posted in Development
      B
      bc-23
    • Ceph (qemu-dp) in XCP-ng 7.6

      Hi,

      the last week, I tried to understand how the RBDSR plugin is working (or at the moment not working) in XCP-ng togther with qemu-dp.

      I see how the plugin is working together with ceph, and how it communicates with qemu-dp, but I don't understand the current state of the qemu-dp package.

      At the moment I'm able to create a disk image in ceph, but starting a VM with this image results in a qemu error that the rbd protocol is unknown.

      Maybe someone can explain to me the current state of the qemu-dp package in XCP-ng 7.6? I see that there is a version in the xcp-ng-extras repo, which I
      have installed at the moment. But is seems that it don't support rbd protocol. For 7.5 there was a extra qemu-dp package build for ceph, should this be the
      same package as in the 7.6 extras repo?

      I also see that there is work done in a smapiv3-changes branch in this repo:
      https://github.com/xcp-ng/qemu-dp/tree/smapiv3-changes

      As there is a file block/rbd.c I would assume this is a qemu-dp version which supports the rbd protocol, is this correct?

      Would be great if someone could give me a explanation how the qemu-dp is handled in XCP-ng and what your plans are.

      posted in Development
      B
      bc-23