Skip to content

Document how to enable verbose log messages for tapback #128

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: xs64bit
Choose a base branch
from
Open

Document how to enable verbose log messages for tapback #128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,5 +118,20 @@ xm block-attach 0 tap:qcow:<FILENAME> /dev/xvda1 w 0
mount /dev/xvda1 /mnt/disk


Enabling verbose log messages for tapback
=========================================

As of blktap3, the establishment of a connection between blkfront and a tap
disk is handled by tapback.

When needed, tapback can be configured to print verbose log messages. To do
that, edit /etc/init.d/tapback and ensure tapback is started with the '-v'
option, like this:

${TAPBACK} -v -p ${PID_FILE} >/dev/null 2>&1 </dev/null

Then, restart the tapback service:

service tapback restart