WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] setting up Ubuntu DomU on CentOS Dom0

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] setting up Ubuntu DomU on CentOS Dom0
From: "Donald Plummer" <donald@xxxxxxxxxxxx>
Date: Thu, 27 Mar 2008 11:30:10 -0700
Delivery-date: Thu, 27 Mar 2008 11:31:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0803270900q4008b25dx568c78a4a81749be@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <3656250B41D80048BD37067756994088A9D620@xxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0803270900q4008b25dx568c78a4a81749be@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciQI8AnGm7Q6wk6SdGB1RvWmRoQCAAFLfsw
Thread-topic: [Xen-users] setting up Ubuntu DomU on CentOS Dom0

Awesome, that totally did it. Now to dig around (as I’m sure someone has solved this problem before) and find out why I don’t have an eth0 in my new ubuntu domU.

 

Thanks!

Donald

 

From: Todd Deshane [mailto:deshantm@xxxxxxxxx]
Sent: Thursday, March 27, 2008 9:01 AM
To: Donald Plummer
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] setting up Ubuntu DomU on CentOS Dom0

 

 

On Wed, Mar 26, 2008 at 12:22 PM, Donald Plummer <donald@xxxxxxxxxxxx> wrote:

So, I'm trying to setup an Ubuntu gutsy amd64 DomU on my CentOS 5.1
x86_64 Dom0.  Unfortunately, jailtime.org doesn't have an ubuntu amd64
image, so I've used debootstrap to setup the image. To do that, I
installed Ubuntu 7.10 amd64 server on a spare machine, installed all the
xen bits, and ran debootstrap:
# sudo debootstrap --arch amd64 gutsy /mnt/gutsy/

