Virtualizar Windows Xp En Windows 7
Nelson Suggs
Ok, this is embarrassing and thanks for reporting. Above it show that I have installed distrobuilder from the stable, published on the 20th of January 2021. But that is not recent enough. We need to refresh our distrobuilder so that it comes from the edge channel for now. Once the version from the stable channel gets updated, we can switch back to the stable channel.
So I decided to start from a clean system, and launched a VPS with Ubuntu 20.04. I downloaded the Windows ISO through that VPS and run the command. It worked fine, and finally I downloaded the generated .iso.
I have tried the whole process from scratch and have updated the whole post accordingly.
To make sure I have a clean Ubuntu 20.04 LTS system, I created a $5 VPS (Linode, in my case) and run the following exact commands.
Note the Windows ISO URL. I attempted a download from my desktop just to let it download a bit and then click on the Firefox download manager to Copy Download Link. Then, I pasted that command in the wget command below. It got downloaded at 35MB/s :-). Therefore, replace with your download link from Firefox, and cancel the download from your desktop. The next command to the wget is to rename (mv) the file so that the filename is cleaned up.
I do not know what went wrong with the previous instructions. I do too get those errors when I run the repack-windows command on my desktop. I have tested the above instructions with distrobuilder from the edge channel and it still worked.
You are running the LXD commands as root and I suppose that you are connected to your host as a non-root user.
You should log out from root and go back to your non-root user account (such as user or ubuntu).
To verify that you can run X11 apps from within an account from the terminal, try to run xclock. If it works, you are good to go.
Also, the message says localhost:10.0. Normally, if you run echo $DISPLAY, it should say something like :0 or :1.
You typically get localhost:10.0 when you connect to the system through SSH. If that is the case, you should use ssh -X (i.e. add the -X parameter) in order to enable X11 forwarding. If it still does not work, use -Y instead (trusted X11 forwarding). If it still fails, describe your setup so that I cat try to replicate.
Get a shell to the LXD host and install x11-apps and mesa-utils. These will give you the xlock application, and the glxgears GL application.
You can see that both run fine from the remote LXD host. Below, I ssh to localhost for demonstration purposes.
Visit and file a bug report.
Mention that you connect to the LXD host with SSH. And while you can run X11 and GL applications
through X11 forwarding, you cannot get the remote viewer for the Win10 VM to work.
Things to do to get better performance:
1. Use ZFS or btrfs for the storage pool in LXD. dir is likely bad for performance.
2. A VM needs much more RAM than a system container. If you have less than 8GB of total RAM, you should look into this.
With the following, you can see the available storage pools in LXD; where LXD can store containers and virtual machines. Here you can see that my storage pool is called lxd, uses ZFS in some way to organize the space, and I have 34 instances (either containers or virtual machines!). Obviously, when I do not use an instance, I stop it so save precious memory.
Go through these steps and report back the free space available. Most likely you use a storage pool with a loop file, and the space in that file has been exhausted. There are ways around the issue, and we will explore them once we have an idea about the diskspace picture.
James, from what I can see, you have used the defaults when you set up LXD. Your storage pool uses ZFS, and most likely over a loop file. This means that LXD pre-allocated the space for you, and this is a fixed number of GBs.
The last command that you tried, should be lxc storage show default, because default is the name of the storage pool from the previous command. The lxc storage show default will definitely show whether you are using a loop file (a big file that is formatted as ZFS), or a partition (like /dev/sdb4).
So, what do you do if you are stuck with a small storage pool? Being Linux and all, there are too ways around it. The obvious one is to tear everything apart and reinstall from scratch. When you run sudo lxd init this time, you would allocate more space. But that would be too easy.
First, if you have a spare partition, with 80GB or more, then it would be great to put there the storage pool. ZFS on a block partition (instead of a loop file) is even more performant. If that is the case, then tell me to show you the lxc storage commands to create a second storage pool, and move your existing containers/VMs over to the second storage pool. Finally, you make the second storage pool the new default storage pool (and can get rid of the first one).
Second, if you have lots of free space on your root partition (i.e. the / partition), then you can create an additional second storage pool. Now, this can be tricky if you have created separate / and /home/ partitions, and opted to allocate just 30-40GB for / as most installation guides say.
Since you are running this on the RPi4, I suppose you are already familiar with the special instructions at
There should be a few more steps to get from to running distrobuilder which I have not tried.
i tried adding the i915-GVTg_V5_4 profile as an mdev gpu to the instance, and it sort of worked, it was detected in windows and auto installed the driver, device manager says device ok and in task manager it also appears, but i noticed i was still only seeing display feed from virtual gpu, tried disabling that in device manager but after i no longer had display (black screen) in spicy and had to restore snapshot. have any ideas?
thank you for this great tutorial eveything is working like a charm.
I notice only one problem, i cant set a proper display resolution, inside windows settings is set to 800600 and the menu is greyed out.
I have tried to update gpu driver from win10 lxc without success, any thoughts on this? thank you in advance
As described in another post, I was looking for ways to install and run Windows 7, and various Windows programs, in a virtual machine (VM). Of course, creating a VM from scratch, and then installing and configuring a bunch of Windows programs in it, could take a substantial amount of time. Thus, it seemed that the most convenient method for creating a usable Windows system in a VM might be to simply restore one of those ATI 2011 TIBs into a new VM, or convert the TIB to some format that VM software could use.
It appeared that VMware, VirtualBox, and other VM software could use a file in VHD format. VHD also appeared to be the format that ATI 2011 and other tools would most readily convert drive image files into. (Apparently it was possible to create VMs from images created by AOMEI Backupper, by EaseUS Todo Backup, or by Macrium Reflect. Note also that, just as Acronis included a tool to mount and view the contents of its TIB images without restoring them, there were multiple tools to mount, read, and write to VHD files without actually running the VM contained in those files.)
The question at hand, then, was whether and how I could convert an ATI 2011 TIB into a working VM, probably using VHD format. This post explores that question. I was using VirtualBox, so I focused particularly on converting TIBs into working VirtualBox VMs.
In this relatively brief exploration, I found that it was possible to use ATI 2011 to convert a half-dozen TIB drive images of old Windows 7 installations to VHD, and to use those VHDs as the basis for VMs in VirtualBox.
I found, unfortunately, that the resulting VMs had problems. These VMs came from three different computers. The VMs from two of the three computers had Windows-related problems: they either failed to start at all, or they started but did not seem to be running software effectively. Perhaps some or all of those problems could have been resolved with sufficient troubleshooting effort. (I did not realize that the Hyper-V virtualization option built into Windows 10 used VHD format. When I added this later note, it seemed that Hyper-V might thus avoid the second conversion step, from VHD to a format compatible with VirtualBox, and might therefore be able to do a better job with these VHDs.)
While those two Lenovo-based VMs seemed to be running Windows successfully, VirtualBox did not allow them (and the other VMs that I was able to run) to run in properly sized windows. It would still have been possible to use them for some purposes, but plainly the little windows were not helpful. It was not clear when or if VirtualBox would be revised so as to eliminate that problem and make those VMs useful.
Since those Lenovo-based VMs did run successfully, without driver issues, it was possible that the TIBs from which they were created would also be most likely to succeed if I were to use restoration approach with them. That is, I might have been able to restore those TIBs into a previously created VM, and that might have avoided the problem of small windows. I did not explore that possibility.
Finally, the VMs that ran successfully indicated that their copies of Windows 7 needed to be reactivated, and so did the copies of Microsoft Office 2010 installed in those VMs. If phone-based activation worked, this would not necessarily pose a problem to the goal of having VMs that were not connected to the Internet and thus, hopefully, would be insulated from corruption by future Windows updates or other invasive Microsoft activities.
The last of the methods explored in this section did not require ATI to be installed: it would be sufficient to use ATI on a USB or other bootable disk to restore a TIB or other image to the computer, and then use VMware vCenter to virtualize that restored installation. My own needs did not call for further exploration of that method.
d3342ee215