libvirt-bin error on a VM when I try to list VM

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I'm using Virtualbox 4.3.18 on my Arch Linux Host machine and libvirt-bin 1.2.9 on my Ubuntu Server Cloud guest machine. Everytime I try to follow this tutorial I receive the following error when I run virsh:



Command:



virsh -c vbox+ssh://leandro@10.0.3.15/system list --all


Error:



error: failed to connect to the hypervisor
error: internal error: unable to initialize VirtualBox driver API


Someone know how to fix this?










share|improve this question













migrated from serverfault.com Oct 17 '14 at 19:58


This question came from our site for system and network administrators.


















  • Can you ssh to the IP address 10.0.3.15 as the user leandro?

    – slm
    Oct 17 '14 at 21:39











  • Yes, I can ssh to his IP.

    – Leandro
    Oct 17 '14 at 23:55















1















I'm using Virtualbox 4.3.18 on my Arch Linux Host machine and libvirt-bin 1.2.9 on my Ubuntu Server Cloud guest machine. Everytime I try to follow this tutorial I receive the following error when I run virsh:



Command:



virsh -c vbox+ssh://leandro@10.0.3.15/system list --all


Error:



error: failed to connect to the hypervisor
error: internal error: unable to initialize VirtualBox driver API


Someone know how to fix this?










share|improve this question













migrated from serverfault.com Oct 17 '14 at 19:58


This question came from our site for system and network administrators.


















  • Can you ssh to the IP address 10.0.3.15 as the user leandro?

    – slm
    Oct 17 '14 at 21:39











  • Yes, I can ssh to his IP.

    – Leandro
    Oct 17 '14 at 23:55













1












1








1








I'm using Virtualbox 4.3.18 on my Arch Linux Host machine and libvirt-bin 1.2.9 on my Ubuntu Server Cloud guest machine. Everytime I try to follow this tutorial I receive the following error when I run virsh:



Command:



virsh -c vbox+ssh://leandro@10.0.3.15/system list --all


Error:



error: failed to connect to the hypervisor
error: internal error: unable to initialize VirtualBox driver API


Someone know how to fix this?










share|improve this question














I'm using Virtualbox 4.3.18 on my Arch Linux Host machine and libvirt-bin 1.2.9 on my Ubuntu Server Cloud guest machine. Everytime I try to follow this tutorial I receive the following error when I run virsh:



Command:



virsh -c vbox+ssh://leandro@10.0.3.15/system list --all


Error:



error: failed to connect to the hypervisor
error: internal error: unable to initialize VirtualBox driver API


Someone know how to fix this?







ssh virtualbox openstack arch-linux virsh






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 17 '14 at 19:52









LeandroLeandro

1063




1063




migrated from serverfault.com Oct 17 '14 at 19:58


This question came from our site for system and network administrators.









migrated from serverfault.com Oct 17 '14 at 19:58


This question came from our site for system and network administrators.














  • Can you ssh to the IP address 10.0.3.15 as the user leandro?

    – slm
    Oct 17 '14 at 21:39











  • Yes, I can ssh to his IP.

    – Leandro
    Oct 17 '14 at 23:55

















  • Can you ssh to the IP address 10.0.3.15 as the user leandro?

    – slm
    Oct 17 '14 at 21:39











  • Yes, I can ssh to his IP.

    – Leandro
    Oct 17 '14 at 23:55
















Can you ssh to the IP address 10.0.3.15 as the user leandro?

– slm
Oct 17 '14 at 21:39





Can you ssh to the IP address 10.0.3.15 as the user leandro?

– slm
Oct 17 '14 at 21:39













Yes, I can ssh to his IP.

– Leandro
Oct 17 '14 at 23:55





Yes, I can ssh to his IP.

– Leandro
Oct 17 '14 at 23:55










1 Answer
1






active

oldest

votes


















0














Your installation of libvirtd needs to be configured to handle the vbox+ssh connection type. Details on how to do this are covered here, titled: VirtualBox hypervisor driver.



There's a sample domain XML config that you'll need to load into libvirtd so that it knows how to talk to the VirtualBox VM.



excerpt - sample config

