DomUdoes not start with Fedora-Xen-ia64
by jean-paul.pigache@bull.net
We want to test Fedora-Xen-ia64, but Domu does not start.
Here is a short description of the problem, and below a more detailed
description of the context.
DomU does not start:
-------------------
Xen30 has been installed from Aron Griffis repositories
(http://free.linux.hp.com/ãgriffis/agriffis-xen-ia64.repo)
on may the 24th.
File state:
vmlinuz-2.6.16-%3.2232_FC6agriffis.3xen0
xen.gz-2.6.16-%3.2232_FC6agriffis.3
initrd-2.6.16-%3.2232_FC6agriffis.3xen0.img
Dom0 starts successfully but we have no useful root console, but
we can connect by ssh.
Root console displayes some messages but we have no prompt
to connect.
The DomU is a clone of Dom0.
But it does not start. DomU console does not open, and
we do not know why.
Any idea of what the problem could be ?
We will make another try with a newest kernel.
Jean-Paul
Background information: here is a summary of the problems we faced before
getting Fedora-Xen running:
Fedora history :
Fedora Core 5:
----------------
Install with CDs built from iso files.
1- Graphic install KO and no switching to text mode.
So text mode only available because X server can not start:
/var/log/Xorg.0.log:
....
ATI Radeon X800 (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 XTP (R430)
(PCIE),
ATI Radeon X850 5D4C (PCIE), ATI Radeon FireGL (R480) GL
5D50(PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480)
(PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 XT PE (R480)
(AGP)
(II) Primary Device is: PCI 01:01:0
(II) ATI: Candidate "Device" section "Videocard0".
Fatal server error:
xf86MapVidMem: Could not mmap framebuffer (0xfbfd0000,0x4000) (Invalid
argument)
My video card is: 01:01.0 VGA compatible controller: ATI Technologies
Inc Rage XL (rev 27)
Bypass proposed by Tony Luck does not work.
Patch of Bjorn Helgaas does not work too (not applicable because
different sources)
NOTE: Same problem occurs with Rawhide ia64 from 27 April. When system is
running, X server
can not start for the same reason.
2- hwclock can not be set when linux starts.
hwclock: Open of /dev/efirtc failed, errno=2. No such file or
directory.
No usabel clock interface found.
Cannot access the Hardware Clock in any known method.
Problem seems to be located in /etc/rc.sysinit file where hardware clock
is set before device creation (/sbin/start_udev step).
When hardware clock setting step is done after device creation, hwclock
gives right remanent time information.
3- After Dependencies checking and install beginning, an exception
occurred.
Messages are:
Traceback (most recent call last):
File "/usr/bin/anaconda", line 1080, in ?
intf.run(id, dispatch)
File "/usr/lib/anaconda/test.py", line513 in run
rc=apply(win,(self.screen, )+ args)
File "/usr/lib/anaconda/textw/confirm_text.py", line 32 in __call__
rc=present.requiredMediaMessage (intf, id.grpset)
Attribute error: installData Instance has no attribute 'grpset'
Fedora weekly 05142006 : install withCDs built from iso files
---------------------------------------------------------------
Install in graphic mode does not work but install switches to text mode.
1- Graphic install still KO and switch to text mode.
( message 'module libXau.so.6 not found" in /tmp/X.log file'
I don't investigate this problem further more and hope that library name
is
correct.)
2- In Partionning step, when 'Create custom Layout' option is choosen
/boot/efi partition can not be created (Mounting point already in use).
Partitionning has been made using 'Default layout creation' choice.
3- In Network Configuration for Eth0, when 'Configure using DHCP' default
option is unset, given IP address is declared as invalid.
Information message is:
'You must enter a valid IP address to continue.'
When active on boot is not selected and others network adapters not
configured, exception occurs in:
anaconda.intf.run at line 938:
ns1Entry.set (network.primaryNS
NameError: global name 'network' is not defined.
4- With default configuration options for network adapters, setup goes
on
and aborts
5- After Dependencies checking and install beginning, an exception
occurred.
Traceback (most recent call last):
File "/usr/bin/anaconda", line 1080, in ?
intf.run(id, dispatch)
File "/usr/lib/anaconda/test.py", line513 in run
rc=apply(win,(self.screen, )+ args)
File "/usr/lib/anaconda/textw/confirm_text.py", line 32 in __call__
rc=present.requiredMediaMessage (intf, id.grpset)
Attribute error: installData Instance has no attribute 'grpset'
Choice is then : OK to reboot, or Debug to enter in anaconda debugging
mode.
Fedora weekly 04252006: install with http method (vnc askmethod)
---------------------------------------------------------------------
Come back on previous weekly because network configuration problems
1- Graphic install still KO and switch to text mode.
2- After language selection, an error occurrs:
'Failed to read keymap information:
Success'
Only choice is OK and install goes on
Default options are kept and install ends.
Warnings :
- install from CDs built from iso files does not work in any case
- don't choose CD-Rom test: it leads to finally reboot
17 years, 10 months
FC6 VNC issue
by Zhang, Xiantao
Hi all,
We met vnc server issue in FC6-ia64. Seems VNC server in FC6 has
some bugs so as not to connect it. After reversing to FC5's VNC
package(4.1.1-36), we solved this issue with this method. So currently,
we can use this version for Xen's development.
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
17 years, 10 months
keyboard error
by Manogna Ramakrishna Chebiyyam
hi,
i had domain 0 already installed on my PC..
i was installing FC5 on my PC from CD's without disturbing the grub..
i chose /dev/VolGroup00/LogVol00 for / and /boot was in /dev/sda5..
and now i am not able to login in domain 0 because my keyboard and mouse is not responding..
they are in perfect working condition by the way..
please help!!!!!!!!!!!!
Manogna
Employee ID-53967
High Performance Computing
SETLabs
Infosys Technologies Limited
Bangalore
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
17 years, 10 months
[PATCH] make fedaro-kernel-ia64 build pass
by Zhang, Xiantao
Hi, Aron
Since ioremap has been implemented @/arch/kernel/mm/ioremap.c
separately in kernel 2.6.17. We can remove it from io.h safely. This fix
makes kernel rpm package build successfully.
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
17 years, 10 months
RE: [Fedora-xen] Fedora Xen/IA64 status page
by Zhang, Xiantao
Hi, Aron
I have tried linux-2.6.tip-xen, and build successfully after some fixes. But I don't know which CSet it based, so the hypervisor couldn't be built to boot this kernel, Could you give some tips ?
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
> -----Original Message-----
> From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com]
> On Behalf Of Aron Griffis
> Sent: 2006年6月14日 5:23
> To: fedora-xen(a)redhat.com
> Subject: [Fedora-xen] Fedora Xen/IA64 status page
>
> I created a wiki page to track Fedora Xen/IA64 work items and status.
> For anybody interested:
>
> http://wiki.xensource.com/xenwiki/FedoraXenIA64
>
> Aron
17 years, 10 months
Multiple Xens with static IP addresses
by Chris Vaughan
I am wanting to boot multiple xen images but I was wondering if there is an
easier way to set it's ip address than mounting the image and editing
/etc/sysconfig/network-scripts/ifcfg-eth0 every time.
I've tried putting this in my xen.cfg file vif=['192.168.0.3'] and it
doesn't appear to do anything. Is this the correct way to boot a xen image
and assign it a static ip address?
Thanks,
--
------------------------------
Christopher Vaughan
17 years, 10 months
RE: [Fedora-xen] Exporting "SD" device.
by You, Yongkang
Priya,
HVM QEMU doesn’t support emulate SCSI device. So you have to use the IDE device. Your first configuration is correct.
Best Regards,
Yongkang (Kangkang) 永康
________________________________
From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of P M, Priya
Sent: 2006年6月14日 3:05
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] Exporting "SD" device.
Hi,
We have Intel VT enabled system loaded with Xen 3.0.2 and qemu based FC5+linux 2.6.16 as a guest operating system. We want to export the disk to the domain 1 (FC5_linux 2.6.16) as "SD" device. But we are not able to export the SCSI disk as a SD device, we could export as a "HD" device.
In the Configuration file,
disk = [ 'file:/home/adteam/linux_fc5_2.6.16,ioemu:hda,w','phy:/dev/sdd,ioemu:hdb,w' ]
if we use ioemu:hdb, then the device is exported to the domain 1 and we could see the device.
If we use
disk = [ 'file:/home/adteam/linux_fc5_2.6.16,ioemu:hda,w','phy:/dev/sdd,/dev/sdb,w' ]
/dev/sdb, then the device is not seen on domain 1.
Are we missing something. Is it not possible to export an SD device to domain 1? Is there any limitiation in qemu based domain 1, because our domain 0 is qemu based operating system.
Is there any performance difference between "hda" and "sda" exported devices???
Thanks.
17 years, 10 months
[RFC] Extending xenguest-install.py
by Gawain Lynch
The attached patch adds the following options to the xenguest-install.py
script:
-U, --genuuid Generate a random UUID and exit
-M, --genmac Generate a random MAC address and exit
-C CONFOUT, --genconf=CONFOUT
Generate a template guest config file
Is this something that people think might be useful? If so I'll raise
an RFE in bugzilla.
Take care,
Gawain
17 years, 10 months
Exporting "SD" device.
by P M, Priya
Hi,
We have Intel VT enabled system loaded with Xen 3.0.2 and qemu based
FC5+linux 2.6.16 as a guest operating system. We want to export the disk
to the domain 1 (FC5_linux 2.6.16) as "SD" device. But we are not able
to export the SCSI disk as a SD device, we could export as a "HD"
device.
In the Configuration file,
disk = [
'file:/home/adteam/linux_fc5_2.6.16,ioemu:hda,w','phy:/dev/sdd,ioemu:hdb
,w' ]
if we use ioemu:hdb, then the device is exported to the domain 1 and we
could see the device.
If we use
disk = [
'file:/home/adteam/linux_fc5_2.6.16,ioemu:hda,w','phy:/dev/sdd,/dev/sdb,
w' ]
/dev/sdb, then the device is not seen on domain 1.
Are we missing something. Is it not possible to export an SD device to
domain 1? Is there any limitiation in qemu based domain 1, because our
domain 0 is qemu based operating system.
Is there any performance difference between "hda" and "sda" exported
devices???
Thanks.
17 years, 10 months