Strak8: > Hello to all, > I'm using with happiness for a month the latest release of qubesOS, I'd like > to know: > > 1. I have created several virtual disk (vmdk-to-img or new both with DD and > with mkfs) to be attached to a StandaloneVM. > > [For now, Qubes is installed on a 30GB SSD in the laptop, I had not read the > specifications with automatic partition so much occupied space. I honestly do > not understand why a hypervisor occupies so much space, but soon I will turn > the disk with a larger one. The problem (in addition to money) is that the > ssd is a Msata that I would not be replaced by a more capacious because I > knew that Msata quite warm, so as soon as possible'll take one Sata] > > I would install MS Windows on a virtual disk that I created on the secondary > disk, this I attached a StandaloneVM. Unfortunately the installation fails in > any way. But I doubt that he had done something wrong in creating the virtual > disk. > I would like to know if I can install Windows on a virtual disk on the second > disc? > > 2. In general I would like to know if you can install or run the OS on images > on the secondary disk or as an alternative to a secondary physical disk (SATA > or USB)? > > 3. On some Linux distributions install or even in Live mode, just imposed the > native resolution of the primary display the video freezes. I have not found > the Xrandr option to count down to return to the initial setting. In > addition, for example, I can not set the full screen on installing Windows > OS. There's a reason for this? > > Thank you ;=) >
Hi, Well, I am not an expert on this, so perhaps you want to wait for more expert advice. But it seems to me that Windows probably does not have a driver for the Xen virtual block device presented to the StandaloneVM. I suggest you try an alternative approach. First, create an HVM template for your Windows installation (do everything just as you would normally). Then, obliterate what's on your second disk, luksFormat it and mkfs.ext4 it (or whatever file system you want). Now, in Dom0, navigate to /var/lib/qubes/vm-templates/[name of created HVM template]. Inside this directory should be three .img files: private.img, root.img, and volatile.img. It's OK if volatile.img doesn't exist. Now, just delete root.img, create a new root.img of the size you want (dd if=/dev/zero bs=1M count=...) on your secondary drive, then make a symlink (ln -s /mnt/second/windows/root.img /var/lib/qubes/vm-templates/windows/root.img). Then start the template and install normally (hopefully). You can then create many Windows HVMs based on that Windows HVM template and enjoy :). Andrew -- 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/733381b0-6a29-5997-2aac-b22e7ba9b81a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
