kali failing to start as a HVM (bootable iso)

[cubit]

I'm trying to run the kali iso as a HVM but when running qvm-start in dom0  it just fails with the errors below.  The template being used is a standalone HVM. Can anyone have pointers on how to work this?

$ qvm-start kali --cdrom work:/home/user/kali-linux-xfce-2016.2-amd64.iso
--> Loading the VM (type = HVM)...
Traceback (most recent call last):
  File "/usr/bin/qvm-start", line 136, in <module>
    main()
  File "/usr/bin/qvm-start", line 120, in main
    xid = vm.start(verbose=options.verbose, preparing_dvm=options.preparing_dvm, start_guid=not options.noguid, notify_function=tray_notify_generic if options.tray else None)
  File "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesHVm.py", line 335, in start
    return super(QubesHVm, self).start(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1966, in start
    self.libvirt_domain.createWithFlags(libvirt.VIR_DOMAIN_START_PAUSED)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1059, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirt.libvirtError: internal error: libxenlight failed to create new domain 'kali'

[spfmc...@gmail.com]

What steps did you do before this step? Did you create the HVM using qvm-create?

Have you referenced the Docs page for setting up Kali?
https://www.qubes-os.org/doc/pentesting/kali/

[cubit]

17. Jan 2017 00:31 by spfmc...@gmail.com:

What steps did you do before this step? Did you create the HVM using qvm-create?

Have you referenced the Docs page for setting up Kali?
https://www.qubes-os.org/doc/pentesting/kali

I followed https://www.qubes-os.org/doc/pentesting/kali/#hvm

With step 2 being done through Qubes VM manager (VM > Create VM)

Name: kali

color: red

HVM: standalone

Allow networking: sys-firewal

Then on to step 3 which gives the error as last email

 

[andr...@gmail.com]

cubit 13/01/2017 20:31:05 UTC-2:

Any updates about this issue? I'm getting the same error trying to install Debian 8 or Ubuntu 16.04 as HVM.

[Unman]

I see this error if there's a typo in the filename or permissions are
wrong.
Otherwise it works as expected - what versions of the Qubes packages are
you using? What are specs of your box? Plenty of RAM?

[Andres MRM]

[2017-07-05 19:30] Unman:

> I see this error if there's a typo in the filename or permissions are
> wrong.
> Otherwise it works as expected - what versions of the Qubes packages are
> you using? What are specs of your box? Plenty of RAM?

Thanks for the reply!

I noticed it gives the same error for filename typos, so I checked the path
multiple times and even copied the file to /a.iso to make sure.
The permissions of the images are "-rw-r--r--" owned by user.

My RAM is 8GB, and the error seems to change when there isn't enough RAM (when
many VMs are running), so I think this is not the case.

Not sure about Qubes packages version, but I just did a qubes-dom0-update to
test, and still same error.

[Unman]

You can see packkage information from QubesManager - About - Qubes OS -
Version Information.

Are you using standard repositories, or have yu enabled testing?

[Andres MRM]

[2017-07-06 11:33] Unman:

> You can see packkage information from QubesManager - About - Qubes OS -
> Version Information.

xen_version : 4.6.5
Linux 4.4.38-11.pvops.qubes.x86_64

Installed Packages:

i3-settings-qubes.x86_64 1.2-1.fc23
kernel-qubes-vm.x86_64 1000:4.4.62-12.pvops.qubes
kernel-qubes-vm.x86_64 1000:4.4.67-12.pvops.qubes
kernel-qubes-vm.x86_64 1000:4.4.67-13.pvops.qubes
qubes-anaconda-addon.noarch 3.2.3-1.fc23
qubes-artwork.noarch 3.2.0-2.fc23
qubes-core-dom0.x86_64 3.2.14-1.fc23
qubes-core-dom0-doc.noarch 3.2.14-1
qubes-core-dom0-linux.x86_64 3.2.13-1.fc23
qubes-core-dom0-linux-kernel-install.x86_64
qubes-db.x86_64 3.2.3-1.fc23
qubes-db-dom0.x86_64 3.2.3-1.fc23
qubes-db-libs.x86_64 3.2.3-1.fc23
qubes-gpg-split-dom0.x86_64 2.0.24-1.fc23
qubes-gui-dom0.x86_64 3.2.11-1.fc23
qubes-img-converter-dom0.x86_64 1.2.3-1.fc23
qubes-input-proxy.x86_64 1.0.8-1.fc23
qubes-libvchan-xen.x86_64 3.2.1-1.fc23
qubes-manager.x86_64 3.2.11-1.fc23
qubes-menus.noarch 2.0-1
qubes-mgmt-salt.noarch 3.2.5-1.fc23
qubes-mgmt-salt-admin-tools.noarch 3.2.5-1.fc23
qubes-mgmt-salt-base.noarch 3.2.2-1.fc23
qubes-mgmt-salt-base-config.noarch 3.2.2-1.fc23
qubes-mgmt-salt-base-overrides.noarch
qubes-mgmt-salt-base-overrides-libs.noarch
qubes-mgmt-salt-base-topd.noarch 3.2.1-1.fc23
qubes-mgmt-salt-config.noarch 3.2.5-1.fc23
qubes-mgmt-salt-dom0.noarch 3.2.5-1.fc23
qubes-mgmt-salt-dom0-qvm.noarch 3.2.1-1.fc23
qubes-mgmt-salt-dom0-update.noarch 3.2.0-1.fc23
qubes-mgmt-salt-dom0-virtual-machines.noarch
qubes-pdf-converter-dom0.x86_64 2.1.2-1.fc23
qubes-release.noarch 3.2-0.26
qubes-release-notes.noarch 3.2-0.26
qubes-template-archlinux.noarch 3.0.6-201611130159
qubes-template-debian-8.noarch 3.0.6-201608090120
qubes-template-fedora-23.noarch 3.0.6-201608081228
qubes-template-whonix-gw.noarch 3.0.6-201608050041
qubes-template-whonix-ws.noarch 3.0.6-201608050146
qubes-usb-proxy-dom0.noarch 1.0.5-1.fc23
qubes-utils.x86_64 3.2.4-1.fc23
qubes-utils-libs.x86_64 3.2.4-1.fc23
xfce4-settings-qubes.x86_64 3.2.2-1.fc23

> Are you using standard repositories, or have yu enabled testing?

Yes and no.

[Andres MRM]

I just copied the debian ISO to dom0 and it booted (installing at this very
moment, let's see if works).
So it can't boot the ISO from inside another VM... No idea why... And yes, I
checked the path many times, even moved and renamed to a short path
(/home/user/a.iso) and set permissions to 777.


[2017-07-06 12:20] Andres MRM:

[Unman]

Can you check the command line?
In the thread it is incorrect and i want to make sure that you havent
been misled.
The correct format would be something like:
qvm-start <kali> --cdrom=<qube>:/home/user/kali.iso

[Unman]

Ignore this please - it works fine without the "="

[Andres MRM]

[2017-07-06 17:18] Unman:

> Can you check the command line?
> In the thread it is incorrect and i want to make sure that you havent
> been misled.
> The correct format would be something like:
> qvm-start <kali> --cdrom=<qube>:/home/user/kali.iso

Sure. This didn't work:

$ qvm-start hvm --cdrom=media:/home/user/a.iso

Then I copied the ISO to dom0 and this worked:

$ qvm-start hvm --cdrom=/home/user/a.iso