Copied the kernel modules (all of them, since I wasn't exactly sure what
I'd need):
# sudo cp -a /lib/modules/2.6.* /mnt/gutsy/lib/modules/

Setup the domU config (after copying the image to the CentOS Dom0)
-----
kernel = "/xen/ubuntu/vmlinuz-2.6.22-14-xen"
ramdisk = "/xen/ubuntu/initrd.img-2.6.22-14-xen"
memory = "512"
name = "gutsy-test"
vif = ['bridge=xenbr0']
disk = ['phy:/dev/VolGroup00/gutsy-test,sda1,w', 'phy:/dev/VolGroup00/
gutsy-test -swap,sda2,w']
root = "/dev/sda1 ro"
-----

But when I start the domU up, it hangs on starting up. Here's the boot
log:
Using config file "./ gutsy-test ".
Started domain gutsy-test
[    0.000000] Linux version 2.6.22-14-xen (buildd@king) (gcc version
4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12
04:26:15 UTC 2008 (Unofficial)
[    0.000000] Command line:  root=/dev/sda1 ro
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 0000000020800000 (usable)
[    0.000000] end_pfn_map = 133120
[254216.349891] Zone PFN ranges:
[254216.349894]   DMA             0 ->   133120
[254216.349897]   DMA32      133120 ->   133120
[254216.349899]   Normal     133120 ->   133120
[254216.349901] early_node_map[1] active PFN ranges
[254216.349903]     0:        0 ->   133120
[254216.359982] No mptable found.
[254216.361337] PERCPU: Allocating 25096 bytes of per cpu data
[254216.361363] Built 1 zonelists.  Total pages: 131300
[254216.361366] Kernel command line:  root=/dev/sda1 ro
[254216.362009] Initializing CPU#0
[254216.362143] PID hash table entries: 4096 (order: 12, 32768 bytes)
[254216.362183] Xen reported: 1994.999 MHz processor.
[254216.362209] Console: colour dummy device 80x25
[254216.362667] Dentry cache hash table entries: 131072 (order: 8,
1048576 bytes)
[254216.363097] Inode-cache hash table entries: 65536 (order: 7, 524288
bytes)
[254216.363222] Software IO TLB disabled
[254216.367366] Memory: 487680k/532480k available (2343k kernel code,
36052k reserved, 1193k data, 208k init)
[254216.367410] SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4,
CPUs=1, Nodes=1
[254216.434207] Calibrating delay using timer specific routine.. 3991.73
BogoMIPS (lpj=7983477)
[254216.434239] Security Framework v1.0.0 initialized
[254216.434247] SELinux:  Disabled at boot.
[254216.434261] Mount-cache hash table entries: 256
[254216.434373] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[254216.434380] CPU: L2 Cache: 1024K (64 bytes/line)
[254216.434386] CPU: Physical Processor ID: 0
[254216.434390] CPU: Processor Core ID: 0
[254216.434399] SMP alternatives: switching to UP code
[254216.434542] Freeing SMP alternatives: 23k freed
[254216.434667] Early unpacking initramfs... done
[254216.449181] Brought up 1 CPUs
[254216.449777] NET: Registered protocol family 16
[254216.450862] Brought up 1 CPUs
[254216.450879] PCI: Fatal: No config space access function found
[254216.450884] PCI: setting up Xen PCI frontend stub
[254216.451292] ACPI: Interpreter disabled.
[254216.451300] Linux Plug and Play Support v0.97 (c) Adam Belay
[254216.451310] pnp: PnP ACPI: disabled
[254216.451604] xen_mem: Initialising balloon driver.
[254216.452857] Setting mem allocation to 524288 kiB
[254216.452920] PCI: System does not support PCI
[254216.452925] PCI: System does not support PCI
[254216.452947] NET: Registered protocol family 8
[254216.452951] NET: Registered protocol family 20
[254216.453236] NET: Registered protocol family 2
[254216.454426] Time: xen clocksource has been installed.
[254216.486452] IP route cache hash table entries: 32768 (order: 6,
262144 bytes)
[254216.486576] TCP established hash table entries: 131072 (order: 9,
3145728 bytes)
[254216.487969] TCP bind hash table entries: 65536 (order: 8, 1048576
bytes)
[254216.488487] TCP: Hash tables configured (established 131072 bind
65536)
[254216.488495] TCP reno registered
[254216.498527] checking if image is initramfs... it is
[254216.514166] Freeing initrd memory: 20320k freed
[254216.523431] audit: initializing netlink socket (disabled)
[254216.523449] audit(1206547938.077:1): initialized
[254216.524946] VFS: Disk quotas dquot_6.5.1
[254216.524988] Dquot-cache hash table entries: 512 (order 0, 4096
bytes)
[254216.525062] io scheduler noop registered
[254216.525067] io scheduler anticipatory registered
[254216.525070] io scheduler deadline registered
[254216.525144] io scheduler cfq registered (default)
[254216.544937] rtc: IRQ 8 is not free.
[254216.544998] Linux agpgart interface v0.102 (c) Dave Jones
[254216.545409] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[254216.545556] input: Macintosh mouse button emulation as
/class/input/input0
[254216.545603] xencons_init: Initializing xen vfb; pass xencons=tty to
prevent this
[254216.545677] Xen virtual console successfully installed as xvc0
[254216.545715] Event-channel device installed.
[254216.563066] netfront: Initialising virtual ethernet driver.
[254216.563596] PNP: No PS/2 controller found. Probing ports directly.
[254216.564418] i8042.c: No controller found.
[254216.564497] mice: PS/2 mouse device common for all mice
[254216.564596] TCP cubic registered
[254216.564648] NET: Registered protocol family 1
[254216.565226] xen-vbd: registered block device major 8
[254216.571135] netfront: device eth0 has flipping receive path.
[254216.662471]
/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[254216.662489] Freeing unused kernel memory: 208k freed
[254216.925032] fuse init (API version 7.8)
[254216.933839] Capability LSM initialized
[254216.966859] thermal: Unknown symbol acpi_processor_set_thermal_limit
[254216.982901] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12)
initialised: dm-devel@xxxxxxxxxx
[254217.789297] kjournald starting.  Commit interval 5 seconds
[254217.789321] EXT3-fs: mounted filesystem with ordered data mode.



This hang is *usually* fixed by adding extra='xencons=tty' to the guest config file

See this bug for even more suggestions:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/144631
 
Regards,
Todd



Anyone have any ideas on what I missed? I was able to run the 32-bit
Ubuntu from jailtime.org (though it crashed frequently, since it was a
32-bit domU on a 645-bit dom0).

Perhaps a related question, how can I tell what architecture a kernel
and initrd are compiled for? The two I'm using for this domU I think are
for amd64, but I'm not 100% sure.

Thanks for the help,
Donald


_______________________________________________
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