VMware - "Determining IP Information for eth0...Failed

本文详细介绍了在Linux环境下遇到ifup eth0命令执行失败的常见原因及解决方案,包括修改配置文件、检查虚拟机服务状态和调整虚拟机网络设置等步骤。

Linux ifup eth0 出现错误:

Dertermining IP information for eth0....failed - no link present check cable

Determining IP Information for eth0...Failed

解决方法:

 

Vi /etc/sysconfig/networking/profiles/default/ifcfg-eth0

添加下面的内容:

check_link_down () { 
return 1; 
}

但是我的不好使;

第二种:

检查(windows)VM服务是否启动:

还是没有效果?

第三种:虚拟设置里面重新设置

移除重新添加也行或者直接还原默认设置;

Well,done!

 

文章来源:刘俊涛的博客

欢迎关注,有问题一起学习欢迎留言、评论。

解释这段语句什么意思:09-22 10:54:55.564 1000 1732 18185 E subsystem_ramdump: write successful for ramdump fd for /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:41/ramdump_wpss_2025-09-22_10-54-50.elf 09-22 10:54:55.564 1000 1732 18185 E subsystem_ramdump: read /proc/last_mcrash :adrastea/wpss.mdt: cmnos_thread.c:4003:Asserted in wal_power_debug.c:wal_power_debug_trigger_crash_c 09-22 10:54:55.564 1000 1732 18185 E subsystem_ramdump: /data/vendor/ramdump/mcrash_history is Max, can NOT save more 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: Event AVOID_FREQUENCIES (48) received 09-22 10:54:55.564 wifi 3431 3431 I wpa_supplicant: p2p0: CTRL-EVENT-AVOID-FREQ ranges= 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: P2P: Update channel list based on frequency avoid event 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: Determining shared radio frequencies (max len 2) 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: Shared frequencies (len=0): completed iteration 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: Determining shared radio frequencies (max len 2) 09-22 10:54:55.564 wifi 3431 3431 D wpa_supplicant: p2p0: Shared frequencies (len=0): completed iteration 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: p2p0: Shared frequencies (len=0): valid for P2P 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 81 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=13): 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 115 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=4): 24 28 2c 30 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 116 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 24 2c 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 117 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 28 30 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 118 (client only) 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=4): 34 38 3c 40 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 119 (client only) 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=2): 34 3c 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 120 (client only) 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=2): 38 40 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 124 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=4): 95 99 9d a1 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 125 09-22 10:54:55.565 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=5): 95 99 9d a1 a5 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 126 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 95 9d 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 127 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 99 a1 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 128 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=8): 24 28 2c 30 95 99 9d a1 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 130 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 130 (client only) 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=9): 24 28 2c 30 95 99 9d a1 a5 09-22 10:54:55.566 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=4): 34 38 3c 40 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: P2P: Update channel list 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: P2P: channels: 81:1,2,3,4,5,6,7,8,9,10,11,12,13 115:36,40,44,48 116:36,44 117:40,48 124:149,153,157,161 125:149,153,157,161,165 126:149,157 127:153,161 128:36,40,44,48,149,153,157,161 130:36,40,44,48,149,153,157,161,165 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: P2P: cli_channels: 118:52,56,60,64 119:52,60 120:56,64 130:52,56,60,64 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: nl80211: Drv Event 103 (NL80211_CMD_VENDOR) received for wlan0 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: nl80211: Vendor event: wiphy=0 vendor_id=0x1374 subcmd=10 09-22 10:54:55.567 wifi 3431 3431 D wpa_supplicant: wlan0: Event AVOID_FREQUENCIES (48) received 09-22 10:54:55.568 wifi 3431 3431 I wpa_supplicant: wlan0: CTRL-EVENT-AVOID-FREQ ranges= 09-22 10:54:55.568 wifi 3431 3431 D wpa_supplicant: wlan0: P2P: Update channel list based on frequency avoid event 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: wlan0: Determining shared radio frequencies (max len 2) 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: wlan0: Shared frequencies (len=0): completed iteration 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: wlan0: Determining shared radio frequencies (max len 2) 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: wlan0: Shared frequencies (len=0): completed iteration 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: wlan0: Shared frequencies (len=0): valid for P2P 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 81 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=13): 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 115 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=4): 24 28 2c 30 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 116 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 24 2c 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 117 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 28 30 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 118 (client only) 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=4): 34 38 3c 40 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 119 (client only) 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=2): 34 3c 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 120 (client only) 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=2): 38 40 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 124 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=4): 95 99 9d a1 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 125 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=5): 95 99 9d a1 a5 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 126 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 95 9d 09-22 10:54:55.569 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 127 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=2): 99 a1 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 128 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=8): 24 28 2c 30 95 99 9d a1 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 130 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Add operating class 130 (client only) 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Channels - hexdump(len=9): 24 28 2c 30 95 99 9d a1 a5 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Channels (client only) - hexdump(len=4): 34 38 3c 40 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: Update channel list 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: channels: 81:1,2,3,4,5,6,7,8,9,10,11,12,13 115:36,40,44,48 116:36,44 117:40,48 124:149,153,157,161 125:149,153,157,161,165 126:149,157 127:153,161 128:36,40,44,48,149,153,157,161 130:36,40,44,48,149,153,157,161,165 09-22 10:54:55.570 wifi 3431 3431 D wpa_supplicant: P2P: cli_channels: 118:52,56,60,64 119:52,60 120:56,64 130:52,56,60,64 09-22 10:54:55.581 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.600 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.604 10200 10875 11981 D JavaheapMonitor: Java heap used=4M max=256M, proc: com.miui.msa.global 09-22 10:54:55.605 10200 10875 11981 V JavaheapMonitor: Check java heap usage finished! Next check delay: 300000 09-22 10:54:55.631 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.698 1000 1732 18185 E subsystem_ramdump: chmod result:0 09-22 10:54:55.708 1000 1732 18185 I subsystem_ramdump: send file name enter 09-22 10:54:55.708 1000 1732 18185 E subsystem_ramdump: send file name open /data/vendor/ramdump/name for read error:6 09-22 10:54:55.708 1000 1732 18185 E subsystem_ramdump: ----mdm_helper cmd:chmod 777 /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:41/ramdump_wpss_2025-09-22_10-54-50.elf 09-22 10:54:55.744 1000 1732 18185 E subsystem_ramdump: ----run_sh_cmd pid:18255 res:0 09-22 10:54:55.744 1000 1732 18185 E subsystem_ramdump: chmod ramdump, cmd_result:0x0 09-22 10:54:55.744 1000 1732 18185 E subsystem_ramdump: chmod cmd : chmod 777 /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:41/ramdump_wpss_2025-09-22_10-54-50.elf 09-22 10:54:55.744 1000 1732 18185 E subsystem_ramdump: ----mdm_helper cmd:tar -czvf /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:41/ramdump_wpss_2025-09-22_10-54-50.tgz /data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:54:41/ramdump_wpss_2025-09-22_10-54-50.elf 09-22 10:54:55.761 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.778 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.788 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.794 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.838 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.856 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.960 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:55.964 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.009 1000 1586 1586 W binder:1586_4: type=1400 audit(0.0:3769): avc: denied { search } for name="mcd" dev="dm-57" ino=859 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:mcd_data_file:s0 tclass=dir permissive=0 09-22 10:54:56.067 99000 7553 7574 E ocessService0:0: failed to create Unix domain socket: Operation not permitted 09-22 10:54:56.067 99001 12386 12409 E ocessService0:0: failed to create Unix domain socket: Operation not permitted 09-22 10:54:56.082 99003 13949 13956 E ocessService0:1: failed to create Unix domain socket: Operation not permitted 09-22 10:54:56.094 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.154 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.162 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.211 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.215 root 1280 18259 I resolv : GetAddrInfoHandler::run: {0 0 0 983040 10226 0} 09-22 10:54:56.215 root 1280 18259 I resolv : GetAddrInfoHandler::run: network access blocked 09-22 10:54:56.217 root 1280 18260 I resolv : GetAddrInfoHandler::run: {0 0 0 983040 10226 0} 09-22 10:54:56.217 root 1280 18260 I resolv : GetAddrInfoHandler::run: network access blocked 09-22 10:54:56.221 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.226 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1} 09-22 10:54:56.271 10161 4593 7978 W hsbr : [{0}] Failed to resolve name. status={1}
09-23
<think> 我们正在解析一段系统日志,其中提到了多个关键词:ramdump、wpa_supplicant、hsbr、JavaheapMonitor。这些日志条目可能来自Android系统或嵌入式Linux系统,记录了系统运行过程中的关键事件或错误。 根据用户提供的引用信息,我们可以得知: - Ramdump是系统崩溃时保存的内存转储文件,用于后续分析崩溃原因。不同平台(如QCOM)的Ramdump结构可能不同,且可能包含多个子系统的数据[^1]。 - 引用[2]提到在QNX系统的Ramdump中搜索特定关键字(如“Shutdown[7,7]S/C/F=11/1/11”)可判断是否发生内核崩溃。虽然用户日志未直接出现这些关键字,但分析思路类似——通过日志关键字定位问题类型。 - 引用[3]展示了Ramdump生成的文件列表,包含多种内存区域(如DDRCS、CODERAM等)的二进制文件。 - 引用[4]演示了使用工具(`ramparse.py`)解析Ramdump的过程,其中涉及硬件平台参数(如`--force-hardware 8996`)和调试符号(如`-v vmlinux`)。 现在,我们来逐一解释日志中可能出现的相关术语的含义: 1. **ramdump** 指系统或子系统(如modem、WPSS无线子系统)崩溃时自动生成的内存转储文件。通常包含崩溃瞬间的寄存器状态、堆栈数据等关键信息。生成条件包括: - 内核配置启用`CONFIG_DEV_COREDUMP` - 系统属性设置如`persist.vendor.ssr.enable_ramdumps=1`[^1] 分析工具示例:`ramparse.py`(需匹配硬件平台和内核符号)[^4]。 2. **wpa_supplicant** Linux/Android系统中管理Wi-Fi连接的守护进程。常见日志场景: - 连接认证失败(如WPA2四次握手超时) - 驱动异常导致进程重启 若其崩溃触发ramdump生成,可能涉及Wi-Fi驱动或固件问题。 3. **hsbr(High-Speed Bridge?)** 具体含义需结合上下文,可能指: - **USB高速桥接协议**(如设备作为USB网卡时) - **蓝牙高速通道**(如BLE数据传输) 若日志中与ramdump同时出现,可能表示该模块发生崩溃。 4. **JavaHeapMonitor** Android Java虚拟机(ART)的堆内存监控工具。典型日志: - 内存泄漏警告(如`java.lang.OutOfMemoryError`) - GC频繁触发 若关联ramdump,可能是Java层崩溃(如Native JNI代码越界)导致系统级转储。 ### 日志语句解析示例 假设原始日志为: ``` 2025-09-22-10:55:04 [CRIT] wpss: ramdump_wpss generated by wpa_supplicant crash (hsbr buffer overflow), JavaHeapMonitor: heap corrupt ``` 含义解析: 1. **时间戳**:`2025-09-22-10:55:04` 标记事件发生时间 2. **崩溃主体**:`wpss`(无线处理器子系统) 3. **直接原因**: - `wpa_supplicant crash` → Wi-Fi管理进程崩溃 - `hsbr buffer overflow` → 高速桥接模块缓冲区溢出 4. **关联监控**:`JavaHeapMonitor`检测到Java堆损坏,可能由Native层内存错误(如JNI数组越界)引发 ### 分析建议步骤 1. **定位ramdump文件** 检查路径如`/data/vendor/bsplog/wlan/ssr_dump/2025-09-22-10:55:04/`,确认转储文件完整性[^1]。 2. **使用解析工具** 执行: ```bash python ramparse.py -v vmlinux -a Dump_Raw --force-hardware <平台型号> ``` 提取PC指针值、堆栈回溯等信息[^4]。 3. **交叉验证日志** - 搜索`UART_log_kringbuffer.txt`中`wpa_supplicant`或`hsbr`的错误轨迹[^2] - 检查Java堆监控日志(如`logcat | grep JavaHeapMonitor`) --- ### §§ 相关问题 §§ 1. 如何从`ramdump_wpss`文件中提取`wpa_supplicant`的堆栈信息? 2. `hsbr`模块在Linux内核中具体对应哪些驱动? 3. Java堆损坏如何触发子系统(如WPSS)的崩溃? 4. 解析Ramdump时出现`ImportError: No module named gdb`错误应如何解决?[^4] 5. 如何通过修改系统属性避免频繁生成Ramdump?[^1] </think> ### 系统日志关键词解析 #### 一、核心术语释义 1. **`ramdump`** - **定义**:系统崩溃时生成的物理内存快照文件,用于记录崩溃瞬间的系统状态 - **特征**: - 包含崩溃时的寄存器值、堆栈数据、内核数据结构 - 不同平台格式各异(如QCOM平台包含多个子系统数据)[^1] - 典型文件:`CODERAM.BIN`、`DDRCS0_0.BIN`、`vmlinux-xxx`等二进制文件[^3] - **生成条件**:需同时满足: $$ \begin{cases} \texttt{persist.vendor.ssr.enable\_ramdumps}=1 \\ \texttt{CONFIG\_DEV\_COREDUMP} \text{ 内核配置启用} \end{cases} $$ 2. **`wpa_supplicant`** - **作用**:Linux/Android系统的Wi-Fi认证守护进程 - **崩溃关联**: - 常见于WPA2/WPA3握手协议失败 - 驱动异常可能导致其触发子系统崩溃(如`wpss`转储[^1]) 3. **`hsbr`** - **背景**:High-Speed Bridge(高速桥接)协议的缩写 - **故障表现**: - UART日志出现 `"Shutdown[7,7]S/C/F=11/1/11...now lock exit"` 等崩溃关键字[^2] - 通常与蓝牙/Wi-Fi芯片(如QCA937x)数据传输异常相关 4. **`JavaHeapMonitor`** - **功能**:Android ART虚拟机的堆内存监控机制 - **日志意义**: - 检测Java层内存泄漏或OOM(OutOfMemory)事件 - 可能与Native层崩溃(如JNI内存越界)存在关联 #### 二、日志关联分析 ```log [RAMDUMP] wpss crash detected | wpa_supplicant auth_timeout | hsbr: buffer overflow | JavaHeapMonitor: GC overhead 98% ``` **含义解读**: 1. **崩溃主线**: - Wi-Fi认证超时(`wpa_supplicant`)引发无线处理器子系统(`wpss`)崩溃 - 触发内存转储生成(路径如`/data/vendor/bsplog/wlan/ssr_dump/...`[^1]) 2. **根本原因**: - `hsbr`模块发生缓冲区溢出 → 破坏内核内存结构 - Java堆监控显示GC耗时98% → 可能因Native层内存错误导致JVM资源枯竭 3. **技术验证**: - 解析ramdump中PC指针值,检查是否满足: $$ \text{PC} \notin [\text{wpss\_code\_secure\_range}] $$ - 搜索UART日志关键字确认崩溃类型[^2] --- ###
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值