国产 无码 综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

  1. Toy模板網(wǎng)首頁
  2. >Toy博客

RDMA在KVM實現(xiàn)條件

2年前作者：redhat7890分類：Toy博客閱讀(40)違法舉報

這篇具有很好參考價值的文章主要介紹了RDMA在KVM實現(xiàn)條件。希望對大家有所幫助。如果存在錯誤或未考慮完全的地方，請大家不吝賜教，您也可以點擊"舉報違法"按鈕提交疑問。

KVM 支持VF passthrough條件

CPU必須支持 Intel VT-d 或 AMD-Vi（IOMMU）技術(shù)

demsg要包含下述兩部分

  • DMAR: Intel(R) Virtualization Technology for Directed I/O
  • DMAR: IOMMU enabled

檢查CPU是否支持VT-d或AMD-Vi

# dmesg |grep -e?"DMAR"?-e?"IOMMU"|grep -e?"Virtualization"?-e enabled

[????0.000000] DMAR: IOMMU enabled

[????0.001068] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.

[????1.150702] DMAR: Intel(R) Virtualization Technology?for?Directed I/O

內(nèi)核必須支持vfio,?vfio_iommu_type1,?vfio_pci?等模塊

檢查Kernel加載 IOMMU 相關(guān)的內(nèi)核模塊

[root@stgExt1?qemu]# lsmod|grep -e vfio -e iommu

vfio_pci???????????????61440??0

vfio_virqfd????????????16384??1?vfio_pci

vfio_iommu_type1???????36864??0

vfio???????????????????36864??2?vfio_iommu_type1,vfio_pci

irqbypass??????????????16384??422?vfio_pci,kvm

QEMU必須2.0版本以上

centos8.4自帶qemu版本4.2.0，BVT環(huán)境已升級至8.0.2，且QEMU需要重新編譯

configure ./

./configure --prefix=/usr/local/qemu_rdma/ --enable-debug --enable-kvm --enable-vnc --target-list=x86_64-softmmu --enable-spice --enable-spice-protocol --enable-vnc --enable-usb-redir --enable-rdma

QEMU替換步驟

example

ln -sf /usr/local/qemu_rdma/bin/qemu-system-x86_64 /usr/libexec/qemu-kvm

setenforce?0

libvirt 版本是 1.2.9 或更高版本

centos8.4自帶libvirt 版本為6.0.0

KVM支持SR-IOV

我們把SR-IOV創(chuàng)建出的虛擬網(wǎng)卡稱為VF，如下命令可以查看網(wǎng)卡物理端口ens4f0/1（稱PF）最大支持創(chuàng)建的VF均為8個；

KVM支持SR-IOV

我們把SR-IOV創(chuàng)建出的虛擬網(wǎng)卡稱為VF，如下命令可以查看網(wǎng)卡物理端口ens4f0/1（稱PF）最大支持創(chuàng)建的VF均為8個；

# cat /sys/class/net/ens4f0/device/sriov_totalvfs

8

# cat /sys/class/net/ens4f1/device/sriov_totalvfs

8

ens4f0單個網(wǎng)口虛擬出6個VF

# echo?6?> /sys/class/net/ens4f0/device/sriov_numvfs

# lspci|grep Mellanox

b1:00.0?Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6?Lx]

b1:00.1?Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6?Lx]

b1:00.2?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

b1:00.3?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

b1:00.4?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

b1:00.5?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

b1:00.6?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

b1:00.7?Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function

# ip link |grep ens4

261: ens4f0v0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

262: ens4f0v1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

263: ens4f0v2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

264: ens4f0v3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

265: ens4f0v4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

266: ens4f0v5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

18: ens4f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

19: ens4f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

# ip link show ens4f0v0

261: ens4f0v0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether?56:ba:79:b5:fb:3a brd ff:ff:ff:ff:ff:ff

[root@stgExt1?qemu]# ip link show ens4f0v1

262: ens4f0v1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether?42:f9:c8:62:be:fd brd ff:ff:ff:ff:ff:ff

[root@stgExt1?qemu]# ip link show ens4f0v2

263: ens4f0v2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether 2e:2b:21:22:a7:da brd ff:ff:ff:ff:ff:ff

