1 |
On Fri, 8 Jul 2011 21:22:40 +0100 |
2 |
john <jdm@××××××××××××.uk> wrote: |
3 |
|
4 |
> On Thu, 07 Jul 2011 21:17:12 -0400 |
5 |
> Albert Hopkins <marduk@×××××××××××.org> wrote: |
6 |
> |
7 |
> > |
8 |
> > |
9 |
> > On Thursday, July 7 at 23:30 (+0100), john said: |
10 |
> > |
11 |
> > > On Thu, 07 Jul 2011 17:26:18 -0400 |
12 |
> > |
13 |
> > > |
14 |
> > > Have cleared up error messages using config as suggested. |
15 |
> > > |
16 |
> > > I still get the issue when starting /etc/init.d/libvirtd |
17 |
> > > |
18 |
> > > > * Starting libvirtd ... |
19 |
> > > > /usr/sbin/libvirtd: error: Unable to initialize network sockets. |
20 |
> > > > Check /var/log/messages or run without --daemon for more info. |
21 |
> > > > * start-stop-daemon: failed to start |
22 |
> > > > `/usr/sbin/libvirtd' [ !! ] |
23 |
> > > > * ERROR: libvirtd failed to start |
24 |
> > |
25 |
> > You'll have to turn up the logging level of libvirt (to find out |
26 |
> > exactly what it's trying to do and where it's erroring out). |
27 |
> > |
28 |
> > > BUT when i start /usr/sbin/libvirtd from command line virt-manager |
29 |
> > > now works. It lets me create vms (yippee) |
30 |
> > > |
31 |
> > > I was unaware that libvirtd was a separate package (thought it was |
32 |
> > > part of virt-manager. After reading your hints it dawned on me |
33 |
> > > that is was seaparate so have enabled more use flags. I should |
34 |
> > > check more carefully the output of emerge -vp. |
35 |
> > > |
36 |
> > |
37 |
> > libvirt (not libvirtd) is a seperate package, it (possibly) |
38 |
> > contains a number of things, including |
39 |
> > |
40 |
> > libvirt: the C library that allows you to manage many different |
41 |
> > types of virtualization platforms using a common API. |
42 |
> > Python bindings for the above |
43 |
> > A command-line and shell interface (called virsh) |
44 |
> > libvirtd, which is a daemon helper used to manage virtualization |
45 |
> > platforms which don't have their own management service (such as |
46 |
> > kvm). |
47 |
> > |
48 |
> > virt-manager, is a seperate product. It is a GUI interface written |
49 |
> > in python that is used to talk to manage different types of |
50 |
> > virtualization platforms. It uses libvirt (its python bindings) to |
51 |
> > do this. Think of it as a GUI version of virsh. |
52 |
> > |
53 |
> > But you don't need virt-manager to use libvirt, and you don't even |
54 |
> > need libvirtd to use libvirt (e.g. you are interfacing with Xen or |
55 |
> > VMware hypervisors). |
56 |
> > |
57 |
> > That's why I was trying to say it's good for you to figure out what |
58 |
> > you are trying to do, before you go through the trouble of figuring |
59 |
> > out how to solve a problem that doesn't even pertain to you and |
60 |
> > could have been avoided altogether just by choosing the right |
61 |
> > combination of USE flags. |
62 |
> > |
63 |
> > If you are just wanting have a GUI for Xen, for example, you don't |
64 |
> > even need to worry about libvirtd. If, for example, you are using |
65 |
> > KVM but you want the VMs to bridge off a physical interface and have |
66 |
> > no need for "virtual networks", then you don't even need the |
67 |
> > virt-net USE flag. |
68 |
> > > Anyway I am up and running with a big thanks to yourself and will |
69 |
> > > have a closer look at the service another day. |
70 |
> > |
71 |
> > Ok |
72 |
> > |
73 |
> > |
74 |
> |
75 |
> LOL Well I was up and running but now when trying to create VMs I get |
76 |
> (have done upgrade of around 20 packages) |
77 |
> |
78 |
> Uncaught error validating install parameters: Must pass a |
79 |
> VirtualDevice instance. |
80 |
> |
81 |
> Traceback (most recent call last): |
82 |
> File "/usr/share/virt-manager/virtManager/create.py", line 1241, in |
83 |
> validate |
84 |
> return self.validate_final_page() |
85 |
> File "/usr/share/virt-manager/virtManager/create.py", line 1501, in |
86 |
> validate_final_page |
87 |
> self.guest.add_device(self.nic) |
88 |
> File "/usr/lib64/python2.7/site-packages/virtinst/Guest.py", line |
89 |
> 666, in add_device |
90 |
> raise ValueError(_("Must pass a VirtualDevice instance.")) |
91 |
> ValueError: Must pass a VirtualDevice instance. |
92 |
> |
93 |
> dnsmasq installed. python-updater run. revdep-rebuild etc...... |
94 |
> |
95 |
> Are there any other GUIs to try for for virtualisation????? |
96 |
> |
97 |
> Or is it better sticking to CL to qemu-kvm? |
98 |
> Am I expecting too much for this just to work? |
99 |
> |
100 |
> |
101 |
> |
102 |
> |
103 |
|
104 |
ok I might be being dumb but found a way round this (through trial and |
105 |
error) |
106 |
|
107 |
In advanced options in step 5 of 5 select "Specify Shared Device Name" |
108 |
|
109 |
Please note you'll need to create a bridge as well but selecting the |
110 |
above removes error message. |
111 |
|
112 |
Caw this is tough but fun. |
113 |
|
114 |
|
115 |
|
116 |
|
117 |
-- |
118 |
-------------- |
119 |
John D Maunder |
120 |
jdm@××××××××××××.uk |