Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan error umum yang mungkin Anda alami saat menggunakan virtualisasi bertingkat dan metode untuk menyelesaikan error tersebut. Untuk informasi selengkapnya
tentang virtualisasi bertingkat, lihat
Membuat VM bertingkat.
Tidak dapat memulai VM bertingkat
Jika project Anda merupakan bagian dari organisasi, organisasi Anda mungkin telah menonaktifkan kemampuan untuk membuat VM dengan virtualisasi bertingkat. Pastikan
virtualisasi bertingkat diizinkan sebelum mencoba membuat VM yang
mengaktifkan virtualisasi bertingkat.
Prosesor tidak menampilkan virtualisasi bertingkat
Jika grep -c vmx /proc/cpuinfo perintah menampilkan 0 dan melaporkan bahwa VM tidak diaktifkan untuk bertingkat, pastikan Anda memulai VM dengan platform CPU Haswell atau yang lebih baru. Untuk informasi selengkapnya, lihat Ringkasan virtualisasi
bertingkat.
Tidak dapat keluar dari VM bertingkat
Jika tidak menjalankan screen sebelum setiap sesi VM bertingkat, Anda dapat
menonaktifkan VM bertingkat atau menghentikan proses dari terminal lain. Untuk menonaktifkan VM bertingkat, jalankan perintah poweroff dari dalam VM bertingkat.
Atau, login ke VM host di terminal lain dan akhiri prosesnya, lalu jalankan screen di VM host sebelum Anda memulai VM bertingkat baru.
iptables tidak meneruskan traffic
iptables menyelesaikan aturan dari atas ke bawah. Pastikan aturan Anda memiliki prioritas
yang lebih tinggi daripada aturan lainnya.
Pastikan tidak ada aturan bertentangan yang mengganggu paket Anda.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eNested virtualization might be disabled at the organizational level, so verify that it's permitted before creating VMs with nested virtualization enabled.\u003c/p\u003e\n"],["\u003cp\u003eIf the processor isn't displaying nested virtualization, ensure the VM is started with a CPU platform of Haswell or later.\u003c/p\u003e\n"],["\u003cp\u003eIf you are unable to exit a nested VM, use \u003ccode\u003epoweroff\u003c/code\u003e to shut it down, or log into the host VM from another terminal to end the process and run \u003ccode\u003escreen\u003c/code\u003e for new sessions.\u003c/p\u003e\n"],["\u003cp\u003eWhen \u003ccode\u003eiptables\u003c/code\u003e fails to forward traffic, ensure that your forwarding rules have higher priority than other rules and that no conflicting rules are present.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting nested virtualization\n\n*** ** * ** ***\n\nThis document describes common errors that you may run into when using nested\nvirtualization and methods for resolving those errors. For more information\nabout nested virtualization, see\n[Creating nested VMs](/compute/docs/instances/nested-virtualization/creating-nested-vms).\n\nCan't start nested VM\n---------------------\n\nIf your project is part of an organization, your organization might have\ndisabled the ability to create VMs with nested virtualization. Make sure that\n[nested virtualization is allowed](/compute/docs/instances/nested-virtualization/managing-constraint#checking_whether_nested_virtualization_is_allowed) before you try to create a VM that has\nnested virtualization enabled.\n\nProcessor not displaying nested virtualization\n----------------------------------------------\n\nIf the `grep -c vmx /proc/cpuinfo` command returns `0` and reports that the VM\nis not enabled for nesting, make sure that you have started your VM with a CPU\nplatform of Haswell or later. For more information, see [Nested virtualization\noverview](/compute/docs/instances/nested-virtualization/overview).\n\nCan't exit nested VM\n--------------------\n\nIf you did not run `screen` before each nested VM session, you can either\nshut down the nested VM or stop the process from another terminal. To shut down\nthe nested VM, run the `poweroff` command from within your nested VM.\nAlternatively, log into the host VM in another terminal and end the process,\nthen run `screen` on the host VM before you start a new nested VM.\n\n`iptables` not forwarding traffic\n---------------------------------\n\n- `iptables` resolve rules from top to bottom. Make sure your rules are higher priority than other rules.\n- Check that there are no conflicting rules intercepting your packets.\n- Consider flushing your `iptables`:\n\n | **Note:** Flushing `iptables` disables your firewall. You should only do this if you want to start over configuring your firewall.\n 1. First, set the default policies:\n\n sudo iptables -P INPUT ACCEPT\n sudo iptables -P FORWARD ACCEPT\n sudo iptables -P OUTPUT ACCEPT\n\n 2. Next, flush all tables and chains, and delete non-default chains:\n\n sudo iptables -t nat -F\n sudo iptables -t mangle -F\n sudo iptables -F\n sudo iptables -X"]]
