search for: 6144m

...mmand line is specifies a fixed dom0 memory allocation and noselfballooning is specified for the kernel and ballooning is also disabled in the xend-config.sxp / xl.conf (one system using xm, another xl) xen command line: placeholder xsave=0 iommu=0 console=vga,com2 com2=115200,8n1 dom0_mem=max:6144m kernel command line: root=/dev/loop0 ro console=tty1 console=hvc0 earlyprintk=xen nomodeset noselfballooning Examining /proc/iomem does show that the dom0 memory allocation is actually 64kb short of 6144Mb: cat /proc/iomem | grep System\ RAM 00010000-0009bfff : System RAM [573440 bytes] 0...

On Mon, Jan 22, 2018 at 10:38 PM, Nathan March <nathan at gt.net> wrote: > Just a heads up that I'm seeing major stability problems on these builds. > Didn't have console capture setup unfortunately, but have seen my test > hypervisor hard lock twice over the weekend. > > This is with xpti being used, rather than the shim. Thanks for the heads-up. It's been

...t;] kthread_data+0x10/0x20 [64929.010620] RSP <ffffc90048afbdd8> [64929.010626] CR2: ffffffffffffffd8 [64929.010638] ---[ end trace e1da1cdf77fed145 ]--- [64929.010647] Fixing recursive fault but reboot is needed! This is a centos 6 system booting with: kernel /boot/xen.gz dom0_mem=6144M,max:6144M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all msi=off com2=115200,8n1 console=com2,tty1 module /boot/vmlinuz-4.9.75-30.el6.x86_64 ro root=UUID=ffab1fdf-28a4-4239-b112-5e920e3d6c36 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crash...

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

...10620] RSP <ffffc90048afbdd8> > [64929.010626] CR2: ffffffffffffffd8 > [64929.010638] ---[ end trace e1da1cdf77fed145 ]--- > [64929.010647] Fixing recursive fault but reboot is needed! > > This is a centos 6 system booting with: > > kernel /boot/xen.gz dom0_mem=6144M,max:6144M cpuinfo com1=115200,8n1 > console=com1,tty loglvl=all guest_loglvl=all msi=off com2=115200,8n1 > console=com2,tty1 > module /boot/vmlinuz-4.9.75-30.el6.x86_64 ro > root=UUID=ffab1fdf-28a4-4239-b112-5e920e3d6c36 rd_NO_LUKS rd_NO_LVM > LANG=en_US.UTF-8 rd_NO_MD SYSFON...

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

The following two patches fixes / reimplements the oVirt appliance project, installing the entire oVirt stack including all server and node components on one machine. These patches are intended to be checked out and used to build the appliance rpm, after which it is installed provides the /usr/sbin/ovirt-appliance-ctrl script to install/uninstall the appliance. The first patch merely removes

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >