gestrella

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About gestrella

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. unRAID OS version 6.4.0 Stable Release Available

    I had same issue and turned out to be Safari VNC didnot work. Used chrome from a mac and VNC worked like a champ.
  2. So - issue seem to be with Safari and not ebing able to see the VNC console ! tried Chrome and it display fine now. Strange !
  3. That is correct - still not working even after those changes. I also tried to do a fresh install as per latest video using HighSiera, and getting same issue as type of error as soon as start the VM - 2018-01-14 19:12:25.974+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: DataSvr LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=HighSierra,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-HighSierra/master-key.aes -machine pc-q35-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/a7ba6695-e230-2eef-5c1d-c8f4082bd62b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 32768 -realtime mlock=off -smp 3,sockets=1,cores=3,threads=1 -uuid a7ba6695-e230-2eef-5c1d-c8f4082bd62b -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-HighSierra/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device pcie-root-port,port=0x10,chassis=,mac=52:54:00:64:91:f7,bus=pci.2,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-HighSierra/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 -usb -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -smbios type=2 -cpu Penryn,vendor=GenuineIntel,kvm=on,+invtsc,vmware-cpuid-freq=on, -msg timestamp=on 2018-01-14 19:12:25.974+0000: Domain id=3 is tainted: high-privileges 2018-01-14 19:12:25.974+0000: Domain id=3 is tainted: custom-argv 2018-01-14 19:12:25.974+0000: Domain id=3 is tainted: host-cpu 2018-01-14T19:12:26.015821Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0) Will do more digging perhaps on QEMU . Seems odd.
  4. Unfortunately it gets stuck there. I have updated the pc-q35-2.7 to the same as per the latest video ( <type arch='x86_64' machine='pc-q35-2.10'>hvm</type> ). and also have chnaged all of the <qemu:commandline> and <qemu:arg ... area to again be same as the latest video instructions. Still no dice and all the reading have not yielded nay clue. Will sit tight as would think some other upgrading will face same issue soon. Thanks
  5. I just updated from UNRAID to 6.4 from 6.3.4. Ahd OSX running fine (10.12) but getting now the following error - 2018-01-13 14:21:09.999+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: DataSvr 2018-01-13 14:21:09.999+0000: Domain id=1 is tainted: high-privileges 2018-01-13 14:21:09.999+0000: Domain id=1 is tainted: custom-argv My XML config is as follows - <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Sierra</name> <uuid>b7d74bb4-4562-a693-2e77-08499282d392</uuid> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>32913408</memory> <currentMemory unit='KiB'>32913408</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b7d74bb4-4562-a693-2e77-08499282d392_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S21NNXBGA18817M'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WD20NPVX-00EA4T0_WD-WXK1EC4AMS7U'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='none'/> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=DELETED!!!'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> ------------ Stumped and would appreciate any hints / pointers . regards
  6. unRAID OS version 6.4.0 Stable Release Available

    upgraded from 6.3.5 to 6.4.0 Only issue seeing is VM (OSx) wont start and get following error on the VM log - 2018-01-13 14:21:09.999+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: DataSvr 2018-01-13 14:21:09.999+0000: Domain id=1 is tainted: high-privileges 2018-01-13 14:21:09.999+0000: Domain id=1 is tainted: custom-argv ------
  7. Thanks for all your work. These are life savers !
  8. Well, I erroneously did the upgrade and now get kernel panics as start the OSX. Message around DSMOS: SMC read error K0: ...." Any tip or guidance on how to correct ? Thanks in advance.
  9. I just realized after running for a solid week - that the clock drifts and the time get out of sync badly ! After a day running see more than an hour off. I noted different setting on the XML folks using for the clock tag but they don't seem to make any difference. Searching the WWW see some folks refer to this issue, but cant find any fix Any though or ideas ? Thanks, Gus
  10. yes download and unzip this one. its the newest 3974 but patched for qemu.Dont use the offical one its not good on qemu. Then just install package on the vm. https://www.dropbox.com/s/d47kj8ng2j8ma14/Clover_v2.3k_r3974patched.pkg.zip?dl=0 So just so don't screw anything - 1. Download the enclosed file referenced above inside the VM to be updated 2. Execute file Clover_v2.3k_r3974.pkg ------------ Ask as so many other files and config unsure if anything else needed to be tweaked. Thanks for all these BTW. they are very useful !!!
  11. For those that used your old guide, any change to post how to upgrade Clover to latest ? I think very simple but would hate to screw something up.
  12. [Support] Watcher (beta app)

    There is also a group in reddit too for the app - https://www.reddit.com/r/watcher/
  13. Well just tried it - and all set with the new resolution. I am new to OVMF and KVM - but really liking what it brings to the hankintosh side of things. Thanks for these guides.
  14. gridrunner, works like a champ !!!!! Instead of migrating what i ended up doing was starting fresh. So used a new drive, used 'diskutil list' to ensure that could get the drive id. Then followed all of the steps on the guide - replaced the drive area with the instructions you noted above - and all working like a champ. Only suggestion to the guide is should note on format of the USB, to use GUID Partition and most master boot record. for some reason I missed this and had to redo later THE ONLY thing that have tried to do with no luck is, increase the size of the virtual screen. I do not have a graphics card to pass along (VGA), so just enabled screen sharing to connect. However, shows as 800x600 resolution. I used clover configurator to change on the GUI section, and when restart on the console view it shows garbled but kind off can see it going. On the screen sharing still just see as 800x600 though. Will try some other things and of works will post update. All else working fine. Will do some stress testing but love fact can take drive out, change EFI config (or use a boot one on another system) and will be up and running. This is really Really cool !
  15. Thank you for this guide !!!! I already have a drive with OSX El Capitan and clover installed working on a physical computer. Can I use this guide and use under UNRAID? Any suggestion how to go about it ? Thanks again - greta stuff

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.