Bug#721946: [Pkg-xen-devel] Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value

[Ian Campbell]

On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote:
 Package: xen-hypervisor-4.1-amd64
 Version: 4.1.4-3+deb7u1
 Severity: normal
 
 I tried GRUB_CMDLINE_XEN=dom0_mem=8192M:  that delivers 6964868K total, then
 crashes when used=2837436K free=4127432K.
 By crash I mean the gnome screen was blown away, replaced by a black screen
 with white log lines.  That seems to happen every time dom0 uses a large 
 amount
 of memory.

On a modern dom0 kernel you need to specify the maximum memory as well,
i.e. dom0_mem=8192M,max:8192M otherwise the kernel will attempt to
allocate enough page tables to cover all of *host* RAM which can exhaust
its actual memory allocation. You can of course also boot preballooned
e.g. dom0_mem=1G,max:4G but need to be mindful of the ratio between the
two.

http://blog.xen.org/index.php/2012/04/30/memory-where-it-has-not-gone/
has some background discussion.

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721946: [Pkg-xen-devel] Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value

[Ian Campbell]

On Fri, 2013-09-06 at 16:39 +0200, Alessandro Vesely wrote:

Both sets of log contain stuff like:

 Sep  6 15:22:53 pcale kernel: [  126.828195] ata4.00: exception Emask 0x0 
 SAct 0x0 SErr 0x8 action 0x6 frozen
 Sep  6 15:22:53 pcale kernel: [  126.828199] ata4: SError: { 10B8B }
 Sep  6 15:22:53 pcale kernel: [  126.828201] ata4.00: failed command: SMART
 Sep  6 15:22:53 pcale kernel: [  126.828205] ata4.00: cmd 
 b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
 Sep  6 15:22:53 pcale kernel: [  126.828206]  res 
 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 Sep  6 15:22:53 pcale kernel: [  126.828207] ata4.00: status: { DRDY }
 Sep  6 15:22:53 pcale kernel: [  126.828211] ata4: hard resetting link
 Sep  6 15:22:54 pcale kernel: [  127.320197] ata4: SATA link up 3.0 Gbps 
 (SStatus 123 SControl 300)
 Sep  6 15:22:54 pcale kernel: [  127.321358] ata4.00: configured for UDMA/133
 Sep  6 15:22:54 pcale kernel: [  127.336200] ata4: EH complete 

Is your disk dying?

Does this happen if you boot the exact same Linux kernel without Xen
underneath?

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721946: [Pkg-xen-devel] Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value

[Alessandro Vesely]

On Fri 06/Sep/2013 17:05:15 +0200 Ian Campbell wrote:
 
 Both sets of log contain stuff like:
 
 Sep  6 15:22:53 pcale kernel: [  126.828195] ata4.00: exception Emask 0x0 
 SAct 0x0 SErr 0x8 action 0x6 frozen
 Sep  6 15:22:53 pcale kernel: [  126.828199] ata4: SError: { 10B8B }
 Sep  6 15:22:53 pcale kernel: [  126.828201] ata4.00: failed command: SMART
 Sep  6 15:22:53 pcale kernel: [  126.828205] ata4.00: cmd 
 b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
 Sep  6 15:22:53 pcale kernel: [  126.828206]  res 
 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 Sep  6 15:22:53 pcale kernel: [  126.828207] ata4.00: status: { DRDY }
 Sep  6 15:22:53 pcale kernel: [  126.828211] ata4: hard resetting link
 Sep  6 15:22:54 pcale kernel: [  127.320197] ata4: SATA link up 3.0 Gbps 
 (SStatus 123 SControl 300)
 Sep  6 15:22:54 pcale kernel: [  127.321358] ata4.00: configured for UDMA/133
 Sep  6 15:22:54 pcale kernel: [  127.336200] ata4: EH complete 
 
 Is your disk dying?

Died already.  It was just an 80G Western Digital of 2005, but it
contained the Windows XP install that I wanted to run under Xen :-(

 Does this happen if you boot the exact same Linux kernel without Xen
 underneath?

Yes, but was never mounted.  Only update-grub reported read errors.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org