From ArchWiki
Revision as of 06:21, 17 July 2013 by Dzavitz (Talk | contribs) (bridged network edit)

Jump to: navigation, search

What is the reasoning behind disabling xen integration? I'm tempted to open a bug for the missing xen integration, but I assume there is a reason it is excluded. TripleSpeeder (talk) 14:43, 27 November 2012 (UTC)

libvirt-guests does not work with systemd. At least not without modification to the scripts. To enable a guest to auto-start you can either check the "autostart" box in virt-manager, enable autostart through virsh or you can manually create a symlink in the libvirt auto-start directory.

To automatically start a guest named www that runs in qemu

ln -s /etc/libvirt/qemu/www.xml /etc/libvirt/qemu/autostart/www.xml

--En0 (talk) 14:35, 10 December 2012 (UTC)

virt-manager-0.9.4-4 python scripts don't seem to be working. I have been testing them all day.. Including but not limited to a full clean reinstall of Arch 4 times.. I have been getting the error: Building default storage pool failed error. So as a work around I used is below.. This is after the directories are created and root has access to them.

# virsh
# pool-destroy default
# pool-undefine default
# pool-define-as --name default --type dir --target /path/to/default/directory 
# pool-autostart default
# pool-build default
# pool-start default
# pool-destroy local
# pool-undefine local
# pool-define-as --name local-iso --type dir --target /path/to/default/local-iso/directory
# pool-autostart local-iso
# pool-build local-iso
# pool-start local-iso
# quit

$ virt-manager

--Rxdarkdawg10 (talk) 21:17, 30 January 2013 (MST)

Last version broke for me. It was a permissions issue that i solved by creating a service account. I am running v1.0.2-1 with qemu.

Create service account for qemu:

# useradd -g kvm -M -N -r qemu

Edit to run under creds: /etc/libvirt/qemu.conf


Also you will need to modify the permissions to the /dev/kvm

# chown root:kvm /dev/kvm

--En0 (talk) 04:50, 31 January 2013 (UTC)

In order to have KVM accelaration after the removal of qemu-kvm I had to edit the config of my virtual machines like this:

<domain type='qemu' xmlns:qemu=''>
    <qemu:arg value='-machine'/>
    <qemu:arg value='accel=kvm'/>
    <qemu:arg value='kernel_irqchip=on' />

I don't know if there is some specific field in libvirt XML, but this works for me.

--Vimes656 (talk) 13:16, 7 March 2013 (UTC)Vimes656

Added chip level IRQs to the argument list of Vimes656 recommendation.

--En0 (talk) 15:49, 7 March 2013 (UTC)

bridged network edit

note: sorry this is typed all lowercase (broken wrist)

im looking to do an edit on bridged networking section im looking for a suggestion as what to keep since netcfg is deprecated...

i pretty much want to layout how to set a bridge with netctl...


first find your network device to bridge...

ip a

it should be somthing along the lines of enpXXX

next create the bridge profile for netctl, then start and enable it

Description="Internet bridge"
netctl start br0
netctl enable br0


now this is where i need the current info relevant?

all i did was setup my vm to use br0 in virt-manager

i will go through these steps i used virt-manager but dont want to delete info if it isnt deprecate

(Sorry for your wrist)
Please don't delete anything if you're not sure of what you're doing: add templates like Template:Accuracy or Template:Out of date where appropriate instead. -- Kynikos (talk) 13:35, 16 July 2013 (UTC)

Kynikos, just wondering if the info is still relevant as i took a totally different approach with virt-manager, ill go ahead and post my relevant info, removing only the deprecated netcfg stuff --Dzavitz (talk) 06:21, 17 July 2013 (UTC)