Ovms 9.2-3 community.vmdk install/config issue
Ovms 9.2-3 community.vmdk install/config issue
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
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
Re: Ovms 9.2-3 community.vmdk install/config issue
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.
Re: Ovms 9.2-3 community.vmdk install/config issue
Use the same solution when file was not found.
Best, Gorazd
Best, Gorazd
Re: Ovms 9.2-3 community.vmdk install/config issue
I was also wondering as to how this build passed QA/testing ?
Thx
Thx
-
- 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
We are aware of the issue and are working on a solution.
VMS Forum Moderator
VMS Forum Administrator
VMS Forum Administrator
Re: Ovms 9.2-3 community.vmdk install/config issue
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.
-
- 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
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.
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 ].
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].
-
- 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
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.the volume name of the community disk is X86_SYS which is different to the previous
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.