After detaching an ssd drive from a a qube, the device will then not attach to another qube unless I reboot.
WARNING: protocol error for call b’admin.vm.device.block.Attach’+b’dom0+sdb1:0000:0000::?******:None:1’ (b’dom0’ → b’disp3973’) with payload of 132 bytes
before that i can see several lines of
xen:grant_table: g.e. 0x2e still pending
but not sure if they are relevant.
4.3rc3
I have the exact same issue, with the same error message in journalctl. It started to happen after my upgrade from 4.2 to 4.3. There’s definitely something wrong here.
Did you detached the device before trying to attach to another qube? When done via devices widget, it should happen automatically.
I’m also experiencing this issue, present only in 4.3.
In 4.2, the device would return availability for re-attaching whether manually detached or done so from the shutdown of the VM.
In 4.3, in all circumstances including manually detaching, I see the protocol error appear in dom0 and it doesn’t work until restarted.
As an example, upon detaching sdb1 never reappears in the statusbar/usb attachment dropdown. It is highly reproducible; is there anything I can provide that would demonstrate this?
Also, this happens only on ssds (so in my case, sdbX)–all USB devices operate as-expected, whether detached beforehand or through domU shutdown.