search for: openbios

...9 09:53 bamboo.dtb 19 Dec 14 13:16 bios.bin -> ../seabios/bios.bin 4.0K Dec 14 13:16 keymaps 34 Dec 14 13:16 linuxboot.bin -> ../seabios/optionrom/linuxboot.bin 2.3K Nov 29 09:53 mpc8544ds.dtb 34 Dec 14 13:16 multiboot.bin -> ../seabios/optionrom/multiboot.bin 24 Dec 14 13:16 openbios-ppc -> ../openbios/openbios-ppc 28 Dec 14 13:16 openbios-sparc32 -> ../openbios/openbios-sparc32 28 Dec 14 13:16 openbios-sparc64 -> ../openbios/openbios-sparc64 27 Dec 14 13:16 ppc_rom.bin -> ../openhackware/ppc_rom.bin 37 Dec 14 13:16 pxe-e1000.bin -> ../../lib/etherboo...

...9 09:53 bamboo.dtb 19 Dec 14 13:16 bios.bin -> ../seabios/bios.bin 4.0K Dec 14 13:16 keymaps 34 Dec 14 13:16 linuxboot.bin -> ../seabios/optionrom/linuxboot.bin 2.3K Nov 29 09:53 mpc8544ds.dtb 34 Dec 14 13:16 multiboot.bin -> ../seabios/optionrom/multiboot.bin 24 Dec 14 13:16 openbios-ppc -> ../openbios/openbios-ppc 28 Dec 14 13:16 openbios-sparc32 -> ../openbios/openbios-sparc32 28 Dec 14 13:16 openbios-sparc64 -> ../openbios/openbios-sparc64 27 Dec 14 13:16 ppc_rom.bin -> ../openhackware/ppc_rom.bin 37 Dec 14 13:16 pxe-e1000.bin -> ../../lib/etherboo...

...-nv-b75-sparc-...iso), created an empty image for the hard disk, and tried to start qemu in a linux x64bit-host: qemu-system-sparc -hda test.img -cdrom sol-nv-b75-sparc-v1.iso -boot d -nographic The output says: Nvram id QEMU_BIOS, version 1 CPUs: 1 nvram error detected, zapping pram Welcome to OpenBIOS v1.0RC1 built on Sep 21 2006 18:03 Type ''help'' for detailed information Nvram id QEMU_BIOS, version 1 CPUs: 1 nvram error detected, zapping pram Welcome to OpenBIOS v1.0RC1 built on Sep 21 2006 18:03 Type ''help'' for detailed information [sparc] Booting file...

...mu qemu-system The following NEW packages will be installed: qemu qemu-system{b} 0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 16.6 MB of archives. After unpacking 50.9 MB will be used. The following packages have unmet dependencies: qemu-system: Depends: openbios-ppc (>= 1.0+svn1018) but 1.0+svn640-1 is installed. Depends: openbios-sparc (>= 1.0+svn1018) but 1.0+svn640-1 is installed. My first question is, is this normal? Do I need the qemu and qemu-system packages installed? What about these openbios dependencies? The next probl...