[root@stgExt1?qemu]# ip link show ens4f0v3

264: ens4f0v3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether?22:cd:f8:8e:8b:39?brd ff:ff:ff:ff:ff:ff

[root@stgExt1?qemu]# ip link show ens4f0v4

265: ens4f0v4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether b6:b1:22:d5:28:46?brd ff:ff:ff:ff:ff:ff

[root@stgExt1?qemu]# ip link show ens4f0v5

266: ens4f0v5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu?1500?qdisc mq state UP mode DEFAULT group?default?qlen?1000

????link/ether be:64:4f:36:e0:f7 brd ff:ff:ff:ff:ff:ff

lspci命令行輸出

# lspci -nn |grep Mellanox

b1:00.0?Ethernet controller [0200]: Mellanox Technologies MT2894 Family [ConnectX-6?Lx] [15b3:101f]

b1:00.1?Ethernet controller [0200]: Mellanox Technologies MT2894 Family [ConnectX-6?Lx] [15b3:101f]

b1:00.2?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

b1:00.3?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

b1:00.4?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

b1:00.5?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

b1:00.6?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

b1:00.7?Ethernet controller [0200]: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e]

永久生效還需要

創(chuàng)建文件?/etc/modprobe.d/mlx5.conf，并添加以下內(nèi)容：

cat /etc/modprobe.d/mlx5.conf

options mlx5_core num_vfs=2

為VF接口創(chuàng)建一個udev 規(guī)則/etc/udev/rules.d/ens4f0.rules, 使創(chuàng)建的VF持久化

cat /etc/udev/rules.d/ens4f0.rules

ACTION=="add", SUBSYSTEM=="net", DRIVERS=="mlx5_core", ATTR{device/sriov_numvfs}="8"

重新加載 mlx5_core 內(nèi)核模塊以使配置生效：

modprobe -r mlx5_core && modprobe mlx5_core

$ modprobe -r mlx5_core && modprobe mlx5_core

保存生效后，可以查看到VF，例如：

$ ip link show

$ ip link show

查看RDMA鏈接狀態(tài)

$ ip link show

$ rdma link show

0/1: mlx5_0/1: state ACTIVE physical_state LINK_UP netdev ens1f0np0

1/1: mlx5_1/1: state ACTIVE physical_state LINK_UP netdev ens1f1np1

網(wǎng)口下層Link Layer: Ethernet表示RoCE協(xié)議

# ibstat

CA?'mlx5_0'

????CA type: MT4123

????Number of ports:?1

????Firmware version:?20.30.1004

????Hardware version:?0

????Node GUID:?0xb83fd20300d3e4c6

????System image GUID:?0xb83fd20300d3e4c6

????Port?1:

????????State: Active

????????Physical state: LinkUp

????????Rate:?100

????????Base lid:?0

????????LMC:?0

????????SM lid:?0

????????Capability mask:?0x00010000

????????Port GUID:?0xba3fd2fffed3e4c6

????????Link layer: Ethernet

CA?'mlx5_1'

????CA type: MT4123

????Number of ports:?1

????Firmware version:?20.30.1004

????Hardware version:?0

????Node GUID:?0xb83fd20300d3e4c7

????System image GUID:?0xb83fd20300d3e4c6

????Port?1:

????????State: Active

????????Physical state: LinkUp

????????Rate:?100

????????Base lid:?0

????????LMC:?0

????????SM lid:?0

????????Capability mask:?0x00010000

????????Port GUID:?0xba3fd2fffed3e4c7

????????Link layer: Ethernet

ibv_devinfo -v?的輸出中，每個網(wǎng)絡(luò)接口都可能包含多個 GID（Global Identifier），每個 GID 表示一個全局唯一標識符，用于唯一標識 InfiniBand 網(wǎng)絡(luò)中的節(jié)點或端口。其中，每個 GID 都會指定一個協(xié)議版本，如 RoCE v1 或 RoCE v2。

在?ibv_devinfo -v?命令的輸出中

  • 如果看到?transport: Ethernet，則表示使用以太網(wǎng)協(xié)議；
  • 如果同時看到?RoCE v1?或?RoCE v2，則說明使用了 RoCE 協(xié)議；

