[Mageia-dev] [changelog] [RPM] cauldron core/release libvirt-1.0.2-4.mga3

Fri Mar 8 07:54:59 CET 2013

Op vrijdag 8 maart 2013 07:15:48 schreef Thierry Vignaud:
+> On 8 March 2013 01:50, alien <buildsystem-daemon at mageia.org> wrote:
+> > alien <alien> 1.0.2-4.mga3:
+> > + Revision: 401739
+> > - XEN: do not force blktap as disk backend
+> 
+> Still:
+> # service libvirtd status
+> Redirecting to /bin/systemctl status libvirtd.service
+> libvirtd.service - Virtualization daemon
+>           Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
+> Active: active (running) since Fri, 2013-03-08 07:12:14 CET; 2min 48s ago
+>         Main PID: 860 (libvirtd)
+>           CGroup: name=systemd:/system/libvirtd.service
+>                   ├  860 /usr/sbin/libvirtd
+>                   └ 1280 dnsmasq
+> --conf-file=/var/lib/libvirt/dnsmasq/default.conf
+> 
+> Mar 08 07:12:59 localhost libvirtd[860]: Unable to issue hypervisor
+> ioctl 3166208: Permission non accordée
+> Mar 08 07:12:59 localhost libvirtd[860]: Unable to issue hypervisor
+> ioctl 3166208: Permission non accordée
+> Mar 08 07:12:59 localhost libvirtd[860]: Unable to issue hypervisor
+> ioctl 3166208: Permission non accordée
+> Mar 08 07:12:59 localhost libvirtd[860]: erreur interne impossible de
+> se connecter à Xen
+> Mar 08 07:12:59 localhost libvirtd[860]: unable to connect to
+> 'localhost:8000': Connexion refusée
+> Mar 08 07:12:59 localhost libvirtd[860]: this function is not
+> supported by the connection driver: virConnectNumOfInterfaces
+> Mar 08 07:13:00 localhost libvirtd[860]: this function is not
+> supported by the connection driver: virConnectNumOfInterfaces
+> Mar 08 07:13:01 localhost libvirtd[860]: this function is not
+> supported by the connection driver: virConnectNumOfInterfaces
+> Mar 08 07:13:02 localhost libvirtd[860]: this function is not
+> supported by the connection driver: virConnectNumOfInterfaces
+> Mar 08 07:13:28 localhost libvirtd[860]: No response from client
+> 0x21d39b0 after 5 keepalive messages in 30 seconds
+
+
+either try to connect to xen://127.0.0.1/ or ssh+xen://127.0.0.1/ . (as a 
+remote machine)
+
+that, or use xend and xm commands (supposedly xend works better with libvirt 
+rather than xenlight)
+
+i see connection refused, so, is port 8000 actually running? and/or firewalled?
+
+check with "netstat -lntop" if 8000 is in use by xend.
+
+it seems to fall back to libxl... maybe if you change default.xml file to have
+
+<bridge name="br0" />
+<forward mode="bridge" />
+
+(this is if you have an existing bridge)
+
+this is because libxl doesn't manage a bridge and/or networking. libxl 
+mentions that the user should set up a bridge on your system with network 
+scripts.
+
+so in short, there's 2 ways to do xen (+libvirt) and you're somewhere in 
+between atm...
+