[gentoo-user] Virt-manager

[gentoo-user] Virt-manager

[john]

I am trying to start virt-manager but when I start the daemon

/etc/init.d/libvirtd i get

 * Starting libvirtd ...
/usr/sbin/libvirtd: error: Unable to initialize network sockets.
Check /var/log/messages or run without --daemon for more info.
 * start-stop-daemon: failed to start
`/usr/sbin/libvirtd'                [ !! ]
 * ERROR: libvirtd failed to start

Any suggestions???
-- 
--------------
John D Maunder
jdm@jdm.myzen.co.uk

Re: [gentoo-user] Virt-manager

[Albert Hopkins]

On Thursday, July 7 at 19:15 (+0100), john said:

> 
> I am trying to start virt-manager but when I start the daemon
> 
> /etc/init.d/libvirtd i get
> 
>  * Starting libvirtd ...
> /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> Check /var/log/messages or run without --daemon for more info.
>  * start-stop-daemon: failed to start
> `/usr/sbin/libvirtd'                [ !! ]
>  * ERROR: libvirtd failed to start
> 
> Any suggestions???

Other than the obvious (which is to check /var/log/messages or run
without --daemon)...

My guess is that you have enabled the virt-network USE flag but the
system is not configured as such that it could start the default virtual
network.  Among other things you need:

      * iptables support in there kernel
      * bridging support in the kernel
      * tun/tap support in the kernel
      * brctl (probably a dependency of the package itself)
      * iproute2 (probably a dependency of the package itself)

Did /var/log/messages tell you anything (did you bother to look)?  Also
libvirt has a log level that can be set in the config, you could
increase that (and also check the logs).

You should also check the logs.

-a

Re: [gentoo-user] Virt-manager

[john]

On Thu, 07 Jul 2011 14:24:48 -0400
Albert Hopkins <marduk@letterboxes.org> wrote:

> 
> 
> On Thursday, July 7 at 19:15 (+0100), john said:
> 
> > 
> > I am trying to start virt-manager but when I start the daemon
> > 
> > /etc/init.d/libvirtd i get
> > 
> >  * Starting libvirtd ...
> > /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> > Check /var/log/messages or run without --daemon for more info.
> >  * start-stop-daemon: failed to start
> > `/usr/sbin/libvirtd'                [ !! ]
> >  * ERROR: libvirtd failed to start
> > 
> > Any suggestions???
> 
> Other than the obvious (which is to check /var/log/messages or run
> without --daemon)...
> 
> My guess is that you have enabled the virt-network USE flag but the
> system is not configured as such that it could start the default
> virtual network.  Among other things you need:
> 
>       * iptables support in there kernel
>       * bridging support in the kernel
>       * tun/tap support in the kernel
>       * brctl (probably a dependency of the package itself)
>       * iproute2 (probably a dependency of the package itself)
> 
> Did /var/log/messages tell you anything (did you bother to look)?
> Also libvirt has a log level that can be set in the config, you could
> increase that (and also check the logs).
> 
> You should also check the logs.
> 
> -a
> 
> 
>
 
iptables is running, bridging and tun have been loaded as modules
iproute2 has now been installed but makes no odds. Not sure about brctl
as I can't find this?

Have started libvirtd and get the following
when trying to start virt-manager

20:28:05.083: 5216: info :
libvirt version: 0.9.1 20:28:05.083: 5216: error : virCommandWait:1281 :
internal error Child process (/sbin/iptables --table mangle --insert
POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68
--jump CHECKSUM --checksum-fill) status unexpected: exit status 1
20:28:05.084: 5216: warning : networkAddGeneralIptablesRules:1199 :
Could not add rule to fixup DHCP response checksums on network
'default'. 20:28:05.084: 5216: warning :
networkAddGeneralIptablesRules:1200 : May need to update iptables
package & kernel to support CHECKSUM rule. 20:28:05.256: 5216: error :
virCommandWait:1281 : internal error Child process (/sbin/ip addr add
192.168.122.1/24 broadcast 192.168.122.255 dev virbr0) status
unexpected: exit status 1 20:28:05.256: 5216: error :
networkAddAddrToBridge:1625 : internal error cannot set IP address on
bridge 'virbr0' 20:28:05.449: 5216: error : virCommandWait:1281 :
internal error Child process (/sbin/iptables --table mangle --delete
POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68
--jump CHECKSUM --checksum-fill) status unexpected: exit status 1
20:28:05.481: 5216: warning : networkStartNetworkDaemon:1800 : Failed
to delete dummy tap device '(null)' on bridge 'virbr0' : Invalid
argument 20:28:05.526: 5216: error : udevGetDMIData:1493 : Failed to
get udev device for syspath '/sys/devices/virtual/dmi/id' or
'/sys/class/dmi/id' 20:28:51.078: 5219: error :
remoteDispatchAuthPolkit:5139 : Policy kit denied action
org.libvirt.unix.manage from pid 6810, uid 1000: exit status 1
20:31:26.177: 5218: error : do_open:1085 : no connection driver
available for No connection for URI qemu:///system

Does mean something++++++
no connection driver
available for No connection for URI qemu:///system


The only log entry is:-
Jul  7 20:40:53 localhost /etc/init.d/libvirtd[8275]:
start-stop-daemon: failed to start `/usr/sbin/libvirtd' Jul  7 20:40:53
localhost /etc/init.d/libvirtd[8264]: ERROR: libvirtd failed to star

