To Chandrakant cannot find this file. here is screen shot :

I could not copy and paste or attach it here so I will email it.

To Chandrakant,

I will email you screenshot but it says no such file or directory : xorg.o.log

To Chandrakant,

I was about to go into vm and reun the commands you postedthat i previously ran but they had typos swanted to correct that.

However when I sat down to do that I had a notification that I had updates Chakra- so I ran the pacman command (Package manager for Chakra ) to update and then I rebooted and then when I tried to open vm for aryalinux there was an error : the installed support driver does not match the version of the user. I cannot post the screenshot because I then closed out virtual box and since my ssd only had a few mb of space - I did research and decided instead of deleting files in tmp and var cache and var logs- I decided to move the logs from the ssd to the hdd. This then freed up 11.9 GB on the ssd. I thought all was well after a reboot except could not even open virtualbox because got error that can't find COM object.

So I decided to move the virtualbox files back to the ssd but even though i had created a folder on the hd to put all the moved files for some reason I could not find the virtualbox files. I will keep looking and if find them I will put them back on the ssd and then try to re run the commands to correct the typos so I can continue to try to fix the startx issue in arya linux with your help.

I do not know why that error occurs in Chakra. Maybe you should consult the chakra team for that. I am still unclear about the partitions and setup you have on your system. Please try and let me know if there is anything I can do.

To Chandracant,

Are you referring to both errors or only the error about the mismatch driver ?

The 2 errors :

1. mismatched driver- When I originally installed Virtualbox a couple of weeks ago it was version 5.0.24 When I had vms running , when first open it would always say that there is another update available ver 5.0.26 and it asked if want to update- I always declined because vms were running fine and wanted to not download new version and have to create the vms again- I just wanted to concentrate on geting aryalinux built. ( in hindsight maybe I should have updated virtual box )

