Xen users - Apr 2009 - Linux PV Drivers - VBD device not loading - Cannot get Major 3/22 for ide

I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3
HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the
kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. 

For the network drivers to work I had to unload the Realtek NIC driver
and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias
to modprobe.conf then got the PV NICs working nicely (Much faster).

The problem is I can''t seem to get the PV disk drivers running,
I''m
using a standard partition for the VM (phy:), part of the problem may be
that the QEMU emulated disks are loading first but I''m unsure. Below is
what I think are the relevant extracts from the Centos 5.3 HVM log,
anyone have any idea on how to fix this?



ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
PCI: Setting latency timer of device 0000:00:01.1 to 64
    ide0: BM-DMA at 0xc200-0xc207, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xc208-0xc20f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 512KiB
hda: 104854328 sectors (53685 MB) w/256KiB Cache, CHS=16383/255/63,
(U)DMA
hda: cache flushes supported
 hda: hda1 hda2
....<SNIP>......
Xen version 3.3.
Hypercall area is 1 pages.
Grant table initialized
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
piix4_smbus 0000:00:01.3: Found 0000:00:01.3 device
piix4_smbus 0000:00:01.3: SMB base address uninitialized - upgrade BIOS
or use f
orce_addr=0xaddr
hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.20
Registering block device major 3
register_blkdev: cannot get major 3 for ide
xen_blk: can''t get major 3 with name ide
vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/109/768
Registering block device major 3
register_blkdev: cannot get major 3 for ide
xen_blk: can''t get major 3 with name ide
vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/109/768
Registering block device major 22
register_blkdev: cannot get major 22 for ide
xen_blk: can''t get major 22 with name ide
vbd vbd-5632: 19 xlvbd_add at /local/domain/0/backend/vbd/109/5632
xen_mem: Initialising balloon driver.
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has copying receive path.
XENBUS: Timeout connecting to device: device/vbd/768 (state 6)
XENBUS: Timeout connecting to device: device/vbd/5632 (state 6)



The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. services
to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit :
Backups : Managed Networks : Remote Support.

ISPA Member

Find us in http://www.thebestof.co.uk/petersfield


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

Robert Dunkley wrote:
> I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3
> HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the
> kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. 
>
> For the network drivers to work I had to unload the Realtek NIC driver
> and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias
> to modprobe.conf then got the PV NICs working nicely (Much faster).
>
>   
Since realtek and xen-vnif each create an eth (with the same MAC), you
could simply set ifcfg-eth*''s "ONBOOT=no" on
realtek''s NICs. Do a "dmesg
| grep eth" to find which NIC uses which driver.

Problem is I can''t get xen-vnif driver to work correctly on RHEL 5.3
(kernel 2.6.18-128.1.1.el5), not sure why.
> The problem is I can''t seem to get the PV disk drivers running,
I''m
> using a standard partition for the VM (phy:), part of the problem may be
> that the QEMU emulated disks are loading first but I''m unsure.
Below is
> what I think are the relevant extracts from the Centos 5.3 HVM log,
> anyone have any idea on how to fix this?
>
>   
On /etc/modprobe.conf :
#alias scsi_hostadapter ata_piix
alias scsi_hostadapter xen-vbd

On grub.conf:
title Red Hat Enterprise Linux Server (2.6.18-128.1.1.el5)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-128.1.1.el5 ro root=/dev/VolGroup00/LogVol00
console=vga console=ttyS0 ide0=noprobe noapic
    initrd /initrd-2.6.18-128.1.1.el5.img

The "ide0=noprobe" should allow xen-vbd to handle hda, and
modprobe.conf
ensures it''s included on initrd.

Regards,

Fajar


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

On Wed, Apr 1, 2009 at 3:25 PM, Robert Dunkley <Robert@saq.co.uk>
wrote:
>
> Method below did not work too well for me, the kernel ends up unbootable
> (Cant mount anything). Was the noapic option important? (I only added
> ide0=noprobe)
ide0=noprobe -> makes ide skips probing ide0 (hda and hdb). If it''s
unbootable, chances are you haven''t load xen-vbd. That why I told you
to modify modprobe.conf, and you have to recreate initrd afterwards
(you might want to use "-v" to see what drivers are added). If it
still doesn''t work, post full startup log (which is easier if you use
text console instead of VNC console)

noapic -> a performance-improvement suggestion from Redhat (can''t
remember exactly which URL though)

Regards,

Fajar

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

On 01/04/2009, at 7:06 PM, Fajar A. Nugraha wrote:
> ide0=noprobe -> makes ide skips probing ide0 (hda and hdb). If
it''s
> unbootable, chances are you haven''t load xen-vbd. That why I told
you
> to modify modprobe.conf, and you have to recreate initrd afterwards
> (you might want to use "-v" to see what drivers are added). If it
> still doesn''t work, post full startup log (which is easier if you
use
> text console instead of VNC console)
>
> noapic -> a performance-improvement suggestion from Redhat
(can''t
> remember exactly which URL though)
>
> Regards,
>
> Fajar

I can''t seem to get a RHEL4 i386 HVM guest to boot on RHEL5.2 x86_64  
when using the PV vbd either.

The initrd contains the xen-vbd driver and xen-platform-pci but it  
dies when trying to boot:

ACPI: (supports S5)
XENBUS: Device with no driver: device/vbd/768
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vbd/5632
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 192k freed
SCSI subsystem initialized
kobject_register failed for xen-platform-pci (-17)
  [<c01c432f>] kobject_register+0x31/0x39
  [<c0225171>] bus_add_driver+0x36/0x99
  [<c01cdc02>] pci_register_driver+0x6e/0x8a
  [<f881800b>] platform_pci_module_init+0xb/0x2e [xen_platform_pci]
  [<c0138e69>] sys_init_module+0xf8/0x240
  [<c02e0767>] syscall_call+0x7/0xb
xen-platform-pci: No platform pci device model found
device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel@redhat.com
Kernel panic - not syncing: Attempted to kill init!

It seems to see the devices and the xen-vnif ethernet device works  
well. Have I missed something simple?

Regards,
Tom

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

On Fri, Apr 3, 2009 at 2:38 PM, Tom Lanyon <tom@netspot.com.au>
wrote:
> I can''t seem to get a RHEL4 i386 HVM guest to boot on RHEL5.2
x86_64 when
> using the PV vbd either.
As usual, use PV if you can as it provides best performance :)
>
> The initrd contains the xen-vbd driver and xen-platform-pci but it dies
when
> trying to boot:
> It seems to see the devices and the xen-vnif ethernet device works well.
> Have I missed something simple?
Worth to try :
- map additional disk to domU as xvdf (for example)
- load xen-vbd, see if it detects the disk

If that works, try putting using ide0=noprobe and put the module on
initrd. If it doesn''t, there''s probably something wrong with
the
kernel version you''re using, try downgrade, or (even better) use
RedHat support and ask them what''s wrong :D

Regards,

Fajar

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