[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Newbie question on network and VM management



hi gurus,

I am trying to create my domU from the kernel and ramdisk of dom0 and it fails. I think i am missing the root file system config. Can you advise how to instruct domu kernel to load correct domu ramdisk?

Also the errors says:Â
CPU: 0 PID: 1 Comm: init Not tainted 3.10.68-11.el6.centos.alt.x86_64 #1
What this actually means?


thanks!

===============

$uname -a

Â3.10.68-11.el6.centos.alt.x86_64 #1 SMP Fri Feb 6 10:40:16 CST 2015 x86_64 x86_64 x86_64 GNU/Linux


$cat tengiz1.cfg


kernel = "/root/vmlinuz_dom0"

ramdisk = "/root/ramdisk_dom0"

name = "myfirstdomu"

memory = "450"

disk = [ 'tap:aio:/home/tengiz/image10gb.img,xvda,w', ]

vif = [ 'bridge=xenbr0', ]

vcpus=1

>

>




# xl create -c tengiz1.cfg
[skip]

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Freeing unused kernel memory: 1876k freed

Write protecting the kernel read-only data: 12288k

Freeing unused kernel memory: 2008k freed

Freeing unused kernel memory: 1156k freed

dracut: dracut-004-356.el6

dracut: FATAL: No or empty root= argument

dracut: Refusing to continue



dracut Warning: Signal caught!

dracut Warning: dracut: FATAL: No or empty root= argument

dracut Warning: dracut: Refusing to continue

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100


CPU: 0 PID: 1 Comm: init Not tainted 3.10.68-11.el6.centos.alt.x86_64 #1

Âffffffff81c3fea0 ffff88001af4dd98 ffffffff815f672d ffff88001af4de18

Âffffffff815f64ce ffffffff00000010 ffff88001af4de28 ffff88001af4ddc8

Âffffffff8112841e ffff88001af4dde8 0000000000000100 ffff88001af4b060

Call Trace:

Â[<ffffffff815f672d>] dump_stack+0x19/0x1c

Â[<ffffffff815f64ce>] panic+0xc4/0x1e4

Â[<ffffffff8112841e>] ? __perf_cgroup_move+0xe/0x20

Â[<ffffffff8105f81c>] find_new_reaper+0x17c/0x180

Â[<ffffffff81060055>] forget_original_parent+0x45/0x2d0

Â[<ffffffff81128410>] ? perf_cgroup_switch+0x180/0x180

Â[<ffffffff810602f7>] exit_notify+0x17/0x140

Â[<ffffffff81061cbb>] do_exit+0x1fb/0x480

Â[<ffffffff81061f95>] do_group_exit+0x55/0xd0

Â[<ffffffff81062027>] SyS_exit_group+0x17/0x20

Â[<ffffffff81602d99>] system_call_fastpath+0x16/0x1b




On Mon, Feb 16, 2015 at 10:05 PM, Tengiz Dawkins <tengiz.dawkins@xxxxxxxxx> wrote:
thanks a lot! I have one more question: should I do any specific tuning of Xen/Dom0 for my config? That will be 64+ core, 1TB RAM, 1.2TB SDD storage
host. What is the best version/release/flavour I should use to build a rock solid system for 30+VMs?


On Mon, Feb 9, 2015 at 12:47 AM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote:
On Fri, 2015-02-06 at 08:37 -0800, Tengiz Dawkins wrote:
> Thanks Sarah,
>
>
> My understanding is that the traffic will be routed inside the Dom0
> bridge amongst all the ports (layer 2 routing kind of). And will not
> leave Dom0 at all. Will openVswitch help in this situation?

ovs is certainly more configurable than Linux bridge for this sort of
thing, I don't know the specific recipe to achieve what you want but I'm
sure it can be done.

Likewise for Linux brudge, Sarah's suggestion looks plausible to me,
although it will broadcast everything everywhere, whereas you probably
want to figure out a way to send the packets only to the intended target
plus the IDS, which would be easier

Ian.





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.