ibv_devinfo -v |grep GID

# ibv_devinfo -v

hca_id: mlx5_0

????transport:????????? InfiniBand (0)

????fw_ver:?????????????20.30.1004

????node_guid:????????? b83f:d203:00d3:e4c6

????sys_image_guid:???????? b83f:d203:00d3:e4c6

????vendor_id:??????????0x02c9

????vendor_part_id:?????????4123

????hw_ver:?????????????0x0

????board_id:?????????? LNV0000000017

????phys_port_cnt:??????????1

????max_mr_size:????????????0xffffffffffffffff

????page_size_cap:??????????0xfffffffffffff000

????max_qp:?????????????262144

????max_qp_wr:??????????32768

????device_cap_flags:???????0x25321c36

????????????????????BAD_PKEY_CNTR

????????????????????BAD_QKEY_CNTR

????????????????????AUTO_PATH_MIG

????????????????????CHANGE_PHY_PORT

????????????????????PORT_ACTIVE_EVENT

????????????????????SYS_IMAGE_GUID

????????????????????RC_RNR_NAK_GEN

????????????????????MEM_WINDOW

????????????????????XRC

????????????????????MEM_MGT_EXTENSIONS

????????????????????MEM_WINDOW_TYPE_2B

????????????????????RAW_IP_CSUM

????????????????????MANAGED_FLOW_STEERING

????max_sge:????????????30

????max_sge_rd:?????????30

????max_cq:?????????????16777216

????max_cqe:????????????4194303

????max_mr:?????????????16777216

????max_pd:?????????????8388608

????max_qp_rd_atom:?????????16

????max_ee_rd_atom:?????????0

????max_res_rd_atom:????????4194304

????max_qp_init_rd_atom:????????16

????max_ee_init_rd_atom:????????0

????atomic_cap:???????? ATOMIC_HCA (1)

????max_ee:?????????????0

????max_rdd:????????????0

????max_mw:?????????????16777216

????max_raw_ipv6_qp:????????0

????max_raw_ethy_qp:????????0

????max_mcast_grp:??????????2097152

????max_mcast_qp_attach:????????240

????max_total_mcast_qp_attach:??503316480

????max_ah:?????????????2147483647

????max_fmr:????????????0

????max_srq:????????????8388608

????max_srq_wr:?????????32767

????max_srq_sge:????????????31

????max_pkeys:??????????128

????local_ca_ack_delay:?????16

????general_odp_caps:

????????????????????ODP_SUPPORT

????????????????????ODP_SUPPORT_IMPLICIT

????rc_odp_caps:

????????????????????SUPPORT_SEND

????????????????????SUPPORT_RECV

????????????????????SUPPORT_WRITE

????????????????????SUPPORT_READ

????????????????????SUPPORT_SRQ

????uc_odp_caps:

????????????????????NO SUPPORT

????ud_odp_caps:

????????????????????SUPPORT_SEND

????xrc_odp_caps:

????????????????????SUPPORT_SEND

????????????????????SUPPORT_WRITE

????????????????????SUPPORT_READ

????????????????????SUPPORT_SRQ

????completion timestamp_mask:??????????0x7fffffffffffffff

????hca_core_clock:???????? 156250kHZ

????raw packet caps:

????????????????????C-VLAN stripping offload

????????????????????Scatter FCS offload

????????????????????IP csum offload

????????????????????Delay drop

????device_cap_flags_ex:????????0x3000005425321C36

????????????????????RAW_SCATTER_FCS

????????????????????PCI_WRITE_END_PADDING

????????????????????Unknown flags:?0x3000004000000000

????tso_caps:

????????max_tso:????????????262144

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????rss_caps:

????????max_rwq_indirection_tables:?????????1048576

????????max_rwq_indirection_table_size:?????????2048

????????rx_hash_function:???????????????0x1

????????rx_hash_fields_mask:????????????????0x800000FF

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????max_wq_type_rq:?????????8388608

????packet_pacing_caps:

????????qp_rate_limit_min:? 1kbps