<domain type='vbox'>
<name>vbox</name>
<uuid>4dab22b31d52d8f32516782e98ab3fa0</uuid>

<os>
<type>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<boot dev='fd'/>
<boot dev='network'/>
</os>

<memory>654321</memory>
<vcpu>1</vcpu>

<features>
<pae/>
<acpi/>
<apic/>
</features>

<devices>
<disk type='file' device='cdrom'>
<source file='/home/user/Downloads/slax-6.0.9.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>

<disk type='file' device='disk'>
<source file='/home/user/tmp/vbox.vdi'/>
<target dev='hdd'/>
</disk>

<disk type='file' device='floppy'>
<source file='/home/user/tmp/WIN98C.IMG'/>
<target dev='fda'/>
</disk>

<filesystem type='mount'>
<source dir='/home/user/stuff'/>
<target dir='my-shared-folder'/>
</filesystem>

<!--BRIDGE-->
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<model type='am79c973'/>
</interface>

<!--NAT-->
<interface type='user'>
<mac address='56:16:3e:5d:c7:9e'/>
<model type='82540eM'/>
</interface>

<sound model='sb16'/>

<parallel type='dev'>
<source path='/dev/pts/1'/>
<target port='0'/>
</parallel>

<parallel type='dev'>
<source path='/dev/pts/2'/>
<target port='1'/>
</parallel>

<serial type="dev">
<source path="/dev/ttyS0"/>
<target port="0"/>
</serial>

<serial type="pipe">
<source path="/tmp/serial.txt"/>
<target port="1"/>
</serial>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x1234'/>
<product id='0xbeef'/>
</source>
</hostdev>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x4321'/>
<product id='0xfeeb'/>
</source>
</hostdev>
</devices>
</domain>


Save this to a file, say my.xml, on your system and then use virsh to import it.



$ virsh create my.xml


NOTE: You'll also need the libvirt daemon driver installed. On Fedora 20 it's in a package called: libvirt-daemon-driver-vbox. You'll need libvirt-daemon along with the interface, libvirt-daemon-driver-interface. I would assume there are similar packages that provide these on ArchLinux.



References



KVM/Virsh - Ubuntu documentation






share|improve this answer

























  • I couldn't find any of this packages for Arch and Ubuntu.

    – Leandro
    Oct 17 '14 at 23:54











  • Their names will likely be different. Relax your searches using pacman. Look for libvirt.

    – slm
    Oct 18 '14 at 0:05











  • There are only 3 packages: libvirt, libvirt-glib and libvirt-python

    – Leandro
    Oct 18 '14 at 0:30












  • @Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

    – slm
    Oct 18 '14 at 0:39












  • Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

    – Leandro
    Oct 18 '14 at 0:41










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f162775%2flibvirt-bin-error-on-a-vm-when-i-try-to-list-vm%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









0














Your installation of libvirtd needs to be configured to handle the vbox+ssh connection type. Details on how to do this are covered here, titled: VirtualBox hypervisor driver.



There's a sample domain XML config that you'll need to load into libvirtd so that it knows how to talk to the VirtualBox VM.



excerpt - sample config

<domain type='vbox'>
<name>vbox</name>
<uuid>4dab22b31d52d8f32516782e98ab3fa0</uuid>

<os>
<type>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<boot dev='fd'/>
<boot dev='network'/>
</os>

<memory>654321</memory>
<vcpu>1</vcpu>

<features>
<pae/>
<acpi/>
<apic/>
</features>

<devices>
<disk type='file' device='cdrom'>
<source file='/home/user/Downloads/slax-6.0.9.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>

<disk type='file' device='disk'>
<source file='/home/user/tmp/vbox.vdi'/>
<target dev='hdd'/>
</disk>

<disk type='file' device='floppy'>
<source file='/home/user/tmp/WIN98C.IMG'/>
<target dev='fda'/>
</disk>

<filesystem type='mount'>
<source dir='/home/user/stuff'/>
<target dir='my-shared-folder'/>
</filesystem>

<!--BRIDGE-->
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<model type='am79c973'/>
</interface>

