My Oracle Support Banner

[PCA 2.3.3] VM Guest with Odd maxvcpu Does not Bootup Correctly (Doc ID 2485293.1)

Last updated on JULY 14, 2020

Applies to:

Private Cloud Appliance - Version 2.3.3 to 2.3.3 [Release 2.0]
Linux x86-64

Symptoms

In PCA 2.3.3 when customer have VMs with odd number of maxvcpus (such as 7, 11, 13 and 15), the VM cannot start fine.

The console of the VM is in blank "white screen only" and cannot be log in through ssh.

[root@ovcacn08r1 ~]# xm list
Name ID Mem VCPUs State Time(s)
0004fb0000060000183e309d240bc8e1 33 35843 5 -b---- 9432.1
0004fb0000060000674fe496e02bd454 34 8195 2 -b---- 19956.7
0004fb0000060000c11f454076d46b32 32 16387 8 -b---- 23222.2
0004fb0000060000cb07b0be234a093a 40 4195 1 r----- 260.0 <<<<<<<<<<<<<<< VM with 7 maxvcpus
0004fb0000060000d628317aed375866 22 39939 8 -b---- 77798.2
0004fb0000060000f0e0b025974cefb0 2 4192 2 -b---- 37287.0
Domain-0 0 6045 20

The qemu-dm log of the VM seems stuck always here:

[root@ovcacn08r1 ~]# tail -f /var/log/xen/qemu-dm-0004fb0000060000cb07b0be234a093a.log
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
cirrus vga map change while on lfb mode

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.