Starting VM with ISO Fails: libxenlight failed to create new domain:

[tharrisone]

Qubes OS version: 4.0RC2
---
Steps to reproduce the behavior:
qvm-create meh --class StandaloneVM --label blue
qvm-prefs meh kernel ""
qvm-start meh --cdrom=dom0:/home/klepto/Downloads/ant.iso

Actual behavior:
Start failed: internal error: libxenlight failed to create new domain 'meh'

General notes:
I've tried various isos and they all fail.
I am using the testing repository with 4.0RC2

When I do this through the vm settings gui after I pick the iso and press ok nothing happens and the gui stays open and pressing ok over and over does nothing.

[andrewdavidwong]

Possibly related: #2784, #2753.

[andrewdavidwong]

Possibly related: #2784, #2753.

[golia78]

Good morning,
i have the same issue but with a situation a little bit different.

Qubes OS version:

4.0RC3(updated Yesterday from RC2).

Steps to reproduce the behavior:

• Update Qubes OS from 4.0RC2 to 4.0RC3 whit these commands:
  • sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
  • sudo qubes-dom0-update
• Standalone kali-full VM previously created from an iso under 4.0RC2 without problems
• qvm-start kali-full

Actual behavior:

• Start failed: internal error: libxenlight failed to create new domain "kali-full"

P.S.:
I have worked on my kali-full standalone VM without problems for about one month under RC2 testing release. The update introduced the problem.

[golia78]

Good morning,
i have the same issue but with a situation a little bit different.

Qubes OS version:

4.0RC3(updated Yesterday from RC2).

Steps to reproduce the behavior:

• Update Qubes OS from 4.0RC2 to 4.0RC3 whit these commands:
  • sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
  • sudo qubes-dom0-update
• Standalone kali-full VM previously created from an iso under 4.0RC2 without problems
• qvm-start kali-full

Actual behavior:

• Start failed: internal error: libxenlight failed to create new domain "kali-full"

P.S.:
I have worked on my kali-full standalone VM without problems for about one month under RC2 testing release. The update introduced the problem.

[arjan-s]

Exactly the same issue here as @golia78 , with a Linux and a Windows VM created under 4.0 RC2.

[arjan-s]

Exactly the same issue here as @golia78 , with a Linux and a Windows VM created under 4.0 RC2.

[q-ubes]

Me too. Trying to follow the instructions in the 'tails in qubes' page: https://www.qubes-os.org/doc/tails/

Fresh install of 4.0-rc3.

[q-ubes]

Me too. Trying to follow the instructions in the 'tails in qubes' page: https://www.qubes-os.org/doc/tails/

Fresh install of 4.0-rc3.

[lokedhs]

Same problem here. Originally installed as rc2, updated to the latest version from the testing repository.

[lokedhs]

Same problem here. Originally installed as rc2, updated to the latest version from the testing repository.

[jupiter126]

Same issue with fresh 4.0RC3 trying to boot on cd for debian stretch netinstall

it does the same on a vhm vm created from qubes-template-debian-9. For some reason it started once, havn't been able to reproduce.

Note; To get qubes running on my machine, I had to nomsi like in:
qvm-prefs sys-net kernelopts "nopat iommu=soft swiotlb=8192 pci=nomsi"
not sure if it can might related

[jupiter126]

Same issue with fresh 4.0RC3 trying to boot on cd for debian stretch netinstall

it does the same on a vhm vm created from qubes-template-debian-9. For some reason it started once, havn't been able to reproduce.

Note; To get qubes running on my machine, I had to nomsi like in:
qvm-prefs sys-net kernelopts "nopat iommu=soft swiotlb=8192 pci=nomsi"
not sure if it can might related

[golia78]

Hi guys,
i did another test, the error "... libxenlight failed to create new domain ..." is generated after setting the kernel prefs to '' whith the command:
qvm-prefs kernel ''

You can reproduce the issue also from the VM Settings GUI choosing "none" from the kernel listbox in the advanced tab panel.
If you choose another kernel option from the listbox, you can see the VM that try to start without the "... libxenlight failed to create new domain ..." error.
I hope this helps.

[golia78]

Hi guys,
i did another test, the error "... libxenlight failed to create new domain ..." is generated after setting the kernel prefs to '' whith the command:
qvm-prefs kernel ''

You can reproduce the issue also from the VM Settings GUI choosing "none" from the kernel listbox in the advanced tab panel.
If you choose another kernel option from the listbox, you can see the VM that try to start without the "... libxenlight failed to create new domain ..." error.
I hope this helps.

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.15-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.15-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.15-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.15-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update