similar to: Cannot start xen domUs anymore, domUs hang on kernel startup, happens after a long dom0 uptime

Hello list! I''ve noticed this problem a couple of times now.. so I''m wondering if it''s a known bug? Symptoms: After "long" dom0 uptime (174 days when it happened now, was something similar on previous times too) cannot start new pv domUs anymore.. pygrub runs and boots the kernel, but kernel newer gets to actually running initrd and the console output

Hello all, I'm addressing the mailing list following the suggestion of gwd on #centos-virt @freenode IRC. The subject says most of it. Here are the details : - Was running 4.4.x and configured such that /etc/xen/auto domUs would be saved/restored on dom0 shutdown/bootup. - Installation was based on "centos-release-xen" such that "yum upgrade" brough Xen to 4.6.1. After

On Thu, Apr 7, 2016 at 5:46 PM, exvito here <ex.vitorino at gmail.com> wrote: > Hello all, > > I'm addressing the mailing list following the suggestion of gwd on > #centos-virt @freenode IRC. > > The subject says most of it. Here are the details : > > - Was running 4.4.x and configured such that /etc/xen/auto domUs would be > saved/restored on dom0

Using a default xen3.0.1 setup for dom0(rhel4 distro) and domUs (gentoo, rhel4, centos4.2 distros, ttylinux) with the domUs all having dhcp turned on, is there an easy way to tell from within the dom0 what ip addresses were assigned to the domUs after bootup? Toby Ford USi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi Is there any docs, howtos, etc, if i am installed eg. CentOS 5 to as domU as fully virtualized and now i am wanting to use it PV drivers. Any help how migration can be done? Terveisin/Regards, Pekka Panula, Net Servant Oy - A Sofor company pekka.panula@sofor.fi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I have setup MRTG with 14all.cgi cgi script. I downloaded it from below URL. http://my14all.sourceforge.net/14all-1.1.txt and did only below 3 changes to that file. those can be seen in BOLDletters. # if MRTG_lib.pm (from mrtg) is not in the module search path (@INC) # uncomment the following line and change the path appropriatly: #use lib qw(/usr/local/mrtg-2/lib/mrtg2); use lib

Hello, I tried to build an debian package from svn. First I checked out trunk and the 2.3.2 branch, which both build this quite "old" package :-) icecast2_1.9+2.0alphasnap2+20030802-1_amd64.deb Then I tried the kh branch, which doesn't build with dpkg-buildpackage: debian/rules:6: debian/cdbs/1/rules/buildinfo.mk: No such file or directory make: *** No rule to make target

Hello, I didn't want to have to choose between Icecast running on port 80 and all my Apache virtual hosts, running also on port 80, on my sole external IP address. I didn't want either to open port 8000 on my firewall because I wanted all users being able to reach Icecast even the ones behind enterprise firewalls. So I managed to run Apache 2.2 listening on port 80 and Icecast 2.3.2

Now this is what I call uptime... minipbx*CLI> show uptime System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds Last reload: 8 hours, 3 minutes, 51 seconds Bizarre bug? root at minipbx:~# asterisk -V Asterisk 1.4.37 root at minipbx:~# uname -a Linux minipbx 2.6.32-dockstar #2 Thu Nov 25 18:03:25 UTC 2010 armv5tel GNU/Linux root at minipbx:~# uptime 03:29:27 up 5 days,

Hello! I recently upgraded a number of Debian testing packages (three days ago) and just now rebooted the system, with the effect that the Xen domUs don't know their `eth0' devices anymore: #v+ # ifconfig eth0 eth0: error fetching interface information: Device not found #v- I'm using xen-hypervisor-3.0.3-1-i386-pae 3.0.3-0-2 and upgraded linux-image-2.6.18-4-xen-686 from

CentOS 4.1, Xen 2.0.7. My dom0 is booting up but can''t get to the outside network because eth0 won''t start due to, apparently, Xen providing a different mac address than expected. How do I tell Xen to start eth0 at the bootup with a specific mac address that lines up with the HWADDR= line in my ifcfg-eth0? Note that a normal bootup into CentOS 4.1 outside of the Grub Xen bootup

I'm trying to get icecast 2.3.1 compiled on a slackware 10.0 box. I've successfully compiled the libshout libraries. Now this is what I got after a make in the source dir: > make[3]: Entering directory `/tar_archive/icecast-2.3.1/src' > /bin/sh ../libtool --mode=link gcc -pthread -g -O2 -L/usr/local/lib > -o icecast cfgfile.o main.o logging.o sighandler.o connection.o

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any vifs/taps connected to it anymore. Has anyone seen that

Hi, I have done some debugging to find out the root cause of bug 1282, which has the following symptoms with paravirtualized guests: - after a live migrate, the time on the guest can jump - after a live migrate, the guest "forgets" to wake up processes - after a domU save, dom0 reboot and domU restore, the time is correct but processes are not woken up from sys_nanosleep The problem

I''m trying to get DHCP working with DomU clients. I don''t want to use libvirtd. There''s a dhcpd on the machine and it works fine for all clients in the network, but not for DomUs. If I set a static IP on the DomU all networking for them is fine, so there''s no general networking problem. I use the xen 3.2 packages for CentOS on CentOS 5.1. There was a public

Hi, Where is the mount option 'limit-rate' in the current version? I checked in cfgfile.c and in the documentation, no mention. Yet this option did exist at one time: http://lists.xiph.org/pipermail/icecast/2010-October/011703.html http://lists.xiph.org/pipermail/icecast/2009-January/011391.html I try to limit the bitrate of a mount-point, is there another solution? Do you know why this

Hi all, I've been trying to get an answer to this question for a long time and in a lot of different places, but no luck. Basically I want to mount an XP volume on my Linux machine at boot time over Samba. The network is just an XP box and a Linux box, connected by a crossover cable. The XP box is a gateway to the net (don't ask), with two NICs, one internal, and one going to the

Hello, I have a live migration problem on my setup. Migrated DomUs hang, but continue as normal when migrated back. Both nodes are i386 Debian Squeeze dom0 (xen 4.0.1 + pvops0 2.6.32-5-xen-686) Node A is a 32bits 2.4 Ghz Pentium4, node B is a 32bits 2.0 Ghz Celeron. DomUs are Debian Squeeze (2.6.32-5-xen-686 >= 2.6.32-22 or 2.6.32-5-686-bigmem >= 2.6.32-22) and Ubuntu Maverick

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up