Instance stuck booting from Hard Disk

asked 2017-06-26 21:20:11 -0600

zosocanuck gravatar image

Hi, I'm using the standard cirros image that comes with Ocata, however when I attempt to launch the instance and go to the console I see it stuck at Booting from Hard Disk... GRUB.

Any ideas?

My system is Windows 10 with VMware workstation 12.1.1 with OpenStack running as a guest (Ubuntu 16.04 LTS).

Here is the instance log:

2017-06-27 02:11:08.177+0000: starting up libvirt version: 2.5.0, package: 3ubuntu5~cloud0 (Openstack Ubuntu Testing Bot <openstack-testing-bot@ubuntu.com> Tue, 21 Mar 2017 21:54:49 +0000), qemu version: 2.8.0(Debian 1:2.8+dfsg-3ubuntu2~cloud0), hostname: ubuntu
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name guest=instance-00000002,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-instance-00000002/master-key.aes -machine pc-i440fx-zesty,accel=kvm,usb=off,dump-guest-core=off -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 7c685933-b5db-4bdf-9a90-293a209e92fd -smbios 'type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=16.0.0,serial=1254bba0-f915-8a03-9a07-9756594e98dd,uuid=7c685933-b5db-4bdf-9a90-293a209e92fd,family=Virtual Machine' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-instance-00000002/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/disk/by-path/ip-192.168.71.185:3260-iscsi-iqn.2010-10.org.openstack:volume-28624f84-87c8-48a5-9fbe-7840e030c02c-lun-1,format=raw,if=none,id=drive-virtio-disk0,serial=28624f84-87c8-48a5-9fbe-7840e030c02c,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:9f:1f:65,bus=pci.0,addr=0x3 -add-fd set=2,fd=31 -chardev pty,id=charserial0,logfile=/dev/fdset/2,logappend=on -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
char device redirected to /dev/pts/1 (label charserial0)
warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
edit retag flag offensive close merge delete

Comments

Might be a mismatch of CPU features (CPU provided by Vmware versus CPU expected by qemu). You can tune that with cpu_mode and cpu_model in nova.conf. Try cpu_mode=none.

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-26 21:38:34 -0600 )edit
2

this is what i have:

[libvirt]
live_migration_uri = qemu+ssh://stack@%s/system
cpu_mode = none
virt_type = qemu

I also tested deploying the same image with virt-manager and it successfully started up.

There is a workaround by changing machine type of instance to pc-i440fx-2.3

zosocanuck gravatar imagezosocanuck ( 2017-06-26 22:55:51 -0600 )edit

Thank you very much .This solved my problem.

[libvirt]
cpu_mode = none
virt_type = qemu
George Gao gravatar imageGeorge Gao ( 2018-04-14 20:03:56 -0600 )edit