Re: [CentOS-virt] Cannot start xen domUs anymore, domUs hang on kernel startup, happens after a long dom0 uptime
Pasi Kärkkäinen wrote: Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier. - This problem starts to happen after a "longer" uptime.. atm uptime for the dom0-host is 174 days. Cannot say what the actual "limit" is.. last time I used the dom0 everything worked fine, now it doesn't.. "xm list" shows the domain as "-b" and the Time(s) for the domain does not increase.. it stays at 1.9 or so. It might increase to 2.0 after 15 mins or so.. it looks like nothing happens in domU kernel. "xm console" shows the bootup has stalled.. destroying the domU and restarting it might show the hang in a bit different place (+- a couple of lines). It always hangs before actually executing initrd image. Example console output: checking if image is initramfs... it is Freeing initrd memory: 12028k freed Grant table initialized NET: Registered protocol family 16 SMP alternatives: switching to SMP code Like said, it could be a couple of lines later or earlier where it hangs.. I tried changing the domU to use just a single vcpu.. doesn't help. I tried changing (lowering and increasing) the amount of memory.. didn't help either. Any ideas how to debug this? -- Pasi ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt Sometimes xenconsoled dies after a while. Is it running when you attempt this? -- Christopher G. Stach II ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Check out Proxmox VE... can CentOS improve on this?
Greetings, I'm a big OpenVZ fanboy. I've sent a few emails on this list that proves that... and I'm sure I've annoyed some people... but be that as it may... I would like to draw everyone on this list's attention to Proxmox VE. What is Proxmox VE? Here's a review from the end of June: ProxMox: The high-performance virtualization server for the rest of us http://blogs.zdnet.com/BTL/?p=9181 It is a "bare-metal" Linux distribution based on Debian that has been stripped down to a minimum that includes a kernel that provides support for both KVM and OpenVZ so it does fully virtualized machines (requiring hardware support in the CPU) and containers. It has a nice web-based management system that is fairly feature complete and allows for the easy creation and management of KVM virtual machines and OpenVZ containers. It also has clustering features. That's a long enough description. Ok, how does this differ from everything else out there? 1) It is bare-metal... just pop in the CD (which is a 250MB download)... boot up the machine, answer about two questions... a few minutes worth of install time... and a reboot later... you have what looks very similar to a VMware ESX host... with a console (text) login screen that says... I man a Proxmox VE machine... connect to me at the following URL. Start browsing. 2) It supports both fully virtualized machines AND containers 3) It has a really nice, maturing (two releases so far) web-interface for managing everything 4) It is cluster aware - add additional Proxmox VE machines, use the really simple command line program to make each machine aware of all of the others... and bang the web-interface on any machine sees all of the virtual machines on all nodes 5) The web-interface includes VNC-java-applet based access so you can graphically attach to any virtual machine including the console of an OpenVZ container. For KVM machines, you get to see the BIOS / boot from ISO image before virtual machine is even on the network 6) Proxmox VE shows the potential that exists with a FOSS OS, FOSS Virtualization products... in a completely FOSS product... that is freaking easy to install, setup and use... that works well Problems - Some of the features aren't done yet. Proxmox VE is a little ahead of its time. Live migration doesn't quite work for OpenVZ yet (although it works fine in stock OpenVZ with their stable kernel branches). Proxmox VE is still in beta. Basically, if and when the Proxmox VE concept is fully realized and matured it'll be a killer app that makes business folks go... Linux DUH... for those that care about virtualization... like yoous guyyys on this hea list. Ok... so any chance CentOS or some of the members of the CentOS development community would like to borrow the Proxmox VE idea (perhaps even their web-interface code) and make something like Proxmox VE... but based on CentOS... that supports Xen and OpenVZ? It would have the benefit of being able to run on both systems with and without hardware support for Virtualization - if you have VT you can run fully virtualized Xen AND para-virtualized machines... if not... para-virtualized VMs only... and in both cases OpenVZ containers. The form-factor would have to retain all of the properties I mentioned above... I think... for it to be a huge success. Where to start? Get two machines to test on... desktops are fine as long as they have VT in the CPU. Download the 250MB Proxmox VE iso. Burn disc. Boot disk. Answer two questions. Wait 5 minutes. Reboot. Play with it. See what you think... and use your imagination. If impressed, plan the take over of the world with a similar setup based on CentOS. Then when RHEL6 comes out and KVM is here... switch to KVM. BTW, the OpenVZ Project had a kernel package built on the RHEL kernel that included both Xen and OpenVZ but I can't seem to find it now. Notice I'm not providing any links to Proxmox VE. You have to care enough to google for it. :) TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Cannot start xen domUs anymore, domUs hang on kernel startup, happens after a long dom0 uptime
Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier. - This problem starts to happen after a "longer" uptime.. atm uptime for the dom0-host is 174 days. Cannot say what the actual "limit" is.. last time I used the dom0 everything worked fine, now it doesn't.. "xm list" shows the domain as "-b" and the Time(s) for the domain does not increase.. it stays at 1.9 or so. It might increase to 2.0 after 15 mins or so.. it looks like nothing happens in domU kernel. "xm console" shows the bootup has stalled.. destroying the domU and restarting it might show the hang in a bit different place (+- a couple of lines). It always hangs before actually executing initrd image. Example console output: checking if image is initramfs... it is Freeing initrd memory: 12028k freed Grant table initialized NET: Registered protocol family 16 SMP alternatives: switching to SMP code Like said, it could be a couple of lines later or earlier where it hangs.. I tried changing the domU to use just a single vcpu.. doesn't help. I tried changing (lowering and increasing) the amount of memory.. didn't help either. Any ideas how to debug this? -- Pasi ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Re: NetBSD on CentOS 5.2 Xen 3
On Wed, 13 Aug 2008, white list wrote: hi all good people, can someone direct me to a solution i get the following error # xm create -c vm03 Using config file "./vm03". Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n') Have you actually tried to solve this problem yourself? I know nothing about your problem but http://mail-index.netbsd.org/port-xen/2008/01/29/msg003223.html sounds a lot like what you describe. Hint, if you put, "Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32" in google you might just get the info you need. Do not forget to include the quotes in your google search. Hope this helps. Regards, -- Tom Diehl [EMAIL PROTECTED] Spamtrap address [EMAIL PROTECTED] ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] NetBSD on Xen 3.1 CentOS 5.2
Thanks for your help Jerry, I did not know that! On Wed, Aug 13, 2008 at 9:29 AM, Jerry Amundson <[EMAIL PROTECTED]> wrote: > On Wed, Aug 13, 2008 at 11:06 AM, white list > <[EMAIL PROTECTED]> wrote: > > hi all good people, > > > > can someone direct me to a solution, I get the following error. > > > > # xm create -c vm03 > > Using config file "./vm03". > > Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type > xen-3.0-x86_32 > > not supported by xen kernel, sorry\n') > > Three words - inter net search > > jerry > > -- > Some people say I have A.D.D. but they just don't understand. Oh look! > A chicken! > ___ > CentOS-virt mailing list > CentOS-virt@centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] NetBSD on Xen 3.1 CentOS 5.2
On Wed, Aug 13, 2008 at 11:06 AM, white list <[EMAIL PROTECTED]> wrote: > hi all good people, > > can someone direct me to a solution, I get the following error. > > # xm create -c vm03 > Using config file "./vm03". > Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 > not supported by xen kernel, sorry\n') Three words - inter net search jerry -- Some people say I have A.D.D. but they just don't understand. Oh look! A chicken! ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] NetBSD on CentOS 5.2 Xen 3
hi all good people, can someone direct me to a solution i get the following error # xm create -c vm03 Using config file "./vm03". Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n') here is my configuration file /etc/xen/vm03 kernel="/boot/netbsd/netbsd-INSTALL_XEN3_DOMU.gz" name = "vm03" maxmem = 512 memory = 512 vcpus = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "tap:aio:/var/lib/xen/images/vm03.img,wd0d,w" ] vif = [ "mac=00:16:3e:fc:84:3c,bridge=xenbr0" ] Thanks, - Augustin ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] NetBSD on Xen 3.1 CentOS 5.2
hi all good people, can someone direct me to a solution, I get the following error. # xm create -c vm03 Using config file "./vm03". Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n') Here is my config file kernel="/boot/netbsd/netbsd-INSTALL_XEN3_DOMU.gz" (Download from amd64) name = "vm03" maxmem = 512 memory = 512 vcpus = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "tap:aio:/var/lib/xen/images/vm03.img,wd0d,w" ] vif = [ "mac=00:16:3e:fc:84:3c,bridge=xenbr0" ] ~ Thanks, - Augustin ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Djbdns Working in VPS ?
Scott Dowdle wrote: Ludwig, - "Lodewijk christoffel" <[EMAIL PROTECTED]> wrote: It is said at djbdnsrocks.org that it shouln't work on VPS or jails...i'm try it out on my VPS and nothing seems work, at least to see this thing working by using "ps -aux". I see on this (http://www.djbdnsrocks.org/single/getting_started.htm) page they say, "Virtual private servers (jails) will usually NOT work." That implies that a VPS is a jail. OpenVZ is much, much more than a jail and I see no reason it shouldn't work. TYL, Scott, Hahaha...i believe that too... I think that word just make a little confusion to new user like me.. Thank you Scott and Hristo. My question is now answered. Regards, Ludwig ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] NetBSD, FreeBSD on Xen 3.1
Hi all, please direct me to NetBSD install file or FreeBSD to install on Xen 3.1 on (CentOS 5.2) Thanks, - Augustin ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Djbdns Working in VPS ?
Ludwig, - "Lodewijk christoffel" <[EMAIL PROTECTED]> wrote: > It is said at djbdnsrocks.org that it shouln't work on VPS or > jails...i'm try it out on my VPS and nothing seems work, at > least to see this thing working by using "ps -aux". I see on this (http://www.djbdnsrocks.org/single/getting_started.htm) page they say, "Virtual private servers (jails) will usually NOT work." That implies that a VPS is a jail. OpenVZ is much, much more than a jail and I see no reason it shouldn't work. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Installing guest OS on Xen 3
Did you boot with "netbsd-XEN3_DOMU"? You should be boot with "netbsd-INSTALL_XEN3_DOMU". It has NetBSD installer image. Best regards. TAIRA Hajime <[EMAIL PROTECTED]>, web: http://pantora.net/ CentOS WikiName: HajimeTaira On 2008/08/13, at 1:34, white list wrote: > [EMAIL PROTECTED] xen]# xm create -c vm02 > Using config file "./vm02". > Started domain vm02 > Loaded initial symtab at 0x8064bbe4, strtab at 0x80697538, # > entries 12820 > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, > 2006, 2007, 2008 > The NetBSD Foundation, Inc. All rights reserved. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > NetBSD 4.99.72 (XEN3_DOMU) #0: Sat Aug 9 17:41:48 PDT 2008 > [EMAIL > PROTECTED]:/home/builds/ab/HEAD/amd64/200808090002Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOMU > total memory = 512 MB > avail memory = 487 MB > mainbus0 (root) > hypervisor0 at mainbus0: Xen version 3.1 > vcpu0 at hypervisor0: Intel 686-class, 3200MHz, id 0xf41 > vcpu0: 32 page colors > xenbus0 at hypervisor0: Xen Virtual Bus Interface > xencons0 at hypervisor0: Xen Virtual Console Driver > xencons0: using event channel 2 > xenbus0: using event channel 1 > unknown type vkbd at xenbus0 id 0 not configured > xbd0 at xenbus0 id 51712: Xen Virtual Block Device Interface > xennet0 at xenbus0 id 0: Xen Virtual Network Interface > xennet0: MAC address 00:16:3e:66:84:3c > unknown type vfb at xenbus0 id 0 not configured > xbd0: 8220 MB, 512 bytes/sect x 16836057 sectors > raidattach: Asked for 8 units > Kernelized RAIDframe activated > Searching for RAID components... > boot device: xbd0 > root on xbd0a dumps on xbd0b > mountroot: trying lfs... > mountroot: trying ffs... > mountroot: trying ext2fs... > mountroot: trying nfs... > mountroot: trying smbfs... > mountroot: trying ntfs... > unknown type vkbd at xenbus0 id 0 not configured > mountroot: trying msdos... > mountroot: trying cd9660... > mountroot: trying coda... > no file system for xbd0 (dev 0x8e00) > cannot mount root, error = 79 > root device (default xbd0a): > dump device (default xbd0b): > file system (default generic): > root on xbd0a dumps on xbd0b > mountroot: trying lfs... > mountroot: trying ffs... > mountroot: trying ext2fs... > mountroot: trying nfs... > mountroot: trying smbfs... > mountroot: trying ntfs... > mountroot: trying msdos... > mountroot: trying cd9660... > unknown type vfb at xenbus0 id 0 not configured > mountroot: trying coda... > no file system for xbd0 (dev 0x8e00) > cannot mount root, error = 79 > root device (default xbd0a): / > use one of: xbd0[a-p] xennet0 md0[a-p] ddb halt reboot > root device (default xbd0a): > dump device (default xbd0b): > file system (default generic): > root on xbd0a dumps on xbd0b > mountroot: trying lfs... > mountroot: trying ffs... > mountroot: trying ext2fs... > mountroot: trying nfs... > mountroot: trying smbfs... > mountroot: trying ntfs... > mountroot: trying msdos... > mountroot: trying cd9660... > mountroot: trying coda... > no file system for xbd0 (dev 0x8e00) > cannot mount root, error = 79 > root device (default xbd0a): > dump device (default xbd0b): > file system (default generic): / > use one of: generic lfs ffs ext2fs nfs smbfs ntfs msdos cd9660 coda ddb halt > reboot > file system (default generic): generic lfs > use one of: generic lfs ffs ext2fs nfs smbfs ntfs msdos cd9660 coda ddb halt > reboot > file system (default generic): lfs > root on xbd0a dumps on xbd0b > cannot mount root, error = 5 > root device (default xbd0a): xbd0a > dump device (default xbd0b): xbd0b > file system (default lfs): lfs > root on xbd0a dumps on xbd0b > cannot mount root, error = 5 > root device (default xbd0a): /dev/xbd0a > use one of: xbd0[a-p] xennet0 md0[a-p] ddb halt reboot > root device (default xbd0a): xbd0d > dump device (default xbd0b): xbd0e > file system (default lfs): xbd0f > use one of: generic lfs ffs ext2fs nfs smbfs ntfs msdos cd9660 coda ddb halt > reboot > file system (default lfs): ffs > root on xbd0d dumps on xbd0e > cannot mount root, error = 5 > root device (default xbd0d): ext2fs > use one of: xbd0[a-p] xennet0 md0[a-p] ddb halt reboot > root device (default xbd0d): xbd0a > dump device (default xbd0b): xbd0b > file system (default ffs): ext2fs > root on xbd0a dumps on xbd0b > cannot mount root, error = 5 > root device (default xbd0a): > > > Thanks a bunch, > it work, however i'm stuck with the error above. > any idea? > Thanks, > - Augustin > > > > > > On Tue, Aug 12, 2008 at 5:58 AM, TAIRA Hajime <[EMAIL PROTECTED]> wrote: > Hi, > > You had a mistake. If you want to boot from kernel image. > Didn't set builder='hvm'. Please try to use following configuration. > > kernel="/boot/netbsd/netbsd-XEN3_DOMU" > #builder='hvm' > name = "vm02" > maxmem = 512 > memory = 512 > vcpus = 1 > #bootloader = "/usr/bin/pygrub" > on_poweroff = "destroy" > on_reboot = "re