Yesterday when I posted about updating Chakra- I saw that it did update virtualbox. Today I checked in Chakra Octopi ( GUI frontend for pacman package manager ) to see which version of virtualbox I had and I thought it would be ver 5.0.26 but instead it said 5.1.7 I then went to virtualbox website and that version was just released on 7/21/16 ( I installed from Chakra repositories on 7/26/16 so I knew that that version is a little behind the cutting edge version but then when I updated yesterday as I mentioned it is the current version 5.1.7.

So why is there a mismatch regarding driver. Does the error message mean that the driver installed in virtualbox is now newer than the driver installed in the vm created before the update ? Do I need to somehow update the vm from inside the vm ? ( How to do that since now because of second error about not finding COM object I cannot even get to the vm.

2. COM error- Could this be because yesterday I moved var/cache var/logs from SSD to HD ? ( maybe something that was needed got moved from ssd to hd that should have stayed in ssd ) A couple of weeks ago because of not enough space for the vms on the ssd I had moved them to HD and changed the download options from download folder in /home/ed on ssd to /edwardddowlingiv/downloads on the hd and all vms were working and every thing I was doing in aryalinux vm using aryalinux ISO builder tool was all being done on HD not the ssd so I am not sure what the problem is.

I will also post in Chakra forums to see if it has to do with the chakra update.

My set up is on ssd : 2 partitions 1. 2GB swap ( /dev/sda1 ) and 2. root remainder of the 54 GB useable space on the 60 GB ssd (/dev/sda2

I have a separate 1 TB HD for /home ( entire disk for home no partitions )( /dev/sdb1 )

In the aryalinux vm the virtual HD setup is : 3 partitions

1./dev/sda1 root ( 20 GB )
2./dev/sda2 swap ( 10 GB )
3./dev/sda3 home ( 20 GB )

If you need further information ( I will post Chakra's response ) let me know

If there is anything you can figure out what to do let me know and i will try it ( I am even willing to uninstall virtualbox ( even though that means I will lose all the vms ( 4 ) I have ) reinstall it and start all over the long process of aryalinuux build process.

Thanks for your help so far. I have learned a lot even though not succesful in getting aryalinux set up yet.

To Chandrakant,

This is response from my post in Chakra forums and my reply :

21:45:47
edddowlingiv
Member
From: Port Jefferson, NY
Registered: 2011-10-22
Posts: 374
Email

tetris4 wrote:

Hello,

Your issue seems related to this:
https://chakralinux.org/bugtracker/inde … sk_id=1654
There was a change in the way virtualbox is packaged in the latest version, so you might want to try reinstalling virtualbox-host-dkms. What is the output of pacman -Qs virtualbox?
Btw, don't you keep your .vdi files saved? If yes, you should be easily able to restore or move them to any virtualbox installation on any system.

To Tetris4,

Thanks for your response.

In response to your post I will re install vrtualbox-host-dkms ( do I do that by usual pacman command pacman -S virtualbox-host-dkms or just state virtualbox and let it install the other items ?( I saw in Octopi there are a lot of packages listed separately from virtualbox - install them separately or just with virtual box or virtualbox-host-dkms ?

2. I did save the .vdi files for all my vms and would gladly try to move them back but I can not access any of the vms ( I think because of the error about COM not being found but maybe some other reason )
here is the output of pacman -Qs virtualbox :

[ed@edwardddowlingiv-chpc ~]$ sudo pacman -Qs virtualbox [sudo] password for ed: local/virtualbox 5.1.2-7 Powerful x86 virtualization for enterprise as well as home use local/virtualbox-host-dkms 5.1.2-7 VirtualBox Host kernel modules sources [ed@edwardddowlingiv-chpc ~]$

To Chandrakant,

Do you know if there is anyhing else I should do or just do what Chakra post by Tetris4 says.


here is the contents of the link to the bug that tetris provided ( this is exactlly the error message I get to the word )

FS#1654 - virtualbox return driver mismatch error launching virtual machines

Description:

virtualbox return driver mismatch error launching virtual machines

Additional information:
* virtualbox 5.1.2-7 (packages: virtualbox,virtualbox-ext-oracle,virtualbox-guest-dkms,virtualbox-host-dkms)
* Error messages:

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/sbin/vboxconfig'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.


Steps to reproduce:

Add testing repos
Open virtual box
Launch any virtualmachine (here tested Win7 and Win10)
* Rolling back to stable solve the issue


Actual result:
Popup windows with error

Expected result:
Virtual machine boots regularly
This task does not depend on any other tasks.

You need to get the AryaLinux VM up and running for me to give any suggestion because I need to know what's the error you're getting.

To Chandrakant,

See the additional content regarding the link tetris4 provided regarding the bug ( which is exactly word for word the error message I got said )

if you think I should try what tetris said to do i will and see if I can get a vm running again.

Thanks for your help.

I'm not able to access the link. It gives me a 404. Page not found. Anyways get the VM going and we can sort out the x-server issue once that's done

To Chakrakant,

You don't have to go to the link I edited post 21 by adding the contents of the link

Also i will try to get vm running should i do what tetris said ?

To Chandrakant,

I have been spending and continuing to spend many hours researcing, posting and trying to fix the problems created with updated version of virtualbox without success. I have also researched alternative virtualization software to virtualbox like qemu/kvm , xen and vmware workstation. The bug fix instructions in Chakra website does not work for me I tried several times. I keep geting following errors :

1. . /chakra/desktop/virtualbox/src/VirtualBox-5.1.2/src/VBox/Main/src-server/VirtualBoxImpl.cpp[550] (nsresult VirtualBox::init()). Result Code: NS_ERROR_FAILURE (0x80004005) Component: VirtualBoxWrap Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945} Callee: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

2. Error about mismatched driver.

To Chandrakant,

Yesterday I had decided to stop trying to get the problems in virtualbox resolved and instead I did a lot of research regarding alternatives to virtualbox and decided to go with qemu ( Chakra has it in their repositories ) and KVM. As you probablky are aware, kvm is a hypervisor type 1 ( not type 2 like virtualbox and vmware and others ) and according to the research since kvm is in the kernal itself the virtual machines are supposed to run faster and more natively than in virtualbox ( Most linux kernels have kvm inside their kernel. So when developers improve the kernel kvm virtualization improves too. I was not able to use the frontend aqemu to qemu/kvm either because I was not doing it correctly or some other reason. I found a very well written step by step tutorial on catchlinux that had screen shots and very easy to understand instructions for using the command line for qemu kvm. I tried to get aryalinux running but could not. Not because instructions were wrong or I did not follow them corectly but because of the statement buried near the end of the instructions that qemu/kvm can only use a live cd/dvd ( either physical or iso image ) and not a install builder disc or iso.
To make sure that a live dvd would work I used an iso of another distro and followed the tutorial command line instructions and it worked . Now i know if i have live dvd or iso I can and probably should use qemu/kvm instead of virtualbox. ( the internet has many articles and forum discussions that unless using a windows host or want to use a windows guest ( which qemu/kvm cannot do ) use qmeu/kvm.

Then i went back to virtualbox ( since can't use kvm unless live dvd or iso ) and tried to get the problems fixed but after spending many hours I was not able to.

However today when i started my Chakra sustem there were many updates and one of them wqas for all 7 packages of virtualbox updated from 5.2-7 to 5.4.1 and after the update virtualbox to my great surprise and satisfaction worked fine without any problems.

Therefore I started over again and created partitions using minitool and then booted to aryalinux iso to see if could get to it so I could run the builder scripts- i did get to it but did not start the scripts in 2016.04 because i went to the aryalinux website to get the builder instructions but then i saw it was not there only the 2016.08 was there. It appears to be a live dvd with a GUI installer instead of buider scripts.

On one hand that is good because it should be much easier and quicker than builder scripts. But on the other hand it is not good if you want the learning experience of the builder scripts to learn something about how LFS works without having to go through the even longer process of using the LFS books.

Perhaps what I will do is either try using 2016.08 as live dvd ( will it work if burn to a dvd or is it still only a GUI installer and not live bootable os and thus I need to install in virtualbox ) and if i like aryalinux ( I'm sure I will ) then either install it on hd or maybe install the 2016.04 version and run the builder scripts to have the learning experience ( I learned a lot over the weekend about virtualization )

Questions to you then are : 1. is 2016.08 a bootable live dvd or just a GUI installer disk ?

2. Do you think the learning experience is worth the time and effort of using the builder scripts ? ( I think it will be provided we can resolve the startx xfce issue )

3. Do you think the startx xfce issue is something that will be very difficult to resolve or not hat difficult. ?

4. Is the 2016.08 version much less stable because it is curtting/bleeding edge or is it fairly stable compared to 2016.04 ( If it is not that stabnle and if 2016.04 is more stable and if can resolve startx xfce issue then I would prefer to do that for the learning experience and for the stability.

Sorry this is so long and maybe I should have emailed you but then again maybe other people viewing this may have same questions and also may be interested to know ( if they did not already know ) about qemu/kvm alternative to virtualbox for linux hosts and linux guests .

Thanks in advance.

Hi,

Sorry for the delayed response. To answer your questions:

1) 2016.08 is both a Live system that can be boot into and you can run it without installing it. It contains most daily-use applications like browser, mail-reader, office suite, VLC etc. This same DVD is also the builder. It contains an updated set of build scripts and can be used to create a Linux from Scratch all. It also includes scripts to build bootable iso files out of the Linux that you end up creating. There is a small glitch however. In case you would like to run it inside VirtualBox, you would end up with no GUI. There is a problem in the ISO which is online right now. How did this problem crept into the release is a long story but to keep it brief, this ISO shipped without VESA graphics driver which is the driver that is used inside VBox to show GUI. The ISO however if burnt onto a DVD or written onto a pen drive(using dd command) would function well on the native system and of course since it would run in live mode, you need not worry installing and stuff. The point is if you really want to see it and test it, I would recommend you to try it on the system using pen-drive or DVD than trying it inside VirtualBox. I am planning to release another revision of this ISO which would have this and few other issued fixed. So you can wait for it(possibly another week) if you would only like to try inside VBox.

2) Ah. Now getting back to the problem at hand. I could really help in case you could help me with the Xorg.0.log file. Without it, the whole process would be like a shot in the dark. The problem can be either very trivial or it may be big or there may be more than one issues. So its kind of difficult to tell what needs to be done. To answer the point you made in 2) I would like to say the following. The thing with AryaLinux is that you have to build it all. Everything from the compiler to the last application that you can think of that you would like to use. This definitely takes a lot of time but once that is done, there is nothing much to it and you have a pretty stable system at your disposal. The process of building works like this: Every package before it gets installed checks if all its dependencies are satisfied in the system where it is being built and then only would it proceed with the process of compilation. The resulting system in my opinion is more stable than a system where an external program satisfies the dependencies for packages. Anyways that debatable but if this process is worth the time and then about learning that you take from all of it, well I would say though no matter how easy and lavish the whole process of building becomes, it definitely takes the time and since unlike LFS/BLFS you do not have to type or copy-paste commands, you would tend to learn less. So answering this question is difficult for me. I use AryaLinux in the system I have at office, at home, I am a Java Programmer so I work on things pretty heavy on memory like eclipse IDE and intellij and tomcat and mysql.. The list is longer. I also work on PHP, MySQL sometimes and then there is building Arya. I often build full fledged system two-three times every week. I never had an issue of stability and most things except few like QT and WebkitGTK, LLVM and Mesa build pretty fast. If you go past the inital hurdle, AryaLinux is fairly similar if not better than any other Linux out there. So time, yes that's needed but not like everyday, just till you get everything in place and learning, yes lesser compared to LFS/BLFS but definitely more than simple binary installable linuxes.

3) I do not think it would take time just that its difficult to troubleshoot without the logs.

4) 2016.08 is stable and works real neat. I can tell you because since the past three weeks I am working on this system and did not have a single misbehaving application or crash. It's bleeding edge means its less tried and tested than the stable version. That's all. If you wanna give it a shot, go ahead but then if you would like to try it on VBox first please wait till I do the revised release.

To Chandrakant,

Thanks for the very informative response. However in my previous post although I should have probably put as one of the questions at the end ( I put it in the body of the post ) I had wanted to ask about whether I should use the 2016.04 version and run the builder scripts for stability purposes ( I now know 2016.08 has been stable so far in the 3 weeks you have been using it ) and since I already partitioned a virtual hd inside virtualbox ( now that I have new version of virtualbox working ).
Question Am i less likely to have the startx issue now that I have the new version of virtualbox ( which had fixed the previous errors ) on the 2016.04 version of aryalinux? or is startx a problem with the 2016.04 build ? or s it more probably an issue with my Chakra system ?

Questions Would it be less likely to have the startx issue with the new 2016.08 issue of aryalinux ( if it is a Chakra problem that probably not )?

Question Besides the fact that if I used 2016.08 version I would have more bleeding edge software and thus possibly less stable than 2016.04, is there any other advantage to using the new 2016.08 version ( other than that there is a live dvd that can be burned to disc and used as installer and contains scripts to build iso of the system I create or is that the only advantage ? )

Your previous post did not affress 2016/04 version - Does the 2016.08 version fix any bugs ( if there were any )in the 2016.04 version ?

Thanks for your help in advance.

I could have missed on certain points probably considering the overall length of the post. Sorry about that. Anyways here it is:

Questions Would it be less likely to have the startx issue with the new 2016.08 issue of aryalinux ( if it is a Chakra problem that probably not )?
I cannot say till I know what actually caused the issue in 2016.04 in the first place. It may happen again. People have built XFCE inside VBox using 2016.04 all through till the end. So I cannot say what caused the issue and would it happen again whether it be the stable version or the bleeding edge version.

Why the bleeding edge and why the stable version?
Well to answer this I need to be a little technical here. The stable version builds packages using gcc5. This is a pretty old version of gcc and most packages compile without issues on gcc5. The bleeding edge ships with gcc6. Its newer no doubt there are packages that have yet not caught up with gcc6. Build would fail for these packages as their source code is not gcc6 compatible. Now its possible to have both the gcc versions in one system but building everything else selectively on either of these would become a major hurdle. This is the primary difference between the two. In essence if you want to build some package that has not been maintained for some time now or has not been written considering gcc6 then you would not be able to build it on the bleeding edge. Over time I guess most packages would do this and this issue would no longer exist.

Another reason why you might need bleeding edge is if you want to your desktop to be KDE or LXQt. Building KDE or LXQt does not work in the stable version because the state of the build-scripts(which depends on the BLFS book version from which they were built) is buggy. If you'd like to know my opinion, I would recommend you go for the stable release.

Your previous post did not affress 2016/04 version - Does the 2016.08 version fix any bugs ( if there were any )in the 2016.04 version ?
2016.08 is not a bug-fix release. Its just that a lot of packages are updated in 2016.08 and it comes with updated build scripts. Eventually I would be making a new release for 2016.04 as well with the updated packages and installer.