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.
- I'm assuming that Xen integration is disabled because AUR is not in the official repositories. Even if an Arch user manages Xen VMs on remote systems (I'm assuming the remote systems are not running Arch), enabling Xen support in Arch's package isn't going to help because when you connect to a remote VM host, you are connecting to the remote host's libvirt daemon, so only the remote host would need libvirt to support Xen. You could open an issue on the bug tracker requesting that Xen support be enabled, but I'm guessing it won't happen.
- -- Jstjohn (talk) 03:25, 5 December 2013 (UTC)
libvirt-guests and systemd
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
KVM acceleration after removing qemu-kvm package
In order to have KVM acceleration after the removal of qemu-kvm I had to edit the config of my virtual machines like this:
<domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> ... <qemu:commandline> <qemu:arg value='-machine'/> <qemu:arg value='accel=kvm'/> <qemu:arg value='kernel_irqchip=on' /> </qemu:commandline> </domain>
I don't know if there is some specific field in libvirt XML, but this works for me.
Added chip level IRQs to the argument list of Vimes656 recommendation.
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...
it should be somthing along the lines of enpXXX
next create the bridge profile for netctl, then start and enable it
Description="Internet bridge" Interface=br0 Connection=bridge BindsToInterfaces=(enp8s) IP=dhcp
netctl start br0
netctl enable br0
now this is where i need suggestions...is 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)