El domingo, 20 de noviembre de 2016, 20:11:45 (UTC), Scot Anderson escribió:
> New to Qubes (installed today!), and this is my first post, but I had this > same problem on my Thinkpad T420 and have gotten past it. Some light google > sleuthing led me to a Proxmox issue that was similar, and they suggested > trying a 'cirrus' video card instead of default. > > Digging around in Qubes source, I found you can pass a custom config to > qvm-start. I copied the config for the vm to another location (from > /var/lib/qubes/vm-templates/win7/win7.conf in my case) and edited the line in > domain->devices->video->model and changed the type from 'xen' to 'cirrus'. So > the result looked like this: > > <model type='cirrus' vram='16384' /> > > Then I started the vm with: > qvm-start win7 --custom-config=[path to new config] > > This allowed me to get past the install hang. I haven't completed the install > yet, so don't know if it'll be necessary once the install is complete. > Great tip, Scot! Doing that I was able to move on into the install process. Being a long-time proxmox user, it never occurred to me that look there for tips (my understanding is that proxmox is kvm- or lxc-based, and since Qubes is trying to move away from qemu-related stuff that sort of things would not apply here). So, for the record, storage pools and specific Lenovo X250 had nothing to do with this Windows 7 "no further than glowing logo" issue. Thanks again! ///Pablo -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f3645941-fb07-49e6-8b31-0f055b2febfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
