Recent content by Semmo

proxmox-ve: 6.4-1 (running kernel: 5.4.143-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-helper: 6.4-8 pve-kernel-5.4: 6.4-7 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-5.4.140-1-pve: 5.4.140-1 pve-kernel-5.4.128-1-pve...

I got the same mail from Hetzner. And the reported MAC addresses belong to some of the fwbr devices (Firwall Bridge from Proxmox). That's weird.. that shouldn't happen?! But they closed the case before I reported back :(

Just to complete this thread. I found a solution: I switched the SCSI Controller of the VM from "VirtIO SCSI" to "Default (LSI 53C895A)" and it booted up completely.

Maybe that has nothing to do with the error but you are missing the proxmox updates for non-subsribers. You have still selected the enterprise repository: Ign:8 https://enterprise.proxmox.com/debian/pve stretch InRelease Err:10 https://enterprise.proxmox.com/debian/pve stretch Release 401...

Okay right now I get this, don' know what I changed but that's more then last time:

Hi there. Is anyone using Metasploitable2 (or 3) on Proxmox? I converted the metasploitable2 vdmk to qcow2 and also tried it with my lvm based storage but I have no luck. It boots up but I can not pass this point: Has anyone a idea what I could try? On a local Virtualbox the vmdk runs fine.

@MarcoP & @tom Thank you! :)

I tried the version "0.1.173-2" and it worked. So maybe version 0.1.173-5 is just buggy.

I installed a VM with Windows 10 Pro 1909 like mentioned in the best practices here: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices I downloaded the ISO for the windows virtio drivers version 0.1.173-5 (latest) but i can not complete the msi installer. It does a rollback and in...

I finally captured something when my server freezes... but now I don't know what to do with it :/ That's my netconsole output right before the crash: [616084.497241] general protection fault: 0000 [#2] SMP PTI [616084.497243] kvm[11243]: segfault at 2c ip 00007f36cb5eea48 sp 00007fff0e5562c0...

No it's not reachable. I also tried it over my internal switch only > no route to host Nothing helpful in the logs so far. Is there anyway to increase the loglevel maybe?

So you mean i kill the process right now, restart it in the foreground and just wait for the next crash? Thank you for the help btw :)

For my 501 machine (also stopped but without a process still running or a log entry) there is no PID file. The 504 has a PID which do not match the processes.

root@proxmox:/etc# qm status 504 --verbose cpus: 1 disk: 0 diskread: 0 diskwrite: 0 maxdisk: 34359738368 maxmem: 536870912 mem: 0 name: syncthing netin: 1278583348 netout: 1113400037 nics: tap504i0: netout: 102865911 netin: 337972211 tap504i2...

Hi there! I had this issue multiple times now and just want to find out whats going on. When i log into my proxmox host I see an unusual load on my node and several VMs had stopped. I can not start them again because the kvm (id 504) is still running with a high cpu load (see screenshot). An...