Vizhouz

Members
  • Posts

    13
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Vizhouz's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hey, I followed the new instructions on page 28 and everything works until I get to the point of creating an admin. I create it and get no error message but it doesn't seem like an admin account is created. It reloads and then stays on the same "create admin" page. If I try to create a new admin account now I get: "Error while trying to create admin user: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000][1045] Access denied for user 'root'@docker-ip (using password:YES). I guess thats because I already created the same thing once but I don't know. Don't really know what to do now. EDIT: Okay I was able to fix it. I think it has something to do with adding/granting privileges to the root@localhost. I also did that for root@docker-ip like SRB on page 13 (http://lime-technology.com/forum/index.php?topic=50090.180) and I think that's what solved it.
  2. I'm using an i7 5820k, 16GB, MSI X99s Sli Plus and a GTX 770 right now. Which diagnostics do you need?
  3. Hey, according to http://lime-technology.com/forum/index.php?topic=51874.0 nested virtualization should work now. I would like to have a vm in my vm, so I tried vmware and also changed the vmx.allowNested="TRUE". As far as I know to use nested virtualiziation I have to tick the "Virtualize Intel VT-x/EPT or AMD-V/RVI" settings, so I did that but I get the error "Virtualized Intel VT-x/EPT is not supported on this platform". Do I need to do something else? Thanks
  4. Hey, according to http://lime-technology.com/forum/index.php?topic=51874.0 nested virtualization should work now. I would like to have a vm in my vm, so I tried vmware and also changed the vmx.allowNested="TRUE". As far as I know to use nested virtualiziation I have to tick the "Virtualize Intel VT-x/EPT or AMD-V/RVI" settings, so I did that but I get the error "Virtualized Intel VT-x/EPT is not supported on this platform". Do I need to do something else? Thanks
  5. It sounds like you should stub the USB controller so unraid doesn't use use it. The info on how to do this should be in the first post in the 6.2 announcement thread. Tried that but it didn't change anything. As soon as I turn on the VM the devices on the controller don't work anymore. The lights on mouse/keyboard turn off, but not on my sound card. Tried to switch ports on the controller, but the devices don't work, but since the lights don't turn off the controller seems to be "on" atleast. Ok I was able to fix this by installing the USB controller's drivers, in my case VIA Labs drivers. I did this by connecting keyboard/mouse to another controller and accessing the vm with vnc so that I could use them. This was only necessary on Win7, that's why I was confused. Win10 included these drivers.
  6. It sounds like you should stub the USB controller so unraid doesn't use use it. The info on how to do this should be in the first post in the 6.2 announcement thread. Tried that but it didn't change anything. As soon as I turn on the VM the devices on the controller don't work anymore. The lights on mouse/keyboard turn off, but not on my sound card. Tried to switch ports on the controller, but the devices don't work, but since the lights don't turn off the controller seems to be "on" atleast.
  7. Can confirm there is no issue with creating a Windows 7 VM in unRAID 6.2 that I can find. I was able to install Windows 7 just fine right now on a test machine. No errors. Chances are you have corrupt installation media or something amiss with your hardware. If the VM enters a paused state, it could also be because of insufficient disk space on the underlying storage device. Hey, that's good to know, so it's something on my machine. I solved it by only using 1 cpu. Right now I think it was either that or that I'm not using the emulatorpin option anymore. Something cpu related though I think.
  8. not sure if it will help, but many other issues around installing/upgrading Windows have been resolved by limiting the VM to a single vCPU while installing, and only enabling more vCPUs when the install completes. Thank you very much! Using one CPU (cpu0) worked fine. Although after restarting it and adding the other cores it didn't boot up anymore (stuck at win symbol). Tried some more combinations and I 'm back to all the cores I wanted to use and it works. Don't know what's different but it works.
  9. Hey Guys, I already passed through an usb controller before. That works fine for my Windows 10 VM. But everytime I pass through the whole controller for my Windows 7 VM all the devices on the controller turn off and don't turn on again (Usually when I start the win10 VM they also turn off/on once). I don't know why and would like to fix that. I use <hostdev> to pass through the controller.
  10. Any updates on this? I'm experiencing the same while installing Windows 7. The last step freezes and in UnRaid the VM pauses and I can't unpause it "internal error: unable to execute QEMU command 'cont'...". The Win 10 Installation was flawless though, since I'm running this right now. Wouldn't want to downgrade since im using NVMe.
  11. Hey guys, I've already installed a Win10 VM a few weeks before and everything went fine but this time I want to install a Win7 VM and I can't get it to work. First step of the installation (copying files etc.) works fine then it restarts once and works on the last step "completing installation..." it works for a minute but then it freezes. At first I thought it's the installation itself, but then I saw in unraid, that the VM is paused. I don't know why it should pause there and I can't continue the vm since I get the error "internal error: unable to execute QEMU command 'cont'...". I'm using 6.2.0-rc5 right now. Did this happen to anyone else or does someone know a solution? Thanks EDIT: For everyone else having this error: Using only one cpu (I chose default cpu0) works. Although changing it back to 10 cores caused a freeze on the first boot again.. Don't know why but now it works.