summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/graphic/716
blob: 04b37daaffa158cbcf43e6ba7d15b859fd7d3ee9 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
graphic: 0.958
virtual: 0.936
debug: 0.928
device: 0.862
arm: 0.825
semantic: 0.733
architecture: 0.644
VMM: 0.629
ppc: 0.501
vnc: 0.493
network: 0.415
mistranslation: 0.350
boot: 0.316
hypervisor: 0.312
performance: 0.310
PID: 0.302
KVM: 0.292
risc-v: 0.286
assembly: 0.252
TCG: 0.244
socket: 0.237
permissions: 0.233
kernel: 0.231
peripherals: 0.230
user-level: 0.176
register: 0.162
files: 0.160
i386: 0.022
x86: 0.016

using "-device scsi-cd" option on arm64 platform
Description of problem:
When using OpenStack to create a virtual machine instance, I need to configure the password of the root user through cloud-init. I use the ConfigDriver method, in which OpenStack will mount a virtual disk in iso9660 format to the virtual machine instance. The command line generated by OpenStack is shown above. You can see that this ConfigDrive virtual disk is mounted via "--device scsi-cd". But when I entered the virtual machine instance and used lsblk, blkid and searched in /dev/disk/by-label, I did not find the virtual disk that should be mounted. In addition, I don't have more debugging messages or error messages. I want to know if the "scsi-cd" is not fully adapted to arm64 platform.