????????qp_rate_limit_max:? 100000000kbps

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????tag matching not supported

????cq moderation caps:

????????max_cq_count:???65535

????????max_cq_period:??4095?us

????maximum available device memory:??? 131072Bytes

????num_comp_vectors:???????63

????????port:???1

????????????state:????????? PORT_ACTIVE (4)

????????????max_mtu:????????4096?(5)

????????????active_mtu:?????1024?(3)

????????????sm_lid:?????????0

????????????port_lid:???????0

????????????port_lmc:???????0x00

????????????link_layer:???? Ethernet

????????????max_msg_sz:?????0x40000000

????????????port_cap_flags:?????0x04010000

????????????port_cap_flags2:????0x0000

????????????max_vl_num:???? invalid value (0)

????????????bad_pkey_cntr:??????0x0

????????????qkey_viol_cntr:?????0x0

????????????sm_sl:??????????0

????????????pkey_tbl_len:???????1

????????????gid_tbl_len:????????255

????????????subnet_timeout:?????0

????????????init_type_reply:????0

????????????active_width:?????? 4X (2)

????????????active_speed:???????25.0?Gbps (32)

????????????phys_state:???? LINK_UP (5)

????????????GID[??0]:?????? fe80:0000:0000:0000:ba3f:d2ff:fed3:e4c6, RoCE v1

????????????GID[??1]:?????? fe80::ba3f:d2ff:fed3:e4c6, RoCE v2

hca_id: mlx5_1

????transport:????????? InfiniBand (0)

????fw_ver:?????????????20.30.1004

????node_guid:????????? b83f:d203:00d3:e4c7

????sys_image_guid:???????? b83f:d203:00d3:e4c6

????vendor_id:??????????0x02c9

????vendor_part_id:?????????4123

????hw_ver:?????????????0x0

????board_id:?????????? LNV0000000017

????phys_port_cnt:??????????1

????max_mr_size:????????????0xffffffffffffffff

????page_size_cap:??????????0xfffffffffffff000

????max_qp:?????????????262144

????max_qp_wr:??????????32768

????device_cap_flags:???????0x25321c36

????????????????????BAD_PKEY_CNTR

????????????????????BAD_QKEY_CNTR

????????????????????AUTO_PATH_MIG

????????????????????CHANGE_PHY_PORT

????????????????????PORT_ACTIVE_EVENT

????????????????????SYS_IMAGE_GUID

????????????????????RC_RNR_NAK_GEN

????????????????????MEM_WINDOW

????????????????????XRC

????????????????????MEM_MGT_EXTENSIONS

????????????????????MEM_WINDOW_TYPE_2B

????????????????????RAW_IP_CSUM

????????????????????MANAGED_FLOW_STEERING

????max_sge:????????????30

????max_sge_rd:?????????30

????max_cq:?????????????16777216

????max_cqe:????????????4194303

????max_mr:?????????????16777216

????max_pd:?????????????8388608

????max_qp_rd_atom:?????????16

????max_ee_rd_atom:?????????0

????max_res_rd_atom:????????4194304

????max_qp_init_rd_atom:????????16

????max_ee_init_rd_atom:????????0

????atomic_cap:???????? ATOMIC_HCA (1)

????max_ee:?????????????0

????max_rdd:????????????0

????max_mw:?????????????16777216

????max_raw_ipv6_qp:????????0

????max_raw_ethy_qp:????????0

????max_mcast_grp:??????????2097152

????max_mcast_qp_attach:????????240

????max_total_mcast_qp_attach:??503316480

????max_ah:?????????????2147483647

????max_fmr:????????????0

????max_srq:????????????8388608

????max_srq_wr:?????????32767

????max_srq_sge:????????????31

????max_pkeys:??????????128

????local_ca_ack_delay:?????16

????general_odp_caps:

????????????????????ODP_SUPPORT

????????????????????ODP_SUPPORT_IMPLICIT

????rc_odp_caps:

????????????????????SUPPORT_SEND

????????????????????SUPPORT_RECV

????????????????????SUPPORT_WRITE

????????????????????SUPPORT_READ

????????????????????SUPPORT_SRQ

????uc_odp_caps:

