Re: [Savannah-hackers-public] Next Savannah VM system upgrade - internal

[Bob Proulx]

The VM internal has been upgraded.  For the most part everything is
happy and working fine.  Please let me know if there are any problems.

Here are the issues I know about and am continuing to work through.

Problem 1:

  internal:~# debsums -c
  /lib/modules/2.6.26-2-xen-686/modules.symbols
  /lib/modules/2.6.26-2-xen-686/modules.pcimap
  /lib/modules/2.6.26-2-xen-686/modules.dep
  /lib/modules/2.6.26-2-xen-686/modules.usbmap
  /lib/modules/2.6.26-2-xen-686/modules.isapnpmap
  /lib/modules/2.6.26-2-xen-686/modules.inputmap
  /lib/modules/2.6.26-2-xen-686/modules.alias
  /lib/modules/2.6.26-2-xen-686/modules.seriomap
  /lib/modules/2.6.26-2-xen-686/modules.ieee1394map
  debsums: missing file /var/lib/pcp/pmns/.NeedRebuild (from pcp package)

There are two separate complains.  I have no idea why the above is
complaining for the kernel package.  The pcp complaint just looks like
a simple package bug.

Problem 2:

  internal:~# dpkg-reconfigure grub-pc
  /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition 
device /dev/xvda2.
  /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition 
device /dev/xvda2.
  /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition 
device /dev/xvda2.
  /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition 
device /dev/xvda2.
  /usr/sbin/grub-setup: warn: disk does not exist, so falling back to partition 
device /dev/xvda2.
  /usr/sbin/grub-setup: error: cannot guess the root device. Specify the option 
`--root-device'.

I imagine this problem is due to it being a Xen domU.  The previous VM
mgt doesn't have grub installed.  I chatted with Ward and he says that
the dom0 will bootstrap the xen domU based upon the presence of the
menu.lst file.  Therefore I think internal needs the same treatment as
mgt.  Meaning that I think grub needs to be purged off leaving only
the menu.lst file for the dom0 to boot.

Bob