![]() The fact that you're reporting your clonezilla actually works fine under windows templates, but not linux templates, tells me some wires are crossed somewhere - it could be the ISO you're using, the templates you're using or choosing from, or your XCP-ng install. ![]() So a customer that was trying to boot clonezilla under windows 10 templated VMs had garbled display output until he used xe to change platform:device_id=0002 to platform:device_id=0001 which is what linux templates use. In fact, the issue Olivier is remembering is that clonezilla does not work out of the box when booted under a Windows 10 template, because windows 10 templates present platform:device_id=0002 to the guest OS, and QEMU combined with some linux OS's get confused by this (understandably, the ID is for windows), and it breaks the display. To double check, I just downloaded both clonezilla stable live ISO (debian based) and clonezilla live stable alternative (the ubuntu build), and both boot fine and have working network adapters out of the box, using either debian VM templates or ubuntu VM templates (doesn't matter). In fact, you should be able to use any linux template when creating a VM. ![]() I think you definitely have your templates or something else mixed up, Clonezilla works great out of the box running as a VM under XCP-ng, using any Ubuntu or Debian VM template.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |