[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] VM won't start after a shutdown


  • To: xen-api@xxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Fri, 08 Mar 2013 15:33:01 +0400
  • Delivery-date: Fri, 08 Mar 2013 11:33:36 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

Looks really strange.

1. Check which disk is bootable. (xe vbd-list vm-uuid=... params=all and check bootable flag).
2. Try to play with xe-bootloader-edit to see if you can easy access to grub.cfg.
3. Attach vdi to dom0 and perform fsck on /boot (or root).

That bug is related to pygrub, not to xcp (but pygrub is the part of the XCP, yep).

On 08.03.2013 13:57, Tom Luong wrote:

Â

I was in the process of moving a VM from a XCP 1.1 to XCP 1.6 host. I shut down the VM and exported it and then imported it to the new host. Everything went fine until I try to boot the VM. Any help or advise is much appreciated.

Â

Hereâs problem 1:

Thereâs the error when I try to boot the VM on the new XCP 1.6 host. ÂHas anyone seen this?

Â

[root@xen65 ~]# xe vm-start vm=srch-plgr00

The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.

message: xenopsd internal error: VM = b5de268f-9c4c-239f-1980-de12010ecfa4; domid = 15; Bootloader.Bad_error Using <class 'grub.GrubConf.GrubConfigFile'> to parse /grub/menu.lst

Traceback (most recent call last):

 File "/usr/bin/pygrub", line 962, in ?

ÂÂÂ not_really)

 File "/usr/bin/pygrub", line 782, in copy_from_image

ÂÂÂ data = "" dataoff)

IOError: [Errno 22] Invalid argument

Â

Â

Hereâs problem 2:

I tried to boot the VM in the original XCP 1.1 host, and it still wonât start. I have seen many posts state boot issues after a kernel update relating to pygrub. However, I didnât do any kernel update, and this looks like an invalid argument in âramdisk.â ÂÂÂ

Â

[root@xen04 ~]# xe vm-start vm=srch-plgr00

Error code: Traceback (most recent call last):

Error parameters:ÂÂ File "/usr/bin/pygrub", line 768, in ?,ÂÂÂÂ data = "" IOError: [Errno 22] Invalid argument,

Â

I compared grub.conf to a known good bootable VM on the same host, and it looks the same. I donât see anything wrong ramdisk(initrd) parameter.

Â

[root@xen04 ~]# xe-edit-bootloader -n srch-plgr00 -p 1

# grub.conf generated by anaconda

#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

#ÂÂÂÂÂÂÂÂÂ all kernel and initrd paths are relative to /boot/, eg.

#ÂÂÂÂÂÂÂÂÂ root (hd0,0)

#ÂÂÂÂÂÂÂÂÂ kernel /vmlinuz-version ro root=/dev/xvda3

#ÂÂÂÂÂÂÂÂÂ initrd /initrd-[generic-]version.img

#boot=/dev/xvda

default=0

timeout=5

splashimage=(hd0,0)/grub/splash.xpm.gz

hiddenmenu

title Red Hat Enterprise Linux (2.6.32-220.4.2.el6.x86_64)

ÂÂÂÂÂÂÂ root (hd0,0)

ÂÂÂÂÂÂÂ kernel /vmlinuz-2.6.32-220.4.2.el6.x86_64 ro root=UUID=9caebb06-8102-4158-853f-7f07e66daefa rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFO$

 ÂÂÂÂÂÂinitrd /initramfs-2.6.32-220.4.2.el6.x86_64.img

Â

I tried without success to change the PV-bootable-args to see if that works.

xe vm-param-set uuid=738e0e50-c579-b35f-a8e1-d03d23274a50 PV-bootloader-args="--kernel=/vmlinuz-2.6.32-220.4.2.el6.x86_64 --ramdisk=/initramfs-2.6.32-220.4.2.el6.x86_64.img"

Â

Hereâs the params for my VM on the original XCP 1.1 host.

[root@xen04 ~]# xe vm-list params=all name-label=srch-plgr00

uuid ( RO)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ : 738e0e50-c579-b35f-a8e1-d03d23274a50

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ name-label ( RW): srch-plgr00

