Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1060729

Summary: Change NIC type from sPAPR VLAN to any other type causes error when starting the VM (PPC)
Product: [Retired] oVirt Reporter: Leonardo Bianconi <leonardo.bianconi>
Component: ovirt-engine-coreAssignee: Leonardo Bianconi <leonardo.bianconi>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, gklein, gustavo.pedrosa, iheim, leonardo.bianconi, masayag, ofrenkel, rgolan, vitor.lima, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: ppc64   
OS: Unspecified   
Whiteboard: ppc
Fixed In Version: ovirt-3.4.0-beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:27:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leonardo Bianconi 2014-02-03 13:18:59 UTC 
Description of problem:
After created the VM, added a network interface and have changed its type, the VM cannot be started.


Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.4


How reproducible:
100%


Steps to Reproduce:
1. Create a PPC64 cluster
2. Add a PPC64 host
3. Create a VM using the PPC64 host
4. Add a Network Interface to the VM using the sPAPR VLAN type
5. Run the VM.
6. Shutdown the VM.
7. Edit the Network inteface type, created on step 4, to any other.
8. Run the VM.

Actual results:
VM failed to run and the message is displayed: "VM PPC_VM is down. Exit message: internal error: process exited while connecting to monitor: Warning: Disabling some instructions which are not emulated by TCG (0x0, 0x6) qemu-system-ppc64: -device e1000,netdev=hostnet0,id=net0,mac=00:1a:4a:74:d0:00,reg=0x1000: Property '.reg' not found ."


Expected results:
VM run without errors.


Additional info:
If a new NIC is created, the problem does not appear. Seems there are info related with the last NIC being stored.
Comment 1 Sandro Bonazzola 2014-03-31 12:27:04 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released