Ovms 9.2-3 community.vmdk install/config issue

Having difficulties when installing the system? Your system runs slowly and requires some tweaking? You can get help here.
Post Reply

Topic author
anamika
Newbie
Posts: 3
Joined: Sat Jan 18, 2025 7:03 am
Reputation: 0
Status: Offline

Ovms 9.2-3 community.vmdk install/config issue

Post by anamika » Sat Jan 18, 2025 9:38 am

Folks
On Jan 16th, I received the download link for Ovms 9.2-3 hobbyist release.
On attempting to configure a virtual disk for the new VM using community.vmdk, I encountered "unable to find the file" message. On inspecting the community.vmdk in the 9.2-3 download, it was found that there is a problem.

The filename for community-flat.vmdk has a suffix "X86_V923-" which renders the that file to become inaccessible due to the improper filename.

To correct this issue, open the community.vmdk file in a text editor and remove the prefix "X86_V923-" so that the filename is now just "community-flat.vmdk". Save and it should fix the issue.

Thanks


sms
Senior Member
Posts: 525
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by sms » Sat Jan 18, 2025 3:23 pm

Code: Select all

> [...] remove the prefix "X86_V923-" [...]

   Or, add it elsewhere:

      https://forum.vmssoftware.com/viewtopic.php?f=39&p=23248


   A little more organization in the packaging of this stuff might be
nice.  I doubt that a prefix of "X86_V923-" is ideal, but having the
same name (community[-flat].vmdk) for every version might be worse. 
Including something resembling a (sortable) date might be helpful.


gorazd
Newbie
Posts: 4
Joined: Sat Jan 18, 2025 3:56 pm
Reputation: 0
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by gorazd » Sat Jan 18, 2025 4:07 pm

Use the same solution when file was not found.

Best, Gorazd


Topic author
anamika
Newbie
Posts: 3
Joined: Sat Jan 18, 2025 7:03 am
Reputation: 0
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by anamika » Sun Jan 19, 2025 9:50 am

I was also wondering as to how this build passed QA/testing ?

Thx

User avatar

mister.moderator
Site Admin
Active Contributor
Posts: 49
Joined: Thu Apr 27, 2023 11:14 am
Reputation: 0
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by mister.moderator » Mon Jan 20, 2025 9:04 am

We are aware of the issue and are working on a solution.
VMS Forum Moderator
VMS Forum Administrator


malmberg
Contributor
Posts: 22
Joined: Tue Apr 16, 2024 7:55 pm
Reputation: 0
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by malmberg » Mon Jan 20, 2025 10:42 pm

I got past that on linux/kvm by creating a symlink to the -flat file. Renaming the -flat file to the one that it wants may also work for virtual box.

User avatar

imiller
Master
Posts: 181
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by imiller » Thu Jan 23, 2025 6:38 am

I note that the volume name of the community disk is X86_SYS which is different to the previous X86SYS and wonder why.
I agree that including a version or date in the vmdk filename would be a good idea.
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].


dgordon
VSI Expert
Valued Contributor
Posts: 72
Joined: Tue May 09, 2023 7:57 am
Reputation: 1
Status: Offline

Re: Ovms 9.2-3 community.vmdk install/config issue

Post by dgordon » Thu Jan 23, 2025 8:51 am

the volume name of the community disk is X86_SYS which is different to the previous
I have nothing to do with creating the community disk. Given that cluster-common system disks are not yet available on x86, I make it a practice to label my system volume NODE_VERSION (FOO_V923 for example) so that all the system disks in my cluster can be mounted cluster-wide which simplifies managing a multi-system-disk cluster just a tiny bit. Note that I upgrade my "current build" disk on the order of once a month or more, and that most of my VMs have multiple system disks containing versions from V9.2-1 through V9.2-3 as well for testing purposes.

I name "user" disks the same way, Same reason.

Of course, to put a new volume label on a system disk requires that you can boot off of something else. At a minimum, you could clone your system disk (BACKUP/IMAGE/IGNORE=INTERLOCK of the running system disk is probably good enough in this case.) and then boot the clone so you can relabel the original system disk. Having a few spare virtual devices never hurts.
Executive Vice President of InfoServer Engineering at VSI.

Post Reply