[SOLVED] Unable to edit vm settings on disk

[adhd]

Hi,

I can't edit vm settings "On Disk". I imported my virtual machines with "Import Virtual Machine Config File(s)" option to convirt. After I was succesfully imported virtual machines I tried to edit virtual machine settings. I tried to allocate more memory to virtual machine. I can increase memory only if I select "Change settings: In Memory".

But when I tried to allocate more memory permanently and selected "Change settings: On Disk", nothing happened! I can save settings and convirt say to me that everything goes just fine. But when I reboot virtual machine there is no any effect to its memory allocation. And there is no any changes on virtual machine config file which I imported. There is same situation when I try edit settings with "Edit Virtual Machine Config File" option.

So, am I missing something? Which location convirt try to save the edited config file?

Thanks for you help!

[jd_jedi]

ConVirt keeps the setting in the repository. (The one that u can view using "Edit VM config file")
When you start the VM, it makes a temp copy in /tmp and uses it to start the VM.
Check if the most recent /tmp file has the correct settings.

[adhd]

ConVirt keeps the setting in the repository. (The one that u can view using "Edit VM config file")
When you start the VM, it makes a temp copy in /tmp and uses it to start the VM.
Check if the most recent /tmp file has the correct settings.

Thanks, I got it to work. Only way to reload the settings "On Disk" seems to be shutdown and then start vm manually? It would be nice if there be option to reload settings automatically ie. convirt first shutdown and then automatically start the vm.

I also noticed that there is some problems the way how convirt handles storage setting when importing virtual machine config files.

My original config wich I imported to convirt:

Code: Select all

name = "tools"
uuid = "466181db-d591-46d0-99a8-0b5d59200e0b"
maxmem = 10240
memory = 4096
vcpus = 4
cpus = "4-7,12-15"
bootloader = "/usr/bin/pygrub"
bootloader_args = "-q"
extra = " sax2=1"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "destroy"
vfb = [ "type=vnc,vncunused=1" ]
disk = [ "file:/server/xen/images/tools/boot,xvda,w", "file:/server/xen/images/tools/server,xvdb,w", "file:/server/install-images/SLES-11-DVD-x86_64-GM-DVD1.iso,xvdc:cdrom,r" ]
vif = [ "mac=00:16:3e:ec:39:73,bridge=br0,script=vif-bridge,vifname=vif12.0", "mac=00:16:3e:6c:ee:73,bridge=br0,script=vif-bridge,vifname=vif12.1", "mac=00:16:3e:67:41:73,bridge=br1,script=vif-bridge,vifname=vif12.2" ]


Generated config by convirt (without any modifications by me)

Code: Select all

bootloader = '/usr/bin/pygrub'
vif = ['mac=00:16:3e:ec:39:73,bridge=br0,script=vif-bridge,vifname=vif12.0', 'mac=00:16:3e:6c:ee:73,bridge=br0,script=vif-bridge,vifname=vif12.1', 'mac=00:16:3e:67:41:73,bridge=br1,script=vif-bridge,vifname=vif12.2']
uuid = '466181db-d591-46d0-99a8-0b5d59200e0b'
extra = ' sax2=1'
on_reboot = 'restart'
maxmem = 10240
on_poweroff = 'destroy'
bootloader_args = '-q'
cpus = '4-7,12-15'
STORAGE_STATS = {'DISK_STATS': {'/server/xen/images/tools/server': {'DEV_TYPE': 'FILE', 'IS_LOCAL': True, 'DISK_SIZE': 4194304000, 'DISK_NAME': '/server/xen/images/tools/server', 'STORAGE_DISK_ID': None}, '/server/install-images/SLES-11-DVD-x86_64-GM-DVD1.iso': {'DEV_TYPE': 'FILE', 'IS_LOCAL': True, 'DISK_SIZE': 2882527232, 'DISK_NAME': '/server/install-images/SLES-11-DVD-x86_64-GM-DVD1.iso', 'STORAGE_DISK_ID': None}, '/server/xen/images/tools/boot': {'DEV_TYPE': 'FILE', 'IS_LOCAL': True, 'DISK_SIZE': 10737418240, 'DISK_NAME': '/server/xen/images/tools/boot', 'STORAGE_DISK_ID': None}}, 'LOCAL_ALLOCATION': 17814249472, 'SHARED_ALLOCATION': 0}
on_crash = 'destroy'
vcpus = 4
memory = 4096
vfb = ['type=vnc,vncunused=1']
disk = ['file:/server/xen/images/tools/boot,xvda,w', 'file:/server/xen/images/tools/server,xvdb,w', 'file:/server/install-images/SLES-11-DVD-x86_64-GM-DVD1.iso,xvdc:cdrom,r']
name = 'tools'


As you can see from attachement, storages are messed up. And if I now shutdown and then start the vm from convirt it won't start.

Of course I can fix this manually, but it is certainly not the desired way

Edit: Actually, it messed up storage order every time when I edit settings. So, if I want edit settings I have to remember every time to correct the order before I restart vm, otherwise bootable flag is on wrong disk and I get an error: "Error: Boot loader didn't return any data!"

[jd_jedi]

To the best of my knowledge, we have a fix for this. Let me see if I can get you a patch.

[adhd]

To the best of my knowledge, we have a fix for this. Let me see if I can get you a patch.

It would be great

[rajasekhar911]

Attached is a diff for solving the disk sequence issue

apply the Patch bundle #1 if it is not already applied
http://www.convirture.com/wiki/index.ph ... atches_2_0

Save the following file in a backup area.
src/convirt/web/convirt/convirt/model/GridManager.py

Download the attached diff.
Apply the diff.
Go to convirt directory and
patch -p0 < import_disk_patch.diff.txt

Restart CMS.

Let us know if this works.

[adhd]

Attached is a diff for solving the disk sequence issue

apply the Patch bundle #1 if it is not already applied
http://www.convirture.com/wiki/index.ph ... atches_2_0

Save the following file in a backup area.
src/convirt/web/convirt/convirt/model/GridManager.py

Download the attached diff.
Apply the diff.
Go to convirt directory and
patch -p0 < import_disk_patch.diff.txt

Restart CMS.

Let us know if this works.

Yes, it works! Thanks for the patch.