On Mon, Jan 4, 2016 at 1:18 PM, Roy Golan <[email protected]> wrote: > > > On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi <[email protected]> wrote: > >> Hi ! >> After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start >> hosted-engine vm using "hosted-engine --vm-start" >> >> I have only one host. >> I put engine in global maintenance mode, I shutdown all VM and hosted >> engine VM. >> I reboot the host and run "hosted-engine --vm-start", but the VM never >> start (I waited for 10 minutes). >> When I run " hosted-engine --set-maintenance --mode=none" engine VM start >> immediately. >> >> [root@ovirt01 ~]# hosted-engine --vm-start >> >> b66ae2c5-de0f-4361-953b-f10226da7eb8 >> Status = WaitForLaunch >> nicModel = rtl8139,pv >> statusTime = 4294711929 >> emulatedMachine = pc >> pid = 0 >> vmName = HostedEngine >> devices = [{'index': '2', 'iface': 'ide', 'specParams': {}, >> 'readonly': 'true', 'deviceId': '9866b541-20db-40c8-9512-b4f5277700fd', >> 'address': {'bus': '1', 'controller': '0', 'type': 'drive', 'target': '0', >> 'unit': '0'}, 'device': 'cdrom', 'shared': 'false', 'path': >> '/home/pacchetti/iso/CentOS-7.0-1406-x86_64-Minimal.iso', 'type': 'disk'}, >> {'index': '0', 'iface': 'virtio', 'format': 'raw', 'bootOrder': '1', >> 'poolID': '00000000-0000-0000-0000-000000000000', 'volumeID': >> 'f89cf2a9-af3c-4c07-9e45-5f2c5fd8e155', 'imageID': >> 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06', 'specParams': {}, 'readonly': >> 'false', 'domainID': '46f55a31-f35f-465c-b3e2-df45c05e06a7', 'optional': >> 'false', 'deviceId': 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06', 'address': >> {'slot': '0x06', 'bus': '0x00', 'domain': '0x0000', 'type': 'pci', >> 'function': '0x0'}, 'device': 'disk', 'shared': 'exclusive', >> 'propagateErrors': 'off', 'type': 'disk'}, {'device': 'scsi', 'model': >> 'virtio-scsi', 'type': 'controller'}, {'nicModel': 'pv', 'macAddr': >> '00:16:3e:12:d5:35', 'linkActive': 'true', 'network': 'ovirtmgmt', >> 'filter': 'vdsm-no-mac-spoofing', 'specParams': {}, 'deviceId': >> '3f76ab15-bf91-41ad-b02d-dbdb21fae828', 'address': {'slot': '0x03', 'bus': >> '0x00', 'domain': '0x0000', 'type': 'pci', 'function': '0x0'}, 'device': >> 'bridge', 'type': 'interface'}, {'device': 'console', 'specParams': {}, >> 'type': 'console', 'deviceId': 'a40e268c-bef7-4ca4-832a-28e550e9e012', >> 'alias': 'console0'}] >> guestDiskMapping = {} >> vmType = kvm >> clientIp = >> displaySecurePort = -1 >> memSize = 4096 >> displayPort = -1 >> cpuType = SandyBridge >> spiceSecureChannels = >> smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir >> smp = 2 >> displayIp = 0 >> display = vnc >> [root@ovirt01 ~]# hosted-engine --vm-status >> >> >> !! Cluster is in GLOBAL MAINTENANCE mode !! >> >> > yes, pull you cluster out of global maintenance: > > $ hosted-engine --set-maintenance --mode=none > > $ hosted-engine --vm-start > >
Sorry I was quick to answer and now I saw you already tried and it immediately started the vm. > >> >> --== Host 1 status ==-- >> >> Status up-to-date : False >> Hostname : ovirt01.hawai.lan >> Host ID : 1 >> Engine status : unknown stale-data >> Score : 3400 >> stopped : False >> Local maintenance : False >> crc32 : d2fb89cb >> Host timestamp : 3569 >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >> > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
