Xen users - Jul 2008 - Re: Finally got CentOS installed as domU on SLES10SP2dom0, but....

This seems to be a bug in SLES10 SP2 - you need to edit the /etc/xen/vm/<domU
Name> file and add the line:
root="/dev/<root dev> ro" 

So, if you''re domU is call centos and your root dev is /dev/xvda1, add
the line as follows to the /etc/xen/vm/centos file:
root="/dev/xvda1 ro" 

-Nick
>>> On Fri, Jul 25, 2008 at  8:23 AM, James Pifer
<jep@obrien-pifer.com> wrote:
On Fri, 2008-07-25 at 08:54 -0500, Steven Timm wrote:
> The stage that the error happens at looks like it is trying to mount
> the root device and not finding it.  Are you sure the root device is
> specified correctly in the config file?
>
> Steve Timm
>
Honestly no, I''m not sure, but the install itself ran fine. How do I
verify it?

Thanks,
James






This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Fri, 2008-07-25 at 10:26 -0600, Nick Couchman wrote:
> root="/dev/xvda1 ro"
Okay, that worked. Mine was xvda3.

Thanks!!!!

James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Fri, 2008-07-25 at 10:26 -0600, Nick Couchman wrote:
> This seems to be a bug in SLES10 SP2 - you need to edit
> the /etc/xen/vm/<domU Name> file and add the line: 
> 
> root="/dev/<root dev> ro" 
> 
> 
> So, if you''re domU is call centos and your root dev is /dev/xvda1,
add
> the line as follows to the /etc/xen/vm/centos file: 
> 
> root="/dev/xvda1 ro" 
> 
> 
This worked on my SLES10SP2 machine. I transferred it to a SLES10SP1
server and have the exact same problem. Modifying the config file did
not work this time. Should it work on SP1?

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

As far as I know it should work on SLES10SP1, yes.  When you transferred it to
the SLES10SP1 machine, did the path to the disk file change and did you make
sure to change it the config file?
>>> On 2008/08/02 at 16:49, James Pifer <jep@obrien-pifer.com>
wrote:
On Fri, 2008-07-25 at 10:26 -0600, Nick Couchman wrote:
> This seems to be a bug in SLES10 SP2 - you need to edit
> the /etc/xen/vm/<domU Name> file and add the line: 
> 
> root="/dev/<root dev> ro" 
> 
> 
> So, if you''re domU is call centos and your root dev is /dev/xvda1,
add
> the line as follows to the /etc/xen/vm/centos file: 
> 
> root="/dev/xvda1 ro" 
> 
> 
This worked on my SLES10SP2 machine. I transferred it to a SLES10SP1
server and have the exact same problem. Modifying the config file did
not work this time. Should it work on SP1?

Thanks,
James



This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, 2008-08-02 at 16:52 -0600, Nick Couchman wrote:
> As far as I know it should work on SLES10SP1, yes.  When you
> transferred it to the SLES10SP1 machine, did the path to the disk file
> change and did you make sure to change it the config file?
> 
Yes, and it actually tries to boot, I just get the exact same error as
before:
 # xm create server04;xm console server04
