Missing steps while booting qube from cdrom

[marmarek]

Qubes OS version (e.g., R3.2): R4.0

New GUI for creating standalone qube and booting it from cdrom should set kernel to None (or empty string). Otherwise dom0-provided kernel will be used, instead of booting from provided cdrom.
Also virt_mode needs to be hvm.

Additionally, when one want to install Windows, some more steps are needed:

1. Set maxmem = memory = 1024 (or more)
2. Increase size of root volume - Windows 7 installer suggests at least 12GB, by default there is 10GB.

This probably should be covered in documentation: https://www.qubes-os.org/doc/windows-appvms/ (which currently link to https://www.qubes-os.org/doc/hvm/ for actual qube setup).

[0spinboson]

Kernel can only be set to none using qvm-prefs --set name kernel ''; when I try this via the GUI, I get an error, namely "kernel '(none)' not installed".

Additionally, when I try to install w7 via 'qvm-start w7 --cdrom=dom0:/run/media/etc/etc/etc.iso', qubesd appears to crash ("got empty response from qubesd, see journalctl").

relevant bits: w7iso.txt

[0spinboson]

Kernel can only be set to none using qvm-prefs --set name kernel ''; when I try this via the GUI, I get an error, namely "kernel '(none)' not installed".

Additionally, when I try to install w7 via 'qvm-start w7 --cdrom=dom0:/run/media/etc/etc/etc.iso', qubesd appears to crash ("got empty response from qubesd, see journalctl").

relevant bits: w7iso.txt

[marmarek]

Relevant messages:

Sep 27 23:11:20 dom0 qubesdb-daemon[2895]: invalid message received from client 5
Sep 27 23:11:20 dom0 qubesd[13511]: python3: qdb-client.c:443: qdb_list: Assertion `hdr.type == QDB_RESP_LIST' failed.

Is it reproducible?

[marmarek]

Relevant messages:

Sep 27 23:11:20 dom0 qubesdb-daemon[2895]: invalid message received from client 5
Sep 27 23:11:20 dom0 qubesd[13511]: python3: qdb-client.c:443: qdb_list: Assertion `hdr.type == QDB_RESP_LIST' failed.

Is it reproducible?

[0spinboson]

Yes, this is the only thing it does -- it never works.

[0spinboson]

Yes, this is the only thing it does -- it never works.

[0spinboson]

additional info, no idea if it's useful: when I launch qubes-vm-boot-from-device from a shell and try it, it outputs this:

Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/qubesmanager/bootfromdevice.py", line 52, in save_and_apply
cdrom_location = self.vm_list[self.fileVM.currentIndex()] + ":" + self.pathText.text()
TypeError: unsupported operand type(s) for +: 'StandaloneVM' and 'str'

[0spinboson]

additional info, no idea if it's useful: when I launch qubes-vm-boot-from-device from a shell and try it, it outputs this:

Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/qubesmanager/bootfromdevice.py", line 52, in save_and_apply
cdrom_location = self.vm_list[self.fileVM.currentIndex()] + ":" + self.pathText.text()
TypeError: unsupported operand type(s) for +: 'StandaloneVM' and 'str'

[marmarek]

I've reproduced both errors, working on the fix.

[marmarek]

I've reproduced both errors, working on the fix.

[0spinboson]

I'm not getting the qubesd crash any more, but when I now try to mount an ISO file, I get the following warning:

traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/qubesmanager/bootfromdevice.py", line 52, in save_and_apply
cdrom_location = self.vm_list[self.fileVM.currentIndex()] + ":" + self.pathText.text()
TypeError: unsupported operand type(s) for +: 'AppVM' and 'str'

VM type was set to 'StandaloneVM without template', so something may be wrong with the detection.
Possibly related: Oct 08 14:35:14 dom0 qubesd[2962]: QubesNoSuchPropertyError("Invalid property 'template' of w7",) while calling src=b'dom0' meth=b'admin.vm.property.Get' dest=b'w7' arg=b'template' len(untrusted_payload)=0

[0spinboson]

I'm not getting the qubesd crash any more, but when I now try to mount an ISO file, I get the following warning:

traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/qubesmanager/bootfromdevice.py", line 52, in save_and_apply
cdrom_location = self.vm_list[self.fileVM.currentIndex()] + ":" + self.pathText.text()
TypeError: unsupported operand type(s) for +: 'AppVM' and 'str'

VM type was set to 'StandaloneVM without template', so something may be wrong with the detection.
Possibly related: Oct 08 14:35:14 dom0 qubesd[2962]: QubesNoSuchPropertyError("Invalid property 'template' of w7",) while calling src=b'dom0' meth=b'admin.vm.property.Get' dest=b'w7' arg=b'template' len(untrusted_payload)=0

[marmarek]

This one is already fixed in QubesOS/qubes-manager#42. Updated package will be in repo today.

[marmarek]

This one is already fixed in QubesOS/qubes-manager#42. Updated package will be in repo today.

[0spinboson]

did qubes-manager v4.0.6 get stuck in a pipe somewhere? :)

[0spinboson]

did qubes-manager v4.0.6 get stuck in a pipe somewhere? :)

[marmarek]

did qubes-manager v4.0.6 get stuck in a pipe somewhere? :)

Apparently, calling a plumber ;)

[marmarek]

did qubes-manager v4.0.6 get stuck in a pipe somewhere? :)

Apparently, calling a plumber ;)

[qubesos-bot]

Automated announcement from builder-github

The package qubes-manager-4.0.6-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-manager-4.0.6-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

[0spinboson]

Thanks. :)

fyi: qubes-vm-boot-from-device doesn't load a GUI selection window any more, is broken.

[0spinboson]

Thanks. :)

fyi: qubes-vm-boot-from-device doesn't load a GUI selection window any more, is broken.

