also sprach martin f krafft <madduck(a)madduck.net> [2013.04.03.1606 +0200]:
Unfortunately, when I run virt-manager and connect to the host, the
host's capabilities are fetched very quickly (according to
virt-manager's debug output), but it then takes 20–30 seconds until
the connection is established.
This isn't fixed, but…
The next problem is that when I then try to create a host, I am
shown the dialog and can enter one or two characters into the name
field, then the GUI completely freezes, and so does libvirtd on the
other system (ctrl-c does not work anymore).
This was apparently due to my definition of a default network
(172.27.0.0/24) on the "any physical interface" using NAT. Once
I removed this network, I could create test machines.
This may or may not be due to the fact that one of my interfaces
is slave to a bridge (eth0 slaves to the "wan" bridge). However, in
the interfaces dropdown of the network creation dialog, only eth0
shows up.
--
martin |
http://madduck.net/ |
http://two.sentenc.es/
a bachelor is a man who never made the same mistake once.
spamtraps: madduck.bogus(a)madduck.net