Problem Installing Proxmox MG 5.0 on Hyper-V

[Philipp Rümmele]

Hi,
we use Proxmox V4.1-7 as a Hyper-V virtuall Machine. I want to upgrade to V5 - but i can't install on hyper-v (Server 2012R2).. tryed on different Servers (HP DL380G5, IBM eServer - Both are Dual Quad Xeons ) .. i was able to install a running Proxmox V5 on my workstation (i7-3xxx) but i can't start this VM on any of my Win2012R2 Servers.
I get a "Kernel Panic - not syncing " error short after booting
see the attached screenshot - picture

Any hints, tips how to get Proxmox Mail Gateway 5 up and running with Hyper-V 2012 R2 ?

Thanks and Greetings
Philipp

 

[tom]

Works here. Do you run it as a "generation 1" VM?

 

[Philipp Rümmele]

Hi,
thanks for your reply..
Yes - i installed it as "Generation 1" - on both servers..

(i also tryed it as Generation 2.. but it did't boot because of UEFI Errors)

greetings
Philipp

 

[Philipp Rümmele]

installation okay:
- hyper-v on a windwos 10 workstation - i7-3770, 16gb, gtx1050, .. nothing special

can't install / can't boot the vm, which i created on my workstation -> kernel panic
- hyper-v on server 2012 r2 - an a hp dl380 g5 server - dual xeon e5345, 24gb, ..
- hyper-v on server 2012 r2 - an a ibm xserver x3650 - dual xeon e5420, 32gb, ..

is there a boot switch i can use in grub to start linux in a kind of compatibillity mode ?
(sorry, i'm not a linux expert..)

greetings
Philipp

 

[Philipp Rümmele]

Update: I gerated a log file of the boot process ( turned on Com1 on the VM, send output to named pipe, logged output in textfile)
started kernel with ..../pmg-root ro console=ttyS1,115200n8

First Try:

...
[ 2.691170] i2c /dev entries driver
[ 2.699064] device-mapper: uevent: version 1.0.3
[ 2.711749] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[ 2.752039] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.761034] NET: Registered protocol family 10
[ 2.797785] PANIC: double fault, error_code: 0x0
[ 2.804336] CPU: 1 PID: 110 Comm: modprobe Not tainted 4.13.13-5-pve #1
[ 2.804336] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012
[ 2.804336] task: ffff888b34e5d800 task.stack: ffff9d1981d38000
[ 2.804336] RIP: 0010:vprintk_default+0xb/0x50
[ 2.804336] RSP: 0000:fffffe000002e000 EFLAGS: 00010046
[ 2.804336] RAX: 0000000000000000 RBX: fffffe000002e118 RCX: 0000000000000001
[ 2.804336] RDX: 0000000000000000 RSI: fffffe000002e018 RDI: ffffffffb0292141
....

Second Try:


...
[ 1.889158] rtc_cmos 00:00: RTC can wake from S4
[ 1.914492] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1

[ 1.914591] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0


[ 1.921555] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[ 1.923331] i2c /dev entries driver
[ 1.924658] device-mapper: uevent: version 1.0.3
[ 1.926426] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[ 1.929729] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.933757] NET: Registered protocol family 10
[ 1.941244] PANIC: double fault, error_code: 0x0
[ 1.944027] CPU: 2 PID: 109 Comm: modprobe Not tainted 4.13.13-5-pve #1
[ 1.944027] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012
[ 1.944027] task: ffff8ed38080d800 task.stack: ffffba3c01dd8000
[ 1.944027] RIP: 0010:vprintk_default+0xb/0x50
[ 1.944027] RSP: 0000:fffffe000005a000 EFLAGS: 00010046
[ 1.944027] RAX: 0000000000000000 RBX: fffffe000005a118 RCX: 0000000000000001
[ 1.944027] RDX: 0000000000000000 RSI: fffffe000005a018 RDI: ffffffff93a92141
[ 1.944027] RBP: fffffe000005a008 R08: ffffffff93ae3716 R09: ffffffff93a9213c
[ 1.944027] R10: fffffe000005a080 R11: 0000000000000000 R12: ffffffff93a91c7d
[ 1.944027] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1.944027]
...


full logs are attached as text files

any hints? any ideas?

thanks and greetings
Philipp

 

[Rene Chirivi]

This same error happens to me but in proxmox ve 3.1

 

[tom]

...

Second Try:

any hints? any ideas?

thanks and greetings
Philipp

Did you try a fresh install from the ISO (generation 1) on these servers?

 

[Philipp Rümmele]

Hi,
yes - my first try was to create a new vm (gen.1) - and install Proxmox Mail Gateway from the downloaded iso...
that didn't work on both servers - so i tried it on my workstation, where it worked..

Attached you can see the linux boot log, when i try to install

Thanks for any other ideas..
greetings
Philipp

 

[Vladislav Solovei]

Same problem with KVM
CPU-s: 2 x Xeon L5420
Host OS: CentOS 6.8, kernel 2.6.32-504.el6.x86_64
Host Hypervisor: KVM