search for: grub_cmdline_xen_default

Hi! I''m experimenting with Xen 4 on Squeeze. Squeeze uses grub2 by default, and the config format has changed. I can''t for the life of me figure out where to set options for the hypervisor and the Dom0 kernel on bootup. It seems the grub2 stanza for xen is being generated by /etc/grub.d/20_linux_xen and that seems to have some provisions for receiving arguments, but I

...ing immediately after the Xen kernel load. Just to note this is a second system and not just the first system with an update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following /etc/sysconfig/grub line: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" But I've done that on other servers without issue. In fact I have a Dell R710 that DOES work with CentOS 7 and the new kernel... so confused. On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman <sr...

...e boots. Also there is nothing on the screen when I reboot. My /etc/default/grub is GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_CMDLINE_LINUX="crashkernel=auto rhgb intremap=no_x2apic_optout" GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=13312M,max:14336M dom0_max_vcpus=6 dom0_vcpus_pin" GRUB_GFXMODE=1024x768 GRUB_GFXPAYLOAD_LINUX=keep GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen nomodeset" I have tried setting (for a 1024x768 resolution) vga=792 in the GRUB_CMDLINE_LINUX a...

...'s your Xen command-line look like? The default should be > "console=com1,tty", so Xen's output should show up both places (and so > should Linux's if it's set to console=hvc0). > This is what's defined in /etc/default/grub following the install of the Xen: GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all" GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen nomodeset" I didn't set these myself, this is what the xen package (or one of its dependencies) is doing. I&...

Package: xen-hypervisor-4.5-amd64 Severity: normal Hi, when running xen inside of kvm the hypervisor fails to set up the proper IRQ routing and suggests to use noapic. If you add this via GRUB_CMDLINE_XEN_DEFAULT it will boot futher but then report that noapic isn't supported. So please make Xen not claim to support noapic if it doesn't (the issue was finally resolved by removeing all virtion devices and doubling the hypervisors RAM so the suggestion was misplaced anyways). Cheers, -- Guido

