From barry.scott at onelan.co.uk Tue Apr 1 11:30:44 2008 From: barry.scott at onelan.co.uk (Barry Scott) Date: Tue, 01 Apr 2008 12:30:44 +0100 Subject: [Fedora-xen] Domain will not stop Message-ID: <47F21CE4.10909@onelan.co.uk> I'm setting up a VM called svn-server running fedora 8. After login in as root on the console and doing "halt -p" the domain has got stuck in this state. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 981 2 r----- 80476.9 svn-server 18 1024 1 ---s-d 22.8 When I try to do destroy on the domain I get: # virsh destroy svn-server libvir: Xen Daemon error : POST operation failed: (xend.err "(3, 'No such process')") libvir: Xen error : failed Xen syscall ioctl 3166208 error: Failed to destroy domain svn-server Is there any way to recover without rebooting? xm info give me: # xm info host : hotel.office.onelan.co.uk release : 2.6.21-2952.fc8xen version : #1 SMP Mon Nov 19 07:06:36 EST 2007 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1800 hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f total_memory : 2047 free_memory : 1024 xen_major : 3 xen_minor : 1 xen_extra : .0-rc7 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) cc_compile_by : kojibuilder cc_compile_domain : (none) cc_compile_date : Mon Nov 19 07:04:51 EST 2007 xend_config_format : 4 Barry From fred at derf.nl Tue Apr 1 12:18:45 2008 From: fred at derf.nl (Friedrich Clausen) Date: Tue, 1 Apr 2008 14:18:45 +0200 Subject: [Fedora-xen] Domain will not stop In-Reply-To: <47F21CE4.10909@onelan.co.uk> References: <47F21CE4.10909@onelan.co.uk> Message-ID: Hi, On Tue, Apr 1, 2008 at 1:30 PM, Barry Scott wrote: > I'm setting up a VM called svn-server running fedora 8. > After login in as root on the console and doing "halt -p" the > domain has got stuck in this state. You can always use : # xm destroy svn-server as this bypasses virsh. Cheers, Fred. > > > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 981 2 r----- > 80476.9 > svn-server 18 1024 1 > ---s-d 22.8 > > When I try to do destroy on the domain I get: > > # virsh destroy svn-server > libvir: Xen Daemon error : POST operation failed: (xend.err "(3, 'No > such process')") > libvir: Xen error : failed Xen syscall ioctl 3166208 > error: Failed to destroy domain svn-server > > Is there any way to recover without rebooting? > > xm info give me: > > # xm info > host : hotel.office.onelan.co.uk > release : 2.6.21-2952.fc8xen > version : #1 SMP Mon Nov 19 07:06:36 EST 2007 > machine : x86_64 > nr_cpus : 2 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 1800 > hw_caps : > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > total_memory : 2047 > free_memory : 1024 > xen_major : 3 > xen_minor : 1 > xen_extra : .0-rc7 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) > cc_compile_by : kojibuilder > cc_compile_domain : (none) > cc_compile_date : Mon Nov 19 07:04:51 EST 2007 > xend_config_format : 4 > > Barry > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From barry.scott at onelan.co.uk Tue Apr 1 14:08:35 2008 From: barry.scott at onelan.co.uk (Barry Scott) Date: Tue, 01 Apr 2008 15:08:35 +0100 Subject: [Fedora-xen] Domain will not stop In-Reply-To: References: <47F21CE4.10909@onelan.co.uk> Message-ID: <47F241E3.1000609@onelan.co.uk> Friedrich Clausen wrote: > Hi, > > On Tue, Apr 1, 2008 at 1:30 PM, Barry Scott > wrote: > > I'm setting up a VM called svn-server running fedora 8. > After login in as root on the console and doing "halt -p" the > domain has got stuck in this state. > > > You can always use : > > # xm destroy svn-server > > as this bypasses virsh. > I have already tried that but it fails as well. Barry From zzojaji at aim.com Tue Apr 1 17:44:17 2008 From: zzojaji at aim.com (zzojaji at aim.com) Date: Tue, 01 Apr 2008 13:44:17 -0400 Subject: [Fedora-xen] Problem with XEN In-Reply-To: <882854.53356.qm@web36202.mail.mud.yahoo.com> References: <882854.53356.qm@web36202.mail.mud.yahoo.com> Message-ID: <8CA623724C63BF8-20C-10E0@FWM-D08.sysops.aol.com> Hi Swethu! do you have enough space in /home folder for a guest image? and did you disable firewall by "service iptables stop"? i'm not sure but it may help! Regards, Zahra Zojaji -----Original Message----- From: swethu bandaru To: fedora-xen at redhat.com Sent: Mon, 31 Mar 2008 10:20 am Subject: [Fedora-xen] Problem with XEN Respected Sir, When we are trying to install a guest os by using xen in fedora6 I am using virt-install command and i have specified the following What is the name of the VM ?guest1 How much RAM should be allocated in MB ? 200 What would you like to use as the diskpath ? /home/xenbox.img What is the install location ?nfs:192.168.5.47:/home/fc6 In /home/fc6 folder we have the fc6 installation docs. when i used xm list command we have found the guest os guest1 and its permission as -b----- when we have given xm create -c guest1 then we got the errors UNABLE TO READ FILE SYSTEM BOOTLOADER DIDN.T RETURN ANY DATA please help me with this problem Thank you! Like movies? Here's a limited-time offer: Blockbuster Total Access for one month at no cost.-- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From davidl at matissenetworks.com Wed Apr 2 00:56:53 2008 From: davidl at matissenetworks.com (David Levinger) Date: Tue, 1 Apr 2008 17:56:53 -0700 (PDT) Subject: [Fedora-xen] Possible Stupid Question... In-Reply-To: <8CA623724C63BF8-20C-10E0@FWM-D08.sysops.aol.com> References: <882854.53356.qm@web36202.mail.mud.yahoo.com> <8CA623724C63BF8-20C-10E0@FWM-D08.sysops.aol.com> Message-ID: <002401c8945c$684c92d0$0200000a@nbdavidl> Hey guys, Been loving Xen and playing around with it for awhile now but recently tried something new and had a really weird result, not sure if it is at all related to Xen so I'm gonna ask here. 1. I have a SATA based Xen x64 machine running a para-virtualized x64 VM, that VM is written out to an LVM Partition. /dev/vgmachine/lvVM 2. I shut down that VM and then dd_rescue it over to another machine. (With the same LVM setup) 3. The other machine is running the same exact host OS but has SAS based IO instead of SATA. 4. When I bring up the Xen machine on the SAS host the whole computer gets hosed. I see SAS controller errors and I have to hard power the machine. I'm building a new Xen machine on the SAS host now and it doesn't seem to be causing trouble, did I do something stupid in assuming that I could move a Para-virtualized machine from one type of IO to another? David -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomas at jikos.cz Wed Apr 2 10:50:44 2008 From: tomas at jikos.cz (=?windows-1252?Q?Tom=E1=9A_Kouba?=) Date: Wed, 02 Apr 2008 12:50:44 +0200 Subject: [Fedora-xen] iwlwifi with 2.6.21-7.fc7xen Message-ID: <47F36504.4000505@jikos.cz> Hello, is anybody on this mailing list using iwlwifi driver with fedora and xen kernel? I have downloaded sources, untarred but it doesn't compile with error: include/asm/fixmap.h: At top level: include/asm/fixmap.h:110: error: expected declaration specifiers or ?...? before ?maddr_t? In file included from include/asm/elf.h:52, from include/linux/elf.h:7, from include/linux/module.h:15, from /root/iwlwifi/iwlwifi-1.2.25/compatible/iwl3945-base.c:31: The problem is this line: extern void __set_fixmap(enum fixed_addresses idx, maddr_t phys, pgprot_t flags); I am not very sure what gcc complains about maddr_t. Thanks for any help. -- Tomas Kouba From Dustin.Henning at prd-inc.com Wed Apr 2 13:19:27 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 2 Apr 2008 09:19:27 -0400 Subject: [Fedora-xen] Possible Stupid Question... Message-ID: <000e01c894c4$2d51de20$87f59a60$@Henning@prd-inc.com> David, This is probably a "something stupid" related to Linux more than Xen. It sounds like the system isn't booting at all, and the most likely cause is that the drivers necessary for the SAS are not in the kernel. Linux picks appropriate drivers for the machine you install on and then all updates use those drivers, so when you move to new hardware, it just doesn't work. If you copy the kernel and modules from the working machine to the machine that didn't work when you did your dd_rescue, it might boot with them, however, when it comes time to update, you will need to manually compile your new kernels instead of using the standard automated update method, i.e. do the standard update, ut then do a custom compile and boot to the custom kernel, not the one from the standard update, as it ill crash, but the custom compiled one will be compatible with the other changes made by the automatic update. This is far from detailed and complete, as it has been a while since I have dealt with that kind of thing, but I most often experienced it switching from "Compatibility Mode" SATA to AHCI on some machines that I didn't want to rebuild. I n your case, a rebuild on the problem machine is probably a better option, as you can then migrate whatever you want however you want to a clean machine with no thorn in its side. Dustin From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Levinger Sent: Tuesday, April 01, 2008 20:57 To: fedora-xen at redhat.com Subject: [Fedora-xen] Possible Stupid Question... Hey guys, Been loving Xen and playing around with it for awhile now but recently tried something new and had a really weird result, not sure if it is at all related to Xen so I'm gonna ask here. 1. I have a SATA based Xen x64 machine running a para-virtualized x64 VM, that VM is written out to an LVM Partition. /dev/vgmachine/lvVM 2. I shut down that VM and then dd_rescue it over to another machine. (With the same LVM setup) 3. The other machine is running the same exact host OS but has SAS based IO instead of SATA. 4. When I bring up the Xen machine on the SAS host the whole computer gets hosed. I see SAS controller errors and I have to hard power the machine. I'm building a new Xen machine on the SAS host now and it doesn't seem to be causing trouble, did I do something stupid in assuming that I could move a Para-virtualized machine from one type of IO to another? David -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gerrard.Geldenhuis at datacash.com Thu Apr 3 14:06:35 2008 From: Gerrard.Geldenhuis at datacash.com (Gerrard Geldenhuis) Date: Thu, 3 Apr 2008 15:06:35 +0100 Subject: [Fedora-xen] root element in config file Message-ID: Hi I am trying to put together a working xml file to create a new domain.... The root element is baffling me a bit. from the http://libvirt.org/ website root: the root filesystem from the guest viewpoint, it may be passed as part of the cmdline content too My current value is /dev/xvd but that was automatically created by satellite which I am trying to adapt for my own use. When I do a virsh create config file I get the following error: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\\n')") If someone would'nt mind explaing a bit more what this root file system is... Regards From WCoole at aperiogroup.com Thu Apr 3 18:04:20 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Thu, 3 Apr 2008 11:04:20 -0700 Subject: [Fedora-xen] Newby Help In-Reply-To: <87ej9wpc56.fsf@pike.pond.sub.org> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local><47E9A056.5090008@redhat.com><4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local><47EA4173.8050609@redhat.com><4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> <87ej9wpc56.fsf@pike.pond.sub.org> Message-ID: <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> Thanks for the hint; sorry it took so long for me to try several different approaches. I hadn't tried virt-install; I had assumed that virt-manager's Create Wizard did the equivalent job. Trying virt-install, this is what my session looked like: sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 --nographics --noautoconsole -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ Password: Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID Retrieving file fedora.cs 100% |=========================| 2.3 kB 00:00 Retrieving file vmlinuz.. 100% |=========================| 1.8 MB 00:00 Retrieving file initrd.im 100% |=========================| 5.6 MB 00:01 libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Creating storage file... 100% |=========================| 4.0 GB 00:00 Creating domain... 0 B 00:00 Domain installation still in progress. You can reconnect to the console to complete the installation process. I got to virt-manager, where a new machine named "hockey" has just showed up, which I open and view serial console. I see what looks like an Anaconda session, asking "Choose a Language". I pick English, US, deselect dynamic IP and IPv6, set 192.168.1.201/24,192.168.1.1,192.168.1.2 . It says "Retrieving images/minstg2.img..." and stays there forever 192.168.1.117 is our internal Apache server, to which I've mirrored download.fedora.redhat.com/pub/fedora. Just as a check, I downloaded http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/images/sta ge2.img with my browser and got a 78M file. It seems as though the image is being built by virt-install, but that the network settings aren't allowing the virtual machine to talk to the install server properly. I don't know Anaconda well enough to change or even examine the network settings it uses. Perhaps there is a problem with not using DHCP? It seems that several of other approaches I've tried are encountering the same underlying issue, but with different symptoms. Thanks! Walter -----Original Message----- From: Markus Armbruster [mailto:armbru at redhat.com] Sent: Thursday, March 27, 2008 5:47 AM To: Walter Coole Cc: Chris Lalancette; fedora-xen at redhat.com Subject: Re: [Fedora-xen] Newby Help You need to tell us *exactly* how you run virt-install, and what error you get back. From armbru at redhat.com Fri Apr 4 07:57:32 2008 From: armbru at redhat.com (Markus Armbruster) Date: Fri, 04 Apr 2008 09:57:32 +0200 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> (Walter Coole's message of "Thu\, 3 Apr 2008 11\:04\:20 -0700") References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> <87ej9wpc56.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> Message-ID: <87y77u6oib.fsf@pike.pond.sub.org> "Walter Coole" writes: > Thanks for the hint; sorry it took so long for me to try several > different approaches. > > I hadn't tried virt-install; I had assumed that virt-manager's Create > Wizard did the equivalent job. Uh, I must have somehow missed that you used virt-manager, not virt-install. Telling us exactly how you interact with either is fine. Telling us how you run virt-install is easier, though. > Trying virt-install, this is what my session looked like: > > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 > --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > Password: This is an unusual image location. Is SELinux enabled? Does /var/lib/xen/images/hockey.img work? [...] From Gerrard.Geldenhuis at datacash.com Fri Apr 4 12:21:32 2008 From: Gerrard.Geldenhuis at datacash.com (Gerrard Geldenhuis) Date: Fri, 4 Apr 2008 13:21:32 +0100 Subject: [Fedora-xen] Accessing other terminals Message-ID: Hi How do I access other terminals during a kickstart installation? I am using virsh to create the xen domain. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From barry.scott at onelan.co.uk Fri Apr 4 14:21:23 2008 From: barry.scott at onelan.co.uk (Barry Scott) Date: Fri, 04 Apr 2008 15:21:23 +0100 Subject: [Fedora-xen] Accessing other terminals In-Reply-To: References: Message-ID: <47F63963.5090607@onelan.co.uk> Gerrard Geldenhuis wrote: > > Hi > > How do I access other terminals during a kickstart installation? > > I am using virsh to create the xen domain. > Do you mean the screen you switch to with Ctrl-Alt-F[1-7]? Use a VNC console and type Alt-F[1-7]. Barry From Gerrard.Geldenhuis at datacash.com Fri Apr 4 14:26:02 2008 From: Gerrard.Geldenhuis at datacash.com (Gerrard Geldenhuis) Date: Fri, 4 Apr 2008 15:26:02 +0100 Subject: [Fedora-xen] Accessing other terminals In-Reply-To: <47F63963.5090607@onelan.co.uk> References: <47F63963.5090607@onelan.co.uk> Message-ID: Would there be any other way apart from using vnc? Regards > -----Original Message----- > From: Barry Scott [mailto:barry.scott at onelan.co.uk] > Sent: 04 April 2008 15:21 > To: Gerrard Geldenhuis > Cc: Fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Accessing other terminals > > Gerrard Geldenhuis wrote: > > > > Hi > > > > How do I access other terminals during a kickstart installation? > > > > I am using virsh to create the xen domain. > > > Do you mean the screen you switch to with Ctrl-Alt-F[1-7]? > Use a VNC console and type Alt-F[1-7]. > > Barry From WCoole at aperiogroup.com Mon Apr 7 22:41:25 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Mon, 7 Apr 2008 15:41:25 -0700 Subject: [Fedora-xen] Newby Help In-Reply-To: <87y77u6oib.fsf@pike.pond.sub.org> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local><47E9A056.5090008@redhat.com><4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local><47EA4173.8050609@redhat.com><4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local><87ej9wpc56.fsf@pike.pond.sub.org><4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> Message-ID: <4292CEA5F4927248979C701CA83500BB83DDE6@SERVER.aperiogroup.local> The originating host (where I'm running virt-install) has SELinux in "Permissive" mode. The web server (192.168.1.117) had SELinux in "Secure" mode, so I changed it to "Permissive" mode. I don't think SELinux is started on the system being installed, but if someone knows how to set or confirm that, I'd be happy to be corrected. I'm not finicky about the path where the file lives, so I tried it with /var/lib/xen/images/hockey.img. The symptom is unchanged: stuck at minstg2.img. The revised command line is: sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s 4 --nographics --noautoconsole -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ Thanks! Walter -----Original Message----- From: Markus Armbruster [mailto:armbru at redhat.com] Sent: Friday, April 04, 2008 12:58 AM To: Walter Coole Cc: Chris Lalancette; fedora-xen at redhat.com Subject: Re: [Fedora-xen] Newby Help "Walter Coole" writes: > Thanks for the hint; sorry it took so long for me to try several > different approaches. > > I hadn't tried virt-install; I had assumed that virt-manager's Create > Wizard did the equivalent job. Uh, I must have somehow missed that you used virt-manager, not virt-install. Telling us exactly how you interact with either is fine. Telling us how you run virt-install is easier, though. > Trying virt-install, this is what my session looked like: > > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 > --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > Password: This is an unusual image location. Is SELinux enabled? Does /var/lib/xen/images/hockey.img work? [...] From barry.scott at onelan.co.uk Tue Apr 8 10:52:12 2008 From: barry.scott at onelan.co.uk (Barry Scott) Date: Tue, 08 Apr 2008 11:52:12 +0100 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DDE6@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local><47E9A056.5090008@redhat.com><4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local><47EA4173.8050609@redhat.com><4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local><87ej9wpc56.fsf@pike.pond.sub.org><4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DDE6@SERVER.aperiogroup.local> Message-ID: <47FB4E5C.6040609@onelan.co.uk> Walter Coole wrote: > The originating host (where I'm running virt-install) has SELinux in > "Permissive" mode. The web server (192.168.1.117) had SELinux in > "Secure" mode, so I changed it to "Permissive" mode. I don't think > SELinux is started on the system being installed, but if someone knows > how to set or confirm that, I'd be happy to be corrected. I'm not > finicky about the path where the file lives, so I tried it with > /var/lib/xen/images/hockey.img. The symptom is unchanged: stuck at > minstg2.img. > > The revised command line is: > > sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s > 4 --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > > Use a VNC console so that you can look at the extra screens of info from anaconda. In VNC use ALT-F[0-7] to switch console windows. Alt-F2 and Alt-F3 are usually interesting. Barry From WCoole at aperiogroup.com Tue Apr 8 18:44:05 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Tue, 8 Apr 2008 11:44:05 -0700 Subject: [Fedora-xen] Newby Help References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local><47E9A056.5090008@redhat.com><4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local><47EA4173.8050609@redhat.com><4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local><87ej9wpc56.fsf@pike.pond.sub.org><4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> Message-ID: <4292CEA5F4927248979C701CA83500BB83DE4E@SERVER.aperiogroup.local> Thanks for the suggestion. I tried it and Alt-F3 showed a message about dropping to a serial console due to lack of memory, so I tried it again with this command line: sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s 4 --vnc -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ Password: Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID Retrieving file fedora.cs 100% |=========================| 2.3 kB 00:00 Retrieving file vmlinuz.. 100% |=========================| 1.8 MB 00:00 Retrieving file initrd.im 100% |=========================| 5.6 MB 00:00 libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Creating storage file... 100% |=========================| 4.0 GB 00:00 Creating domain... 0 B 00:00 VNC Viewer Free Edition 4.1.2 for X - built Jul 18 2006 06:59:52 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Tue Apr 8 11:14:19 2008 main: unable to resolve host by name: Success (0) Domain installation still in progress. You can reconnect to the console to complete the installation process. and a dialog box with the same message: unable to resolve host by name: Success (0) popped up on my workstation. Despite that, Virtual Machine Manager was able to open it, so I see the Anaconda window. Most of the console windows are blank, but a screenshot of Alt-F3 is attached, in hopes someone can interpret it with more success than I've had. The serial console shows: IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1207679422.076:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 4D36EEF71C3A3150 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Console: switching to colour frame buffer device 100x37 input: Xen Virtual Keyboard/Mouse as /class/input/input0 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/vkbd/0 XENBUS: Device with no driver: device/vfb/0 Write protecting the kernel read-only data: 440k Looking at the screen shot, it appears that several transfers from the tree were successful, which makes it seem as though basic networking is working. Since the messaging for stage2.img is the same, it looks as though that was also successful and the hang up is in the next item. Not having seen it, I'm pretty vague on what it is or why it might fail. I didn't check Alt-F4, as that causes the window to go away (on Windows XP), is it likely to be interesting? If so, is there an alternate way to get at it? Continued thanks! Walter -----Original Message----- From: Walter Coole Sent: Monday, April 07, 2008 3:41 PM To: 'Markus Armbruster' Cc: Chris Lalancette; fedora-xen at redhat.com Subject: RE: [Fedora-xen] Newby Help The originating host (where I'm running virt-install) has SELinux in "Permissive" mode. The web server (192.168.1.117) had SELinux in "Secure" mode, so I changed it to "Permissive" mode. I don't think SELinux is started on the system being installed, but if someone knows how to set or confirm that, I'd be happy to be corrected. I'm not finicky about the path where the file lives, so I tried it with /var/lib/xen/images/hockey.img. The symptom is unchanged: stuck at minstg2.img. The revised command line is: sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s 4 --nographics --noautoconsole -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ Thanks! Walter -----Original Message----- From: Markus Armbruster [mailto:armbru at redhat.com] Sent: Friday, April 04, 2008 12:58 AM To: Walter Coole Cc: Chris Lalancette; fedora-xen at redhat.com Subject: Re: [Fedora-xen] Newby Help "Walter Coole" writes: > Thanks for the hint; sorry it took so long for me to try several > different approaches. > > I hadn't tried virt-install; I had assumed that virt-manager's Create > Wizard did the equivalent job. Uh, I must have somehow missed that you used virt-manager, not virt-install. Telling us exactly how you interact with either is fine. Telling us how you run virt-install is easier, though. > Trying virt-install, this is what my session looked like: > > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 > --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > Password: This is an unusual image location. Is SELinux enabled? Does /var/lib/xen/images/hockey.img work? [...] -------------- next part -------------- A non-text attachment was scrubbed... Name: shot2.png Type: image/png Size: 24201 bytes Desc: shot2.png URL: From mnielsen at redhat.com Tue Apr 8 19:01:00 2008 From: mnielsen at redhat.com (Mark Nielsen) Date: Tue, 08 Apr 2008 15:01:00 -0400 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DE4E@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> <87ej9wpc56.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DE4E@SERVER.aperiogroup.local> Message-ID: <1207681260.11296.38.camel@localhost.localdomain> (resend to all + additional comment) try the --nogfx option with virt-install, and/or use -x "linux text" which should cause the install to proceed in a text mode. From the looks of that message things are actually installing but showing in a graphical console which you can't see (for whatever reason..) Mark On Tue, 2008-04-08 at 11:44 -0700, Walter Coole wrote: > Thanks for the suggestion. I tried it and Alt-F3 showed a message about > dropping to a serial console due to lack of memory, so I tried it again > with this command line: > > sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s > 4 --vnc -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > Password: > > > Starting install... > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID > Retrieving file fedora.cs 100% |=========================| 2.3 kB > 00:00 > Retrieving file vmlinuz.. 100% |=========================| 1.8 MB > 00:00 > Retrieving file initrd.im 100% |=========================| 5.6 MB > 00:00 > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > Creating storage file... 100% |=========================| 4.0 GB > 00:00 > Creating domain... 0 B > 00:00 > > VNC Viewer Free Edition 4.1.2 for X - built Jul 18 2006 06:59:52 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Tue Apr 8 11:14:19 2008 > main: unable to resolve host by name: Success (0) > Domain installation still in progress. You can reconnect to > the console to complete the installation process. > > and a dialog box with the same message: > > unable to resolve host by name: Success (0) > > popped up on my workstation. Despite that, Virtual Machine Manager was > able to open it, so I see the Anaconda window. Most of the console > windows are blank, but a screenshot of Alt-F3 is attached, in hopes > someone can interpret it with more success than I've had. The serial > console shows: > > IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > TCP established hash table entries: 131072 (order: 10, 4194304 bytes) > TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > IA-32 Microcode Update Driver: v1.14-xen > audit: initializing netlink socket (disabled) > audit(1207679422.076:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key 4D36EEF71C3A3150 > - User ID: Red Hat, Inc. (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Console: switching to colour frame buffer device 100x37 > input: Xen Virtual Keyboard/Mouse as /class/input/input0 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver libusual > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/vkbd/0 > XENBUS: Device with no driver: device/vfb/0 > Write protecting the kernel read-only data: 440k > > Looking at the screen shot, it appears that several transfers from the > tree were successful, which makes it seem as though basic networking is > working. Since the messaging for stage2.img is the same, it looks as > though that was also successful and the hang up is in the next item. > Not having seen it, I'm pretty vague on what it is or why it might fail. > I didn't check Alt-F4, as that causes the window to go away (on Windows > XP), is it likely to be interesting? If so, is there an alternate way > to get at it? > > Continued thanks! > Walter > > > -----Original Message----- > From: Walter Coole > Sent: Monday, April 07, 2008 3:41 PM > To: 'Markus Armbruster' > Cc: Chris Lalancette; fedora-xen at redhat.com > Subject: RE: [Fedora-xen] Newby Help > > The originating host (where I'm running virt-install) has SELinux in > "Permissive" mode. The web server (192.168.1.117) had SELinux in > "Secure" mode, so I changed it to "Permissive" mode. I don't think > SELinux is started on the system being installed, but if someone knows > how to set or confirm that, I'd be happy to be corrected. I'm not > finicky about the path where the file lives, so I tried it with > /var/lib/xen/images/hockey.img. The symptom is unchanged: stuck at > minstg2.img. > > The revised command line is: > > sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s > 4 --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > > Thanks! > Walter > > > -----Original Message----- > From: Markus Armbruster [mailto:armbru at redhat.com] > Sent: Friday, April 04, 2008 12:58 AM > To: Walter Coole > Cc: Chris Lalancette; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Newby Help > > "Walter Coole" writes: > > > Thanks for the hint; sorry it took so long for me to try several > > different approaches. > > > > I hadn't tried virt-install; I had assumed that virt-manager's Create > > Wizard did the equivalent job. > > Uh, I must have somehow missed that you used virt-manager, not > virt-install. Telling us exactly how you interact with either is > fine. Telling us how you run virt-install is easier, though. > > > Trying virt-install, this is what my session looked like: > > > > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 > > --nographics --noautoconsole -l > > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > > Password: > > This is an unusual image location. Is SELinux enabled? Does > /var/lib/xen/images/hockey.img work? > > [...] > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Mark Nielsen, RHCE Red Hat, Inc. mnielsen at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2145 bytes Desc: not available URL: From WCoole at aperiogroup.com Tue Apr 8 19:32:40 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Tue, 8 Apr 2008 12:32:40 -0700 Subject: [Fedora-xen] Newby Help In-Reply-To: <1207681260.11296.38.camel@localhost.localdomain> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> <87ej9wpc56.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DE4E@SERVER.aperiogroup.local> <1207681260.11296.38.camel@localhost.localdomain> Message-ID: <4292CEA5F4927248979C701CA83500BB83DE60@SERVER.aperiogroup.local> My version of virt-install doesn't understand --nogfx, but I tried: sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s 4 --nographics -x "linux text" -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os , which led to a partial success. Anaconda got well beyond the minstg2.img step (although I don't really know why this would work. It did give me this: ?????????????????????????????? Error ?????????????????????????????? ? ? ? Unable to read package metadata. This may be due to a missing ? ? repodata directory. Please ensure that your install tree has ? ? been correctly generated. Cannot open/read repomd.xml file ? ? for repository: anaconda-base-200610172015.x86_64 ? ? ? ? ????????? ? ? ? Abort ? ? ? ????????? ? ? ? ? ? ??????????????????????????????????????????????????????????????????? I don't really understand what it's looking for, since http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/repodata/repomd.xml is there and looks like sensible XML to a casual glance. It doesn't refer to anything like "anaconda-base-200610172015.x86_64". 192.168.1.117/mirror has a copy of download.fedora.redhat.com/pub/fedora, as I don't know of a better place to get a tree from. I'm running out of space and bandwidth, so it's not complete, but pub/fedora/linux/core/6/x86_64 looks complete. Walter -----Original Message----- From: Mark Nielsen [mailto:mnielsen at redhat.com] Sent: Tuesday, April 08, 2008 12:01 PM To: Walter Coole Cc: barry.scott at onelan.co.uk; Markus Armbruster; fedora-xen at redhat.com Subject: RE: [Fedora-xen] Newby Help (resend to all + additional comment) try the --nogfx option with virt-install, and/or use -x "linux text" which should cause the install to proceed in a text mode. From the looks of that message things are actually installing but showing in a graphical console which you can't see (for whatever reason..) Mark On Tue, 2008-04-08 at 11:44 -0700, Walter Coole wrote: > Thanks for the suggestion. I tried it and Alt-F3 showed a message about > dropping to a serial console due to lack of memory, so I tried it again > with this command line: > > sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s > 4 --vnc -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > Password: > > > Starting install... > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID > Retrieving file fedora.cs 100% |=========================| 2.3 kB > 00:00 > Retrieving file vmlinuz.. 100% |=========================| 1.8 MB > 00:00 > Retrieving file initrd.im 100% |=========================| 5.6 MB > 00:00 > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > Creating storage file... 100% |=========================| 4.0 GB > 00:00 > Creating domain... 0 B > 00:00 > > VNC Viewer Free Edition 4.1.2 for X - built Jul 18 2006 06:59:52 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Tue Apr 8 11:14:19 2008 > main: unable to resolve host by name: Success (0) > Domain installation still in progress. You can reconnect to > the console to complete the installation process. > > and a dialog box with the same message: > > unable to resolve host by name: Success (0) > > popped up on my workstation. Despite that, Virtual Machine Manager was > able to open it, so I see the Anaconda window. Most of the console > windows are blank, but a screenshot of Alt-F3 is attached, in hopes > someone can interpret it with more success than I've had. The serial > console shows: > > IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > TCP established hash table entries: 131072 (order: 10, 4194304 bytes) > TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > IA-32 Microcode Update Driver: v1.14-xen > audit: initializing netlink socket (disabled) > audit(1207679422.076:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key 4D36EEF71C3A3150 > - User ID: Red Hat, Inc. (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Console: switching to colour frame buffer device 100x37 > input: Xen Virtual Keyboard/Mouse as /class/input/input0 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver libusual > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/vkbd/0 > XENBUS: Device with no driver: device/vfb/0 > Write protecting the kernel read-only data: 440k > > Looking at the screen shot, it appears that several transfers from the > tree were successful, which makes it seem as though basic networking is > working. Since the messaging for stage2.img is the same, it looks as > though that was also successful and the hang up is in the next item. > Not having seen it, I'm pretty vague on what it is or why it might fail. > I didn't check Alt-F4, as that causes the window to go away (on Windows > XP), is it likely to be interesting? If so, is there an alternate way > to get at it? > > Continued thanks! > Walter > > > -----Original Message----- > From: Walter Coole > Sent: Monday, April 07, 2008 3:41 PM > To: 'Markus Armbruster' > Cc: Chris Lalancette; fedora-xen at redhat.com > Subject: RE: [Fedora-xen] Newby Help > > The originating host (where I'm running virt-install) has SELinux in > "Permissive" mode. The web server (192.168.1.117) had SELinux in > "Secure" mode, so I changed it to "Permissive" mode. I don't think > SELinux is started on the system being installed, but if someone knows > how to set or confirm that, I'd be happy to be corrected. I'm not > finicky about the path where the file lives, so I tried it with > /var/lib/xen/images/hockey.img. The symptom is unchanged: stuck at > minstg2.img. > > The revised command line is: > > sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s > 4 --nographics --noautoconsole -l > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > > Thanks! > Walter > > > -----Original Message----- > From: Markus Armbruster [mailto:armbru at redhat.com] > Sent: Friday, April 04, 2008 12:58 AM > To: Walter Coole > Cc: Chris Lalancette; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Newby Help > > "Walter Coole" writes: > > > Thanks for the hint; sorry it took so long for me to try several > > different approaches. > > > > I hadn't tried virt-install; I had assumed that virt-manager's Create > > Wizard did the equivalent job. > > Uh, I must have somehow missed that you used virt-manager, not > virt-install. Telling us exactly how you interact with either is > fine. Telling us how you run virt-install is easier, though. > > > Trying virt-install, this is what my session looked like: > > > > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 > > --nographics --noautoconsole -l > > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ > > Password: > > This is an unusual image location. Is SELinux enabled? Does > /var/lib/xen/images/hockey.img work? > > [...] > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Mark Nielsen, RHCE Red Hat, Inc. mnielsen at redhat.com From berrange at redhat.com Tue Apr 8 19:41:56 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 8 Apr 2008 20:41:56 +0100 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DE60@SERVER.aperiogroup.local> References: <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> <87ej9wpc56.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DCAD@SERVER.aperiogroup.local> <87y77u6oib.fsf@pike.pond.sub.org> <4292CEA5F4927248979C701CA83500BB83DE4E@SERVER.aperiogroup.local> <1207681260.11296.38.camel@localhost.localdomain> <4292CEA5F4927248979C701CA83500BB83DE60@SERVER.aperiogroup.local> Message-ID: <20080408194156.GD6560@redhat.com> On Tue, Apr 08, 2008 at 12:32:40PM -0700, Walter Coole wrote: > My version of virt-install doesn't understand --nogfx, but I tried: It is --nographics actually Check 'man virt-install' or 'virt-install --help' for more details Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From WCoole at aperiogroup.com Wed Apr 9 17:52:33 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Wed, 9 Apr 2008 10:52:33 -0700 Subject: [Fedora-xen] RE: Newby Help In-Reply-To: <20080409160014.ABE19619A32@hormel.redhat.com> References: <20080409160014.ABE19619A32@hormel.redhat.com> Message-ID: <4292CEA5F4927248979C701CA83500BB83DEDE@SERVER.aperiogroup.local> With a lot of help and trying things without much of a clue, I think I've gotten virt-install to create a machine image, but that machine boots into an Anaconda session that hangs. The error says: Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated. Cannot open/read repomd.xml file for repository: anaconda-base-200610172015.x86_64 Can anyone tell me where this repomd.xml file is supposed to be? Or a way to validate my install tree? Or a better way to build an install tree than turning wget loose on download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64 ? I've gone through a couple of sets of instructions that have failed for me in a variety of ways that I don't seem to be able to cope with. Since someone seems to be able to use Xen, I'm apparently doing something clueless that isn't covered by those instructions. If someone can provide some guidance, I'd be happy to start over from scratch. Extremely grateful for any hints, Walter From swethu_bandaru at yahoo.com Thu Apr 10 10:59:42 2008 From: swethu_bandaru at yahoo.com (swethu bandaru) Date: Thu, 10 Apr 2008 03:59:42 -0700 (PDT) Subject: [Fedora-xen] xen installation Message-ID: <901500.14368.qm@web36201.mail.mud.yahoo.com> I am new to xen and I don,t know anything about it Plz, any one can tell me all the steps in how to install guest O.S through Xen plzzzzzzzzzzzzzzzzzzzzz Thank you __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From turbo at bayour.com Thu Apr 10 12:55:46 2008 From: turbo at bayour.com (Turbo Fredriksson) Date: Thu, 10 Apr 2008 14:55:46 +0200 Subject: [Fedora-xen] Weird routing problem Message-ID: <87lk3lj2ct.fsf@pumba.bayour.com> I have two physical hosts (Correo and Alexander), running two XEN instances on one of them (Ferrari and Amarillo on Correo) and one on the other (Graham on Alexander)... Picture at http://bayour.com/misc/VoIP.jpg. On the firewall/gateway (192.168.1.1) I route 192.168.3.0/24 to Correo (192.168.1.7) and 192.168.4.0/24 to Alexander (192.168.1.6). This so that I can access the XEN hosts from the internal network. Very basic... And all my VoIP phones is on it's (about to be on a) separate network with the firewall/gateway as default gateway. On Alexander: ============= * /etc/xen/graham.cfg kernel = '/boot/vmlinuz-2.6.18-5-xen-amd64' ramdisk = '/boot/initrd.img-2.6.18-5-xen-amd64' memory = '2500' root = '/dev/sda1 ro' disk = [ 'file:/home/xen/domains/graham/disk.img,sda1,w', 'file:/home/xen/domains/graham/swap.img,sda2,w' ] name = 'graham' vif = [ 'ip=192.168.4.11' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' * /etc/xen/xend-config.sxp (xend-http-server yes) (xend-unix-server yes) (xend-tcp-xmlrpc-server no) (xend-unix-xmlrpc-server yes) (xend-relocation-server yes) (xend-unix-path /var/lib/xend/xend-socket) (xend-port 8000) (xend-relocation-port 8002) (xend-address 'alexander') (xend-relocation-address 'alexander') (console-limit 1024) (network-script network-route) (vif-script vif-route) (dom0-min-mem 196) (dom0-cpus 2) (enable-dump yes) (vnc-listen '0.0.0.0') * ifconfig (trimmed - only 'lo' if removed) eth0 Link encap:Ethernet HWaddr 00:1C:23:C4:28:92 inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21c:23ff:fec4:2892/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0:0 Link encap:Ethernet HWaddr 00:1C:23:C4:28:92 inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.255 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 * route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.4.11 0.0.0.0 255.255.255.255 UH 0 0 0 vif5.0 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 * iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT 0 -- 192.168.4.11 0.0.0.0/0 PHYSDEV match --physdev-in vif5.0 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif5.0 udp spt:68 dpt:67 Chain OUTPUT (policy ACCEPT) target prot opt source destination * iptables -L -n -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination On Graham: ========== * ifconfig (trimmed - only 'lo' if removed) eth0 Link encap:Ethernet HWaddr 00:16:3E:00:AB:28 inet addr:192.168.4.11 Bcast:192.168.4.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 * route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 * iptables -L -n FATAL: Could not load /lib/modules/2.6.18-5-xen-amd64/modules.dep: No such file or directory iptables v1.3.6: can't initialize iptables table `filter': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. Correo with the XEN hosts Ferrari and Amarillo basically look identical (only different networks). As seen, I do NOT use NAT here. I wanted to use true routed network... And it seems to work. My primary Asterisk server (the one that do all the routing - the one on Alexander only deals with the PSTN trafik) runs on Graham and it can be accessed from the outside - with port forwarding on the firewall/gateway and it can also contact external Asterisk servers (I run one at home to deal with my private VoIP). The DNS runs on Correo, but it can not be reached (queried) from Graham! ----- s n i p ----- graham# ping -c 5 correo ping: unknown host correo graham# ping -c 5 192.168.1.7 PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data. 64 bytes from 192.168.1.7: icmp_seq=1 ttl=62 time=0.270 ms 64 bytes from 192.168.1.7: icmp_seq=2 ttl=62 time=0.260 ms 64 bytes from 192.168.1.7: icmp_seq=3 ttl=62 time=0.264 ms 64 bytes from 192.168.1.7: icmp_seq=4 ttl=62 time=0.273 ms 64 bytes from 192.168.1.7: icmp_seq=5 ttl=62 time=0.257 ms --- 192.168.1.7 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4000ms rtt min/avg/max/mdev = 0.257/0.264/0.273/0.021 ms graham# traceroute -n 192.168.1.7 traceroute to 192.168.1.7 (192.168.1.7), 30 hops max, 52 byte packets 1 192.168.1.6 0.285 ms 0.091 ms 0.090 ms 2 192.168.1.7 0.323 ms 0.262 ms 0.258 ms graham# telnet 192.168.1.7 53 Trying 192.168.1.7... Connected to 192.168.1.7. Escape character is '^]'. correo Connection closed by foreign host. graham# host graham 192.168.1.7 ;; reply from unexpected source: 192.168.1.1#53, expected 192.168.1.7#53 ;; reply from unexpected source: 192.168.1.1#53, expected 192.168.1.7#53 ;; connection timed out; no servers could be reached ----- s n i p ----- Also, scp or ssh FROM Graham to Correo don't work, but the other way around works fine... Looking at the answer that 'host' gave me, I now see that the connection goes via the firewall/gateway which is not directly obvious - Alexander (which is Graham's default GW) is on the same network as Correo... PS. I solved this specific DNS problem with a caching DNS server on Alexander, but scp/ssh (etc) naturally still don't work because of this weird problem... I just can't see it! Maybe a set of (many :) extra eyes can... Thanx! From markmc at redhat.com Thu Apr 10 13:15:45 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 10 Apr 2008 14:15:45 +0100 Subject: [Fedora-xen] Testing xen installs with a new kernel Message-ID: <1207833345.16779.4.camel@muff> Hey, Fedora 9 is frozen right now, so as we continue getting kernel-xen into shape, we need to be able to test installs with new kernel builds before requesting that the build gets tagged. Here's some instructions for anyone who needs to do this: 1) Checkout anaconda from git[1]: $> git-clone git://git.fedorahosted.org/anaconda.git 2) Pull down the latest installer images: $> d=$(date +%F) $> mkdir $d $> pushd $d $> wget http://download.fedora.redhat.com/pub/fedora/linux/development/${arch}/os/images/xen/vmlinuz $> wget http://download.fedora.redhat.com/pub/fedora/linux/development/${arch}/os/images/xen/initrd $> popd 3) Create the new images $> anaconda/scripts/upd-kernel $d $d-$kver ./kernel-xen-$kver.rpm $> cat > $d-$kver < virt-install ... -l ./$d-$kver ... -x "method=http://mymirror/foobar/${arch}/os/" Cheers, Mark. [1] - You'll also need these patches which hopefully will be applied soon: http://www.redhat.com/archives/anaconda-devel-list/2008-April/thread.html#00037 From alroger.filho at sdev.com Thu Apr 10 19:26:59 2008 From: alroger.filho at sdev.com (Alroger L. Gomes F.) Date: Thu, 10 Apr 2008 16:26:59 -0300 Subject: [Fedora-xen] Fedora9 and HP ML350 Message-ID: <47FE6A03.4050005@sdev.com> Hello everyone. I've just installed Fedora9, on a HP Proliant Server ML350 with SmartArray E200i (cciss driver), hoping to use the latest Xen features. When I boot into the kernel-xen, it gets up to the following line and reboots itself in an endless loop. XEN is relinquishing VGA console It does not generate any output on /var/log/messages nor /var/log/xen/*. Any ideas? -- Alroger Luiz Gomes Filho SDEV - Smart Developments http://www.sdev.com http://cafe-ti.blog.br So little time, so many systems . . . From itamar at ispbrasil.com.br Thu Apr 10 19:29:06 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Thu, 10 Apr 2008 16:29:06 -0300 Subject: [Fedora-xen] Fedora9 and HP ML350 In-Reply-To: <47FE6A03.4050005@sdev.com> References: <47FE6A03.4050005@sdev.com> Message-ID: <47FE6A82.1040207@ispbrasil.com.br> adiciona a linha noreboot na frente da linha do kernel e envia a mensagem de erro pra gente analisar. Alroger L. Gomes F. wrote: > Hello everyone. > I've just installed Fedora9, on a HP Proliant Server ML350 with > SmartArray E200i (cciss driver), hoping to use the latest Xen features. > When I boot into the kernel-xen, it gets up to the following line and > reboots itself in an endless loop. > XEN is relinquishing VGA console > > It does not generate any output on /var/log/messages nor /var/log/xen/*. > > Any ideas? > From lavalamp at spiritual-machines.org Thu Apr 10 19:36:12 2008 From: lavalamp at spiritual-machines.org (Brian A. Seklecki) Date: Thu, 10 Apr 2008 15:36:12 -0400 Subject: [Fedora-xen] Fedora9 and HP ML350 In-Reply-To: <47FE6A03.4050005@sdev.com> References: <47FE6A03.4050005@sdev.com> Message-ID: <1207856172.12507.108.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> On Thu, 2008-04-10 at 16:26 -0300, Alroger L. Gomes F. wrote: > When I boot into the kernel-xen, it gets up to the following line and We need to see your grub.conf / /grug/boot.lst ~BAS From berrange at redhat.com Thu Apr 10 19:39:21 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 10 Apr 2008 20:39:21 +0100 Subject: [Fedora-xen] Fedora9 and HP ML350 In-Reply-To: <47FE6A03.4050005@sdev.com> References: <47FE6A03.4050005@sdev.com> Message-ID: <20080410193921.GK22656@redhat.com> On Thu, Apr 10, 2008 at 04:26:59PM -0300, Alroger L. Gomes F. wrote: > Hello everyone. > I've just installed Fedora9, on a HP Proliant Server ML350 with > SmartArray E200i (cciss driver), hoping to use the latest Xen features. > When I boot into the kernel-xen, it gets up to the following line and > reboots itself in an endless loop. > XEN is relinquishing VGA console Xen Dom0 host is *NOT* supported in Fedora 9. Only DomU guest is supported. If you need dom0 host, stay on Fedora 8. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From alroger.filho at sdev.com Thu Apr 10 20:10:37 2008 From: alroger.filho at sdev.com (Alroger L. Gomes F.) Date: Thu, 10 Apr 2008 17:10:37 -0300 Subject: [Fedora-xen] Re: Fedora9 and HP ML350 In-Reply-To: <47FE6A03.4050005@sdev.com> References: <47FE6A03.4050005@sdev.com> Message-ID: <47FE743D.9010405@sdev.com> Dan, what do you mean? You mean in this beta stage, or what? What about all the talks of bringing kernel-xen uptodate with the latest kernels and P2V tools? > Xen Dom0 host is *NOT* supported in Fedora 9. Only DomU guest is > supported. If you need dom0 host, stay on Fedora 8. > > Dan. Anyway, here is my GRUB... And noreboot, simply does that... stays at that line, but there is no way to check for errors. Here is my grub: #boot=/dev/cciss/c0d0 default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25-0.18.rc8.fc9.x86_64.xen) root (hd0,0) kernel /xen.gz-2.6.25-0.18.rc8.fc9.x86_64.xen noreboot module /vmlinuz-2.6.25-0.18.rc8.fc9.x86_64.xen ro root=UUID=73930cfa-e3d2-4b71-979b-dfa1634c195f rhgb quiet selinux=0 module /initrd-2.6.25-0.18.rc8.fc9.x86_64.xen.img Alroger L. Gomes F. wrote: > Hello everyone. > I've just installed Fedora9, on a HP Proliant Server ML350 with > SmartArray E200i (cciss driver), hoping to use the latest Xen features. > When I boot into the kernel-xen, it gets up to the following line and > reboots itself in an endless loop. > XEN is relinquishing VGA console > > It does not generate any output on /var/log/messages nor /var/log/xen/*. > > Any ideas? -- Alroger Luiz Gomes Filho SDEV - Smart Developments http://www.sdev.com http://cafe-ti.blog.br So little time, so many systems . . . From itamar at ispbrasil.com.br Thu Apr 10 20:19:56 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Thu, 10 Apr 2008 17:19:56 -0300 Subject: [Fedora-xen] Re: Fedora9 and HP ML350 In-Reply-To: <47FE743D.9010405@sdev.com> References: <47FE6A03.4050005@sdev.com> <47FE743D.9010405@sdev.com> Message-ID: <47FE766C.8080502@ispbrasil.com.br> dom0 ? o kernel que d? o boot. os kernels-xen que vem no fedora 9 simplesmente nao servem para dar boot na maquina. ele disse que se quiser dar boot na maquina com o kernel-xen pra voce utilizar o fedora 8 Alroger L. Gomes F. wrote: > Dan, what do you mean? You mean in this beta stage, or what? > What about all the talks of bringing kernel-xen uptodate with the > latest kernels and P2V tools? > >> Xen Dom0 host is *NOT* supported in Fedora 9. Only DomU guest is >> supported. If you need dom0 host, stay on Fedora 8. >> >> Dan. > Anyway, here is my GRUB... > And noreboot, simply does that... stays at that line, but there is no > way to check for errors. > > Here is my grub: > #boot=/dev/cciss/c0d0 > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora (2.6.25-0.18.rc8.fc9.x86_64.xen) > root (hd0,0) > kernel /xen.gz-2.6.25-0.18.rc8.fc9.x86_64.xen noreboot > module /vmlinuz-2.6.25-0.18.rc8.fc9.x86_64.xen ro > root=UUID=73930cfa-e3d2-4b71-979b-dfa1634c195f rhgb quiet selinux=0 > module /initrd-2.6.25-0.18.rc8.fc9.x86_64.xen.img > > > Alroger L. Gomes F. wrote: >> Hello everyone. >> I've just installed Fedora9, on a HP Proliant Server ML350 with >> SmartArray E200i (cciss driver), hoping to use the latest Xen features. >> When I boot into the kernel-xen, it gets up to the following line and >> reboots itself in an endless loop. >> XEN is relinquishing VGA console >> >> It does not generate any output on /var/log/messages nor /var/log/xen/*. >> >> Any ideas? From armbru at redhat.com Fri Apr 11 10:00:22 2008 From: armbru at redhat.com (Markus Armbruster) Date: Fri, 11 Apr 2008 12:00:22 +0200 Subject: [Fedora-xen] Re: Fedora9 and HP ML350 In-Reply-To: <47FE743D.9010405@sdev.com> (Alroger L. Gomes F.'s message of "Thu\, 10 Apr 2008 17\:10\:37 -0300") References: <47FE6A03.4050005@sdev.com> <47FE743D.9010405@sdev.com> Message-ID: <87skxsr9s9.fsf@pike.pond.sub.org> [Quoting fixed] "Alroger L. Gomes F." writes: > "Daniel P. Berrange" writes: >> Xen Dom0 host is *NOT* supported in Fedora 9. Only DomU guest is >> supported. If you need dom0 host, stay on Fedora 8. >> >> Dan. > > Dan, what do you mean? You mean in this beta stage, or what? > What about all the talks of bringing kernel-xen uptodate with the > latest kernels and P2V tools? [...] F9 will not support Xen Dom0 when released. Whether we will be able to provide that support in a later update I can't say. Old kernels are unsupportable in F9, and splitting resources between more forward porting of the Xen kernel patches and the pvops kernel makes no sense; we'd get neither done. So we opted for getting pvops done, because when that's done it's *done*. Unfortunately, we couldn't get there in time for F9. From erenoglu at gmail.com Mon Apr 14 01:10:21 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Mon, 14 Apr 2008 03:10:21 +0200 Subject: [Fedora-xen] no xenfb module in 2.6.21.7-3.fc8xen ? Message-ID: Hi, I'm trying to start Xorg on a PV Fedora8 guest running 2.6.21.7 fedora stock xen kernel, however, it seems that there's no xenfb.ko driver included in the .rpm package. The only included drivers I see in /lib/modules are: emre at xenroot:/lib/modules/2.6.21.7-3.fc8xen/kernel/drivers/xen$ ls blkback blkfront blktap netback netfront pciback however, if I look at the source rpm: emre at xenroot:/d/xen/fedora8/xen-3.1.3/linux-2.6-xen-sparse/drivers/xen$ ls balloon blktap core gntdev netback pcifront util.c blkback char evtchn Kconfig netfront privcmd xenbus blkfront console fbfront Makefile pciback tpmback xenoprof I can clearly see the fbfront directory, with "xenfb.c xenkbd.c" files inside. Is there a specific reason why these drivers are excluded from the default build? Thanks a lot for your comments. Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Mon Apr 14 07:06:51 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 14 Apr 2008 08:06:51 +0100 Subject: [Fedora-xen] no xenfb module in 2.6.21.7-3.fc8xen ? In-Reply-To: References: Message-ID: <1208156811.3384.1.camel@muff> On Mon, 2008-04-14 at 03:10 +0200, Emre ERENOGLU wrote: > Hi, > > I'm trying to start Xorg on a PV Fedora8 guest running 2.6.21.7 fedora > stock xen kernel, however, it seems that there's no xenfb.ko driver > included in the .rpm package. It's built-in to the kernel since it's used early on in boot to display to the console: CONFIG_XEN_FRAMEBUFFER=y Cheers, Mark. From erenoglu at gmail.com Mon Apr 14 09:52:33 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Mon, 14 Apr 2008 11:52:33 +0200 Subject: [Fedora-xen] no xenfb module in 2.6.21.7-3.fc8xen ? In-Reply-To: <1208156811.3384.1.camel@muff> References: <1208156811.3384.1.camel@muff> Message-ID: Hi Mark, thanks for the answer. If it's built into the kernel, why can't I modprobe it, or see it in the list of loaded modules? Maybe I'm missing something here??? Here's the output from my DomU running with this kernel: voyager ~ # lsmod Module Size Used by microcode 7428 0 nls_utf8 6144 1 cifs 212980 1 joydev 13376 0 ext3 125704 3 jbd 59816 1 ext3 mbcache 12420 1 ext3 fuse 45972 1 xennet 30216 0 xenblk 20592 4 pciback 30348 0 blkbk 23584 0 [permanent] netloop 10752 0 netbk 78912 0 [permanent] xenblktap 118916 0 [permanent] dm_snapshot 20644 0 dm_mirror 24724 0 dm_mod 57548 2 dm_snapshot,dm_mirror raid456 125712 0 xor 18312 1 raid456 raid10 27136 0 linear 9984 0 multipath 12672 0 ahci 23044 0 ata_generic 11780 0 pata_jmicron 10496 0 libata 112624 3 ahci,ata_generic,pata_jmicron sd_mod 29056 0 sg 37276 0 sr_mod 20132 0 scsi_mod 139532 4 libata,sd_mod,sg,sr_mod cdrom 37152 1 sr_mod raid1 26496 0 raid0 12032 0 voyager ~ # modprobe xenfb FATAL: Module xenfb not found. voyager ~ # Emre On Mon, Apr 14, 2008 at 9:06 AM, Mark McLoughlin wrote: > On Mon, 2008-04-14 at 03:10 +0200, Emre ERENOGLU wrote: > > Hi, > > > > I'm trying to start Xorg on a PV Fedora8 guest running 2.6.21.7 fedora > > stock xen kernel, however, it seems that there's no xenfb.ko driver > > included in the .rpm package. > > It's built-in to the kernel since it's used early on in boot to display > to the console: > > CONFIG_XEN_FRAMEBUFFER=y > > Cheers, > Mark. > > -- Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Mon Apr 14 10:20:31 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 14 Apr 2008 11:20:31 +0100 Subject: [Fedora-xen] no xenfb module in 2.6.21.7-3.fc8xen ? In-Reply-To: References: <1208156811.3384.1.camel@muff> Message-ID: <1208168431.24894.0.camel@muff> On Mon, 2008-04-14 at 11:52 +0200, Emre ERENOGLU wrote: > thanks for the answer. If it's built into the kernel, why can't I > modprobe it, or see it in the list of loaded modules? If it's built-in, it's not visible as a module ... Cheers, Mark. From erenoglu at gmail.com Mon Apr 14 10:26:54 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Mon, 14 Apr 2008 12:26:54 +0200 Subject: [Fedora-xen] no xenfb module in 2.6.21.7-3.fc8xen ? In-Reply-To: <1208168431.24894.0.camel@muff> References: <1208156811.3384.1.camel@muff> <1208168431.24894.0.camel@muff> Message-ID: Hi Mark, Thanks again very much for the explanation. OK, one last question and I'll stop bugging, would you have an idea why X refuse to launch? on this frame buffer? I'm pasting the Xorg.0.log, it seems that the driver (FBDEV) cannot change resolution or something like this. I have the login promt in the this VNC (or SDL) window, so I guess the xenfb driver is working properly. Is it possible that X can't use the console that I'm currently logged on? (ttyX ?) (II) FBDEV: driver for framebuffer: fbdev (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 1.3.0, module version = 0.0.2 ABI class: X.Org Video Driver, version 1.2 (II) FBDEV(0): using default device (II) Running in FRAMEBUFFER Mode (**) FBDEV(0): Depth 16, (--) framebuffer bpp 16 (==) FBDEV(0): RGB weight 565 (==) FBDEV(0): Default visual is TrueColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: xen (video memory: 1875kB) (II) FBDEV(0): checking modes against framebuffer device... (II) FBDEV(0): mode "800x600" test failed (II) FBDEV(0): mode "640x480" test failed (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 800x600 (pitch 800) (**) FBDEV(0): Built-in mode "current": 28000.0 MHz, 35000.0 kHz, 58333.3 Hz (II) FBDEV(0): Modeline "current" 28000.00 800 800 800 800 600 600 600 600 -hsync -vsync -csync (==) FBDEV(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (**) FBDEV(0): using shadow framebuffer (II) Loading sub module "shadow" (II) LoadModule: "shadow" (II) Loading /usr/lib/xorg/modules//libshadow.so (II) Module shadow: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.3 (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 Emre On Mon, Apr 14, 2008 at 12:20 PM, Mark McLoughlin wrote: > On Mon, 2008-04-14 at 11:52 +0200, Emre ERENOGLU wrote: > > > thanks for the answer. If it's built into the kernel, why can't I > > modprobe it, or see it in the list of loaded modules? > > If it's built-in, it's not visible as a module ... > > Cheers, > Mark. > > -- Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erenoglu at gmail.com Tue Apr 15 15:34:05 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Tue, 15 Apr 2008 17:34:05 +0200 Subject: [Fedora-xen] Why does this compilation fail? Message-ID: Hi, Does anybody have an idea why the following code fails in the 2.6.21.7Fedora 8 XEN kernel but not in 2.6.18.8-xen ? emre at xenroot:/d/nvidia/nvidia-source-100.14.19-x86_64-xen$ cc -D__KERNEL__ '-DKBUILD_BASENAME="#conftest.emre"' '-DKBUILD_MODNAME="#conftest.emre"' -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.1.3/include -I/lib/modules/2.6.21.7-3.fc8xen/build/include/asm/mach-xen -I/lib/modules/2.6.21.7-3.fc8xen/build/include -I/lib/modules/2.6.21.7-3.fc8xen/build/include/asm/mach-default -o conftest.emre conftest.emre.c In file included from /lib/modules/2.6.21.7-3.fc8xen/build/include/asm/system.h:10, from /lib/modules/2.6.21.7-3.fc8xen/build/include/asm/mach-xen/asm/processor.h:18, from /lib/modules/2.6.21.7-3.fc8xen/build/include/asm/thread_info.h:16, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/thread_info.h:21, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/preempt.h:9, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/spinlock.h:49, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/capability.h:45, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/sched.h:46, from /lib/modules/2.6.21.7-3.fc8xen/build/include/linux/utsname.h:35, from conftest.emre.c:3: /lib/modules/2.6.21.7-3.fc8xen/build/include/asm/mach-xen/asm/hypervisor.h: In function 'HYPERVISOR_poll': /lib/modules/2.6.21.7-3.fc8xen/build/include/asm/mach-xen/asm/hypervisor.h:198: error: request for member 'p' in something not a structure or union emre at xenroot:/d/nvidia/nvidia-source-100.14.19-x86_64-xen$ The code is: emre at xenroot:/d/nvidia/nvidia-source-100.14.19-x86_64-xen$ cat conftest.emre.c #include #include #include int main() { if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)) { return 0; } else { return 1; } } emre at xenroot:/d/nvidia/nvidia-source-100.14.19-x86_64-xen$ Due to this, the whole nvidia driver compilation is failing even though it works on 2.6.18.8-xen dom0 kernel. Any ideas on what's missing in the 2.6.21.7 sources? Thanks a lot, Emre Erenoglu -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Apr 15 15:37:27 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 15 Apr 2008 16:37:27 +0100 Subject: [Fedora-xen] Why does this compilation fail? In-Reply-To: References: Message-ID: <20080415153727.GG5713@redhat.com> On Tue, Apr 15, 2008 at 05:34:05PM +0200, Emre ERENOGLU wrote: > Hi, > > Does anybody have an idea why the following code fails in the > 2.6.21.7Fedora 8 XEN kernel but not in 2.6.18.8-xen ? Because the kernel changes & nvidia is an out of tree module which doesn't track the changes to the upstream kernels. Go speak to NVIDIA and tell them to support an open source driver for their graphics cards. > Due to this, the whole nvidia driver compilation is failing even though it > works on 2.6.18.8-xen dom0 kernel. > > Any ideas on what's missing in the 2.6.21.7 sources? Nothing is missing. The NVidia module is broken. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From erenoglu at gmail.com Tue Apr 15 15:49:06 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Tue, 15 Apr 2008 17:49:06 +0200 Subject: [Fedora-xen] Why does this compilation fail? In-Reply-To: <20080415153727.GG5713@redhat.com> References: <20080415153727.GG5713@redhat.com> Message-ID: Hi Daniel, Thanks for the quick comment. I understand, then why do you think it is compiling fine under 2.6.18.8-xen and also seemingly working fine since a lot of months on my Xen 3.2 system? (game, video playing, compiz, etc.) Emre On Tue, Apr 15, 2008 at 5:37 PM, Daniel P. Berrange wrote: > On Tue, Apr 15, 2008 at 05:34:05PM +0200, Emre ERENOGLU wrote: > > Hi, > > > > Does anybody have an idea why the following code fails in the > > 2.6.21.7Fedora 8 XEN kernel but not in 2.6.18.8-xen ? > > Because the kernel changes & nvidia is an out of tree module which doesn't > track the changes to the upstream kernels. Go speak to NVIDIA and tell > them > to support an open source driver for their graphics cards. > > > Due to this, the whole nvidia driver compilation is failing even though > it > > works on 2.6.18.8-xen dom0 kernel. > > > > Any ideas on what's missing in the 2.6.21.7 sources? > > Nothing is missing. The NVidia module is broken. > > Dan. > -- > |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/:| > |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org:| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| > |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > :| > -- Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsolan at knouse.com Tue Apr 15 19:19:12 2008 From: jsolan at knouse.com (Jason Solan) Date: Tue, 15 Apr 2008 15:19:12 -0400 Subject: [Fedora-xen] iwl3945 driver Message-ID: <1208287152.5433.10.camel@jsolan.knouse.com> Hello, I am wondering if anyone has the iwl3945 driver working on xen? I'm using Fedora 8 and under the standard kernel the driver works great. When i switch the xen kernel, fedora can no longer find the device. If I do a kudzu -pc NETWORK the device shows up (as eth1 instead of wlan0) but it does not have a mac address. I've tried just manually adding the entry and its mac address to /etc/sysconfig/hwconf but that didn't seem to do anything for me. Any help is appreciated. --Jason IMPORTANT: This transmission is sent on behalf of Knouse Foods for business purposes. It is for the intended recipient only. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this Email message, and please dispose of and delete this transmission. Thank you. From jeevanullas at gmail.com Wed Apr 16 00:37:34 2008 From: jeevanullas at gmail.com (Deependra Singh Shekhawat) Date: Wed, 16 Apr 2008 06:07:34 +0530 Subject: [Fedora-xen] iwl3945 driver In-Reply-To: <1208287152.5433.10.camel@jsolan.knouse.com> References: <1208287152.5433.10.camel@jsolan.knouse.com> Message-ID: <57127b5f0804151737i3496a3aesc38253b365371de2@mail.gmail.com> Hi, You should use ipw3945 if you want to have a working wireless device in fedora8 kernel. Thanks Deependra Singh Shekhawat On Wed, Apr 16, 2008 at 12:49 AM, Jason Solan wrote: > Hello, > > I am wondering if anyone has the iwl3945 driver working on xen? I'm > using Fedora 8 and under the standard kernel the driver works great. > When i switch the xen kernel, fedora can no longer find the device. > > If I do a > > kudzu -pc NETWORK > > the device shows up (as eth1 instead of wlan0) but it does not have a > mac address. > > I've tried just manually adding the entry and its mac address > to /etc/sysconfig/hwconf but that didn't seem to do anything for me. > > Any help is appreciated. > > --Jason > > > > > > > IMPORTANT: > This transmission is sent on behalf of Knouse Foods for business > purposes. It is for the intended recipient only. If you are not the intended > recipient or a person responsible for delivering this transmission to > the intended recipient, you may not disclose, copy or distribute this > transmission or take any action in reliance on it. If you received this > transmission in error, please notify us immediately by replying to this > Email message, and please dispose of and delete this transmission. > Thank you. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Enjoy Life ! From alroger at cafe-ti.blog.br Wed Apr 16 02:33:49 2008 From: alroger at cafe-ti.blog.br (Alroger L. Gomes F.) Date: Tue, 15 Apr 2008 23:33:49 -0300 Subject: [Fedora-xen] F9 Feature List correction Message-ID: <4805658D.3070107@cafe-ti.blog.br> In the Feature List Accepted Features (http://fedoraproject.org/wiki/Releases/9/FeatureList), Xen paravirt_ops should say 50% or less, instead of 100%, since Dom0 XEN is NOT working in Fedora9, since it's description includes Dom0: "Replacing the current forward-ported XenSource code on kernel-xen by a paravirt_ops based implementation, including dom0 suppor" - 2008-04-07 Acording to http://fedoraproject.org/wiki/Features/XenPvopsDom0, Dom0 is at 30% still. -- I see babies crying... I watch them grow. They will learn much more... ...than I'll ever know! --- http://cafe-ti.blog.br Informacao de Pessoas para Pessoas. From berrange at redhat.com Wed Apr 16 16:37:04 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 16 Apr 2008 17:37:04 +0100 Subject: [Fedora-xen] F9 Feature List correction In-Reply-To: <4805658D.3070107@cafe-ti.blog.br> References: <4805658D.3070107@cafe-ti.blog.br> Message-ID: <20080416163704.GF1444@redhat.com> On Tue, Apr 15, 2008 at 11:33:49PM -0300, Alroger L. Gomes F. wrote: > In the Feature List Accepted Features > (http://fedoraproject.org/wiki/Releases/9/FeatureList), Xen paravirt_ops > should say 50% or less, instead of 100%, since Dom0 XEN is NOT working > in Fedora9, since it's description includes Dom0: The feature was split into 2 - the original F9 feature now merely refers to DomU pvops for 32 & 64 bit. Dom0 pvops was split off to F10. So the original feature is correct in saying 100% complete, since DomU is finished, bar bug fixing. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From dlbewley at lib.ucdavis.edu Wed Apr 16 22:34:08 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 16 Apr 2008 15:34:08 -0700 Subject: [Fedora-xen] Weird routing problem In-Reply-To: <87lk3lj2ct.fsf@pumba.bayour.com> References: <87lk3lj2ct.fsf@pumba.bayour.com> Message-ID: <1208385248.18783.26.camel@tofu.lib.ucdavis.edu> On Thu, 2008-04-10 at 14:55 +0200, Turbo Fredriksson wrote: > I have two physical hosts (Correo and Alexander), running two XEN > instances on one of them (Ferrari and Amarillo on Correo) and one > on the other (Graham on Alexander)... > > Picture at http://bayour.com/misc/VoIP.jpg. > > > On the firewall/gateway (192.168.1.1) I route 192.168.3.0/24 to Correo > (192.168.1.7) and 192.168.4.0/24 to Alexander (192.168.1.6). This so > that I can access the XEN hosts from the internal network. Very basic... > > And all my VoIP phones is on it's (about to be on a) separate network > with the firewall/gateway as default gateway. > > > On Alexander: > ============= > * /etc/xen/graham.cfg > kernel = '/boot/vmlinuz-2.6.18-5-xen-amd64' > ramdisk = '/boot/initrd.img-2.6.18-5-xen-amd64' > memory = '2500' > root = '/dev/sda1 ro' > disk = [ 'file:/home/xen/domains/graham/disk.img,sda1,w', 'file:/home/xen/domains/graham/swap.img,sda2,w' ] > name = 'graham' > vif = [ 'ip=192.168.4.11' ] > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'restart' > > * /etc/xen/xend-config.sxp > (xend-http-server yes) > (xend-unix-server yes) > (xend-tcp-xmlrpc-server no) > (xend-unix-xmlrpc-server yes) > (xend-relocation-server yes) > (xend-unix-path /var/lib/xend/xend-socket) > (xend-port 8000) > (xend-relocation-port 8002) > (xend-address 'alexander') > (xend-relocation-address 'alexander') > (console-limit 1024) > (network-script network-route) > (vif-script vif-route) > (dom0-min-mem 196) > (dom0-cpus 2) > (enable-dump yes) > (vnc-listen '0.0.0.0') > > * ifconfig (trimmed - only 'lo' if removed) > eth0 Link encap:Ethernet HWaddr 00:1C:23:C4:28:92 > inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::21c:23ff:fec4:2892/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > eth0:0 Link encap:Ethernet HWaddr 00:1C:23:C4:28:92 > inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.255 > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > * route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.4.11 0.0.0.0 255.255.255.255 UH 0 0 0 vif5.0 > 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 > > * iptables -L -n > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT 0 -- 192.168.4.11 0.0.0.0/0 PHYSDEV match --physdev-in vif5.0 > ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-in vif5.0 udp spt:68 dpt:67 > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > * iptables -L -n -t nat > Chain PREROUTING (policy ACCEPT) > target prot opt source destination > > Chain POSTROUTING (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > On Graham: > ========== > * ifconfig (trimmed - only 'lo' if removed) > eth0 Link encap:Ethernet HWaddr 00:16:3E:00:AB:28 > inet addr:192.168.4.11 Bcast:192.168.4.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > * route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 > > * iptables -L -n > FATAL: Could not load /lib/modules/2.6.18-5-xen-amd64/modules.dep: No such file or directory > iptables v1.3.6: can't initialize iptables table `filter': iptables who? (do you need to insmod?) > Perhaps iptables or your kernel needs to be upgraded. > > Correo with the XEN hosts Ferrari and Amarillo basically look identical (only different > networks). > > As seen, I do NOT use NAT here. I wanted to use true routed network... And it seems to work. > My primary Asterisk server (the one that do all the routing - the one on Alexander only deals > with the PSTN trafik) runs on Graham and it can be accessed from the outside - with port > forwarding on the firewall/gateway and it can also contact external Asterisk servers (I run > one at home to deal with my private VoIP). > > > The DNS runs on Correo, but it can not be reached (queried) from Graham! > > ----- s n i p ----- > graham# ping -c 5 correo > ping: unknown host correo > > graham# ping -c 5 192.168.1.7 > PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data. > 64 bytes from 192.168.1.7: icmp_seq=1 ttl=62 time=0.270 ms > 64 bytes from 192.168.1.7: icmp_seq=2 ttl=62 time=0.260 ms > 64 bytes from 192.168.1.7: icmp_seq=3 ttl=62 time=0.264 ms > 64 bytes from 192.168.1.7: icmp_seq=4 ttl=62 time=0.273 ms > 64 bytes from 192.168.1.7: icmp_seq=5 ttl=62 time=0.257 ms > > --- 192.168.1.7 ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 4000ms > rtt min/avg/max/mdev = 0.257/0.264/0.273/0.021 ms > > graham# traceroute -n 192.168.1.7 > traceroute to 192.168.1.7 (192.168.1.7), 30 hops max, 52 byte packets > 1 192.168.1.6 0.285 ms 0.091 ms 0.090 ms > 2 192.168.1.7 0.323 ms 0.262 ms 0.258 ms > > graham# telnet 192.168.1.7 53 > Trying 192.168.1.7... > Connected to 192.168.1.7. > Escape character is '^]'. > correo > Connection closed by foreign host. > > graham# host graham 192.168.1.7 > ;; reply from unexpected source: 192.168.1.1#53, expected 192.168.1.7#53 > ;; reply from unexpected source: 192.168.1.1#53, expected 192.168.1.7#53 > ;; connection timed out; no servers could be reached > ----- s n i p ----- > > Also, scp or ssh FROM Graham to Correo don't work, but the other way > around works fine... > > > Looking at the answer that 'host' gave me, I now see that the connection > goes via the firewall/gateway which is not directly obvious - Alexander > (which is Graham's default GW) is on the same network as Correo... > > > PS. I solved this specific DNS problem with a caching DNS server on > Alexander, but scp/ssh (etc) naturally still don't work because > of this weird problem... I just can't see it! Maybe a set of > (many :) extra eyes can... Thanx! Did you figure it out yet? I can not quite tell what you're doing. Who is that blue router in your diagram? Maybe you are using a router icon to indicate a switch? At any rate if I had to guess it sounds like you are expecting to speak from eth0:0 IP when you are actually speaking from eth0 IP. This you could problably confirm with a tcpdump on the target machine while you probe from the other. If so, you could fix that with policy routing AKA source routing. i.e. `ip rule help`. Look at your ARP tables too just in case. From turbo at bayour.com Thu Apr 17 05:16:00 2008 From: turbo at bayour.com (Turbo Fredriksson) Date: Thu, 17 Apr 2008 07:16:00 +0200 Subject: [Fedora-xen] Weird routing problem References: <87lk3lj2ct.fsf@pumba.bayour.com> <1208385248.18783.26.camel@tofu.lib.ucdavis.edu> Message-ID: <87y77dm57z.fsf@pumba.bayour.com> Quoting Dale Bewley : > Did you figure it out yet? No I didn't. > I can not quite tell what you're doing. Who is that blue router in your > diagram? Maybe you are using a router icon to indicate a switch? I am, sorry. Didn't find any switch icons in dia. > At any rate if I had to guess it sounds like you are expecting to speak > from eth0:0 IP when you are actually speaking from eth0 IP. This you > could problably confirm with a tcpdump on the target machine while you > probe from the other. If so, you could fix that with policy routing AKA > source routing. i.e. `ip rule help`. Look at your ARP tables too just in > case. I'll have a look. Thanx for the idea... From rjones at redhat.com Thu Apr 17 14:11:54 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 17 Apr 2008 15:11:54 +0100 Subject: [Fedora-xen] ANNOUNCE: virt-df ('df' for guests) now supports LVM Message-ID: <20080417141154.GA18657@amd.home.annexia.org> I'm happy to say that virt-df, the command-line 'df'-like tool for looking at disk usage of guests, now supports LVM, making it usable for the majority of situations where your guests are running Linux distributions. You can now run 'virt-df' on the host and display the disk space used/available on all filesystems of all your guests. There is no need to run anything inside the guest. Here is an example with two running domains: # virt-df -c qemu:///system -h Filesystem Size Used Available Type rhel51x32kvm:hda1 96.8 MiB 14.6 MiB 82.2 MiB Linux ext2/3 rhel51x32kvm:VolGroup00/LogVol00 6.4 GiB 3.6 GiB 2.8 GiB Linux ext2/3 rhel51x32kvm:VolGroup00/LogVol01 992.0 MiB Linux swap rhel51x64kvm:hda1 96.8 MiB 22.1 MiB 74.7 MiB Linux ext2/3 rhel51x64kvm:VolGroup00/LogVol00 6.4 GiB 3.2 GiB 3.2 GiB Linux ext2/3 rhel51x64kvm:VolGroup00/LogVol01 992.0 MiB Linux swap Home page: http://et.redhat.com/~rjones/virt-df/ Source and binaries from: http://et.redhat.com/~rjones/virt-df/files/ Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v From davidl at matissenetworks.com Fri Apr 18 00:11:25 2008 From: davidl at matissenetworks.com (David Levinger) Date: Thu, 17 Apr 2008 17:11:25 -0700 (PDT) Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? Message-ID: <00c101c8a0e8$b5f94c10$a564a8c0@nbdavidl> Hey guys and gals, As the subject suggests, is it possible to block-attach a newly placed CD/DVD/HD/Img file to an XP guest? I've done the "normal" block-attach command and it says it has "attached" but nothing shows in the XP guest. d -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Fri Apr 18 07:42:02 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 18 Apr 2008 08:42:02 +0100 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] Message-ID: <1208504522.3464.4.camel@muff> Hey, There doesn't appear to be any install trees yet for the F9 Preview release, but please do try and run F9 rawhide in your Xen DomU (both i686 and x86_64) and help us flush out any remaining issues in the lead up to the final release. The current blocker list looks like: https://bugzilla.redhat.com/showdependencytree.cgi?id=434756&hide_resolved=1 Cheers, Mark. -------------- next part -------------- An embedded message was scrubbed... From: Jesse Keating Subject: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff! Date: Thu, 17 Apr 2008 17:31:48 -0400 Size: 6464 URL: From Dustin.Henning at prd-inc.com Fri Apr 18 12:25:44 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 18 Apr 2008 08:25:44 -0400 Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? In-Reply-To: <00c101c8a0e8$b5f94c10$a564a8c0@nbdavidl> References: <00c101c8a0e8$b5f94c10$a564a8c0@nbdavidl> Message-ID: <002101c8a14f$52cbb7b0$f8632710$@Henning@prd-inc.com> David, I don't know how much this will help you, as I don't know much about your setup. I am running XP HVM guests on F7 (Moonshine) using the old fashioned text xen method (/etc/xen From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Levinger Sent: Thursday, April 17, 2008 20:11 To: fedora-xen at redhat.com Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? Hey guys and gals, As the subject suggests, is it possible to block-attach a newly placed CD/DVD/HD/Img file to an XP guest? I've done the "normal" block-attach command and it says it has "attached" but nothing shows in the XP guest. d -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dustin.Henning at prd-inc.com Fri Apr 18 12:34:52 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 18 Apr 2008 08:34:52 -0400 Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? References: <00c101c8a0e8$b5f94c10$a564a8c0@nbdavidl> Message-ID: <002c01c8a150$99ad34a0$cd079de0$@Henning@prd-inc.com> David, I don't know how much this will help you, as I don't know much about your setup. I am running XP HVM guests on F7 (Moonshine) using the old fashioned text xen method (/etc/xen/auto/guest.hvm, xm create, xm destroy, etc), and I can't change actual CDs or DVDs in my XP guests. That is to say, I think if a CD/DVD is in the drive when I start the guest and hdc:cdrom is connected to /dev/cdrom in the hvm file, the CD/DVD in the drive works, however, changing it out does not. However, if hdc:cdrom is connected to /dev/cdrom and there is no disc in the drive (or perhaps even if there is), I can ues the xm block-attach and xm block-detach, for instance: xm block-list 2 xm block-detach 2 5632 -f xm block-attach 2 file:///iso/lm70200.iso hdc:cdrom r xm block-detach 2 5632 -f xm block-attach 2 phy:/dev/cdrom hdc:cdrom r In the above commands, I listed the block devices, determined which was the cdrom, detached it, attached an iso, used it as needed in the guest, detached the iso, and reattached the physical drive (even though it doesn't work). I can do this over and over again. Going back to the physical device probably isn't necessary, but I do it so I am always starting from the same point. The reason I doubt it matters is that once XP is booted, it always shows that drive, detaching it doesn't make it disappear, and reattaching it doesn't give it a new ID (even if scanning for hardware changes between steps). I am also fairly certain that trying to attach one iso over another isn't sufficient. If you eject the tray on the cdrom drive from within xp, you're done until you reboot as far as I can tell, but with the above steps, if you don't do that, it seems to work alright. I don't know if this will help you at all, seeing a how you more than likely use virt-install, virt-manager, etc, but I figure it can't hurt if there is a similar process for that system. Good luck, Dustin From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Levinger Sent: Thursday, April 17, 2008 20:11 To: fedora-xen at redhat.com Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? Hey guys and gals, As the subject suggests, is it possible to block-attach a newly placed CD/DVD/HD/Img file to an XP guest? I've done the "normal" block-attach command and it says it has "attached" but nothing shows in the XP guest. d -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsolan at knouse.com Fri Apr 18 13:28:32 2008 From: jsolan at knouse.com (Jason Solan) Date: Fri, 18 Apr 2008 09:28:32 -0400 Subject: [Fedora-xen] iwl3945 driver In-Reply-To: <57127b5f0804151737i3496a3aesc38253b365371de2@mail.gmail.com> References: <1208287152.5433.10.camel@jsolan.knouse.com> <57127b5f0804151737i3496a3aesc38253b365371de2@mail.gmail.com> Message-ID: <1208525312.3219.8.camel@jsolan.knouse.com> Hello, Thanks for the information. Where can I find this driver? Will it work with xen? On Fedora 8 standard, the driver loaded automatically was iwl3945. I didn't mention it earlier, but the network device is the intel pro wireless 3945 ABG. Also, I have tried using ndiswrapper for the wireless card, and it almost works. I installed ndiswrapper from the livna repository and installed my windows driver. If I rmmod iwl3945, then insmod ndiswrapper, i get a kernel oops, but the wireless card still works. If I try to enable ndiswrapper at boot time (/etc/modprobe.conf) then the kernel dump causes the system to crash. Has anyone had any luck with ndiswrapper and xen? As I understand it, Fedora 9 does not have dom0 support, so I'd really like to get wireless working under Fedora 8 xen. I've also tried usb wireless cards, but they seem to cause a kernel dump as soon as I enable them. Thanks, --Jason On Wed, 2008-04-16 at 06:07 +0530, Deependra Singh Shekhawat wrote: > Hi, > > You should use ipw3945 if you want to have a working wireless device > in fedora8 kernel. > > Thanks > Deependra Singh Shekhawat > > On Wed, Apr 16, 2008 at 12:49 AM, Jason Solan wrote: > > Hello, > > > > I am wondering if anyone has the iwl3945 driver working on xen? I'm > > using Fedora 8 and under the standard kernel the driver works great. > > When i switch the xen kernel, fedora can no longer find the device. > > > > If I do a > > > > kudzu -pc NETWORK > > > > the device shows up (as eth1 instead of wlan0) but it does not have a > > mac address. > > > > I've tried just manually adding the entry and its mac address > > to /etc/sysconfig/hwconf but that didn't seem to do anything for me. > > > > Any help is appreciated. > > > > --Jason > > > > > > > > > > > > > > IMPORTANT: > > This transmission is sent on behalf of Knouse Foods for business > > purposes. It is for the intended recipient only. If you are not the intended > > recipient or a person responsible for delivering this transmission to > > the intended recipient, you may not disclose, copy or distribute this > > transmission or take any action in reliance on it. If you received this > > transmission in error, please notify us immediately by replying to this > > Email message, and please dispose of and delete this transmission. > > Thank you. > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > IMPORTANT: This transmission is sent on behalf of Knouse Foods for business purposes. It is for the intended recipient only. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this Email message, and please dispose of and delete this transmission. Thank you. From pasik at iki.fi Fri Apr 18 14:46:05 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 18 Apr 2008 17:46:05 +0300 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] In-Reply-To: <1208504522.3464.4.camel@muff> References: <1208504522.3464.4.camel@muff> Message-ID: <20080418144605.GS21162@edu.joroinen.fi> On Fri, Apr 18, 2008 at 08:42:02AM +0100, Mark McLoughlin wrote: > Hey, > There doesn't appear to be any install trees yet for the F9 Preview > release, but please do try and run F9 rawhide in your Xen DomU (both > i686 and x86_64) and help us flush out any remaining issues in the lead > up to the final release. > Hi! I just tried installing rawhide domU with virt-inst on CentOS 5.1 x86 32bit dom0: virt-install -n test -r 512 --vcpus=1 -f /dev/vg0/test_disk1 --vnc -p -b xenbr0 -l "ftp://ftp.mirror.country/pub/mirrors/fedora.redhat.com/pub/fedora/linux/development/i386/os" Graphical installation seems to work fine.. and now the mouse/pointer even follows like it should :) # uname -a Linux f9preview.localdomain 2.6.25-0.24.rc9.fc9.i686.xen #1 SMP Tue Apr 15 19:01:14 EDT 2008 i686 i686 i386 GNU/Linux Is there something specific I should try? Thanks for all the hard work on pv_ops! -- Pasi From markmc at redhat.com Fri Apr 18 14:52:14 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 18 Apr 2008 15:52:14 +0100 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] In-Reply-To: <20080418144605.GS21162@edu.joroinen.fi> References: <1208504522.3464.4.camel@muff> <20080418144605.GS21162@edu.joroinen.fi> Message-ID: <1208530334.16291.17.camel@muff> On Fri, 2008-04-18 at 17:46 +0300, Pasi K?rkk?inen wrote: > I just tried installing rawhide domU with virt-inst on CentOS 5.1 x86 32bit > dom0: Great, thanks. > Is there something specific I should try? Nope, just use it in anger if you can, test new kernel-xen updates etc. x86_64 DomU is where most of our current troubles are, so people testing that would be greatly appreciated too. Cheers, Mark. From davidl at matissenetworks.com Fri Apr 18 21:10:59 2008 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 18 Apr 2008 14:10:59 -0700 (PDT) Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? In-Reply-To: <002c01c8a150$99ad34a0$cd079de0$@Henning@prd-inc.com> References: <00c101c8a0e8$b5f94c10$a564a8c0@nbdavidl> <002c01c8a150$99ad34a0$cd079de0$@Henning@prd-inc.com> Message-ID: <004f01c8a198$ab7a0260$a564a8c0@nbdavidl> Thanks Dustin, Your response gave me hope and I kept poking around and found the following two previous email threads: http://xen.markmail.org/message/55544ap2h34mzi3n?q=block-attach+hvm &page=6 and http://xen.markmail.org/message/xxnkqhjgsqrtvukn?q=block-attach+hvm &page=2#query:block-attach%20hvm+page:2+mid:6eyxxqeg3vrrobe6+state:results And it looks like xm block-configure was the ticket! It hasn't worked for me 100% but by setting the devices to "null" it works pretty darn good :-) Thanks again, David _____ From: Dustin Henning [mailto:Dustin.Henning at prd-inc.com] Sent: Friday, April 18, 2008 5:35 AM To: 'David Levinger'; fedora-xen at redhat.com Subject: RE: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? David, I don't know how much this will help you, as I don't know much about your setup. I am running XP HVM guests on F7 (Moonshine) using the old fashioned text xen method (/etc/xen/auto/guest.hvm, xm create, xm destroy, etc), and I can't change actual CDs or DVDs in my XP guests. That is to say, I think if a CD/DVD is in the drive when I start the guest and hdc:cdrom is connected to /dev/cdrom in the hvm file, the CD/DVD in the drive works, however, changing it out does not. However, if hdc:cdrom is connected to /dev/cdrom and there is no disc in the drive (or perhaps even if there is), I can ues the xm block-attach and xm block-detach, for instance: xm block-list 2 xm block-detach 2 5632 -f xm block-attach 2 file:///iso/lm70200.iso hdc:cdrom r xm block-detach 2 5632 -f xm block-attach 2 phy:/dev/cdrom hdc:cdrom r In the above commands, I listed the block devices, determined which was the cdrom, detached it, attached an iso, used it as needed in the guest, detached the iso, and reattached the physical drive (even though it doesn't work). I can do this over and over again. Going back to the physical device probably isn't necessary, but I do it so I am always starting from the same point. The reason I doubt it matters is that once XP is booted, it always shows that drive, detaching it doesn't make it disappear, and reattaching it doesn't give it a new ID (even if scanning for hardware changes between steps). I am also fairly certain that trying to attach one iso over another isn't sufficient. If you eject the tray on the cdrom drive from within xp, you're done until you reboot as far as I can tell, but with the above steps, if you don't do that, it seems to work alright. I don't know if this will help you at all, seeing a how you more than likely use virt-install, virt-manager, etc, but I figure it can't hurt if there is a similar process for that system. Good luck, Dustin From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Levinger Sent: Thursday, April 17, 2008 20:11 To: fedora-xen at redhat.com Subject: [Fedora-xen] Can you attach CDs/DVDs/HDs to an XP Guest? Hey guys and gals, As the subject suggests, is it possible to block-attach a newly placed CD/DVD/HD/Img file to an XP guest? I've done the "normal" block-attach command and it says it has "attached" but nothing shows in the XP guest. d -------------- next part -------------- An HTML attachment was scrubbed... URL: From turbo at bayour.com Sat Apr 19 11:29:51 2008 From: turbo at bayour.com (Turbo Fredriksson) Date: Sat, 19 Apr 2008 13:29:51 +0200 Subject: [Fedora-xen] Weird routing problem References: <668269706.5121208450894669.JavaMail.root@mail.mro.nmt.edu> Message-ID: <87od86hykw.fsf@pumba.bayour.com> Quoting Ron King : > Your default route is eth0 for the network shared between the two > servers. Should be eth0:0. With the help of Ron on private conversation, I solved the problem by removing the network route, leaving only the host route on Alexander: alexander:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.4.11 0.0.0.0 255.255.255.255 UH 0 0 0 vif5.0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Thanx all for the help, much apprecieated. From nospam2 at mcswartz.org Sat Apr 19 14:45:32 2008 From: nospam2 at mcswartz.org (John Swartzentruber) Date: Sat, 19 Apr 2008 10:45:32 -0400 Subject: [Fedora-xen] Upgrading a Xen guest Message-ID: I hope I am using correct terminology for this question. I'm a home user who is using Xen in a small way, but want to ramp up my usage over time. I have a Fedora 7 host server. On this computer, I installed two Fedora 8 virtual servers using virt-install. What I can't find the answer to, is how to upgrade these virtual computers from Fedora 8 to Fedora 9 when Fedora 9 is released. On my physical server, I normally create an installation DVD, then boot from that. Anaconda then takes care of appropriately upgrading the system and generally does a very good job of it. So how will I do the equivalent for a virtual computer? I don't know how to virtually put the virtual DVD in the virtual DVD drive and reboot the virtual computer. I know I've read of ways to upgrade using Yum, which I assume would work, but I'd prefer to upgrade using Anaconda because that seems like a much safer approach. Because my two current virtual computers are not used for much yet, I could start from scratch, but in the future that isn't going to be the way I will want to handle the upgrades. Thanks for your help. I've read the FedoraProject.org wiki docs, but if there are references I missed, please feel free to point me to them. From davidl at matissenetworks.com Sat Apr 19 17:40:35 2008 From: davidl at matissenetworks.com (David Levinger) Date: Sat, 19 Apr 2008 10:40:35 -0700 (PDT) Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM Message-ID: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> Hey Guys, I have a fully virtualized XP guest that is set to have 2 VCPUs and in the guest I see 2 CPUs but when it is under heavy load it only utilizes 1 of the physical cores. Both xm and virsh show that the guest only has 1 CPU, but my config file and the guest show it should have 2. What am I missing? How can I get this guest to have access to both cores? Thanks! David -------------- next part -------------- An HTML attachment was scrubbed... URL: From deepc2005 at hotmail.com Sun Apr 20 15:46:40 2008 From: deepc2005 at hotmail.com (Maximilian Freisinger) Date: Sun, 20 Apr 2008 11:46:40 -0400 Subject: [Fedora-xen] Freeze with xen is relinquishing vga console Message-ID: Hello i'm just testing f9 with xen but when i try to boot with xen kernel it freezes at "xen is relinquishing vga console" Anyone an idea why? My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset thx, Felix _________________________________________________________________ Get in touch in an instant. Get Windows Live Messenger now. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008 -------------- next part -------------- An HTML attachment was scrubbed... URL: From itamar at ispbrasil.com.br Sun Apr 20 15:49:36 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 20 Apr 2008 12:49:36 -0300 Subject: [Fedora-xen] Freeze with xen is relinquishing vga console In-Reply-To: References: Message-ID: <480B6610.40207@ispbrasil.com.br> are you trying to boot as dom0 or domu ? Maximilian Freisinger wrote: > Hello > i'm just testing f9 with xen but when i try to boot with xen kernel it > freezes at "xen is relinquishing vga console" > Anyone an idea why? > My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset > thx, Felix > From deepc2005 at hotmail.com Sun Apr 20 16:09:15 2008 From: deepc2005 at hotmail.com (Maximilian Freisinger) Date: Sun, 20 Apr 2008 12:09:15 -0400 Subject: [Fedora-xen] Freeze with xen is relinquishing vga console In-Reply-To: <480B6610.40207@ispbrasil.com.br> References: <480B6610.40207@ispbrasil.com.br> Message-ID: I'm trying to boot as dom0 > Date: Sun, 20 Apr 2008 12:49:36 -0300> From: itamar at ispbrasil.com.br> To: deepc2005 at hotmail.com> CC: fedora-xen at redhat.com> Subject: Re: [Fedora-xen] Freeze with xen is relinquishing vga console> > are you trying to boot as dom0 or domu ?> > > Maximilian Freisinger wrote:> > Hello> > i'm just testing f9 with xen but when i try to boot with xen kernel it > > freezes at "xen is relinquishing vga console"> > Anyone an idea why?> > My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset> > thx, Felix> >> > _________________________________________________________________ Get in touch in an instant. Get Windows Live Messenger now. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008 -------------- next part -------------- An HTML attachment was scrubbed... URL: From itamar at ispbrasil.com.br Sun Apr 20 16:19:51 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 20 Apr 2008 13:19:51 -0300 Subject: [Fedora-xen] Freeze with xen is relinquishing vga console In-Reply-To: References: <480B6610.40207@ispbrasil.com.br> Message-ID: <480B6D27.6010800@ispbrasil.com.br> fedora 9 kernel-xen package at this moment works only as domU if you need dom0 try fedora 8 Maximilian Freisinger wrote: > I'm trying to boot as dom0 > > > > ------------------------------------------------------------------------ > > Date: Sun, 20 Apr 2008 12:49:36 -0300 > > From: itamar at ispbrasil.com.br > > To: deepc2005 at hotmail.com > > CC: fedora-xen at redhat.com > > Subject: Re: [Fedora-xen] Freeze with xen is relinquishing vga console > > > > are you trying to boot as dom0 or domu ? > > > > > > Maximilian Freisinger wrote: > > > Hello > > > i'm just testing f9 with xen but when i try to boot with xen > kernel it > > > freezes at "xen is relinquishing vga console" > > > Anyone an idea why? > > > My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 > chipset > > > thx, Felix > > > From alroger.filho at sdev.com Sun Apr 20 16:36:01 2008 From: alroger.filho at sdev.com (Alroger L. Gomes F.) Date: Sun, 20 Apr 2008 13:36:01 -0300 Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM In-Reply-To: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> References: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> Message-ID: <480B70F1.9040600@sdev.com> I have noticed that too. David Levinger wrote: > > Hey Guys, > > I have a fully virtualized XP guest that is set to have 2 VCPUs and in > the guest I see 2 CPUs but when it is under heavy load it only > utilizes 1 of the physical cores. > > Both xm and virsh show that the guest only has 1 CPU, but my config > file and the guest show it should have 2. > > What am I missing? How can I get this guest to have access to both cores? > > Thanks! > > David > -- Alroger Luiz Gomes Filho SDEV - Smart Developments http://www.sdev.com http://cafe-ti.blog.br So little time, so many systems . . . From alroger.filho at sdev.com Sun Apr 20 16:38:06 2008 From: alroger.filho at sdev.com (Alroger L. Gomes F.) Date: Sun, 20 Apr 2008 13:38:06 -0300 Subject: [Fedora-xen] Freeze with xen is relinquishing vga console In-Reply-To: References: Message-ID: <480B716E.6080002@sdev.com> Fedora9 does not work as a XEN Host (Dom0). I read that it will be back in Fedora10. I sure would help if this was clearly specified in the Fedora9 wiki. Maximilian Freisinger wrote: > Hello > i'm just testing f9 with xen but when i try to boot with xen kernel it > freezes at "xen is relinquishing vga console" > Anyone an idea why? > My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset > thx, Felix > > -- Alroger Luiz Gomes Filho SDEV - Smart Developments http://www.sdev.com http://cafe-ti.blog.br So little time, so many systems . . . From acathrow at redhat.com Sun Apr 20 18:11:39 2008 From: acathrow at redhat.com (Andrew Cathrow) Date: Sun, 20 Apr 2008 14:11:39 -0400 Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM In-Reply-To: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> References: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> Message-ID: <1208715099.7117.7.camel@aic-desktop.cathrow.org> When Windows installed selects the HAL library appropriate the the hardware. If you install on a single CPU system then the uniprocessor HAL is installed. If you then add a second vcpu to the guest then the windows HAL won't see it. You'll need to replace Window's hal. See links below for some background. I don't think there is a Microsoft *supported* way to do this but I've done this a number of times without issue on XP and 2000, but I've not tried this on 2003, 2008 or Vista http://support.microsoft.com/kb/309283/en-us http://support.microsoft.com/default.aspx?scid=kb;EN-US;237556 On Sat, 2008-04-19 at 10:40 -0700, David Levinger wrote: > Hey Guys, > > I have a fully virtualized XP guest that is set to have 2 VCPUs and in > the guest I see 2 CPUs but when it is under heavy load it only > utilizes 1 of the physical cores. > > Both xm and virsh show that the guest only has 1 CPU, but my config > file and the guest show it should have 2. > > What am I missing? How can I get this guest to have access to both > cores? > > Thanks! > > David > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfu at kaneda.iguw.tuwien.ac.at Sun Apr 20 19:19:48 2008 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Sun, 20 Apr 2008 21:19:48 +0200 Subject: [Fedora-xen] no sda1 in DomU Message-ID: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> hi, I try to get the Centos.5-1.64 image from Jailtime.org running in a Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the DomU. I tried both file- and lvm-backed VBDs, but with no luck: [...] Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) configfile looks like this: kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" memory = 256 name = "myzel" vif = [ '' ] dhcp= "dhcp" disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', 'phy:vg_virtual/lv_myzel_swap,sda2,w'] # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] root = "/dev/sda1" extra = "fastboot" (I also tried device name xvda, but to no avail) Dom0 kernel: Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux any help appreciated. xend.log excerpt and DomU dmesg follows: *** xend.log excerpt: [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_t! ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_! time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': 256} [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. *** DomU dmesg: [root at xenserv xen]# xm create -c myzel.cfg Using config file "/etc/xen/myzel.cfg". Started domain myzel Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 67584 Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 2666.982 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1208718852.478:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key F8170EB5CF71EF90 - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 67584 Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 2666.982 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1208718852.478:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key F8170EB5CF71EF90 - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) From itamar at ispbrasil.com.br Sun Apr 20 19:27:17 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 20 Apr 2008 16:27:17 -0300 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> Message-ID: <480B9915.40702@ispbrasil.com.br> create a initrd with xenblk module Rainer Fuegenstein wrote: > hi, > > I try to get the Centos.5-1.64 image from Jailtime.org running in a > Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the > DomU. I tried both file- and lvm-backed VBDs, but with no luck: > > [...] > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > configfile looks like this: > > kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" > memory = 256 > name = "myzel" > vif = [ '' ] > dhcp= "dhcp" > disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', > 'phy:vg_virtual/lv_myzel_swap,sda2,w'] > # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] > root = "/dev/sda1" > extra = "fastboot" > > (I also tried device name xvda, but to no avail) > > Dom0 kernel: > Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux > > any help appreciated. xend.log excerpt and DomU dmesg follows: > > *** xend.log excerpt: > > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None > [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. > [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. > [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen > [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = > [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = > [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. > [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. > [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. > [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. > [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_t! > ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_! > time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': 256} > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. > [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen > [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = > [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. > [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. > [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > > > > *** DomU dmesg: > [root at xenserv xen]# xm create -c myzel.cfg > Using config file "/etc/xen/myzel.cfg". > Started domain myzel > Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) > Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000010800000 (usable) > No mptable found. > Built 1 zonelists. Total pages: 67584 > Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > Initializing CPU#0 > PID hash table entries: 2048 (order: 11, 16384 bytes) > Xen reported: 2666.982 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > Software IO TLB disabled > Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) > Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 256 > CPU: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 1024K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > (SMP-)alternatives turned off > Brought up 1 CPUs > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > TCP bind hash table entries: 8192 (order: 5, 131072 bytes) > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1208718852.478:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key F8170EB5CF71EF90 > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) > Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000010800000 (usable) > No mptable found. > Built 1 zonelists. Total pages: 67584 > Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > Initializing CPU#0 > PID hash table entries: 2048 (order: 11, 16384 bytes) > Xen reported: 2666.982 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > Software IO TLB disabled > Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) > Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 256 > CPU: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 1024K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > (SMP-)alternatives turned off > Brought up 1 CPUs > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > TCP bind hash table entries: 8192 (order: 5, 131072 bytes) > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1208718852.478:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key F8170EB5CF71EF90 > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > From alroger.filho at sdev.com Sun Apr 20 21:27:34 2008 From: alroger.filho at sdev.com (Alroger L. Gomes F.) Date: Sun, 20 Apr 2008 18:27:34 -0300 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> Message-ID: <480BB546.9010805@sdev.com> Well, I suspect your disk parameters are simply wrong... disk = ['phy:vg_virtual/lv_myzel_root,sda1,w','phy:vg_virtual/lv_myzel_swap,sda2,w'] -This one seems to be messing / or /dev before vg_virtual. disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] -This one I'm not sure, but I use "file:/", have you tried it like below? disk = ['file:/virtual/centos.5-1.64.img,sda1,w', 'file:/virtual/centos.swap,sda2,w'] Rainer Fuegenstein wrote: > hi, > > I try to get the Centos.5-1.64 image from Jailtime.org running in a > Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the > DomU. I tried both file- and lvm-backed VBDs, but with no luck: > > [...] > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > configfile looks like this: > > kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" > memory = 256 > name = "myzel" > vif = [ '' ] > dhcp= "dhcp" > disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', > 'phy:vg_virtual/lv_myzel_swap,sda2,w'] > # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] > root = "/dev/sda1" > extra = "fastboot" > > (I also tried device name xvda, but to no avail) > > Dom0 kernel: > Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux > > any help appreciated. xend.log excerpt and DomU dmesg follows: > > *** xend.log excerpt: > > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None > [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. > [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. > [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen > [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = > [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 > [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = > [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. > [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} > [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. > [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. > [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. > [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. > [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. > [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_t! > ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', 0.15769001999999999], ['online_vcpus', 1], ['up_! > time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': 256} > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing > [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. > [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen > [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = > [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 > [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. > [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. > [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 > [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. > > > > *** DomU dmesg: > [root at xenserv xen]# xm create -c myzel.cfg > Using config file "/etc/xen/myzel.cfg". > Started domain myzel > Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) > Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000010800000 (usable) > No mptable found. > Built 1 zonelists. Total pages: 67584 > Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > Initializing CPU#0 > PID hash table entries: 2048 (order: 11, 16384 bytes) > Xen reported: 2666.982 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > Software IO TLB disabled > Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) > Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 256 > CPU: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 1024K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > (SMP-)alternatives turned off > Brought up 1 CPUs > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > TCP bind hash table entries: 8192 (order: 5, 131072 bytes) > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1208718852.478:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key F8170EB5CF71EF90 > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) > Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000010800000 (usable) > No mptable found. > Built 1 zonelists. Total pages: 67584 > Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot > Initializing CPU#0 > PID hash table entries: 2048 (order: 11, 16384 bytes) > Xen reported: 2666.982 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > Software IO TLB disabled > Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) > Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 256 > CPU: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 1024K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > (SMP-)alternatives turned off > Brought up 1 CPUs > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > TCP bind hash table entries: 8192 (order: 5, 131072 bytes) > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1208718852.478:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key F8170EB5CF71EF90 > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > > -- Alroger Luiz Gomes Filho SDEV - Smart Developments http://www.sdev.com http://cafe-ti.blog.br So little time, so many systems . . . From rfu at kaneda.iguw.tuwien.ac.at Sun Apr 20 22:20:05 2008 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Mon, 21 Apr 2008 00:20:05 +0200 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <480B9915.40702@ispbrasil.com.br> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> <480B9915.40702@ispbrasil.com.br> Message-ID: <4510644480.20080421002005@kaneda.iguw.tuwien.ac.at> hi, II> create a initrd with xenblk module big thanks for the hint - I created the initrd by using mkinitrd -v -f --preload=ext3 --preload=xenblk --preload=xennet --omit-raid-modules --omit-lvm-modules --omit-scsi-modules /boot/initrd-2.6.18.xenU.img `uname -r` the VM boots now, but hangs after starting the crond: [...] Press 'I' to enter interactive startup. Setting clock : Sun Apr 20 18:15:04 EDT 2008 [ OK ] Starting udev: [ OK ] Setting hostname myzel: [ OK ] No devices found Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 /dev/sda1: clean, 26084/1310720 files, 269769/2621440 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] Starting crond: [ OK ] ... hangs here ... also, although the network is configured properly, the interface can't be pinged. a "xm shutdown myzel" shuts down the VM properly (vm console shows shutdown messages and finally terminates). do I need to put any additional modules into the initrd ? tnx in advance. II> Rainer Fuegenstein wrote: >> hi, >> >> I try to get the Centos.5-1.64 image from Jailtime.org running in a >> Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the >> DomU. I tried both file- and lvm-backed VBDs, but with no luck: >> >> [...] >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vbd/2049 >> XENBUS: Device with no driver: device/vbd/2050 >> XENBUS: Device with no driver: device/vif/0 >> md: Autodetecting RAID arrays. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "sda1" or unknown-block(0,0) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >> >> configfile looks like this: >> >> kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" >> memory = 256 >> name = "myzel" >> vif = [ '' ] >> dhcp= "dhcp" >> disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', >> 'phy:vg_virtual/lv_myzel_swap,sda2,w'] >> # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] >> root = "/dev/sda1" >> extra = "fastboot" >> >> (I also tried device name xvda, but to no avail) >> >> Dom0 kernel: >> Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux >> >> any help appreciated. xend.log excerpt and DomU dmesg follows: >> >> *** xend.log excerpt: >> >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >> [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 >> [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = >> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >> 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. >> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >> 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >> '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >> '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >> 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux >> (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} >> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. >> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. >> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. >> [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. >> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. >> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >> 0.15769001999999999], ['online_vcpus', 1], ['up_t! >> ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >> 0.15769001999999999], ['online_vcpus', 1], ['up_! >> time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': >> '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', >> ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': >> 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', >> 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], >> 'bootloader': None, 'cpu': None, 'maxmem': 256} >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. >> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing >> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >> [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 >> [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >> '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >> '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. >> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >> 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. >> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >> 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >> 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel >> /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. >> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. >> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 >> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) >> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >> >> >> >> *** DomU dmesg: >> [root at xenserv xen]# xm create -c myzel.cfg >> Using config file "/etc/xen/myzel.cfg". >> Started domain myzel >> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000010800000 (usable) >> No mptable found. >> Built 1 zonelists. Total pages: 67584 >> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >> Initializing CPU#0 >> PID hash table entries: 2048 (order: 11, 16384 bytes) >> Xen reported: 2666.982 MHz processor. >> Console: colour dummy device 80x25 >> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> Software IO TLB disabled >> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >> Security Framework v1.0.0 initialized >> SELinux: Initializing. >> selinux_register_security: Registering secondary module capability >> Capability LSM initialized as secondary >> Mount-cache hash table entries: 256 >> CPU: Trace cache: 12K uops, L1 D cache: 16K >> CPU: L2 cache: 1024K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 1 >> (SMP-)alternatives turned off >> Brought up 1 CPUs >> Grant table initialized >> NET: Registered protocol family 16 >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >> Brought up 1 CPUs >> PCI: setting up Xen PCI frontend stub >> ACPI: Interpreter disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> pnp: PnP ACPI: disabled >> xen_mem: Initialising balloon driver. >> usbcore: registered new driver usbfs >> usbcore: registered new driver hub >> PCI: System does not support PCI >> PCI: System does not support PCI >> NetLabel: Initializing >> NetLabel: domain hash size = 128 >> NetLabel: protocols = UNLABELED CIPSOv4 >> NetLabel: unlabeled traffic allowed by default >> NET: Registered protocol family 2 >> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >> TCP: Hash tables configured (established 16384 bind 8192) >> TCP reno registered >> audit: initializing netlink socket (disabled) >> audit(1208718852.478:1): initialized >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> Initializing Cryptographic API >> ksign: Installing public key data >> Loading keyring >> - Added public key F8170EB5CF71EF90 >> - User ID: CentOS (Kernel Module GPG key) >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >> rtc: IRQ 8 is not free. >> Non-volatile memory driver v1.2 >> Linux agpgart interface v0.101 (c) Dave Jones >> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >> Xen virtual console successfully installed as xvc0 >> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000010800000 (usable) >> No mptable found. >> Built 1 zonelists. Total pages: 67584 >> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >> Initializing CPU#0 >> PID hash table entries: 2048 (order: 11, 16384 bytes) >> Xen reported: 2666.982 MHz processor. >> Console: colour dummy device 80x25 >> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> Software IO TLB disabled >> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >> Security Framework v1.0.0 initialized >> SELinux: Initializing. >> selinux_register_security: Registering secondary module capability >> Capability LSM initialized as secondary >> Mount-cache hash table entries: 256 >> CPU: Trace cache: 12K uops, L1 D cache: 16K >> CPU: L2 cache: 1024K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 1 >> (SMP-)alternatives turned off >> Brought up 1 CPUs >> Grant table initialized >> NET: Registered protocol family 16 >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >> Brought up 1 CPUs >> PCI: setting up Xen PCI frontend stub >> ACPI: Interpreter disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> pnp: PnP ACPI: disabled >> xen_mem: Initialising balloon driver. >> usbcore: registered new driver usbfs >> usbcore: registered new driver hub >> PCI: System does not support PCI >> PCI: System does not support PCI >> NetLabel: Initializing >> NetLabel: domain hash size = 128 >> NetLabel: protocols = UNLABELED CIPSOv4 >> NetLabel: unlabeled traffic allowed by default >> NET: Registered protocol family 2 >> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >> TCP: Hash tables configured (established 16384 bind 8192) >> TCP reno registered >> audit: initializing netlink socket (disabled) >> audit(1208718852.478:1): initialized >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> Initializing Cryptographic API >> ksign: Installing public key data >> Loading keyring >> - Added public key F8170EB5CF71EF90 >> - User ID: CentOS (Kernel Module GPG key) >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >> rtc: IRQ 8 is not free. >> Non-volatile memory driver v1.2 >> Linux agpgart interface v0.101 (c) Dave Jones >> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >> Xen virtual console successfully installed as xvc0 >> Event-channel device installed. >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx >> ide-floppy driver 0.99.newide >> usbcore: registered new driver hiddev >> usbcore: registered new driver usbhid >> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> md: bitmap version 4.39 >> TCP bic registered >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vbd/2049 >> XENBUS: Device with no driver: device/vbd/2050 >> XENBUS: Device with no driver: device/vif/0 >> md: Autodetecting RAID arrays. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "sda1" or unknown-block(0,0) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> ------------------------------------------------------------------------------ Rainer Fuegenstein rfu at kaneda.iguw.tuwien.ac.at ------------------------------------------------------------------------------ "Why are you looking into the darkness and not into the fire as we do ?", Nell asked. "Because the darkness is where danger comes from," Peter said, "and from the fire comes only illusion". (from "The Diamond Age") ------------------------------------------------------------------------------ From itamar at ispbrasil.com.br Sun Apr 20 22:36:43 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 20 Apr 2008 19:36:43 -0300 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <4510644480.20080421002005@kaneda.iguw.tuwien.ac.at> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> <480B9915.40702@ispbrasil.com.br> <4510644480.20080421002005@kaneda.iguw.tuwien.ac.at> Message-ID: <480BC57B.4060208@ispbrasil.com.br> boot in single user mode, start network and update your linux with yum Rainer Fuegenstein wrote: > hi, > > II> create a initrd with xenblk module > > big thanks for the hint - I created the initrd by using > > mkinitrd -v -f --preload=ext3 --preload=xenblk --preload=xennet --omit-raid-modules --omit-lvm-modules --omit-scsi-modules /boot/initrd-2.6.18.xenU.img `uname -r` > > the VM boots now, but hangs after starting the crond: > > [...] > Press 'I' to enter interactive startup. > Setting clock : Sun Apr 20 18:15:04 EDT 2008 [ OK ] > Starting udev: [ OK ] > Setting hostname myzel: [ OK ] > No devices found > Setting up Logical Volume Management: No volume groups found > [ OK ] > Checking filesystems > Checking all file systems. > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 > /dev/sda1: clean, 26084/1310720 files, 269769/2621440 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > Mounting local filesystems: [ OK ] > Enabling /etc/fstab swaps: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Starting system logger: [ OK ] > Starting kernel logger: [ OK ] > Starting sshd: [ OK ] > Starting crond: [ OK ] > ... hangs here ... > > also, although the network is configured properly, the interface can't > be pinged. > > a "xm shutdown myzel" shuts down the VM properly (vm console shows > shutdown messages and finally terminates). > > do I need to put any additional modules into the initrd ? > > tnx in advance. > > II> Rainer Fuegenstein wrote: > >>> hi, >>> >>> I try to get the Centos.5-1.64 image from Jailtime.org running in a >>> Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the >>> DomU. I tried both file- and lvm-backed VBDs, but with no luck: >>> >>> [...] >>> Initializing IPsec netlink socket >>> NET: Registered protocol family 1 >>> NET: Registered protocol family 17 >>> XENBUS: Device with no driver: device/vbd/2049 >>> XENBUS: Device with no driver: device/vbd/2050 >>> XENBUS: Device with no driver: device/vif/0 >>> md: Autodetecting RAID arrays. >>> md: autorun ... >>> md: ... autorun DONE. >>> VFS: Cannot open root device "sda1" or unknown-block(0,0) >>> Please append a correct "root=" boot option >>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >>> >>> configfile looks like this: >>> >>> kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" >>> memory = 256 >>> name = "myzel" >>> vif = [ '' ] >>> dhcp= "dhcp" >>> disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', >>> 'phy:vg_virtual/lv_myzel_swap,sda2,w'] >>> # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] >>> root = "/dev/sda1" >>> extra = "fastboot" >>> >>> (I also tried device name xvda, but to no avail) >>> >>> Dom0 kernel: >>> Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux >>> >>> any help appreciated. xend.log excerpt and DomU dmesg follows: >>> >>> *** xend.log excerpt: >>> >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >>> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >>> [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 >>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = >>> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>> 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >>> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>> 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >>> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >>> '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >>> '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >>> 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux >>> (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >>> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} >>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. >>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. >>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. >>> [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. >>> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. >>> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >>> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >>> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >>> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >>> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >>> 0.15769001999999999], ['online_vcpus', 1], ['up_t! >>> ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >>> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >>> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >>> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >>> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >>> 0.15769001999999999], ['online_vcpus', 1], ['up_! >>> time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': >>> '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', >>> ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': >>> 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', >>> 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], >>> 'bootloader': None, 'cpu': None, 'maxmem': 256} >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing >>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >>> [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 >>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >>> '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >>> '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>> 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >>> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>> 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >>> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >>> 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel >>> /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >>> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. >>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. >>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 >>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) >>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>> >>> >>> >>> *** DomU dmesg: >>> [root at xenserv xen]# xm create -c myzel.cfg >>> Using config file "/etc/xen/myzel.cfg". >>> Started domain myzel >>> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >>> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >>> BIOS-provided physical RAM map: >>> Xen: 0000000000000000 - 0000000010800000 (usable) >>> No mptable found. >>> Built 1 zonelists. Total pages: 67584 >>> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>> Initializing CPU#0 >>> PID hash table entries: 2048 (order: 11, 16384 bytes) >>> Xen reported: 2666.982 MHz processor. >>> Console: colour dummy device 80x25 >>> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >>> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >>> Software IO TLB disabled >>> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >>> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >>> Security Framework v1.0.0 initialized >>> SELinux: Initializing. >>> selinux_register_security: Registering secondary module capability >>> Capability LSM initialized as secondary >>> Mount-cache hash table entries: 256 >>> CPU: Trace cache: 12K uops, L1 D cache: 16K >>> CPU: L2 cache: 1024K >>> CPU: Physical Processor ID: 0 >>> CPU: Processor Core ID: 1 >>> (SMP-)alternatives turned off >>> Brought up 1 CPUs >>> Grant table initialized >>> NET: Registered protocol family 16 >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>> Brought up 1 CPUs >>> PCI: setting up Xen PCI frontend stub >>> ACPI: Interpreter disabled. >>> Linux Plug and Play Support v0.97 (c) Adam Belay >>> pnp: PnP ACPI: disabled >>> xen_mem: Initialising balloon driver. >>> usbcore: registered new driver usbfs >>> usbcore: registered new driver hub >>> PCI: System does not support PCI >>> PCI: System does not support PCI >>> NetLabel: Initializing >>> NetLabel: domain hash size = 128 >>> NetLabel: protocols = UNLABELED CIPSOv4 >>> NetLabel: unlabeled traffic allowed by default >>> NET: Registered protocol family 2 >>> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >>> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >>> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >>> TCP: Hash tables configured (established 16384 bind 8192) >>> TCP reno registered >>> audit: initializing netlink socket (disabled) >>> audit(1208718852.478:1): initialized >>> VFS: Disk quotas dquot_6.5.1 >>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>> Initializing Cryptographic API >>> ksign: Installing public key data >>> Loading keyring >>> - Added public key F8170EB5CF71EF90 >>> - User ID: CentOS (Kernel Module GPG key) >>> io scheduler noop registered >>> io scheduler anticipatory registered >>> io scheduler deadline registered >>> io scheduler cfq registered (default) >>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >>> rtc: IRQ 8 is not free. >>> Non-volatile memory driver v1.2 >>> Linux agpgart interface v0.101 (c) Dave Jones >>> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >>> Xen virtual console successfully installed as xvc0 >>> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >>> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >>> BIOS-provided physical RAM map: >>> Xen: 0000000000000000 - 0000000010800000 (usable) >>> No mptable found. >>> Built 1 zonelists. Total pages: 67584 >>> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>> Initializing CPU#0 >>> PID hash table entries: 2048 (order: 11, 16384 bytes) >>> Xen reported: 2666.982 MHz processor. >>> Console: colour dummy device 80x25 >>> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >>> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >>> Software IO TLB disabled >>> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >>> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >>> Security Framework v1.0.0 initialized >>> SELinux: Initializing. >>> selinux_register_security: Registering secondary module capability >>> Capability LSM initialized as secondary >>> Mount-cache hash table entries: 256 >>> CPU: Trace cache: 12K uops, L1 D cache: 16K >>> CPU: L2 cache: 1024K >>> CPU: Physical Processor ID: 0 >>> CPU: Processor Core ID: 1 >>> (SMP-)alternatives turned off >>> Brought up 1 CPUs >>> Grant table initialized >>> NET: Registered protocol family 16 >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>> Brought up 1 CPUs >>> PCI: setting up Xen PCI frontend stub >>> ACPI: Interpreter disabled. >>> Linux Plug and Play Support v0.97 (c) Adam Belay >>> pnp: PnP ACPI: disabled >>> xen_mem: Initialising balloon driver. >>> usbcore: registered new driver usbfs >>> usbcore: registered new driver hub >>> PCI: System does not support PCI >>> PCI: System does not support PCI >>> NetLabel: Initializing >>> NetLabel: domain hash size = 128 >>> NetLabel: protocols = UNLABELED CIPSOv4 >>> NetLabel: unlabeled traffic allowed by default >>> NET: Registered protocol family 2 >>> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >>> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >>> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >>> TCP: Hash tables configured (established 16384 bind 8192) >>> TCP reno registered >>> audit: initializing netlink socket (disabled) >>> audit(1208718852.478:1): initialized >>> VFS: Disk quotas dquot_6.5.1 >>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>> Initializing Cryptographic API >>> ksign: Installing public key data >>> Loading keyring >>> - Added public key F8170EB5CF71EF90 >>> - User ID: CentOS (Kernel Module GPG key) >>> io scheduler noop registered >>> io scheduler anticipatory registered >>> io scheduler deadline registered >>> io scheduler cfq registered (default) >>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >>> rtc: IRQ 8 is not free. >>> Non-volatile memory driver v1.2 >>> Linux agpgart interface v0.101 (c) Dave Jones >>> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >>> Xen virtual console successfully installed as xvc0 >>> Event-channel device installed. >>> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >>> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx >>> ide-floppy driver 0.99.newide >>> usbcore: registered new driver hiddev >>> usbcore: registered new driver usbhid >>> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >>> PNP: No PS/2 controller found. Probing ports directly. >>> i8042.c: No controller found. >>> mice: PS/2 mouse device common for all mice >>> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >>> md: bitmap version 4.39 >>> TCP bic registered >>> Initializing IPsec netlink socket >>> NET: Registered protocol family 1 >>> NET: Registered protocol family 17 >>> XENBUS: Device with no driver: device/vbd/2049 >>> XENBUS: Device with no driver: device/vbd/2050 >>> XENBUS: Device with no driver: device/vif/0 >>> md: Autodetecting RAID arrays. >>> md: autorun ... >>> md: ... autorun DONE. >>> VFS: Cannot open root device "sda1" or unknown-block(0,0) >>> Please append a correct "root=" boot option >>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >>> >>> -- >>> Fedora-xen mailing list >>> Fedora-xen at redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-xen >>> >>> >>> >>> > > > > > ------------------------------------------------------------------------------ > Rainer Fuegenstein rfu at kaneda.iguw.tuwien.ac.at > ------------------------------------------------------------------------------ > "Why are you looking into the darkness and not into the fire as we do ?", Nell > asked. "Because the darkness is where danger comes from," Peter said, "and > from the fire comes only illusion". (from "The Diamond Age") > ------------------------------------------------------------------------------ > > > > From rfu at kaneda.iguw.tuwien.ac.at Sun Apr 20 23:52:23 2008 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Mon, 21 Apr 2008 01:52:23 +0200 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <480BC57B.4060208@ispbrasil.com.br> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> <480B9915.40702@ispbrasil.com.br> <4510644480.20080421002005@kaneda.iguw.tuwien.ac.at> <480BC57B.4060208@ispbrasil.com.br> Message-ID: <1979874587.20080421015223@kaneda.iguw.tuwien.ac.at> II> boot in single user mode, start network and update your linux with yum ok, I'm now one step further: - can boot into single user mode - all block devices are mounted in the VM - network starts properly, yum update loaded & applied some updates - sshd starts, I can ssh into the vm from outside. dmesg shows some strange messages: XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?) Failed to obtain physical IRQ 6 floppy0: no floppy controllers found lp: driver loaded but no devices found my assumption: the VM can't connect to the console or some tty or whatever because of the missing drivers what means that the login prompt doesn't show. I exaleaded for the messages and found some threads with the same problem, but without solution: http://www.mail-archive.com/fedora-xen at redhat.com/msg00076.html http://lists.xensource.com/archives/html/xen-users/2006-08/msg00064.html II> Rainer Fuegenstein wrote: >> hi, >> >> II> create a initrd with xenblk module >> >> big thanks for the hint - I created the initrd by using >> >> mkinitrd -v -f --preload=ext3 --preload=xenblk --preload=xennet --omit-raid-modules --omit-lvm-modules --omit-scsi-modules /boot/initrd-2.6.18.xenU.img `uname -r` >> >> the VM boots now, but hangs after starting the crond: >> >> [...] >> Press 'I' to enter interactive startup. >> Setting clock : Sun Apr 20 18:15:04 EDT 2008 [ OK ] >> Starting udev: [ OK ] >> Setting hostname myzel: [ OK ] >> No devices found >> Setting up Logical Volume Management: No volume groups found >> [ OK ] >> Checking filesystems >> Checking all file systems. >> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 >> /dev/sda1: clean, 26084/1310720 files, 269769/2621440 blocks >> [ OK ] >> Remounting root filesystem in read-write mode: [ OK ] >> Mounting local filesystems: [ OK ] >> Enabling /etc/fstab swaps: [ OK ] >> INIT: Entering runlevel: 3 >> Entering non-interactive startup >> Bringing up loopback interface: [ OK ] >> Bringing up interface eth0: [ OK ] >> Starting system logger: [ OK ] >> Starting kernel logger: [ OK ] >> Starting sshd: [ OK ] >> Starting crond: [ OK ] >> ... hangs here ... >> >> also, although the network is configured properly, the interface can't >> be pinged. >> >> a "xm shutdown myzel" shuts down the VM properly (vm console shows >> shutdown messages and finally terminates). >> >> do I need to put any additional modules into the initrd ? >> >> tnx in advance. >> >> II> Rainer Fuegenstein wrote: >> >>>> hi, >>>> >>>> I try to get the Centos.5-1.64 image from Jailtime.org running in a >>>> Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the >>>> DomU. I tried both file- and lvm-backed VBDs, but with no luck: >>>> >>>> [...] >>>> Initializing IPsec netlink socket >>>> NET: Registered protocol family 1 >>>> NET: Registered protocol family 17 >>>> XENBUS: Device with no driver: device/vbd/2049 >>>> XENBUS: Device with no driver: device/vbd/2050 >>>> XENBUS: Device with no driver: device/vif/0 >>>> md: Autodetecting RAID arrays. >>>> md: autorun ... >>>> md: ... autorun DONE. >>>> VFS: Cannot open root device "sda1" or unknown-block(0,0) >>>> Please append a correct "root=" boot option >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >>>> >>>> configfile looks like this: >>>> >>>> kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" >>>> memory = 256 >>>> name = "myzel" >>>> vif = [ '' ] >>>> dhcp= "dhcp" >>>> disk = ['phy:vg_virtual/lv_myzel_root,sda1,w', >>>> 'phy:vg_virtual/lv_myzel_swap,sda2,w'] >>>> # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 'tap:aio:/virtual/centos.swap,sda2,w'] >>>> root = "/dev/sda1" >>>> extra = "fastboot" >>>> >>>> (I also tried device name xvda, but to no avail) >>>> >>>> Dom0 kernel: >>>> Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux >>>> >>>> any help appreciated. xend.log excerpt and DomU dmesg follows: >>>> >>>> *** xend.log excerpt: >>>> >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; need 2048; done. >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 18 1.0 >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >>>> [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 vcpus=1 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid = 18 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize = 256 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn = 1 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk = >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus = 1 >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features = >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>>> 'backend': '/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >>>> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>>> 'backend': '/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >>>> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'phy'} to /local/domain/0/backend/vbd/18/2050. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >>>> '/local/domain/0/backend/vif/18/0'} to /local/domain/18/device/vif/0. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >>>> '/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '18'} to /local/domain/0/backend/vif/18/0. >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >>>> 'start_time': '1208719030.67', 'on_poweroff': 'destroy', 'name': 'myzel', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux >>>> (kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '376156', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >>>> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '18', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '374871', 'store/port': '1'} >>>> [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:143) Waiting for devices vif. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:149) Waiting for 0. >>>> [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices usb. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vbd. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2049. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2049/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:149) Waiting for 2050. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/18/2050/hotplug-status. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:490) hotplugStatusCallback 1. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices irq. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vkbd. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vfb. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices pci. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices ioports. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices tap. >>>> [2008-04-20 21:17:11 xend 2627] DEBUG (DevController:143) Waiting for devices vtpm. >>>> [2008-04-20 21:17:11 xend 2627] INFO (XendDomain:370) Domain myzel (18) unpaused. >>>> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=18. >>>> [2008-04-20 21:17:14 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(18) >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >>>> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >>>> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >>>> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >>>> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >>>> 0.15769001999999999], ['online_vcpus', 1], ['up_t! >>>> ime', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]]) >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:306) parseConfig: config is ['domain', ['domid', 18], ['uuid', '8772f05d-7d2b-fd71-dbcb-cfef1870e83c'], ['vcpus', 1], >>>> ['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], ['maxmem', 256], ['features', ''], ['name', 'myzel'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], >>>> ['on_crash', 'restart'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']]], ['device', ['vif', >>>> ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]], ['device', ['vbd', ['backend', 0], ['dev', 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]], >>>> ['device', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']]], ['state', '----c-'], ['shutdown_reason', 'crash'], ['cpu_time', >>>> 0.15769001999999999], ['online_vcpus', 1], ['up_! >>>> time', '4.2952029705'], ['start_time', '1208719030.67'], ['store_mfn', 374871], ['console_mfn', 376156]] >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:411) parseConfig: result is {'shadow_memory': 0, 'start_time': 1208719030.6700001, 'uuid': >>>> '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-53.1.14.el5xen'], ['ip', >>>> ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1'], ['args', 'fastboot']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'myzel', 'backend': [], 'vcpus': 1, 'cpu_weight': >>>> 1.0, 'features': '', 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'], ['mac', '00:16:3e:31:5d:55']]), ('vbd', ['vbd', ['backend', 0], ['dev', >>>> 'sda1:disk'], ['uname', 'phy:vg_virtual/lv_myzel_root'], ['mode', 'w']]), ('vbd', ['vbd', ['backend', 0], ['dev', 'sda2:disk'], ['uname', 'phy:vg_virtual/lv_myzel_swap'], ['mode', 'w']])], >>>> 'bootloader': None, 'cpu': None, 'maxmem': 256} >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) XendDomainInfo.construct: None >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 88748 KiB free; need 2048; done. >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) XendDomainInfo.initDomain: 19 1.0 >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:133) Balloon: 100276 KiB free; 162460 to scrub; need 262144; retries: 20. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:141) Balloon: waiting on scrubbing >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; need 262144; done. >>>> [2008-04-20 21:17:15 xend 2627] INFO (image:136) buildDomain os=linux dom=19 vcpus=1 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:201) domid = 19 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:202) memsize = 256 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:203) image = /boot/vmlinuz-2.6.18-53.1.14.el5xen >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:204) store_evtchn = 1 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:205) console_evtchn = 2 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:206) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:207) ramdisk = >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:208) vcpus = 1 >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (image:209) features = >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': >>>> '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >>>> '/local/domain/19/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>>> 'backend': '/local/domain/0/backend/vbd/19/2049'} to /local/domain/19/device/vbd/2049. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': >>>> 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2049. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:110) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', >>>> 'backend': '/local/domain/0/backend/vbd/19/2050'} to /local/domain/19/device/vbd/2050. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:112) DevController: writing {'domain': 'myzel', 'frontend': '/local/domain/19/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': >>>> 'vg_virtual/lv_myzel_swap', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'phy'} to /local/domain/0/backend/vbd/19/2050. >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_memory': '0', 'uuid': '8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', >>>> 'start_time': '1208719035.65', 'on_poweroff': 'destroy', 'name': 'myzel', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': '(linux (kernel >>>> /boot/vmlinuz-2.6.18-53.1.14.el5xen) (ip :1.2.3.4::::eth0:dhcp) (root /dev/sda1) (args fastboot))', 'maxmem': '256'} >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '368494', 'console/port': '2', 'name': 'myzel', 'console/limit': '1048576', >>>> 'vm': '/vm/8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '370229', 'store/port': '1'} >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>>> [2008-04-20 21:17:15 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>>> [2008-04-20 21:17:15 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch >>>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] WARNING (XendDomainInfo:923) Domain has crashed: name=myzel id=19. >>>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] ERROR (XendDomainInfo:1825) VM myzel restarting too fast (4.333381 seconds since the last restart). Refusing to restart to avoid loops. >>>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=19 >>>> [2008-04-20 21:17:19 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(19) >>>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. >>>> [2008-04-20 21:17:19 xend 2627] DEBUG (DevController:476) hotplugStatusCallback /local/domain/0/backend/vbd/5/2049/hotplug-status. >>>> >>>> >>>> >>>> *** DomU dmesg: >>>> [root at xenserv xen]# xm create -c myzel.cfg >>>> Using config file "/etc/xen/myzel.cfg". >>>> Started domain myzel >>>> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >>>> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >>>> BIOS-provided physical RAM map: >>>> Xen: 0000000000000000 - 0000000010800000 (usable) >>>> No mptable found. >>>> Built 1 zonelists. Total pages: 67584 >>>> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>>> Initializing CPU#0 >>>> PID hash table entries: 2048 (order: 11, 16384 bytes) >>>> Xen reported: 2666.982 MHz processor. >>>> Console: colour dummy device 80x25 >>>> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >>>> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >>>> Software IO TLB disabled >>>> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >>>> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >>>> Security Framework v1.0.0 initialized >>>> SELinux: Initializing. >>>> selinux_register_security: Registering secondary module capability >>>> Capability LSM initialized as secondary >>>> Mount-cache hash table entries: 256 >>>> CPU: Trace cache: 12K uops, L1 D cache: 16K >>>> CPU: L2 cache: 1024K >>>> CPU: Physical Processor ID: 0 >>>> CPU: Processor Core ID: 1 >>>> (SMP-)alternatives turned off >>>> Brought up 1 CPUs >>>> Grant table initialized >>>> NET: Registered protocol family 16 >>>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>>> Brought up 1 CPUs >>>> PCI: setting up Xen PCI frontend stub >>>> ACPI: Interpreter disabled. >>>> Linux Plug and Play Support v0.97 (c) Adam Belay >>>> pnp: PnP ACPI: disabled >>>> xen_mem: Initialising balloon driver. >>>> usbcore: registered new driver usbfs >>>> usbcore: registered new driver hub >>>> PCI: System does not support PCI >>>> PCI: System does not support PCI >>>> NetLabel: Initializing >>>> NetLabel: domain hash size = 128 >>>> NetLabel: protocols = UNLABELED CIPSOv4 >>>> NetLabel: unlabeled traffic allowed by default >>>> NET: Registered protocol family 2 >>>> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >>>> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >>>> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >>>> TCP: Hash tables configured (established 16384 bind 8192) >>>> TCP reno registered >>>> audit: initializing netlink socket (disabled) >>>> audit(1208718852.478:1): initialized >>>> VFS: Disk quotas dquot_6.5.1 >>>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>>> Initializing Cryptographic API >>>> ksign: Installing public key data >>>> Loading keyring >>>> - Added public key F8170EB5CF71EF90 >>>> - User ID: CentOS (Kernel Module GPG key) >>>> io scheduler noop registered >>>> io scheduler anticipatory registered >>>> io scheduler deadline registered >>>> io scheduler cfq registered (default) >>>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >>>> rtc: IRQ 8 is not free. >>>> Non-volatile memory driver v1.2 >>>> Linux agpgart interface v0.101 (c) Dave Jones >>>> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >>>> Xen virtual console successfully installed as xvc0 >>>> Bootdata ok (command line is ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot) >>>> Linux version 2.6.18-53.1.14.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008 >>>> BIOS-provided physical RAM map: >>>> Xen: 0000000000000000 - 0000000010800000 (usable) >>>> No mptable found. >>>> Built 1 zonelists. Total pages: 67584 >>>> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 fastboot >>>> Initializing CPU#0 >>>> PID hash table entries: 2048 (order: 11, 16384 bytes) >>>> Xen reported: 2666.982 MHz processor. >>>> Console: colour dummy device 80x25 >>>> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >>>> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >>>> Software IO TLB disabled >>>> Memory: 251120k/270336k available (2358k kernel code, 10680k reserved, 1325k data, 172k init) >>>> Calibrating delay using timer specific routine.. 6671.50 BogoMIPS (lpj=13343016) >>>> Security Framework v1.0.0 initialized >>>> SELinux: Initializing. >>>> selinux_register_security: Registering secondary module capability >>>> Capability LSM initialized as secondary >>>> Mount-cache hash table entries: 256 >>>> CPU: Trace cache: 12K uops, L1 D cache: 16K >>>> CPU: L2 cache: 1024K >>>> CPU: Physical Processor ID: 0 >>>> CPU: Processor Core ID: 1 >>>> (SMP-)alternatives turned off >>>> Brought up 1 CPUs >>>> Grant table initialized >>>> NET: Registered protocol family 16 >>>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 267A0 could not acquire Mutex [2] [20060707] >>>> Brought up 1 CPUs >>>> PCI: setting up Xen PCI frontend stub >>>> ACPI: Interpreter disabled. >>>> Linux Plug and Play Support v0.97 (c) Adam Belay >>>> pnp: PnP ACPI: disabled >>>> xen_mem: Initialising balloon driver. >>>> usbcore: registered new driver usbfs >>>> usbcore: registered new driver hub >>>> PCI: System does not support PCI >>>> PCI: System does not support PCI >>>> NetLabel: Initializing >>>> NetLabel: domain hash size = 128 >>>> NetLabel: protocols = UNLABELED CIPSOv4 >>>> NetLabel: unlabeled traffic allowed by default >>>> NET: Registered protocol family 2 >>>> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >>>> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >>>> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >>>> TCP: Hash tables configured (established 16384 bind 8192) >>>> TCP reno registered >>>> audit: initializing netlink socket (disabled) >>>> audit(1208718852.478:1): initialized >>>> VFS: Disk quotas dquot_6.5.1 >>>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>>> Initializing Cryptographic API >>>> ksign: Installing public key data >>>> Loading keyring >>>> - Added public key F8170EB5CF71EF90 >>>> - User ID: CentOS (Kernel Module GPG key) >>>> io scheduler noop registered >>>> io scheduler anticipatory registered >>>> io scheduler deadline registered >>>> io scheduler cfq registered (default) >>>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >>>> rtc: IRQ 8 is not free. >>>> Non-volatile memory driver v1.2 >>>> Linux agpgart interface v0.101 (c) Dave Jones >>>> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >>>> Xen virtual console successfully installed as xvc0 >>>> Event-channel device installed. >>>> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >>>> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx >>>> ide-floppy driver 0.99.newide >>>> usbcore: registered new driver hiddev >>>> usbcore: registered new driver usbhid >>>> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >>>> PNP: No PS/2 controller found. Probing ports directly. >>>> i8042.c: No controller found. >>>> mice: PS/2 mouse device common for all mice >>>> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >>>> md: bitmap version 4.39 >>>> TCP bic registered >>>> Initializing IPsec netlink socket >>>> NET: Registered protocol family 1 >>>> NET: Registered protocol family 17 >>>> XENBUS: Device with no driver: device/vbd/2049 >>>> XENBUS: Device with no driver: device/vbd/2050 >>>> XENBUS: Device with no driver: device/vif/0 >>>> md: Autodetecting RAID arrays. >>>> md: autorun ... >>>> md: ... autorun DONE. >>>> VFS: Cannot open root device "sda1" or unknown-block(0,0) >>>> Please append a correct "root=" boot option >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >>>> >>>> -- >>>> Fedora-xen mailing list >>>> Fedora-xen at redhat.com >>>> https://www.redhat.com/mailman/listinfo/fedora-xen >>>> >>>> >>>> >>>> >> >> >> >> >> ------------------------------------------------------------------------------ >> Rainer Fuegenstein rfu at kaneda.iguw.tuwien.ac.at >> ------------------------------------------------------------------------------ >> "Why are you looking into the darkness and not into the fire as we do ?", Nell >> asked. "Because the darkness is where danger comes from," Peter said, "and >> from the fire comes only illusion". (from "The Diamond Age") >> ------------------------------------------------------------------------------ >> >> >> >> ------------------------------------------------------------------------------ Rainer Fuegenstein rfu at kaneda.iguw.tuwien.ac.at ------------------------------------------------------------------------------ "Why are you looking into the darkness and not into the fire as we do ?", Nell asked. "Because the darkness is where danger comes from," Peter said, "and from the fire comes only illusion". (from "The Diamond Age") ------------------------------------------------------------------------------ From itamar at ispbrasil.com.br Mon Apr 21 00:25:25 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 20 Apr 2008 21:25:25 -0300 Subject: [Fedora-xen] no sda1 in DomU In-Reply-To: <1979874587.20080421015223@kaneda.iguw.tuwien.ac.at> References: <846731579.20080420211948@kaneda.iguw.tuwien.ac.at> <480B9915.40702@ispbrasil.com.br> <4510644480.20080421002005@kaneda.iguw.tuwien.ac.at> <480BC57B.4060208@ispbrasil.com.br> <1979874587.20080421015223@kaneda.iguw.tuwien.ac.at> Message-ID: <480BDEF5.2030103@ispbrasil.com.br> add this line to your domU config and try again extra = "ro selinux=0 3 console=/dev/xvc0 " the trick is the console=/dev/xvc0 From orenault at redhat.com Mon Apr 21 16:47:58 2008 From: orenault at redhat.com (Olivier Renault) Date: Mon, 21 Apr 2008 18:47:58 +0200 Subject: [Fedora-xen] Upgrading a Xen guest In-Reply-To: References: Message-ID: <480CC53E.5000807@redhat.com> John Swartzentruber wrote: > I hope I am using correct terminology for this question. I'm a home user > who is using Xen in a small way, but want to ramp up my usage over time. > > I have a Fedora 7 host server. On this computer, I installed two Fedora > 8 virtual servers using virt-install. What I can't find the answer to, > is how to upgrade these virtual computers from Fedora 8 to Fedora 9 when > Fedora 9 is released. On my physical server, I normally create an > installation DVD, then boot from that. Anaconda then takes care of > appropriately upgrading the system and generally does a very good job of > it. > > So how will I do the equivalent for a virtual computer? I don't know how > to virtually put the virtual DVD in the virtual DVD drive and reboot the > virtual computer. I know I've read of ways to upgrade using Yum, which I > assume would work, but I'd prefer to upgrade using Anaconda because that > seems like a much safer approach. Because my two current virtual > computers are not used for much yet, I could start from scratch, but in > the future that isn't going to be the way I will want to handle the > upgrades. > > Thanks for your help. I've read the FedoraProject.org wiki docs, but if > there are references I missed, please feel free to point me to them. > Grab the fedora-release package from the F9 repository, install it on your VM and you can then simply run # yum upgrade You may want to double check if xen in F7 ( Dom0 ) / F9 ( domU ) are compatible. Good luck, Olivier From davidl at matissenetworks.com Mon Apr 21 23:05:40 2008 From: davidl at matissenetworks.com (David Levinger) Date: Mon, 21 Apr 2008 16:05:40 -0700 (PDT) Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM In-Reply-To: <1208715099.7117.7.camel@aic-desktop.cathrow.org> References: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO> <1208715099.7117.7.camel@aic-desktop.cathrow.org> Message-ID: <00a701c8a404$2fffd920$a564a8c0@nbdavidl> You were 100% correct Andrew. The problem was with how I configured XP, though I seriously thought I knew better. I sysprepped my image and redid it with the "multi-processor" hal and voila I now see and utilize both cores. The odd part, however, is that the time required to complete a processor intensive operation seems to remain almost the same. Instead of using 50% of the available host CPU it now using 100% but estimates only a tem minute savings in processing time. Whaaaaat? I still feel like I'm missing something rather important, but at least both CPUs are now available for use. d _____ From: Andrew Cathrow [mailto:acathrow at redhat.com] Sent: Sunday, April 20, 2008 11:12 AM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Unable to use multiple CPUs inside an HVM When Windows installed selects the HAL library appropriate the the hardware. If you install on a single CPU system then the uniprocessor HAL is installed. If you then add a second vcpu to the guest then the windows HAL won't see it. You'll need to replace Window's hal. See links below for some background. I don't think there is a Microsoft *supported* way to do this but I've done this a number of times without issue on XP and 2000, but I've not tried this on 2003, 2008 or Vista http://support.microsoft.com/kb/309283/en-us http://support.microsoft.com/default.aspx?scid=kb;EN-US;237556 On Sat, 2008-04-19 at 10:40 -0700, David Levinger wrote: Hey Guys, I have a fully virtualized XP guest that is set to have 2 VCPUs and in the guest I see 2 CPUs but when it is under heavy load it only utilizes 1 of the physical cores. Both xm and virsh show that the guest only has 1 CPU, but my config file and the guest show it should have 2. What am I missing? How can I get this guest to have access to both cores? Thanks! David -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott-forum at scottkate.com Tue Apr 22 00:26:50 2008 From: scott-forum at scottkate.com (bcrawfo2) Date: Mon, 21 Apr 2008 17:26:50 -0700 (PDT) Subject: [Fedora-xen] Serial console as well as serial access for apps Message-ID: <16819063.post@talk.nabble.com> I have 2.6.18-53.1.14.el5xen on a box with an on-board serial port I want to use for console access to my dom0. I also have a 4 port serial card I want to use on the dom0 as well. I can configure one or the other...access to the console, or access to the 4 port serials. I can't figure out how to do both. When I get console to work, dmesg | grep ttyS only shows it binding to the virtual console...no others. I do use domUs, but don't have a direct need for serials there. I could, if I had to...move the serial apps over to a domU, but that would be un-ideal. Any help would be appreciated. Thanks Scott -- View this message in context: http://www.nabble.com/Serial-console-as-well-as-serial-access-for-apps-tp16819063p16819063.html Sent from the Fedora Xen mailing list archive at Nabble.com. From armbru at redhat.com Tue Apr 22 08:57:31 2008 From: armbru at redhat.com (Markus Armbruster) Date: Tue, 22 Apr 2008 10:57:31 +0200 Subject: [Fedora-xen] Serial console as well as serial access for apps In-Reply-To: <16819063.post@talk.nabble.com> (bcrawfo2's message of "Mon\, 21 Apr 2008 17\:26\:50 -0700 \(PDT\)") References: <16819063.post@talk.nabble.com> Message-ID: <87od82tgg4.fsf@pike.pond.sub.org> bcrawfo2 writes: > I have 2.6.18-53.1.14.el5xen on a box with an on-board serial port I want to > use for console access to my dom0. I also have a 4 port serial card I want > to use on the dom0 as well. I can configure one or the other...access to > the console, or access to the 4 port serials. I can't figure out how to do > both. > When I get console to work, dmesg | grep ttyS only shows it binding to the > virtual console...no others. You didn't tell us what exactly you did and how exactly it went wrong. [...] From davidl at matissenetworks.com Tue Apr 22 17:03:08 2008 From: davidl at matissenetworks.com (David Levinger) Date: Tue, 22 Apr 2008 10:03:08 -0700 (PDT) Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM In-Reply-To: <00a701c8a404$2fffd920$a564a8c0@nbdavidl> References: <2dcd01c8a27f$23a8caf0$2d01a8c0@TILLO><1208715099.7117.7.camel@aic-desktop.cathrow.org> <00a701c8a404$2fffd920$a564a8c0@nbdavidl> Message-ID: <00e901c8a49a$b46fe510$a564a8c0@nbdavidl> To add a couple more data points to this, if I look in virt-manager it shows at 97-99% CPU usage, but if I look at the virsh vcpuinfo domain then it shows that only one processor seems to be doing anything at a time. IE one will show blocked and the other running, or one will show offline and the other running and sometimes running and "no state". Considering the rather poor performance I'm assuming that I'm really only utilizing one at a time. Any thoughts? d _____ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of David Levinger Sent: Monday, April 21, 2008 4:06 PM To: acathrow at redhat.com Cc: fedora-xen at redhat.com Subject: RE: [Fedora-xen] Unable to use multiple CPUs inside an HVM You were 100% correct Andrew. The problem was with how I configured XP, though I seriously thought I knew better. I sysprepped my image and redid it with the "multi-processor" hal and voila I now see and utilize both cores. The odd part, however, is that the time required to complete a processor intensive operation seems to remain almost the same. Instead of using 50% of the available host CPU it now using 100% but estimates only a tem minute savings in processing time. Whaaaaat? I still feel like I'm missing something rather important, but at least both CPUs are now available for use. d _____ From: Andrew Cathrow [mailto:acathrow at redhat.com] Sent: Sunday, April 20, 2008 11:12 AM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Unable to use multiple CPUs inside an HVM When Windows installed selects the HAL library appropriate the the hardware. If you install on a single CPU system then the uniprocessor HAL is installed. If you then add a second vcpu to the guest then the windows HAL won't see it. You'll need to replace Window's hal. See links below for some background. I don't think there is a Microsoft *supported* way to do this but I've done this a number of times without issue on XP and 2000, but I've not tried this on 2003, 2008 or Vista http://support.microsoft.com/kb/309283/en-us http://support.microsoft.com/default.aspx?scid=kb;EN-US;237556 On Sat, 2008-04-19 at 10:40 -0700, David Levinger wrote: Hey Guys, I have a fully virtualized XP guest that is set to have 2 VCPUs and in the guest I see 2 CPUs but when it is under heavy load it only utilizes 1 of the physical cores. Both xm and virsh show that the guest only has 1 CPU, but my config file and the guest show it should have 2. What am I missing? How can I get this guest to have access to both cores? Thanks! David -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From swethu_bandaru at yahoo.com Wed Apr 23 05:24:19 2008 From: swethu_bandaru at yahoo.com (swethu bandaru) Date: Tue, 22 Apr 2008 22:24:19 -0700 (PDT) Subject: [Fedora-xen] xen booting problem Message-ID: <366933.44166.qm@web36205.mail.mud.yahoo.com> While booting XEN I amgetting an eror saying Kernel panic - not syncing:attempted to kill init! I am not getting what is the problem I am using FC6 OS Can any one please suggest me Thank you --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From armbru at redhat.com Wed Apr 23 07:06:34 2008 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 23 Apr 2008 09:06:34 +0200 Subject: [Fedora-xen] xen booting problem In-Reply-To: <366933.44166.qm@web36205.mail.mud.yahoo.com> (swethu bandaru's message of "Tue\, 22 Apr 2008 22\:24\:19 -0700 \(PDT\)") References: <366933.44166.qm@web36205.mail.mud.yahoo.com> Message-ID: <87hcdtnj7p.fsf@pike.pond.sub.org> swethu bandaru writes: > While booting XEN I amgetting an eror saying > Kernel panic - not syncing:attempted to kill init! > I am not getting what is the problem Most likely, the interesting error message is further up. Try giving us more context. > I am using FC6 OS > Can any one please suggest me > Thank you FC-6 is no longer supported. You might be better off upgrading to something that is. From rjones at redhat.com Wed Apr 23 12:10:40 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 23 Apr 2008 13:10:40 +0100 Subject: [Fedora-xen] Unable to use multiple CPUs inside an HVM In-Reply-To: <00e901c8a49a$b46fe510$a564a8c0@nbdavidl> References: <00a701c8a404$2fffd920$a564a8c0@nbdavidl> <00e901c8a49a$b46fe510$a564a8c0@nbdavidl> Message-ID: <20080423121039.GA2486@amd.home.annexia.org> On Tue, Apr 22, 2008 at 10:03:08AM -0700, David Levinger wrote: > To add a couple more data points to this, if I look in virt-manager it > shows at 97-99% CPU usage, but if I look at the virsh vcpuinfo domain then > it shows that only one processor seems to be doing anything at a time. > > IE one will show blocked and the other running, or one will show offline > and the other running and sometimes running and "no state". Considering > the rather poor performance I'm assuming that I'm really only utilizing > one at a time. Any thoughts? Use virt-top. It's able to tell you which physical CPUs are being utilized. You can also try using virsh vcpupin to pin virtual CPUs to physical CPUs in case there's some contention (but use virt-top first to find out). Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From orion at cora.nwra.com Wed Apr 23 21:30:00 2008 From: orion at cora.nwra.com (Orion Poplawski) Date: Wed, 23 Apr 2008 15:30:00 -0600 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] In-Reply-To: <1208504522.3464.4.camel@muff> References: <1208504522.3464.4.camel@muff> Message-ID: <480FAA58.5040705@cora.nwra.com> Mark McLoughlin wrote: > Hey, > There doesn't appear to be any install trees yet for the F9 Preview > release, but please do try and run F9 rawhide in your Xen DomU (both > i686 and x86_64) and help us flush out any remaining issues in the lead > up to the final release. > > The current blocker list looks like: > > https://bugzilla.redhat.com/showdependencytree.cgi?id=434756&hide_resolved=1 > Installing x86_64 on F8 x86_64 host, I'm hung at "installing bootloader". -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com From markmc at redhat.com Thu Apr 24 15:39:41 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 24 Apr 2008 16:39:41 +0100 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] In-Reply-To: <480FAA58.5040705@cora.nwra.com> References: <1208504522.3464.4.camel@muff> <480FAA58.5040705@cora.nwra.com> Message-ID: <1209051581.25146.5.camel@muff> Hi, On Wed, 2008-04-23 at 15:30 -0600, Orion Poplawski wrote: > Mark McLoughlin wrote: > > Hey, > > There doesn't appear to be any install trees yet for the F9 Preview > > release, but please do try and run F9 rawhide in your Xen DomU (both > > i686 and x86_64) and help us flush out any remaining issues in the lead > > up to the final release. > > > > The current blocker list looks like: > > > > https://bugzilla.redhat.com/showdependencytree.cgi?id=434756&hide_resolved=1 > > > > Installing x86_64 on F8 x86_64 host, I'm hung at "installing bootloader". Yep, that's this one: https://bugzilla.redhat.com/442685 Basically, the x86_64 kernel-xen doesn't currently have support for running 32 binaries, so grub-install fails at the very end of the install and anaconda hangs. If you just reboot the guest at that point, all is well since pygrub doesn't actually need grub-install to have been run. It's on F9Blocker and hopefully we'll fix it either with an ugly, temporary hack in anaconda or by getting ia32 support into kernel-xen.x86_64. (You wouldn't have seen the bug looking at PvOpsTracker because I moved PvOpsTracker from F9Blocker to F9Tracker and moved #442685 from PvOpsTracker to F9Blocker) Cheers, Mark. From orion at cora.nwra.com Thu Apr 24 16:35:10 2008 From: orion at cora.nwra.com (Orion Poplawski) Date: Thu, 24 Apr 2008 10:35:10 -0600 Subject: [Fedora-xen] [Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!] In-Reply-To: <1209051581.25146.5.camel@muff> References: <1208504522.3464.4.camel@muff> <480FAA58.5040705@cora.nwra.com> <1209051581.25146.5.camel@muff> Message-ID: <4810B6BE.5080407@cora.nwra.com> Mark McLoughlin wrote: > Hi, > > On Wed, 2008-04-23 at 15:30 -0600, Orion Poplawski wrote: >> Installing x86_64 on F8 x86_64 host, I'm hung at "installing bootloader". > > Yep, that's this one: > > https://bugzilla.redhat.com/442685 > > Basically, the x86_64 kernel-xen doesn't currently have support for > running 32 binaries, so grub-install fails at the very end of the > install and anaconda hangs. > > If you just reboot the guest at that point, all is well since pygrub > doesn't actually need grub-install to have been run. Okay, that got it up. Unfortunately it crashes before my kickstart %post script could run, but that can be done by hand. Thanks for the info. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com From tmblue at gmail.com Tue Apr 29 21:33:44 2008 From: tmblue at gmail.com (tmblue at gmail.com) Date: Tue, 29 Apr 2008 14:33:44 -0700 Subject: [Fedora-xen] Xen 3.x FC6 paravirt no issues, trying to create guest with full virt, problem Message-ID: <18574212.182501209504824090.JavaMail.nabble@isper.nabble.com> If I do a install using -p things work great, no issues, have 8+ virtuals created around using para and even on my fully virtual enabled server, I can create a guest without issue using paravirtual. If i do the same install but use the config switch -v (full virtualization) the install dumps me back saying i can reconnect but I can't. Attempted creation: [root at devxen xen]# /usr/bin/virt-install --debug -n trub -r 1000 -m 00:16:3e:41:71:d1 --nographics --os-type=linux --os-variant=fedora6 -l /virtual.img -f /dev/mapper/dev-trub --noapic --noacpi --arch=i686 Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. y Tue, 29 Apr 2008 14:25:34 DEBUG Path is block file: Assuming Block disk type. Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Tue, 29 Apr 2008 14:25:35 DEBUG Creating guest from ' trub 1024000 1024000 dd0a4cef-ce10-b268-fa3f-5e44e4ac346c hvm /usr/lib/xen/boot/hvmloader destroy destroy destroy 1 /usr/lib/xen/bin/qemu-dm ' Creating domain... 0 B 00:01 Tue, 29 Apr 2008 14:25:36 DEBUG Created guest, looking to see if it is running Tue, 29 Apr 2008 14:25:36 DEBUG Launching console callback Tue, 29 Apr 2008 14:25:36 DEBUG Saving XML boot config ' trub 1024000 1024000 dd0a4cef-ce10-b268-fa3f-5e44e4ac346c hvm /usr/lib/xen/boot/hvmloader destroy restart restart 1 /usr/lib/xen/bin/qemu-dm ' Domain installation still in progress. You can reconnect to the console to complete the installation process. [root at devxen xen]# virsh connect trub libvir: error : could not connect to trub error: Failed to connect to the hypervisor [root at devxen xen]# virsh list Id Name State ---------------------------------- 0 Domain-0 running 4 trub no state I can't connect or console or anything and I'm only using console access, ssh, serial, no graphical stuff at all. I must be missing something, just strange. don't see anything in logs, and my remote install is showing that it's getting to installing some boel binaries and nothing else. What's so different about paravirt and fullvirt? Thanks Tory