Cannot see option to make this more verbose.

 
--------------
John D Maunder
jdm@jdm.myzen.co.uk

Re: [gentoo-user] Virt-manager

[Albert Hopkins]

On Thursday, July 7 at 20:46 (+0100), john said:

Well, I see several errors, you may want to start with the first one and
work your way down.

> iptables is running, bridging and tun have been loaded as modules
> iproute2 has now been installed but makes no odds. Not sure about brctl
> as I can't find this?
> 
> Have started libvirtd and get the following
> when trying to start virt-manager
> 
> 20:28:05.083: 5216: info :
> libvirt version: 0.9.1 20:28:05.083: 5216: error : virCommandWait:1281 :
> internal error Child process (/sbin/iptables --table mangle --insert
> POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68
> --jump CHECKSUM --checksum-fill) status unexpected: exit status 1

iptables is failing.  Maybe you don't have the correct modules or have
them installed.

> 20:28:05.084: 5216: warning : networkAddGeneralIptablesRules:1199 :
> Could not add rule to fixup DHCP response checksums on network
> 'default'. 20:28:05.084: 5216: warning :
> networkAddGeneralIptablesRules:1200 : May need to update iptables
> package & kernel to support CHECKSUM rule. 20:28:05.256: 5216: error :
> virCommandWait:1281 : internal error Child process (/sbin/ip addr add
> 192.168.122.1/24 broadcast 192.168.122.255 dev virbr0) status
> unexpected: exit status 1 20:28:05.256: 5216: error :
> networkAddAddrToBridge:1625 : internal error cannot set IP address on
> bridge 'virbr0' 20:28:05.449: 5216: error : virCommandWait:1281 :
> internal error Child process (/sbin/iptables --table mangle --delete
> POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68
> --jump CHECKSUM --checksum-fill) status unexpected: exit status 1
> 20:28:05.481: 5216: warning : networkStartNetworkDaemon:1800 : Failed
> to delete dummy tap device '(null)' on bridge 'virbr0' : Invalid
> argument 20:28:05.526: 5216: error : udevGetDMIData:1493 : Failed to
> get udev device for syspath '/sys/devices/virtual/dmi/id' or
> '/sys/class/dmi/id' 20:28:51.078: 5219: error :
> remoteDispatchAuthPolkit:5139 : Policy kit denied action
> org.libvirt.unix.manage from pid 6810, uid 1000: exit status 1
> 20:31:26.177: 5218: error : do_open:1085 : no connection driver
> available for No connection for URI qemu:///system
> 
> Does mean something++++++
> no connection driver
> available for No connection for URI qemu:///system
> 

The subsequent errors may be because of the first.  So I'd start with
that.

If you are not going to use virtual networks, then you could simply
disable the virt-net USE flag and save yourself some time.

