billytheczeh

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About billytheczeh

  • Rank
    Newbie
  1. I'm trying to use gnoboot with Xen (not Xenserver) on Debian, without any result, kernel is booting, but no disk is found. How do you do on Ubuntu ? Do you have a cfg config file ? Thanks for your help. That's what I need as well. I haven't been able to get anything to boot so far! Problem with disks in latest gnoBoot comes from using pvrit drivers for disks and nics, however latest gnoBoot synoboot is not patched for using /dev/xvda instaed of /dev/sda... at least that is what i think. (gnoBoot solved it once, but then he moved to new upstream kernel.. and this feature was gone
  2. Hi there, did you succesfully installed DSM 5.0 build 4495 ?
  3. Hi, I was previously trying to run gnoBoot on XenServer. Any chance you could add Xen virt drivers in future build? Currently nanoboot cant find NICs and HDDs.. http://wiki.xenproject.org/wiki/Mainlin ... mU_Support There might be another issue, virtualized HDD will be /dev/xvda.. /dev/xvdb .. etc.. instead of /dev/sda ... If needed I can provide testing, etc.. Thank you
  4. okey (misunderstood your gdisk files..), anyway I just downloaded last one just now: uname -a Linux DiskStation 3.2.40 #1 SMP Sat Mat 15 13:16:17 CST 2014 x86_64 GNU/Linux synology_bromlow_3612xs DSM 5.0 4458 sucesfully installed on XenServer 6.2SP1 using gnoboot-alpha10.3-zImage ! Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB RAM Using HVM (Other install media, during Xen VM creation). Disabled viridian `xe vm-param-set uuid=... platform:viridian=false` (Makes sure virt-what coretly recognizes Xen) gnoBoot image installed using `dd if=gnoboot-a
  5. Update for Xen Paravirtualization: Try it again using 10.5, added more boot-up messages to trace your problem. Just updated to 10.5 here is console output with debug option: (Still stops during boot) (This are my kernel command options: "root=/dev/md0 console=hvc0 sn=B3JN00... debug" ) [ 0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.2.0) #8 SMP Sat Apr 5 10:56:54 CST 2014 [ 0.000000] Command line: root=/dev/md0 console=hvc0 sn=B3JN00... debug [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD
  6. bump , anything new? Or any idea what shoul I try?
  7. Update for Xen Paravirtualization Hi 10.4-vfat is recognized by XenServer 6.2SP1 in PV mode (pygrub) as bootable however during booting it get stuck after "Re-scanning disks". (Tried 10.4-ext2 but no luck) I am booting with these arguments: "root=/dev/md0 console=hvc0 sn=... debug=true", perhaps root=?? is wrong? Any idea what to try next? Console output with debug=true [ 0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.2.0) #6 SMP Sat Mar 22 14:41:23 CST 2014 [ 0.000000] Command line: root=/dev/md0 console=hvc0 sn=... debug=true [ 0.000000] K
  8. Update on XenServer Paravirtualization I tried to run gnoboot using XenServer PV (pygrub), however getting error in Xen console when starting VM: Internal error: xenopsd internal error: XenguestHelper.Xenctrl_dom_linux_build_failure(2, " panic: xc_dom_core.c:616: xc_dom_find_loader: no loader\\\"") Which i found is result of XenServer having pygrub compiled WITHOUT LZMA/XS support for kernel compression (which holds for last XenServer release http://discussions.citrix.com/topic/330 ... z-support/) gnoBoot what compression are you using? (I could not find it using `file zImag
  9. Lol, you're using the wrong zImage. That's five-zero kernel which doesn't have the XEN disk patch. okey (misunderstood your gdisk files..), anyway I just downloaded last one just now: uname -a Linux DiskStation 3.2.40 #1 SMP Sat Mat 15 13:16:17 CST 2014 x86_64 GNU/Linux synology_bromlow_3612xs DSM 5.0 4458 sucesfully installed on XenServer 6.2SP1 using gnoboot-alpha10.3-zImage ! Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB RAM Using HVM (Other install media, during Xen VM creation). Disabled viridian `xe vm-param-set uuid=... platform:viri
  10. Update for v5 on XenServer Problem with hard disks persists. During installation of DSM -> Error 38. Tried 4458, 3827, booting with/without gnoboot_me... Still the same cat /proc/partitions major minor #blocks name 202 16 8388608 xvdb 202 17 2490240 xvdb1 202 18 2097152 xvdb2 202 0 32768 xvda 202 1 32098 xvda1 dmesg [ 0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.7.3 20130102 (prerelease) (crosstool-NG 1.18.0) ) #5 SMP Mon Mar 10 20:37:38 CST 2014 [ 0.000000] Command line: gnoboot_me=5.0-4458
  11. I booted with debug console=tty0, hope it worked as desired dmesg [ 0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.2.0) #8 SMP Sun Mar 9 14:04:20 CST 2014 [ 0.000000] Command line: debug console=tty0 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000
  12. I just tried 10.2, and Syno Assistant sucessfully installs DSM (disks recognized), however after final reboot, on :5000 there is still Syno Web Assistant with message "configuration lost" , am I doing anything wrong? (I set custom SN, tried booting/installing with menu_alpha.lst and menu_me.lst using DSM43. In last effort I tried even DSM5, however Syno Assistant failed with message I should install DSM43). If I will make at least this work I will give paravirtualization another shot... it is quite interesting by it self and at least I will learn something new Thanks for help
  13. Update for XenServer Paravirtualization: I tried last gnoboot build (Wed Mar 5 18:05:38 CST) -> problem with xen disks presists, eg. I can't install DSM using Syno Assistant (error 38). I am attaching two virtual disks - first 32MB, second 8GB, using 512MB RAM, and 2 CPUs, viridan disabled (HyperV win8 support). Here is "cat /proc/partitions" major minor #blocks name 202 16 8388608 sdxb 202 0 32768 sdxa 202 1 32098 sdxa1 Here is "dmesg" [ 0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.2.0) #1 SMP Wed Mar 5 18:05:38
  14. Follow up for Xen Paravirtualization: uname -a Linux DiskStation 3.2.40 #2 SMP Fri Feb 28 08:52:14 CST 2014 x86_64 GNU/Linux synology_bromlow_3612xs According to this article http://support.citrix.com/article/CTX121875 , for sucessful paravirt booting it is recomended to do something like this: initrd --omit-scsi-modules --with=xennet --with=xenblk --preload=xenblk initrd-$(uname -r)xen-no-scsi.img $(uname -r)xen which is I guess not an option here.. (disabling scsi modules), anyway booting is then realized by pygrub and kernel is executed with additional param
  15. Nope, but there's a workaround which is a bit ugly or modify the driver but I'm not sure about its side effect. @billy Are you running nested Xen on HyperV? Can you login to console and try running virt-what? No, I am using standard XenServer 6.2 on hardware (Intel Xeon 5130). virt-what returns hyperv... :/ (same as in dmesg...) I digged little bit around and: "dmidecode -s system-manufacturer" reports "Xen" "virt-what-cpuid-helper" reports "Microsoft Hv" "cat /sys/hypervisor/type" reports "xen" I found this mail https://www.redhat.com/archives/virt-to ... 00126.html ,