...- As I said above, what does the absence of that property mean ? An old qemu that does bypass on all virtio or a new qemu trying to tell you that the virtio device actually does use the iommu (or some other environment that isn't qemu) ? ? - On things like macs, the device-tree is generated by openbios, it would have to have some added logic to try to figure that out, which means it needs to know *via different means* that some or all virtio devices bypass the iommu. I thus go back to my original statement, it's a LOT easier to handle if the device itself is self describing, indicating wheth...

...- As I said above, what does the absence of that property mean ? An old qemu that does bypass on all virtio or a new qemu trying to tell you that the virtio device actually does use the iommu (or some other environment that isn't qemu) ? ? - On things like macs, the device-tree is generated by openbios, it would have to have some added logic to try to figure that out, which means it needs to know *via different means* that some or all virtio devices bypass the iommu. I thus go back to my original statement, it's a LOT easier to handle if the device itself is self describing, indicating wheth...

...oes the absence of that property mean ? An > old qemu that does bypass on all virtio or a new qemu trying to tell > you that the virtio device actually does use the iommu (or some other > environment that isn't qemu) ? > > - On things like macs, the device-tree is generated by openbios, it > would have to have some added logic to try to figure that out, which > means it needs to know *via different means* that some or all virtio > devices bypass the iommu. > > I thus go back to my original statement, it's a LOT easier to handle > if > the device itself i...

...does the absence of that property mean ? An > old qemu that does bypass on all virtio or a new qemu trying to tell > you that the virtio device actually does use the iommu (or some other > environment that isn't qemu) ? > > - On things like macs, the device-tree is generated by openbios, it > would have to have some added logic to try to figure that out, which > means it needs to know *via different means* that some or all virtio > devices bypass the iommu. > > I thus go back to my original statement, it's a LOT easier to handle if > the device itself is self...

Hi all, I'm facing a serious problem with the e100e kernel module for Intel 82574L gigabit nics on Centos 6. The device eth0 suddenly stops working i.e. no more networking. When I do ifconfig from console I get eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:EA inet6 addr: fe80::225:90ff:fe50:8fea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

So ... I've finally tried to sort that out for powerpc and I can't find a way to make that work that isn't a complete pile of stinking shit. I'm very tempted to go back to my original idea: virtio itself should indicate it's "bypassing ability" via the virtio config space or some other bit (like the ProgIf of the PCI header etc...). I don't see how I can make

So ... I've finally tried to sort that out for powerpc and I can't find a way to make that work that isn't a complete pile of stinking shit. I'm very tempted to go back to my original idea: virtio itself should indicate it's "bypassing ability" via the virtio config space or some other bit (like the ProgIf of the PCI header etc...). I don't see how I can make

...it 7a97676b968bcdf60fb987afe6308bc0b4ab9cd3 Author: Paolo Bonzini <pbonzini@redhat.com> Date: Tue Jul 5 14:35:28 2016 +0200 qemu: generate -display none This is preferrable to -nographic which (in addition to disabling graphics output) redirects the serial port to stdio and on OpenBIOS enables the firmware's serial console. We don't want to use stdio serial port at all, but rather explicitly defined ones exposed internally such as: <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-s...

Is crony running? It's default ntpd nowadays Eero 29.7.2016 11.34 ap. "Volker" <volker at openbios.org> kirjoitti: > Hi, > > I have got problems with the ntp daemon. > > It is enabled in systemd but is not started on boot. > > # systemctl status ntpd > ? ntpd.service - Network Time Service > Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor &...

I installed CentOS 7.6 then installed all things QEMU on my machine. I have a SPARC image I need to bringing up in a VM. I've been using *qemu-system-sparc *on a box on which I have Fedora-30 installed. $ qemu-system-sparc -m 256 -hda solaris_v2-qemu_v2.2.0.disk -nographic -bios ./openbios-sparc32 Can I use *qemu-sparc* to bring up my Solaris image: *solaris_v2-qemu_v2.2.0.disk* ? If so, how? It's not apparent and there's almost no info on it. BTW, *qemu-sparc* come with (on CentOS 7.6) when you: $ sudo yum install qemu* *PS> I've tried to install qemu-system-spar...

...do with it. > > I tried out Sparc emulation a long time ago and it barely worked. I was > able to load in Red Hat Linux 6.2 for Sparc for a little while and then it > blew up badly. I gave up after that. It''s getting there. but not enough for SunOS or Solaris, AFAIK. The openbios folks need some forth experts to help resolve some issues around how the customizations in the normal sun openboot do some device remapping, IIRC. > That was .. at least a year ago. It''s getting better. Some of the debian and netbsd sparc stuff is booting and installing. I haven...

On 10/12/20 2:14 PM, john doe wrote: >> <snip/> > > I sent privately the requested xml file to 'Peter Krempa > <pkrempa@redhat.com>'. > Peter Krempa 's privately answered me back suggesting to add the > following in the domain xml file: Solving things privately doesn't help the community. > > > <bios useserial='yes'/>

Hi, I have got problems with the ntp daemon. It is enabled in systemd but is not started on boot. # systemctl status ntpd ? ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) Starting manually works # systemctl start ntpd # systemctl status ntpd ? ntpd.service - Network Time Service

Hi All, The following patch set provides a low-overhead system for collecting kernel tracing data of guests by a host in a virtualization environment. A guest OS generally shares some devices with other guests or a host, so reasons of any problems occurring in a guest may be from other guests or a host. Then, to collect some tracing data of a number of guests and a host is needed when some

Hi All, The following patch set provides a low-overhead system for collecting kernel tracing data of guests by a host in a virtualization environment. A guest OS generally shares some devices with other guests or a host, so reasons of any problems occurring in a guest may be from other guests or a host. Then, to collect some tracing data of a number of guests and a host is needed when some

Hello, yum lists only some of the groups as available # yum group list Loaded plugins: fastestmirror, langpacks, nvidia [nvidia]: No NVIDIA display devices found Loading mirror speeds from cached hostfile * base: ftp.plusline.de * elrepo: ftp.nluug.nl * extras: mirror.wiuwiu.de * updates: ftp.plusline.de Available Environment Groups: Minimal Install Compute Node Infrastructure