Hoping someone out there is still running an original config like myself, from the pre-6.x days.

 

I never did setup unraid as a vm, but I did do an Arch/Xen setup and things were great once it got going.  I was totally satisfied with everything until a few weeks ago.

 

I did an update on my dom0 which brought the latest xen and linux kernel.  However, once I rebooted all I get is a black screen.  I was in talks with grumpy, but we were not able to solve anything.  I also went to the Arch forum where nobody like to talk to me.  In the end, I went to debian, just to get things up and running again, but since then, I have been wanting to go back to Arch.  I have tried to install it in other places with similar results.

 

So, really, the purpose of this post is to just see if anyone else has 3.15 and 4.4.0-3+ installed and running.  If you do, I am curious if something extra needed to be done this time around to make it work.

 

I tried using downgrader, to go back to kernel 3.13 and such, but it made no difference.  Any help is appreciated.

Hoping someone out there is still running an original config like myself, from the pre-6.x days.

 

I never did setup unraid as a vm, but I did do an Arch/Xen setup and things were great once it got going.  I was totally satisfied with everything until a few weeks ago.

 

I did an update on my dom0 which brought the latest xen and linux kernel.  However, once I rebooted all I get is a black screen.  I was in talks with grumpy, but we were not able to solve anything.  I also went to the Arch forum where nobody like to talk to me.  In the end, I went to debian, just to get things up and running again, but since then, I have been wanting to go back to Arch.  I have tried to install it in other places with similar results.

 

So, really, the purpose of this post is to just see if anyone else has 3.15 and 4.4.0-3+ installed and running.  If you do, I am curious if something extra needed to be done this time around to make it work.

 

I tried using downgrader, to go back to kernel 3.13 and such, but it made no difference.  Any help is appreciated.

 

I was running IronicBadger's ArchVM_3 until a few days ago. With IB having shut down his repository it just seemed like a pain in the ass to maintain. I took what I was running in the VM (sab, sb, plex, mariadb) and have moved them over to Docker with relative ease (mariadb was a bit of a pain, but I got threw it).

 

Unless  you are more Linux savvy than I (which isn't say much as I only know Linux because of my work on UnRAID), I would suggest you move over to Docker, provided it meets your requirements. It's a hell of a lot simpler, and more stable.

 

I didn't have the same issues you reported (I hadn't updated in maybe 2 weeks), but I started having problems where the VM would lose connectivity. It still had it's IP address, but couldn't ping anything on the network. If I tried stopping the VM and restarting it then I'd either end up with the same issue, or the VM would fail to start because memory had not been properly released. The IP issue was intermittent, and would just start magically working again for a bit, then die. Since all my TVs were using mariadb on this VM it became a huge problem which is what caused me to finally bite the bullet and give up on the VM.

 

I would like to stay with arch and Xen if at all possible,  thank you

 

Sent from my XT1060 using Tapatalk

 

 

I was running IronicBadger's ArchVM_3 until a few days ago. With IB having shut down his repository it just seemed like a pain in the ass to maintain. I took what I was running in the VM (sab, sb, plex, mariadb) and have moved them over to Docker with relative ease (mariadb was a bit of a pain, but I got threw it).

 

Unless  you are more Linux savvy than I (which isn't say much as I only know Linux because of my work on UnRAID), I would suggest you move over to Docker, provided it meets your requirements. It's a hell of a lot simpler, and more stable.

 

I didn't have the same issues you reported (I hadn't updated in maybe 2 weeks), but I started having problems where the VM would lose connectivity. It still had it's IP address, but couldn't ping anything on the network. If I tried stopping the VM and restarting it then I'd either end up with the same issue, or the VM would fail to start because memory had not been properly released. The IP issue was intermittent, and would just start magically working again for a bit, then die. Since all my TVs were using mariadb on this VM it became a huge problem which is what caused me to finally bite the bullet and give up on the VM.

 

Just an FYI, if you liked arch, it is not hard to maintain.  The only thing you needed to know now that IB has stepped back is you should install yaourt which will allow you to install packages from the AUR without waiting for IB to add it to his own repo.  In fact I removed IB's repo once I learned about yaourt.  Now I can self-update things like Plex and you could do sickbeard, etc the same way.

 

[shrug] FWIW

I was running IronicBadger's ArchVM_3 until a few days ago. With IB having shut down his repository it just seemed like a pain in the ass to maintain. I took what I was running in the VM (sab, sb, plex, mariadb) and have moved them over to Docker with relative ease (mariadb was a bit of a pain, but I got threw it).

 

Unless  you are more Linux savvy than I (which isn't say much as I only know Linux because of my work on UnRAID), I would suggest you move over to Docker, provided it meets your requirements. It's a hell of a lot simpler, and more stable.

 

I didn't have the same issues you reported (I hadn't updated in maybe 2 weeks), but I started having problems where the VM would lose connectivity. It still had it's IP address, but couldn't ping anything on the network. If I tried stopping the VM and restarting it then I'd either end up with the same issue, or the VM would fail to start because memory had not been properly released. The IP issue was intermittent, and would just start magically working again for a bit, then die. Since all my TVs were using mariadb on this VM it became a huge problem which is what caused me to finally bite the bullet and give up on the VM.

 

Just an FYI, if you liked arch, it is not hard to maintain.  The only thing you needed to know now that IB has stepped back is you should install yaourt which will allow you to install packages from the AUR without waiting for IB to add it to his own repo.  In fact I removed IB's repo once I learned about yaourt.  Now I can self-update things like Plex and you could do sickbeard, etc the same way.

 

