Hide Forgot
Created attachment 792770 [details] vdsm + engine logs Description of problem: When cloning a vm from snapshot the new vm's vnic_profile_id is blank, and the vm does not get an IP when booting up. engine=# select * from vm_interface; id | vm_guid | vmt_guid | mac_addr | name | speed | type | _create_date | _update_date | linked | vnic_profile_id --------------------------------------+--------------------------------------+----------+-------------------+------+-------+------+-------------------------------+--------------+--------+-------------------------- ------------ 4a96568d-999a-496b-8736-c25f5ddf622d | cb360a32-b71c-41c3-8b8c-b429c88b9418 | | 00:1a:4a:16:81:bc | nic1 | 1000 | 3 | 2013-09-02 10:53:31.368373+03 | | t | a7c50b98-e8ca-4d92-a7a2-2 474efc7f718 9a28a9a7-a04f-4ac8-9514-ced71cc0ab5f | f6f1981d-c53a-45bc-8a89-f08ba4768eef | | 00:1a:4a:16:81:bd | nic1 | 1000 | 3 | 2013-09-02 10:57:20.136157+03 | | t | (2 rows) Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create vm and install OS on it, then set persistent network 2. Power off vm and create a snapshot 3. Clone vm from snapshot 4. Start new vm Actual results: New vm does not have vnic_profile_id, also on webadmin on the VM itself,the new vm's network interfaces tab has only the NIC - the network name and network profile for the NIC are empty.
Created attachment 797877 [details] VM2 now has vNicProfile Bug fixed.
Bug fixed. See attachment
Closing - RHEV 3.3 Released