similar to: how to configure seabios with libvirt

Maybe this should go to the qemu mail list, but I have domains configured to dump to serial. Works fine I see Grub menu/kernel messages and the like, but the "bootmenu" listing only shows up over vnc. Is there a way to have that show up over serial? I definitely can hit up the qemu mail list as well if inappropriate for here

On 13.02.2015 09:23, Ján Tomko wrote: > On Thu, Feb 12, 2015 at 03:32:02PM -0600, mail list wrote: >> Maybe this should go to the qemu mail list, but I have domains configured >> to dump to serial. Works fine I see Grub menu/kernel messages and the like, >> but the "bootmenu" listing only shows up over vnc. Is there a way to have >> that show up over serial?

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 For the latest seabios version, it said: Support for vga emulation over a serial port in SeaBIOS (sercon). So I want to know how can I find the application of this feature in libvirt? And whether my understanding is correct? There are no related instruction on the website: https://libvirt.org/ My understanding: (1) The feature means: we can set this the IO address of a serial port to

Dear all, I'm looking for a bit of help with a problematic VM. We have an hypervisor which has 4 eth ports. 3 are already used, and I wanted to pass the 4th one directly to a VM (which is fully working without it). So, I modified the XML accordingly (which matches our hardware), adding: <hostdev mode='subsystem' type='pci' managed='yes'> <source>

The SeaBIOS ROM image may validly exceed 128k in size, it''s only our interface code that so far assumed that it wouldn''t. Remove that restriction by setting the base address depending on image size. Add a check to HVM loader so that too big images won''t result in silent guest failure anymore. Uncomment the intended build-time size check for rombios, moving it into a

Cross posting from seabios@ [snip] > > Now I'd like to ask you guys if you could print the amount > > of RAM available -- like most other BIOSes out there already > > do - it would be extremely helpful to aid troubleshooting. > > SeaBIOS boots too fast for anything useful to be seen on the screen. > That said, one can add "-chardev stdio,id=seabios -device

I've uploaded seabios 1.7.4-2 to debian archive which now ships 2 versions of the bios binary -- small 128Kb one and bios-256k.bin (with size = 256Kb, obviously). For now, both are built with Xen support. So for now, it is enough to just rebuild xen with seabios >= 1.7.4-2~ to get this fixed without patching. However, please apply the mentioned patch (or update to xen-4.3.1 version)

Qemu upstream now can be added on xen >=4.2, seabios added support for xen: seabios (1.7.1-1) unstable; urgency=low * updated to new minor upstream release (1.7.1): - native scsi boot support (Closes: #652530) - usb-attached scsi boot support - Xen support (Closes: #678042) - better integration with qemu - some bugfixes * removed fix-==-in-shell.patch (not

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: important Tags: upstream patch When using Xen compiled with seabios-1.7.4-1 (now in unstable/testing), HVMs fail immediately upon starting with a VCPU triple fault: (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. This is because SeaBIOS can now be greater than 128k, which breaks an

On Wed, Feb 28, 2018 at 03:10:08PM +0800, Meina Li wrote: >Hi > >For the latest seabios version, it said: Support for vga emulation over a >serial port in SeaBIOS (sercon). > >So I want to know how can I find the application of this feature in >libvirt? And whether my understanding is correct? >There are no related instruction on the website: https://libvirt.org/ >

Hi, I have installed Debian Buster with encrypted LVM so apon installation my root partition is encrypted. So far so good but as soon as I encrypt the boot partition, after reboot the OS won't start. If I start the drive directly with qemu, it works but it looks like Libvirt is somehow not able to deel with it. What am I missing? -- John Doe

Hi Paolo & Co, So I've been running into another bug with SeaBIOS w/ virtio-scsi + vhost-scsi-pci code.. During the last weeks debugging on the QEMU vhost memory re-mapping bug, my seabios builds have been using a smaller target ID (16) for scanning than the default hard coded value of 256 in init_virtio_scsi(). After bumping this value back to 256 recently, a bogus out_num value from

Hi Paolo & Co, So I've been running into another bug with SeaBIOS w/ virtio-scsi + vhost-scsi-pci code.. During the last weeks debugging on the QEMU vhost memory re-mapping bug, my seabios builds have been using a smaller target ID (16) for scanning than the default hard coded value of 256 in init_virtio_scsi(). After bumping this value back to 256 recently, a bogus out_num value from

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

Pass PYTHON=$(PYTHON) to gmake when building seabios. This fixes seabios build error ''python not found'' along with the patches from Kevin O''Connor. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo,

On Wed, Jul 30, 2014 at 03:58:43PM -0700, Zetan Drableg wrote: > [00183ms] /usr/libexec/qemu-kvm \ > -global virtio-blk-pci.scsi=off \ > -nodefconfig \ > -nodefaults \ > -nographic \ > -machine accel=kvm:tcg \ > -cpu host,+kvmclock \ > -m 500 \ > -no-reboot \ > -kernel /var/tmp/.guestfs-0/kernel.47903 \

I gave this series a spin, along a custom QEMU, and `supermin` from Git, for my `libguestfs-test-tool` itself fails with: "Could not open option rom 'linuxboot_dma.bin': No such file or directory" How I went about: (1) Build QEMU with https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05891.html -- Add optionrom compatible with fw_cfg DMA version

@Ian Campbell: you do not receive my email? I have sent some mails to you and pkg-xen-devel at lists.alioth.debian.org reporting this problem since long time ago to some days ago. As Michael Tokarev above wrote also the build-dep should be changed to seabios >= 1.7.4-2~ I saw in git that is missed in your commit:

Hi Richard thanks for the info. I took the strace approach and ran into this looping over and over again. Is it failing to get time? timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 0}}) = 0 timer_settime(0x8, 0, {it_interval={0, 0}, it_value={0, 250000}}, NULL) = 0 timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 204443}}) = 0 select(16, [0 6 9 13 15], [], [], {1, 0}) = 2 (in [6 13],