Development

• 

  Great projects have great documentation. Is XCP-ng a great project?
  • stormi  

  53
  8
  Votes
  53
  Posts
  3233
  Views

  

  No you can't that's why as an introduction we warn that you need to make a choice, not mix them. We might be able to make our agent work with Citrix drivers in the future, but for this we need a dev.
• J

  Reworking the 'xe-guest-utilities' Repo
  • JustinTimperio  

  18
  0
  Votes
  18
  Posts
  93
  Views

  J

  @olivierlambert @stormi Having tests will be a great argument to become the new upstream Our situation is different from that of any linux distribution that wants to provide the tools (which we encourage any distro to do), since what we provide is a RPM that contains an ISO that itself contains DEBs, RPMs, and others. It's not something we can easily build in our build system, koji (though there may be a way to manage it). So we've get to automate that build process. This weekend I was able to finish the first tool I needed to help streamline the process of testing and building these tools. Its something I'm just calling PRT(Parallel Remote Terminal) for now. I currently have a number of testbeds in my cluster but testing manually on each is a huge pain. PRT is a tool that allows a user to define a group of remote hosts using a yaml file, then send the same command in parallel to each host. PRT returns the connection status, output, and errors on each host directly back to your machine. I hope you won't judge too hard on the quality of my code and docs because this was built in space of 48 hours lol. You can check it out here: https://github.com/JustinTimperio/prt I'll clean this up and improve it over the coming weeks but obviously, this is just tooling to help facilitate the actual work of improving these tools.
• P

  Intel vGPU - GVT-G
  • packy2000  

  6
  0
  Votes
  6
  Posts
  79
  Views

  

  What? Are you sure?
• S

  SOLVED XCPng 8.0 with Ryzen7 4750G(Renoir) suddenly reboot.
  • seirios  

  19
  0
  Votes
  19
  Posts
  116
  Views

  

  Ahh good news! Thanks for the feedback
• C

  vGPU - which graphics card supported?
  vgpu • • chirag11  

  45
  1
  Votes
  45
  Posts
  3506
  Views

  

  I wonder why AMD isn't selling its more modern Pro cards on the market directly?
• D

  SOLVED Cannot export VM in .ova file
  • dan2462  

  18
  0
  Votes
  18
  Posts
  106
  Views

  E

  Hi Dan2462, I would like you to go for the following steps. In the star just choose the virtual machine and pick the option that says File > Export to OVF. Now add a name for the OVF file and mention a directory in which you need to save it. Here mention if you want to export the virtual machine as an OVF, a folder with individual files, or as an OVA, a single-file archive. At the end press Export to start the procedure of OVF export. This step will take some time and a status bar lets you know about the progress of the export process. Apart from that, https://appuals.com/export-import-vm-oracle/ this website would be really helpful for you in getting to know much more about it. I hope that by following these steps you would be able to resolve this issue.
• M

  XCP-ng 8.1 PCIe onboard usb controller passthrough does not work
  • Maggehagge  

  10
  0
  Votes
  10
  Posts
  82
  Views

  

  Using the link on the bottom of the doc will create a PR
• S

  Hiding hypervisor from guest to prevent Nvidia Code 43
  • slavD  

  30
  0
  Votes
  30
  Posts
  248
  Views

  I

  @r1 said in Hiding hypervisor from guest to prevent Nvidia Code 43: @olivierlambert @imtrobin I had worked on CPUID for exposing temperature data of CPU to Guest (Dom0). May be we can use same. # cpuid | grep -I hypervisor_id hypervisor_id = "Microsoft Hv" Is this the one which should be hidden? I'm have no idea if that is enough, but maybe. How can we try this? For kvm , they do this https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#.22Error_43:_Driver_failed_to_load.22_on_Nvidia_GPUs_passed_to_Windows_VMs
• 

  SMAPIv3 - Feedback & Bug reports
  • Marc.pezin  

  43
  2
  Votes
  43
  Posts
  687
  Views

  R

  Ok, thanks for the update. Wasn't expecting production ready, was just curious on status and if was safe to run tests with it which sounds like not.
• S

  How to get know a temperature of MxGPU?
  • savage79  

  6
  0
  Votes
  6
  Posts
  77
  Views

  

  @savage79 said in How to get know a temperature of MxGPU?: I tested only with xcp-ng-8.1.0-2.iso which is based on centos8 Not exact. XCP-ng 8.1 is based on CentOS 7.5 (well 2/3 of it is, the rest is custom).