As for as iptables.  You need the right sub-drivers (or whatever they're
called).  Basically if you are using virtual networking you need to be
able to do NAT.  I have the following:

CONFIG_NF_CONNTRACK=m
CONFIG_NF_CONNTRACK_MARK=y
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
# CONFIG_NF_CT_PROTO_SCTP is not set
# CONFIG_NF_CT_PROTO_UDPLITE is not set
# CONFIG_NF_CONNTRACK_AMANDA is not set
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
# CONFIG_NF_CONNTRACK_PPTP is not set
# CONFIG_NF_CONNTRACK_SANE is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CONNTRACK_TFTP is not set
# CONFIG_NF_CT_NETLINK is not set
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=mNAT/masquerading.
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_REDIRECT is not set
# CONFIG_NF_NAT_SNMP_BASIC is not set
# CONFIG_NF_NAT_FTP is not set
# CONFIG_NF_NAT_IRC is not set
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
# CONFIG_NF_NAT_PPTP is not set
# CONFIG_NF_NAT_H323 is not set
# CONFIG_NF_NAT_SIP is not set
CONFIG_IP_NF_MANGLE=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_TARGET_ECN is not set
# CONFIG_IP_NF_TARGET_TTL is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_BRIDGE_NF_EBTABLES is not set

I have the following modules loaded (may not all be used by libvirt
though):

$ lsmod|egrep 'ipt|nf'
ipt_MASQUERADE          1523  3 
iptable_nat             3053  1 
nf_nat                 11757  2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4       8846  4 iptable_nat,nf_nat
nf_defrag_ipv4          1131  1 nf_conntrack_ipv4
nf_conntrack           40786  5
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
ipt_REJECT              1998  2 
iptable_mangle          1392  1 
iptable_filter          1312  1 
ip_tables              13195  3
iptable_nat,iptable_mangle,iptable_filter
x_tables               13624  9
ipt_MASQUERADE,iptable_nat,xt_state,ipt_REJECT,xt_CHECKSUM,iptable_mangle,xt_tcpudp,iptable_filter,ip_tables


You also need to be able do to ethernet bridging.  The virtual device
vibr0 is a bridge.  You also need bridge-utils, but it's probably
already installed.

A good reference is this: http://wiki.libvirt.org/page/Networking

Re: [gentoo-user] Virt-manager

[john]

On Thu, 07 Jul 2011 17:26:18 -0400
Albert Hopkins <marduk@letterboxes.org> wrote:

