Unable to install cirros on vmware esxi

Bug #1755152 reported by Sheshagiri Rao M
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CirrOS
New
Undecided
Unassigned

Bug Description

Unable to start CirrOS vm on an ubuntu vm install on VMWare ESXi(ESXi-6.5.0-20170104001-standard)

##Ubuntu Version##
root@ubuntu:/home/rvbd# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
##CPU Info##
root@ubuntu:/home/rvbd# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 3
On-line CPU(s) list: 0-2
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 3
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
Stepping: 2
CPU MHz: 2599.998
BogoMIPS: 5199.99
Virtualization: VT-x
Hypervisor vendor: VMware
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 20480K
NUMA node0 CPU(s): 0-2
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm epb tpr_shadow vnmi ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 invpcid xsaveopt dtherm ida arat pln pts
##KVM/libvirt Info##
root@ubuntu:/home/rvbd# libvirtd -V
libvirtd (libvirt) 1.3.1
root@ubuntu:/home/rvbd# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

CirrOS Image: cirros-0.4.0-x86_64-disk.img

##Install using virt-install##
root@ubuntu:/home/rvbd# virt-install --import --name=cirros --disk /home/cirros-0.4.0-x86_64-disk.img,format=qcow2,bus=ide,cache=writethrough --os-type=linux --network bridge=ens192_br,model=e1000 --ram=1024 --arch=x86_64 --vcpus=1 --graphics none --noautoconsole

Starting install...
Creating domain... | 0 B 00:00:01
Domain creation completed.
root@ubuntu:/home/rvbd#
##Error(/var/log/libvirt/qemu/cirros.log)##
018-03-12 12:11:52.276+0000: starting up libvirt version: 1.3.1, package: 1ubuntu10.19 (Marc Deslauriers <email address hidden> Fri, 16 Feb 2018 07:51:15 -0500), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.22), 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 cirros -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu Haswell-noTSX -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 40a38fc6-29a9-46cd-bad1-6b6c0e84ce1a -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-cirros/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 -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 -drive file=/home/cirros-0.4.0-x86_64-disk.img,format=raw,if=none,id=drive-ide0-0-0,cache=writethrough -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:99:5c:25,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -msg timestamp=on
char device redirected to /dev/pts/1 (label charserial0)
warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]

description: updated
summary: - Unable to install cirros on vmware
+ Unable to install cirros on vmware esxi
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.