• 

  Looking for a temporary test host with a nVIDIA GPU
  • stormi  

  26
  0
  Votes
  26
  Posts
  246
  Views

  

  I've got a NVIDIA card in my lab, but I probably need to install that driver you're talking about. Are there any instructions on the wiki? 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [NVS 510] (rev a1)
• J

  hypervisor memory introspection
  • jengelha  

  2
  0
  Votes
  2
  Posts
  30
  Views

  

  We are aware of it Our "bandwidth" right now is not enough to investigate further. edit: it's more a generic library than a real product, so it's nice but that would require a reasonable amount of work to turn it into something "turnkey". However, we are definitely keeping an eye on it
• A

  USB passthrough test reports in 7.5RC1
  • Aimdev  

  57
  0
  Votes
  57
  Posts
  7816
  Views

  G

  Let's give it another try to give my host its USB controller back and pass-through just the USB devices. In this case we're going for a virtual machine hosting common USB devices for home domotica. The devices we want to pass-through: Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO) Which apparently is technical speak for a RFXtrx433XL USB 433.92MHz Transceiver Prolific Technology, Inc. PL2303 Serial Port Which apparently is technical speak for a ZiGate USB-TTL Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB I'm using XCP-ng Center 20.04.00 to help me out and XCP-NG 8.1 on the host. Let's start with a good old: [12:56 vmhost ~]# xe pusb-list host-uuid=***** uuid ( RO) : 2ba8de5b-8fe1-0262-f741-35b4ed350ae0 path ( RO): 1-2 vendor-id ( RO): 067b vendor-desc ( RO): Prolific Technology, Inc. product-id ( RO): 2303 product-desc ( RO): PL2303 Serial Port serial ( RO): version ( RO): 1.10 description ( RO): Prolific Technology, Inc._PL2303 Serial Port uuid ( RO) : 08b23122-e01b-9ab2-e72d-185648ae19d7 path ( RO): 1-7 vendor-id ( RO): 0403 vendor-desc ( RO): Future Technology Devices International, Ltd product-id ( RO): 6015 product-desc ( RO): Bridge(I2C/SPI/UART/FIFO) serial ( RO): ******* version ( RO): 2.00 description ( RO): Future Technology Devices International, Ltd_Bridge(I2C/SPI/UART/FIFO)_DO2VQGDG Ok, we have 2 devices already ready to be passthrough. Let's try to make the third one show up! Using the follow commands and some reading I could identify the DENY rules in "/etc/xensource/usb-policy.conf", which prevent my Aeotec Z-Stick from showing. [13:06 vmhost ~]# /opt/xensource/libexec/usb_scan.py -d [13:06 vmhost ~]# cat /var/log/user.log | less I've adjusted my "/etc/xensource/usb-policy.conf" to the following: # When you change this file, run 'xe pusb-scan' to confirm # the file can be parsed correctly. # # Syntax is an ordered list of case insensitive rules where # is line comment # and each rule is (ALLOW | DENY) : ( match )* # and each match is (class|subclass|prot|vid|pid|rel) = hex-number # Maximum hex value for class/subclass/prot is FF, and for vid/pid/rel is FFFF # # USB Hubs (class 09) are always denied, independently of the rules in this file DENY: vid=17e9 # All DisplayLink USB displays ALLOW:vid=0658 pid=0200 class=02 # Aeotec Z-Stick Gen5 (ZW090) - UZB DENY: class=02 # Communications and CDC-Control ALLOW:vid=056a pid=0315 class=03 # Wacom Intuos tablet ALLOW:vid=056a pid=0314 class=03 # Wacom Intuos tablet ALLOW:vid=056a pid=00fb class=03 # Wacom DTU tablet DENY: class=03 subclass=01 prot=01 # HID Boot keyboards DENY: class=03 subclass=01 prot=02 # HID Boot mice ALLOW:vid=0658 pid=0200 class=0a # Aeotec Z-Stick Gen5 (ZW090) - UZB DENY: class=0a # CDC-Data DENY: class=0b # Smartcard DENY: class=e0 # Wireless controller DENY: class=ef subclass=04 # Miscellaneous network devices ALLOW: # Otherwise allow everything else but also tried: # When you change this file, run 'xe pusb-scan' to confirm # the file can be parsed correctly. # # Syntax is an ordered list of case insensitive rules where # is line comment # and each rule is (ALLOW | DENY) : ( match )* # and each match is (class|subclass|prot|vid|pid|rel) = hex-number # Maximum hex value for class/subclass/prot is FF, and for vid/pid/rel is FFFF # # USB Hubs (class 09) are always denied, independently of the rules in this file DENY: vid=17e9 # All DisplayLink USB displays ALLOW:vid=0658 pid=0200 # Aeotec Z-Stick Gen5 (ZW090) - UZB ALLOW: class=02 # Communications and CDC-Control ALLOW:vid=056a pid=0315 class=03 # Wacom Intuos tablet ALLOW:vid=056a pid=0314 class=03 # Wacom Intuos tablet ALLOW:vid=056a pid=00fb class=03 # Wacom DTU tablet DENY: class=03 subclass=01 prot=01 # HID Boot keyboards DENY: class=03 subclass=01 prot=02 # HID Boot mice ALLOW: class=0a # CDC-Data DENY: class=0b # Smartcard DENY: class=e0 # Wireless controller DENY: class=ef subclass=04 # Miscellaneous network devices ALLOW: # Otherwise allow everything else After some playing around we got: [13:14 vmhost ~]# xe pusb-scan host-uuid=***** [13:15 vmhost ~]# xe pusb-list host-uuid=***** uuid ( RO) : 0f7d6f12-6c4e-4f71-0c81-f7a7503a75f1 path ( RO): 1-8 vendor-id ( RO): 0658 vendor-desc ( RO): Sigma Designs, Inc. product-id ( RO): 0200 product-desc ( RO): Aeotec Z-Stick Gen5 (ZW090) - UZB serial ( RO): version ( RO): 2.00 description ( RO): Sigma Designs, Inc._Aeotec Z-Stick Gen5 (ZW090) - UZB uuid ( RO) : 2ba8de5b-8fe1-0262-f741-35b4ed350ae0 path ( RO): 1-2 vendor-id ( RO): 067b vendor-desc ( RO): Prolific Technology, Inc. product-id ( RO): 2303 product-desc ( RO): PL2303 Serial Port serial ( RO): version ( RO): 1.10 description ( RO): Prolific Technology, Inc._PL2303 Serial Port uuid ( RO) : 08b23122-e01b-9ab2-e72d-185648ae19d7 path ( RO): 1-7 vendor-id ( RO): 0403 vendor-desc ( RO): Future Technology Devices International, Ltd product-id ( RO): 6015 product-desc ( RO): Bridge(I2C/SPI/UART/FIFO) serial ( RO): ***** version ( RO): 2.00 description ( RO): Future Technology Devices International, Ltd_Bridge(I2C/SPI/UART/FIFO)_DO2VQGDG Well we're ready for some pass-through, right? Using XCP-ng Center we can see these 3 devices and "Enable pass-through" for all of these 3 devices. After shutting down the VM, using properties we can attach all 3 USB-devices and start the VM again, but not before running the following command as was recommended: xe vm-param-set uuid=**** platform:device-model=qemu-upstream-compat Let's start and monitor dmesg: [ 742.309309] block tda: sector-size: 512/512 capacity: 20971520 [ 742.727012] device vif6.0 entered promiscuous mode [ 742.961272] device tap6.0 entered promiscuous mode [ 743.068536] usb 1-8: reset full-speed USB device number 4 using xhci_hcd [ 743.217985] cdc_acm 1-8:1.0: ttyACM0: USB ACM device [ 743.376482] usb 1-8: reset full-speed USB device number 4 using xhci_hcd [ 743.525903] cdc_acm 1-8:1.0: ttyACM0: USB ACM device [ 743.571126] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 743.571136] ftdi_sio 1-7:1.0: device disconnected [ 743.700284] usb 1-7: reset full-speed USB device number 3 using xhci_hcd [ 743.851993] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected [ 743.852018] usb 1-7: Detected FT-X [ 743.852171] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0 [ 743.984286] usb 1-8: reset full-speed USB device number 4 using xhci_hcd [ 744.137611] cdc_acm 1-8:1.0: ttyACM0: USB ACM device [ 744.138491] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 744.138500] ftdi_sio 1-7:1.0: device disconnected [ 744.268258] usb 1-7: reset full-speed USB device number 3 using xhci_hcd [ 744.420007] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected [ 744.420029] usb 1-7: Detected FT-X [ 744.420464] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0 [ 744.465529] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1 [ 744.465539] pl2303 1-2:1.0: device disconnected [ 744.592213] usb 1-2: reset full-speed USB device number 2 using xhci_hcd [ 744.741634] pl2303 1-2:1.0: pl2303 converter detected [ 744.742254] usb 1-2: pl2303 converter now attached to ttyUSB1 [ 744.876149] usb 1-8: reset full-speed USB device number 4 using xhci_hcd [ 745.025388] cdc_acm 1-8:1.0: ttyACM0: USB ACM device [ 745.025629] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 745.025636] ftdi_sio 1-7:1.0: device disconnected [ 745.156079] usb 1-7: reset full-speed USB device number 3 using xhci_hcd [ 745.307475] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected [ 745.307495] usb 1-7: Detected FT-X [ 745.307652] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0 [ 745.308046] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1 [ 745.308054] pl2303 1-2:1.0: device disconnected [ 747.307309] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 747.307318] ftdi_sio 1-7:1.0: device disconnected [ 747.435543] usb 1-7: reset full-speed USB device number 3 using xhci_hcd [ 747.586967] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected [ 747.586987] usb 1-7: Detected FT-X [ 747.587202] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0 [ 756.026324] device tap6.0 left promiscuous mode [ 756.744069] vif vif-6-0 vif6.0: Guest Rx ready [ 757.925017] usb 1-2: reset full-speed USB device number 2 using xhci_hcd [ 758.321147] usb 1-2: reset full-speed USB device number 2 using xhci_hcd [ 768.745084] pl2303 1-2:1.0: pl2303 converter detected [ 768.746207] usb 1-2: pl2303 converter now attached to ttyUSB1 [ 769.803089] device vif6.0 left promiscuous mode And xensource.log as txt file while the VM started and got shutdown. Oh and so far everything looked good, right? Everything got attached, the VM booted and the properties of the VM shows that all 3 devices are "Attached". On the VM running ubuntu I get the following: vm@vm:~$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 12M |__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M My USB 1.1 device (ZiGate) is present! The other 2 devices are USB2.0 and those are magically missing?! Why? How? What did I do wrong!? What can I try to make this work? Ah well, time to pci-pass-through my USB controller into that device again, although I would have prefered USB-passthrough! I did also apply scottyXCPNG's workaround, but not allow my USB 2.0 devices to be passed into the VM with those applied.
