Posts made by cheese

I figured out that it is an old issue. It is fatal when memory-dynamic-max is less than memory-static-max.

I met a strange issue when doing vm-checkpoint for a win 2019 VM:

# xe vm-checkpoint uuid=9e379243-2eba-b273-037c-60f5d53b4422 new-name-label=lirb-checkpoint
The server failed to handle your request, due to an internal error.  The given message may give details useful for debugging the problem.
message: xenopsd internal error: (Failure "Error from emu-manager: xenguest Invalid argument")

The xenguest error log in daemon.log:

May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: detail: Failed allocation for dom 39: 1024 extents of order 0
May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Failed to populate physmap (16 = Device or resource busy): Int
ernal error
May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Failed to populate pfns for batch of 1024 pages: Internal erro
r
May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Restore failed (16 = Device or resource busy): Internal error
May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xenguest: xc_domain_restore: [1] Restore failed (16 = Device or resource 
busy)
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: poll failed because revents=0x11 for `xenguest`.
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error for emu `xenguest`: wait_for_event => Invalid argument
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error waiting for events: `Invalid argument`.
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error sending message to emu client: `Broken pipe`.
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Emu `xenguest` exited with an error: 1.
May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Reporting: `error:xenguest Invalid argument#012`...

The final error comes from xenguest. Any idea about this?

Welcome!

@olivierlambert That's true...

XCP-ng 7.6

We have two CentOS 7 vms running on the same host. Qemu commands are almost the same:

6 S 65546    14161 14134  1  80   0 - 46957 poll_s 16:57 ?        00:00:35 qemu-dm-11 -machine pc-0.10,accel=xen,max-ram-below-4g=4026531840,allow-unassigned=true,trad_compat=true -vnc unix:/var/run/xen/vnc-11,lock-key-sync=off -incoming fd:4 -monitor null -xen-domid 11 -m size=1024 -boot order=cdn -usb -device usb-tablet,port=2 -smp 1,maxcpus=24 -serial pty -display none -nodefaults -trace enable=xen_platform_log -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=deny,resourcecontrol=deny -S -global PIIX4_PM.revision_id=0x1 -global ide-hd.ver=0.10.2 -global piix3-ide-xen.subvendor_id=0x5853 -global piix3-ide-xen.subsystem_id=0x0001 -global piix3-usb-uhci.subvendor_id=0x5853 -global piix3-usb-uhci.subsystem_id=0x0001 -global rtl8139.subvendor_id=0x5853 -global rtl8139.subsystem_id=0x0001 -parallel null -qmp unix:/var/run/xen/qmp-libxl-11,server,nowait -qmp unix:/var/run/xen/qmp-event-11,server,nowait -device xen-platform,addr=3,device-id=0x0001,revision=0x2,class-id=0x0100,subvendor_id=0x5853,subsystem_id=0x0001 -drive file=,if=ide,index=1,media=cdrom,force-lba=off -drive file=/dev/sm/backend/f6a05383-96e4-91ea-9bca-b6aa96d95919/2089fe0e-5b64-4220-97ef-e91809bcef55,if=ide,index=0,media=disk,force-lba=on,format=raw -device rtl8139,netdev=tapnet0,mac=3a:11:65:47:d7:83,addr=4 -netdev tap,id=tapnet0,fd=7 -device cirrus-vga,vgamem_mb=8,rombar=1,romfile=,subvendor_id=0x5853,subsystem_id=0x0001,addr=2 -vnc-clipboard-socket-fd 6 -xen-domid-restrict -chroot /var/xen/qemu/root-11 -runas 65546.1006
4 S root     32475     1  0  80   0 -  4200 pipe_w 17:29 ?        00:00:00 logger -p daemon.info -t qemu-dm-13[32499]
6 S 65548    32499 32475  3  80   0 - 45677 poll_s 17:29 ?        00:00:25 qemu-dm-13 -machine pc-0.10,accel=xen,max-ram-below-4g=4026531840,allow-unassigned=true,trad_compat=true -vnc unix:/var/run/xen/vnc-13,lock-key-sync=off -incoming fd:4 -monitor null -xen-domid 13 -m size=1024 -boot order=cdn -usb -device usb-tablet,port=2 -smp 1,maxcpus=24 -serial pty -display none -nodefaults -trace enable=xen_platform_log -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=deny,resourcecontrol=deny -S -global PIIX4_PM.revision_id=0x1 -global ide-hd.ver=0.10.2 -global piix3-ide-xen.subvendor_id=0x5853 -global piix3-ide-xen.subsystem_id=0x0001 -global piix3-usb-uhci.subvendor_id=0x5853 -global piix3-usb-uhci.subsystem_id=0x0001 -global rtl8139.subvendor_id=0x5853 -global rtl8139.subsystem_id=0x0001 -parallel null -qmp unix:/var/run/xen/qmp-libxl-13,server,nowait -qmp unix:/var/run/xen/qmp-event-13,server,nowait -device xen-platform,addr=3,device-id=0x0001,revision=0x2,class-id=0x0100,subvendor_id=0x5853,subsystem_id=0x0001 -drive file=,if=ide,index=1,media=cdrom,force-lba=off -drive file=/dev/sm/backend/f6a05383-96e4-91ea-9bca-b6aa96d95919/720d227c-2b2e-4e8b-b598-eb0878db5bb9,if=ide,index=0,media=disk,force-lba=on,format=raw -device rtl8139,netdev=tapnet0,mac=ea:33:87:06:64:8a,addr=4 -netdev tap,id=tapnet0,fd=7 -device cirrus-vga,vgamem_mb=8,rombar=1,romfile=,subvendor_id=0x5853,subsystem_id=0x0001,addr=2 -vnc-clipboard-socket-fd 6 -xen-domid-restrict -chroot /var/xen/qemu/root-13 -runas 65548.1008