If this has already been done, please forgive me. However, if not, I''d like to submit this as a mechanism for generating a bootable grub2 stanza for hypervisors. As the /etc/grub.d/* files rely on defaults in /etc/default/grub, I added the following Xen specific variable: GRUB_CMDLINE_XEN_DEFAULT="console=com1 115200,8n1 dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin=true iommu=1,passthrough,no-intremap loglvl=all loglvl_guest=all loglevl=10 debug acpi=force apic=on apic_verbosity=verbose numa=on" The script itself is a hacked version of the10-linux that comes with grub2. This is...

...reen when I reboot. > > My /etc/default/grub is > > GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" > GRUB_DEFAULT=saved > GRUB_DISABLE_SUBMENU=true > GRUB_CMDLINE_LINUX="crashkernel=auto rhgb intremap=no_x2apic_optout" > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=13312M,max:14336M dom0_max_vcpus=6 > dom0_vcpus_pin" > GRUB_GFXMODE=1024x768 > GRUB_GFXPAYLOAD_LINUX=keep > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > nomodeset" > > I have tried setting (for a 1024x768 resolution...

...ion for Xen hypervisor console= parameter. That can be easily fixed in "/etc/sysconfig/grub", and executing "grub2-mkconfig -o /boot/grub2/grub.cfg" afterwards, but we should fix the default.. Here is the working setting (console=com1,vga, instead of console=com1,tty): # grep GRUB_CMDLINE_XEN_DEFAULT /etc/sysconfig/grub GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all" Thanks, -- Pasi

...reen when I reboot. > > My /etc/default/grub is > > GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" > GRUB_DEFAULT=saved > GRUB_DISABLE_SUBMENU=true > GRUB_CMDLINE_LINUX="crashkernel=auto rhgb intremap=no_x2apic_optout" > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=13312M,max:14336M dom0_max_vcpus=6 dom0_vcpus_pin" > GRUB_GFXMODE=1024x768 > GRUB_GFXPAYLOAD_LINUX=keep > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen nomodeset" > > I have tried setting (for a 1024x768 resolution) vga=792 in...

> This is what's defined in /etc/default/grub following the install of the > Xen: > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 > console=com1,tty loglvl=all guest_loglvl=all" > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > nomodeset" > > I didn't set these myself, this is what the xen package (or one of its &g...

Hi, Can someone help. Ive setup xen on a fresh build but are having problems setting up grub. Ive run update-grub which has scanned the /boot folder and created the entries in /boot/grub/grub.cfg but im not sure how to add the dom0_mem=512M parameter? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...ks on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum reinstall microcode_ctl (there were arguably better ways to do this part, but I cant recall) add ucode=scan to your GRUB_CMDLINE_XEN_DEFAULT line grub2-mkconfig to update your grub config reboot Once that's done, every time microcode_ctl updates, you'll get the microcode on the next reboot just like any other centos machine. Feel free to jump in if I missed any steps/caveats/notes, but that looks to be how I set it up on my...

On Wed, May 17, 2017 at 8:44 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Wed, May 17, 2017 at 4:20 PM, Jerry <jerryubi at gmail.com> wrote: > > This is what's defined in /etc/default/grub following the install of the > > Xen: > > > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo > com1=115200,8n1 > > console=com1,tty loglvl=all guest_loglvl=all" > > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > > nomodeset" > > > > I didn't set these myself, this is what the...

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

Hello Xen folks, I use Debian Squeeze. I want to passthrough PCI devices. With the old stable Debian (grub legacy) i did not have problems. I edit /etc/default/grub like: quote: GRUB_CMDLINE_XEN_DEFAULT="quiet xen-pciback.permissive xen-pciback.hide=(00:14.2)(01:05.1)" I run "update-grub". Now i look at /boot/grub/grub.cfg: ### BEGIN /etc/grub.d/20_linux_xen ### menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'' --class d...

...1 RIP [<ffffffff8103e527>] identify_secondary_cpu+0x57/0x80 RSP <ffffc900400b7f08> ---[ end trace dc5563100443876e ]--- I surmised that reducing the number of dom0 vcpu might solve this issue (they were unbounded) In testing adding "dom0_max_vcpus=4 dom0_vcpus_pin" to the GRUB_CMDLINE_XEN_DEFAULT line in /etc/defaults/grub and re-running grub2-mkconfig has resulted in the system I have that never booted Xen 4.6.3-12 + Kernel 4.9.13, booting every single time out of 5-10 tests. So...I don't know if there's a race condition somewhere, or what...but...so far this workaround has not f...

...d. Just to note this is a second system and not just the first > > system with an update. I hope I'm not introducing something odd. They > > only "interesting" thing I have done for historical reasons is to change > > the following /etc/sysconfig/grub line: > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1 > > console=com1,tty loglvl=all guest_loglvl=all" > > But I've done that on other servers without issue. In fact I have a Dell > > R710 that DOES work with CentOS 7 and the new kernel... so confused. > > > > On...

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the

...rom xen.git. Although maybe in a file which originates in Linux. (So now I realised I don't really know which entity was complaining) > > Did you also try the first thing it suggested? What was the result? > > > > > If you add this via > > > > > > GRUB_CMDLINE_XEN_DEFAULT > > > > > > it will boot futher but then report that noapic isn't supported. > > Don't add Linux command line options to the Xen command line. > > David > > _______________________________________________ > Xen-devel mailing list > Xen-devel at...

...say: panic("IO-APIC + timer doesn't work! Boot with apic_verbosity=debug " "and send a report. Then try booting with the 'noapic' option"); Did you also try the first thing it suggested? What was the result? > If you add this via > > GRUB_CMDLINE_XEN_DEFAULT > > it will boot futher but then report that noapic isn't supported. Is this the kernel saying that or Xen? Do you have full boot logs? I think it is the kernel since I can't find such a message in Xen and http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html says for th...