????????????????????NO SUPPORT

????ud_odp_caps:

????????????????????SUPPORT_SEND

????xrc_odp_caps:

????????????????????SUPPORT_SEND

????????????????????SUPPORT_WRITE

????????????????????SUPPORT_READ

????????????????????SUPPORT_SRQ

????completion timestamp_mask:??????????0x7fffffffffffffff

????hca_core_clock:???????? 156250kHZ

????raw packet caps:

????????????????????C-VLAN stripping offload

????????????????????Scatter FCS offload

????????????????????IP csum offload

????????????????????Delay drop

????device_cap_flags_ex:????????0x3000005425321C36

????????????????????RAW_SCATTER_FCS

????????????????????PCI_WRITE_END_PADDING

????????????????????Unknown flags:?0x3000004000000000

????tso_caps:

????????max_tso:????????????262144

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????rss_caps:

????????max_rwq_indirection_tables:?????????1048576

????????max_rwq_indirection_table_size:?????????2048

????????rx_hash_function:???????????????0x1

????????rx_hash_fields_mask:????????????????0x800000FF

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????max_wq_type_rq:?????????8388608

????packet_pacing_caps:

????????qp_rate_limit_min:? 1kbps

????????qp_rate_limit_max:? 100000000kbps

????????supported_qp:

????????????????????SUPPORT_RAW_PACKET

????tag matching not supported

????cq moderation caps:

????????max_cq_count:???65535

????????max_cq_period:??4095?us

????maximum available device memory:??? 131072Bytes

????num_comp_vectors:???????63

????????port:???1

????????????state:????????? PORT_ACTIVE (4)

????????????max_mtu:????????4096?(5)

????????????active_mtu:?????1024?(3)

????????????sm_lid:?????????0

????????????port_lid:???????0

????????????port_lmc:???????0x00

????????????link_layer:???? Ethernet

????????????max_msg_sz:?????0x40000000

????????????port_cap_flags:?????0x04010000

????????????port_cap_flags2:????0x0000

????????????max_vl_num:???? invalid value (0)

????????????bad_pkey_cntr:??????0x0

????????????qkey_viol_cntr:?????0x0

????????????sm_sl:??????????0

????????????pkey_tbl_len:???????1

????????????gid_tbl_len:????????255

????????????subnet_timeout:?????0

????????????init_type_reply:????0

????????????active_width:?????? 4X (2)

????????????active_speed:???????25.0?Gbps (32)

????????????phys_state:???? LINK_UP (5)

????????????GID[??0]:?????? fe80:0000:0000:0000:ba3f:d2ff:fed3:e4c7, RoCE v1

????????????GID[??1]:?????? fe80::ba3f:d2ff:fed3:e4c7, RoCE v2

更多參考：

QEMU官網(wǎng)?Download QEMU - QEMU文章來源地址http://www.zghlxwxcb.cn/news/detail-823154.html

到了這里，關(guān)于RDMA在KVM實現(xiàn)條件的文章就介紹完了。如果您還想了解更多內(nèi)容，請在右上角搜索TOY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！

本文來自互聯(lián)網(wǎng)用戶投稿，該文觀點僅代表作者本人，不代表本站立場。本站僅提供信息存儲空間服務(wù)，不擁有所有權(quán)，不承擔(dān)相關(guān)法律責(zé)任。如若轉(zhuǎn)載，請注明出處： 如若內(nèi)容造成侵權(quán)/違法違規(guī)/事實不符，請點擊違法舉報進行投訴反饋，一經(jīng)查實，立即刪除！

領(lǐng)支付寶紅包贊助服務(wù)器費用

