Recent content by moarph

Since I'm not on a hosted environment - I thought this step is not needed. Can you confirm, taht this step is required even in a home-network envornment?

Hello, after I upgraded to 7 I lost the network connection. ifupdown2 is NOT installed since I sticked to he upgrade guide. # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network...

did you remove the vmware tools (if they were installed) before you migrated? just tried it and sticked to the wiki. even used the mergeide from proxmox directly. No success

did you try to set the scsi controller also to lsi? Yes I also set the scsi controller to lsi and set the hard disks to scsi - no success what is your pveversion -v ? proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve) pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)...

I am currently trying to migrate from ESXi 5.5 to Proxmox 5.0. For my Server 2008 guests there were no problems at all. Server 2012R2 and up will fail booting with BSOD. I tried to use MergeIDE from here: https://www.andysblog.de/windows-mergeide-v3-0 but had no success. Both 2008 and 2012R2...

@john: Only adding the swapping and the min_free_kbytes didin't do the job for me. The system performed slightly better but kvm still crashed. After the kernel update i deleted the swapiness and the min_free_kbytes and it still works very well.

Depends on the OS of the client. Linux guest have usually no problems and shut down as expected. For Windows guest the Qemu-Agent should do the job. Generally the shutdown cmommand is like pushing the power off button of a hardware (ACPI) computer. Usually the system shuts itsself down after...

Yes I had problems with the stock kernel. with the following one: "pve-kernel-4.4.35-2-pve: 4.4.35-78~test1" backup works like it always used to work. My biggest problem was I blamed everything else but Proxmox because I put a new RAID card in and upgraded my backup-server.

Same here...latest Kernel will kill my windows machines during backup...

Since it has actuallay to be fixed by hp it will probably never be fixed...would be nice to have a 'i know what i'm doing' boot flag for this. regarding vswitch you will find good information in the proxmox wiki. however i managed to patch the kernel and it seemed to work though but the upgrades...

Hey proppa, negativ same error, however if you want the nic isolated you might use vswitch for that....or if it has to be be isolated on the 'hardware' layer you need to patch the kernel...

OK I changed the BIOS like the advisory said...but no luck. Same error-message....

yes he might be our help :) I read the advisory but i can't even get the commandline tools since this seems for RHEL only...correct me if i'm wrong

Is there any news on this? Could the changes be importet in the proxmox kernel? SInce it seems that many HP users are affected

This correct, why don't you put your kernel changes to the proxmox bugtracker?