[qubes-users] Re: Trouble installing Windows SP1 7 64-bit on Qubes 3.2
> I have the same Problem :( > When I change the model type to Cirrus,then appear a libvirtError that > doesn't make any sense to me: > > Orignal Message: libvirt.libvirtError: Operation schlug fehl: Domain > 'win7x64test2' ist bereits mit UUID ---- > definiert > > In english it should be something like: libvirt.libvirtError: operation > failed: Domain 'win7x64test2' already exists with UUID > ---- > > The Original command that I run: > qvm-start win7x64test2 --cdrom=/home/dave/Schreibtisch/win7_x64.iso > --custom-config=/home/dave/Schreibtisch/win7x64test2.conf > > Can anyone help me please?? Run "virsh undefine win7x64test2" in dom0, then try again. -- 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/dc1534f6-5a9f-4ad8-9ef2-e04e4467b525%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Trouble installing Windows SP1 7 64-bit on Qubes 3.2
On Thursday, February 9, 2017 at 12:19:47 PM UTC-6, bal...@gmail.com wrote: > I have the same Problem :( > When I change the model type to Cirrus,then appear a libvirtError that > doesn't make any sense to me: > > Orignal Message: libvirt.libvirtError: Operation schlug fehl: Domain > 'win7x64test2' ist bereits mit UUID ---- > definiert > > In english it should be something like: libvirt.libvirtError: operation > failed: Domain 'win7x64test2' already exists with UUID > ---- > > The Original command that I run: > qvm-start win7x64test2 --cdrom=/home/dave/Schreibtisch/win7_x64.iso > --custom-config=/home/dave/Schreibtisch/win7x64test2.conf > > Can anyone help me please?? I was having the same issue, but these instructions worked for me. https://github.com/QubesOS/qubes-issues/issues/2488 -- 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/5de1c628-e458-43ac-99e1-6988d1d8d5d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Trouble installing Windows SP1 7 64-bit on Qubes 3.2
I have the same Problem :( When I change the model type to Cirrus,then appear a libvirtError that doesn't make any sense to me: Orignal Message: libvirt.libvirtError: Operation schlug fehl: Domain 'win7x64test2' ist bereits mit UUID ---- definiert In english it should be something like: libvirt.libvirtError: operation failed: Domain 'win7x64test2' already exists with UUID ---- The Original command that I run: qvm-start win7x64test2 --cdrom=/home/dave/Schreibtisch/win7_x64.iso --custom-config=/home/dave/Schreibtisch/win7x64test2.conf Can anyone help me please?? -- 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/2d62d4d9-acb6-443d-8470-bffdc1b3bffa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Trouble installing Windows SP1 7 64-bit on Qubes 3.2
tirsdag 6. desember 2016 11.07.52 UTC+1 skrev Swâmi Petaramesh følgende: > Hello, > > I run Qubes 3.2 on an HP ProBook 6470b laptop > > I'm trying to install Windows 7 64-bit SP1 following instructions : > https://www.qubes-os.org/doc/hvm/ > > I'm using an ISO file sitting in an AppVM. > > I could create the VM and start it, it first starts in character mode > and displays a "Windows is loading files..." progress bar (so I'm sure > that the VM boots and can access the ISO image), then shifts to graphics > mode and displays "Starting Windows" in a nice font, and then... sits > there forever without any visible activity, and no error message. > > Any clue ? > > I know that my Qubes setup is able to run Windows 7 in an HVM as I have > created another Win7 HVM, with a Windows 7 converted from a VirtualBox > installation, and it works good. But this one is 32-bit, and I'm trying > to install a 64-bit version as I read that Qubes Windows tools support > only a 64-bit Windows installation... > > Thanks in advance for your help. > > Kind regards. I have experienced the same thing (and was actually just now about to create a new topic when I saw you beat me to it). As far as I can tell the problem is caused by some update to the system (using qubes-dom0-update) as everything works just fine on a fresh Qubes 3.2 system. This is my experience: 1. Installed Qubes 3.2 2. Installed Windows 32-bit HVM just fine. 3. (started testing QubesOS, including updating dom0) 4. Discovered that I should have installed win7-x64 in the first place. 5. Tried installing win7-x64, but booting the install media hung at exactly the same place as described by thread starter. 6. Made a fresh install of Qubes 3.2 and now win7-x64 installed just fine. 7. (started testing QubesOS, including updating dom0) 8. Now I want to make a win7-x64 Template, using the same install media, and I am once again stuck... How should we proceed to debug what is causing this problem? -- 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/7f10d8b5-f9e8-4705-a5cd-8de7b05aa1f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
