Public bug reported:
When having an interfaces stanza:
auto myvpn
iface myvpn inet manual
openvpn myvpn
At least on ubuntu 13.10 (confirmed with ifupdown 0.7.44ubuntu3), doing a
'ifup -v myvpn' resulted in:
# ifup -v myvpn
Configuring interface myvpn=myvpn (inet)
run-parts --verbose /etc/n
The command line used was :
virt-install -n laranja.fritz.box -r 512 --os-variant=ubuntuprecise --disk
/home/vms/disk_laranja_root.img,device=disk,bus=virtio,size=8,sparse=true,format=raw
-w bridge=vms,model=virtio --graphics vnc,listen=0.0.0.0,password=qwerty
--location=http://de.archive.ubun
I will try to investigate what happened that the socket path was used
instead of listen (maybe in one of the debugging attempts, I did not
supply the listen parameter ?). I'm sorry to not be able to provide an
immediate answer on this one since I can't reach my test system at the
moment since I'm c
After checking again, the XML file (/etc/libvirt/qemu/laranja.fritz.box.xml)
contains (snipped):
a virsh dumpxml produces after the vm is started (snipped):
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
When creating machines using virt-install using the --vnc option, it
misses the following line into the /etc/apparmor.d/libvirt/libvirt-
xxxmachineuuid.files :
"/var/lib/libvirt/**/vm-fqdn.vnc" rw,
The files are auto-generated from a template, but adding the mentioned
line m
