| 1 |
On Thursday, July 7 at 20:46 (+0100), john said: |
| 2 |
|
| 3 |
Well, I see several errors, you may want to start with the first one and |
| 4 |
work your way down. |
| 5 |
|
| 6 |
> iptables is running, bridging and tun have been loaded as modules |
| 7 |
> iproute2 has now been installed but makes no odds. Not sure about brctl |
| 8 |
> as I can't find this? |
| 9 |
> |
| 10 |
> Have started libvirtd and get the following |
| 11 |
> when trying to start virt-manager |
| 12 |
> |
| 13 |
> 20:28:05.083: 5216: info : |
| 14 |
> libvirt version: 0.9.1 20:28:05.083: 5216: error : virCommandWait:1281 : |
| 15 |
> internal error Child process (/sbin/iptables --table mangle --insert |
| 16 |
> POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68 |
| 17 |
> --jump CHECKSUM --checksum-fill) status unexpected: exit status 1 |
| 18 |
|
| 19 |
iptables is failing. Maybe you don't have the correct modules or have |
| 20 |
them installed. |
| 21 |
|
| 22 |
> 20:28:05.084: 5216: warning : networkAddGeneralIptablesRules:1199 : |
| 23 |
> Could not add rule to fixup DHCP response checksums on network |
| 24 |
> 'default'. 20:28:05.084: 5216: warning : |
| 25 |
> networkAddGeneralIptablesRules:1200 : May need to update iptables |
| 26 |
> package & kernel to support CHECKSUM rule. 20:28:05.256: 5216: error : |
| 27 |
> virCommandWait:1281 : internal error Child process (/sbin/ip addr add |
| 28 |
> 192.168.122.1/24 broadcast 192.168.122.255 dev virbr0) status |
| 29 |
> unexpected: exit status 1 20:28:05.256: 5216: error : |
| 30 |
> networkAddAddrToBridge:1625 : internal error cannot set IP address on |
| 31 |
> bridge 'virbr0' 20:28:05.449: 5216: error : virCommandWait:1281 : |
| 32 |
> internal error Child process (/sbin/iptables --table mangle --delete |
| 33 |
> POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68 |
| 34 |
> --jump CHECKSUM --checksum-fill) status unexpected: exit status 1 |
| 35 |
> 20:28:05.481: 5216: warning : networkStartNetworkDaemon:1800 : Failed |
| 36 |
> to delete dummy tap device '(null)' on bridge 'virbr0' : Invalid |
| 37 |
> argument 20:28:05.526: 5216: error : udevGetDMIData:1493 : Failed to |
| 38 |
> get udev device for syspath '/sys/devices/virtual/dmi/id' or |
| 39 |
> '/sys/class/dmi/id' 20:28:51.078: 5219: error : |
| 40 |
> remoteDispatchAuthPolkit:5139 : Policy kit denied action |
| 41 |
> org.libvirt.unix.manage from pid 6810, uid 1000: exit status 1 |
| 42 |
> 20:31:26.177: 5218: error : do_open:1085 : no connection driver |
| 43 |
> available for No connection for URI qemu:///system |
| 44 |
> |
| 45 |
> Does mean something++++++ |
| 46 |
> no connection driver |
| 47 |
> available for No connection for URI qemu:///system |
| 48 |
> |
| 49 |
|
| 50 |
The subsequent errors may be because of the first. So I'd start with |
| 51 |
that. |
| 52 |
|
| 53 |
If you are not going to use virtual networks, then you could simply |
| 54 |
disable the virt-net USE flag and save yourself some time. |
| 55 |
|
| 56 |
As for as iptables. You need the right sub-drivers (or whatever they're |
| 57 |
called). Basically if you are using virtual networking you need to be |
| 58 |
able to do NAT. I have the following: |
| 59 |
|
| 60 |
CONFIG_NF_CONNTRACK=m |
| 61 |
CONFIG_NF_CONNTRACK_MARK=y |
| 62 |
# CONFIG_NF_CONNTRACK_EVENTS is not set |
| 63 |
# CONFIG_NF_CT_PROTO_DCCP is not set |
| 64 |
# CONFIG_NF_CT_PROTO_SCTP is not set |
| 65 |
# CONFIG_NF_CT_PROTO_UDPLITE is not set |
| 66 |
# CONFIG_NF_CONNTRACK_AMANDA is not set |
| 67 |
# CONFIG_NF_CONNTRACK_FTP is not set |
| 68 |
# CONFIG_NF_CONNTRACK_H323 is not set |
| 69 |
# CONFIG_NF_CONNTRACK_IRC is not set |
| 70 |
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set |
| 71 |
# CONFIG_NF_CONNTRACK_PPTP is not set |
| 72 |
# CONFIG_NF_CONNTRACK_SANE is not set |
| 73 |
# CONFIG_NF_CONNTRACK_SIP is not set |
| 74 |
# CONFIG_NF_CONNTRACK_TFTP is not set |
| 75 |
# CONFIG_NF_CT_NETLINK is not set |
| 76 |
CONFIG_NF_DEFRAG_IPV4=m |
| 77 |
CONFIG_NF_CONNTRACK_IPV4=m |
| 78 |
CONFIG_NF_CONNTRACK_PROC_COMPAT=y |
| 79 |
# CONFIG_IP_NF_QUEUE is not set |
| 80 |
CONFIG_IP_NF_IPTABLES=m |
| 81 |
CONFIG_IP_NF_MATCH_ADDRTYPE=m |
| 82 |
# CONFIG_IP_NF_MATCH_AH is not set |
| 83 |
# CONFIG_IP_NF_MATCH_ECN is not set |
| 84 |
# CONFIG_IP_NF_MATCH_TTL is not set |
| 85 |
CONFIG_IP_NF_FILTER=m |
| 86 |
CONFIG_IP_NF_TARGET_REJECT=mNAT/masquerading. |
| 87 |
# CONFIG_IP_NF_TARGET_LOG is not set |
| 88 |
# CONFIG_IP_NF_TARGET_ULOG is not set |
| 89 |
CONFIG_NF_NAT=m |
| 90 |
CONFIG_NF_NAT_NEEDED=y |
| 91 |
CONFIG_IP_NF_TARGET_MASQUERADE=m |
| 92 |
# CONFIG_IP_NF_TARGET_NETMAP is not set |
| 93 |
# CONFIG_IP_NF_TARGET_REDIRECT is not set |
| 94 |
# CONFIG_NF_NAT_SNMP_BASIC is not set |
| 95 |
# CONFIG_NF_NAT_FTP is not set |
| 96 |
# CONFIG_NF_NAT_IRC is not set |
| 97 |
# CONFIG_NF_NAT_TFTP is not set |
| 98 |
# CONFIG_NF_NAT_AMANDA is not set |
| 99 |
# CONFIG_NF_NAT_PPTP is not set |
| 100 |
# CONFIG_NF_NAT_H323 is not set |
| 101 |
# CONFIG_NF_NAT_SIP is not set |
| 102 |
CONFIG_IP_NF_MANGLE=m |
| 103 |
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set |
| 104 |
# CONFIG_IP_NF_TARGET_ECN is not set |
| 105 |
# CONFIG_IP_NF_TARGET_TTL is not set |
| 106 |
# CONFIG_IP_NF_RAW is not set |
| 107 |
# CONFIG_IP_NF_ARPTABLES is not set |
| 108 |
# CONFIG_BRIDGE_NF_EBTABLES is not set |
| 109 |
|
| 110 |
I have the following modules loaded (may not all be used by libvirt |
| 111 |
though): |
| 112 |
|
| 113 |
$ lsmod|egrep 'ipt|nf' |
| 114 |
ipt_MASQUERADE 1523 3 |
| 115 |
iptable_nat 3053 1 |
| 116 |
nf_nat 11757 2 ipt_MASQUERADE,iptable_nat |
| 117 |
nf_conntrack_ipv4 8846 4 iptable_nat,nf_nat |
| 118 |
nf_defrag_ipv4 1131 1 nf_conntrack_ipv4 |
| 119 |
nf_conntrack 40786 5 |
| 120 |
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state |
| 121 |
ipt_REJECT 1998 2 |
| 122 |
iptable_mangle 1392 1 |
| 123 |
iptable_filter 1312 1 |
| 124 |
ip_tables 13195 3 |
| 125 |
iptable_nat,iptable_mangle,iptable_filter |
| 126 |
x_tables 13624 9 |
| 127 |
ipt_MASQUERADE,iptable_nat,xt_state,ipt_REJECT,xt_CHECKSUM,iptable_mangle,xt_tcpudp,iptable_filter,ip_tables |
| 128 |
|
| 129 |
|
| 130 |
You also need to be able do to ethernet bridging. The virtual device |
| 131 |
vibr0 is a bridge. You also need bridge-utils, but it's probably |
| 132 |
already installed. |
| 133 |
|
| 134 |
A good reference is this: http://wiki.libvirt.org/page/Networking |
Archives