Using config file "./server04".
Started domain server04
Bootdata ok (command line is TERM=xterm )
Linux version 2.6.18-92.el5xen (mockbuild@builder10.centos.org) (gcc
version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Jun 10 19:20:18
EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 00000000c0800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 788480
Kernel command line: TERM=xterm 
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2666.760 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Software IO TLB disabled
Memory: 3072512k/3153920k available (2414k kernel code, 72548k reserved,
1349k data, 176k init)
Calibrating delay using timer specific routine.. 6273.92 BogoMIPS
(lpj=12547845)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 10317A0 could
not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 10317A0 could
not acquire Mutex [2] [20060707]
Initializing CPU#1
migration_cost=5823
Initializing CPU#2
migration_cost=5823
Initializing CPU#3
migration_cost=5823
Brought up 4 CPUs
PCI: Fatal: No PCI config space access function found
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1217715664.034:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 52394A11B61A91
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Console: switching to colour frame buffer device 100x37
input: Xen Virtual Keyboard/Mouse as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
USB Universal Host Controller Interface driver v3.0
Registering block device major 202
 xvda: xvda1 xvda2 xvda3
Kernel panic - not syncing: Attempted to kill init!

I''ve tried changing the root device to all three of the above (on my
SP2
server it was xvda3, so I assume it would be the same).

Thanks,
James

James



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, Aug 2, 2008 at 7:07 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> On Sat, 2008-08-02 at 16:52 -0600, Nick Couchman wrote:
>> As far as I know it should work on SLES10SP1, yes.  When you
>> transferred it to the SLES10SP1 machine, did the path to the disk file
>> change and did you make sure to change it the config file?
>>
>
> Yes, and it actually tries to boot, I just get the exact same error as
> before:
> USB Universal Host Controller Interface driver v3.0
> Registering block device major 202
>  xvda: xvda1 xvda2 xvda3
> Kernel panic - not syncing: Attempted to kill init!
>
Maybe it is an SELinux problem (on the guest or host)?
> I''ve tried changing the root device to all three of the above (on
my SP2
> server it was xvda3, so I assume it would be the same).
>
> Thanks,
> James
>
> James
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, 2008-08-02 at 20:46 -0400, Todd Deshane wrote:
> On Sat, Aug 2, 2008 at 7:07 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> > On Sat, 2008-08-02 at 16:52 -0600, Nick Couchman wrote:
> >> As far as I know it should work on SLES10SP1, yes.  When you
> >> transferred it to the SLES10SP1 machine, did the path to the disk
file
> >> change and did you make sure to change it the config file?
> >>
> >
> > Yes, and it actually tries to boot, I just get the exact same error as
> > before:
> > USB Universal Host Controller Interface driver v3.0
> > Registering block device major 202
> >  xvda: xvda1 xvda2 xvda3
> > Kernel panic - not syncing: Attempted to kill init!
> >
> 
> Maybe it is an SELinux problem (on the guest or host)?
> 
It''s possible it''s still on in the guest. Pretty sure
it''s off on dom0.

James 


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, Aug 2, 2008 at 8:55 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> On Sat, 2008-08-02 at 20:46 -0400, Todd Deshane wrote:
>> On Sat, Aug 2, 2008 at 7:07 PM, James Pifer
<jep@obrien-pifer.com> wrote:
>> > On Sat, 2008-08-02 at 16:52 -0600, Nick Couchman wrote:
>> >> As far as I know it should work on SLES10SP1, yes.  When you
>> >> transferred it to the SLES10SP1 machine, did the path to the
disk file
>> >> change and did you make sure to change it the config file?
>> >>
>> >
>> > Yes, and it actually tries to boot, I just get the exact same
error as
>> > before:
>> > USB Universal Host Controller Interface driver v3.0
>> > Registering block device major 202
>> >  xvda: xvda1 xvda2 xvda3
>> > Kernel panic - not syncing: Attempted to kill init!
>> >
>>
>> Maybe it is an SELinux problem (on the guest or host)?
>>
>
> It''s possible it''s still on in the guest. Pretty sure
it''s off on dom0.
>
Try to mount the root partition and edit the file within the partition:
/etc/selinux/config

> James
>
>


-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Try to mount the root partition and edit the file within the partition:
> /etc/selinux/config
> 
> 
> > James
> >
> >
> 
> 
> 
If I try to mount the image file with this command:
mount -o loop,offset=$((63*512)),rw disk0 /mnt

All I see is the boot partition. IRC the image file has:
/boot
swap
/

James




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Aug 3, 2008 at 7:21 AM, James Pifer <jep@obrien-pifer.com>
wrote:
>> Try to mount the root partition and edit the file within the partition:
>> /etc/selinux/config
>>
>>
>> > James
>> >
>> >
>>
>>
>>
>
> If I try to mount the image file with this command:
> mount -o loop,offset=$((63*512)),rw disk0 /mnt
>
> All I see is the boot partition. IRC the image file has:
> /boot
> swap
> /
>
Use kpartx -av diskname to make the partitions available in
/dev/mapper/loop*p<num>
> James
>
>
>
>


-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Use kpartx -av diskname to make the partitions available in
> /dev/mapper/loop*p<num>
> 
> > James
> >
I used lomount to mount the image. (found that in one of your previous
posts)

I disabled selinux by modifying /etc/sysconfig/selinux.
I umounted and remouonted to make sure the setting was saved. 

It still fails to load. :-(

James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> SLES 10 (your Dom0) doesn''t ship with SELinux - using AppArmor in
it''s
> place, so I''d be very surprised if this is an SELinux/AppArmor
> problem, especially as you have had this image previously running. On
> the other hand there is a Xen version jump between SLES 10 SP1 and
> SLES 10 SP2. Is there a specific reason why the original CentOS DomU
> image was built on SLES 10 SP2 with the aim of running it on SLES 10
> SP1? This is were I''d start looking for problems...
> 
> Jon 
> 
> 
> 
I plan on updating the SP1 servers to SP2. I have SP2 here locally,
which is why it was created on SP1. I could not get centos to install on
SP1 at all. Can''t remember off the top of my head the exact problems.
I''ll have to try it again.

Is there that big of a difference in the img file that was created
between xen on SP1 and SP2?

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

>         
> 
> Yes - because SLES 10 SP2 is based on Xen 3.2 and SLES 10 SP1 is an
> earlier version (3.1 I think, but I''m not sure). I may have missed
it
> earlier on, but is CentOS a paravirtual instance or HVM instance?
> Also, it might be worth a look at the config file from the SLES 10 SP2
> (working) and the altered one on SLES 10 SP1 (not working)
> 
It''s PV. The config files basically look the same. I also tried using
the same config file from the SP2 machine, as well as having the SP1
virt-manager create it. Both give me the same result.

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users