相關(guān)文章

  • 服務(wù)器安裝KVM環(huán)境并安裝虛擬機（centOS7）

    服務(wù)器安裝KVM環(huán)境并安裝虛擬機（centOS7）

    一. 安裝KVM環(huán)境 1. 檢測是否支持KVM ????????cat /proc/cpuinfo | egrep \\\'vmx|svm\\\' ????????返回結(jié)果中有vmx或svm，說明cpu是支持的 2.?關(guān)閉SELinux，將 /etc/sysconfig/selinux 中的? SELinux=enforcing ?修改為? SELinux=disabled ????????vi /etc/sysconfig/selinux 3. 安裝KVM環(huán)境 4. 重啟服務(wù)器，加載k

    2024年04月09日
    瀏覽(23)

  • 在阿里云Linux服務(wù)器上部署MySQL數(shù)據(jù)庫流程

    阿里云百科分享在阿里云Linux服務(wù)器上部署MySQL數(shù)據(jù)庫流程，MySQL是一個關(guān)系型數(shù)據(jù)庫管理系統(tǒng)，常用于LAMP和LNMP等網(wǎng)站場景中。本教程介紹如何在Linux系統(tǒng)ECS實例上安裝、配置以及遠程訪問MySQL數(shù)據(jù)庫。 目錄 背景信息 Alibaba Cloud Linux 2/3、CentOS 7.x 步驟一：安裝MySQL 步驟二：配置

    2024年02月13日
    瀏覽(86)
  • 必看＞＞＞＞Linux數(shù)據(jù)庫被其他服務(wù)器遠程訪問（修改權(quán)限、開設(shè)端口）

    必看＞＞＞＞Linux數(shù)據(jù)庫被其他服務(wù)器遠程訪問（修改權(quán)限、開設(shè)端口）

    目錄 一：修改權(quán)限 1.1 進入Linux數(shù)據(jù)庫 1.2 修改數(shù)據(jù)庫的遠程連接權(quán)限 1.2.1 數(shù)據(jù)庫遠程權(quán)限修改命令 1.2.2 數(shù)據(jù)庫遠程權(quán)限查看命名 1.3?給Linux機添加端口 1.4 遠程數(shù)據(jù)庫連接 文章中的四：Linux中mysql數(shù)據(jù)庫的安裝 1.2.1 數(shù)據(jù)庫遠程權(quán)限修改命令 grant all privileges on *.* to \\\'root\\\'@\\\'%\\\'id

    2023年04月17日
    瀏覽(92)
  • Linux服務(wù)器裝mysql數(shù)據(jù)庫并且連接數(shù)據(jù)庫（詳細教程）(阿里云)

    Linux服務(wù)器裝mysql數(shù)據(jù)庫并且連接數(shù)據(jù)庫（詳細教程）(阿里云)

    廢話不多說，直接上教程。 1.首先執(zhí)行如下命令，更新YUM源。 2.執(zhí)行如下命令，安裝MySQL。 3.執(zhí)行如下命令，查看MySQL版本號。 4.返回結(jié)果如下，表示您已成功安裝MySQL。 5.執(zhí)行如下命令，啟動MySQL服務(wù)。 6. 執(zhí)行如下命令，設(shè)置MySQL服務(wù)開機自啟動。 7.配置MySQL的root用戶密碼。

    2024年02月06日
    瀏覽(96)
  • Linux服務(wù)器安裝部署MongoDB數(shù)據(jù)庫 - 無公網(wǎng)IP遠程連接

    Linux服務(wù)器安裝部署MongoDB數(shù)據(jù)庫 - 無公網(wǎng)IP遠程連接

    目錄 前言 1. 配置Mongodb源 2. 安裝MongoDB 3. 局域網(wǎng)連接測試 4. 安裝cpolar內(nèi)網(wǎng)穿透 5. 配置公網(wǎng)訪問地址 6. 公網(wǎng)遠程連接 7. 固定連接公網(wǎng)地址 8. 使用固定地址連接 轉(zhuǎn)載自Cpolar Lisa文章：Linux服務(wù)器安裝部署MongoDB數(shù)據(jù)庫 - 無公網(wǎng)IP遠程連接「內(nèi)網(wǎng)穿透」 MongoDB是一個介于關(guān)系數(shù)據(jù)庫

    2024年02月02日
    瀏覽(30)
  • 【MySQL數(shù)據(jù)庫】--- 初始數(shù)據(jù)庫以及MySQL數(shù)據(jù)庫在Linux云服務(wù)器下載（詳細教程）

    【MySQL數(shù)據(jù)庫】--- 初始數(shù)據(jù)庫以及MySQL數(shù)據(jù)庫在Linux云服務(wù)器下載（詳細教程）

    ?? 博客主頁：??@披星戴月的賈維斯 ?? 歡迎關(guān)注：??點贊??收藏??留言 ??系列專欄：?? MYSQL數(shù)據(jù)庫 ??請不要相信勝利就像山坡上的蒲公英一樣唾手可得，但是請相信，世界上總有一些美好值得我們?nèi)σ愿?，哪怕粉身碎骨?? ??一起加油，去追尋、去成為更好的自

    2023年04月24日
    瀏覽(101)
  • 【MySQL數(shù)據(jù)庫】--- 初識數(shù)據(jù)庫以及MySQL數(shù)據(jù)庫在Linux云服務(wù)器下載（詳細教程）

    【MySQL數(shù)據(jù)庫】--- 初識數(shù)據(jù)庫以及MySQL數(shù)據(jù)庫在Linux云服務(wù)器下載（詳細教程）

    ?? 博客主頁：??@披星戴月的賈維斯 ?? 歡迎關(guān)注：??點贊??收藏??留言 ??系列專欄：?? MYSQL數(shù)據(jù)庫 ??請不要相信勝利就像山坡上的蒲公英一樣唾手可得，但是請相信，世界上總有一些美好值得我們?nèi)σ愿埃呐路凵硭楣牵?? ??一起加油，去追尋、去成為更好的自

    2024年02月03日
    瀏覽(23)
  • 本地連接線上服務(wù)器數(shù)據(jù)庫（基于MobaXterm實現(xiàn)）

    本地連接線上服務(wù)器數(shù)據(jù)庫（基于MobaXterm實現(xiàn)）

    ?本地?zé)o法直接連接線上服務(wù)器，需要由ssh隧道代理實現(xiàn)，用xshell、MobaXterm等工具皆可實現(xiàn)。由于習(xí)慣使用MobaXterm，本文以此工具為演示。 線上測試服務(wù)器一臺、本地電腦安裝MobaXterm、navicat、（pycharm--數(shù)據(jù)庫自動化使用） 打開mobaXterm，進入Tunneling 點擊【New SSH tunnel】，新建

    2024年02月08日
    瀏覽(108)

  • 重啟Linux服務(wù)器 Oracle 數(shù)據(jù)庫步驟 重啟數(shù)據(jù)庫startup 報ORA-01031 insufficient privileges錯誤解決

    在一次重啟數(shù)據(jù)庫的時候，沒有正確按照步驟重啟數(shù)據(jù)庫，導(dǎo)致服務(wù)器重啟。 正確步驟及詳解： (1) su - oracle 打開Xshell，連接到數(shù)據(jù)庫所在的linux機器。若用戶為root，請輸入命令“su - oracle”并回車，若要密碼，輸入密碼后并回車，就切換到了oracle用戶下。 檢測方法：“#”變

    2024年02月15日
    瀏覽(165)
  • linux 17day 堡壘機 堡壘機下載 堡壘機安裝 堡壘機使用 堡壘機管理服務(wù)器 堡壘機管理數(shù)據(jù)庫

    linux 17day 堡壘機 堡壘機下載 堡壘機安裝 堡壘機使用 堡壘機管理服務(wù)器 堡壘機管理數(shù)據(jù)庫

    https://jumpserver.org/ 沒有注冊的需要注冊一個賬號 即可下載 配置站點url 配置郵箱 創(chuàng)建要管理的服務(wù)器 現(xiàn)在還不能 管理 因為還沒有配置用戶名和密碼 創(chuàng)建 特權(quán)用戶用于管理 創(chuàng)建普通用戶 添加命令過濾 命令過濾創(chuàng)建好 之后就需要 給用戶名 和管理添加 管理用戶也是一樣的

    2024年02月20日
    瀏覽(28)

覺得文章有用就打賞一下文章作者

支付寶掃一掃打賞

博客贊助

微信掃一掃打賞

請作者喝杯咖啡吧~博客贊助

支付寶掃一掃領(lǐng)取紅包，優(yōu)惠每天領(lǐng)

二維碼1

領(lǐng)取紅包

二維碼2

領(lǐng)紅包