search for: bootscrub

..., with Xen hypervisor"/'' /etc/default/grub sed -i ''s/GRUB_CMDLINE_LINUX=.*\+/GRUB_CMDLINE_LINUX="apparmor=0"/'' /etc/default/grub sed -i ''/GRUB_CMDLINE_LINUX="apparmor=0"/ a\GRUB_CMDLINE_XEN="dom0_mem=384M,max:384M dom0_max_vcpus=1 no-bootscrub"'' /etc/default/grub update-grub echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab reboot After the reboot - $ ls /proc/xen capabilities privcmd xenbus xsd_kva xsd_port $ cat /proc/xen/capabilities control_d $ xl info libxl: error: libxl.c:87:libxl_ctx_all...

Dear George, Thanks for the input and ideas. Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! I am asking the xen-users as you suggest Regards, Francis From: "George Dunlap" <dunlapg at umich.edu> To: "Francis Greaves" <francis at choughs.net>, "cent...

On Wed, May 25, 2011 at 12:41 AM, JAMES BOND 123 007 <james123007@gmail.com> wrote: > Hi , > I saw your thread post at > http://web.archiveorange.com/archive/v/ZvO4jnaavtTfcyqnHoRX > , about problems with XEN 4.0 installation. > I have the same problem and my machine is similar to yours( HP Proliant > DL380G6, 4GB-RAM) This question is better asked on the xen-users list.

Hi everyone, I am working on a project whose goal is evaluating the performance of the vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13 with Fedora11. I I finished all installation and configuration parts. Now I need to boot the system with Xen but while booting, it is freezing at the step "scrubbing free ram". What can be cause this problem and how can I figure it

Hi everyone, I am working on a project whose goal is evaluating the performance of the vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13 with Fedora11. I I finished all installation and configuration parts. Now I need to boot the system with Xen but while booting, it is freezing at the step "scrubbing free ram". What can be cause this problem and how can I figure it

On Tue, 23 Feb 2016 14:40, Francis Greaves wrote: > Dear George, > Thanks for the input and ideas. > Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! > I am asking the xen-users as you suggest > Regards, Francis > > > From: "George Dunlap" > To: "Francis Greaves" , "centos-virt" > Sent: Tuesday,...

...86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Tue Apr 10 10:50:08 2012 +0200 12:efd10c64454c xen_commandline : auto BOOT_IMAGE=user-xen root=801 placeholder no-bootscrub dom0_mem=4096M dom0_max_vcpus=16 dom0_vcpus_pin root=/dev/sda1 noreboot cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) To avoid as much noise as possible I''ve got a kernel module in which I''m performing the following straight forward test: for (j = 2; j...

Dear All I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 When the machine boots, after the 'Scrubbing Free RAM' message, I get a screen filled with little white squares until the login prompt, so I cannot see what is happening as the machine boots. Also there is nothing on the screen when I reboot. My /etc/default/grub is GRUB_DISTRIBUTOR="$(sed 's, release

...ace `badpage=0x12345` on Xen''s command line. +Specify that certain pages, or certain ranges of pages contain bad +bytes and should not be used. For example, if your memory tester says +that byte `0x12345678` is bad, you would place `badpage=0x12345` on +Xen''s command line. ### bootscrub ### cachesize @@ -108,9 +137,11 @@ Specify that certain pages, or certain r Both option `com1` and `com2` follow the same format. -* `<baud>` may be either an integer baud rate, or the string `auto` if the bootloader or other earlier firmware has already set it up. +* `<baud>` may...

...M and 64G,max:64G ( At the beginning in Steps of 256M and at the end in Steps of 2G) ... makes no difference mem : diffent Values between 512M and 64G ( like dom0_mem or a little bit higher) ... makes no difference dom0_max_vcpus=1 dom0_vcpus_pin : with and without .... makes no difference no-bootscrub : with or without ... the only difference is that the Scubbing Free RAM Message and the dots afterwards are disappearing ... the crash/reboot is happening at the same Position noreboot: with or without ... no difference ... with the System hangs with a blank screen and needs a hardware-reset...