> 
> 
> On Thursday, July 7 at 20:46 (+0100), john said:
> 
> Well, I see several errors, you may want to start with the first one
> and work your way down.
> 
> > iptables is running, bridging and tun have been loaded as modules
> > iproute2 has now been installed but makes no odds. Not sure about
> > brctl as I can't find this?
> > 
> > Have started libvirtd and get the following
> > when trying to start virt-manager
> > 
> > 20:28:05.083: 5216: info :
> > libvirt version: 0.9.1 20:28:05.083: 5216: error :
> > virCommandWait:1281 : internal error Child process (/sbin/iptables
> > --table mangle --insert POSTROUTING --out-interface virbr0
> > --protocol udp --destination-port 68 --jump CHECKSUM
> > --checksum-fill) status unexpected: exit status 1
> 
> iptables is failing.  Maybe you don't have the correct modules or have
> them installed.
> 
> > 20:28:05.084: 5216: warning : networkAddGeneralIptablesRules:1199 :
> > Could not add rule to fixup DHCP response checksums on network
> > 'default'. 20:28:05.084: 5216: warning :
> > networkAddGeneralIptablesRules:1200 : May need to update iptables
> > package & kernel to support CHECKSUM rule. 20:28:05.256: 5216:
> > error : virCommandWait:1281 : internal error Child process
> > (/sbin/ip addr add 192.168.122.1/24 broadcast 192.168.122.255 dev
> > virbr0) status unexpected: exit status 1 20:28:05.256: 5216: error :
> > networkAddAddrToBridge:1625 : internal error cannot set IP address
> > on bridge 'virbr0' 20:28:05.449: 5216: error : virCommandWait:1281 :
> > internal error Child process (/sbin/iptables --table mangle --delete
> > POSTROUTING --out-interface virbr0 --protocol udp
> > --destination-port 68 --jump CHECKSUM --checksum-fill) status
> > unexpected: exit status 1 20:28:05.481: 5216: warning :
> > networkStartNetworkDaemon:1800 : Failed to delete dummy tap device
> > '(null)' on bridge 'virbr0' : Invalid argument 20:28:05.526: 5216:
> > error : udevGetDMIData:1493 : Failed to get udev device for syspath
> > '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id' 20:28:51.078:
> > 5219: error : remoteDispatchAuthPolkit:5139 : Policy kit denied
> > action org.libvirt.unix.manage from pid 6810, uid 1000: exit status
> > 1 20:31:26.177: 5218: error : do_open:1085 : no connection driver
> > available for No connection for URI qemu:///system
> > 
> > Does mean something++++++
> > no connection driver
> > available for No connection for URI qemu:///system
> > 
> 
> The subsequent errors may be because of the first.  So I'd start with
> that.
> 
> If you are not going to use virtual networks, then you could simply
> disable the virt-net USE flag and save yourself some time.
> 
> As for as iptables.  You need the right sub-drivers (or whatever
> they're called).  Basically if you are using virtual networking you
> need to be able to do NAT.  I have the following:
> 
> CONFIG_NF_CONNTRACK=m
> CONFIG_NF_CONNTRACK_MARK=y
> # CONFIG_NF_CONNTRACK_EVENTS is not set
> # CONFIG_NF_CT_PROTO_DCCP is not set
> # CONFIG_NF_CT_PROTO_SCTP is not set
> # CONFIG_NF_CT_PROTO_UDPLITE is not set
> # CONFIG_NF_CONNTRACK_AMANDA is not set
> # CONFIG_NF_CONNTRACK_FTP is not set
> # CONFIG_NF_CONNTRACK_H323 is not set
> # CONFIG_NF_CONNTRACK_IRC is not set
> # CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
> # CONFIG_NF_CONNTRACK_PPTP is not set
> # CONFIG_NF_CONNTRACK_SANE is not set
> # CONFIG_NF_CONNTRACK_SIP is not set
> # CONFIG_NF_CONNTRACK_TFTP is not set
> # CONFIG_NF_CT_NETLINK is not set
> CONFIG_NF_DEFRAG_IPV4=m
> CONFIG_NF_CONNTRACK_IPV4=m
> CONFIG_NF_CONNTRACK_PROC_COMPAT=y
> # CONFIG_IP_NF_QUEUE is not set
> CONFIG_IP_NF_IPTABLES=m
> CONFIG_IP_NF_MATCH_ADDRTYPE=m
> # CONFIG_IP_NF_MATCH_AH is not set
> # CONFIG_IP_NF_MATCH_ECN is not set
> # CONFIG_IP_NF_MATCH_TTL is not set
> CONFIG_IP_NF_FILTER=m
> CONFIG_IP_NF_TARGET_REJECT=mNAT/masquerading.
> # CONFIG_IP_NF_TARGET_LOG is not set
> # CONFIG_IP_NF_TARGET_ULOG is not set
> CONFIG_NF_NAT=m
> CONFIG_NF_NAT_NEEDED=y
> CONFIG_IP_NF_TARGET_MASQUERADE=m
> # CONFIG_IP_NF_TARGET_NETMAP is not set
> # CONFIG_IP_NF_TARGET_REDIRECT is not set
> # CONFIG_NF_NAT_SNMP_BASIC is not set
> # CONFIG_NF_NAT_FTP is not set
> # CONFIG_NF_NAT_IRC is not set
> # CONFIG_NF_NAT_TFTP is not set
> # CONFIG_NF_NAT_AMANDA is not set
> # CONFIG_NF_NAT_PPTP is not set
> # CONFIG_NF_NAT_H323 is not set
> # CONFIG_NF_NAT_SIP is not set
> CONFIG_IP_NF_MANGLE=m
> # CONFIG_IP_NF_TARGET_CLUSTERIP is not set
> # CONFIG_IP_NF_TARGET_ECN is not set
> # CONFIG_IP_NF_TARGET_TTL is not set
> # CONFIG_IP_NF_RAW is not set
> # CONFIG_IP_NF_ARPTABLES is not set
> # CONFIG_BRIDGE_NF_EBTABLES is not set
> 
> I have the following modules loaded (may not all be used by libvirt
> though):
> 
> $ lsmod|egrep 'ipt|nf'
> ipt_MASQUERADE          1523  3 
> iptable_nat             3053  1 
> nf_nat                 11757  2 ipt_MASQUERADE,iptable_nat
> nf_conntrack_ipv4       8846  4 iptable_nat,nf_nat
> nf_defrag_ipv4          1131  1 nf_conntrack_ipv4
> nf_conntrack           40786  5
> ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
> ipt_REJECT              1998  2 
> iptable_mangle          1392  1 
> iptable_filter          1312  1 
> ip_tables              13195  3
> iptable_nat,iptable_mangle,iptable_filter
> x_tables               13624  9
> ipt_MASQUERADE,iptable_nat,xt_state,ipt_REJECT,xt_CHECKSUM,iptable_mangle,xt_tcpudp,iptable_filter,ip_tables
> 
> 
> You also need to be able do to ethernet bridging.  The virtual device
> vibr0 is a bridge.  You also need bridge-utils, but it's probably
> already installed.
> 
> A good reference is this: http://wiki.libvirt.org/page/Networking
> 
> 
> 
> 

Thanks Albert,

Have cleared up error messages using config as suggested.

I still get the issue when starting /etc/init.d/libvirtd
 
>  * Starting libvirtd ...
> /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> Check /var/log/messages or run without --daemon for more info.
>  * start-stop-daemon: failed to start
> `/usr/sbin/libvirtd'                [ !! ]
>  * ERROR: libvirtd failed to start

BUT when i start /usr/sbin/libvirtd from command line virt-manager now
works. It lets me create vms (yippee)

I was unaware that libvirtd was a separate package (thought it was part
of virt-manager. After reading your hints it dawned on me that is was
seaparate so have enabled more use flags. I should check more carefully
the output of emerge -vp.

Anyway I am up and running with a big thanks to yourself and will have
a closer look at the service another day.

Thank You 
-- 
--------------
John D Maunder
jdm@jdm.myzen.co.uk

Re: [gentoo-user] Virt-manager

[Albert Hopkins]

On Thursday, July 7 at 23:30 (+0100), john said:

> On Thu, 07 Jul 2011 17:26:18 -0400

> 
> Have cleared up error messages using config as suggested.
> 
> I still get the issue when starting /etc/init.d/libvirtd
>  
> >  * Starting libvirtd ...
> > /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> > Check /var/log/messages or run without --daemon for more info.
> >  * start-stop-daemon: failed to start
> > `/usr/sbin/libvirtd'                [ !! ]
> >  * ERROR: libvirtd failed to start

You'll have to turn up the logging level of libvirt (to find out exactly
what it's trying to do and where it's erroring out).

