Re: [vdsm] start vm which in pool failed
On 09/18/2013 08:03 AM, bigclouds wrote:
when starting a vm of a pool fails.in the process of hooks, i
modify guestvm hostname, and modify the path of backing file of chain.
do nothing else.
i can munually define a xml(after hooks), and start it without error.
env:
libvirt-0.10.2-18.el6_4.5.x86_64
2.6.32-358.6.2.el6.x86_64
centos6.4
1.where does this error message come from ?
Storage.StorageDomain WARNING Could not find mapping for lv
d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/cae1bb2d-0529-4287-95a3-13dcb14f082f
2.
Thread-6291::ERROR::2013-09-18
12:44:21,205::vm::683::vm.Vm::(_startUnderlyingVm)
vmId=`24f7e975-9aa5-4a14-b0f0-590add14c8b5`::The vm start process failed
Traceback (most recent call last):
File /us r/share/vdsm/vm.py, line 645, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/libvirtvm.py, line 1529, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py,
line 83, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.6/site-packages/libvirt.py, line 2645, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error Process exited while reading console log
output: char device redirected to /dev/pts/4
qemu-kvm: -drive
file=/rhev/data-center/7828f2ae-955e-4e4b-a4bb-43807629dc52/d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/images/ac025dc1-4e25-4b71-8c56-88dcb61b9f09/cae1bb2d-0529-4287-95a3-13dcb14f082f,if=none,id=drive-ide0-0-0,format=qcow2,serial=ac025dc1-4e25-4b71-8c56-88dcb61b9f09,cache=none,werror=stop,rerror=stop,aio=n
ative: could not open disk image
/rhev/data-center/7828f2ae-955e-4e4b-a4bb-43807629dc52/d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/images/ac025dc1-4e25-4b71-8c56-88dcb61b9f09/cae1bb2d-0529-4287-95a3-13dcb14f082f:
Operation not permitted
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
can you share your hook?
(if it works without your hook, i suspect a bug there)
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] start vm which in pool failed
On Wed, Sep 18, 2013 at 01:03:08PM +0800, bigclouds wrote:
when starting a vm of a pool fails.in the process of hooks, i modify
guestvm hostname, and modify the path of backing file of chain. do nothing
else.
i can munually define a xml(after hooks), and start it without error.
Could you compare (or share) the manual domxml and the one produced by
your hook? It might be easier to spot the bug that way.
env:
libvirt-0.10.2-18.el6_4.5.x86_64
2.6.32-358.6.2.el6.x86_64
centos6.4
1.where does this error message come from ?
Storage.StorageDomain WARNING Could not find mapping for lv
d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/cae1bb2d-0529-4287-95a3-13dcb14f082f
2.
Thread-6291::ERROR::2013-09-18
12:44:21,205::vm::683::vm.Vm::(_startUnderlyingVm)
vmId=`24f7e975-9aa5-4a14-b0f0-590add14c8b5`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 645, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/libvirtvm.py, line 1529, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py, line
83, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.6/site-packages/libvirt.py, line 2645, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output:
char device redirected to /dev/pts/4
qemu-kvm: -drive
file=/rhev/data-center/7828f2ae-955e-4e4b-a4bb-43807629dc52/d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/images/ac025dc1-4e25-4b71-8c56-88dcb61b9f09/cae1bb2d-0529-4287-95a3-13dcb14f082f,if=none,id=drive-ide0-0-0,format=qcow2,serial=ac025dc1-4e25-4b71-8c56-88dcb61b9f09,cache=none,werror=stop,rerror=stop,aio=native:
could not open disk image
/rhev/data-center/7828f2ae-955e-4e4b-a4bb-43807629dc52/d028d521-d4a9-4dd7-a0fe-3e9b60e7c4e4/images/ac025dc1-4e25-4b71-8c56-88dcb61b9f09/cae1bb2d-0529-4287-95a3-13dcb14f082f:
Operation not permitted
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] rebasing for oVirt 3.3.1?
On Mon, Sep 09, 2013 at 03:17:35PM +0300, Itamar Heim wrote: with 3.3.0 coming soon, one of the questions I heard is what about 3.3.1 considering the number of patches fox bugs that went into master branch since since we branched to stabilize 3.3.0. i.e., most of the work in master branch has been focused on bug fixes) so my suggestion is for 3.3.1 that we rebase from master, then move to backporting patches to that branch for the rest of 3.3 time frame. while this poses a small risk, i believe its the best course forward to making ovirt 3.3 a more robust and stable version going forward. this is mostly about ovirt-engine, and probably vdsm. for the other projects, its up to the maintainer, based on risk/benefit. To make this happen for Vdsm, we need to slow things down a bit, stabilize what we have, and test it out. Most of our work since ovirt-3.3 was bug fixing (23 patches), but some of the 101 patches we've got are related to refactoring (19), cleanups (27), test improvements (21), behind-the-scenes features (6), and visible features (5). Refactoring included Zhou Zheng Sheng's Ubuntu-readiness patches, which may still incur surprises to sysV/systemd/upstart service framework, and changes to how network configurators are to be used. Behind-the-scenes features include speedup to block-based storage: - One shot teardown. - Avoid Img and Vol produces in fileVolume.getV*Size - Make lvm.listPVNames() be based on vgs information. - One shot prepare. - Introduce lvm short filters. Visible features are few, and only one of them: - clientIF: automatically unpause vms in EIO when SD becomes active carries some kind of a risk to a timely release. The rest of them are: - Support for multiple heads for Qxl display device - Add support for direct setting of cpu_shares when creating a VM - Introducing hidden_vlans configurable. - macspoof hooks: new hook script to enable macspoof filtering per vnic. I think we can release vdsm-4.13.0 within a week if we put a hold on new features and big changes, and put enough effort into testing the mostly-changed areas: - service framework - VM lifecycle over block storage (including auto unpause) - network configuration Then, we could release vdsm-4.13.z without risking the stability of ovirt-3.3.1. Let's do it! Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
