XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Virtual Machines are not starting automatically

    Scheduled Pinned Locked Moved Compute
    8 Posts 3 Posters 1.8k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      Ascar
      last edited by

      Hello, everyone.

      I am setting up a fresh 8.2.1 host with all patches applied. Right now just a couple of essential VMs which are set to start automatically on host power up. For whatever reason the VMs are not starting automatically and I have to start them up manually. What can be the reason for such behavior?

      Thanks for any advice in advance,

      One of the VM's param-list

       xe vm-param-list uuid=e607debe-a04f-1744-a305-efe3fb97a952
      uuid ( RO)                                  : e607debe-a04f-1744-a305-efe3fb97a952
                                  name-label ( RW): (SI1-FW1) - MIGRATION FROM XXX- PFSENSE - (20230604T133424Z)_clone
                            name-description ( RW): pFsense 2.5.2 (SI1-FW1) - 92.xxx.248.45
                                user-version ( RW): 1
                               is-a-template ( RW): false
                         is-default-template ( RW): false
                               is-a-snapshot ( RO): false
                                 snapshot-of ( RO): <not in database>
                                   snapshots ( RO):
                               snapshot-time ( RO): 19700101T00:00:00Z
                               snapshot-info ( RO):
                                      parent ( RO): <not in database>
                                    children ( RO):
                           is-control-domain ( RO): false
                                 power-state ( RO): running
                               memory-actual ( RO): 8589930496
                               memory-target ( RO): 8589934592
                             memory-overhead ( RO): 73400320
                           memory-static-max ( RW): 8589934592
                          memory-dynamic-max ( RW): 8589934592
                          memory-dynamic-min ( RW): 4294967296
                           memory-static-min ( RW): 134217728
                            suspend-VDI-uuid ( RW): <not in database>
                             suspend-SR-uuid ( RW): <not in database>
                                VCPUs-params (MRW): weight: 256
                                   VCPUs-max ( RW): 4
                            VCPUs-at-startup ( RW): 4
                      actions-after-shutdown ( RW): Destroy
                        actions-after-reboot ( RW): Restart
                         actions-after-crash ( RW): Restart
                               console-uuids (SRO): 1452896d-ac5a-5093-4e3e-1b6f93bf0a4b
                                         hvm ( RO): true
                                    platform (MRW): timeoffset: 1; nic_type: e1000; device-model: qemu-upstream-compat; hpet: true; nx: true; secureboot: false; pae: true; apic: true; viridian: true; acpi: 1; cores-per-socket: 4
                          allowed-operations (SRO): changing_dynamic_range; changing_VCPUs_live; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; snapshot
                          current-operations (SRO):
                          blocked-operations (MRW): destroy: true
                         allowed-VBD-devices (SRO): 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; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 80; 81; 82; 83; 84; 85; 86; 87; 88; 89; 90; 91; 92; 93; 94; 95; 96; 97; 98; 99; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 110; 111; 112; 113; 114; 115; 116; 117; 118; 119; 120; 121; 122; 123; 124; 125; 126; 127; 128; 129; 130; 131; 132; 133; 134; 135; 136; 137; 138; 139; 140; 141; 142; 143; 144; 145; 146; 147; 148; 149; 150; 151; 152; 153; 154; 155; 156; 157; 158; 159; 160; 161; 162; 163; 164; 165; 166; 167; 168; 169; 170; 171; 172; 173; 174; 175; 176; 177; 178; 179; 180; 181; 182; 183; 184; 185; 186; 187; 188; 189; 190; 191; 192; 193; 194; 195; 196; 197; 198; 199; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 240; 241; 242; 243; 244; 245; 246; 247; 248; 249; 250; 251; 252; 253; 254
                         allowed-VIF-devices (SRO): 2; 3; 4; 5; 6
                              possible-hosts ( RO): 9101b375-2c2f-45df-99b3-fd164974e84f
                                 domain-type ( RW): hvm
                         current-domain-type ( RO): hvm
                             HVM-boot-policy ( RW): BIOS order
                             HVM-boot-params (MRW): firmware: bios; order: cd
                       HVM-shadow-multiplier ( RW): 1.000
                                   PV-kernel ( RW):
                                  PV-ramdisk ( RW):
                                     PV-args ( RW):
                              PV-legacy-args ( RW):
                               PV-bootloader ( RW):
                          PV-bootloader-args ( RW):
                         last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 1fcbfbff-f7fa3223-2c100800-00000121-00000001-001c0fab-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000
                            last-boot-record ( RO): ''
                                 resident-on ( RO): 9101b375-2c2f-45df-99b3-fd164974e84f
                                    affinity ( RW): <not in database>
                                other-config (MRW): pci: 0/0000:03:00.0; xo:backup:job: 2934e755-a3a0-4754-8571-054c6842cc29; xo:backup:sr: a111b6fb-be51-d8d4-eade-ad683d842a98; xo:backup:datetime: 20230604T13:34:24Z; xo:backup:schedule: b6909bf3-a7a1-45f1-8d5f-cb40985ed89d; xo:backup:vm: 8ce4da44-0fcb-bef0-76e4-f6dca2df547d; auto_poweron: true; folder: /Firewalls; base_template_name: Other install media; import_task: OpaqueRef:d41d6d8e-48f4-433b-8da5-22398b6e3843; mac_seed: 8f0081e9-8c37-f219-8a8c-8e848ac0ad17; install-methods: cdrom; xo:copy_of: a414893b-e38d-24e7-bdfb-9571f812ec8a
                                      dom-id ( RO): 2
                             recommendations ( RO): <restrictions><restriction field="memory-static-max" max="137438953472"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="false"/><restriction field="supports-bios" value="yes"/><restriction field="supports-uefi" value="yes"/><restriction field="supports-secure-boot" value="yes"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions>
                               xenstore-data (MRW): vm-data/mmio-hole-size: 536870912; vm-data:
                  ha-always-run ( RW) [DEPRECATED]: false
                         ha-restart-priority ( RW):
                                       blobs ( RO):
                                  start-time ( RO): 20230605T11:35:34Z
                                install-time ( RO): 20230604T13:51:38Z
                                VCPUs-number ( RO): 4
                           VCPUs-utilisation (MRO): 0: 0.007; 1: 0.006; 2: 0.006; 3: 0.005
                                  os-version (MRO): name: FreeBSD 12.3-STABLE; uname: 12.3-STABLE; distro: FreeBSD
                          PV-drivers-version (MRO): major: 6; minor: 2; micro: 0; build: 76888
          PV-drivers-up-to-date ( RO) [DEPRECATED]: true
                                      memory (MRO):
                                       disks (MRO):
                                        VBDs (SRO): 1fd4bd46-4eec-476f-9ab5-afe2939074be
                                    networks (MRO): 1/ip: 192.168.0.253; 1/ipv4/0: 192.168.0.253
                         PV-drivers-detected ( RO): true
                                       other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-balloon: 1
                                        live ( RO): true
                  guest-metrics-last-updated ( RO): 20230605T11:37:18Z
                         can-use-hotplug-vbd ( RO): unspecified
                         can-use-hotplug-vif ( RO): unspecified
                    cooperative ( RO) [DEPRECATED]: true
                                        tags (SRW): Continuous Replication
                                   appliance ( RW): <not in database>
                           snapshot-schedule ( RW): <not in database>
                            is-vmss-snapshot ( RO): false
                                 start-delay ( RW): 0
                              shutdown-delay ( RW): 0
                                       order ( RW): 0
                                     version ( RO): 0
                               generation-id ( RO):
                   hardware-platform-version ( RO): 0
                           has-vendor-device ( RW): false
                             requires-reboot ( RO): false
                             reference-label ( RO):
                                bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; baseboard-manufacturer: ; baseboard-product-name: ; baseboard-version: ; baseboard-serial-number: ; baseboard-asset-tag: ; baseboard-location-in-chassis: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d
      
      1 Reply Last reply Reply Quote 0
      • KuningaskuntaK Offline
        Kuningaskunta
        last edited by

        I noticed the same, xen orchestra isn't starting with the xcp-ng after a restart.. annoying.

        A 1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Untoggle/re-toggle the auto power on for any VM of your choice, try again.

          A 2 Replies Last reply Reply Quote 0
          • A Offline
            Ascar @Kuningaskunta
            last edited by

            @Kuningaskunta This behavior was observed even before I applied patches.

            I am on single-socker Xeon D-1521, 128GB ECC, 9300-8i HBA, 3 x 2TB QVO SSDs.

            Anything in your hardware similar?

            1 Reply Last reply Reply Quote 0
            • A Offline
              Ascar @olivierlambert
              last edited by

              @olivierlambert I am always following your instructions like a good student listens to his master in school. Let me try and reboot 👍

              1 Reply Last reply Reply Quote 0
              • A Offline
                Ascar @olivierlambert
                last edited by

                @olivierlambert It is so easy for you to make someone a happier person! Thanks, the trick you suggested worked for me

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by olivierlambert

                  So I think the problem is:

                  • when you toggle auto power on a VM, it also enable it at the pool level (required to make it work)
                  • however, if you migrated VMs to this pool with the auto power on enable, it was not enabled on the pool first

                  That's why, disable/enable fixed it. It should probably be a setting in Pool/advanced, but it's some UI work to make it logical 🙂

                  A 1 Reply Last reply Reply Quote 0
                  • A Offline
                    Ascar @olivierlambert
                    last edited by

                    @olivierlambert This is correct, your logic is spot on. The pFsense VM was soft-migrated with continuous replication. However the XO VM was made afresh from scratch and it was not starting. Anyway, things work as expected now, thanks!

                    1 Reply Last reply Reply Quote 0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    • First post
                      Last post