search for: ignore_loglevel

On 05/18/2015 01:02 PM, Jim Fehlig wrote: > On 05/18/2015 11:35 AM, Emma Anderson wrote: >> hi, >> >> I use xl toolstack to manage vms on a Xen machine, and also pass some >> custom parameters when creating a vm, for example: >> >> xl create vm.cfg ' param="xyz" ' > > Documentation on create subcommand in the xl man page describes the

...Any boot parameters, esp relating to ACPI, PM, or related? None for those, what's there that will be unfamiliar to you are for patches that aren't applied. nortsched hpc_cpusets skew_tick=1 ftrace_dump_on_oops audit=0 nodelayacct cgroup_disable=memory rtkthreads=1 rtworkqueues=2 panic=60 ignore_loglevel crashkernel=256M,high -Mike

.../* workaround for RHBZ#857026 */ #endif - " " SERIAL_CONSOLE /* serial console */ + " " SERIAL_CONSOLE /* serial console */ + EARLYPRINTK /* get messages from early boot */ #ifdef __aarch64__ - " earlyprintk=pl011,0x9000000 ignore_loglevel" + " ignore_loglevel" /* This option turns off the EFI RTC device. QEMU VMs don't * currently provide EFI, and if the device is compiled in it * will try to call the EFI function GetTime unconditionally -- 2.7.4

With this config: $ head -n2 isolinux/isolinux.cfg serial 0 9600 default vesamenu.c32 via the "Raw File Port Mode - VirtualBox" I got this: $ file /tmp/serial0.txt /tmp/serial0.txt: empty For the kernel log this in turn works OK: console=ttyS0 console=tty0 ignore_loglevel Is it really needed, exclusively a physical serial connection for the isolinux debug?

Hi, Now that the Arndale board is supported in upstream Xen I don''t get any output on the serial console. I followed the instructions on the wiki with no luck: The xen repository I''m using is: git://xenbits.xen.org/xen.git last commit: 61c6dfce3296da2643c4c4f90eaab6fa3c1cf8b3 The linux repository is: git://xenbits.xen.org/people/julieng/linux-arm.git last commit:

...oapic"); +#endif + + /* Serial console. */ + guestfs_int_add_string (g, &argv, SERIAL_CONSOLE); + +#ifdef EARLYPRINTK + /* Get messages from early boot. */ + guestfs_int_add_string (g, &argv, EARLYPRINTK); +#endif + +#ifdef __aarch64__ + guestfs_int_add_string (g, &argv, "ignore_loglevel"); + + /* This option turns off the EFI RTC device. QEMU VMs don't + * currently provide EFI, and if the device is compiled in it + * will try to call the EFI function GetTime unconditionally + * (causing a call to NULL). However this option requires a + * non-upstream patch. +...

...s), used 0 (slots) [ 32.178535] e1000 0000:00:03.0: TX DMA map failed my qemu command is like this: qemu-system-x86_64 --enable-kvm \ -m 2G,maxmem=16G -kernel /root/linux-next/$1/arch/x86/boot/bzImage \ -smp 4 \ -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ -net user,hostfwd=tcp::2222-:22 -net nic -s \ -object memory-backend-ram,id=mem0,size=3G \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ --nographic

...s), used 0 (slots) [ 32.178535] e1000 0000:00:03.0: TX DMA map failed my qemu command is like this: qemu-system-x86_64 --enable-kvm \ -m 2G,maxmem=16G -kernel /root/linux-next/$1/arch/x86/boot/bzImage \ -smp 4 \ -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ -net user,hostfwd=tcp::2222-:22 -net nic -s \ -object memory-backend-ram,id=mem0,size=3G \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ --nographic

...g to ACPI, PM, or related? > > None for those, what's there that will be unfamiliar to you are for > patches that aren't applied. > > nortsched hpc_cpusets skew_tick=1 ftrace_dump_on_oops audit=0 > nodelayacct cgroup_disable=memory rtkthreads=1 rtworkqueues=2 panic=60 > ignore_loglevel crashkernel=256M,high OK, thanks. So in other words, a fairly standard desktop with a PCIe board plugged in. No funny business. (Laptops can create a ton of additional weirdness, which I assumed you had since you were talking about STR.) My best guess is that gf119_head_vblank_put either has a bo...

...inux/isolinux.cfg > serial 0 9600 > default vesamenu.c32 > > via the "Raw File Port Mode - VirtualBox" > > I got this: > $ file /tmp/serial0.txt > /tmp/serial0.txt: empty > > > For the kernel log this in turn works OK: > console=ttyS0 console=tty0 ignore_loglevel > > > Is it really needed, exclusively a physical serial connection for the isolinux debug? > > Actually, ISOLINUX's "serial" directive works quite OK for both, VirtualBox and Virtual Machine Manager(virt-manager). virt-manager config example: - Serial Device 1 (...

