[Fedora-xen] Strange Disk Goings On and No Console (Long)
Thomas J. Baker
tjb at unh.edu
Thu Dec 14 14:23:16 UTC 2006
I did a virt-manager install of FC6 on an FC6 host. I used a real disk
(/dev/sdw) for the disk. The install went fine. Upon reboot, I get a
pygrub error and the following xend-debug log entries:
[root at wintermute xen]# more xend-debug.log
Traceback (most recent call last):
File "/usr/bin/pygrub", line 489, in ?
g = Grub(file, isconfig)
File "/usr/bin/pygrub", line 147, in __init__
self.read_config(file, isconfig)
File "/usr/bin/pygrub", line 345, in read_config
raise RuntimeError, "Unable to read filesystem"
RuntimeError: Unable to read filesystem
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py",
line 77, in op_create
dominfo = self.xd.domain_create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
228, in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 195, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1290, in initDomain
self.configure_bootloader()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1756, in configure_bootloader
self.info['image'])
File "/usr/lib64/python2.4/site-packages/xen/xend/XendBootloader.py",
line 85, in bootloader
raise VmError, msg
VmError: Boot loader didn't return any data!
Traceback (most recent call last):
File "/usr/bin/pygrub", line 489, in ?
g = Grub(file, isconfig)
File "/usr/bin/pygrub", line 147, in __init__
self.read_config(file, isconfig)
File "/usr/bin/pygrub", line 345, in read_config
raise RuntimeError, "Unable to read filesystem"
RuntimeError: Unable to read filesystem
When I do an fdisk -l of the disk I just did the install on, it returns
an empty disk:
fdisk -l /dev/sdw
Disk /dev/sdw: 9105 MB, 9105018880 bytes
255 heads, 63 sectors/track, 1106 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
I go home for the night. I come back the next morning and try to start
the domain and it starts fine (except for a lack of console, more on
that later.) Then for grins, I look at the disk again:
fdisk -l /dev/sdw
Disk /dev/sdw: 9105 MB, 9105018880 bytes
255 heads, 63 sectors/track, 1106 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdw1 * 1 13 104391 83 Linux
/dev/sdw2 14 1106 8779522+ 8e Linux LVM
It shows the correct layout that the domain would have written to the
disk. Maybe I made a mistake. I don't know. So then I explode an RHEL5B2
tree to see if I can do a virt-manager install with it and it works
fine. I point it to a blank disk (/dev/sdx) and do a complete install.
Reboot and get the same pybrub errors. Look at the disk and it's showing
this disk as empty too.
fdisk -l /dev/sdx
Disk /dev/sdx: 50.0 GB, 50019202560 bytes
255 heads, 63 sectors/track, 6081 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
I remember the apparent lack of sync so I run sync a couple of times,
restart xend, all trying to get whatever has the disk data in memory
sync'd back out to disk. No luck. I go home and come back in this
morning and
fdisk -l /dev/sdx
Disk /dev/sdx: 50.0 GB, 50019202560 bytes
255 heads, 63 sectors/track, 6081 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdx1 * 1 13 104391 83 Linux
/dev/sdx2 14 6081 48741210 8e Linux LVM
Domain starts up fine again (except for the console.)
Any clue what's going on here?
As for the console, when I start either domain (FC6 or RHEL5B2), I don't
get a graphics console. Here is the dumpxml of the fc6 domain:
# virsh dumpxml doolittle.fc6
<domain type='xen' id='10'>
<name>doolittle.fc6</name>
<uuid>8a187e862a14669361a482be4df7135f</uuid>
<bootloader>/usr/bin/pygrub</bootloader>
<os>
<type>linux</type>
<kernel>/var/lib/xen/vmlinuz.h_sGDJ</kernel>
<initrd>/var/lib/xen/initrd.oSeDqz</initrd>
<cmdline>ro root=/dev/vgx0/root rhgb quiet</cmdline>
</os>
<memory>512000</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<interface type='bridge'>
<mac address='00:16:3e:5f:03:fd'/>
<script path='vif-bridge'/>
</interface>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sdw'/>
<target dev='xvda'/>
</disk>
<console tty='/dev/pts/1'/>
</devices>
</domain>
#
It seems to be define correctly:
# cat /etc/xen/doolittle.fc6
# Automatically generated xen config file
name = "doolittle.fc6"
memory = "500"
disk = [ 'phy:/dev/sdw,xvda,w', ]
vif = [ 'mac=00:16:3e:5f:03:fd, bridge=xenbr0', ]
vnc=1
vncunused=1
uuid = "8a187e86-2a14-6693-61a4-82be4df7135f"
bootloader="/usr/bin/pygrub"
vcpus=1
on_reboot = 'restart'
on_crash = 'restart'
#
Any clues on how to get a graphics console after an install?
Thanks,
tjb
--
=======================================================================
| Thomas Baker email: tjb at unh.edu |
| Systems Programmer |
| Research Computing Center voice: (603) 862-4490 |
| University of New Hampshire fax: (603) 862-1761 |
| 332 Morse Hall |
| Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb |
=======================================================================
More information about the Fedora-xen
mailing list