Re: [Xen-users] xen 4.3.3 -> 4.4.1 after dom0 upgrade : domU refuses to boot

[Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx>]

Hello Niels,

the bootloader.log is really just a reproduction of the console, here goes a "cat":

Ââ Debian GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode) Â Â Â Â Â Â â
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Ââ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ââ
Âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.


  ÂWill boot selected entry in Â3 seconds

Traceback (most recent call last):
 File "/usr/lib/xen/bin/pygrub", line 921, in <module>
  os.write(fd, ostring)
OSError: [Errno 28] No space left on device

Here is one of the domU config file :

name = "debiantest"
memory = "2048"
disk = [ 'file:/vmdisks/debian_new.dsk,xvda,w', ]
##vif = [ 'bridge=br0','bridge=xenbr1' ]
vif = [ 'bridge=br0' ]
bootloader="pygrub"
vcpus=1

I'm not familiar at all with the non-pygrub syntax, I have to look that up before testing...

Pierre

On Mon, Apr 20, 2015 at 7:42 PM, Niels Dettenbach (Syndicat IT & Internet) <nd@xxxxxxxxxxxx> wrote:

Am 20. April 2015 19:14:55 MESZ, schrieb Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx>:
>- consult logfile /var/log/xen/bootloader.3.log
What does this logfile consist?

>[Errno 28] No space left on device
>Error writing temporary copy of ramdisk
Could you try to boot your DomU by test without pygrub just with a external kernel= file and check log output?

It seems that the virtual disk could not be mounted rw by the DomU or something similiar. To find reasons or possibly required kernel options we should know what type of disk your domU is using (ideally the complete domU config).

hth a bit
cheerioh,


Niels.
--
Niels Dettenbach
Syndicat IT & Internet
http://www.syndicat.com

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