> BUT when i start /usr/sbin/libvirtd from command line virt-manager now
> works. It lets me create vms (yippee)
> 
> I was unaware that libvirtd was a separate package (thought it was part
> of virt-manager. After reading your hints it dawned on me that is was
> seaparate so have enabled more use flags. I should check more carefully
> the output of emerge -vp.
> 

libvirt (not libvirtd) is a seperate package, it (possibly) contains a
number of things, including

libvirt: the C library that allows you to manage many different types of
virtualization platforms using a common API.
Python bindings for the above
A command-line and shell interface (called virsh)
libvirtd, which is a daemon helper used to manage virtualization
platforms which don't have their own management service (such as kvm).

virt-manager, is a seperate product.  It is a GUI interface written in
python that is used to talk to manage different types of virtualization
platforms.  It uses libvirt (its python bindings) to do this.  Think of
it as a GUI version of virsh.

But you don't need virt-manager to use libvirt, and you don't even need
libvirtd to use libvirt (e.g. you are interfacing with Xen or VMware
hypervisors).

That's why I was trying to say it's good for you to figure out what you
are trying to do, before you go through the trouble of figuring out how
to solve a problem that doesn't even pertain to you and could have been
avoided altogether just by choosing the right combination of USE flags.

If you are just wanting have a GUI for Xen, for example, you don't even
need to worry about libvirtd.  If, for example, you are using KVM but
you want the VMs to bridge off a physical interface and have no need for
"virtual networks", then you don't even need the virt-net USE flag.
 
> Anyway I am up and running with a big thanks to yourself and will have
> a closer look at the service another day.

Ok

Re: [gentoo-user] Virt-manager

[john]

On Thu, 07 Jul 2011 21:17:12 -0400
Albert Hopkins <marduk@letterboxes.org> wrote:

> 
> 
> On Thursday, July 7 at 23:30 (+0100), john said:
> 
> > On Thu, 07 Jul 2011 17:26:18 -0400
> 
> > 
> > Have cleared up error messages using config as suggested.
> > 
> > I still get the issue when starting /etc/init.d/libvirtd
> >  
> > >  * Starting libvirtd ...
> > > /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> > > Check /var/log/messages or run without --daemon for more info.
> > >  * start-stop-daemon: failed to start
> > > `/usr/sbin/libvirtd'                [ !! ]
> > >  * ERROR: libvirtd failed to start
> 
> You'll have to turn up the logging level of libvirt (to find out
> exactly what it's trying to do and where it's erroring out).
> 
> > BUT when i start /usr/sbin/libvirtd from command line virt-manager
> > now works. It lets me create vms (yippee)
> > 
> > I was unaware that libvirtd was a separate package (thought it was
> > part of virt-manager. After reading your hints it dawned on me that
> > is was seaparate so have enabled more use flags. I should check
> > more carefully the output of emerge -vp.
> > 
> 
> libvirt (not libvirtd) is a seperate package, it (possibly) contains a
> number of things, including
> 
> libvirt: the C library that allows you to manage many different types
> of virtualization platforms using a common API.
> Python bindings for the above
> A command-line and shell interface (called virsh)
> libvirtd, which is a daemon helper used to manage virtualization
> platforms which don't have their own management service (such as kvm).
> 
> virt-manager, is a seperate product.  It is a GUI interface written in
> python that is used to talk to manage different types of
> virtualization platforms.  It uses libvirt (its python bindings) to
> do this.  Think of it as a GUI version of virsh.
> 
> But you don't need virt-manager to use libvirt, and you don't even
> need libvirtd to use libvirt (e.g. you are interfacing with Xen or
> VMware hypervisors).
> 
> That's why I was trying to say it's good for you to figure out what
> you are trying to do, before you go through the trouble of figuring
> out how to solve a problem that doesn't even pertain to you and could
> have been avoided altogether just by choosing the right combination
> of USE flags.
> 
> If you are just wanting have a GUI for Xen, for example, you don't
> even need to worry about libvirtd.  If, for example, you are using
> KVM but you want the VMs to bridge off a physical interface and have
> no need for "virtual networks", then you don't even need the virt-net
> USE flag. 
> > Anyway I am up and running with a big thanks to yourself and will
> > have a closer look at the service another day.
> 
> Ok
> 
> 

LOL Well I was up and running but now when trying to create VMs I get
(have done upgrade of around 20 packages)
 
Uncaught error validating install parameters: Must pass a VirtualDevice
instance.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1241, in
validate
    return self.validate_final_page()
  File "/usr/share/virt-manager/virtManager/create.py", line 1501, in
validate_final_page
    self.guest.add_device(self.nic)
  File "/usr/lib64/python2.7/site-packages/virtinst/Guest.py", line
666, in add_device
    raise ValueError(_("Must pass a VirtualDevice instance."))
ValueError: Must pass a VirtualDevice instance.

dnsmasq installed. python-updater run. revdep-rebuild etc......

Are there any other GUIs to try for for virtualisation?????

Or is it better sticking to CL to qemu-kvm?
Am I expecting too much for this just to work?



 
-- 
--------------
John D Maunder
jdm@jdm.myzen.co.uk

Re: [gentoo-user] Virt-manager

[john]

On Fri, 8 Jul 2011 21:22:40 +0100
john <jdm@jdm.myzen.co.uk> wrote:

> On Thu, 07 Jul 2011 21:17:12 -0400
> Albert Hopkins <marduk@letterboxes.org> wrote:
> 
> > 
> > 
> > On Thursday, July 7 at 23:30 (+0100), john said:
> > 
> > > On Thu, 07 Jul 2011 17:26:18 -0400
> > 
> > > 
> > > Have cleared up error messages using config as suggested.
> > > 
> > > I still get the issue when starting /etc/init.d/libvirtd
> > >  
> > > >  * Starting libvirtd ...
> > > > /usr/sbin/libvirtd: error: Unable to initialize network sockets.
> > > > Check /var/log/messages or run without --daemon for more info.
> > > >  * start-stop-daemon: failed to start
> > > > `/usr/sbin/libvirtd'                [ !! ]
> > > >  * ERROR: libvirtd failed to start
> > 
> > You'll have to turn up the logging level of libvirt (to find out
> > exactly what it's trying to do and where it's erroring out).
> > 
> > > BUT when i start /usr/sbin/libvirtd from command line virt-manager
> > > now works. It lets me create vms (yippee)
> > > 
> > > I was unaware that libvirtd was a separate package (thought it was
> > > part of virt-manager. After reading your hints it dawned on me
> > > that is was seaparate so have enabled more use flags. I should
> > > check more carefully the output of emerge -vp.
> > > 
> > 
> > libvirt (not libvirtd) is a seperate package, it (possibly)
> > contains a number of things, including
> > 
> > libvirt: the C library that allows you to manage many different
> > types of virtualization platforms using a common API.
> > Python bindings for the above
> > A command-line and shell interface (called virsh)
> > libvirtd, which is a daemon helper used to manage virtualization
> > platforms which don't have their own management service (such as
> > kvm).
> > 
> > virt-manager, is a seperate product.  It is a GUI interface written
> > in python that is used to talk to manage different types of
> > virtualization platforms.  It uses libvirt (its python bindings) to
> > do this.  Think of it as a GUI version of virsh.
> > 
> > But you don't need virt-manager to use libvirt, and you don't even
> > need libvirtd to use libvirt (e.g. you are interfacing with Xen or
> > VMware hypervisors).
> > 
> > That's why I was trying to say it's good for you to figure out what
> > you are trying to do, before you go through the trouble of figuring
> > out how to solve a problem that doesn't even pertain to you and
> > could have been avoided altogether just by choosing the right
> > combination of USE flags.
> > 
> > If you are just wanting have a GUI for Xen, for example, you don't
> > even need to worry about libvirtd.  If, for example, you are using
> > KVM but you want the VMs to bridge off a physical interface and have
> > no need for "virtual networks", then you don't even need the
> > virt-net USE flag. 
> > > Anyway I am up and running with a big thanks to yourself and will
> > > have a closer look at the service another day.
> > 
> > Ok
> > 
> > 
> 
> LOL Well I was up and running but now when trying to create VMs I get
> (have done upgrade of around 20 packages)
>  
> Uncaught error validating install parameters: Must pass a
> VirtualDevice instance.
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1241, in
> validate
>     return self.validate_final_page()
>   File "/usr/share/virt-manager/virtManager/create.py", line 1501, in
> validate_final_page
>     self.guest.add_device(self.nic)
>   File "/usr/lib64/python2.7/site-packages/virtinst/Guest.py", line
> 666, in add_device
>     raise ValueError(_("Must pass a VirtualDevice instance."))
> ValueError: Must pass a VirtualDevice instance.
> 
> dnsmasq installed. python-updater run. revdep-rebuild etc......
> 
> Are there any other GUIs to try for for virtualisation?????
> 
> Or is it better sticking to CL to qemu-kvm?
> Am I expecting too much for this just to work?
> 
> 
> 
>  

