I am having problems with kvm-spice trying to use filesystem, it is
giving the same message reported by many sources which reference PCI
passthrough, I don't know if they rely on a similar mechanism behind the
scenes, I am a bit of a noob, but I can't see a problem with the use of
Public bug reported:
Hi after going through a common prcedure to create a self signed
certificate, using the default directory, the VM log reports that it
cannot load the certificates, a similar log response was seen in Red Hat
with spice, where the path was not set despite being set in qemu.conf,
Hi
Obviously this cannot really be classified as a bug at this stage, I
have gone through a number of basic procedures to check this, although I
haven't yet looked at (or really understand) how SELinux and former
issues with this could interfere with spice+TLS
I do know Red Hat had some issue wit
This is a post by me from the people who have been giving me some advice
at spice-de...@lists.freedesktop.org with more information of a recent
re-attempt
/etc/hostname
squealer
/etc/hosts
127.0.0.1 localhost squealer squealer.maiakaat.co.uk maiakaat.co.uk
www.maiakaat.co.uk
192.168.2.140 loc
I can confirm the same problem on Ubuntu 12.10 with Apache installed
using all the default options
sudo serve-branches file:///location/ --allow-writes #works without correct
permissions being set
sudo serve-branches file:///location/ #works, as long as permissions are set
accordingly.
sudo serv