Closed danielschonfeld closed 8 years ago
UPDATE: I have found out that the above error was the result of me moving the VM from a non pool master to the master machine, and XenServer not moving along the VM's Automatic Config Drive
along with it. Rather the drive stayed on the original host the VM was created on.
As a result the exported ISO file to the /tmp directory had a byte size of 0 bytes.
However, I've noticed a similar problem when trying to load up Properties on a VM that is hosted on a non pool master. It's a very similar problem to the one above, with the ISO file being exported and created on the master machine, not on the machine where the VM is hosted, with a size of 0 bytes. As a result, no errors are generated but XenCenter just keeps spinning and hanging and never being able to load the cloud-config.
Thanks for reporting this, and also the fix in #15. It's an interesting bug, as it can only be seen when local storage is being used. I'll try to reproduce the behavior that you see when I get a free minute. That XenServer isn't moving the Automatic Config Drive sounds rather odd and I am not quite sure what may be causing this.
Best wishes, Robert
All flavors of this bug should be properly resolved by a combination of the above with the following Toolstack fixes: https://github.com/xapi-project/xen-api/commit/466afdfe103a58c502fcd5c6e6a1f538b4158ee9 https://github.com/xapi-project/xen-api/commit/c68cabcb6fbb284d37cf430a564dff715353e947 https://github.com/xapi-project/xen-api/commit/ebd0b2c19bad96fd3ff88c26b21d4945c90f7aad
It appears that reading the cloud-config is the reason for this, I get the following inside xsconstainer.log
Interesting to note that even though above it says something about wrong FS type etc, the VM loads just fine with the cloud-config file being the one i expect and it mounts just fine.
So this problem is limited to trying to open that virtual disk only when calling
get_config_drive_configuration