@KB973 Hello, thanks for the details. Regarding migration we are aware of issues in the lock system to resume a VM after migration. Often a lock is locked by SR.scan. We can't easily patch in V1.
Also do you have the same issues using a default MTU (1500)?
@samuelolavo Hello,
Could the fact that this is a local LVM SR on a non-master host be relevant to how make_chain_rw is being handled?
Yes, it's indeed what's happening. The check for the SRMaster (for a shared SR it's the master but for a local it's supposed to be done on the host directly) is failing and always saying False. I'll fix this.
Thank you for the help 
@samuelolavo Hello,
It is indeed linked to QCOW2.
Is mixing VHD and QCOW2 VDIs on the same VM and on the same SR fully supported?
Yes, it's supposed to work.
Are there specific minimum versions of xapi, sm, blktap, or other storage components required for large QCOW2 VDIs?
Yes, but we would prefer for people to be uptodate, we have been fixing things.
But I don't think it's a problem for you at the moment.
make_chain_rw is necessary for the master to make the QCOW2 LV RW at the VDI activation time. So it's likely linked to this particular QCOW2.
make_chain_rw is executed on the master host and is logging in /var/log/SMlog, could you take a look at what it's erroring on?
Hello @mike.potapov , We found a race-condition happening on Qcow2 driver that explains this issue. We developed a fix that will be ship in the next release of blktap.
It might be worth adding a message in XO at export, or in the documentation ?
@Dan Hello,
So our investigation found that this change was introduced with commit https://github.com/xcp-ng/sm/commit/00637dd52e845d6016add9718fc9cc694aec9f0d
It was aimed at EXTSR in particular, it appear that the first SR to be plugged is the one choosing the mode of sr-mount since util.makedirs also create the parent directory with the given mode.
I have created a card for the issue on our side.
@Dan Hello,
I can't answer from memory, we'll take a look at this and come back to you
Thanks for the report, I guess it could be considered a bug since even it's one of the other, it's not the expected behaviour to have the mode change between runs.
@irtaza9 Hello, could you share the content of your logs during the SR creation with us to investigate on our side ?
You can produce a tar of logs with https://docs.xcp-ng.org/troubleshooting/log-files/#produce-a-status-report .
|
0
Posts
0
Reputation
|
|
3
Posts
2
Reputation
|