ok I might be being dumb but found a way round this (through trial and
error) 

In advanced options in step 5 of 5 select "Specify Shared Device Name"

Please note you'll need to create a bridge as well but selecting the
above removes error message.

Caw this is tough but fun.




-- 
--------------
John D Maunder
jdm@jdm.myzen.co.uk

Re: [gentoo-user] Virt-manager

[Albert Hopkins]

On Friday, July 8 at 21:22 (+0100), john said:

[...]
> LOL Well I was up and running but now when trying to create VMs I get
> (have done upgrade of around 20 packages)
>  
> Uncaught error validating install parameters: Must pass a VirtualDevice
> instance.
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/create.py", line 1241, in
> validate
>     return self.validate_final_page()
>   File "/usr/share/virt-manager/virtManager/create.py", line 1501, in
> validate_final_page
>     self.guest.add_device(self.nic)
>   File "/usr/lib64/python2.7/site-packages/virtinst/Guest.py", line
> 666, in add_device
>     raise ValueError(_("Must pass a VirtualDevice instance."))
> ValueError: Must pass a VirtualDevice instance.
> 
> dnsmasq installed. python-updater run. revdep-rebuild etc......
> 

> Are there any other GUIs to try for for virtualisation?????
> 
> Or is it better sticking to CL to qemu-kvm?
> Am I expecting too much for this just to work?
> 

