similar to: problem booting from virtual disk, looking for pointers to the code

On Thu, Feb 22, 2018 at 11:23 AM, Chris Friesen via Syslinux <syslinux at zytor.com> wrote: > Hi, > > I'm booting an qemu VM from a virtual disk. In the success case the virtual > console shows something like this: > > SYSLINUX 4.05 0x54f93f16 Copyright (C) 1994-2011 H. Peter Anvin et al > Loading vmlinuz......... > Loading

Hi, I'm trying to figure out what controls the number if in-flight virtio block operations when running linux in qemu on top of a linux host. The problem is that we're trying to run as many VMs as possible, using ceph/rbd for the rootfs. We've tripped over the fact the the memory consumption of qemu can spike noticeably when doing I/O (something as simple as "dd" from

Hi, I'm trying to figure out what controls the number if in-flight virtio block operations when running linux in qemu on top of a linux host. The problem is that we're trying to run as many VMs as possible, using ceph/rbd for the rootfs. We've tripped over the fact the the memory consumption of qemu can spike noticeably when doing I/O (something as simple as "dd" from

Attempts to load *.lkrn images were failing with "Not enough memory to load specified image". These images have the su_ramdisk_max header field set to zero, and the code in core/runkernel.inc was limiting MyHighMemSize too early (before the load_high call used to load the main part of the kernel). Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- core/runkernel.inc | 13

I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from

Hi, in syslinux-386, I think I've found a problem in com32/lib/syslinux/load_linux.c that leads to cmdline being truncated unnecessarily when e.g. linux.c32 is used. The patch below fixes the problem for me. But I don't know, whether the patch is safe in all cases. I tried to reproduce the logic found in runkernel.inc, but I might have missed something. So, feel free to tell me

On 08/26/2014 04:34 AM, Stefan Hajnoczi wrote: > On Mon, Aug 25, 2014 at 8:42 PM, Chris Friesen > <chris.friesen at windriver.com> wrote: >> I'm trying to figure out if there are any limits on how high the inflight >> numbers can go, but I'm not having much luck. >> >> I was hopeful when I saw qemu calling virtio_add_queue() with a queue size, >>

On 08/26/2014 04:34 AM, Stefan Hajnoczi wrote: > On Mon, Aug 25, 2014 at 8:42 PM, Chris Friesen > <chris.friesen at windriver.com> wrote: >> I'm trying to figure out if there are any limits on how high the inflight >> numbers can go, but I'm not having much luck. >> >> I was hopeful when I saw qemu calling virtio_add_queue() with a queue size, >>

Hi, I'm running into some problems with libvirt and hoping someone can point me at some instructions or maybe even help me out. First, are there any requirements on qemu version in order to use the "numatune" and/or "cpu/numa/cell" elements? Or do they use cgroups and not the native qemu numa support? Second, are there any instructions on how to set up cgroups? I

Hi everyone, I'm working with libguestfs 1.30.3 on Centos 7 host. I encountered a problem when I wanted to install extlinux with guestfish as a bootloader for my guests and I always get this error: SYSLINUX 4.05 EDD 0x54f93f16 Copyright (C) 1994-2010 H. Peter Anvin et al ERROR: No configuration file found No default or UI configuration directive found! boot: _ *This is how I create the

Hi Michael, > > __u32 guest_cid; > > Given that cid is like an IP address, 32 bit seems too > limiting. I would go for a 64 bit one or maybe even 128 bit, > so that e.g. GUIDs can be used there. That's likely based on what vSockets uses, which is in turn based on what the VMCI device exposes (which is what vSockets was originally built on), so unfortunately

Hi Michael, > > __u32 guest_cid; > > Given that cid is like an IP address, 32 bit seems too > limiting. I would go for a 64 bit one or maybe even 128 bit, > so that e.g. GUIDs can be used there. That's likely based on what vSockets uses, which is in turn based on what the VMCI device exposes (which is what vSockets was originally built on), so unfortunately

Hello, I'm having a challenge with increasing vmalloc memory beyond 512M using pxelinux.0 to boot. This config works fine: --- # Configuration file # linux-2.6.20-1.2962.fc6 DEFAULT linux LABEL linux kernel kernels/vmlinuz-2.6.20-1.2962.fc6 append initrd=initrds/bladeinitrd-2.6.20-1.2962.fc6.img enforcing=0 vmalloc=512M --- If I increase vmalloc to 513M, I get errors

Split the vSockets header into kernel and UAPI parts. The former gets the bits that used to be in __KERNEL__ guards, while the latter gets everything that is user-visible. Tested by compiling vsock (+transport) and a simple user-mode vSockets application. Reported-by: David Howells <dhowells at redhat.com> Acked-by: Dmitry Torokhov <dtor at vmware.com> Signed-off-by: Andy King

Split the vSockets header into kernel and UAPI parts. The former gets the bits that used to be in __KERNEL__ guards, while the latter gets everything that is user-visible. Tested by compiling vsock (+transport) and a simple user-mode vSockets application. Reported-by: David Howells <dhowells at redhat.com> Acked-by: Dmitry Torokhov <dtor at vmware.com> Signed-off-by: Andy King

Stefan Hajnoczi <stefanha at redhat.com> writes: > From: Asias He <asias at redhat.com> > > Enable virtio-vsock and vhost-vsock. > > Signed-off-by: Asias He <asias at redhat.com> > Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> > --- > v3: > * Don't put vhost vsock driver into staging > * Add missing Kconfig dependencies (Arnd

Stefan Hajnoczi <stefanha at redhat.com> writes: > From: Asias He <asias at redhat.com> > > Enable virtio-vsock and vhost-vsock. > > Signed-off-by: Asias He <asias at redhat.com> > Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> > --- > v3: > * Don't put vhost vsock driver into staging > * Add missing Kconfig dependencies (Arnd

Minor vSockets fixes, two of which were reported on LKML. Andy King (2): VSOCK: Remove hypervisor-only socket option VSOCK: Don't reject PF_VSOCK protocol Dmitry Torokhov (2): VSOCK: get rid of EXPORT_SYMTAB VSOCK: get rid of vsock_version.h include/uapi/linux/vm_sockets.h | 8 -------- net/vmw_vsock/af_vsock.c | 7 ++----- net/vmw_vsock/vmci_transport.c | 2 --

Minor vSockets fixes, two of which were reported on LKML. Andy King (2): VSOCK: Remove hypervisor-only socket option VSOCK: Don't reject PF_VSOCK protocol Dmitry Torokhov (2): VSOCK: get rid of EXPORT_SYMTAB VSOCK: get rid of vsock_version.h include/uapi/linux/vm_sockets.h | 8 -------- net/vmw_vsock/af_vsock.c | 7 ++----- net/vmw_vsock/vmci_transport.c | 2 --

Fix return from execute() if type == KT_NONE. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> --- com32/elflink/ldlinux/execute.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c index f713eb1..899154c 100644 --- a/com32/elflink/ldlinux/execute.c +++ b/com32/elflink/ldlinux/execute.c @@ -108,7