Announcement

Collapse
No announcement yet.

XenServer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    XenServer

    FUCK STICKS! XenServer and XCP is pissing me off A LOT. I cannot seem to get that mother fucker to install on my computer at fucking all. I just want to run a bare metal hyper visor that is free but fuck is that really too much to god damn ask for! Fucking thing doesn't install. I have tried multiple ISOs burned on multiple different burners and every fucking time their is some sort of error either a recursive error or a corrupt .tar file never the same fucking file mind you. WTF!?

    I7 supports VMs check.
    Pretty damn sure the mother board does as well.
    8 gigs of ram and its own god damn 400+GB hd so fuck?

    FUCK FUCK FUCK FUCK FUCKIDY FUCK FUCK!!

    More venting than anything else but hey if you have any good advice on the matter I will happily take it.

    #2
    Have you tried dd'ing the iso to a flash drive? What are you using as a host *nix OS? Have you set the BIOS to allow virtualization?

    Comment


      #3
      Originally posted by wetware View Post
      Have you tried dd'ing the iso to a flash drive? What are you using as a host *nix OS? Have you set the BIOS to allow virtualization?
      Yeah I tried the flash drive no luck.
      I am not 100% sure which host I am going to use quite yet, I am heavily leaning toward Cent OS.

      The only place vitalization is mentioned in the BIOS is under chip and its turned on there.

      Its just really frustrating cause it randomly goes into a tracedump sometimes right out the gate, sometimes right after installing sometimes in the middle of installing.
      Some times the tracedump itself will completely freeze up other times after some time will give a recessive error and says it needs to be rebooted.
      Then sometimes it doesn't tracedump but instead says random file is damaged and system needs to be rebooted. Never the same .tar file ever.

      Comment


        #4
        Opp about the host I am using what ever Citrix puts on XenServer which is debian I believe.
        Yeah I am that frustrated where I am making stupid mistakes.
        Basically this is the process I am doing other then I am using 6.2 XenServer and not putting it in virtual box.


        It never makes it to the reboot portion
        I also do not get a hardware doesn't support it error so I think the bios is good.

        Comment


          #5
          That is weird. I've only played with Xen a little bit and then as part of an Arch install. I've been considering reinstalling it in order to play some games with a graphics passthrough. I think in most cases Xen needs a preexisting *nix OS, but XenServer has its own, right?

          What motherboard are you using and where are you getting your ISOs from?

          Comment


            #6
            Originally posted by wetware View Post
            That is weird. I've only played with Xen a little bit and then as part of an Arch install. I've been considering reinstalling it in order to play some games with a graphics passthrough. I think in most cases Xen needs a preexisting *nix OS, but XenServer has its own, right?

            What motherboard are you using and where are you getting your ISOs from?
            Yeah XenServer has its own pretty thin one.
            So I am getting them from
            https://www.citrix.com/downloads/xenserver.html
            Interestingly enough I just got a blue screen on windows 7 with a supercilious familiar dump memory address. So I am going to try and pull a few sticks out hope its one of the ones with the right memory address and try and re-install.
            I am not sure which mother board it is aside from being a MSI when I yank the memory maybe I can find something that says what it is. Didn't see it listed in bios.

            Comment


              #7
              Well alrighty then, I guess I had an errant stick of ram. Well fuck I am just happy it works now.

              Comment


                #8
                For future reference when running into weird VM trouble, always try the same virtual setup on different host hardware.

                9 times out of 10, it will be a physical hardware issue, not a VM/software problem. Either a component that doesn't play nicely with virtualization, or as you discovered, a faulty one.

                Comment


                  #9
                  Originally posted by W. Rabbit View Post
                  For future reference when running into weird VM trouble, always try the same virtual setup on different host hardware.

                  9 times out of 10, it will be a physical hardware issue, not a VM/software problem. Either a component that doesn't play nicely with virtualization, or as you discovered, a faulty one.
                  yeah, you pretty much want at least a pair of hypervisors, with enough headroom to host all crucial services on only one of them. unfortunately when IT budgets are being made, a lot of the people who sign the checks don't see things that way.

                  Comment

                  Collapse

                  Edit this module to specify a template to display.

                  Working...
                  X