I can honestly say that I haven't experienced so much pain working with
libvirt/virt-manger.  If I had I probably would have given up, but I've
been using it for years now.

What versions of packages are you using?  Are you mixing stable/unstable packages?

I can't really say.  I've never seen that error before.  What steps are
you taking to create the VM?

 

Re: [gentoo-user] Virt-manager

[Albert Hopkins]

On Friday, July 8 at 22:37 (+0100), john said:

> ok I might be being dumb but found a way round this (through trial and
> error) 
> 
> In advanced options in step 5 of 5 select "Specify Shared Device Name"
> 
> Please note you'll need to create a bridge as well but selecting the
> above removes error message.
> 

Ok, the problem appears that you never really solved the first issue you
had.  So that's causing other issues down the pipe, which is often the
case.

Re: [gentoo-user] Virt-manager

[john]

On Fri, 08 Jul 2011 17:57:55 -0400
Albert Hopkins <marduk@letterboxes.org> wrote:

> 
> 
> On Friday, July 8 at 21:22 (+0100), john said:
> 
> [...]
> > LOL Well I was up and running but now when trying to create VMs I
> > get (have done upgrade of around 20 packages)
> >  
> > Uncaught error validating install parameters: Must pass a
> > VirtualDevice instance.
> > 
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1241,
> > in validate
> >     return self.validate_final_page()
> >   File "/usr/share/virt-manager/virtManager/create.py", line 1501,
> > in validate_final_page
> >     self.guest.add_device(self.nic)
> >   File "/usr/lib64/python2.7/site-packages/virtinst/Guest.py", line
> > 666, in add_device
> >     raise ValueError(_("Must pass a VirtualDevice instance."))
> > ValueError: Must pass a VirtualDevice instance.
> > 
> > dnsmasq installed. python-updater run. revdep-rebuild etc......
> > 
> 
> > Are there any other GUIs to try for for virtualisation?????
> > 
> > Or is it better sticking to CL to qemu-kvm?
> > Am I expecting too much for this just to work?
> > 
> 
> I can honestly say that I haven't experienced so much pain working
> with libvirt/virt-manger.  If I had I probably would have given up,
> but I've been using it for years now.
> 
> What versions of packages are you using?  Are you mixing
> stable/unstable packages?
> 
> I can't really say.  I've never seen that error before.  What steps
> are you taking to create the VM?
> 
>  
> 
> 
> 

Using latest stable versions of all packages regarding
virt-manager/libvirt and all associated but I am using 
.39-r2 kernel (which oddly cures a usb issue I have been having
with .38 

There is post on the forum regarding this issue as well (recent)
but looks like no fix was found.

Have tried a few vms now and seen to be running ok. Was trying to see
any differences with VirtualBox (better speed/usability).

Can't say there is much in it but only a home user so will not see too
much speed difference anyway.

Using gui to create images on hard disc and running isos from there.

I perhaps should read the documentation but like to try things first
before getting too involved. lxc next!!!!!!!


Thanks for your guidance. I don't think I would have got this far
without it.

-- 
--------------
John D Maunder
jdm@jdm.myzen.co.uk