<!--NAT-->
<interface type='user'>
<mac address='56:16:3e:5d:c7:9e'/>
<model type='82540eM'/>
</interface>

<sound model='sb16'/>

<parallel type='dev'>
<source path='/dev/pts/1'/>
<target port='0'/>
</parallel>

<parallel type='dev'>
<source path='/dev/pts/2'/>
<target port='1'/>
</parallel>

<serial type="dev">
<source path="/dev/ttyS0"/>
<target port="0"/>
</serial>

<serial type="pipe">
<source path="/tmp/serial.txt"/>
<target port="1"/>
</serial>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x1234'/>
<product id='0xbeef'/>
</source>
</hostdev>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x4321'/>
<product id='0xfeeb'/>
</source>
</hostdev>
</devices>
</domain>


Save this to a file, say my.xml, on your system and then use virsh to import it.



$ virsh create my.xml


NOTE: You'll also need the libvirt daemon driver installed. On Fedora 20 it's in a package called: libvirt-daemon-driver-vbox. You'll need libvirt-daemon along with the interface, libvirt-daemon-driver-interface. I would assume there are similar packages that provide these on ArchLinux.



References



KVM/Virsh - Ubuntu documentation






share|improve this answer

























  • I couldn't find any of this packages for Arch and Ubuntu.

    – Leandro
    Oct 17 '14 at 23:54











  • Their names will likely be different. Relax your searches using pacman. Look for libvirt.

    – slm
    Oct 18 '14 at 0:05











  • There are only 3 packages: libvirt, libvirt-glib and libvirt-python

    – Leandro
    Oct 18 '14 at 0:30












  • @Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

    – slm
    Oct 18 '14 at 0:39












  • Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

    – Leandro
    Oct 18 '14 at 0:41















0














Your installation of libvirtd needs to be configured to handle the vbox+ssh connection type. Details on how to do this are covered here, titled: VirtualBox hypervisor driver.



There's a sample domain XML config that you'll need to load into libvirtd so that it knows how to talk to the VirtualBox VM.



excerpt - sample config

<domain type='vbox'>
<name>vbox</name>
<uuid>4dab22b31d52d8f32516782e98ab3fa0</uuid>

<os>
<type>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<boot dev='fd'/>
<boot dev='network'/>
</os>

<memory>654321</memory>
<vcpu>1</vcpu>

<features>
<pae/>
<acpi/>
<apic/>
</features>

<devices>
<disk type='file' device='cdrom'>
<source file='/home/user/Downloads/slax-6.0.9.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>

<disk type='file' device='disk'>
<source file='/home/user/tmp/vbox.vdi'/>
<target dev='hdd'/>
</disk>

<disk type='file' device='floppy'>
<source file='/home/user/tmp/WIN98C.IMG'/>
<target dev='fda'/>
</disk>

<filesystem type='mount'>
<source dir='/home/user/stuff'/>
<target dir='my-shared-folder'/>
</filesystem>

<!--BRIDGE-->
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<model type='am79c973'/>
</interface>

<!--NAT-->
<interface type='user'>
<mac address='56:16:3e:5d:c7:9e'/>
<model type='82540eM'/>
</interface>

<sound model='sb16'/>

<parallel type='dev'>
<source path='/dev/pts/1'/>
<target port='0'/>
</parallel>

<parallel type='dev'>
<source path='/dev/pts/2'/>
<target port='1'/>
</parallel>

<serial type="dev">
<source path="/dev/ttyS0"/>
<target port="0"/>
</serial>

<serial type="pipe">
<source path="/tmp/serial.txt"/>
<target port="1"/>
</serial>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x1234'/>
<product id='0xbeef'/>
</source>
</hostdev>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x4321'/>
<product id='0xfeeb'/>
</source>
</hostdev>
</devices>
</domain>


Save this to a file, say my.xml, on your system and then use virsh to import it.



$ virsh create my.xml


NOTE: You'll also need the libvirt daemon driver installed. On Fedora 20 it's in a package called: libvirt-daemon-driver-vbox. You'll need libvirt-daemon along with the interface, libvirt-daemon-driver-interface. I would assume there are similar packages that provide these on ArchLinux.



References



