Ticket #3340 (closed defect: fixed)
Issues creating a new virtual machine
| Reported by: | ira@… | Owned by: | jamor@… |
|---|---|---|---|
| Milestone: | 2.2.X | Component: | virt |
| Severity: | major | Keywords: | |
| Cc: |
Description
Hi, am creating an ubuntu 10.04 vm following these steps:
- Add VM
- Add NAT network interface
- Add CD iso
- Add new disk image
When I hit 'save changes' it tries to change two modules: firewall and another that fails before it tells you what it is
Here is the out put of the error message: element mac does not exist. element mac does not exist. at /usr/share/perl5/EBox/Model/Row.pm line 409 EBox::Model::Row::elementByName('EBox::Model::Row=HASH(0x9476d80)', 'mac') called at /usr/share/perl5/EBox/Model/Row.pm line 496 EBox::Model::Row::valueByName('EBox::Model::Row=HASH(0x9476d80)', 'mac') called at /usr/share/perl5/EBox/Virt/Model/NetworkSettings.pm line 166 EBox::Virt::Model::NetworkSettings::isEqual('EBox::Virt::Model::NetworkSettings?=HASH(0x93d36e8)', 'virt3219') called at /usr/share/perl5/EBox/Virt/Model/VirtualMachines.pm line 206 EBox::Virt::Model::VirtualMachines::vmChanged('EBox::Virt::Model::VirtualMachines?=HASH(0x937d848)', 'virt3219') called at /usr/share/perl5/EBox/Virt.pm line 359 EBox::Virt::_saveConfig('EBox::Virt=HASH(0x7aa4720)') called at /usr/share/perl5/EBox/Module/Base.pm line 229 EBox::Module::Base::save('EBox::Virt=HASH(0x7aa4720)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 606 EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl?=HASH(0x3c3c7e0)', 'progress', 'EBox::ProgressIndicator?=HASH(0x3c6c668)') called at /usr/share/perl5/EBox/Global.pm line 95 EBox::Global::AUTOLOAD('EBox::Global=HASH(0x3c6ca58)', 'progress', 'EBox::ProgressIndicator?=HASH(0x3c6c668)') called at /usr/share/zentyal/global-action line 39
My hardware setup is as follows:
i7 2600, 16 GB RAM, 3x 36GB HDD in RAID0, 2x 2TB in RAID1, Motherboard supports VT-x, VT-d.
Attachments
Change History
comment:3 Changed 19 months ago by ira@…
Deleted Virtual Machine and made a new one with same name and still had same issues. Made one with a different name and it works now. Most likely conflicting with old settings that weren't deleted...
comment:4 Changed 19 months ago by don@…
Had the same error so I deleted virtual machine, added new virtual machine, add hd, add cd pointing to an image file, boot VM and all looks fine (if I could log into it with vnc :-()
Now I want to remove the CD image and I get the error again.
Core version 2.2.3
comment:5 Changed 19 months ago by du-sky@…
- Severity changed from normal to major
I have exactly same problem as don@
comment:6 Changed 19 months ago by rintjema.s@…
This problem is caused by the name of the virtual machine. Example
If you use "Server Branch Office" it will fail. Use server01 instead, it will work.
Kind Regards, Sijbren Rintjema
comment:7 Changed 19 months ago by jamor@…
- Owner changed from jacalvo@… to jamor@…
- Status changed from new to assigned
comment:8 Changed 19 months ago by jamor@…
- Status changed from assigned to closed
- Resolution set to fixed
comment:9 Changed 19 months ago by jamor@…
Thanks to all for your reports.
I had tried to fix this but unfortunately the program 'virtsh' refuses to accept anmes with spaces.
So I had to restrict the names to a small character set without spaces.
If you have this problem, please edit your virtual machine name and remove spaces or non-ASCII characters.
Regards,
Javier
comment:10 Changed 19 months ago by aleks@…
- Status changed from closed to reopened
- Resolution fixed deleted
I don't think that problem is in machine name and virsh utility. I'm using virtualbox and keep getting this error.
comment:11 Changed 19 months ago by jamor@…
- Status changed from reopened to closed
- Resolution set to fixed
comment:12 Changed 19 months ago by jamor@…
Hello Aleks, the name problem was real, yours was a different problem but it is fixed now in the repository.
If you don't want to wait for a new release, you can hotfix your server with this steps:
1) Replace /usr/share/perl5/EBox/Virt/Model/NetworkSettings with the new version at
2) Restart interface webserver with: 'sudo /etc/init.d/zentyal apache restart'.
3) Unluckily is very probable that you old machine contains corrupted configuration data after the error, so I advise you delete it and create a new one.
Regards,
Javier
comment:13 Changed 19 months ago by aleks@…
Many thanks.