But one of it has a normal keymap in the console. Another gets a strange one, for example '&' mapped to '/' and '/' mapped to '-'.

Any one met the same issue?

What can I help to make XCP-ng 8.0 available sooner?

@olivierlambert Oh! I appreciate your plan.

And I am sorry again. "XCP" in my previous messages actually means XAPI project. Sorry.

@olivierlambert Sorry. Currently XenServer is the upstream of XCP-ng. And XCP-ng does not directly choose XCP package versions. XCP-ng will not make a new major release until XS released new version. How this can be improved? Can XCP-ng get rid of the XenServer stage? XenServer itself is composed from XCP packages or is a distribution of XCP. Can XCP-ng directly be based on XCP packages instead of XenServer? Or for comparing, should XCP-ng be the 'Fedora' of XCP instead of the 'CentOS' for XS?

Of course, being 'Fedora' of XCP requires a huge work. And QA is a big problem.

Should XCP-ng aim to be upstream? Like Debian/Fedora, XCP-ng maintains an unstable/cutting-edge branch that directly follow each XCP package?

@stormi I am watching you.

@Ruskofff There are already some modules about XenServer within Ansibe sources. Just find 'xenserver'. I hope you can use them as start point.

There is binary rpm but not src rpm.

We has been customising XenServer for our need. And now we are rebasing our work on XCP-ng. So we sometimes need to rebuild packages that even XCP-ng doesn't have to customise.

ocaml-xenops should produce three binary packages. But only ocaml-xenops-tools is available.

How XCP-ng keep tracking of rebuild due to updated of dependency? That means if A requires B, and B is updated. How XCP-np decides whether and when to rebuild A?

Since there is no official mirror for ISOs, it is hard to download the ISOs in some special region of Internet.
A good solution is to provide official bt seed for ISOs and is a common practice of Linux distros.
Like Fedora, all the iso bt seeds are available here https://torrent.fedoraproject.org/ .

@buzzzo Most for integration with different distributed storage providers. And it is kind of dayjob and not quite possible to be open sourced.

We are working on new SR type and a few modification to upstream code. Despite the work is far from mature to merge upstream, we want to rely on the work of XCP-ng. And we found multiple core XCP packages like xapi, xenopsd available under https://github.com/xcp-ng-rpms. But 'sm' is missing. And if needed, I am happy to help bootstrapping the repo.

We are working on a modification of sm. But there is no repo under https://github.com/xcp-ng-rpms.