[shrug] FWIW

 

Thanks for the suggestion, but I've ported everything over to Docker, which I kind of prefer anyways. As I mentioned, the Arch VM would sort of fall off the network periodically, then come back, and with it holding my DB for XBMC clients it fubared the house when it happened. It's all been good since Docker, and at worst now I just have to restart a container.

I was running IronicBadger's ArchVM_3 until a few days ago. With IB having shut down his repository it just seemed like a pain in the ass to maintain. I took what I was running in the VM (sab, sb, plex, mariadb) and have moved them over to Docker with relative ease (mariadb was a bit of a pain, but I got threw it).

 

Unless  you are more Linux savvy than I (which isn't say much as I only know Linux because of my work on UnRAID), I would suggest you move over to Docker, provided it meets your requirements. It's a hell of a lot simpler, and more stable.

 

I didn't have the same issues you reported (I hadn't updated in maybe 2 weeks), but I started having problems where the VM would lose connectivity. It still had it's IP address, but couldn't ping anything on the network. If I tried stopping the VM and restarting it then I'd either end up with the same issue, or the VM would fail to start because memory had not been properly released. The IP issue was intermittent, and would just start magically working again for a bit, then die. Since all my TVs were using mariadb on this VM it became a huge problem which is what caused me to finally bite the bullet and give up on the VM.

 

Just an FYI, if you liked arch, it is not hard to maintain.  The only thing you needed to know now that IB has stepped back is you should install yaourt which will allow you to install packages from the AUR without waiting for IB to add it to his own repo.  In fact I removed IB's repo once I learned about yaourt.  Now I can self-update things like Plex and you could do sickbeard, etc the same way.

 

[shrug] FWIW

 

Jumper,  are you on 3.15 and 4.4.0-6?

 

As mentioned,  I did use yaourt to go from -3 to -6, but the same crash/black screen is there with both. Makes no sense unless I am screwing up a configuration.

Hmmm I get the feeling you are talking about unraid as a domU?  if so, then I'm not the person to give advice.  I'm running plain jane unraid 6.0b5a (with xen 4.3 ... I wouldn't know how to update that to 4.4) as Dom0 and IB's archVM as a domU.  Now, that domU is indeed running 3.15.5.

no, this is completely outside of unraid.

 

I had an Arch dom0 with xen and an arch domu, no unraid.

 

I did an upgrade and the dom0 broke.  I was just trying to see if anyone had this configuration as well.  Things are fine with debian, but the xen is older and the networking is more confusing, so I want to get back to arch, but can't since it doesnt work any more.

 

I am currently planning to test out ubuntu 14.04 as it seems to use xen 4.4 so if arch doesnt get fixed, that is where I will end up.

I just did a fresh install of Arch and installed the latest Xen 4.4-6.

 

No problems on my end.

 

Either new Arch / Xen doesnt like your hardware or its how you setup Arch or Xen.

I just did a fresh install of Arch and installed the latest Xen 4.4-6.

 

No problems on my end.

 

Either new Arch / Xen doesnt like your hardware or its how you setup Arch or Xen.

 

HAHA, funny thing.  I was coming here to post that I installed last night/today to new hardware, rebooted things came up.  Time to break things tonight and install to my main rig again to see if I have the same result.  I will be sure to report those findings, but I do know that linux 3.15.5 is newer than the last time I went through it all...stay tuned.

 

edit:

Well, small note.  I am not concerned as I had the issue with my normal system too, but surely there is a fix, I just don't know what it is.  For whatever reason when the xen kernel boots, the screen goes out of range.  The system itself is fine in the background and putty works fine, but I lose the console.  I saw this before too but never thought much of it as I usually don't need the console since the system is in the basement and I never access it unless something is broken.  However, I thought it is still a good idea to ask while we talking about my system and the troubles I have had with it.

Well, it would seem that my/the issue has to do with the LVM2 hook.  I did not bother to stick around long enough to confirm, but it would seem so.

 

On my originally deployed Xen/Arch Dom0, I used an LVM volume for root and a standard Linux (83) one for boot because grub does not support LVM2.  For the longest time, life was good, but then, one day upon upgrade things went to hell and never booted again.

 

The switch to Debian was OK, but I never did get the network bridge to function correctly and because of this I was going to switch from it too.  I was thinking Ubuntu and fedora as my next test, but before that, I tried Arch on another system one more time.  I did the simplest config I could, single volume, no LVM, just a hard drive and Arch and things worked, I installed xen and everything was fine.  I then did it again to a different hard drive, this time partitioning it to have a 30GB volume.  Again, Arch installed, then xen and things were good.

 

Finally, I moved the drive to my regular system, booted, system failed to start, booted the iso, executed mkinitcpio - linux, rebooted and at last, I was back to my original system with xen loaded.  I quickly added one of my configs and booted the VM.  However, upon boot, the system didnt seem to want to start.  It acted all flaky and appeared as though it was throwing some sort of disk error.  As a result, I thought it was because the vm was using and LV to boot from and the LVM2 hook was not in my dom0 mkinit.cfg so I added it, updated and rebooted.  The system never came back. 

 

I booted back into fallback mode, removed the hook, updated, rebooted and the system was fine.  This time when starting the vm it started fine and everything appears OK with it, but there is no telling why it failed the first time around.  I am not as concerned with that as I am with the LVM2 hook.  It was late, so I did not crash the car again, but the plan will be to add the hook back, update and reboot to see if the results are the same.  I will then proceed to reboot a few more times before removing the hook to make sure it really is stuck.  This should then confirm the source of the issue.