Development

• 

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

  21
  7
  Votes
  21
  Posts
  2474
  Views

  

  @Patrik48 Just to make things clear: there is no documentation (or project of documentation) that would be restricted to those who subscribed to pro support.
• 

  XCP-ng Center 8.0.1: Switch from MBps to MBit/s for Networks Graphs
  • borzel  

  4
  3
  Votes
  4
  Posts
  240
  Views

  O

  @borzel In my humble opinion, I would say no because then you are deviating from industry standard naming. The reason for standards is so that everyone will know what you are talking about as long as you follow the standard. Lowercase b always means bit and uppercase B always means Byte. Please do not change this. It is trivial to learn the standard. It is less than trivial when people start making up their own abbreviations for things (though admittedly this one isn't rocket science to figure out).
• L

  XenApp or similar on XCP-ng?
  • LonnieTC  

  14
  0
  Votes
  14
  Posts
  247
  Views

  

  @blafuente said in XenApp or similar on XCP-ng?: @nikade Great! Hope it meets your expectations and needs. If you need any help we'll be more than happy to help you out I havent gotten my free serial yet so I havent been able to test it out, but it looks pretty neat in the videos.
• 

  [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1
  • borzel  

  51
  0
  Votes
  51
  Posts
  3849
  Views

  M

  I tested on a fresh 2016 install. The install went well and the management agent was installed. I enabled VSS but the VSS snapshots don't seem to be working. To compare I installed the citrix client tools on a fresh 2016 install and VSS does work.
• 

  XCP-ng Windows PV Drivers 8.2.2
  • borzel  

  16
  4
  Votes
  16
  Posts
  338
  Views

  

  @olivierlambert some minor things like branding https://github.com/xcp-ng/xcp/issues/181 borzel created this issue in xcp-ng/xcp open XCP-ng Windows PV-Drivers 8.2.2 #181
• L

  UNSOLVED XCP-ng LiveCD Available?
  • LonnieTC  

  15
  1
  Votes
  15
  Posts
  206
  Views

  

  Xen is doing all the CPU and memory sharing, so Xen is a type 1. Network and storage are delegate to the privileged domain (dom0).
• L

  SOLVED Getting VM ip's from Dom0?
  • LonnieTC  

  3
  0
  Votes
  3
  Posts
  53
  Views

  L

  Thanks for the info. That really helps
• L

  Compiling XCP-ng from ground to boot?
  • LonnieTC  

  3
  0
  Votes
  3
  Posts
  68
  Views

  L

  @stormi Thanks for the links and I will start to dig in to them more to learn how it can be done. In a quick review of the links, this may be what I need since I do not think that I will actually need to re-compile XCP-ng, but just add for the setup of some additional installation steps via rpms and yum as well as some configurations at this point. This is really an experimental endeavor for the moment while it also allows me to learn more about the whole installation and setup of XCP-ng along the way.
• A

  USB passthrough test reports in 7.5RC1
  • Aimdev  

  33
  0
  Votes
  33
  Posts
  6060
  Views

  A

  Hello, I am Georg, and I am also new to XCP, kind of...at work, we have XEN, but sadly, thats not my business. Long story short, I got nearly everything sorted out, but not USB passthrough. I got all devices showing up in XCP-center, and attached them to the VM. When I start the VM, all USB devices are attached. But as soon as the VM is booting, the status "Attached" changes to "No". [VM -> Properties -> USB] However, what I found out: for example, I attach my keyboard and pass it to my Windows vm: then why I can control the local XEN console with this keyboard I passed through? And this error: "Failed","Starting VM 'Windows 10 (64-bit) (1)' Internal error: xenopsd internal error: Call to usb reset failed: Forkhelpers.Spawn_internal_error("usage: usb_reset.py attach [-h] -d DOMID -p PID [-r RESET_ONLY] device\nusb_reset.py attach: error: argument -r: expected one argument\n", "", _) Time: 00:00:23","xcp-ng","Jun 29, 2019 12:05 AM"
• L

  Dom0 Hypothetical Question about OS's
  • LonnieTC  

  9
  0
  Votes
  9
  Posts
  101
  Views

  L

  Hi All, In some of the latest read that I have been doing, it seems that the XenServer folks were also investigating the ideas of so called "Sub Domains" or "Driver Domains" via Mini-OS and MirageOS as minimal OS's to deaggregate Dom0 to take drivers out and make them independently sufficient such that if something happens to one of them then the rest of the system remains unaffected. This links into the ideas of Unikernels but I think that a lot of this is still in the R&D phase although some great ideas, to be sure. I could see a whole set of Sub-Domains to handle just about all of the functionality that Dom0 currently manages in perhaps a future evolution. Cheers
• L

  XCP-ng Dom0 Clarification question
  • LonnieTC  

  19
  0
  Votes
  19
  Posts
  166
  Views

  L

  @MajorTom Yea, I see what you mean. Just tried it yesterday with similar results.
• L

  Any XPC-ng C/C++ API examples?
  • LonnieTC  

  3
  0
  Votes
  3
  Posts
  66
  Views

  L

  Thanks again. I will dig into XAPI and the XO CLI to get a better feel for things. Best
• L

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

  8
  0
  Votes
  8
  Posts
  151
  Views

  L

  That will be very exciting to see when it is ready since I think that it will help a lot of people.
• L

  VM Calling API to send messages to Hypervisor
  • LonnieTC  

  10
  0
  Votes
  10
  Posts
  115
  Views

  

  From Vbox to XCP-ng: export in OVA then import with XO.
• 

  Windows Server 2016 & 2019 freezing on multiple hosts
  • michael  

  26
  0
  Votes
  26
  Posts
  2538
  Views

  

  @apayne This is a good suggestion, all tho it is happening on a lot of different physical machines if im not mistaken. Im running a couple of Windows Server 2016 on xcp-ng 7.4 and 7.5 without any issues, im hoping this isnt something related to the specific version xcp-ng 7.6 since we're planning on migrating from XenServer to this version.
• L

  XCP-ng Footprint Size
  • LonnieTC  

  10
  0
  Votes
  10
  Posts
  175
  Views

  L

  Thanks. I sure will. Hopefully the project design will go well.
• 

  XCP-ng and NVIDIA GPUs
  • jtbw911  

  22
  0
  Votes
  22
  Posts
  1232
  Views

  

  @olivierlambert I did a bit of light digging. General consensus is that Dell's servers are not ready for this kind of stuff, but then again I've seen crowds get things wrong before: https://www.reddit.com/r/homelab/comments/6mafcg/can_i_install_a_gpu_in_a_dell_power_edge_r810/ This is the method described for KVM: http://mathiashueber.com/fighting-error-43-how-to-use-nvidia-gpu-in-a-virtual-machine/ Additional KVM docs (plus a small description of the vendor ID problem): https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#"Error_43:_Driver_failed_to_load"_on_Nvidia_GPUs_passed_to_Windows_VMs An updated methodology for Ryzen on-chip GPU: http://mathiashueber.com/ryzen-based-virtual-machine-passthrough-setup-ubuntu-18-04/ This is the method described for VMWare: http://codefromabove.com/2019/02/the-hyperconverged-homelab-windows-vm-gaming/ Hyper-V documentation is a bit more sparse, but this hints that Microsoft may have simply worked around the issue (ala vendor license agreements), at least when using RemoteFX: http://techgenix.com/enabling-physical-gpus-hyper/ (Optional) Get CUDA working for cheap-o cards: https://medium.com/@samnco/using-the-nvidia-gt-1030-for-cuda-workloads-on-ubuntu-16-04-4eee72d56791 So it looks like the common factors are: The GPU device must be isolated on the host with the vfio kernel driver. To ensure this, the vfio driver must load first, prior to any vendor or open source driver. GPU must be connected to the guest VM via PCI pass-through. No surprise. The CPU must not be identified as a virtual one, it must have some other identity when probed. This appears to be the key to preventing the dread NVidia Error 43; it suggests the driver is just examining the CPU assigned to it, although some documentation mentions a "vendor" setting. The work-around is to make it into a string it doesn't match against, and it just works. Even a setting of "unknown" is shown to work. I don't know if there is a way to specify in a XCP guest "please don't identify yourself as virtual". For cards that are CUDA capable but "unsupported" by NVidia, you install the software in a difference sequence (CUDA first, then driver). Disclaimer: I'm just compiling a list to get an idea about what to do; I haven't done the actual install, nor do I have the hardware. Hopefully this helps.
• B

  Is it possible to see container
  • Bahman  

  4
  0
  Votes
  4
  Posts
  98
  Views

  B

  lxd is new technology. Linux container is persirtant container (not like docker, with volume share container) and it's coming to be :-).
• C

  vGPU - which graphics card supported?
  vgpu • • chirag11  

  22
  0
  Votes
  22
  Posts
  710
  Views

  

  I am running a WX7100 under XCP-ng 7.6. It only allows full GPU passthrough. So you can run multiple VMS on the server, but only one at a time can be assigned the GPU. I have tested it to work properly with Server 2016 std, Server 2019 std, and Win10 pro. Currently I have it crunching BOINC under win10pro and here are the stats.... BOINCstats for Norby
• G

  RTL8153 Compile
  • geant90  

  43
  0
  Votes
  43
  Posts
  3649
  Views

  

  Here's another willing script tester