yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81780
[Bug 1865120] [NEW] arm64 vm boot failed when set num_pcie_ports to 28
Public bug reported:
We are testing OpenStack on Phytium,FT2000PLUS
root@compute01:~# lscpu
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 16
NUMA node(s): 8
Model name: Phytium,FT2000PLUS
CPU max MHz: 2200.0000
CPU min MHz: 1000.0000
BogoMIPS: 3600.00
NUMA node0 CPU(s): 0-7
NUMA node1 CPU(s): 8-15
NUMA node2 CPU(s): 16-23
NUMA node3 CPU(s): 24-31
NUMA node4 CPU(s): 32-39
NUMA node5 CPU(s): 40-47
NUMA node6 CPU(s): 48-55
NUMA node7 CPU(s): 56-63
Flags: fp asimd evtstrm crc32
The problem we initially met are we are not able to attach to more than
2 volumes (virtio-blk) if config drive enabled. We somehow work around
the problem by using scsi-bus instead.
But we are still interesting to make plug more than 2 virtio-blk devices
possible, and after some investigation I think `num_pcie_ports` might be
too small (looks like it default to 9 if unspecified), and `pcie-root`
does not allow hot plugging, and `pcie-root-port` does not allow more
than 1 slots, so the only way I am thinking to mitigate the problem is
to increase this option to maximum.
But the current problem is vms with previously working images failed to
boot and when I try to virsh console, I only saw the uefi shell console.
Maybe this is not a bug for `code`, but I definitely think it is
necessary to improve the doc and make it easier to understand these
terms. I am glad to provide to additional details if asked. thanks
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1865120
Title:
arm64 vm boot failed when set num_pcie_ports to 28
Status in OpenStack Compute (nova):
New
Bug description:
We are testing OpenStack on Phytium,FT2000PLUS
root@compute01:~# lscpu
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 16
NUMA node(s): 8
Model name: Phytium,FT2000PLUS
CPU max MHz: 2200.0000
CPU min MHz: 1000.0000
BogoMIPS: 3600.00
NUMA node0 CPU(s): 0-7
NUMA node1 CPU(s): 8-15
NUMA node2 CPU(s): 16-23
NUMA node3 CPU(s): 24-31
NUMA node4 CPU(s): 32-39
NUMA node5 CPU(s): 40-47
NUMA node6 CPU(s): 48-55
NUMA node7 CPU(s): 56-63
Flags: fp asimd evtstrm crc32
The problem we initially met are we are not able to attach to more
than 2 volumes (virtio-blk) if config drive enabled. We somehow work
around the problem by using scsi-bus instead.
But we are still interesting to make plug more than 2 virtio-blk
devices possible, and after some investigation I think
`num_pcie_ports` might be too small (looks like it default to 9 if
unspecified), and `pcie-root` does not allow hot plugging, and `pcie-
root-port` does not allow more than 1 slots, so the only way I am
thinking to mitigate the problem is to increase this option to
maximum.
But the current problem is vms with previously working images failed
to boot and when I try to virsh console, I only saw the uefi shell
console.
Maybe this is not a bug for `code`, but I definitely think it is
necessary to improve the doc and make it easier to understand these
terms. I am glad to provide to additional details if asked. thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1865120/+subscriptions