Re: [qubes-users] Windows 7 HVM Install
Here's what worked for me... When you hit the uuid error, delete your custom win7.conf and make a new copy of the system win7.conf, repeat the cirrus fix, and you may be good to go. Apparently a uuid gets written to the system conf file and if your custom one is out of sync then things don't work. Not an expert - just reporting trial and error results. -- 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/6f48052e-a214-43c5-9c0b-d3297afbd812%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Windows 7 Install
On Wednesday, May 24, 2017 at 1:27:13 PM UTC-7, James Chi wrote: > Hello all, > > I am not only new to Qubes, I am also new to linux so I am going to have to > learn a lot. I would appreciate any help. > > I have a windows 7 iso on usb. I created a usb vm called sys-usb. Now I am > trying to copy the iso file to dom0 based on the following: > > "qvm-start win7 --cdrom=/usr/local/iso/win7_en.iso > > The above command assumes the installation ISO was transferred to Dom0 > (copied using dd command from an installation CDROM for example)." > > Can someone help me figure out this step? Sorry for the newbie question. I > will have lots of these. You got the right answer from mikih..., but don't hesitate to bring other newbie questions - we're all learning here. I've installed Win7 on Qubes a few times, most recently today, in fact. I had a couple issues, but everything seems good now. Happy to help if I can. -- 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/61973d5f-f9e2-4f3d-8eab-1d2cf1f888e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] VT-d breaks suspend/resume (Lenovo T460)
On Saturday, May 13, 2017 at 12:18:19 PM UTC-7, Ed wrote: > I had the same problem with a lenovo x1 carbon, there are a lot of threads > out there with this issue, with a lot of fixes (such as update the bios), but > for me I fixed it by disabling the security module (TPM) in bios. > > Ed Thanks - that did it for me, too. I guess I can pick any 2 out of 3: (1) suspend/resume, (2) VT-d, and (3) TPM. I'm not using AEM, so TPM loses. -- 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/2c360070-4f03-4f90-a1c5-4b6c6d4fa465%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] VT-d breaks suspend/resume (Lenovo T460)
I had v3.2 installed and running great with VT-d disabled. When I enabled it in the BIOS, everything else seems OK but when the laptop suspends, it will no longer wake up. I have to hold down the power button for a hard power off to restart. This is a recent, new install of Qubes OS v. 3.2 on a Lenovo T460. Disable/enable of VT-d a couple times and testing the suspend/resume confirms that VT-d is the culprit in this behavior. Can anyone provide insight on how to fix or at least begin to diagnose? Thanks. -- 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/5aab4348-84b4-45b0-99f0-0f69c18580f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 won't boot with newer kernels on Lenovo T450
On Wednesday, May 10, 2017 at 5:46:31 AM UTC-7, migue...@gmail.com wrote: > I had the same problem on my T450S. I seem to have solved it by changing the > Graphics in BIOS from 256M to 512M. After that the 4.4+ kernels seem to boot > fine. Exactly! I had the same experience on my T460. -- 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/d16bf7de-a71a-4274-a48b-b540dd935659%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: What did qubes do to my laptop?
On Monday, May 8, 2017 at 7:04:40 PM UTC-7, Chris Laprise wrote: > Maybe someone is trying out Intel ME backdoor exploits? Or a freak > glitch from a cosmic ray... Better than any explanation I've got... > My advice would be to remove the battery and AC cord to totally > power-off the machine. But that's not easy now since newer laptops have > internal batteries. You should also check for a BIOS firmware update. Good points. In this case, because my 3.2 install failed, I had just updated to the latest March-17 BIOS from Lenovo yesterday. And the BIOS has a way to temporarily disable the internal battery, which I had done along with removing the main battery and unplugging - and it was like that for about 10 minutes while I switched the SSD back to MATE. But it didn't exorcise the ghost. -- 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/079c1217-e0a2-42b5-aa1a-6300c03945a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: What did qubes do to my laptop?
On Monday, May 8, 2017 at 6:21:27 PM UTC-7, cooloutac wrote: > wow thats weird. maybe something to do with your gpu or monitor. Maybe, but it's the same onboard Intel graphics and laptop screen that ran Qubes before. Not criticizing your idea - this is a mystery. I'll probably never know - hope to never duplicate. -- 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/9c3a241a-e12b-48ef-b1da-767f93f480bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] What did qubes do to my laptop?
Sorry, this is long, but it's perhaps the strangest thing I've ever seen happen to a computer - and I started programming in 1979 when I was in Jr. High... I have a Lenovo ThinkPad T460 laptop that previously had Qubes OS 3.1 installed and functioning, but I removed it and installed Ubuntu Mate because some of the things I needed to do (i.e. Skype) weren't easy to do on Qubes. When I read about some of the improvements in 3.2, I decided to try it. I pulled the Ubuntu drive and tried to install 3.2 this weekend to a new SSD. But I couldn't get it to install - just stuck in a reboot loop, even after I tried some of the UEFI bug fixes. So this morning I decided to install 3.1 and see if I could upgrade to 3.2. That's when things started to get weird. After the 3.1 install completed and I logged in to the configured OS, the screen came up asking if a wanted to use the default configuration, and as soon as I touched the mouse, the screen went blank. Keep in mind this is the exact same computer that previously ran 3.1 flawlessly. What I found over the course of several reboots and a reinstall (which still had the same problem) is that after I logged in, moving the mouse pointer (with the trackpad, pointing stick, or external mouse) would cause the display to go blank. (I didn't get a chance to test it with an external monitor because of what I'll describe below.) By randomly moving the mouse pointer, the screen would flicker between black and normal, and if I got lucky I could get the screen to redisplay so I could see it. At that point, if I didn't touch the mouse, I could use the keyboard to interact with the OS. I launched a terminal, updated Dom0 - no change after reboot to the weird mouse/display thing. So I was using a different computer to research options while my Qubes OS desktop was logged in (I had moved the mouse randomly until the screen was displaying). Then after a few minutes I noticed the display rapidly flickering - now not from normal to black but from normal to very bright. I found that the screen was frozen - no response to any keyboard or mouse. So I held down the power button for a hard shutdown. That's when things got REALLY weird. When I restarted the computer, as the Lenovo logo screen came up, the screen was flickering as before and the exact Qubes OS screen that was displayed prior to the shutdown was displayed along with it - like a screenshot (but flickering) overlayed on the normal display. It continued all the way through the boot and login, then the screen froze and continued to flicker the same image. Over the course of several restarts, and going to the BIOS menu, etc., this flickering Qubes desktop was like it was burned into the screen. I was pretty freaked out. I powered completely down and put the Ubuntu Mate drive in, and even then the flickering Qubes ghost image displayed with the Mate desktop. At a loss, I shut down and got some work done with my other computer. An hour later, I started it up again and the flickering Qubes image was still there, but fainter. Basically over the course of about 5 hours, each time I booted the computer, the flickering Qubes ghost image was successively fainter until finally it was gone. What happened? What did Qubes do to my laptop? -- 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/d29d07e0-dac6-4a40-979b-9d4931aa6a7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes R3.2 on Thinkpad X250: cannot install Windows 7 (hangs on "Starting Windows" at install)
On Wednesday, November 9, 2016 at 5:03:12 AM UTC-8, Pablo Di Noto wrote: > Hello, > > Never had much use for a Windows7 HVM so far. > > Months ago, I installed W7 on Qubes just for the sake of testing. Got to the > point of installing qubes-windows-tools and had some success with it, but > never used it much (in fact, never activated a license on the resulting W7 > install). > > Now I want to start from scratch, but cannot make a HVM to go further than > "Starting Windows" screen on the install phase. > > Only changes I recognize on my setup are: > - R3.2 final installed (which included several Xen updates, 4.6 to 4.6.3 IIRC) > - Got a "storage pool" enabled, to use the machine SHDD together with the > boot SSD. > > So far, tried all this: > - several W7 ISO versions (including the ones I successfully used before). > - creating the HVM with 2, 3 and 4gb of memory. > - creating the HVM on my "big storage" pool, the local SHDD, using -P option > in the qvm-create command > - creating the HVM on the original storage pool, the local boot > qubes-dom0-root volume, using the GUI to create the machine. > - using debug options on all the attempts, but logs show absolutely nothing > that I can recognize as error. > > Any pointers on what to try next, or how to debug? > > Thanks in advance! > ///Pablo I don't have any answers, but a data point that might be useful. I've installed windows HVMs on Qubes 3.2 on both Lenovo T460 and x260 recently, and had no issues. The x250 should be similar. One variable I see is that you have a storage pool whereas mine both had a single drive. Don't know if that makes a difference. -- 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/e4f843c6-ad15-4299-a111-30f121a2a6a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Windows HVM doesn't get updates
On Sunday, April 10, 2016 at 4:21:26 PM UTC-7, Salmiakki wrote: > I just installed Win7 in a HVM and I can ping and I can access websites but > it doesn't find any windows updates. > Any suggestions what I might be missing? > Any ideas where I might look for information? The update just seems to hang... Here is the authoritative way to fix Win7 update issues on a new install. I've used it multiple times, including my recent Qubes HVM install. However, one thing it doesn't say that I highly recommend is to STOP the Windows Update service before installing the downloaded update package(s) in step 3. http://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-7-update-solution/f39a65fa-9d10-42e7-9bc0-7f5096b36d0c -- 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/7c0125e9-c538-4849-801b-14e04e6d6839%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Lenovo x260
-- 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/d7227afc-3a56-492d-bce8-01f9fdf1d643%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20F6CTO1WW-20161102-203013.yml Description: Binary data