KVM/Virsh - Ubuntu documentation






share|improve this answer

























  • I couldn't find any of this packages for Arch and Ubuntu.

    – Leandro
    Oct 17 '14 at 23:54











  • Their names will likely be different. Relax your searches using pacman. Look for libvirt.

    – slm
    Oct 18 '14 at 0:05











  • There are only 3 packages: libvirt, libvirt-glib and libvirt-python

    – Leandro
    Oct 18 '14 at 0:30












  • @Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

    – slm
    Oct 18 '14 at 0:39












  • Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

    – Leandro
    Oct 18 '14 at 0:41













0












0








0







Your installation of libvirtd needs to be configured to handle the vbox+ssh connection type. Details on how to do this are covered here, titled: VirtualBox hypervisor driver.



There's a sample domain XML config that you'll need to load into libvirtd so that it knows how to talk to the VirtualBox VM.



excerpt - sample config

<domain type='vbox'>
<name>vbox</name>
<uuid>4dab22b31d52d8f32516782e98ab3fa0</uuid>

<os>
<type>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<boot dev='fd'/>
<boot dev='network'/>
</os>

<memory>654321</memory>
<vcpu>1</vcpu>

<features>
<pae/>
<acpi/>
<apic/>
</features>

<devices>
<disk type='file' device='cdrom'>
<source file='/home/user/Downloads/slax-6.0.9.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>

<disk type='file' device='disk'>
<source file='/home/user/tmp/vbox.vdi'/>
<target dev='hdd'/>
</disk>

<disk type='file' device='floppy'>
<source file='/home/user/tmp/WIN98C.IMG'/>
<target dev='fda'/>
</disk>

<filesystem type='mount'>
<source dir='/home/user/stuff'/>
<target dir='my-shared-folder'/>
</filesystem>

<!--BRIDGE-->
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<model type='am79c973'/>
</interface>

<!--NAT-->
<interface type='user'>
<mac address='56:16:3e:5d:c7:9e'/>
<model type='82540eM'/>
</interface>

<sound model='sb16'/>

<parallel type='dev'>
<source path='/dev/pts/1'/>
<target port='0'/>
</parallel>

<parallel type='dev'>
<source path='/dev/pts/2'/>
<target port='1'/>
</parallel>

<serial type="dev">
<source path="/dev/ttyS0"/>
<target port="0"/>
</serial>

<serial type="pipe">
<source path="/tmp/serial.txt"/>
<target port="1"/>
</serial>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x1234'/>
<product id='0xbeef'/>
</source>
</hostdev>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x4321'/>
<product id='0xfeeb'/>
</source>
</hostdev>
</devices>
</domain>


Save this to a file, say my.xml, on your system and then use virsh to import it.



$ virsh create my.xml


NOTE: You'll also need the libvirt daemon driver installed. On Fedora 20 it's in a package called: libvirt-daemon-driver-vbox. You'll need libvirt-daemon along with the interface, libvirt-daemon-driver-interface. I would assume there are similar packages that provide these on ArchLinux.



References



KVM/Virsh - Ubuntu documentation






share|improve this answer















Your installation of libvirtd needs to be configured to handle the vbox+ssh connection type. Details on how to do this are covered here, titled: VirtualBox hypervisor driver.



There's a sample domain XML config that you'll need to load into libvirtd so that it knows how to talk to the VirtualBox VM.



excerpt - sample config

<domain type='vbox'>
<name>vbox</name>
<uuid>4dab22b31d52d8f32516782e98ab3fa0</uuid>

<os>
<type>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<boot dev='fd'/>
<boot dev='network'/>
</os>

<memory>654321</memory>
<vcpu>1</vcpu>

<features>
<pae/>
<acpi/>
<apic/>
</features>

<devices>
<disk type='file' device='cdrom'>
<source file='/home/user/Downloads/slax-6.0.9.iso'/>
<target dev='hdc'/>
<readonly/>
</disk>

<disk type='file' device='disk'>
<source file='/home/user/tmp/vbox.vdi'/>
<target dev='hdd'/>
</disk>

<disk type='file' device='floppy'>
<source file='/home/user/tmp/WIN98C.IMG'/>
<target dev='fda'/>
</disk>