[0spinboson]

also, when I try to attach a win7 installation image, libxenlight is unable to create a new domain. libxlDomainstart:1320: internal error: libxenlight failed to create new domain.

[0spinboson]

also, when I try to attach a win7 installation image, libxenlight is unable to create a new domain. libxlDomainstart:1320: internal error: libxenlight failed to create new domain.

[marmarek]

Check /var/log/libvirt/libxl/libxl-driver.log

[marmarek]

Check /var/log/libvirt/libxl/libxl-driver.log

[0spinboson]

2017-10-10 09:02:34.125+0000: libxl: libxl_dm.c:2103:stubdom_xswait_cb: Stubdom 38 for 37 startup: startup timed out
2017-10-10 09:02:34.125+0000: libxl: libxl_create.c:1541:domcreate_devmodel_started: device model did not start: -9
2017-10-10 09:02:34.235+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/8/backend/vbd/38/51840
2017-10-10 09:02:34.238+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/4/backend/vif/38/0
2017-10-10 09:02:34.276+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop52: No such device or address
2017-10-10 09:02:34.281+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/8/backend/vbd/37/51840
2017-10-10 09:02:34.620+0000: libxl: libxl.c:1673:devices_destroy_cb: libxl__devices_destroy failed for 37
2017-10-10 09:02:34.663+0000: libxl: libxl.c:1673:devices_destroy_cb: libxl__devices_destroy failed for 38

[0spinboson]

2017-10-10 09:02:34.125+0000: libxl: libxl_dm.c:2103:stubdom_xswait_cb: Stubdom 38 for 37 startup: startup timed out
2017-10-10 09:02:34.125+0000: libxl: libxl_create.c:1541:domcreate_devmodel_started: device model did not start: -9
2017-10-10 09:02:34.235+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/8/backend/vbd/38/51840
2017-10-10 09:02:34.238+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/4/backend/vif/38/0
2017-10-10 09:02:34.276+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop52: No such device or address
2017-10-10 09:02:34.281+0000: libxl: libxl_device.c:1074:device_backend_callback: unable to remove device with path /local/domain/8/backend/vbd/37/51840
2017-10-10 09:02:34.620+0000: libxl: libxl.c:1673:devices_destroy_cb: libxl__devices_destroy failed for 37
2017-10-10 09:02:34.663+0000: libxl: libxl.c:1673:devices_destroy_cb: libxl__devices_destroy failed for 38

[0spinboson]

oh, it seems this only affects loading the ISO via a VM. dom0 as a backend works. (qvm-start VMNAME --cdrom=dom0:/bla/)

Windows installation does now start and finish properly.

[0spinboson]

oh, it seems this only affects loading the ISO via a VM. dom0 as a backend works. (qvm-start VMNAME --cdrom=dom0:/bla/)

Windows installation does now start and finish properly.

[marmarek]

also, when I try to attach a win7 installation image, libxenlight is unable to create a new domain. libxlDomainstart:1320: internal error: libxenlight failed to create new domain.

This is #3172

[marmarek]

also, when I try to attach a win7 installation image, libxenlight is unable to create a new domain. libxlDomainstart:1320: internal error: libxenlight failed to create new domain.

This is #3172

[marmarek]

fyi: qubes-vm-boot-from-device doesn't load a GUI selection window any more, is broken.

Branched to #3182

[marmarek]

fyi: qubes-vm-boot-from-device doesn't load a GUI selection window any more, is broken.

Branched to #3182

[kalkin]

Sorry for closing this issue. It looks like my private repo where I merge changes closes an issue in another organization. Weird :-/

[kalkin]

Sorry for closing this issue. It looks like my private repo where I merge changes closes an issue in another organization. Weird :-/

[qubesos-bot]

Automated announcement from builder-github

The package qubes-manager-4.0.8-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-manager-4.0.8-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

[donob4n]

Hi,

It seems that this issue stills in Qubes 4.0 rc4, at least in the part of:

@marmarek

New GUI for creating standalone qube and booting it from cdrom should set kernel to None (or empty string). Otherwise dom0-provided kernel will be used, instead of booting from provided cdrom.

What should be the right solution? Creating this VM's with kernel 'None' or skip the kernel value when starting with --cdrom option? I think that I could help there if needed.

[donob4n]

Hi,

It seems that this issue stills in Qubes 4.0 rc4, at least in the part of:

@marmarek

New GUI for creating standalone qube and booting it from cdrom should set kernel to None (or empty string). Otherwise dom0-provided kernel will be used, instead of booting from provided cdrom.

What should be the right solution? Creating this VM's with kernel 'None' or skip the kernel value when starting with --cdrom option? I think that I could help there if needed.

[marmarek]

This should be already fixed by QubesOS/qubes-manager#64, included in qubes-manager 4.0.14 package. What version do you have?

[marmarek]

This should be already fixed by QubesOS/qubes-manager#64, included in qubes-manager 4.0.14 package. What version do you have?

[donob4n]

Sorry @marmarek , I was running 4.0.13. After updating with testing repository and get 4.0.15 it works fine. Also I discovered Alpinelinux HVM works (without soft lockup due bochs_drm). I will investigate it in Qubes 3.2 (maybe dom0 kernel or xen version?).

[donob4n]

Sorry @marmarek , I was running 4.0.13. After updating with testing repository and get 4.0.15 it works fine. Also I discovered Alpinelinux HVM works (without soft lockup due bochs_drm). I will investigate it in Qubes 3.2 (maybe dom0 kernel or xen version?).

[marmarta]

I think this one is already fixed, judging from the discussion above. Closing, but if I'm wrong don't hesitate to reopen it.

[marmarta]

I think this one is already fixed, judging from the discussion above. Closing, but if I'm wrong don't hesitate to reopen it.