[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] centos 5.6 upgrade to 4.1 - no DomUs listed
try booting with pci=nomsi on the kernel line,If you setup networking according to this then things should be working, and no need to use vif in the bridge line: http://wiki.xensource.com/xenwiki/HostConfiguration/Networking One of my working confs looks like this (CentOS 5.6 Xen 4.1): name = "test1" memory = "512" disk = [ "phy:/dev/vg1/test1,xvda,w" ] vif = [ 'mac=00:16:3e:aa:aa:91,bridge=xenbr0' ] vcpus=1 on_reboot = 'restart' on_crash = 'restart' bootloader = "/usr/bin/pygrub" on node: # netstat -rn Kernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 xenbr0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 xenbr0 On 5/18/2011 12:26 AM, Andy Howell wrote: Todd,What is the output of running the command: xl create -c trillianI don't know. I had to switch to another box; one that is not running my mail server in a VM :) Why did I think this was going to be easy... The other box, also running CentOS 5.6, will not boot with xen 4.1. The stock xen worked fine. Running with the DEBUG=Y on xen and kernel command line, I see its not able to recognise the disk drives and build the raid device. I get errors like: ata2: Sata link up 3.0 Gbps (SStatus 123 SControl 300) ata 200: failed to identify (io error, err_mask=0x4) ata2: failed to recover some devices retrying in 5 secs Booting with non-xen kernel works fine. My brain is numb from hours of googling to no avail. I'll try again tomorrow. Regards, Andy _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |