Solved

Cumulus VX on KVM


Hi,

I use proxmox virtualisation platform on a HP proliant gen 6 server.
It is a debian distribution with KVM in the bottom.
Should be pretty standard and worsk well with all other software using iso images and qcow2.

I am hitting the same dead end all the time and can not get past it.

hwdb.bin does not exist, please run udevadm hwdb --update


Since syslog nor the installation console provides little information I also added a serial console.
I do get a bit more information there from the intramfs prompt. sorry not in from of the computer but I'm sure you know the first boot prompt if mounting the disk fails.

I can list /dev and procs etc and see that the UID is not 100% accurate and needless to say since there is no disk the /boot/abc123.img can not be loaded.

I'm stuck here and am running out of ideas but was hoping you could shed some light in why it is not working properly.

I've also downloaded the ova file and converted it to qcow2 just to verify it was something in that specific kvm bundle.

Appreciate any hints as to how I could get this working.

Regards Tomas
icon

Best answer by sundsto1 9 August 2018, 19:51

Hi,

I should have responded as I got the assistance I needed.
Got a few routers up and running with some routing protocols.
I wish BGP flowspec was better integrated as I saw some API script with some iptables injections.
Otherwise it has been running well and no major problems yet.

The default installation using SCSI and virtio was not playing nice and since I got the word that KVM defaults to IDE I used this installation options for the qxow2 image.

So this was the 1,5 day headache and solution is just too simple it makes you look stupid.


Thanks for the mindshare though, appreciated.


Regards Tomas

View original

5 replies

Some more information regarding the VM image not loading properly bellow from the console.

Loading Linux 4.1.0-cl-7-amd64 ...
Loading initial ramdisk ...
Loading, please wait...
Scanning for Btrfs filesystems
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/64332656-4908-47d3-9c11-623e46e9803a does not exist. Dropping to a shell!
modprobe: module ehci-orion not found in modules.dep


BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.1.0-cl-7-amd64 root=UUID=64332656-4908-47d3-9c11-623e46e9803a ro cl_platform=cumulus_vx console=tty0 console=ttyS0,115200n8 quiet
(initramfs) cat /proc/modules
btrfs 929792 0 - Live 0xffffffffa009d000
xor 24576 1 btrfs, Live 0xffffffffa001e000
raid6_pq 106496 1 btrfs, Live 0xffffffffa0082000
dm_mod 102400 0 - Live 0xffffffffa005b000
e1000 126976 0 - Live 0xffffffffa0032000
i2c_piix4 24576 0 - Live 0xffffffffa0027000
i2c_core 49152 1 i2c_piix4, Live 0xffffffffa0011000
uhci_hcd 45056 0 - Live 0xffffffffa0000000
(initramfs)
(initramfs) ls /dev
block ram15 tty20 tty49
bsg ram2 tty21 tty5
btrfs-control ram3 tty22 tty50
bus ram4 tty23 tty51
char ram5 tty24 tty52
console ram6 tty25 tty53
core ram7 tty26 tty54
cpu_dma_latency ram8 tty27 tty55
disk ram9 tty28 tty56
fd random tty29 tty57
full rtc tty3 tty58
input rtc0 tty30 tty59
kmem sg0 tty31 tty6
kmsg sr0 tty32 tty60
mapper stderr tty33 tty61
mcelog stdin tty34 tty62
mem stdout tty35 tty63
memory_bandwidth tty tty36 tty7
network_latency tty0 tty37 tty8
network_throughput tty1 tty38 tty9
null tty10 tty39 ttyS0
port tty11 tty4 ttyS1
ptmx tty12 tty40 ttyS2
pts tty13 tty41 ttyS3
ram0 tty14 tty42 ubi_ctrl
ram1 tty15 tty43 urandom
ram10 tty16 tty44 vcs
ram11 tty17 tty45 vcs1
ram12 tty18 tty46 vcsa
ram13 tty19 tty47 vcsa1
ram14 tty2 tty48 zero
(initramfs) ls -lagh /dev/disk/by-id/
total 0
drwxr-xr-x 2 0 60 Jul 27 09:48 .
drwxr-xr-x 3 0 60 Jul 27 09:48 ..
lrwxrwxrwx 1 0 9 Jul 27 09:48 ata-QEMU_DVD-ROM_QM00003 -> ../../sr0
(initramfs) ls -lagh /dev/disk/by-id/../../s
sg0 sr0 stderr stdin stdout
(initramfs) ls -lagh /dev/disk/by-id/../../sr0
brw------- 1 0 11, 0 Jul 27 09:48 /dev/disk/by-id/../../sr0
(initramfs)
(initramfs) ls -lagh /dev/s
sg0 sr0 stderr stdin stdout
(initramfs) ls -lagh /dev/s*
crw------- 1 0 21, 0 Jul 27 09:40 /dev/sg0
brw------- 1 0 11, 0 Jul 27 09:40 /dev/sr0
lrwxrwxrwx 1 0 15 Jul 27 09:40 /dev/stderr -> /proc/self/fd/2
lrwxrwxrwx 1 0 15 Jul 27 09:40 /dev/stdin -> /proc/self/fd/0
lrwxrwxrwx 1 0 15 Jul 27 09:40 /dev/stdout -> /proc/self/fd/1