• T

  Build network drivers from sources
  • tom  

  21
  0
  Votes
  21
  Posts
  3015
  Views

  

  Hi @Andy76 Please open a support ticket, it's within our XCP-ng Enterprise support package
• G

  RTL8153 Compile
  • geant90  

  53
  0
  Votes
  53
  Posts
  4054
  Views

  P

  @Professor-X-Tech I'm back to report that although it working, I am having issue with the USB 3 Nic. Don't have time to troubleshoot it but I will get to it and if I find anything to share I will.
• B

  Creating an API for XCP-ng tasks
  • BeDazzleMe  

  13
  0
  Votes
  13
  Posts
  86
  Views

  

  oVirt is the same concept, the only diff is maybe a REST API, but otherwise it's really similar (but even a bit harder to setup). Anyway, if you need assistance on API calls, let us know.
• P

  Guest Tools on FreeBSD
  • paco  

  8
  0
  Votes
  8
  Posts
  40
  Views

  P

  @stormi It does. I put the screen shots of what it looks like when you run it in the pull request.
• H

  how to get Measured Boot Supplemental Pack
  • hani  

  6
  0
  Votes
  6
  Posts
  62
  Views

  

  @hani sounds great, keep us posted on your progress and findings!
• L

  SOLVED what is the easiest way to load ISO images to XCP-ng?
  • LonnieTC  

  10
  0
  Votes
  10
  Posts
  1703
  Views

  

  It's not a trick, it's a way to do it with the CLI
• B

  Trying to build kernel module : modprobe Exec format error
  • benze  

  5
  0
  Votes
  5
  Posts
  28
  Views

  R

  Short answer is that the module is referring to wrong symbol table. Its a lookup table for function interaction between module and kernel. Easy answer is to use this .config file and build full kernel.