• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About tasraison

  • Rank


  • Gender

Recent Profile Visitors

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

  1. Thank you, I messed with the mount options, "_netdev" did the trick, now the Vm is mounting shares at boot. Cheers,
  2. One more question : On Vbox 2.3 9p filesystem wouldn't mount on boot, so I used the post_startup script to mount Unraid shares. I cannot get it to work with Vortexbox 2.4. I also tried to modify fstab, but no success either. How do you mount your shares? tq
  3. thank you,, I had switched it to scsi (previously working w vortexbox2.3), switched one more time to sata, now it's booting !
  4. I tried to install Vortexbox 2.4 but got stuck at boot with : "a start job is running on dev-disk", could you explain how you managed to install it ? thank you for your help
  5. not sure but I think the Lian Li case comes with 3 4-pin connectors for the 5-drives bay. The PSU you selected will only give you 2 of these connectors, you 'll need one extra . And one sata connector from the psu is enough if you have a disk outside the bay. In the end you'll end up with a lot of cables inside a small unit, may be a modular psu makes more sense.
  6. I spent a few too many hours on this issue, I'm glad it's not a total waste of time...
  7. If you have solved GPU/audio passthrough, to get OpenElec working you may also need to add the virtio drivers. They are already part of the linux kernel, so with "make menuconfig" I 've produced a config file including the Virtio drivers (net pci, balloon..). To have a OpenElec+virtio Distro, proceed as follow : Prepare to compile your own OpenElec distro as described in OpenElec Wiki (http://wiki.openelec.tv/index.php/Compile_from_source) . Check that you can build the last stable distro (5.0. : git checkout 5.0.8 PROJECT=Generic ARCH=x86_64 make release Once you are sure
  8. Very nice guide. I still had to struggle to actually pass the USB controller. I make a small note to spare the trouble to anyone else : It's not just about the xml file and BIOS, boot parameters also need to be adjusted : It's mentionned (mentioned?) here https://lime-technology.com/forum/index.php?topic=35070.msg327239#msg327239, thank you!
  9. try with the following, it worked for me: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/mnt/disk1/Images/vortexbox/vdisk1.img'/> <target dev='sda' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Images/vortexbox-2.3.iso'/> <tar
  10. It seems that this plugin is no more available on googlecode. does anyone have a valid download link? Thank you for your help.
  11. Almost same issue here, so just in case : I tried the install with the packages provided in this post (Page18 I think...) on V5-R5. I installed VirtualBox-4.1.18-unRAID.3.0.35 & Oracle_VM_VirtualBox_Extension_Pack-4.1.18 & phpvirtualBox Ended up with the "Could not connect to host (" error. I had to fix a link to get it work : I changed /root/.VirtualBox -> /boot/custom/vbox to .VirtualBox -> /opt/VirtualBox ; Don't know if this issue is related to the installation package or to my config, Anyway everything is ok now, thank U all.