Vagrant gets segmentation fault when trying to add USB
I got a simple Vagrantfile that uses archlinux/archlinux and is trying to access a usb that is connected to my host. When I do vagrant up I get an error like this:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "VAGRANT-ID",
"--machinereadable"]
Stderr:
If I check it with vboxmanage showvminfo VAGRANT-ID --machinereadable I get a segmentation fault like this:
...
USBFilterManufacturer2=""
USBFilterProduct2=""
USBFilterRemote2=""
USBFilterSerialNumber2=""
[1] 9658 segmentation fault (core dumped) vboxmanage showvminfo
VAGRANT-ID --machinereadable
The lines I use in my Vagrantfile that tries to access the USB.
vb.customize ["modifyvm", :id, "--usb", "on"]
vb.customize ["modifyvm", :id, "--usbehci", "on"]
vb.customize ['usbfilter', 'add', '0', '--target', :id, '--name',
'usb', '--vendorid', 'VENDOR-ID-HEX', '--productid', 'PRODUCT-ID-HEX']
My host OS is Fedora 29, Virtualbox version is 6.0 and Vagrant 2.2.3.
Something I've tried:
Removed the .vagrent folder and did vagrant up,
Added
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
to the /etc/sudoers file
Use the
vboxmanage usbfilter add 0 --taget VAGRANT-ID --name usb
--vendorid VENDOR-ID-HEX --productid PRODUCT-ID-HEX
(and that gave no error).
Thank you in advance.
linux usb virtualbox vagrant
asked Jan 22 at 22:48
DeggoDeggo
62
This question has an open bounty worth +50
reputation from peterh ending in 2 days.
This question has not received enough attention.
add a comment |
I got a simple Vagrantfile that uses archlinux/archlinux and is trying to access a usb that is connected to my host. When I do vagrant up I get an error like this:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "VAGRANT-ID",
"--machinereadable"]
Stderr:
If I check it with vboxmanage showvminfo VAGRANT-ID --machinereadable I get a segmentation fault like this:
...
USBFilterManufacturer2=""
USBFilterProduct2=""
USBFilterRemote2=""
USBFilterSerialNumber2=""
[1] 9658 segmentation fault (core dumped) vboxmanage showvminfo
VAGRANT-ID --machinereadable
The lines I use in my Vagrantfile that tries to access the USB.
vb.customize ["modifyvm", :id, "--usb", "on"]
vb.customize ["modifyvm", :id, "--usbehci", "on"]
vb.customize ['usbfilter', 'add', '0', '--target', :id, '--name',
'usb', '--vendorid', 'VENDOR-ID-HEX', '--productid', 'PRODUCT-ID-HEX']
My host OS is Fedora 29, Virtualbox version is 6.0 and Vagrant 2.2.3.
Something I've tried:
Removed the .vagrent folder and did vagrant up,
Added
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
to the /etc/sudoers file
Use the
vboxmanage usbfilter add 0 --taget VAGRANT-ID --name usb
--vendorid VENDOR-ID-HEX --productid PRODUCT-ID-HEX
(and that gave no error).
Thank you in advance.
linux usb virtualbox vagrant
asked Jan 22 at 22:48
DeggoDeggo
62
This question has an open bounty worth +50
reputation from peterh ending in 2 days.
This question has not received enough attention.
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
I got a simple Vagrantfile that uses archlinux/archlinux and is trying to access a usb that is connected to my host. When I do vagrant up I get an error like this:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "VAGRANT-ID",
"--machinereadable"]
Stderr:
If I check it with vboxmanage showvminfo VAGRANT-ID --machinereadable I get a segmentation fault like this:
...
USBFilterManufacturer2=""
USBFilterProduct2=""
USBFilterRemote2=""
USBFilterSerialNumber2=""
[1] 9658 segmentation fault (core dumped) vboxmanage showvminfo
VAGRANT-ID --machinereadable
The lines I use in my Vagrantfile that tries to access the USB.
vb.customize ["modifyvm", :id, "--usb", "on"]
vb.customize ["modifyvm", :id, "--usbehci", "on"]
vb.customize ['usbfilter', 'add', '0', '--target', :id, '--name',
'usb', '--vendorid', 'VENDOR-ID-HEX', '--productid', 'PRODUCT-ID-HEX']
My host OS is Fedora 29, Virtualbox version is 6.0 and Vagrant 2.2.3.
Something I've tried:
Removed the .vagrent folder and did vagrant up,
Added
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
to the /etc/sudoers file
Use the
vboxmanage usbfilter add 0 --taget VAGRANT-ID --name usb
--vendorid VENDOR-ID-HEX --productid PRODUCT-ID-HEX
(and that gave no error).
Thank you in advance.
linux usb virtualbox vagrant
asked Jan 22 at 22:48
DeggoDeggo
62
I got a simple Vagrantfile that uses archlinux/archlinux and is trying to access a usb that is connected to my host. When I do vagrant up I get an error like this:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "VAGRANT-ID",
"--machinereadable"]
Stderr:
If I check it with vboxmanage showvminfo VAGRANT-ID --machinereadable I get a segmentation fault like this:
...
USBFilterManufacturer2=""
USBFilterProduct2=""
USBFilterRemote2=""
USBFilterSerialNumber2=""
[1] 9658 segmentation fault (core dumped) vboxmanage showvminfo
VAGRANT-ID --machinereadable
The lines I use in my Vagrantfile that tries to access the USB.
vb.customize ["modifyvm", :id, "--usb", "on"]
vb.customize ["modifyvm", :id, "--usbehci", "on"]
vb.customize ['usbfilter', 'add', '0', '--target', :id, '--name',
'usb', '--vendorid', 'VENDOR-ID-HEX', '--productid', 'PRODUCT-ID-HEX']
My host OS is Fedora 29, Virtualbox version is 6.0 and Vagrant 2.2.3.
Something I've tried:
Removed the .vagrent folder and did vagrant up,
Added
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
to the /etc/sudoers file
Use the
vboxmanage usbfilter add 0 --taget VAGRANT-ID --name usb
--vendorid VENDOR-ID-HEX --productid PRODUCT-ID-HEX
(and that gave no error).
Thank you in advance.
linux usb virtualbox vagrant
linux usb virtualbox vagrant
asked Jan 22 at 22:48
DeggoDeggo
62
asked Jan 22 at 22:48
DeggoDeggo
62
asked Jan 22 at 22:48
DeggoDeggo
62
asked Jan 22 at 22:48
DeggoDeggo
62
asked Jan 22 at 22:48
DeggoDeggo
62
62
This question has an open bounty worth +50
reputation from peterh ending in 2 days.
This question has not received enough attention.
This question has an open bounty worth +50
reputation from peterh ending in 2 days.
This question has not received enough attention.
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
1 Answer
1
active
oldest
votes
I found a solution.
It is not a Vagrant problem, it is a Virtualbox problem. As you can see, also a
vboxmanage showvminfo <uuid>
causes a segfault, which is visible on Linux. In my experiments, it was not visible in the Windows command line, but probably it can be debugged also there.
Vagrant, if it is used to manage Virtualbox containers, is essentially a big ruby script around vboxmanage. It can detect that vboxmanage fails by its unordinary exit code, but it doesn't know too much from its reason.
The bug is in the vboxmanage binary, not in one of the internal virtualbox libraries what it is using.
The problem can be found in the public VirtualBox bugtracker here.
A fix was implemented with test build 128880, but it wasn't released yet. Until we don't have a new release, we need to use the test build.
If the test build - as an internal development version - doesn't work, there is an option to extract only vboxmanage from that, and using it with the latest stable. This scenario worked for me both on Windows and Linux.
Hopefully a release will happen soon.
answered Mar 7 at 18:07
peterhpeterh
1,37582238
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397203%2fvagrant-gets-segmentation-fault-when-trying-to-add-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found a solution.
It is not a Vagrant problem, it is a Virtualbox problem. As you can see, also a
vboxmanage showvminfo <uuid>
causes a segfault, which is visible on Linux. In my experiments, it was not visible in the Windows command line, but probably it can be debugged also there.
Vagrant, if it is used to manage Virtualbox containers, is essentially a big ruby script around vboxmanage. It can detect that vboxmanage fails by its unordinary exit code, but it doesn't know too much from its reason.
The bug is in the vboxmanage binary, not in one of the internal virtualbox libraries what it is using.
The problem can be found in the public VirtualBox bugtracker here.
A fix was implemented with test build 128880, but it wasn't released yet. Until we don't have a new release, we need to use the test build.
If the test build - as an internal development version - doesn't work, there is an option to extract only vboxmanage from that, and using it with the latest stable. This scenario worked for me both on Windows and Linux.
Hopefully a release will happen soon.
answered Mar 7 at 18:07
peterhpeterh
1,37582238
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
I found a solution.
It is not a Vagrant problem, it is a Virtualbox problem. As you can see, also a
vboxmanage showvminfo <uuid>
causes a segfault, which is visible on Linux. In my experiments, it was not visible in the Windows command line, but probably it can be debugged also there.
Vagrant, if it is used to manage Virtualbox containers, is essentially a big ruby script around vboxmanage. It can detect that vboxmanage fails by its unordinary exit code, but it doesn't know too much from its reason.
The bug is in the vboxmanage binary, not in one of the internal virtualbox libraries what it is using.
The problem can be found in the public VirtualBox bugtracker here.
A fix was implemented with test build 128880, but it wasn't released yet. Until we don't have a new release, we need to use the test build.
If the test build - as an internal development version - doesn't work, there is an option to extract only vboxmanage from that, and using it with the latest stable. This scenario worked for me both on Windows and Linux.
Hopefully a release will happen soon.
answered Mar 7 at 18:07
peterhpeterh
1,37582238
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
I found a solution.
It is not a Vagrant problem, it is a Virtualbox problem. As you can see, also a
vboxmanage showvminfo <uuid>
causes a segfault, which is visible on Linux. In my experiments, it was not visible in the Windows command line, but probably it can be debugged also there.
Vagrant, if it is used to manage Virtualbox containers, is essentially a big ruby script around vboxmanage. It can detect that vboxmanage fails by its unordinary exit code, but it doesn't know too much from its reason.
The bug is in the vboxmanage binary, not in one of the internal virtualbox libraries what it is using.
The problem can be found in the public VirtualBox bugtracker here.
A fix was implemented with test build 128880, but it wasn't released yet. Until we don't have a new release, we need to use the test build.
If the test build - as an internal development version - doesn't work, there is an option to extract only vboxmanage from that, and using it with the latest stable. This scenario worked for me both on Windows and Linux.
Hopefully a release will happen soon.
answered Mar 7 at 18:07
peterhpeterh
1,37582238
I found a solution.
It is not a Vagrant problem, it is a Virtualbox problem. As you can see, also a
vboxmanage showvminfo <uuid>
causes a segfault, which is visible on Linux. In my experiments, it was not visible in the Windows command line, but probably it can be debugged also there.
Vagrant, if it is used to manage Virtualbox containers, is essentially a big ruby script around vboxmanage. It can detect that vboxmanage fails by its unordinary exit code, but it doesn't know too much from its reason.
The bug is in the vboxmanage binary, not in one of the internal virtualbox libraries what it is using.
The problem can be found in the public VirtualBox bugtracker here.
A fix was implemented with test build 128880, but it wasn't released yet. Until we don't have a new release, we need to use the test build.
If the test build - as an internal development version - doesn't work, there is an option to extract only vboxmanage from that, and using it with the latest stable. This scenario worked for me both on Windows and Linux.
Hopefully a release will happen soon.
answered Mar 7 at 18:07
peterhpeterh
1,37582238
edited Mar 8 at 13:34
answered Mar 7 at 18:07
peterhpeterh
1,37582238
answered Mar 7 at 18:07
peterhpeterh
1,37582238
answered Mar 7 at 18:07
peterhpeterh
1,37582238
1,37582238
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397203%2fvagrant-gets-segmentation-fault-when-trying-to-add-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If there is a better answer than mine, I will give the bounty to it.
– peterh
Mar 7 at 18:07