воскресенье, 5 августа 2018 г., 6:04:04 UTC-4 пользователь Unman написал: > On Sun, Aug 05, 2018 at 02:55:01AM -0700, Daniil .Travnikov wrote: > > вторник, 17 июля 2018 г., 17:09:08 UTC-4 пользователь Peter написал: > > > I'm using qubes 4 with qubes-windows-tools-4.0.0-1 > > > I have a win7 template which launches fine. > > > > > > > > > I've made a Appvm from the template and when I try to start it has the > > > following error: > > > > > > > > > qvm-start win7vm > > > > > > > > > ERROR: Start failed: internal error: libenlight failed to create new > > > domain 'win7vm', see /var/log/libvert/libxl/libxl-driver.log > > > > > > > > > Can anyone help with this error? > > > > > > > > > Does this have anything to do with the network issue with Windows7, where > > > you have to set a static IP address? > > > > > > > > > I don't see this error when launching any other VM's. > > > > > > > > > libxl-driver.log has this: > > > > > > > > > > > > > > > 2018-07-17 20:16:54.358+0000: xc: panic: xc_dom_core.c:208: failed to > > > open file 'None/vmlinuz': No such file or directory: Internal error > > > 2018-07-17 20:16:54.358+0000: libxl: > > > libxl_dom.c:994:libxl__domain_firmware: xc_dom_kernel_file failed: No > > > such file or directory > > > 2018-07-17 20:16:54.358+0000: libxl: libxl_dom.c:1140:libxl__build_hvm: > > > initializing domain firmware failed > > > 2018-07-17 20:16:54.358+0000: libxl: > > > libxl_create.c:1284:domcreate_rebuild_done: cannot (re-)build domain: -1 > > > 2018-07-17 20:48:42.071+0000: xc: panic: xc_dom_core.c:208: failed to > > > open file 'None/vmlinuz': No such file or directory: Internal error > > > 2018-07-17 20:48:42.071+0000: libxl: > > > libxl_dom.c:994:libxl__domain_firmware: xc_dom_kernel_file failed: No > > > such file or directory > > > 2018-07-17 20:48:42.071+0000: libxl: libxl_dom.c:1140:libxl__build_hvm: > > > initializing domain firmware failed > > > 2018-07-17 20:48:42.071+0000: libxl: > > > libxl_create.c:1284:domcreate_rebuild_done: cannot (re-)build domain: -1 > > > > > > > > > The other logs are below: > > > > > > > > > cat /var/log/qubes/qrexec.win7vm.log /var/log/qubes/qubesdb.win7vm.log > > > /var/log/qubes/vm-win7vm.log > > > > > > > > > > > > > > > domain dead > > > cannot connect to qrexec agent: No such process > > > > > > > > > > > > > > > vchan closed > > > vchan closed > > > vchan closed > > > vchan closed > > > vchan closed > > > > > > > > > > > > > > > 2018-07-17 16:00:47,733 Creating directory: /var/lib/qubes/appvms/win7vm > > > 2018-07-17 16:00:48,130 Creating icon symlink: > > > /var/lib/qubes/appvms/win7vm/icon.png -> > > > /usr/share/icons/hicolor/128x128/devices/appvm-red.png > > > 2018-07-17 16:02:14,548 Starting win7vm > > > 2018-07-17 16:02:18,294 Setting Qubes DB info for the VM > > > 2018-07-17 16:02:18,295 Starting Qubes DB > > > 2018-07-17 16:02:18,396 Activating the win7vm VM > > > 2018-07-17 16:02:23,203 Start failed: qrexec-daemon startup failed: > > > Connection to the VM failed > > > > > > > > > 2018-07-17 16:04:14,845 Starting win7vm > > > 2018-07-17 16:04:19,028 Setting Qubes DB info for the VM > > > 2018-07-17 16:04:19,029 Starting Qubes DB > > > 2018-07-17 16:04:19,161 Activating the win7vm VM > > > 2018-07-17 16:04:24,616 Start failed: qrexec-daemon startup failed: > > > Waiting for VM's qrexec agent...failed > > > > > > > > > 2018-07-17 16:07:57,847 Starting win7vm > > > 2018-07-17 16:08:01,926 Setting Qubes DB info for the VM > > > 2018-07-17 16:08:01,927 Starting Qubes DB > > > 2018-07-17 16:08:02,025 Activating the win7vm VM > > > 2018-07-17 16:08:04,243 Start failed: qrexec-daemon startup failed: > > > Waiting for VM's qrexec agent...failed > > > > > > > > > 2018-07-17 16:08:41,924 Starting win7vm > > > 2018-07-17 16:08:45,910 Setting Qubes DB info for the VM > > > 2018-07-17 16:08:45,911 Starting Qubes DB > > > 2018-07-17 16:08:46,047 Activating the win7vm VM > > > 2018-07-17 16:08:48,336 Start failed: qrexec-daemon startup failed: > > > Connection to the VM failed > > > > > > > > > 2018-07-17 16:12:10,359 Starting win7vm > > > 2018-07-17 16:12:14,594 Setting Qubes DB info for the VM > > > 2018-07-17 16:12:14,595 Starting Qubes DB > > > 2018-07-17 16:12:14,726 Activating the win7vm VM > > > 2018-07-17 16:12:17,023 Start failed: qrexec-daemon startup failed: > > > Connection to the VM failed > > > > > > > > > 2018-07-17 16:13:55,682 Starting win7vm > > > 2018-07-17 16:13:57,858 Start failed: internal error: libxenlight failed > > > to create new domain 'win7vm' > > > 2018-07-17 16:16:52,661 Starting win7vm > > > 2018-07-17 16:16:54,430 Start failed: internal error: libxenlight failed > > > to create new domain 'win7vm' > > > > > > > > > Thanks! > > > > > > > > > Peter > > > > Did you resolve this? Because I have the same problem in Qubes 4.0 when I > > am trying to start win7 templateVM (not standalone) I got the same error > > "Start failed: internal error: libxenlight failed to create new domain > > 'win7'". > > > If you have the same error it's because you havent set virt mode to HVM and > kernel to none. > Check what values you have using qvm-prefs and change them with the same > tool.
Hi, thanks for you help. When I am choosing HVM for StandaloneVM all working correctly. But when I am choosing HVM for TemplateVM then Windows 7 installer starting like usual and after first reboot VM is not going off. I mean window of VM disappearing but VM staying with yellow circle. And if I am killing this VM even after 1 hour from starting, then windows 7 give me error about aborted installation. P.S. With StandaloneVM all this process with installation and rebooting Windows 7 not taking more then 5 minutes. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a17ea41d-031d-49a5-8c42-0d12d1fec937%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
