Re: VLAN bridge without ip address
Am 15.03.24 um 22:11 schrieb stefanx: > Hello, > > I have a fairly simple question: I need an netplan example configuration for > a VLAN bridge without ip address for using kvm/qemu/libvirt (Ubuntu 22.04). I > can't find anything about it. > > Thanks > > Stefan Hello, can't anyone help me ? :-( Stefan
PCI hot plug to a VM does not work in Alma
Hi We have a chassis with a peripheral PCI device installed. We have a hypervisor running on the chassis where we have deployed a VM which can use the PCI device once it is attached. When the PCI device is powered on or off we need to do a hotplug in/out using virsh commands. Even though the virsh commands for hotplug is executed successfully, the VM sees the PCI inside the VM for one or 2 secs. What do you think is the issue? [root ~]# uname -a Linux 4.18.0-372.9.1.el8.x86_64 #1 SMP Fri Mar 15 05:32:38 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [root ~]# virsh --version 8.0.0 [root ~]# rpm -qa | grep libvirt libvirt-daemon-driver-nwfilter-8.0.0-5.el8.x86_64 python3-libvirt-7.8.0-1.el8.x86_64 libvirt-daemon-driver-storage-logical-8.0.0-5.el8.x86_64 libvirt-libs-8.0.0-5.el8.x86_64 libvirt-daemon-config-nwfilter-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-gluster-8.0.0-5.el8.x86_64 libvirt-8.0.0-5.el8.x86_64 libvirt-daemon-8.0.0-5.el8.x86_64 libvirt-daemon-driver-nodedev-8.0.0-5.el8.x86_64 libvirt-daemon-config-network-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-iscsi-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-rbd-8.0.0-5.el8.x86_64 libvirt-daemon-driver-network-8.0.0-5.el8.x86_64 libvirt-daemon-driver-secret-8.0.0-5.el8.x86_64 python2-libvirt-python-5.10.0-1.el8.x86_64 libvirt-daemon-driver-qemu-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-core-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-iscsi-direct-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-scsi-8.0.0-5.el8.x86_64 libvirt-client-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-disk-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-8.0.0-5.el8.x86_64 libvirt-daemon-driver-interface-8.0.0-5.el8.x86_64 libvirt-daemon-driver-storage-mpath-8.0.0-5.el8.x86_64 libvirt-daemon-kvm-8.0.0-5.el8.x86_64 [root ~]# rpm -qa | grep qemu qemu-kvm-ui-opengl-6.2.0-11.el8.x86_64 qemu-kvm-6.2.0-11.el8.x86_64 qemu-img-6.2.0-11.el8.x86_64 qemu-kvm-block-iscsi-6.2.0-11.el8.x86_64 ipxe-roms-qemu-20200823-7.git4bd064de.el8.noarch qemu-kvm-block-gluster-6.2.0-11.el8.x86_64 qemu-kvm-block-rbd-6.2.0-11.el8.x86_64 qemu-kvm-block-curl-6.2.0-11.el8.x86_64 qemu-kvm-core-6.2.0-11.el8.x86_64 qemu-kvm-hw-usbredir-6.2.0-11.el8.x86_64 libvirt-daemon-driver-qemu-8.0.0-5.el8.x86_64 qemu-kvm-ui-spice-6.2.0-11.el8.x86_64 qemu-kvm-docs-6.2.0-11.el8.x86_64 qemu-kvm-block-ssh-6.2.0-11.el8.x86_64 qemu-kvm-common-6.2.0-11.el8.x86_64 [root ~]# virsh nodedev-dettach pci__04_00_0 [12013.987821] pci_probe_reset_slot: call pci_slot_reset with probe=1 [12014.063669] pci_slot_reset (printk info): reset hotplug slot. [12014.134164] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) [Mar19 21:09] pci_probe_reset_slot: call pci_slot_reset with probe=1 [ +0.075848] pci_slot_reset (printk info): reset hotplug slot. [ +0.070495] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) Device pci__04_00_0 detached [root ~]# virsh attach-device ROUTER8 /opt/us/bin/mrvl.xml [12024.217540] pci_probe_reset_slot: call pci_slot_reset with probe=1 [ +10.083376] pci_probe_reset_slot: call pci_slot_reset with probe=1[12024.293548] pci_slot_reset (printk info): reset hotplug slot. [12024.434828] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) [ +0.076008] pci_slot_reset (printk info): reset hotplug slot. [ +0.141280] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1)4.526807] pci_probe_reset_slot: call pci_slot_reset with probe=1 [12024.749367] pci_slot_reset (printk info): reset hotplug slot. [12024.821327] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) [ +0.091979] pci_probe_reset_slot: call pci_slot_reset with probe=1[12024.911065] pci_probe_reset_slot: call pci_slot_reset with probe=1 [ +0.222560] pci_slot_reset (printk info): reset hotplug slot. [ +0.071960] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) 5.057584] pci_slot_reset (printk info): reset hotplug slot. [ +0.089738] pci_probe_reset_slot: call pci_slot_reset with probe=1 [12025.278585] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) [ +0.146519] pci_slot_reset (printk info): reset hotplug slot. [ +0.221001] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) 5.441574] pci_probe_reset_slot: call pci_slot_reset with probe=1 [ +0.162989] pci_probe_reset_slot: call pci_slot_reset with probe=1[12025.665968] pci_slot_reset (printk info): reset hotplug slot. [12025.806751] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1) [12025.898060] __pci_reset_slot (printk info): Reset slot (not hotplug), probe = 1. [ +0.224394] pci_slot_reset (printk info): reset hotplug slot. [ +0.140783] pci_reset_hotplug_slot(printk INFO): calling reset_slot (probe = 1)5.988477] pci_slot_reset (printk info): reset hotplug slot. [ +0.091309] __pci_reset_slot (printk info): Reset slot (not hotplug), probe = 1. 12026.205654] pci_reset_hotplug_slot(printk INFO):
Re: No 'PCI' bus found for device 'ivshmem-plain'
On Thu, 21 Mar 2024 at 08:16, Sanjeev Kumar wrote: > > Hi, > our kernel is build with aarch64le. it is 64 bit ARM architecture. Such a kernel cannot possibly boot on the vexpress-a15 machine that you say you are using. So something doesn't seem right... > when i am trying to use virt as machine, then qemu isn't starting. it is > being stuck after entering command, You probably didn't build your kernel correctly to have all the support needed for the virt machine's devices. I recommend finding a tutorial on how to boot Linux on the virt board. This one is a bit old but the basic process will still work with newer Debian versions: https://translatedcode.wordpress.com/2017/07/24/installing-debian-on-qemus-64-bit-arm-virt-board/ thanks -- PMM
Re: No 'PCI' bus found for device 'ivshmem-plain'
as we are beginners. can you please guide us on using virt cpu please. On Thu, Mar 21, 2024 at 1:52 PM Sanjeev Kumar wrote: > cpu we are using cortex-a57 because it is nearby to our actual hardware > exynos v9 > > On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar > wrote: > >> Hi, >> our kernel is build with aarch64le. it is 64 bit ARM architecture. >> when i am trying to use virt as machine, then qemu isn't starting. it is >> being stuck after entering command, >> >> On Wed, Mar 20, 2024 at 7:06 PM Peter Maydell >> wrote: >> >>> On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar >>> wrote: >>> > >>> > Hi Peter, >>> > Thanks for your detailed review. >>> > ifs.bin is our custom build and the linux kernel is booting fine with >>> this file. >>> >>> If it is, then it must be a 32-bit kernel. So trying to run it >>> on the cortex-a57 will not work at all, because that is a 64-bit >>> CPU and will only boot 64-bit kernels. (QEMU emulation does not >>> allow booting a guest kernel in 32-bit mode for CPUs that in >>> hardware support both 32-bit and 64-bit, I'm afraid.) >>> >>> > "this board doesn't have a PCI bus" - can you please suggest some >>> board which can support PCI bus? >>> >>> I just did: try the "virt" board. You'll need to decide what >>> CPU you actually want to run first, though. >>> >>> thanks >>> -- PMM >>> >>
Re: No 'PCI' bus found for device 'ivshmem-plain'
cpu we are using cortex-a57 because it is nearby to our actual hardware exynos v9 On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar wrote: > Hi, > our kernel is build with aarch64le. it is 64 bit ARM architecture. > when i am trying to use virt as machine, then qemu isn't starting. it is > being stuck after entering command, > > On Wed, Mar 20, 2024 at 7:06 PM Peter Maydell > wrote: > >> On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar >> wrote: >> > >> > Hi Peter, >> > Thanks for your detailed review. >> > ifs.bin is our custom build and the linux kernel is booting fine with >> this file. >> >> If it is, then it must be a 32-bit kernel. So trying to run it >> on the cortex-a57 will not work at all, because that is a 64-bit >> CPU and will only boot 64-bit kernels. (QEMU emulation does not >> allow booting a guest kernel in 32-bit mode for CPUs that in >> hardware support both 32-bit and 64-bit, I'm afraid.) >> >> > "this board doesn't have a PCI bus" - can you please suggest some board >> which can support PCI bus? >> >> I just did: try the "virt" board. You'll need to decide what >> CPU you actually want to run first, though. >> >> thanks >> -- PMM >> >
Re: No 'PCI' bus found for device 'ivshmem-plain'
Hi, our kernel is build with aarch64le. it is 64 bit ARM architecture. when i am trying to use virt as machine, then qemu isn't starting. it is being stuck after entering command, On Wed, Mar 20, 2024 at 7:06 PM Peter Maydell wrote: > On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar > wrote: > > > > Hi Peter, > > Thanks for your detailed review. > > ifs.bin is our custom build and the linux kernel is booting fine with > this file. > > If it is, then it must be a 32-bit kernel. So trying to run it > on the cortex-a57 will not work at all, because that is a 64-bit > CPU and will only boot 64-bit kernels. (QEMU emulation does not > allow booting a guest kernel in 32-bit mode for CPUs that in > hardware support both 32-bit and 64-bit, I'm afraid.) > > > "this board doesn't have a PCI bus" - can you please suggest some board > which can support PCI bus? > > I just did: try the "virt" board. You'll need to decide what > CPU you actually want to run first, though. > > thanks > -- PMM >
