Unable to boot – please use a kernel appropriate for your CPU.

最新推荐文章于 2024-08-31 18:53:38 发布
原创 最新推荐文章于 2024-08-31 18:53:38 发布 · 7w 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#features #ubuntu #扩展

本文记录了使用VirtualBox安装Ubuntu过程中遇到的问题及解决方法。当安装程序提示内核所需的特性未在CPU上找到时，需要通过设置使能PAE/NX扩展特性来解决问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

   今天用VirtualBox装了个ubuntu系统，正在装的时候就提示：

  This kernel requires the following features not present on theCPU:
    Unable to boot – please use akernel appropriate for your CPU.


选中对应的虚拟系统——设置——系统——处理器——扩展特性------启用 PAE/NX！
iOS开发：运行多个模拟器之后出现Unable to boot device due to insufficient system resources提示
全沾软贱开发攻城狮
03-11 1万+
在iOS开发中，在运行代码之后可能会做多个屏幕尺寸的对比，来查看界面控件的布局和位置，但是如果同时打开多个Xcode里面的模拟器手机尺寸之后，就不能再打开手机模拟器了，原因是模拟器的内存超出最大的限额，苹果开发者官网也有相关的解释文档，要想解决这个问题，方法就是通过修改内存大小来启动更多的模拟器，最好的方法就是通过关闭/重启模拟设备和其他Mac应用程序释放资源。 一、错误问题提示： Unabl...
ubuntu 编译升级内核
luchang的专栏
04-23 1252
当前内核4.15,是由4.14莫名其妙通过软件升级程序自动升级上来的。 打算自行编译配置升级到4.16 先到镜像地址：http://mirror.bjtu.edu.cn/kernel/linux/kernel/ 下载4.16.9版本源码 编译前使用make mrproper命令清理掉编译痕迹，该指令与make clean有区别，可以理解为更彻底。 图形化配置xconfig的依赖需要 fl...
linux 学习笔记一入门问题总结
08-04
linux 学习笔记一入门问题总结。
VirtualBox 错误：This kernel requires the following features not present on the CPU
09-15
主要介绍了VirtualBox 错误：This kernel requires the following features not present on the CPU的相关资料,希望通过本文能帮助到大家，解决这样的问题，需要的朋友可以参考下
Android RecyclerView的使用过程遇到的问题
热门推荐
ReminderFish
10-20 3万+
RecyclerView滚动显示图片
oauth0 oauth2_使用oauth确保本机React
weixin_26646901的博客
09-06 914
oauth0 oauth2In this tutorial, we will set up a React Native application to work with OAuth. We’ll use FusionAuth for auth, but the React Native code should work with any OAuth compliant server.在本教程中，...
问题解决： Unable to boot – please use a kernel appropriate for your CPU.
话题在绕弯的专栏
07-08 3020
今天用VirtualBox 4.1.8 装了个ubuntu-12.04，正在装的时候就提示： This kernel requires the following features not present on the CPU: Unable to boot – please use a kernel appropriate for your CPU. 百度了一下，找到解决方案与我的
Unable to boot : please use a kernel appropriate for your cpu
weixin_33882443的博客
02-25 273
假设你在virtualbox里得到这种提示信息：                  Unable to boot - please use a kernel appropriate for your CPU 以下的解决的方法，能够帮你： 1.重新启动你的电脑进入BIOS中，里面有选项虚拟化技术之类的，让其选项【Enable】 假设这样做还解决不了你的问题，尝试另外一种办...
解决方法unable to boot - please use a kernel appropri
haveysun的专栏
06-05 1463
使用虚拟机软件Oracle VM VirtualBox来进行安装centos6.2时提示以下信息： This kernel requires the following features not present on the CPU: Unable to boot – please use a kernel appropriate for your CPU. 解决方法： 选中对应的虚拟系统——设置——系统——处理器——扩展特性 ------启用 PAE/NX! 如果是灰色，点击不了，请先关闭正在运行的安装界
VirtualBox-“please use a kernel appropriate for your cpu”
技术改变人生
11-24 2668
This kernel requires the following features not present on the CPU: pae Unable to boot – please use a kernel appropriate for your CPU. 百度了一下，找到解决方案： 选中对应的虚拟系统——设置——系统——处理器——启用 PAE/NX！ 重启搞定！
#!/bin/sh # This script installs Ollama on Linux. # It detects the current operating system architecture and installs the appropriate version of Ollama. set -eu red="$( (/usr/bin/tput bold || :; /usr/bin/tput setaf 1 || :) 2>&-)" plain="$( (/usr/bin/tput sgr0 || :) 2>&-)" status() { echo ">>> $*" >&2; } error() { echo "${red}ERROR:${plain} $*"; exit 1; } warning() { echo "${red}WARNING:${plain} $*"; } TEMP_DIR=$(mktemp -d) cleanup() { rm -rf $TEMP_DIR; } trap cleanup EXIT available() { command -v $1 >/dev/null; } require() { local MISSING='' for TOOL in $*; do if ! available $TOOL; then MISSING="$MISSING $TOOL" fi done echo $MISSING } [ "$(uname -s)" = "Linux" ] || error 'This script is intended to run on Linux only.' ARCH=$(uname -m) case "$ARCH" in x86_64) ARCH="amd64" ;; aarch64|arm64) ARCH="arm64" ;; *) error "Unsupported architecture: $ARCH" ;; esac IS_WSL2=false KERN=$(uname -r) case "$KERN" in *icrosoft*WSL2 | *icrosoft*wsl2) IS_WSL2=true;; *icrosoft) error "Microsoft WSL1 is not currently supported. Please use WSL2 with 'wsl --set-version <distro> 2'" ;; *) ;; esac VER_PARAM="${OLLAMA_VERSION:+?version=$OLLAMA_VERSION}" SUDO= if [ "$(id -u)" -ne 0 ]; then # Running as root, no need for sudo if ! available sudo; then error "This script requires superuser permissions. Please re-run as root." fi SUDO="sudo" fi NEEDS=$(require curl awk grep sed tee xargs) if [ -n "$NEEDS" ]; then status "ERROR: The following tools are required but missing:" for NEED in $NEEDS; do echo " - $NEED" done exit 1 fi for BINDIR in /usr/local/bin /usr/bin /bin; do echo $PATH | grep -q $BINDIR && break || continue done OLLAMA_INSTALL_DIR=$(dirname ${BINDIR}) if [ -d "$OLLAMA_INSTALL_DIR/lib/ollama" ] ; then status "Cleaning up old version at $OLLAMA_INSTALL_DIR/lib/ollama" $SUDO rm -rf "$OLLAMA_INSTALL_DIR/lib/ollama" fi status "Installing ollama to $OLLAMA_INSTALL_DIR" $SUDO install -o0 -g0 -m755 -d $BINDIR $SUDO install -o0 -g0 -m755 -d "$OLLAMA_INSTALL_DIR/lib/ollama" status "Downloading Linux ${ARCH} bundle" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" if [ "$OLLAMA_INSTALL_DIR/bin/ollama" != "$BINDIR/ollama" ] ; then status "Making ollama accessible in the PATH in $BINDIR" $SUDO ln -sf "$OLLAMA_INSTALL_DIR/ollama" "$BINDIR/ollama" fi # Check for NVIDIA JetPack systems with additional downloads if [ -f /etc/nv_tegra_release ] ; then if grep R36 /etc/nv_tegra_release > /dev/null ; then status "Downloading JetPack 6 components" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-jetpack6.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" elif grep R35 /etc/nv_tegra_release > /dev/null ; then status "Downloading JetPack 5 components" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-jetpack5.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" else warning "Unsupported JetPack version detected. GPU may not be supported" fi fi install_success() { status 'The Ollama API is now available at 127.0.0.1:11434.' status 'Install complete. Run "ollama" from the command line.' } trap install_success EXIT # Everything from this point onwards is optional. configure_systemd() { if ! id ollama >/dev/null 2>&1; then status "Creating ollama user..." $SUDO useradd -r -s /bin/false -U -m -d /usr/share/ollama ollama fi if getent group render >/dev/null 2>&1; then status "Adding ollama user to render group..." $SUDO usermod -a -G render ollama fi if getent group video >/dev/null 2>&1; then status "Adding ollama user to video group..." $SUDO usermod -a -G video ollama fi status "Adding current user to ollama group..." $SUDO usermod -a -G ollama $(whoami) status "Creating ollama systemd service..." cat <<EOF | $SUDO tee /etc/systemd/system/ollama.service >/dev/null [Unit] Description=Ollama Service After=network-online.target [Service] ExecStart=$BINDIR/ollama serve User=ollama Group=ollama Restart=always RestartSec=3 Environment="PATH=$PATH" [Install] WantedBy=default.target EOF SYSTEMCTL_RUNNING="$(systemctl is-system-running || true)" case $SYSTEMCTL_RUNNING in running|degraded) status "Enabling and starting ollama service..." $SUDO systemctl daemon-reload $SUDO systemctl enable ollama start_service() { $SUDO systemctl restart ollama; } trap start_service EXIT ;; *) warning "systemd is not running" if [ "$IS_WSL2" = true ]; then warning "see https://learn.microsoft.com/en-us/windows/wsl/systemd#how-to-enable-systemd to enable it" fi ;; esac } if available systemctl; then configure_systemd fi # WSL2 only supports GPUs via nvidia passthrough # so check for nvidia-smi to determine if GPU is available if [ "$IS_WSL2" = true ]; then if available nvidia-smi && [ -n "$(nvidia-smi | grep -o "CUDA Version: [0-9]*\.[0-9]*")" ]; then status "Nvidia GPU detected." fi install_success exit 0 fi # Don't attempt to install drivers on Jetson systems if [ -f /etc/nv_tegra_release ] ; then status "NVIDIA JetPack ready." install_success exit 0 fi # Install GPU dependencies on Linux if ! available lspci && ! available lshw; then warning "Unable to detect NVIDIA/AMD GPU. Install lspci or lshw to automatically detect and install GPU dependencies." exit 0 fi check_gpu() { # Look for devices based on vendor ID for NVIDIA and AMD case $1 in lspci) case $2 in nvidia) available lspci && lspci -d '10de:' | grep -q 'NVIDIA' || return 1 ;; amdgpu) available lspci && lspci -d '1002:' | grep -q 'AMD' || return 1 ;; esac ;; lshw) case $2 in nvidia) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[10DE\]' || return 1 ;; amdgpu) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[1002\]' || return 1 ;; esac ;; nvidia-smi) available nvidia-smi || return 1 ;; esac } if check_gpu nvidia-smi; then status "NVIDIA GPU installed." exit 0 fi if ! check_gpu lspci nvidia && ! check_gpu lshw nvidia && ! check_gpu lspci amdgpu && ! check_gpu lshw amdgpu; then install_success warning "No NVIDIA/AMD GPU detected. Ollama will run in CPU-only mode." exit 0 fi if check_gpu lspci amdgpu || check_gpu lshw amdgpu; then status "Downloading Linux ROCm ${ARCH} bundle" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-rocm.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" install_success status "AMD GPU ready." exit 0 fi CUDA_REPO_ERR_MSG="NVIDIA GPU detected, but your OS and Architecture are not supported by NVIDIA. Please install the CUDA driver manually https://docs.nvidia.com/cuda/cuda-installation-guide-linux/" # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-7-centos-7 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-8-rocky-8 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-9-rocky-9 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#fedora install_cuda_driver_yum() { status 'Installing NVIDIA repository...' case $PACKAGE_MANAGER in yum) $SUDO $PACKAGE_MANAGER -y install yum-utils if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo" >/dev/null ; then $SUDO $PACKAGE_MANAGER-config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo else error $CUDA_REPO_ERR_MSG fi ;; dnf) if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo" >/dev/null ; then $SUDO $PACKAGE_MANAGER config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo else error $CUDA_REPO_ERR_MSG fi ;; esac case $1 in rhel) status 'Installing EPEL repository...' # EPEL is required for third-party dependencies such as dkms and libvdpau $SUDO $PACKAGE_MANAGER -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-$2.noarch.rpm || true ;; esac status 'Installing CUDA driver...' if [ "$1" = 'centos' ] || [ "$1$2" = 'rhel7' ]; then $SUDO $PACKAGE_MANAGER -y install nvidia-driver-latest-dkms fi $SUDO $PACKAGE_MANAGER -y install cuda-drivers } # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#ubuntu # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#debian install_cuda_driver_apt() { status 'Installing NVIDIA repository...' if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-keyring_1.1-1_all.deb" >/dev/null ; then curl -fsSL -o $TEMP_DIR/cuda-keyring.deb https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-keyring_1.1-1_all.deb else error $CUDA_REPO_ERR_MSG fi case $1 in debian) status 'Enabling contrib sources...' $SUDO sed 's/main/contrib/' < /etc/apt/sources.list | $SUDO tee /etc/apt/sources.list.d/contrib.list > /dev/null if [ -f "/etc/apt/sources.list.d/debian.sources" ]; then $SUDO sed 's/main/contrib/' < /etc/apt/sources.list.d/debian.sources | $SUDO tee /etc/apt/sources.list.d/contrib.sources > /dev/null fi ;; esac status 'Installing CUDA driver...' $SUDO dpkg -i $TEMP_DIR/cuda-keyring.deb $SUDO apt-get update [ -n "$SUDO" ] && SUDO_E="$SUDO -E" || SUDO_E= DEBIAN_FRONTEND=noninteractive $SUDO_E apt-get -y install cuda-drivers -q } if [ ! -f "/etc/os-release" ]; then error "Unknown distribution. Skipping CUDA installation." fi . /etc/os-release OS_NAME=$ID OS_VERSION=$VERSION_ID PACKAGE_MANAGER= for PACKAGE_MANAGER in dnf yum apt-get; do if available $PACKAGE_MANAGER; then break fi done if [ -z "$PACKAGE_MANAGER" ]; then error "Unknown package manager. Skipping CUDA installation." fi if ! check_gpu nvidia-smi || [ -z "$(nvidia-smi | grep -o "CUDA Version: [0-9]*\.[0-9]*")" ]; then case $OS_NAME in centos|rhel) install_cuda_driver_yum 'rhel' $(echo $OS_VERSION | cut -d '.' -f 1) ;; rocky) install_cuda_driver_yum 'rhel' $(echo $OS_VERSION | cut -c1) ;; fedora) [ $OS_VERSION -lt '39' ] && install_cuda_driver_yum $OS_NAME $OS_VERSION || install_cuda_driver_yum $OS_NAME '39';; amzn) install_cuda_driver_yum 'fedora' '37' ;; debian) install_cuda_driver_apt $OS_NAME $OS_VERSION ;; ubuntu) install_cuda_driver_apt $OS_NAME $(echo $OS_VERSION | sed 's/\.//') ;; *) exit ;; esac fi if ! lsmod | grep -q nvidia || ! lsmod | grep -q nvidia_uvm; then KERNEL_RELEASE="$(uname -r)" case $OS_NAME in rocky) $SUDO $PACKAGE_MANAGER -y install kernel-devel kernel-headers ;; centos|rhel|amzn) $SUDO $PACKAGE_MANAGER -y install kernel-devel-$KERNEL_RELEASE kernel-headers-$KERNEL_RELEASE ;; fedora) $SUDO $PACKAGE_MANAGER -y install kernel-devel-$KERNEL_RELEASE ;; debian|ubuntu) $SUDO apt-get -y install linux-headers-$KERNEL_RELEASE ;; *) exit ;; esac NVIDIA_CUDA_VERSION=$($SUDO dkms status | awk -F: '/added/ { print $1 }') if [ -n "$NVIDIA_CUDA_VERSION" ]; then $SUDO dkms install $NVIDIA_CUDA_VERSION fi if lsmod | grep -q nouveau; then status 'Reboot to complete NVIDIA CUDA driver install.' exit 0 fi $SUDO modprobe nvidia $SUDO modprobe nvidia_uvm fi # make sure the NVIDIA modules are loaded on boot with nvidia-persistenced if available nvidia-persistenced; then $SUDO touch /etc/modules-load.d/nvidia.conf MODULES="nvidia nvidia-uvm" for MODULE in $MODULES; do if ! grep -qxF "$MODULE" /etc/modules-load.d/nvidia.conf; then echo "$MODULE" | $SUDO tee -a /etc/modules-load.d/nvidia.conf > /dev/null fi done fi status "NVIDIA GPU ready." install_success
05-14
1. **CPU架构检测**：使用 `uname -m` 命令识别系统架构（x86_64/arm64） 2. **内核版本验证**：检查 `/proc/version` 确保内核版本≥5.4 3. **二进制包匹配**： ```bash case $(uname -m) in x86_64) ARCH="amd64...
springboot基于小程序的物联网管理平台
2401_86117024的博客
08-31 2263
Key words:目 录1概 述。
第六章：Reminders实验：第二部分[Learn Android Studio 汉化教程]
weixin_30443075的博客
12-17 553
Learn Android Studio 汉化教程 Reminders Lab: Part 2 This chapter covers capturing user input through the use of custom dialog boxes. We alsocontinue to demonstrate the use of adapters and an ...
【React Native】请求设备权限
ZhangKui-01的博客
09-28 6407
React Native请求用户权限 Request user permissions from React Native, iOS + Android 参考链接：https://www.npmjs.com/package/react-native-permissions 一、如何使用 1.1 添加组件库：npm install --save react-native-permission...
简单Dream-please use a kernel appropriate for your CPU.
chemzh的博客
11-21 1113
报错： 重装系统后，再次用vmware server 安装rac测试环境，无法安装，报错 This kernel requires an x86-64 CPU,but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU. 解决过程 1 一开始排查电脑操作系
VirtualBox安装OS异常提示：Unable to boot - please use a kernel appropriate for your CPU.
weixin_33939843的博客
07-19 317
转自：http://yyjlinux.iteye.com/blog/1728974VirtualBox上，启动安装CentOS时提示：This kernel requires the following features not present on the CPU:paeUnable to boot - please use a kernel appropriate for...
不能启动:please use a kernel for your cpu问题解决
AinUser的博客
07-17 1263
上面的问题是virtual Box中安装系统的时候，不能启动 首先关闭虚拟机，检查虚拟机设置是否问题如图2 切换到系统标签——处理器，勾选启用 PAE/NX选项，如图3，确定；
Your local changes would be overwritten by merge.Commit, stash or revert them to proceed.
最新发布
05-28
<think>好的，用户遇到了Git合并时本地更改会被覆盖的问题，需要解决方案。根据之前的引用资料，解决方法主要有commit、stash和revert三种。首先，我得确认用户的具体情况，比如他们的本地更改是否已经完成，是否需要保留，或者是否可以丢弃。用户可能不太清楚这三种方法的适用场景，需要详细解释每个选项的步骤和优缺点。比如，commit适用于需要保留更改的情况，stash适合临时保存以便后续恢复，而revert则是直接撤销更改，适用于不需要保留的情况。需要结构清晰，分点说明，每个方法都给出操作步骤和适用场景，帮助用户理解哪种情况最适合他们。还要注意使用中文，避免技术术语过于复杂，让用户容易理解。同时，生成相关问题，可能涉及如何恢复stash的内容，或者如何避免频繁冲突等，扩展用户的知识点。另外，要确保LaTeX格式正确，但在这个问题中可能用不上数学公式，所以主要关注代码块和引用标识。检查引用是否正确，比如引用[^1]和[^2]的来源是否相关，用户提供的引用内容是否准确对应解决方案。 最后，确保回答真实可靠，操作步骤准确无误，避免误导用户。可能还需要提醒用户根据具体情况选择方法，比如如果有未完成的实验性代码，stash可能是更好的选择，而如果是确定要保留的修改，则应该commit。</think>要解决Git合并时本地更改被覆盖的问题，可根据不同场景选择以下三种方法： ### 一、提交本地更改（commit） **适用场景**：当本地更改已测试通过且需要保留到版本历史中。 **操作步骤**： 1. 将改动添加到暂存区： ```bash git add . # 添加所有文件 # 或指定文件 git add file1.txt file2.py ``` 2. 提交更改并添加描述： ```bash git commit -m "完成用户登录模块优化" ``` 3. 执行合并操作： ```bash git merge origin/main ``` **优点**：保留完整的开发记录，便于后续追溯[^1]。 ### 二、暂存更改（stash） **适用场景**：需要临时保存未完成的修改（如调试代码），优先处理合并操作。 **操作步骤**： 1. 保存当前工作状态： ```bash git stash # 可选添加备注 git stash save "用户登录模块调试代码" ``` 2. 查看暂存记录列表： ```bash git stash list ``` 3. 合并远程分支： ```bash git merge origin/main ``` 4. 恢复暂存内容： ```bash git stash pop # 恢复并删除最近一次暂存 # 或指定特定暂存 git stash apply stash@{1} ``` **优点**：保持工作目录整洁，特别适合处理紧急合并任务[^2]。 ### 三、撤销本地更改（revert） **适用场景**：本地修改可丢弃（如实验性代码或错误修改）。 **操作步骤**： 1. 撤销所有未提交的修改： ```bash git checkout -- . # 全部文件 # 或指定文件 git checkout -- file1.txt ``` 2. 执行合并操作： ```bash git merge origin/main ``` **风险提示**：此操作不可逆，需确认文件无需保留。 --- ### 对比决策表 | 方法 | 保留记录 | 可恢复性 | 适用阶段 | |---------|----------|----------|------------------| | commit | ✅ | ✅ | 功能开发完成时 | | stash | ❌ | ✅ | 开发中途临时切换 | | revert | ❌ | ❌ | 放弃无效修改 | ### 扩展应用场景 - 当存在多个暂存时，可用`git stash list`查看记录，通过`git stash apply stash@{n}`精准恢复 - 合并后出现冲突时，可使用`git mergetool`可视化工具解决冲突 - 长期分支开发推荐使用`git rebase`保持提交历史线性
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值