VM fails to start

mat23

New Member
May 5, 2019
2
0
1
39
Was trying to avoid having to post, however, I can't figure out what is going on. I setup Proxmox with a VM running OMV last week. Everything setup correctly and ran fine. I shut everything down a few days back and disconnected the ethernet cable. Just plugged it back in today and fired everything back up. Proxmox started and is running fine, but the VM fails to start. The only thing that changed was me shutting down and unplugging the cable, so I have checked out the network config, but it seems to be set up correctly. The error I am getting is:

Code:
start VM 100:
pve systemd[1]: Created slice qemu.slice
pve systemd[1]: Started 100.scope
systemd-udevd[5027]: Could not generate persistent MAC address for tap100i0: No such file or directory
pve kernel: device tap100i0 entered promiscuous mode
pve kernel: vmbr0: port 2(tap100i0) entered blocking state
pve kernel: vmbr0: port 2(tap100i0) entered disabled state
pve kernel: vmbr0: port 2(tap100i0) entered blocking state
pve kernel: vmbr0: port 2(tap100i0) entered forwarding state
pve kernel: vmbr0: port 2(tap100i0) entered disabled state
pve pvedaemon[5002]: start failed

*Note, there was a port 1 doing the same thing, but after checking the Datacenter firewall and disabling, it has removed itself.

I have looked into the MAC address issue, but am hesitant to make those changes. Plus the files don't exist, and I find it difficult to believe this coincidentally just started after what I said above. I have tried restarting too.

This is a basic configuration setup, no complicated network configuration, so I am at a loss on what to try next.

Here is some info:

Code:
root@pve:~# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 2
Model name:            AMD FX(tm)-8350 Eight-Core Processor
Stepping:              0
CPU MHz:               1786.010
BogoMIPS:              8668.72
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
L3 cache:              8192K
NUMA node0 CPU(s):     0-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

root@pve:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-13-pve)
pve-manager: 5.4-5 (running version: 5.4-5/c6fdb264)
pve-kernel-4.15: 5.4-1
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

network file:
auto lo
iface lo inet loopback

auto enp10s0
iface enp10s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address  10.0.0.xxx
        netmask  255.255.255.0
        gateway  10.0.0.xxx
        bridge-ports enp10s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094


root@pve:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 30:85:a9:8e:9a:6d brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 30:85:a9:8e:9a:6d brd ff:ff:ff:ff:ff:ff
 
Try to start it at the command line by
Code:
qm start 100
and have a look what it returns.
 
Code:
root@pve:~# qm start 100
kvm: -drive file=/dev/disk/by-id/ata-WDC_WD50EZRZ-00RWYB1_WD-WX81D6550SH0,if=none,id=drive-virtio7,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/disk/by-id/ata-WDC_WD50EZRZ-00RWYB1_WD-WX81D6550SH0': No such file or directory
start failed: command '/usr/bin/kvm -id 100 -name OMV -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=3d7fc46d-f3bf-4715-a052-2cb79c792ce7' -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 2048 -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'vmgenid,guid=f043bbe9-898a-4e0f-b202-981c3b9c0a80' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:6a9b1042e50' -drive 'file=/var/lib/vz/template/iso/openmediavault_4.1.3-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-100-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -drive 'file=/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F1RS3K,if=none,id=drive-virtio2,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc' -drive 'file=/dev/disk/by-id/ata-Hitachi_HDS723020BLA642_MN1220F30YABUD,if=none,id=drive-virtio3,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio3,id=virtio3,bus=pci.0,addr=0xd' -drive 'file=/dev/disk/by-id/ata-ST32000641AS_9WM7F67P,if=none,id=drive-virtio4,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio4,id=virtio4,bus=pci.0,addr=0xe' -drive 'file=/dev/disk/by-id/ata-ST2000DX001-1CM164_Z1E73GBJ,if=none,id=drive-virtio5,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio5,id=virtio5,bus=pci.0,addr=0xf' -drive 'file=/dev/disk/by-id/ata-ST2000DX001-1CM164_Z1E73GPB,if=none,id=drive-virtio6,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio6,id=virtio6,bus=pci.2,addr=0x1' -drive 'file=/dev/disk/by-id/ata-WDC_WD50EZRZ-00RWYB1_WD-WX81D6550SH0,if=none,id=drive-virtio7,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio7,id=virtio7,bus=pci.2,addr=0x2' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=7E:BD:17:6C:D8:99,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc'' failed: exit code 1

This is very interesting since that drive is not the drive OMV is installed on, so I have no idea why it would be pointing to that drive all of a sudden. Actually, come to think about it, that drive was a USB attached drive that has been unplugged since. It would make sense if OMV is still looking at a USB as its first boot drive, however, why would the kvm get stuck on that, especially if I never specified it? The hardware section of the kvm is displaying correctly (see attached).
 

Attachments

  • proxmox_kvm1.PNG
    proxmox_kvm1.PNG
    53.6 KB · Views: 18
why would the kvm get stuck on that, especially if I never specified it? The hardware section of the kvm is displaying correctly (see attached).
mhmm? your picture says clearly:

virtio7: /dev/disk/by-id/ata-WDC_WD50EZRZ-00RWYB1_WD-WX81D6550SH0

the vm cannot start when not all disks are there...
 

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!