ÂÂÂÂÂÂÂÂÂÂÂÂÂ name-description ( RW): Installed via xe CLI

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ user-version ( RW): 1

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ is-a-template ( RW): false

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ is-a-snapshot ( RO): false

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ snapshot-of ( RO): <not in database>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ snapshots ( RO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ snapshot-time ( RO): 19700101T00:00:00Z

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ snapshot-info ( RO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ parent ( RO): c94549a7-a39e-cca7-b347-458f9e3cfc8c

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ children ( RO):

ÂÂÂÂÂÂÂÂÂÂÂÂ is-control-domain ( RO): false

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ power-state ( RO): halted

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ memory-actual ( RO): 25769803776

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ memory-target ( RO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ memory-overhead ( RO): 38797312

ÂÂÂÂÂÂÂÂÂÂÂÂ memory-static-max ( RW): 536870912

ÂÂÂÂÂÂÂÂÂÂÂ memory-dynamic-max ( RW): 536870912

ÂÂÂÂÂÂÂÂÂÂÂ memory-dynamic-min ( RW): 536870912

ÂÂÂÂÂÂÂÂÂÂÂÂ memory-static-min ( RW): 512000

ÂÂÂÂÂÂÂÂÂÂÂÂÂ suspend-VDI-uuid ( RO): <not in database>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ VCPUs-params (MRW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ VCPUs-max ( RW): 32

ÂÂÂÂÂÂÂÂÂÂÂÂÂ VCPUs-at-startup ( RW): 8

ÂÂÂÂÂÂÂ actions-after-shutdown ( RW): Destroy

ÂÂÂÂÂÂÂÂÂ actions-after-reboot ( RW): Restart

ÂÂÂÂÂÂÂÂÂÂ actions-after-crash ( RW): Restart

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ console-uuids (SRO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ platform (MRW): nx: false; acpi: true; apic: true; pae: true; viridian: true

ÂÂÂÂÂÂÂÂÂÂÂ allowed-operations (SRO): changing_dynamic_range; changing_static_range; make_into_template; destroy; export; start_on; start; clone; copy; snapshot

ÂÂÂÂÂÂÂÂÂÂÂ current-operations (SRO):

ÂÂÂÂÂÂÂÂÂÂÂ blocked-operations (MRW):

ÂÂÂÂÂÂÂÂÂÂ allowed-VBD-devices (SRO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂ allowed-VIF-devices (SRO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ possible-hosts ( RO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ HVM-boot-policy ( RW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ HVM-boot-params (MRW):

ÂÂÂÂÂÂÂÂ HVM-shadow-multiplier ( RW): 1.000

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ PV-kernel ( RW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ PV-ramdisk ( RW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ PV-args ( RW): ks=http://cobbler.sv.walmartlabs.com/cblr/svc/op/ks/system/srch-plgr00 ksdevice=eth0 noipv6 utf8

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂPV-legacy-args ( RW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ PV-bootloader ( RW): pygrub

ÂÂÂÂÂÂÂÂÂÂÂ PV-bootloader-args ( RW):

ÂÂÂÂÂÂÂÂÂÂ last-boot-CPU-flags ( RO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂ last-boot-record ( RO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ resident-on ( RO): <not in database>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ affinity ( RW): <not in database>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ other-config (MRW): last_shutdown_time: 20130307T17:41:35Z; last_shutdown_action: Destroy; last_shutdown_initiator: external; last_shutdown_reason: halted; install-repository: http://cobbler.sv.walmartlabs.com/cblr/links/rhel6-x86_64/; mac_seed: 44d1fb0d-e05a-6349-784c-3672bc70f7d9; linux_template: true; install-methods: cdrom,nfs,http,ftp; rhel6: true

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ dom-id ( RO): -1

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ recommendations ( RO): <restrictions><restriction field="memory-static-max" max="17179869184" /><restriction field="vcpus-max" max="8" /><restriction property="number-of-vbds" max="7" /><restriction property="number-of-vifs" max="7" /></restrictions>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ xenstore-data (MRW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ha-always-run ( RW): false

ÂÂÂÂÂÂÂÂÂÂ ha-restart-priority ( RW):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ blobs ( RO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ start-time ( RO): 20121231T18:56:47Z

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Âinstall-time ( RO): 20120321T02:45:09Z

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ VCPUs-number ( RO): 8

ÂÂÂÂÂÂÂÂÂÂÂÂ VCPUs-utilisation (MRO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ os-version (MRO): name: Red Hat Enterprise Linux Server release 6.2 (Santiago); uname: 2.6.32-220.4.2.el6.x86_64; distro: rhel; major: 6; minor: 2

ÂÂÂÂÂÂÂÂÂÂÂ PV-drivers-version (MRO): major: 5; minor: 6; micro: 100; build: 47383

ÂÂÂÂÂÂÂÂ PV-drivers-up-to-date ( RO): true

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ memory (MRO):

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ disks (MRO):

ÂÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂnetworks (MRO): 0/ip: 10.93.11.37

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ other (MRO): platform-feature-multiprocessor-suspend: 1; feature-balloon: 1

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ live ( RO): true

ÂÂÂ guest-metrics-last-updated ( RO): 20130303T12:23:06Z

ÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂcooperative ( RO): <expensive field>

ÂÂÂÂÂÂÂÂÂÂÂÂ protection-policy ( RW): <not in database>

ÂÂÂÂÂÂÂÂ is-snapshot-from-vmpp ( RO): false

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ tags (SRW):

Â

Â

Â



_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

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