It can not find the disk and mount it and as such the kernel is not loading.


Can it be one of these? modules not found and I got an incompatible hardware somehow?

(initramfs) modprobe -l
kernel/arch/x86/crypto/crc32c-intel.ko
kernel/fs/btrfs/btrfs.ko
kernel/crypto/xor.ko
kernel/crypto/async_tx/async_tx.ko
kernel/crypto/async_tx/async_memcpy.ko
kernel/crypto/async_tx/async_xor.ko
kernel/crypto/async_tx/async_pq.ko
kernel/crypto/async_tx/async_raid6_recov.ko
kernel/drivers/gpio/gpio-generic.ko
kernel/drivers/gpio/gpio-adp5588.ko
kernel/drivers/gpio/gpio-amd8111.ko
kernel/drivers/gpio/gpio-bt8xx.ko
kernel/drivers/gpio/gpio-dwapb.ko
kernel/drivers/gpio/gpio-f7188x.ko
kernel/drivers/gpio/gpio-ich.ko
kernel/drivers/gpio/gpio-it8761e.ko
kernel/drivers/gpio/gpio-lynxpoint.ko
kernel/drivers/gpio/gpio-max730x.ko
kernel/drivers/gpio/gpio-max7300.ko
kernel/drivers/gpio/gpio-max732x.ko
kernel/drivers/gpio/gpio-pca953x.ko
kernel/drivers/gpio/gpio-pcf857x.ko
kernel/drivers/gpio/gpio-sch.ko
kernel/drivers/gpio/gpio-sch311x.ko
kernel/drivers/gpio/gpio-vx855.ko
kernel/drivers/acpi/thermal.ko
kernel/drivers/block/loop.ko
kernel/drivers/block/nvme.ko
kernel/drivers/block/cryptoloop.ko
kernel/drivers/scsi/scsi_transport_spi.ko
kernel/drivers/scsi/scsi_transport_fc.ko
kernel/drivers/scsi/scsi_transport_sas.ko
kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko
kernel/drivers/net/phy/marvell.ko
kernel/drivers/net/phy/lxt.ko
kernel/drivers/net/phy/vitesse.ko
kernel/drivers/net/phy/broadcom.ko
kernel/drivers/net/phy/realtek.ko
kernel/drivers/net/phy/fixed_phy.ko
kernel/drivers/net/phy/mdio-bitbang.ko
kernel/drivers/net/phy/mdio-gpio.ko
kernel/drivers/net/phy/national.ko
kernel/drivers/net/phy/amd.ko
kernel/drivers/net/phy/mdio-bcm-unimac.ko
kernel/drivers/net/ethernet/broadcom/sdk/kernel-bde.ko
kernel/drivers/net/ethernet/broadcom/sdk/user-bde.ko
kernel/drivers/net/ethernet/broadcom/sdk/knet.ko
kernel/drivers/net/ethernet/broadcom/tg3.ko
kernel/drivers/net/ethernet/intel/e1000/e1000.ko
kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
kernel/drivers/net/ethernet/intel/igb/igb.ko
kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
kernel/drivers/net/ethernet/intel/i40e/i40e.ko
kernel/drivers/net/ethernet/intel/ixgb/ixgb.ko
kernel/drivers/net/ethernet/rocker/rocker.ko
kernel/drivers/net/ipvlan/ipvlan.ko
kernel/drivers/net/mii.ko
kernel/drivers/net/mdio.ko
kernel/drivers/net/netconsole.ko
kernel/drivers/net/virtio_net.ko
kernel/drivers/net/vxlan.ko
kernel/drivers/net/nlmon.ko
kernel/drivers/net/vrf.ko
kernel/drivers/message/fusion/mptbase.ko
kernel/drivers/message/fusion/mptscsih.ko
kernel/drivers/message/fusion/mptspi.ko
kernel/drivers/message/fusion/mptfc.ko
kernel/drivers/message/fusion/mptsas.ko
kernel/drivers/usb/host/ohci-platform.ko
kernel/drivers/usb/host/uhci-hcd.ko
kernel/drivers/usb/host/xhci-hcd.ko
kernel/drivers/usb/host/xhci-pci.ko
kernel/drivers/rtc/rtc-ds1307.ko
kernel/drivers/i2c/algos/i2c-algo-bit.ko
kernel/drivers/i2c/algos/i2c-algo-pca.ko
kernel/drivers/i2c/busses/i2c-scmi.ko
kernel/drivers/i2c/busses/i2c-ali1535.ko
kernel/drivers/i2c/busses/i2c-ali1563.ko
kernel/drivers/i2c/busses/i2c-ali15x3.ko
kernel/drivers/i2c/busses/i2c-amd756.ko
kernel/drivers/i2c/busses/i2c-amd756-s4882.ko
kernel/drivers/i2c/busses/i2c-amd8111.ko
kernel/drivers/i2c/busses/i2c-i801.ko
kernel/drivers/i2c/busses/i2c-isch.ko
kernel/drivers/i2c/busses/i2c-ismt.ko
kernel/drivers/i2c/busses/i2c-piix4.ko
kernel/drivers/i2c/busses/i2c-sis5595.ko
kernel/drivers/i2c/busses/i2c-sis630.ko
kernel/drivers/i2c/busses/i2c-via.ko
kernel/drivers/i2c/busses/i2c-viapro.ko
kernel/drivers/i2c/busses/i2c-designware-core.ko
kernel/drivers/i2c/busses/i2c-designware-pci.ko
kernel/drivers/i2c/busses/i2c-gpio.ko
kernel/drivers/i2c/busses/i2c-pca-platform.ko
kernel/drivers/i2c/muxes/i2c-mux-gpio.ko
kernel/drivers/i2c/muxes/i2c-mux-pca9541.ko
kernel/drivers/i2c/muxes/i2c-mux-pca954x.ko
kernel/drivers/i2c/i2c-core.ko
kernel/drivers/i2c/i2c-dev.ko
kernel/drivers/i2c/i2c-mux.ko
kernel/drivers/md/raid456.ko
kernel/drivers/md/md-mod.ko
kernel/drivers/md/dm-mod.ko
kernel/drivers/md/dm-bufio.ko
kernel/drivers/md/dm-snapshot.ko
kernel/drivers/md/dm-mirror.ko
kernel/drivers/md/dm-log.ko
kernel/drivers/md/dm-region-hash.ko
kernel/drivers/md/dm-raid.ko
kernel/drivers/mmc/card/mmc_block.ko
kernel/drivers/mmc/host/ushc.ko
kernel/drivers/hid/hid-cp2112.ko
kernel/drivers/hwmon/hwmon.ko
kernel/net/ipv4/udp_tunnel.ko
kernel/net/ipv6/ip6_udp_tunnel.ko
kernel/lib/raid6/raid6_pq.ko
(initramfs)
(initramfs) modprobe -a

Please advice.
Userlevel 3
Hi @sundsto1 I asked around and the engineers working on VX are stumped. They're not familiar with proxmox, so it's hard for us to diagnose. The best we can come up with is that proxmox is sending the wrong arguments to KVM for some reason, or there was some sort of misconfiguration (like the disk was connected correctly or the VM manager assigned it an unexpected driver).

Have you tried another KVM hypervisor?
Hi,

I should have responded as I got the assistance I needed.
Got a few routers up and running with some routing protocols.
I wish BGP flowspec was better integrated as I saw some API script with some iptables injections.
Otherwise it has been running well and no major problems yet.

The default installation using SCSI and virtio was not playing nice and since I got the word that KVM defaults to IDE I used this installation options for the qxow2 image.

So this was the 1,5 day headache and solution is just too simple it makes you look stupid.


Thanks for the mindshare though, appreciated.


Regards Tomas
Userlevel 3
Oh I was just about to reply that someone else just suggested to me you try running `virsh dumpxml GuestID > guest.xml` as this would allow us to compare how Proxmox is applying the settings vs how Vagrant does so.

But I'm glad you got the help you needed! So it was just a matter of SCSI vs IDE...

Reply