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

Enable more than one block device in VM #419

Closed
marmarek opened this Issue Mar 8, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by marmarek on 16 Jan 2012 11:59 UTC
To make possible attaching eg two pendrives.
Perhaps using ConsoleKit/PolicyKit it is already done. But needs testing.

If not needed - perhaps also remove /mnt/removable fstab entry.

Migrated-From: https://wiki.qubes-os.org/ticket/419

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 18 Jan 2012 13:50 UTC
I just verified that one can remove:

/dev/xvdi   /mnt/removable  auto noauto,user,rw 0 0

line from fstab, and qvm-block attach still works fine.

But an attempt to attach more than one device causes this:

[~](joanna@dom0)$ qvm-block -a dom0:sdd personal
Traceback (most recent call last):
  File "/usr/bin/qvm-block", line 114, in <module>
    main()
  File "/usr/bin/qvm-block", line 81, in main
    block_attach(vm, backend_vm, dev['device'], **kwargs)
  File "/usr/lib64/python2.6/site-packages/qubes/qubesutils.py", line 203, in block_attach
    raise QubesException("Frontend %s busy in VM %s, detach it first" % (frontend, vm.name))
qubes.qubes.QubesException: Frontend xvdi busy in VM personal, detach it first

Member

marmarek commented Mar 8, 2015

Comment by joanna on 18 Jan 2012 13:50 UTC
I just verified that one can remove:

/dev/xvdi   /mnt/removable  auto noauto,user,rw 0 0

line from fstab, and qvm-block attach still works fine.

But an attempt to attach more than one device causes this:

[~](joanna@dom0)$ qvm-block -a dom0:sdd personal
Traceback (most recent call last):
  File "/usr/bin/qvm-block", line 114, in <module>
    main()
  File "/usr/bin/qvm-block", line 81, in main
    block_attach(vm, backend_vm, dev['device'], **kwargs)
  File "/usr/lib64/python2.6/site-packages/qubes/qubesutils.py", line 203, in block_attach
    raise QubesException("Frontend %s busy in VM %s, detach it first" % (frontend, vm.name))
qubes.qubes.QubesException: Frontend xvdi busy in VM personal, detach it first

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 18 Jan 2012 14:05 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 18 Jan 2012 14:05 UTC

@marmarek marmarek removed this from the Release 1 Beta 3 milestone Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 18 Jan 2012 14:06 UTC
Currently qvm-block don't automatically choose block front device. You can use -f option to do this.

Because there is no need to use always xvdi (as you said above), qvm-block can choose any device name.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 18 Jan 2012 14:06 UTC
Currently qvm-block don't automatically choose block front device. You can use -f option to do this.

Because there is no need to use always xvdi (as you said above), qvm-block can choose any device name.

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment