pve 自动分配内网ip故障导致虚拟机无法启动的解决方法

pve 自动分配内网ip故障导致虚拟机无法启动的解决方法

错误信息如下

dnsmasq@lan.service is not active, cannot reload.
command 'systemctl reload dnsmasq@lan' failed: exit code 1
kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 256
TASK ERROR: start failed: QEMU exited with code 1

org.freedesktop.DBus.Error.ServiceUnknown: The name uk.org.thekelleys.dnsmasq.lan was not provided by any .service files
kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown,vhost=on: network script /usr/libexec/qemu-server/pve-bridge failed with status 2816
TASK ERROR: start failed: QEMU exited with code 1

journalctl -u dnsmasq@lan.service --since "1 hour ago" //lan是你创建内网ip分配的虚拟网卡名称

检查日记发现ip已经使用，解决方法

修改/etc/dnsmasq.d/目录下网卡名称配置文件，ip分配从10开始而不是从0开始，类似下面

dhcp-range=set:lan-10.10.10.0-24,10.10.10.10,static,255.255.255.0,infinite

//如果还是报错，停止dnsmasq,使用前台启动dnsmasq排查问题

dnsmasq -C /etc/dnsmasq.d/lan/dnsmasq.conf -u dnsmasq -d

systemctl start dnsmasq@lan

其实整个问题的原因就是在创建pve内网时ip分配出现了冲突，最好网关地址使用1,分配ip从10开始