xend hangs at start
by Eric Smith
Hi,
Running FC5 now on Pentium 4 and want to try xen (for the first time).
[root@gum ~]# xm list
Error: Error connecting to xend: Connection refused. Is xend running?
[root@gum ~]# ps -ef | grep xend
root 2343 1 0 22:33 ? 00:00:00 python /usr/sbin/xend start
root 2344 2343 0 22:33 ? 00:00:00 python /usr/sbin/xend start
[root@gum ~]# uname -a
Linux gum 2.6.15-1.1955_FC5hypervisor #1 SMP Wed Feb 15 16:21:02 EST 2006
i686 i686 i386 GNU/Linux
The "start" never completes. Disabled SElinux and rebooted, same results.
Any ideas?
Thanks,
Eric
ps Installed FC5 test 3 and then ran yum update to move to FC5 when
released. Updated again just today:
[root@gum ~]# cat /etc/fedora-release
Fedora Core release 5 (Bordeaux)
18 years
"enhanced" xenguest-install.py
by Ben
I just finished testing my enhancements to xenguest-install.py that
let me specify multiple volumes and multiple NICs to export to the
new domU. Seems to work ok for me, though I'm only testing it on the
paravirtualized server. In case anybody else would find such a thing
useful, I've attached it here.
(Note that I gave up on the default bridging script. It just didn't
make sense to me when I wanted more than a single NIC. Instead, I
used the logic on http://wiki.xensource.com/xenwiki/XenNetworkingSuse?
highlight=%28XenNetworking%29 pretty much verbatim.)
18 years, 1 month
Re: kudzu not seeing my new NIC
by Ben
Actually, I take back that part about using the interfaces just fine.
While I can *see* the manually configured interfaces just fine, it
seems the xen dom0 scripting glue plays with the arp broadcasts in
such a way as that an arp request for any interface always resolves
to just of of them.
On Mar 17, 2006, at 9:19 AM, Ben wrote:
> I'm running a current set of rawhide RPMs on x86_64. I just tried
> to add a new network card (a dual-port eepro100), and while I can
> manually configure the NICs and use them just fine, kudzu didn't
> see them. Is this expected behavior?
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:https://www.redhat.com/mailman/listinfo/fedora-test-
> list
18 years, 1 month
RE: [Fedora-xen] setting IP address for domU in a config file
by Todd Foster
Start the domain and create a
/etc/sysconfig/networking/devices/ifcfg-eth0 file with the following in
it. (works for me!) This is on FC4 Zen 3.01
DEVICE=eth0
BROADCAST=192.168.1.255
HWADDR=aa:bb:00:00:00:12
IPADDR=192.168.1.110
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet
GATEWAY=192.168.1.1
BOOTPROTO=none
USERCTL=no
PEERDNS=yes
IPV6INIT=no
Todd H Foster, CEO
Technetium, Inc.
The Technical Element.
One Ten Pine Avenue Suite 1080
Long Beach, CA 90802
----------------------------
Phone: (310) 508-6476
Fax: (562) 427-4707
Email: toddf(a)technetiuminc.com
Web: www.technetiuminc.com
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Mark Ryden
Sent: Thursday, March 16, 2006 2:15 AM
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] setting IP address for domU in a config file
Hello,
I had followed the instructions in
http://www.fedoraproject.org/wiki/FedoraXenQuickstart
an I am succeeding in creating domain U.
The thing is that I want domU to start with some static IP address.
How can I do it ?
I had tried adding , in the config file for domU, vif = [
'ip=192.168.0.193', 'bridge=xenbr0' ] netmask="255.255.255.0"
and run "xm create -c domUconfig"
Dom U started , ifconfig -a showed eth0, but without the IP address.
Any ideas ?
Mark
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
18 years, 1 month
setting IP address for domU in a config file
by Mark Ryden
Hello,
I had followed the instructions in
http://www.fedoraproject.org/wiki/FedoraXenQuickstart
an I am succeeding in creating domain U.
The thing is that I want domU to start with some static IP address.
How can I do it ?
I had tried adding , in the config file for domU,
vif = [ 'ip=192.168.0.193', 'bridge=xenbr0' ]
netmask="255.255.255.0"
and run "xm create -c domUconfig"
Dom U started , ifconfig -a showed eth0, but without the IP address.
Any ideas ?
Mark
18 years, 1 month
Unable to reboot a domU
by Ben
I installed a domU on x86_64 today, and was very happy. I even logged
into it and saw that things seemed to be working, and all was well. I
tried to reboot it, and now the domU kernel panics every time I try
to boot. :(
The bug is 185603, and the console end with:
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
Kernel panic - not syncing: Attempted to kill init!
Call Trace: <ffffffff80128d62>{panic+134} <ffffffff8020b652>{__up_read
+19}
<ffffffff80170b04>{__fput+354} <ffffffff802d66f2>
{_spin_unlock_irq+9}
<ffffffff802d6006>{__down_read+52} <ffffffff802d67ef>
{_spin_lock_irqsave+38}
<ffffffff8020b652>{__up_read+19} <ffffffff8012c70b>{do_exit+140}
<ffffffff8012cfa0>{sys_exit_group+0} <ffffffff8010ad82>
{system_call+134}
<ffffffff8010acfc>{system_call+0}
Any thoughts?
18 years, 1 month
RE: [Fedora-xen] Unable to reboot a domU
by You, Yongkang
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Ben
>Sent: 2006年3月16日 10:09
>To: fedora-xen(a)redhat.com
>Subject: [Fedora-xen] Unable to reboot a domU
>
>I installed a domU on x86_64 today, and was very happy. I even logged
>into it and saw that things seemed to be working, and all was well. I
>tried to reboot it, and now the domU kernel panics every time I try
>to boot. :(
So at present you couldn't create XenU with that image again? I think maybe your XenU image is broken.
Maybe you can do a manually mount that image file and check if /etc/fstab is there.
mount -oloop xenU_image_file /mnt
>
>The bug is 185603, and the console end with:
>
>no fstab.sys, mounting internal defaults
>Switching to new root and running init.
>unmounting old /dev
>unmounting old /proc
>unmounting old /sys
>Kernel panic - not syncing: Attempted to kill init!
>
>
Best Regards,
Yongkang (Kangkang) 永康
18 years, 1 month
Problem installing FC5 guest in Xen on FC5 using xenguest-install.py
by Scott D Hankin
Howdy -
I'm attempting to install a FC5 guest in Xen on FC5, 2041 xen0 kernel. I've
gotten to the point where anaconda runs and starts presenting me with
menus. Unfortunately, the 3rd menu it presents is stopping me, the one
which sets the IP address.
If I select DHCP and networking is set up for NAT, it thinks for a bit and
then returns to the same page. If I try to manually specify an IP address,
it thinks for a bit, and then segfaults. If networking is bridged, it
segfaults in either case.
The command I'm running is:
xenguest-intall.py -n vm2 -f /root/fedora.img -s 6 -r 256 -p -l
ftp://mymachine
I've tried this with the networking setup as bridged or NAT, but the result
is always the same.
Any thoughts?
-- Scott
(Originally posted, probably in error, to fedora-test.)
-----------------------------
In the beginning, there was nothing, then God said, "Let there be light."
And there was light. There was still nothing, but you could see it a lot
better.
18 years, 1 month
crash booting rawhide xen0
by Andy Burns
Hi there,
I've not been updating my xen kernels to *every* recent rawhide release,
but did so today, to 2.6.15-1.2041_FC5xen0, my first two attempts to
boot this xen0 crashed and stackdumped :-(
Having seen it fail twice, I attached a serial console and was preparing
to capture that with console=ttyS0,115200, but on the next two boots the
crash didn't happen, however my console output still went to the
vgaconsole, does xen have a different way to use the serial console?
I'll gladly log a bug if I can make it happen again ...
Also I've just tidied up my grub.conf, /boot/ and /lib/modules/ to get
rid of heaps of old kernels that the switch from guest/hypervisor to
xen0/xenU had left around, is there anywhere I can get back a few
slightly older kernels to try and find out what version caused this
breakage? I think my last known good version was kernel 2032
18 years, 1 month
RE: [Fedora-xen] crash booting rawhide xen0
by You, Yongkang
Hi Andy,
I suggested that you can do "yum update" to update other RPMs and retry too.
I didn't meet this problem in x86_64, after I do yum update to catch up latest development tree. :)
Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Andy Burns
>Sent: 2006年3月12日 22:02
>To: fedora-xen(a)redhat.com
>Subject: Re: [Fedora-xen] crash booting rawhide xen0
>
>Andy Burns wrote:
>
>> 2.6.15-1.2041_FC5xen0, my first two attempts to
>> boot this xen0 crashed and stackdumped :-(
>
>OK, with Yongkang's info I've captured this happening
>
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185235
>Full serial log attached there, but the offending bit seems to be
>
>Kernel BUG at arch/x86_64/mm/fault-xen.c:292
>invalid opcode: 0000 [1] SMP
>CPU 0
>Modules linked in: snd_mixer_oss snd_pcm snd_timer snd soundcore
>snd_page_alloc hw_random i2c_i801 i2c_core dm_snapshot dm_zero
>dm_mirror
>dm_mod ext3 jbd ahci libata sd_mod scsi_mod
>Pid: 615, comm: udevd Not tainted 2.6.15-1.2041_FC5xen0 #1
>RIP: e030:[<ffffffff801197df>] <ffffffff801197df>{do_page_fault+1690}
>RSP: e02b:ffffffff80418978 EFLAGS: 00010287
>RAX: ffff800000000000 RBX: ffff880000ed7000 RCX: 00003ffffffff000
>RDX: 0000000000050204 RSI: 000000000003ac4e RDI: 0000000000000c00
>RBP: ffffffff80101c20 R08: 000000000003ac4e R09: ffff880000ae8070
>R10: ffff880000ae9000 R11: ffff880000ae9000 R12: ffffc2000000e008
>R13: ffffffff80418a58 R14: ffff880038d8f100 R15: 0000000000000000
>FS: 00002b07a11e66d0(0000) GS:ffffffff80499000(0000)
>knlGS:0000000000000000
>CS: e033 DS: 0000 ES: 0000
>Process udevd (pid: 615, threadinfo ffff880038cc4000, task ffff880038d8f100)
>Stack: 0000000000000001 0000000000030001 ffffffff804189c8 ffffffff801f2163
> ffff880000636048 ffff88000230e800 ffff880000636048
>ffff880000636048
> ffff880000636240 ffffffff801e727d
>Call Trace: <IRQ> <ffffffff801f2163>{cfq_dispatch_requests+326}
> <ffffffff801e727d>{elv_next_request+321}
><ffffffff801f49fa>{kobject_get+18}
> <ffffffff880064f6>{:scsi_mod:scsi_request_fn+843}
><ffffffff8010b503>{error_exit+0}
> <ffffffff8803d447>{:ahci:ahci_interrupt+33}
><ffffffff80151e15>{handle_IRQ_event+78}
> <ffffffff80151efb>{__do_IRQ+156} <ffffffff8010d4c2>{do_IRQ+65}
> <ffffffff8025eeed>{evtchn_do_upcall+132}
><ffffffff8010b5b5>{do_hypervisor_callback+37} <EOI>
> <ffffffff8010722a>{hypercall_page+554}
><ffffffff8010722a>{hypercall_page+554}
> <ffffffff8018e463>{mntput_no_expire+25}
><ffffffff8025e8d5>{force_evtchn_callback+10}
> <ffffffff80119209>{do_page_fault+196}
><ffffffff801845a5>{sys_mknodat+371}
> <ffffffff8010b503>{error_exit+0}
>
>
>--
>Fedora-xen mailing list
>Fedora-xen(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-xen
18 years, 1 month
