[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen 4.3.3 -> 4.4.1 after dom0 upgrade : domU refuses to boot
On Tue, 2015-04-21 at 13:48 +0200, Pierre Peyronnel wrote: > open("/var/run/xen/bootloader.12.d/boot_kernel.OZNCPs", > O_RDWR|O_CREAT|O_EXCL|O_NOFOLLOW, 0600) = 7 [...] > write(7, "x'] > b\250Y\225\201&EY\306x\16\366\260F\207\1-\tq\265\350\n\232\334\310\270\224\6"..., > 389104) = -1 ENOSPC (No space left on device) [...] > The thing is that partition has... > wait i found it... it's writing to /var/run which is symlinked to /run > which on tmpfs and is about 13MB Right, this is what I was just about to suggest. > i dont know if before upgrade my system was like that (i suspect it > was but can't be certain) wrt to /var/run. It's the sort of thing some distros have been transitioning recently, so it may well have changed in the upgrade. > any chance this can be configured somewhere in pygrub ? or in the xl > config file ? AFAIK it is a compile time option only, so you'd need to rebuild. 13MB is pretty meagre for /var/run though, on Debian mine is a 700MB ramdisk for example... Ian. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |