-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.0.beta
-
None
-
Moderate
-
sst_virtualization
-
ssg_virtualization
-
3
-
False
-
-
None
-
None
-
None
-
None
-
-
aarch64
-
None
What were you trying to do that didn't work?
Use virt-install to install a guest on aarch64.
Some devices like graphic, video are missing in the guest on aarch64, but they exist on x86_64 . And tpm device exists on aarch64, but not on x86_64. There are inconsistent default behaviors on x86_64 and aarch64.
Please provide the package NVR for which bug is seen:
virt-install-4.1.0-7.el10.noarch
How reproducible:
100%
Steps to reproduce
Execute below two commands on aarch64 and x86_64 respectively. They are most same, except --cpu mode.
The command on aarch64:
virt-install --connect qemu:///system -n vmzd2 --hvm --accelerate -r 2048 --vcpus=2 --os-variant rhel9.4 --disk path=/var/lib/avocado/data/avocado-vt/images/jeos-27-aarch64.qcow2,bus=virtio,format=qcow2 --network network=default,model=virtio --import --noreboot --noautoconsole --debug --cpu host-passthrough --check path_in_use=off
The command on x86_64:
virt-install --connect qemu:///system -n test_vm --hvm --accelerate -r 2048 --vcpus=2 --os-variant rhel9.4 --disk path=/var/lib/avocado/data/avocado-vt/images/jeos-27-x86_64.qcow2,bus=virtio,format=qcow2 --network network=default,model=virtio --import --noreboot --noautoconsole --debug --cpu host --check path_in_use=off
The devices added automatically in guest xml on aarch64:
<serial type='pty'>
<target type='system-serial' port='0'>
<model name='pl011'/>
</target>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0'/>
</tpm>
<audio id='1' type='none'/>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</memballoon>
<rng model='virtio'>
<backend model='random'>/dev/urandom</backend>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</rng>
The devices added automatically in guest xml on x86_64:
<serial type='pty'>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'>
<listen type='address'/>
</graphics>
<audio id='1' type='none'/>
<video>
<model type='virtio' heads='1' primary='yes'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</video>
<watchdog model='itco' action='reset'/>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</memballoon>
<rng model='virtio'>
<backend model='random'>/dev/urandom</backend>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</rng>
The differences are:
Devices added on aarch64, but not on x86_64:
tpm device
Devices added on x86_64, but not on aarch64:
graphics, usb tablet , and video
The missing of watchdog and ps2 input devices are acceptable because they are not supported on aarch64.
Expected results
For those supported devices, virt-install should provide same default behaviors on both x86_64 and aarch64.
Actual results
See above reproduce step
- is blocked by
-
RHEL-46783 Rebase virt-manager for RHEL-10
-
- Planning
-
