[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



Niels,

thanks but how can i access my domU kernel when it's not booting ? :-)
So, i sued what i had on hand which was the CDROM install kernel.

I traced the pygrub and here's what i can see .

open("/var/run/xen/bootloader.12.d/boot_kernel.OZNCPs", O_RDWR|O_CREAT|O_EXCL|O_NOFOLLOW, 0600) = 7
fcntl(7, F_GETFD) Â Â Â Â Â Â Â Â Â Â Â = 0
fcntl(7, F_SETFD, FD_CLOEXEC) Â Â Â Â Â = 0
mmap(NULL, 1052672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6ca10efe3000
pread(6, "MZ\352\7\0\300\7\214\310\216\330\216\300\216\3201\344\373\374\276@\0\254 \300t\t\264\16\273\7\0"..., 4096, 1118830592) = 4096
[...]
pread(6, "I\345\337\230o\243\346\327gb\242\226\362+\355\352:\21\315\264\250\241>l(\226 %J\374\304>"..., 4096, 1119875072) = 4096
write(7, "MZ\352\7\0\300\7\214\310\216\330\216\300\216\3201\344\373\374\276@\0\254 \300t\t\264\16\273\7\0"..., 1048576) = 1048576
mmap(NULL, 1052672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6ca10eee2000
pread(6, "f~\320v=E9AB\313\26\215\261\301\222\366\352\365\tz\373H\4\202\353\351%\202\303|\1\224"..., 4096, 1119879168) = 4096
[...] a bunch of pread of 6 intertwinedÂwithÂthe occasional write to 7 as above, and then at the endÂ
pread(6, "\301<\6\257\24\302\207\242y\362\3718\274\3506\360,\377i\207\374y\372[\\\10g\7\256,\3707"..., 4096, 2061225984) = 4096
mremap(0x6ca10efe3000, 1052672, 393216, MREMAP_MAYMOVE) = 0x6ca10efe3000
munmap(0x6ca10eee2000, 1052672) Â Â Â Â = 0
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)
writev(2, [{"", 0}, {"[Errno 28] No space left on devi"..., 34}], 2[Errno 28] No space left on device) = 34
writev(2, [{"", 0}, {"\n", 1}], 2
) Â Â Â= 1
close(7) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â= 0
unlink("/var/run/xen/bootloader.12.d/boot_ramdisk.Kop9GL") = 0
unlink("/var/run/xen/bootloader.12.d/boot_kernel.OZNCPs") = 0
writev(2, [{"", 0}, {"Error writing temporary copy of "..., 39}], 2Error writing temporary copy of ramdisk) = 39
writev(2, [{"\n", 1}, {NULL, 0}], 2
) Â Â= 1
munmap(0x6ca10efe3000, 393216) Â Â Â Â Â= 0
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x6ca1146d0190}, {0x6ca1143deb93, [], SA_RESTORER, 0x6ca1146d0190}, 8) = 0
close(6) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â= 0
close(4) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â= 0
close(5) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â= 0
exit_group(1) Â Â Â Â Â Â Â Â Â Â Â Â Â = ?
+++ exited with 1 +++


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

i dont know ifÂbefore upgrade my system was like that (i suspect it was but can't be certain) wrt to /var/run.

any chance this can be configured somewhere in pygrub ? or in the xl config file ?

On Tue, Apr 21, 2015 at 1:31 PM, Niels Dettenbach <nd@xxxxxxxxxxxx> wrote:
Am Dienstag, 21. April 2015, 12:57:26 schrieb Pierre Peyronnel:
> i tried to boot with a kernel and ramdisk line and it "looks" ok, but these
> are install kernel and ram disk, so it just prompts me for install...

I didn't mean any install kernel - just a (domU capable) linux (oder BSD)
kernel (i.e. the same kernel file as you use WITHIN the DomUs).

This should boot as before, except that you have to give kernel options by
your xen domu config instead of the grub-conf within your DomU (pygrub is'nt
used then). I.e. add a:

root="/dev/sda1 ro"
kernel="/full/path/to/myDomUsLinuxKernelFile"

(but make shure that the kernel file is not gzipped or similiar). If you need
a ramdisk, do the same with it (copy it to the Dom= and configure it in the
DomU config) like:
ramdisk = "/full/path/to/my/myDomUsLinuxRamdiskFileinitrd.gz"

but this could be zipped (if originally).

to your DomUs config when booting with "kernel=" from it - but use the correct
device path/node instead of /dev/sda1 in my case.

This should print out possibly more details from the DomUs side if not work
(or just work, if pygrub is the source of your problem here).


hth a bit.
best regards,


Niels.



--
Â---
ÂNiels Dettenbach
ÂSyndicat IT & Internet
Âhttp://www.syndicat.com
ÂPGP: https://syndicat.com/pub_key.asc
Â---





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.