Search the Community

Been conversing with SecurityBreach via PM's, and thought I would bring this topic into the open forum for others reading to learn from. I recently installed Arch Linux x86_64 on a Dell Lattitude E6500. This is a quad core Intel i5 with 8 GB of RAM. For work puposes, I need to have Windows. I have Windows 7 installed on a seperate partition but realized with the setup I have, that I am now equiped to run Windows in a Vitual environment without it adversaly effecting the functionality of Arch. So I started with Virtual Box and installed 3 VMs. Windows 7 Pro 32 Bit, Windows XP Pro, and Linux Mint 14. The issue I was having was I could not get guest additions to properly install and my screen resolutions were terrible. Screen all streched. SecurityBreach recommended to me using QEMU with KVM. The i5 processor supports vitualization so I enabled that in the BIOS and installed QEMU. Since v1.3.0, QEMU comes with KVM. Prior to that, you had to install the package qemu-kvm (which no longer exist) So I started reading the QEMU Arch Wiki and reading some of the links that SecurityBreach provided and was able to get Windows XP installed and actually running. At this point, I was in the same boat as I was with VBox, the resolution was terrible but also, I did not have network (internet) access. In accordance with the QEMU Arch Wiki, I installed the vde2 package and followed the guidance in getting the network up and running. When I started up the VM I still did not have network capability. I started the VM with: qemu system x86_64 enable-kvm -hda winxp.img -net nic -net vde -m 2048 So at this point, I decided to tackle the resolution issue. SecurityBreach shared with me a topic he had started on the Arch Linux forums and was advised to install the VMWare packages outlined in the Wiki. I did this and added the appropriate line to my start command ichase02@arch64 ~$ qemu system-x86_64 -enable-kvm -hda winxp.img -net nic -net vde vga vmware -m 2048 at this point the VM did NOT start and I received the following error: qemu-system-x86_64: -net vde: Device "vde" could not be initialized So in accordance with the Wiki, I loaded the module "tun" and tried again with the same error. So I thought for a moment and decided to remove the -net vde from the start up command which resulted in this error: qemu-system-x86_64: -net nic: drive with bus=0 ,unit=0 (index=0) exists VM still did not start so essentially I am going from bad to worse. I realize that this is a result of lack of knowledge on my part. I will admit sometimes I read the Arch Wiki's and develop that glaze over my eyes. and do not truly understand what it is they are trying to convay. Once again, that is just my lack of knowledge but for those of you who know me, I am a persistant son of a gun and except for CUPS, I don't quite. Thanks ahead of time and always for your guidance and knowledge and education Ian

First of all, I am on the fense whether this post belongs in the Windows forums or the Linux forums. The host for my Windows XP VM is Arch Linux. I have this VM for work purposes. Before setting it up, I would have to re-boot into my Windows 7 partition. I have everything set up for this VM to be actually more optimal than my company laptop. Not to mention I don't have to reboot into Win 7 anymore (Actually, can't see me booting into this anytime soon ) Guest Additions are properly set up. I have access to my SAMBA storage configured. I even created a folder in my host /home directory ( VM_Storage) and have it properly mapped as a network Drive (H:/ drive) This is great considering I made the VM only 20 GB. The only thing I can't figure out is how to see my network printer. I know what you are thinking. Here we go again with Ian trying to print from Linux ) but technically I am not trying to print from Linux, I am trying to print from the WinXP Pro Guest VM. First thing I did was to see if Windows would detect my printer on the network. It did not. So I tried utilizing the default gateway of my guest OS using port 631 That gave me an error stating it could not find the printer and that the printer may not be active. The printer IS active and I confirmed that on my wife's netbook running Win7. I then tried using the IP of the Server Same thing. As I am sitting here typing this, I wonder if using HTTPS vice HTTP might do the trick. I had to use HTTPS to connect to my CUPS web interface via port 631. Hmmmmmmm