[qubes-users] Re: 4.0.1 persistent external LVM block device attach
Got around to checking and this issue has been open for over a year: https://github.com/QubesOS/qubes-issues/issues/3437 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9f7.5c50cc77%40qubes-os.info. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: 4.0.1 persistent external LVM block device attach
Yes qvm-block does not accept any symlink, (mapper/..., disk/by-uuid/... or -L , -U flags like mount) so will open the issue and there is a *possible* related issue that a non existent device fail of qube start may happen if the device is not up yet, since they obviously happen in parallel. Can't test now. Any ideas for a hack? Also noticed that the front device spec is NOT optional for persistent attaches (if there are more than one) as they will all try to grab xvdi on qube start with the second one (not necessarily the second one originally entered) causing a failure - unlike typing the attach commands into dom0. Separate issue (check on entry) or just doc update? Needs man update. Thanks, Eric -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/938.5c490910%40qubes-os.info. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: 4.0.1 persistent external LVM block device attach
On Tuesday, January 22, 2019 at 2:26:16 PM UTC-5, Eric wrote: > qvm-block does not accept a UUID (not documented > and gives an error: not exposed) I suspect that > should be added as an issue. [Out of curiosity, I ask, since I am away from the Qubes systems at the moment:] By "qvm-block does not accept a UUID", may I interpret that to mean "cannot utilize a source device using the link in the sub-tree: /dev/disk/by-id "? If so, that would be worth opening an issue for in qubes-issues, I think. From what I can glean from docs, xl block-attach and virsh attach-disk both support the source being a symbolic link to the real device at the /dev level (and I believe qvm-block is based on virsh and/or libvirt, which utilizes xl block-* in the back-end). Brendan -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0fead00a-fd09-4ee8-a5ea-fec889620d5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