<filesystem type='mount'>
<source dir='/home/user/stuff'/>
<target dir='my-shared-folder'/>
</filesystem>

<!--BRIDGE-->
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<model type='am79c973'/>
</interface>

<!--NAT-->
<interface type='user'>
<mac address='56:16:3e:5d:c7:9e'/>
<model type='82540eM'/>
</interface>

<sound model='sb16'/>

<parallel type='dev'>
<source path='/dev/pts/1'/>
<target port='0'/>
</parallel>

<parallel type='dev'>
<source path='/dev/pts/2'/>
<target port='1'/>
</parallel>

<serial type="dev">
<source path="/dev/ttyS0"/>
<target port="0"/>
</serial>

<serial type="pipe">
<source path="/tmp/serial.txt"/>
<target port="1"/>
</serial>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x1234'/>
<product id='0xbeef'/>
</source>
</hostdev>

<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x4321'/>
<product id='0xfeeb'/>
</source>
</hostdev>
</devices>
</domain>


Save this to a file, say my.xml, on your system and then use virsh to import it.



$ virsh create my.xml


NOTE: You'll also need the libvirt daemon driver installed. On Fedora 20 it's in a package called: libvirt-daemon-driver-vbox. You'll need libvirt-daemon along with the interface, libvirt-daemon-driver-interface. I would assume there are similar packages that provide these on ArchLinux.



References



KVM/Virsh - Ubuntu documentation







share|improve this answer














share|improve this answer



share|improve this answer








edited Oct 17 '14 at 23:00

























answered Oct 17 '14 at 21:48









slmslm

250k66527684




250k66527684












  • I couldn't find any of this packages for Arch and Ubuntu.

    – Leandro
    Oct 17 '14 at 23:54











  • Their names will likely be different. Relax your searches using pacman. Look for libvirt.

    – slm
    Oct 18 '14 at 0:05











  • There are only 3 packages: libvirt, libvirt-glib and libvirt-python

    – Leandro
    Oct 18 '14 at 0:30












  • @Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

    – slm
    Oct 18 '14 at 0:39












  • Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

    – Leandro
    Oct 18 '14 at 0:41

















  • I couldn't find any of this packages for Arch and Ubuntu.

    – Leandro
    Oct 17 '14 at 23:54











  • Their names will likely be different. Relax your searches using pacman. Look for libvirt.

    – slm
    Oct 18 '14 at 0:05











  • There are only 3 packages: libvirt, libvirt-glib and libvirt-python

    – Leandro
    Oct 18 '14 at 0:30












  • @Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

    – slm
    Oct 18 '14 at 0:39












  • Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

    – Leandro
    Oct 18 '14 at 0:41
















I couldn't find any of this packages for Arch and Ubuntu.

– Leandro
Oct 17 '14 at 23:54





I couldn't find any of this packages for Arch and Ubuntu.

– Leandro
Oct 17 '14 at 23:54













Their names will likely be different. Relax your searches using pacman. Look for libvirt.

– slm
Oct 18 '14 at 0:05





Their names will likely be different. Relax your searches using pacman. Look for libvirt.

– slm
Oct 18 '14 at 0:05













There are only 3 packages: libvirt, libvirt-glib and libvirt-python

– Leandro
Oct 18 '14 at 0:30






There are only 3 packages: libvirt, libvirt-glib and libvirt-python

– Leandro
Oct 18 '14 at 0:30














@Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

– slm
Oct 18 '14 at 0:39






@Leandro_GS - Then you may not be able to make use of libvirt on Arch if it doesn't have these packages. You cannot do what you want without the vbox driver for libvirt.

– slm
Oct 18 '14 at 0:39














Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

– Leandro
Oct 18 '14 at 0:41





Looks like these packages are all included on "libvirt" package. libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization back-ends (QEMU/KVM, VirtualBox, Xen, etc), communally called hypervisors .

– Leandro
Oct 18 '14 at 0:41

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f162775%2flibvirt-bin-error-on-a-vm-when-i-try-to-list-vm%23new-answer', 'question_page');

);

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






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?