XCP-ng 7.5.0 final is here



  • Ok migration of W2K8R2 with 6.2 drivers from XCP-ng 7.5 to XCP-ng 7.5 failed with msg:

    Storage_Interface.Does_not_exist(_)

    It also crashed the VM.

    I think this could be related to https://bugs.xenserver.org/browse/XSO-785 as there is only 10GB free on the source storage repository so I don't think I can actually do the migration because of that (it's recommended to have 2x space available to migrate a VM, something that becomes increasingly harder with large VMs!).


  • administrators

    Ah damn! I think you spotted the issue then!



  • @olivierlambert said in XCP-ng 7.5.0 final is here:

    Ah damn! I think you spotted the issue then!

    I think that is different to the original problem as there was enough disk space in that instance, but this non-production VM I was using to test doesn't have the space on the source host.

    New problem I've come across since doing that failed migration, the message-switch process is now eating approx half of the memory on the server:

    [root@host log]# free -m
    total used free shared buff/cache available
    Mem: 1923 1601 27 12 295 221
    Swap: 511 26 485
    [root@host log]# ps axuww | grep message
    root 1920 0.2 52.4 1094032 1033144 ? Ssl Aug16 2:36 /usr/sbin/message-switch --config /etc/message-switch.conf
    root 32669 0.0 0.1 112656 2232 pts/24 S+ 12:43 0:00 grep --color=auto message

    Anyone know how to restart that?


  • administrators

    Restart the toolstack?



  • Hm.. I did a toolstack restart and it still had the high memory usage after, but it has now since dropped..

    root 1920 0.2 2.0 108860 39516 ? Ssl Aug16 2:39 /usr/sbin/message-switch --config /etc/message-switch.conf

    Perhaps it takes a bit of time to clear it out.



  • @olivierlambert said in XCP-ng 7.5.0 final is here:

    Yeah but 7.4 won't be maintained, so it would be better to try to see if it's a XS issue or not.

    My bleeding edge attempt has been dulled. I'll try again later after seeing if the root cause is identified.



  • Hi
    Has there been any update on this please?

    Just tried updating our pool and after updating the master had failed migration of VM (Ubuntu) and then was unable to get VM to start (Missing VDI error). Only solution was to roll master back to 7.4 and everything working again.

    Thanks


  • administrators

    Sorry on what exactly? Maybe it could be better to create a dedicated topic to see more clearly 🙂



  • @dblogic said in XCP-ng 7.5.0 final is here:

    Just tried updating our pool and after updating the master had failed migration of VM (Ubuntu) and then was unable to get VM to start (Missing VDI error). Only solution was to roll master back to 7.4 and everything working again.

    I ran into a similar situation when I upgraded to 7.5 this week. Did you check to see if there was a non-existent ISO mounted in the CD rom for the VM in question?



  • Hi. Apologies for delay in responding.
    Yes I did check for that and there was none. It occurred on at least 2 VMS I tried. In one case just shutting a VM down and trying to restart gave the missing vdi error. Everything I checked (with my limited knowledge of the CLI) looked fine. As soon as I rolled back to 7.4 on the master the VMS started without any issue.
    Its as if the upgrade applied some schema changes to the vdi linking in some way perhaps?

    I did try a second time just updating the master but with the same result - stopping and trying to restart a VM on any host (we have 4) gave the vdi missing error. Again rollling back fixed the problem but leaves me worried about upgrading.