...35] e1000 0000:00:03.0: TX DMA map failed > > my qemu command is like this: > qemu-system-x86_64 --enable-kvm \ > -m 2G,maxmem=16G -kernel /root/linux-next/$1/arch/x86/boot/bzImage \ > -smp 4 \ > -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ > -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ > -net user,hostfwd=tcp::2222-:22 -net nic -s \ > -object memory-backend-ram,id=mem0,size=3G \ > -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ > --nographic > > -- Thanks, David / dhilde...

On 30.06.2015 04:27, Gene Cumm wrote: > On Mon, Jun 29, 2015 at 6:20 PM, poma via Syslinux <syslinux at zytor.com> wrote: >> On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: >> >>> >>> It actuallly looks from Adam's investigation that this isn't different >>> for this package. So, less than certainly. It looks like maybe more a

...h the kernel, initrd and xen.efi files. > All in the same directory! > > Xen.cfg is fairly straightforward, I?ll just put mine here: > > [global] > default=debian8 > > [debian8] > options=console=vga,com1 com1=115200 loglvl=all noreboot > kernel=vmlinuz-3.14-2-amd64 ignore_loglevel root=/dev/mapper/clava-root ro quiet #earlyprintk=xen > ramdisk=initrd.img-3.14-2-amd64 Met vriendelijke groet, John Keates Keates Creative Technology 06 52 633 813 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signatur...

Greetings, I met $subject in master-rt post drm merge, but taking the config (attached) to virgin v4.12-10624-g9967468c0a10, it's reproducible. KERNEL: vmlinux-4.12.0.g9967468-preempt.gz DUMPFILE: vmcore CPUS: 8 DATE: Tue Jul 11 18:55:28 2017 UPTIME: 00:02:03 LOAD AVERAGE: 3.43, 1.39, 0.52 TASKS: 467 NODENAME: homer RELEASE:

On Sun, 2014-09-07 at 00:02 +0200, John Keates wrote: > How do I assist with getting this in for Jessie? > > I have this working in a fairly easy setup, it basically only requires > the pep target to be on for debian?s Xen package, What is "pep"? > and a tiny bit of infrastructure to get xen.efi, vmlinuz, an initrd > and a xen.cfg on to the ESP partition and letting

https://bugs.freedesktop.org/show_bug.cgi?id=69952 Priority: medium Bug ID: 69952 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA] Xorg crash+restart after glxgears on 3.12-rc2 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

...;ext2load mmc 0:1 $script_addr_r /load-xen-mmc.img''// // //setenv bootcmd ''run bootcmd_load_script_mmc; source $script_addr_r''// //setenv xen_bootargs ''sync_console console=dtuart dtuart=/serial@12C20000''// //setenv dom0_bootargs ''console=hvc0 ignore_loglevel psci=enable clk_ignore_unused root=/dev/mmcblk1p1 rw rootwait earlyprintk''/ Save the changes with saveenv and simply boot. At this point, I was able to launch the kernel and Xen successfully, and to log into the dom0. I couldn''t find any reference on the exact steps to follow...

...guration file needs to be on your ESP as well, with the kernel, initrd and xen.efi files. All in the same directory! Xen.cfg is fairly straightforward, I?ll just put mine here: [global] default=debian8 [debian8] options=console=vga,com1 com1=115200 loglvl=all noreboot kernel=vmlinuz-3.14-2-amd64 ignore_loglevel root=/dev/mapper/clava-root ro quiet #earlyprintk=xen ramdisk=initrd.img-3.14-2-amd64 And that?s it! Xen.efi now boots super-fast, dom0 gets booted really fast as well, everything is working! Now, instead of messing around in the UEFI setup ROM to create a boot entry, you might as well do it fro...

x86:x2apic: Disable x2apic on x86-32 permanently x2apic initialization on x86_32 uses vcpu pointer before it is initialized. As x2apic is unlikely to be used on x86_32, this patch disables x2apic permanently on x86_32. It also asserts the sanity of vcpu pointer before dereference to prevent further misuse. Signed-off-by: Fengzhe Zhang <fengzhe.zhang@intel.com> diff -r 02c0af2bf280

Hi Michael, On 11/27/18 5:53 PM, Michael S. Tsirkin wrote: > On Thu, Nov 22, 2018 at 07:37:54PM +0000, Jean-Philippe Brucker wrote: >> Implement the virtio-iommu driver, following specification v0.9 [1]. >> >> Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by >> from Eric and Rob. Thanks! >> >> I changed the specification to fix one