# Unable to install a new Virtual Machine **URL:** \ **Category:** SLES Virtualization\ **Created:** [June 10, 2016, 8:50pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269 "2016-06-10T20:50:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mikenash](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mikenash](https://forums.suse.com/u/mikenash)\ **Post date:** [June 10, 2016, 8:50pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269/1 "2016-06-10T20:50:51Z")
I am on a SLES12-SP1 Enterprise system. I installed the hypervisor and tools. Selected the Virtual Machine Manager and then the new virtual machine. Performaed steps 1 to 5. Step 1 : local install media Step 2: Sles 12 iso file Step 3: 1024 MB 1 CPU Step 4: Create new virtual machine Enable storage for this machine 6.4 GB Select managed or other existing storage Browse select /dev/dasdc1 Finish Creating - system has crashed. I am not finding any logs. ---
**Author:** ![mikenash](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mikenash](https://forums.suse.com/u/mikenash)\ **Post date:** [June 14, 2016, 6:14pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269/2 "2016-06-14T18:14:22Z")
SLES12-SP1 has been updated and still unable to create a VM system. System fails: Unable to complete Install: VM ‘SLES12-SP1-Trial’ didn’t show up after expected time.’ The libvirtd service appeared to be hung so I restarted and reconnected. Started the system and it immediately crashes and loops. Pause system and forced off. The libvirtd status show it could not find a scsi device. I have no scsi devices on the system. Could this be my problem? [CODE]root@linux140:/root $~\>systemctl status libvirtd libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue 2016-06-14 10:54:56 EDT; 12min ago Docs: man:libvirtd(8) [http://libvirt.org](http://libvirt.org) Main PID: 2372 (libvirtd) CGroup: /system.slice/libvirtd.service ├─1645 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/lib… ├─1646 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/lib… └─2372 /usr/sbin/libvirtd --listen Jun 14 10:54:56 linux140 systemd[1]: libvirtd.service: main process exited, code=killed, status=9/KILL Jun 14 10:54:56 linux140 systemd[1]: Unit libvirtd.service entered failed state. Jun 14 10:54:56 linux140 systemd[1]: Starting Virtualization daemon… Jun 14 10:54:56 linux140 systemd[1]: Started Virtualization daemon. Jun 14 10:54:56 linux140 dnsmasq[1645]: read /etc/hosts - 8 addresses Jun 14 10:54:56 linux140 dnsmasq[1645]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jun 14 10:54:56 linux140 dnsmasq-dhcp[1645]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jun 14 10:54:56 linux140 libvirtd[2372]: libvirt version: 1.2.18.2 Jun 14 10:54:56 linux140 libvirtd[2372]: internal error: no monitor path Jun 14 10:57:27 linux140 libvirtd[2372]: internal error: no disk found with alias scsi0-0-0-0[/CODE] ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [June 14, 2016, 6:23pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269/3 "2016-06-14T18:23:38Z")
On 10/06/16 18:54, mikenash wrote: Since nobody else has jumped in I have a couple of questions: [color=blue] > I am on a SLES12-SP1 Enterprise system. > I installed the hypervisor and tools. Selected the Virtual Machine > Manager and then the new virtual machine. Performaed steps 1 to 5. > Step 1 : local install media > Step 2: Sles 12 iso file[/color] SLES12 or SLES12 SP1? I don’t expect it will make any difference but in case we need to try duplicating. [color=blue] > Step 3: 1024 MB > 1 CPU > Step 4: Create new virtual machine > Enable storage for this machine > 6.4 GB > Select managed or other existing storage > Browse select /dev/dasdc1[/color] Is this an existing OCFS2 file system? I wonder if perhaps 6.4GB isn’t big enough. [color=blue] > Finish > Creating - system has crashed. > I am not finding any logs.[/color] ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks. ---
**Author:** ![mikenash](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mikenash](https://forums.suse.com/u/mikenash)\ **Post date:** [June 14, 2016, 9:14pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269/4 "2016-06-14T21:14:41Z")
Greeting Simon, thank you for your reply. This is a SLES12-SP1 system and I am attempting to make a new virtual image. I reran the process after mounting a 27G LVM volume on /var/lib/libvirt/images and taking the 20G default. The process fails the same way with losing the connection with a timeout where libvirtd appears to hang. I restart libvirtd to regain the connection. The status of libvirtd has an error for a scsi device. I am guessing this is a virtual device. Are there any special device drivers that are required? [CODE]root@linux140:/root $~\>systemctl status libvirtd libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue 2016-06-14 13:54:15 EDT; 8min ago Docs: man:libvirtd(8) [http://libvirt.org](http://libvirt.org) Main PID: 2409 (libvirtd) CGroup: /system.slice/libvirtd.service ├─1644 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/lib… ├─1645 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/lib… └─2409 /usr/sbin/libvirtd --listen Jun 14 13:54:15 linux140 systemd[1]: libvirtd.service: main process exited, code=killed, status=9/KILL Jun 14 13:54:15 linux140 systemd[1]: Unit libvirtd.service entered failed state. Jun 14 13:54:15 linux140 systemd[1]: Starting Virtualization daemon… Jun 14 13:54:15 linux140 systemd[1]: Started Virtualization daemon. Jun 14 13:54:15 linux140 dnsmasq[1644]: read /etc/hosts - 8 addresses Jun 14 13:54:15 linux140 dnsmasq[1644]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jun 14 13:54:15 linux140 dnsmasq-dhcp[1644]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jun 14 13:54:15 linux140 libvirtd[2409]: libvirt version: 1.2.18.2 Jun 14 13:54:15 linux140 libvirtd[2409]: internal error: no monitor path Jun 14 13:55:00 linux140 libvirtd[2409]: internal error: no disk found with alias scsi0-0-0-0[/CODE] ---
**Author:** ![mikenash](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@mikenash](https://forums.suse.com/u/mikenash)\ **Post date:** [June 14, 2016, 10:30pm UTC](https://forums.suse.com/t/unable-to-install-a-new-virtual-machine/28269/5 "2016-06-14T22:30:26Z")
Hello Simon, I the following packages installed on this system. [CODE]root@linux140:/root $~\>rpm -qa | grep qemu qemu-s390-2.3.1-7.7.s390x qemu-tools-2.3.1-7.7.s390x qemu-kvm-2.3.1-7.7.s390x qemu-2.3.1-7.7.s390x libvirt-daemon-qemu-1.2.18.2-8.1.s390x qemu-block-curl-2.3.1-7.7.s390x libvirt-daemon-driver-qemu-1.2.18.2-8.1.s390x Tue Jun 14 2016 03:21 PM root@linux140:/root $~\>rpm -qa | grep libvirt libvirt-daemon-qemu-1.2.18.2-8.1.s390x libvirt-glib-1\_0-0-0.2.1-1.2.s390x libvirt-daemon-driver-storage-1.2.18.2-8.1.s390x libvirt-python-1.2.18-1.2.s390x libvirt-daemon-driver-secret-1.2.18.2-8.1.s390x libvirt-daemon-driver-nwfilter-1.2.18.2-8.1.s390x libvirt-daemon-config-network-1.2.18.2-8.1.s390x libvirt-daemon-driver-nodedev-1.2.18.2-8.1.s390x libvirt-client-1.2.18.2-8.1.s390x libvirt-daemon-driver-lxc-1.2.18.2-8.1.s390x libvirt-daemon-driver-network-1.2.18.2-8.1.s390x libvirt-daemon-driver-interface-1.2.18.2-8.1.s390x libvirt-daemon-driver-qemu-1.2.18.2-8.1.s390x libvirt-cim-0.6.3-5.7.s390x libvirt-daemon-1.2.18.2-8.1.s390x libvirt-daemon-lxc-1.2.18.2-8.1.s390x[/CODE]