-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with secondary and up devices #550
Comments
Really strange, the relevant code is:
As you can see from disk2 and higher I assign address 0x5 and up. Maybe it is caused by this lower addresses? You could try replacing 0x5 by 0xd and see if it makes a difference? I cannot test this myself as I have no spare disk devices on my system. |
I'll try it. |
I looked into this again, and to start: these The first possibility is that vDSM only has support for one physical drive (in which case there is nothing we can do about it), but this term One thing I noticed is that in Another thing that could be the issue is that each disk gets its own controller, and maybe vDSM excepts all the drives to be connected to the same controller. So instead of having multiple |
Thank you @kroese . Very usefull information. I'll try to test then with the |
Now I think about it.. as you said changing So the only difference between using Boot drive = 0xA So normally the addresses are in increasing order. Maybe vDSM does not expect to have a drive that has a lower number than the previous drives? Can you try with this https://raw.githubusercontent.com/vdsm/virtual-dsm/scsi/src/disk.sh |
I'll check asap. Please stay on hold. |
Hi @kroese , You are the master! It works like a charm! Tested with config:
And now the container starts without troubles and only the three devices are used. Congratulations! I hope you'll merge it soon. I'll check with a new install without DISK_SIZE, ALLOCATE and DISK_FMT. The idea is to not create the initial disk image. Or almost create it empty with the minimum data and after don't use it at all. 😉 |
Fixed by #552 |
Hi @kroese ,
When using DEVICES only the first one works. When you connect DEVICE2 until DEVICE6, the qemu driver seems to have some trouble with the controller and prints this:
And then the disk is not attached.
You can check it using only one device. Change from this:
that will work, to this:
And then you'll see the trouble (with DEVICE2 or DEVICE6 or anything else).
The text was updated successfully, but these errors were encountered: