Bug 1052168
Summary: | Do not allow migration when 'Use Host CPU' flag checked | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Artyom <alukiano> | ||||
Component: | ovirt-engine | Assignee: | Roy Golan <rgolan> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.3.0 | CC: | dfediuck, gklein, iheim, lpeer, mavital, rbalakri, rgolan, Rhev-m-bugs, scohen, sherold, yeylon | ||||
Target Milestone: | --- | Keywords: | Triaged | ||||
Target Release: | 3.5.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | sla | ||||||
Fixed In Version: | org.ovirt.engine-root-3.5.0-25 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-02-17 17:17:14 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1164308, 1164311 | ||||||
Attachments: |
|
Description
Artyom
2014-01-13 12:40:58 UTC
andrew - i have a vague recollection you specifically asked to not block this? According to libvirt docs [1]- " host-passthrough ... Though the downside of this mode is that the guest environment cannot be reproduced on different hardware. Thus, if you hit any bugs, you are on your own. " So my last recollection of this was we allow the vm to start anywhere, but then it will not migrate. See: https://bugzilla.redhat.com/show_bug.cgi?id=838469#c10 And [2] that says: " Label should be "Pass through host CPU". When this is set the VM should be marked as non-migratable " [1] http://libvirt.org/formatdomain.html#elementsCPU [2] http://www.ovirt.org/Features/Cpu-host_Support#Detailed_Description @Doron Should new/edit/other VM commands be blocked in case the VM is not pinned and pass through is on? Thanks. (In reply to Gilad Chaplik from comment #4) > @Doron > > Should new/edit/other VM commands be blocked in case the VM is not pinned > and pass through is on? > > Thanks. What do you mean by 'new'? As for the others, shouldn't be an issue. The important thing is locking the migration options, once pass through is being used. Check on rhevm-3.5.0-0.23.beta.el6ev.noarch Still have libvirt error and migration failed: Thread-334139::ERROR::2014-12-14 09:53:20,262::migration::260::vm.Vm::(run) vmId=`ffb6cc41-be24-4479-b7a9-3d0c714ea8fc`::Failed to migrate Traceback (most recent call last): File "/usr/share/vdsm/virt/migration.py", line 246, in run self._startUnderlyingMigration(time.time()) File "/usr/share/vdsm/virt/migration.py", line 325, in _startUnderlyingMigration None, maxBandwidth) File "/usr/share/vdsm/virt/vm.py", line 689, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.6/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1210, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: Requested operation is not valid: domain has CPU feature: invtsc Missed patches added to the 3.5.0 branch. Verified on rhevm-3.5.0-0.25.el6ev.noarch rhev 3.5.0 was released. closing. |