January 24, 201610 yr Hello everyone, I'm trying to create a windows 7 virtual machine using an ISO image that I have used previously on my desktop. On the creation menu I select the Windows7.iso from /mnt/user/ISOs, select the VirtIO iso from the same directory and create the VM template. However when I open the VM in the browser based GUI it simply has a 'No bootable device' error after it tries to boot from CD drive and HDD I changed the boot order in the XML to have the the optical drive first but this made no difference. Any ideas? I'm sure this ISO is bootable (I'm pretty sure windows ISOs are by default?) but either way I will test this in the morning. In the meantime is there anything else I can look at? Is there any known issue with installing windows 7 on KVM? Thanks!
January 24, 201610 yr Take a look at this documentation and see if you missed a step or two. http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Management
January 24, 201610 yr Author The Windows 8 ISO I have works fine so must be an issue with the ISO itself. Thanks for responding Moose.
January 24, 201610 yr Author Got the windows 7 iso booting fine after downloading a .bif and re-creating the ISO. Now I'm at the installation stage where windows is asking where I want to install windows - Except I do not have a drive visible. I found this guide in the manual and tried to follow the driver installation steps, however I am not allowed to install the drivers: To continue installation, use the Load Driver option to install 32-bit and signed 64-bit drivers. Installing an unsigned 64-bit device driver is not supported and might result in an unusable windows installation So I guess I need to figure out how to force the driver installation - Or figure out a way to present somewhere to install.
January 24, 201610 yr Author Got the installation working by creating an x86 windows installation instead of an x64. No matter what I did I could not get the x64 version of Windows 7 Professional installed. If anyone has any recommendations I'd like to hear them as I would like a x64 installation instead..
January 24, 201610 yr I had no problem installing from a retail copy of Windows 7 Pro so if you have access to that it is something to try. One thing you might try with your current ISO is: Use the Edit HTML option to change the 'bus' entry for the virtual hard disk to 'sata' instead of 'virtio' Delete the address entry so that libvirt can create an appropriate one for a sata device You should now find that you do not need to load the virtio drivers during the install. You would want to later switch to the virtio drivers for better performance, but this could be done by loading them after the Windows is installed and running. Note in particular that you are going to want the virtio network driver (unless you also change the network device in the XML) to have network access.
January 24, 201610 yr Author Also, I wonder whether this is the same phenomenon we saw recently here... Could be - But this would cause additional problems. The ISO I have is 'activated' already so I do not need a product key. This came from a DVD quite some time ago and I copied the contents my HDD, hence why I needed to go and download the BIF file to make it bootable. If I can't use this ISO I will need to find a product key. I'm sure I have one lying around but I'd rather just use this activated version.
January 24, 201610 yr Also, I wonder whether this is the same phenomenon we saw recently here... Could be - But this would cause additional problems. The ISO I have is 'activated' already so I do not need a product key. This came from a DVD quite some time ago and I copied the contents my HDD, hence why I needed to go and download the BIF file to make it bootable. If I can't use this ISO I will need to find a product key. I'm sure I have one lying around but I'd rather just use this activated version. Apologies, wrong link... Try this one...
January 24, 201610 yr Author Also, I wonder whether this is the same phenomenon we saw recently here... Could be - But this would cause additional problems. The ISO I have is 'activated' already so I do not need a product key. This came from a DVD quite some time ago and I copied the contents my HDD, hence why I needed to go and download the BIF file to make it bootable. If I can't use this ISO I will need to find a product key. I'm sure I have one lying around but I'd rather just use this activated version. Apologies, wrong link... Try this one... I was trying to install 0.1.102 which is much older than the version listed in that post.. so unfortunately doesn't seem related. In all likelihood it's possibly the ISO I used.
January 24, 201610 yr Author I'm up and running without issues on 32 bit so I'm just going to stick with it. No real reason to go to 64 bit, at least for now. Now for a follow up question: I am trying to connect my VM to work VPN so I can work remotely. If connected to the VM over RDP the session gets dropped as soon as the VPN connects. So RDP is not an option. I can connect to the VPN okay in the browser based VNC connection from the unRAID GUI. Working via a web browser is not ideal so I was hoping to use a VNC application instead - I am using 'Terminals'. I am unable to connect via VNC. I have tried both the Windows IP (.20) and unRAID IP (.13) with no luck. I have tried port 5900 and 5700. I cannot get the VNC connection to work over Terminals. Is it possible to use VNC other than the browser based option?
January 24, 201610 yr I'm up and running without issues on 32 bit so I'm just going to stick with it. No real reason to go to 64 bit, at least for now. Now for a follow up question: I am trying to connect my VM to work VPN so I can work remotely. If connected to the VM over RDP the session gets dropped as soon as the VPN connects. So RDP is not an option. I can connect to the VPN okay in the browser based VNC connection from the unRAID GUI. Working via a web browser is not ideal so I was hoping to use a VNC application instead - I am using 'Terminals'. I am unable to connect via VNC. I have tried both the Windows IP (.20) and unRAID IP (.13) with no luck. I have tried port 5900 and 5700. I cannot get the VNC connection to work over Terminals. Is it possible to use VNC other than the browser based option? Try using tightvnc as the client software and connect to unraids IP.
January 24, 201610 yr Author Try using tightvnc as the client software and connect to unraids IP. This seems to do nothing. I press connect and the menu just disappears. 1. I open the TightVNC viewer 2. In the remote host section I type 192.168.0.13::5700 3. Click connect 4. Viewer disappears, nothing happens EDIT: 5900 worked. Why does the browser use 5700?
January 24, 201610 yr Try using tightvnc as the client software and connect to unraids IP. This seems to do nothing. I press connect and the menu just disappears. 1. I open the TightVNC viewer 2. In the remote host section I type 192.168.0.13::5700 3. Click connect 4. Viewer disappears, nothing happens EDIT: 5900 worked. Why does the browser use 5700? 5900 is the right port to use. 5700 is the web socket port used to send VNC through a browser. 5900 is for VNC clients.
January 24, 201610 yr Author Try using tightvnc as the client software and connect to unraids IP. This seems to do nothing. I press connect and the menu just disappears. 1. I open the TightVNC viewer 2. In the remote host section I type 192.168.0.13::5700 3. Click connect 4. Viewer disappears, nothing happens EDIT: 5900 worked. Why does the browser use 5700? 5900 is the right port to use. 5700 is the web socket port used to send VNC through a browser. 5900 is for VNC clients. Cheers Jon - All up and running now - Albeit it's slow. No surprise really with the setup I currently have going. VNC to the Windows 7 VM from my desktop. Once in the VM I connect to the VPN, and then remote desktop to my work laptop. I don't need to RDP to the laptop but it makes my life infinitely easier. An easier solution would be just to install the VPN client on my desktop but then my home connection has to abide by their web browsing policies while connected - Which I do not want.
January 24, 201610 yr Try using tightvnc as the client software and connect to unraids IP. This seems to do nothing. I press connect and the menu just disappears. 1. I open the TightVNC viewer 2. In the remote host section I type 192.168.0.13::5700 3. Click connect 4. Viewer disappears, nothing happens EDIT: 5900 worked. Why does the browser use 5700? 5900 is the right port to use. 5700 is the web socket port used to send VNC through a browser. 5900 is for VNC clients. Cheers Jon - All up and running now - Albeit it's slow. No surprise really with the setup I currently have going. VNC to the Windows 7 VM from my desktop. Once in the VM I connect to the VPN, and then remote desktop to my work laptop. I don't need to RDP to the laptop but it makes my life infinitely easier. An easier solution would be just to install the VPN client on my desktop but then my home connection has to abide by their web browsing policies while connected - Which I do not want. Look up split tunnel configuration. You can make it so browsing from the remote desktop uses your personal network and yet RDP over your VPN.
January 25, 201610 yr Author Look up split tunnel configuration. You can make it so browsing from the remote desktop uses your personal network and yet RDP over your VPN. Is that as simple as: https://documentation.meraki.com/MX-Z/Client_VPN/Configuring_Split-tunnel_Client_VPN Looks straightforward.. So split tunnel would allow me to connect to the VPN on my desktop and simply RDP to my work laptop? Or did I misunderstand what you said?
Archived
This topic is now archived and is closed to further replies.