TASK ERROR: start failed: command '/usr/bin/kvm

Mauricio Rodrigues

New Member
Nov 23, 2019
3
0
1
27
PRECISO MUITO DE UMA AJUDA. QUANDO DOU INICIA PARA INICIALIZAR UMA MAQUINA (SERVIDOR) DENTRO DO PROXMOX DA O SEGUINTE ERRO:
ponte 'vmbr0' não existe
kvm: -netdev type = tap, id = net0, ifname = tap102i0, script = / var / lib / qemu-server / pve-bridge, downscript = / var / lib / qemu-server / pve-bridgedown: script de rede / var / lib / qemu-server / pve-bridge falhou com status 512
ERRO DE TAREFA: falha na inicialização: comando '/ usr / bin / kvm -id 102 -name serverGPO -chardev' socket, id = qmp, caminho = / var / run / qemu-server / 102.qmp, servidor, nowait '-mon 'chardev = qmp, mode = control' -pidfile /var/run/qemu-server/102.pid -daemonize -smbios 'type = 1, uuid = cc88e3a5-927b-4156-b8a6-18e481b06cde' -smp '4, soquetes = 4, núcleos = 1, maxcpus = menu '-nodefaults -boot' = ativado, restrito = ativado, tempo limite de reinicialização = 1000, splash = / usr / share / qemu-server / bootsplash.jpg '-vga std -vnc unix: /var/run/qemu-server/102.vnc,x509,password -no-hpet -cpu 'kvm64, + lahf_lm, + sep, + kvm_pv_unhalt, + kvm_pv_eoi, hv_spinlocks = 0x1fff, hv_vapic, hv_vapx, hv_vapv , hv_runtime, hv_relaxed, aplica '-m 4096 -device' pci-bridge, id = pci.2, chassis_nr = 2, bus = pci.0, addr = 0x1f '-device' pci-bridge, id = pci.1, chassis_nr = 1, barramento = pci.0, addr = 0x1e '-device'piix3-usb-uhci, id = uhci, bus = pci.0, addr = 0x1.0x2 '-device' usb-tablet, id = tablet, bus = uhci.0, porta = 1 '-device' virtio-balloon- pci, id = balloon0, bus = pci.0, addr = 0x3 '-iscsi' iniciador-nome = iqn.1993-08.org.debian: 01: c5b891242c77 '-drive' file = / dev / pve / vm-102 -disk-1, se = nenhum, id = drive-ide0, formato = bruto, cache = nenhum, aio = nativo, detectar-zeros = no '-device' ide-hd, bus = ide.0, unit = 0, drive = drive-ide0, id = ide0, bootindex = arquivo 100 '-drive' = / var / lib / vz / modelo / iso / WINSERVER2012.ISO, se = nenhum, id = drive-ide2, mídia = cdrom, aio = Thread '-dispositivo' ide-cd, bus = ide.1, unidade = 0, drive = drive-ide2, id = ide2, bootindex = 200 '-netdev' type = tap, id = net0, ifname = tap102i0, script = / var / lib / qemu-server / pve-bridge, downscript = / var / lib / qemu-server / pve-bridgedown '-device' rtl8139, mac = 02: 2E: 43: 99: DD: AD, netdev = net0 , barramento = pci.0, endereço = 0x12, id = net0,bootindex = 300 '-rtc' driftfix = slew, base = localtime '-global' kvm-pit.lost_tick_policy = descartar '' falhou: código de saída 1
 

Attachments

  • ERRO.png
    ERRO.png
    54.3 KB · Views: 5
auto lo
iface lo inet loopback

auto enp4s0
iface enp4s0 inet dhcp

auto enp5s0
iface enp5s0 inet dhcp

auto vmbr0
iface vmbr0 inet static
endereço 10.10.0.50
máscara de rede 255.255.0.0
gateway 10.10.0.1
bridge_ports enp4s0
bridge_stp off
bridge_fd 0
 
endereço 10.10.0.50
máscara de rede 255.255.0.0
Is that what's in written in the interface file? If so, no wonder it does not works.. this needs to be named "address" and "netmask".

Also, this was not the output of the command I asked. Just because the bridge is in the interface file it does not means it could be configured.
So the output of those three commands, as is, no modifying (besides maybe ccensoring a public IP):
Code:
ifup vmbr0
ip addr
cat /etc/network/interfaces
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!