From jtatpbl at gmail.com Fri Feb 1 03:12:23 2008 From: jtatpbl at gmail.com (JimmyT _) Date: Thu, 31 Jan 2008 19:12:23 -0800 Subject: [Fedora-xen] "Invalid kernel" error on PV creation -- what's invalid? Message-ID: I don't know if this is a Fedora, Xen, Cobbler/Koan or local config problem. Or some combination. I'm using cobbler+koan to create a PV VM. hostOS = Fedora 8, guestOS = Fedora 8. On attempt to create the PV, it chokes at (console error) "Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')" I see the same in /var/log/xen/xend.log (detailed tail, below), so I suspect it's a problem with xen. The vmlinuz & initrd.img I'm using, by reference in 'cobbler distro ...' invocation are pulled from http://mirrors.kernel.org/fedora/releases/8/Fedora/x86_64/os/images/xen/, so I'm not clear what's "Invalid" about the kernel. Any suggestions? Jimmy [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name', 'f8TEST'], ['memory', '1024'], ['maxmem', '1024'], ['vcpus', '2'], ['uuid', '30a76e12-53ef-dfb7-7acb-1aaf3fdfccff'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/vmlinuz'], ['ramdisk', '/var/lib/xen/initrd.img'], ['args', 'ks= http://10.0.0.100/cblr/kickstarts/f8TEST/ks.cfg ksdevice=eth0 lang= kssendmac syslog=10.0.0.100:25150 text ']]], ['device', ['vbd', ['dev', 'xvda'], ['uname', 'phy:/dev/VG01/f8TEST'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:15:3f:2d:68:d5'], ['bridge', 'eth0']]]]) [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1555) XendDomainInfo.constructDomain [2008-01-31 18:21:13 2438] DEBUG (balloon:116) Balloon: 6596932 KiB free; need 2048; done. [2008-01-31 18:21:13 2438] DEBUG (XendDomain:443) Adding Domain: 22 [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1609) XendDomainInfo.initDomain: 22 256 [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1640) _initDomain:shadow_memory=0x0, memory_static_max=0x40000000, memory_static_min=0x0. [2008-01-31 18:21:13 2438] DEBUG (balloon:116) Balloon: 6596924 KiB free; need 1048576; done. [2008-01-31 18:21:13 2438] INFO (image:129) buildDomain os=linux dom=22 vcpus=2 [2008-01-31 18:21:13 2438] DEBUG (image:198) domid = 22 [2008-01-31 18:21:13 2438] DEBUG (image:199) memsize = 1024 [2008-01-31 18:21:13 2438] DEBUG (image:200) image = /var/lib/xen/vmlinuz [2008-01-31 18:21:13 2438] DEBUG (image:201) store_evtchn = 1 [2008-01-31 18:21:13 2438] DEBUG (image:202) console_evtchn = 2 [2008-01-31 18:21:13 2438] DEBUG (image:203) cmdline = ks= http://10.0.0.100/cblr/kickstarts/f8TEST/ks.cfg ksdevice=eth0 lang= kssendmac syslog=10.0.0.100:25150 text [2008-01-31 18:21:13 2438] DEBUG (image:204) ramdisk = /var/lib/xen/initrd.img [2008-01-31 18:21:13 2438] DEBUG (image:205) vcpus = 2 [2008-01-31 18:21:13 2438] DEBUG (image:206) features = [2008-01-31 18:21:13 2438] ERROR (XendDomainInfo:1682) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1657, in _initDomain channel_details = self.image.createImage() File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 112, in createImage return self.createDomain() File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 131, in createDomain result = self.buildDomain() File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 530, in buildDomain return LinuxImageHandler.buildDomain(self) File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 215, in buildDomain features = self.vm.getFeatures()) Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') [2008-01-31 18:21:13 2438] ERROR (XendDomainInfo:424) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 404, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1685, in _initDomain raise VmError(str(exn)) VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=22 [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1821) XendDomainInfo.destroyDomain(22) [2008-01-31 18:21:13 2438] ERROR (XendDomainInfo:89) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 87, in create vm.start() File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 404, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1685, in _initDomain raise VmError(str(exn)) VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=22 [2008-01-31 18:21:13 2438] DEBUG (XendDomainInfo:1821) XendDomainInfo.destroyDomain(22) [2008-01-31 18:21:13 2438] ERROR (XendDomainInfo:1832) XendDomainInfo.destroy: xc.domain_destroy failed. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1827, in destroyDomain xc.domain_destroy(self.domid) Error: (3, 'No such process') [2008-01-31 18:21:13 2438] ERROR (SrvBase:88) Request create failed. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 82, in op_create raise XendError("Error creating domain: " + str(ex)) XendError: Error creating domain: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n') -------------- next part -------------- An HTML attachment was scrubbed... URL: From jtatpbl at gmail.com Fri Feb 1 05:56:32 2008 From: jtatpbl at gmail.com (JimmyT _) Date: Thu, 31 Jan 2008 21:56:32 -0800 Subject: [Fedora-xen] Re: "Invalid kernel" error on PV creation -- what's invalid? In-Reply-To: References: Message-ID: Digging around for instances of the "no loader found" error, I found in /var/log/xen/domain-builder-ng.log xc_dom_allocate: cmdline="ks= http://10.0.0.100/cblr/kickstarts/f8_min_pv/ks.cfg ksdevice=eth0 lang= kssendmac syslog=10.0.0.100:25150 text ", features="" xc_dom_kernel_file: filename="/var/lib/xen/vmlinuz" xc_dom_ramdisk_file: filename="/var/lib/xen/initrd.img" xc_dom_boot_xen_init: ver 3.1, 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 xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found xc_dom_release: called checking for the loaders in /var/lib/cobbler/settings, --- bootloaders: ia64: /var/lib/cobbler/elilo-3.6-ia64.efi standard: /usr/lib/syslinux/pxelinux.0 ... they do exist: ls -al /var/lib/cobbler/elilo-3.6-ia64.efi /usr/lib/syslinux/pxelinux.0 -rw-r--r-- 1 root root 13408 2007-10-17 08:53 /usr/lib/syslinux/pxelinux.0 -rw-rw-r-- 1 root root 374146 2008-01-31 15:04 /var/lib/cobbler/elilo- 3.6-ia64.efi Not clear why the "xc_dom_find_loader" calls for finding the loader "failed", unless they're the wrong loader type. -------------- next part -------------- An HTML attachment was scrubbed... URL: From huubvanniekerk at gmail.com Fri Feb 1 20:04:06 2008 From: huubvanniekerk at gmail.com (Huub) Date: Fri, 01 Feb 2008 21:04:06 +0100 Subject: [Fedora-xen] no xend on f8 x64 Message-ID: Hi, On my AMD64, running F8, I just installed the virtualization package with yum and rebooted into the Xen kernel. But I can't create a new virtual machine. I read that the xend daemon should be running for that, but I can't find it. Should it be installed or how should I do that? Thanks. From jtatpbl at gmail.com Sat Feb 2 17:35:44 2008 From: jtatpbl at gmail.com (JimmyT _) Date: Sat, 2 Feb 2008 09:35:44 -0800 Subject: [Fedora-xen] [resolved] Re: "Invalid kernel" error on PV creation -- what's invalid? In-Reply-To: References: Message-ID: To close the loop, this problem turns out to be a cobbler/koan issue. the kernel really IS invalid. with the help of "high_roller" in #rhel, i found that koan's pulling the vmlinuz kernel from the cobbler server over an http:// connection -- rather than an apparently required https:// -- and loading the resultant error-page html INTO the vmlinuz file used to (attempt to) create the PV. i.e., the pull occurs as expected, no error about the pull is launched, but the process populates the target DL with error code. of course, this results in the 'kernel', now populated with garbage, being identified as "invalid". since i'd checked my source files, and as i read the logs to imply the pull was happening without error, I simply didn't look at what actually WAS pulled. i'll communicate with the cobbler/koan author to iron this out. hope someone else finds this helpful. jimmy From fcxen at itsbeen.sent.com Sat Feb 2 20:48:20 2008 From: fcxen at itsbeen.sent.com (fc xen list) Date: Sat, 02 Feb 2008 12:48:20 -0800 Subject: [Fedora-xen] what steps are required to manually move a PV domU from one machine to another? Message-ID: <47A4D714.5060709@itsbeen.sent.com> Hi, I am having a problem - I created a lovely bunch of F8 x86_64 domUs and I want to create a vast clone army of them using different dom0s. The problem is, I do: fm # virt-install c1 (no graphics) fm # xm start c1 fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] fm # scp -p c1.img othermachine:/var/lib/xen/images then: om1 # virsh define c1.xml om1 # xm start c1 and hangville, if I do: om1 # xmstart c1 -c it seems to hang just after the grub boot menu. I assume I am "doing it wrong" but this worked great in the past. I've been selling F8/Xen as the answer to all problems, any help would be appreciated. VMWare looms like a line of dark clouds on the horizon... Thanks. From berrange at redhat.com Sat Feb 2 20:57:58 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 2 Feb 2008 20:57:58 +0000 Subject: [Fedora-xen] what steps are required to manually move a PV domU from one machine to another? In-Reply-To: <47A4D714.5060709@itsbeen.sent.com> References: <47A4D714.5060709@itsbeen.sent.com> Message-ID: <20080202205758.GB8276@redhat.com> On Sat, Feb 02, 2008 at 12:48:20PM -0800, fc xen list wrote: > Hi, > > I am having a problem - I created a lovely bunch of F8 x86_64 domUs and I > want to create a vast clone army of them using different dom0s. The problem > is, I do: > > fm # virt-install c1 (no graphics) > fm # xm start c1 > fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] Welcome to the world of massive data corruption if you copy the disk without shutting down. > fm # scp -p c1.img othermachine:/var/lib/xen/images > then: > om1 # virsh define c1.xml You can't just use the same XML for each - you need to change the UUID, the namem, and disk image in the XML at very least. > om1 # xm start c1 > > and hangville, > if I do: > om1 # xmstart c1 -c > it seems to hang just after the grub boot menu. Define hang ? If the guest is configured with graphical framebuffer it is perfectly expected that you'll not see anything on the text console while booting. > I assume I am "doing it wrong" but this worked great in the past. You might want to try the 'virt-clone' tool which will automate much of the stuff. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From fcxen at itsbeen.sent.com Sat Feb 2 21:38:50 2008 From: fcxen at itsbeen.sent.com (fc xen list) Date: Sat, 02 Feb 2008 13:38:50 -0800 Subject: [Fedora-xen] what steps are required to manually move a PV domU from one machine to another? In-Reply-To: <20080202205758.GB8276@redhat.com> References: <47A4D714.5060709@itsbeen.sent.com> <20080202205758.GB8276@redhat.com> Message-ID: <47A4E2EA.3010502@itsbeen.sent.com> My bad, the clone army master was on eth0 and the clone army slaves were on eth1 so when I copied the xml dump, I changed everything but that ugh, but please read below for problems with vanilla F8 and virt-clone. Daniel P. Berrange wrote: > On Sat, Feb 02, 2008 at 12:48:20PM -0800, fc xen list wrote: >> Hi, >> >> I am having a problem - I created a lovely bunch of F8 x86_64 domUs and I >> want to create a vast clone army of them using different dom0s. The problem >> is, I do: >> >> fm # virt-install c1 (no graphics) >> fm # xm start c1 >> fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] > > Welcome to the world of massive data corruption if you copy the > disk without shutting down. Yeah, I know, but they are pretty inactive and it has worked great in the past. > >> fm # scp -p c1.img othermachine:/var/lib/xen/images >> then: >> om1 # virsh define c1.xml > > You can't just use the same XML for each - you need to change the UUID, > the namem, and disk image in the XML at very least. Sorry, I do change that - id, name, image, MAC address, etc. > >> om1 # xm start c1 >> >> and hangville, >> if I do: >> om1 # xmstart c1 -c >> it seems to hang just after the grub boot menu. > > Define hang ? If the guest is configured with graphical framebuffer it > is perfectly expected that you'll not see anything on the text console > while booting. I always choose no graphics on the virt-install The xm list state is usually --p-- > >> I assume I am "doing it wrong" but this worked great in the past. > > You might want to try the 'virt-clone' tool which will automate much of > the stuff. Thanks for mentioning that, I can't - my VMs always enter a "no state" state when I shut them down and virt-clone won't clone them unless they are in a different state that I can't seem to get them to go into. One confusing thing is xm list and virsh use different terms. In xm list the VM shows as state "------" Example: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 5143 8 r----- 10708.0 c1 30 1200 1 -b---- 3294.3 c2 28 768 1 -b---- 349.4 c3 34 2465 1 ------ 0.0 # virsh list --all Id Name State ---------------------------------- 0 Domain-0 running 28 m66 blocked 30 m62 blocked - m82 no state I have never had a machine go to any other state, other than "------" (or "no state" in virsh) after a xm shutdown*, should be using some other shutdown method? All my builds are using vanilla F8 x86_64 and virt-install, no custom kernels or other monkey business. A different dom0 with a centos51 and F8 domU that I just did xm shutdown on, they both go to no state: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2358 4 r----- 15402.7 d1 7 375 1 -b---- 466.3 c51 22 768 1 ------ 138.9 f8-2 21 512 1 ------ 57.3 [root at sc-t131 ~]# virsh list --all Id Name State ---------------------------------- 0 Domain-0 running 7 d1 blocked - c51 no state - f8-2 no state Example of state during hanging after xm start attempt of c3: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 5143 8 r----- 10715.6 c1 30 1200 1 -b---- 3294.3 c2 28 768 1 -b---- 349.4 c3 35 2465 1 --p--- 0.0 # virsh list --all Id Name State ---------------------------------- 0 Domain-0 running 28 m66 blocked 30 m62 blocked 35 m82 paused I'd love to use virt-clone... > > Dan. * OK, one goes into "---s-d" but that is upgraded from a previous Fedora version, so I don't worry about that one. All others are new virt-install installs. From itamar at ispbrasil.com.br Sat Feb 2 22:21:28 2008 From: itamar at ispbrasil.com.br (itamar) Date: Sat, 02 Feb 2008 20:21:28 -0200 Subject: [Fedora-xen] what steps are required to manually move a PV domU from one machine to another? In-Reply-To: <20080202205758.GB8276@redhat.com> References: <47A4D714.5060709@itsbeen.sent.com> <20080202205758.GB8276@redhat.com> Message-ID: <47A4ECE8.3020403@ispbrasil.com.br> Can you explain for me how to do this using LVM ? there are a easy way to move a lvm partition from a machine to another over network ? Daniel P. Berrange wrote: > On Sat, Feb 02, 2008 at 12:48:20PM -0800, fc xen list wrote: > >> Hi, >> >> I am having a problem - I created a lovely bunch of F8 x86_64 domUs and I >> want to create a vast clone army of them using different dom0s. The problem >> is, I do: >> >> fm # virt-install c1 (no graphics) >> fm # xm start c1 >> fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] >> > > Welcome to the world of massive data corruption if you copy the > disk without shutting down. > > >> fm # scp -p c1.img othermachine:/var/lib/xen/images >> then: >> om1 # virsh define c1.xml >> > > You can't just use the same XML for each - you need to change the UUID, > the namem, and disk image in the XML at very least. > > >> om1 # xm start c1 >> >> and hangville, >> if I do: >> om1 # xmstart c1 -c >> it seems to hang just after the grub boot menu. >> > > Define hang ? If the guest is configured with graphical framebuffer it > is perfectly expected that you'll not see anything on the text console > while booting. > > >> I assume I am "doing it wrong" but this worked great in the past. >> > > You might want to try the 'virt-clone' tool which will automate much of > the stuff. > > Dan. > From accarlson at gmail.com Mon Feb 4 10:28:25 2008 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Mon, 4 Feb 2008 08:28:25 -0200 Subject: [Fedora-xen] no xend on f8 x64 In-Reply-To: References: Message-ID: Hi, > On my AMD64, running F8, I just installed the virtualization package > with yum and rebooted into the Xen kernel. But I can't create a new > virtual machine. I read that the xend daemon should be running for that, > but I can't find it. Should it be installed or how should I do that? Have you used the command: yum groupinstall 'Virtualization' I have the packages bellow installed in my system: kernel-xen, xen, xen-libs and libvirtd and it works well. The daemon starts in the system initialization. Regards, -- Augusto Castelan Carlson -------------- next part -------------- An HTML attachment was scrubbed... URL: From orenault at redhat.com Mon Feb 4 08:27:55 2008 From: orenault at redhat.com (Olivier Renault) Date: Mon, 04 Feb 2008 09:27:55 +0100 Subject: [Fedora-xen] what steps are required to manually move a PV domU from one machine to another? In-Reply-To: <47A4ECE8.3020403@ispbrasil.com.br> References: <47A4D714.5060709@itsbeen.sent.com> <20080202205758.GB8276@redhat.com> <47A4ECE8.3020403@ispbrasil.com.br> Message-ID: <47A6CC8B.4050201@redhat.com> itamar wrote: > Can you explain for me how to do this using LVM ? > > > there are a easy way to move a lvm partition from a machine to another > over network ? > > You can easily do it with dd. Create your LV on the host you would like to copy the VM to. dd if=/dev/rootvg/guest1 | ssh newhost dd of=/dev/rootvg/copyguest1 Regards, Olivier > > > > Daniel P. Berrange wrote: >> On Sat, Feb 02, 2008 at 12:48:20PM -0800, fc xen list wrote: >> >>> Hi, >>> >>> I am having a problem - I created a lovely bunch of F8 x86_64 domUs >>> and I want to create a vast clone army of them using different dom0s. >>> The problem is, I do: >>> >>> fm # virt-install c1 (no graphics) >>> fm # xm start c1 >>> fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] >>> >> >> Welcome to the world of massive data corruption if you copy the >> disk without shutting down. >> >> >>> fm # scp -p c1.img othermachine:/var/lib/xen/images >>> then: >>> om1 # virsh define c1.xml >>> >> >> You can't just use the same XML for each - you need to change the UUID, >> the namem, and disk image in the XML at very least. >> >> >>> om1 # xm start c1 >>> >>> and hangville, >>> if I do: >>> om1 # xmstart c1 -c >>> it seems to hang just after the grub boot menu. >>> >> >> Define hang ? If the guest is configured with graphical framebuffer it >> is perfectly expected that you'll not see anything on the text console >> while booting. >> >> >>> I assume I am "doing it wrong" but this worked great in the past. >>> >> >> You might want to try the 'virt-clone' tool which will automate much of >> the stuff. >> >> Dan. >> > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Red Hat France SARL, 171 Avenue Georges Clemenceau, 92024 Nanterre Cedex, France. Siret n? 421 199 464 00056 From accarlson at gmail.com Mon Feb 4 12:55:17 2008 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Mon, 4 Feb 2008 10:55:17 -0200 Subject: [Fedora-xen] Two NICs Message-ID: Hello! I'm running Fedora 8 with two network interfaces. I will have 2 guests. On guest and the host (dom0) need to be connected through eth0 and the other guest through eth1. When I try to create a guest with virt-manager, in the network options for "shared physical device", I have "peth0 (bridged eth0)" and "eth1 (not bridged)". Both the guest and the host will be connected to the same network: Dom0: 172.16.1.2/24 Dom1: 172.16.1.3/24 Dom2: 172.16.1.4/24 What I need to change in the xen network scripts to make eth1 to be a bridged interface? How I set Dom0 be connected through eth0? Thanks in advance. Regards, -- Augusto Castelan Carlson -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin-lists at robinbowes.com Wed Feb 6 14:08:17 2008 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 06 Feb 2008 14:08:17 +0000 Subject: [Fedora-xen] Re: How is network bridging for Xen handled in F7? In-Reply-To: <20070605172910.GK15012@redhat.com> References: <20070605172357.GI15012@redhat.com> <20070605172910.GK15012@redhat.com> Message-ID: Daniel P. Berrange wrote: > Oh btw, before anyone asks - we added compatability code to vif-bridge, so if > you have any existing guest config files which refer to 'xenbr0' they will > automatically join the eth0 bridge device instead. So existing guests are > supposed to 'just work' even though the Dom0 network config changed a little. Dan, I just ran into an issue with this. I have re-built F8 xen-3.1.2 from SRPM on CentOS 5.1 x86_64 and done a clean kickstart install of CentOS 5.1 x86_64 which pulls in the xen-3.1.2 RPMs from a repo (i.e. xen-3.0.3 is never installed). I have some guests created using xen-??? on FC6 which I have migrated to a new machine and which use xenbr0. When I try to start the domains using "xm create -c guestname" I got a message about not finding xenbr0. So, I changed xenvr0 to virbr0 and the guests start OK and can talk to each other but can not talk to anything on the rest of the network. I have figured that this is related to the issue discussed in this thread. How come xenbr0 was not recognised? Do I need to update some other packages, or should I use virsh? Or do I just configure eth0 as a bridge in Dom0 as described here [1] Thanks, R. [1] http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt From robin-lists at robinbowes.com Wed Feb 6 17:28:37 2008 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 06 Feb 2008 17:28:37 +0000 Subject: [Fedora-xen] Re: How is network bridging for Xen handled in F7? In-Reply-To: References: <20070605172357.GI15012@redhat.com> <20070605172910.GK15012@redhat.com> Message-ID: Robin Bowes wrote: > How come xenbr0 was not recognised? Do I need to update some other > packages, or should I use virsh? OK, I've answered my own question. I've rebuilt the following packages from Fedora 8 on CentOS 5.1 x86_64, added them to my own yum repo, then done a clean kickstart install of CentOS 5.1 using my yum repo as a source. The result? It all seems to be working very nicely! The networking on my old domains (that use xenbr0 in the config files) work without any modification. These are the packages I re-built: libvirt-0.4.0-4 virt-viewer-0.0.2-2 xen-libs-3.1.2-1 gtk-vnc-0.2.0-4 libvirt-python-0.4.0-4 python-virtinst-0.300.2-2 xen-3.1.2-1.x86_64 The binaries are in my repo here: http://repo.yo61.net/ Specifically, here: http://repo.yo61.net/centos/5/x86_64/RPMS/ Hopefully, this will keep me going for a while! R. From lists at pavlodarproductions.com Wed Feb 6 21:33:59 2008 From: lists at pavlodarproductions.com (Bob Jones) Date: Wed, 06 Feb 2008 15:33:59 -0600 Subject: [Fedora-xen] newbie's request for info Message-ID: <47AA27C7.6070405@pavlodarproductions.com> Greetings list. I have what might be a strange request but will ask it anyway -- but first some background info. I am new to Xen, having just started using it on Fedora 8 within the last month or 2 on my server (homebuilt AMD x2 6400+ on Asus M2N-E Sli board and 8GB DDR2-800 memory on software RAID5 1TB). Having great sucess on the server running 3 Windows VM's (XP Pro, 2000 server with SQL 2000, and SBS2003 server), I wanted to setup my laptop similarly for client demo purposes. The laptop I am using is a new Dell Latitude D531 running a Turion 64x2 TL-60 with 4GB memory and 100GB drive. My problem is this -- booting into the xen kernel works fine (well, sound doesnt work and won't work with less than 2.6.23 kernel, but thats no big deal). I can create a HVM using virt-manager, allocating memory, vcpu's, etc. etc. However, upon booting the VM the entire laptop locks up (drive activity immediately stops, keyboard and mouse are completely unresponsive). This forces a hard shutdown. Upon starting back up the DomU VM is not listed and when I attempt to create a new fully virtualized VM (HVM?), I am told that virtualization support is present in the CPU but not enabled in the BIOS (but it IS .. verified many times). I suspect that there is a bug in the BIOS that is showing virtualization enabled when in fact it is not. My questions are: 1) Has anyone on this list seen the same symptoms and if so, did you find a workaround? 2) How do I go about logging and checking what is happening when it locks up so I can take that to Dell and file a bug report? Thanks in advance for all pointers. Bob J From berrange at redhat.com Wed Feb 6 21:37:44 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 6 Feb 2008 21:37:44 +0000 Subject: [Fedora-xen] Red Hat 5.1, Xen and virt-manager crashes In-Reply-To: References: Message-ID: <20080206213744.GI9469@redhat.com> On Wed, Jan 30, 2008 at 02:41:45PM -0800, William R. Barker wrote: > > I've been testing Red Hat 5.1's vm stuff for a couple of weeks and was > quite happy with the results so far. But I've run into a bit of an issue > that I hope someone out there can help me solve. > > Since late last week, after a "yum upgrade" that included the newest > kernel (2.6.18-53.1.6.el5xen), virt-manager dies when started from either > the command line or from the desktop with a segmentation fault. > > /var/log/messages gets the following: > kernel: /usr/share/virt[4369] general protection rip:3b4f8401fa > rsp:7fff40efad50 error:0 There was a broken update to 'pygtk2' in RHEL-5 which caused virt-manager and other python + GTK based apps to crash - there should be a newer version out to fix it already: http://rhn.redhat.com/errata/RHBA-2008-0079.html Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From pvanbork at outerline.com Sat Feb 9 00:05:22 2008 From: pvanbork at outerline.com (Petrus B. van Bork) Date: Fri, 08 Feb 2008 19:05:22 -0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. Message-ID: <47ACEE42.5080404@outerline.com> Dear Fellow-List Members: I am running the latest, fully updated, F8 Xen kernel with F8, updated DomU on top. I need to clone that DomU - indeed, a need to do rather a lot of cloning to fulfill our project's mission. I tried to run virt-clone but it will not perform as per the man's examples and despite hours of searching on the 'net I cannot find any reason why not. Here is the example from the man: -EXAMPLES - Clone the guest called "demo" which has a single disk to copy - - # virt-clone \ - --original demo \ - --name newdemo \ - --file /var/lib/xen/images/newdemo.img What I have tried: Where: HanoverGuest = name of functioning DomU (shut off for cloning...) KohaHanoverConf_Gold = name of new DomU New File Image: KohaHanoverConf_Gold.dsk Here is the command sequence I issue: #virt-clone --original HanoverGuest --name KohaHanoverConf_Gold --file /var/lib/xen/images/KohaHanoverConf_Gold.dsk -d I get: Fri, 08 Feb 2008 14:57:31 DEBUG start clone with HV Xen Fri, ditto DEBUG clone device list: ['/var/lib/xen/images/KohaHanoverConf_Gold.dsk'] Fri, ditto DEBUG clone device size: [1048570000L] Fri, ditto DEBUG clone device type: [True] ERROR: Disk size must an int or a float. What would you like to use as the disk (path)? ...I have tried many, many variants with no more luck and usually with the same error message. I have tried to run it without creating a disk image myself, with one of 0 bytes size and, as can be seen, one of 10gig size. No joy! Furthermore, I cannot find any information on the net on what those debug messages mean so I have little to judge what is going on. Apparently the ERROR msg. itself,likely, is generated by: @@ -83,9 +77,13 @@ class VirtualDisk: if size is None and not os.path.exists(self.path): raise ValueError, \ _("A size must be provided for non-existent disks") - if size is not None and size <= 0: + if size is not None and \ + (__builtin__.type(size) is not __builtin__.type(1) and \ + __builtin__.type(size) is not __builtin__.type(1.0)): + raise ValueError, _("Disk size must be an int or a float.") ...which comes from a September 28, 2007 patch authored by Cole Robinson for virtinst validation fixes, found here: http://www.spinics.net/linux/fedora/et-mgmt-tools/msg01760.html ...alas, without knowing all the code I am not sure what is going on. It seems to suggest that somehow the diskimage file is not recognized as a built in data type or something similar - but there seem to be no commands available in virt-clone to set the datatype, adapt for the date type or even tell a user what datatype they need. Since I am a relative Linux newbie I may very well be making a classic 'flat-forehead' error - but what? I tried to run virt-clone as a basic interactive tool - the man states that it can run interactively with no command line switches. Here is what happens: #virt-clone ..and I get... ERROR: A new disk image file for the clone guest is required and then it goes back to the prompt. Not helpful! I very badly need to clone DomU's effectively during our development process - and afterwards and I would be excruciatingly grateful for any help anyone can provide! Regards, Petrus From ask at develooper.com Sun Feb 10 09:24:10 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Sun, 10 Feb 2008 01:24:10 -0800 Subject: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to Fedora 8 Message-ID: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> Hi, Since upgrading from Fedora 6 to Fedora 8 my custom bridge script stopped working. I need to have both eth0 and eth1 bridged into each XM. My xen machines are just defined in old-style /etc/xen/foo configuration files, like vif = [ 'mac=00:16:3e:42:08:1d, bridge=xenbr0', 'mac=00:16:3e: 42:08:1e, bridge=xenbr1' ] I've changed that to vif = [ 'mac=00:16:3e:42:08:1d, bridge=eth0', 'mac=00:16:3e:42:08:1e, bridge=eth1' ] but when I do a "xm create foo" I still end up with the new interfaces on the wrong bridge! # brctl show bridge name bridge id STP enabled interfaces eth0 8000.0030488c8a26 no peth0 eth1 8000.0030488c8a27 no peth1 xenbr0 8000.feffffffffff no vif1.0 xenbr1 8000.feffffffffff no vif1.1 If I manually move the vifX.X interfaces to the eth0/eth1 bridges then everything works. This is my custom bridge script: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" netdev=eth1 bridge=eth1 "$dir/network-bridge" "$@" netdev=eth0 bridge=eth0 Any ideas? - ask -- http://develooper.com/ - http://askask.com/ From crobinso at redhat.com Mon Feb 11 15:15:21 2008 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 11 Feb 2008 10:15:21 -0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <47ACEE42.5080404@outerline.com> References: <47ACEE42.5080404@outerline.com> Message-ID: <47B06689.2000009@redhat.com> Petrus B. van Bork wrote: > Dear Fellow-List Members: > > I am running the latest, > fully updated, F8 Xen kernel with F8, updated DomU on top. I need to > clone that DomU - indeed, a need to do rather a lot of cloning to > fulfill our project's mission. I tried to run virt-clone but it will > not perform as per the man's examples and despite hours of searching on > the 'net I cannot find any reason why not. > > Here is the example from the man: > > -EXAMPLES > - Clone the guest called "demo" which has a single disk to copy > - > - # virt-clone \ > - --original demo \ > - --name newdemo \ > - --file /var/lib/xen/images/newdemo.img > > What I have tried: > > Where: > > HanoverGuest = name of functioning DomU (shut off for cloning...) > KohaHanoverConf_Gold = name of new DomU > New File Image: KohaHanoverConf_Gold.dsk > > Here is the command sequence I issue: > > #virt-clone --original HanoverGuest --name KohaHanoverConf_Gold --file /var/lib/xen/images/KohaHanoverConf_Gold.dsk -d > > I get: > > Fri, 08 Feb 2008 14:57:31 DEBUG start clone with HV Xen > Fri, ditto DEBUG clone device list: ['/var/lib/xen/images/KohaHanoverConf_Gold.dsk'] > Fri, ditto DEBUG clone device size: [1048570000L] > Fri, ditto DEBUG clone device type: [True] > ERROR: Disk size must an int or a float. > What would you like to use as the disk (path)? > > ...I have tried many, many variants with no more luck and usually with the same error message. I have tried to run it > without creating a disk image myself, with one of 0 bytes size and, as can be seen, one of 10gig size. No joy! > Furthermore, I cannot find any information on the net on what those debug messages mean so I have little to judge what is going on. > > Apparently the ERROR msg. itself,likely, is generated by: > > @@ -83,9 +77,13 @@ class VirtualDisk: > if size is None and not os.path.exists(self.path): > raise ValueError, \ > _("A size must be provided for non-existent disks") > - if size is not None and size <= 0: > + if size is not None and \ > + (__builtin__.type(size) is not __builtin__.type(1) and \ > + __builtin__.type(size) is not __builtin__.type(1.0)): > + raise ValueError, _("Disk size must be an int or a float.") > > ...which comes from a September 28, 2007 patch authored by Cole Robinson for virtinst validation fixes, found here: > http://www.spinics.net/linux/fedora/et-mgmt-tools/msg01760.html ...alas, without knowing all the code I am not sure what is going on. > It seems to suggest that somehow the diskimage file is not recognized as a built in data type or something similar - but there seem to > be no commands available in virt-clone to set the datatype, adapt for the date type or even tell a user what datatype they need. Since I am a relative > Linux newbie I may very well be making a classic 'flat-forehead' error - but what? > > I tried to run virt-clone as a basic interactive tool - the man states that it can run interactively with no command line switches. Here is what happens: > > #virt-clone > > ..and I get... > > ERROR: A new disk image file for the clone guest is required and then it goes back to the prompt. Not helpful! > > I very badly need to clone DomU's effectively during our development process - and afterwards and I would be excruciatingly grateful for any help anyone can provide! > > Regards, > > Petrus > Hi Petrus, This is fixed upstream: http://hg.et.redhat.com/virt/applications/virtinst--devel?cs=611782118e76 But this isn't in fedora yet. Follow the instructions at http://virt-manager.org/scmrepo.html to check out the latest virtinst--devel and you should be able to run virt-clone directly from the checkout. - Cole From pvanbork at outerline.com Mon Feb 11 23:35:11 2008 From: pvanbork at outerline.com (Petrus B. van Bork) Date: Mon, 11 Feb 2008 18:35:11 -0500 Subject: [Fedora-xen] Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. Message-ID: <47B0DBAF.8060209@outerline.com> Dear Cole & Fellow List Members: Had some 'tap-dance' at the virt-manager site (which I will deal with later) so I patched CloneManager.py, on my machine, as per the first link Cole, so kindly, provided. I deleted the one line shown in red with a minus, and added the following line, in green, with a plus (...just for the record). This resulted in virt-clone running - but very touchy. After the change virt-clone would still not run interactively - it would ask for a disk and go back to the prompt and it would not run with a full string of command line switches (...as illustrated in my last email and Cole's reply). It would, however, run: #virt-clone -f foo.dsk ...at that point it would ask for several things, including the original clone's UUID or name (...this for those trying it for the first time, seems to need the Virtual Machine Manager running and connected to the Xen hypervisor but, of course, with the DomU to be cloned "Shutoff"). When the cloning began it started with: libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: ...then I got - to my relief... Cloning from /home/xenguest/hanoverguest.dsk to KohaHanoverConf_Gold.dsk ...this worked...sort of...no more error messages BUT the result I ended up with was: * an .sxp file that did not have a disk path to the .dsk, * and it was missing a number of other things as well such as the reference to localhost:5900 * tried running "xm create" But...xm create would not run command xm create -c /... path to UUID/config.sxp resulted in: Error: Errors were found at line 5 while processing /var/lib/xend/domains/...UUID.../config.sxp: (VCPUs_live 1) - alas, this was the 100% identical line from the config.sxp that it was lifted from (...the running DomU). * virsh didn't like the .sxp either and I was not sure how to create an xml for it to read, just don't know enough and not enough documentation available. At the end of the day - another day spent fruitlessly trying, trying, trying... I am a little further than yesterday but I am no further than I was this morning. Still completely unable to get the new cloned DomU to run. Using #xm start changes the status to 'running' in Virtual Machine Manager but with 0 CPU usage and RAM usage. Does anyone have any idea what is wrong? I am still in the dark and would still be most grateful for any more illumination on this! Best, P. ------------------------------------------- Other Issues with virt-clone after fix, this morning: #virt-clone ...result: ERROR: A new disk image file for the cloned guest is required, followed by a command prompt... [...no interactive functionality available, as yet...] #virt-clone -f testdisk.dsk ..result "What is the name or uuid of the original virtual machine? [...which is the correct response but you have not fed the script a path and will result in a config.sxp with no path for the disk!] #virt-clone -f /var/lib/xen/images/testdisk.dsk ...result: ERROR: Disk size must be an in or a float. What would you like to use as the disk path? [...problematic...can't seem to use '-f' switch, as per man syntax, unless I have misread the man....) #virt-clone --file /var/lib/xen/images/testdisk.dsk ...result: "What is the name or uuid of the original virtual machine? So...my question to Cole: "Does the version from the virtual manager site, as per your second provided link, fix the above as well? Or, not yet?" Obviously, if the material at the repository is better/later, I will use it, once I figure out "hg" - which is 'unknown command' on my system, presently. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Tue Feb 12 13:34:25 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 12 Feb 2008 13:34:25 +0000 Subject: [Fedora-xen] newbie's request for info In-Reply-To: <47AA27C7.6070405@pavlodarproductions.com> References: <47AA27C7.6070405@pavlodarproductions.com> Message-ID: <47B1A061.9010203@redhat.com> Bob Jones wrote: > My questions are: > 1) Has anyone on this list seen the same symptoms and if so, did you > find a workaround? Hardware lockups are tricky to solve. However I can tell you that for AMD chips virtualization cannot be disabled in the BIOS. This only applies to Intel chips. Check /proc/cpuinfo flags in the dom0 to make sure that your processor has hardware virtualization support (the flag is 'svm' on AMD). > 2) How do I go about logging and checking what is happening when it > locks up so I can take that to Dell and file a bug report? Serial console might be your best bet, in order to capture that "final" error, if there is one ... Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From christf1 at nortel.com Tue Feb 12 15:24:34 2008 From: christf1 at nortel.com (christf1) Date: Tue, 12 Feb 2008 07:24:34 -0800 (PST) Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <47ACEE42.5080404@outerline.com> References: <47ACEE42.5080404@outerline.com> Message-ID: <15434469.post@talk.nabble.com> I tried the latest dev stream, and continued to have the problem. The quick fix is to simply touch the target file before launching 'virt-clone' touch /newvm.img virt-clone -o existing_vm -n new_vm -o /newvm.img Cheers! -- View this message in context: http://www.nabble.com/virt-clone-Fedora-8-Xen3.1-...-ERROR%3A-Disk-size-must-be-an-int-or-a-float.-tp15366676p15434469.html Sent from the Fedora Xen mailing list archive at Nabble.com. From asraikhn at gmail.com Tue Feb 12 16:49:55 2008 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 12 Feb 2008 21:49:55 +0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <15434469.post@talk.nabble.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> Message-ID: <5f0f8dba0802120849t8b10ee4o144340eb24c0f0b8@mail.gmail.com> On Feb 12, 2008 8:24 PM, christf1 wrote: > > I tried the latest dev stream, and continued to have the problem. The > quick > fix is to simply touch the target file before launching 'virt-clone' > > touch /newvm.img > virt-clone -o existing_vm -n new_vm -o /newvm.img > hi, i wonders virt-clone will work when one is doing LVM for domUs fro example here is mine virutal config file kernel = "/boot/vmlinuz-2.6.21-2952.fc8xen" ramdisk = "/boot/initrd-2.6.21-2952.fc8xen-domU.img" memory = 200 name = "myvm3" vif = [ 'ip=xxx.xxx.xx.xx' ] disk = [ 'phy:vg/vm2.root,sda1,w', 'phy:vg/vm2.swap,sda2,w', 'phy:vg/vm2.var,sda3,w' ] root = "/dev/sda1 ro" on_reboot = 'restart' on_crash = 'restart' On other hosts we are using loop back files for domU FS. thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From crobinso at redhat.com Tue Feb 12 17:30:21 2008 From: crobinso at redhat.com (Cole Robinson) Date: Tue, 12 Feb 2008 12:30:21 -0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <15434469.post@talk.nabble.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> Message-ID: <47B1D7AD.3040102@redhat.com> christf1 wrote: > I tried the latest dev stream, and continued to have the problem. The quick > fix is to simply touch the target file before launching 'virt-clone' > > touch /newvm.img > virt-clone -o existing_vm -n new_vm -o /newvm.img > > Cheers! I'm not seeing this: hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel cd virtinst--devel ./virt-clone -o xen-pv -n clone-pv -f /idontexist.img starts working, for an existing turned off guest named xen-pv on f8. Is there anything you are doing differently? If so, can you detail it and post the complete error message? Thanks, Cole From berrange at redhat.com Tue Feb 12 17:35:27 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 12 Feb 2008 17:35:27 +0000 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <5f0f8dba0802120849t8b10ee4o144340eb24c0f0b8@mail.gmail.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> <5f0f8dba0802120849t8b10ee4o144340eb24c0f0b8@mail.gmail.com> Message-ID: <20080212173527.GK25829@redhat.com> On Tue, Feb 12, 2008 at 09:49:55PM +0500, Asrai khn wrote: > On Feb 12, 2008 8:24 PM, christf1 wrote: > > > > > I tried the latest dev stream, and continued to have the problem. The > > quick > > fix is to simply touch the target file before launching 'virt-clone' > > > > touch /newvm.img > > virt-clone -o existing_vm -n new_vm -o /newvm.img > > > > hi, > > i wonders virt-clone will work when one is doing LVM for domUs fro example > here is mine virutal config file It won't care what type of storage the original VM is using - it'll simply read the data off the original disk whether its a file or block device or LVM vol. If you want to use LVM volumes in the destination VM, then you currently need to manually create the LVM volume ahead of time - virt-clone itself will not create new LVM volumes for you. This is in the future feature list though, once libvirt storage management APIs are merged. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Tue Feb 12 17:36:14 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 12 Feb 2008 17:36:14 +0000 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <15434469.post@talk.nabble.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> Message-ID: <20080212173613.GL25829@redhat.com> On Tue, Feb 12, 2008 at 07:24:34AM -0800, christf1 wrote: > > I tried the latest dev stream, and continued to have the problem. The quick > fix is to simply touch the target file before launching 'virt-clone' > > touch /newvm.img > virt-clone -o existing_vm -n new_vm -o /newvm.img Your command line is wrong - the last flag should be '-f' not '-o' to supply the filename Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From asraikhn at gmail.com Tue Feb 12 17:47:40 2008 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 12 Feb 2008 22:47:40 +0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <20080212173527.GK25829@redhat.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> <5f0f8dba0802120849t8b10ee4o144340eb24c0f0b8@mail.gmail.com> <20080212173527.GK25829@redhat.com> Message-ID: <5f0f8dba0802120947n1fd2cdaas7fe118e90b2cd74a@mail.gmail.com> On Feb 12, 2008 10:35 PM, Daniel P. Berrange wrote: > > It won't care what type of storage the original VM is using - it'll > simply read the data off the original disk whether its a file or > block device or LVM vol. > > If you want to use LVM volumes in the destination VM, then you currently > need to manually create the LVM volume ahead of time - virt-clone itself > will not create new LVM volumes for you. This is in the future feature > list though, once libvirt storage management APIs are merged. > > thanks, one more question what will be the virt-clone command to clone existing vm which FS is based on loop back files and using more then one file for root. var, and swap eg here is the entry from /etc/xen/vm.cfg which we are using kernel = "/boot/vmlinuz-2.6.21-2952.fc8xen" ramdisk = "/boot/initrd-2.6.21-2952.fc8xen-domU.img" memory = 256 name = "vm1" vif = [ 'ip=xx.xx.xxx.xxx' ] disk = ['tap:aio:/var/uml/vm1/root,sda1,w', 'tap:aio:/var/uml/vm1/var,sda2,w', 'tap:aio:/var/uml/vm1/swap,sda3,w'] root = "/dev/sda1 ro" on_reboot = 'restart' on_crash = 'restart' all our our virtual hosts we are using separate loop back files for root, var and swap. thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Feb 12 17:52:40 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 12 Feb 2008 17:52:40 +0000 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <5f0f8dba0802120947n1fd2cdaas7fe118e90b2cd74a@mail.gmail.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> <5f0f8dba0802120849t8b10ee4o144340eb24c0f0b8@mail.gmail.com> <20080212173527.GK25829@redhat.com> <5f0f8dba0802120947n1fd2cdaas7fe118e90b2cd74a@mail.gmail.com> Message-ID: <20080212175240.GM25829@redhat.com> On Tue, Feb 12, 2008 at 10:47:40PM +0500, Asrai khn wrote: > On Feb 12, 2008 10:35 PM, Daniel P. Berrange wrote: > > > > > It won't care what type of storage the original VM is using - it'll > > simply read the data off the original disk whether its a file or > > block device or LVM vol. > > > > If you want to use LVM volumes in the destination VM, then you currently > > need to manually create the LVM volume ahead of time - virt-clone itself > > will not create new LVM volumes for you. This is in the future feature > > list though, once libvirt storage management APIs are merged. > > > > > thanks, one more question what will be the virt-clone command to clone > existing vm which FS is based on loop back files and using more then one > file for root. var, and swap eg here is the entry from /etc/xen/vm.cfg which > we are using Yes it is quite happy dealing with multiple disks, and doesn't care what driver is being used (phy:, file:, tap:aio: - this only affects guest, not the way you access files). Just use the '-f' flag multiple times if you have many disks. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From crobinso at redhat.com Tue Feb 12 17:53:11 2008 From: crobinso at redhat.com (Cole Robinson) Date: Tue, 12 Feb 2008 12:53:11 -0500 Subject: [Fedora-xen] Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <47B0DBAF.8060209@outerline.com> References: <47B0DBAF.8060209@outerline.com> Message-ID: <47B1DD07.8020305@redhat.com> Hi, Petrus B. van Bork wrote: > > Had some 'tap-dance' > at the virt-manager site (which I will deal with later) Just wondering what issues you had. If the documentation to build from source isn't clear I'd like to improve it. > CloneManager.py, on my machine, as per the first link Cole, so kindly, > provided. I deleted the one line shown in red with a minus, and added > the following line, in green, with a plus (...just for the record). > This resulted in virt-clone running - but very touchy. After the change > virt-clone would still not run interactively - it would ask for a disk > and go back to the prompt and it would not run with a full string of > command line switches I'm a bit confused. I see below that just running 'virt-clone' fails (this is a bug that needs to be fixed) but a full string of cmds fails as well? I can't seem to reproduce this. > (...as illustrated in my last email and Cole's > reply). It would, however, run: > > #virt-clone -f foo.dsk > > ...at that point it would ask for several things, including the original > clone's UUID or name (...this for those trying it for the first time, > seems to need the Virtual Machine Manager running and connected to the > Xen hypervisor but, of course, with the DomU to be cloned "Shutoff"). > > When the cloning began it started with: > > libvir: Xen Daemon error : GET operation failed: > libvir: Xen Daemon error : GET operation failed: > > ...then I got - to my relief... > > Cloning from /home/xenguest/hanoverguest.dsk to KohaHanoverConf_Gold.dsk > > ...this worked...sort of...no more error messages BUT the result I ended > up with was: > > * an .sxp file that did not have a disk path to the .dsk, > * and it was missing a number of other things as well such as the > reference to localhost:5900 > * tried running "xm create" But...xm create would not run command > xm create -c /... path to UUID/config.sxp resulted in: > > Error: Errors were found at line 5 while processing > /var/lib/xend/domains/...UUID.../config.sxp: (VCPUs_live 1) - alas, this > was the 100% identical line from the config.sxp that it was lifted from > (...the running DomU). > > * virsh didn't like the .sxp either and I was not sure how to create > an xml for it to read, just don't know enough and not enough > documentation available. > After a successful virt-clone, the domain will already be defined. This means both virsh and xm know it exist. You shouldn't need to run xm create at all: just try 'virsh start cloned_vm_name' or 'xm start cloned_vm_name' and the guest should run. virsh doesn't sxp files, it uses xml. Try 'virsh dumpxml cloned_vm_name'. > At the end of the day - another day spent fruitlessly trying, trying, > trying... I am a little further than yesterday but I am no further than > I was this morning. Still completely unable to get the new cloned DomU > to run. Using #xm start changes the status to 'running' in > Virtual Machine Manager but with 0 CPU usage and RAM usage. Does anyone > have any idea what is wrong? I am still in the dark and would still be > most grateful for any more illumination on this! > > Best, > > P. > > ------------------------------------------- > > Other Issues with virt-clone after fix, this morning: > > #virt-clone > > ...result: ERROR: A new disk image file for the cloned guest is > required, followed by a command prompt... [...no interactive > functionality available, as yet...] > As mentioned above this is definitely a bug. > #virt-clone -f testdisk.dsk > > ..result "What is the name or uuid of the original virtual machine? > [...which is the correct response but you have not fed the script a path > and will result in a config.sxp with no path for the disk!] > This is also a bug, we should put the full path in the cloned guest config. > #virt-clone -f /var/lib/xen/images/testdisk.dsk > > ...result: ERROR: Disk size must be an in or a float. > What would you like to use as the disk path? > [...problematic...can't seem to use '-f' switch, as per man syntax, > unless I have misread the man....) > I can't reproduce this. -f and --file should give the exact same result: they literally call the same functions. > #virt-clone --file /var/lib/xen/images/testdisk.dsk > > ...result: "What is the name or uuid of the original virtual machine? > > > So...my question to Cole: "Does the version from the virtual manager > site, as per your second provided link, fix the above as well? Or, not > yet?" Obviously, if the material at the repository is better/later, I > will use it, once I figure out "hg" - which is 'unknown command' on my > system, presently. > > The 'hg' command belongs to the mercurial package (intuitive, I know.) To use the upstream checkout, try this: yum install mercurial hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel cd virtinst--devel ./virt-clone insert-args-here Let us know how that goes and if you are still encountering above issues I couldn't reproduce. Thanks, Cole From russell at flora.ca Tue Feb 12 17:59:04 2008 From: russell at flora.ca (Russell McOrmond) Date: Tue, 12 Feb 2008 12:59:04 -0500 Subject: [Fedora-xen] Xen packages for Vulnerability to CVE-2008-0600 Message-ID: <47B1DE68.2050204@flora.ca> I suspect people are tracking this, and want to know about the process of the xen kernels. https://bugzilla.redhat.com/show_bug.cgi?id=432517 I tested right away, and the exploit works under Xen. -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From christf1 at nortel.com Tue Feb 12 17:57:38 2008 From: christf1 at nortel.com (Christopher Fournier) Date: Tue, 12 Feb 2008 12:57:38 -0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <47B1D7AD.3040102@redhat.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> <47B1D7AD.3040102@redhat.com> Message-ID: <1202839058.668.12.camel@hal9000> Interesting. I'm using a base installation of Fedora 8, 64 bit version, and all packages are directly out of the distro. The error crops up as soon as I launch the tool: [root at localhost ~]# virt-clone -d -o vm1 -n vm2 -f /opt/VMs/vm2.img Tue, 12 Feb 2008 12:25:30 DEBUG start clone with HV qemu:///system Tue, 12 Feb 2008 12:25:30 DEBUG clone device list: ['/opt/VMs/rhel4u6-3.img'] Tue, 12 Feb 2008 12:25:30 DEBUG clone device size: [0] Tue, 12 Feb 2008 12:25:30 DEBUG clone device type: [True] Tue, 12 Feb 2008 12:25:30 DEBUG Disk path not found: Assuming file disk type. ERROR: Disk size must be an int or a float. What would you like to use as the disk (path)? As mentioned, the error also crops up using the latest dev snapshot. On Tue, 2008-02-12 at 12:30 -0500, Cole Robinson wrote: > christf1 wrote: > > I tried the latest dev stream, and continued to have the problem. The quick > > fix is to simply touch the target file before launching 'virt-clone' > > > > touch /newvm.img > > virt-clone -o existing_vm -n new_vm -o /newvm.img > > > > Cheers! > > I'm not seeing this: > > hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel > cd virtinst--devel > ./virt-clone -o xen-pv -n clone-pv -f /idontexist.img > > starts working, for an existing turned off guest named xen-pv on f8. > Is there anything you are doing differently? If so, can you detail it > and post the complete error message? > > Thanks, > Cole -- Chris Fournier Nortel 3500 Carling Avenue Ottawa, Ontario, Canada K2H 8E9 Phone: 613-763-4860 From christf1 at nortel.com Tue Feb 12 18:02:24 2008 From: christf1 at nortel.com (Christopher Fournier) Date: Tue, 12 Feb 2008 13:02:24 -0500 Subject: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float. In-Reply-To: <20080212173613.GL25829@redhat.com> References: <47ACEE42.5080404@outerline.com> <15434469.post@talk.nabble.com> <20080212173613.GL25829@redhat.com> Message-ID: <1202839344.668.18.camel@hal9000> Correct; I should've just cut and pasted, but apparently I looked the other way when I typed that last option. Thanks for pointing that out. :) On Tue, 2008-02-12 at 17:36 +0000, Daniel P. Berrange wrote: > On Tue, Feb 12, 2008 at 07:24:34AM -0800, christf1 wrote: > > > > I tried the latest dev stream, and continued to have the problem. The quick > > fix is to simply touch the target file before launching 'virt-clone' > > > > touch /newvm.img > > virt-clone -o existing_vm -n new_vm -o /newvm.img > > Your command line is wrong - the last flag should be '-f' not '-o' to > supply the filename > > Dan. -- Chris Fournier From asraikhn at gmail.com Tue Feb 12 18:09:17 2008 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 12 Feb 2008 23:09:17 +0500 Subject: [Fedora-xen] Xen packages for Vulnerability to CVE-2008-0600 In-Reply-To: <47B1DE68.2050204@flora.ca> References: <47B1DE68.2050204@flora.ca> Message-ID: <5f0f8dba0802121009v4f8cced4sdd06760871fe6067@mail.gmail.com> On Feb 12, 2008 10:59 PM, Russell McOrmond wrote: > > I suspect people are tracking this, and want to know about the > process of the xen kernels. > > https://bugzilla.redhat.com/show_bug.cgi?id=432517 > > > I tested right away, and the exploit works under Xen. > > where to find the 'exploit' ? :) thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Feb 12 18:15:14 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 12 Feb 2008 18:15:14 +0000 Subject: [Fedora-xen] Xen packages for Vulnerability to CVE-2008-0600 In-Reply-To: <5f0f8dba0802121009v4f8cced4sdd06760871fe6067@mail.gmail.com> References: <47B1DE68.2050204@flora.ca> <5f0f8dba0802121009v4f8cced4sdd06760871fe6067@mail.gmail.com> Message-ID: <20080212181514.GO25829@redhat.com> On Tue, Feb 12, 2008 at 11:09:17PM +0500, Asrai khn wrote: > On Feb 12, 2008 10:59 PM, Russell McOrmond wrote: > > > > > I suspect people are tracking this, and want to know about the > > process of the xen kernels. > > > > https://bugzilla.redhat.com/show_bug.cgi?id=432517 > > > > > > I tested right away, and the exploit works under Xen. > > > > > where to find the 'exploit' ? :) http://justfuckinggoogleit.com/ Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From asraikhn at gmail.com Tue Feb 12 18:26:54 2008 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 12 Feb 2008 23:26:54 +0500 Subject: [Fedora-xen] Xen packages for Vulnerability to CVE-2008-0600 In-Reply-To: <20080212181514.GO25829@redhat.com> References: <47B1DE68.2050204@flora.ca> <5f0f8dba0802121009v4f8cced4sdd06760871fe6067@mail.gmail.com> <20080212181514.GO25829@redhat.com> Message-ID: <5f0f8dba0802121026k3fcfa3c4i478c519cc113b5cd@mail.gmail.com> On Feb 12, 2008 11:15 PM, Daniel P. Berrange wrote: > http://justfuckinggoogleit.com/ > > > wow got it from http://downloads.securityfocus.com/vulnerabilities/exploits/27704.c gcc -o exploit 27704.c ./expoit gimme at 2.6.21-2952.fc8xen (didn't get root shell) Linux vmsplice Local Root Exploit By qaaz ----------------------------------- [+] mmap: 0x0 .. 0x1000 [+] page: 0x0 [+] page: 0x20 [+] mmap: 0x4000 .. 0x5000 [+] page: 0x4000 [+] page: 0x4020 [+] mmap: 0x1000 .. 0x2000 [+] page: 0x1000 [+] mmap: 0xb7ef4000 .. 0xb7f26000 Segmentation fault [asraikhn at xxxx ~]$ Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: Oops: 0000 [#1] Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: SMP Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: CPU: 0 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: EIP: 0061:[<080487f5>] Not tainted VLI Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: EFLAGS: 00210293 (2.6.21-2952.fc8xen #1) Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: EIP is at 0x80487f5 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: eax: e9000003 ebx: 00000004 ecx: 00000000 edx: 00004000 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: esi: c3c79f8c edi: ffffffe0 ebp: c3c79e70 esp: c3c79e5c Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0069 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: Process exploit (pid: 26415, ti=c3c79000 task=c14217d0 task.ti=c3c79000) Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: Stack: 0000000d 00000000 e9000003 e9000003 00000004 00000001 c1058163 c108adbd Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: 00000000 00000000 00000000 00000000 00000030 00000030 bfe230b8 c108b9e7 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: ffffffd0 00000000 00000000 c3c79f4c 00000000 c3c7a00c c181b120 c039ba00 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: Call Trace: Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: [] put_compound_page+0x13/0x14 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: [] splice_to_pipe+0x1c7/0x1d6 Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: [] sys_vmsplice+0x262/0x28b Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: ======================= Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: Code: Bad EIP value. Message from syslogd at xxxx at Feb 12 18:21:48 ... kernel: EIP: [<080487f5>] 0x80487f5 SS:ESP 0069:c3c79e5c regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From asraikhn at gmail.com Tue Feb 12 18:40:32 2008 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 12 Feb 2008 23:40:32 +0500 Subject: [Fedora-xen] Xen packages for Vulnerability to CVE-2008-0600 In-Reply-To: <5f0f8dba0802121026k3fcfa3c4i478c519cc113b5cd@mail.gmail.com> References: <47B1DE68.2050204@flora.ca> <5f0f8dba0802121009v4f8cced4sdd06760871fe6067@mail.gmail.com> <20080212181514.GO25829@redhat.com> <5f0f8dba0802121026k3fcfa3c4i478c519cc113b5cd@mail.gmail.com> Message-ID: <5f0f8dba0802121040r1f45676ckd66bdca3e981a90d@mail.gmail.com> On Feb 12, 2008 11:26 PM, Asrai khn wrote: > > gcc -o exploit 27704.c > > > ./expoit > > gimme at 2.6.21-2952.fc8xen (didn't get root shell) > > didn't give root shell kernels 2.6.23 (custom build) which we are running for UML. regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvanbork at outerline.com Wed Feb 13 04:11:23 2008 From: pvanbork at outerline.com (Petrus B. van Bork) Date: Tue, 12 Feb 2008 23:11:23 -0500 Subject: [Fedora-xen] Virt-Clone Fedora8/Xen 3.1 In-Reply-To: <20080212180201.1353A73172@hormel.redhat.com> References: <20080212180201.1353A73172@hormel.redhat.com> Message-ID: <47B26DEB.3050601@outerline.com> Dear List Colleagues: Wow! So much traffic on these neat but mysterious tools. I used the 'touch' workaround today and got virt-clone working - thank you both to christf1 and to Cole! The relief was literally indescribable when it ran (...pressure, what pressure?!) I have been in touch with Cole and he informs me that the latest and greatest version of virt-clone can be gotten from the virt-manager devel repository and that this version does not need the 'touch' work-around. For those of you who have not used virt-clone - when it finally works it is really great and as cloning is of vital importance to the project I am working on, many thanks to all who contribute to the virt-manager tools! In a previous post, on this thread today, it was mentioned that some of my results were unduplicable on the usage of switches such as "-f" and "--file" - interestingly, yesterday, the same day I experienced those problems I was unable to duplicate some of them, myself, when I went back to them. I do not know why this was/is the case or what happened, there the results I posted were copied from actual terminal windows where they had run. I am willing to run a set of tests against my machine with virt-clone and send them off to anyone interested in its functionality or lack thereof. I think that this is an important tool and I am willing to do whatever I can to help develop it. I have certainly found it to be 'touchy.' Cole has asked me, as a repository using newbie - who had a lack of success gaining access - to report on my experience of trying to get stuff out of the repository and I will do so, shortly, and report my experience so others can benefit from my efforts to gain competence and my report on how this is done - some steps do seem to be skipped in the instructions on that site! Thanks, again to Cole for pointers on what was going wrong for me, there. It was great to see my questions about LVM and virt-clone answered today, before I could even ask them myself! Best, Petrus fedora-xen-request at redhat.com wrote: > Send Fedora-xen mailing list submissions to > fedora-xen at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen > or, via email, send a message with subject or body 'help' to > fedora-xen-request at redhat.com > > You can reach the person managing the list at > fedora-xen-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-xen digest..." > > > Today's Topics: > > 1. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 2. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 3. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 4. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Asrai khn) > 5. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 6. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 7. Xen packages for Vulnerability to CVE-2008-0600 (Russell McOrmond) > 8. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Christopher Fournier) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Feb 2008 12:30:21 -0500 > From: Cole Robinson > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: christf1 > Cc: fedora-xen at redhat.com > Message-ID: <47B1D7AD.3040102 at redhat.com> > Content-Type: text/plain; charset=us-ascii > > christf1 wrote: > >> I tried the latest dev stream, and continued to have the problem. The quick >> fix is to simply touch the target file before launching 'virt-clone' >> >> touch /newvm.img >> virt-clone -o existing_vm -n new_vm -o /newvm.img >> >> Cheers! >> > > I'm not seeing this: > > hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel > cd virtinst--devel > ./virt-clone -o xen-pv -n clone-pv -f /idontexist.img > > starts working, for an existing turned off guest named xen-pv on f8. > Is there anything you are doing differently? If so, can you detail it > and post the complete error message? > > Thanks, > Cole > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Feb 2008 17:35:27 +0000 > From: "Daniel P. Berrange" > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: Asrai khn > Cc: fedora-xen at redhat.com > Message-ID: <20080212173527.GK25829 at redhat.com> > Content-Type: text/plain; charset=us-ascii > > On Tue, Feb 12, 2008 at 09:49:55PM +0500, Asrai khn wrote: > >> On Feb 12, 2008 8:24 PM, christf1 wrote: >> >> >>> I tried the latest dev stream, and continued to have the problem. The >>> quick >>> fix is to simply touch the target file before launching 'virt-clone' >>> >>> touch /newvm.img >>> virt-clone -o existing_vm -n new_vm -o /newvm.img >>> >>> >> hi, >> >> i wonders virt-clone will work when one is doing LVM for domUs fro example >> here is mine virutal config file >> > > It won't care what type of storage the original VM is using - it'll > simply read the data off the original disk whether its a file or > block device or LVM vol. > > If you want to use LVM volumes in the destination VM, then you currently > need to manually create the LVM volume ahead of time - virt-clone itself > will not create new LVM volumes for you. This is in the future feature > list though, once libvirt storage management APIs are merged. > > Dan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From itamar at ispbrasil.com.br Thu Feb 14 21:45:40 2008 From: itamar at ispbrasil.com.br (itamar) Date: Thu, 14 Feb 2008 19:45:40 -0200 Subject: [Fedora-xen] xen vif rate limit. Message-ID: <47B4B684.70500@ispbrasil.com.br> anyone know how to put xen vif rate limit to work ? http://xenbits.xensource.com/xen-unstable.hg?rev/dadadf9aeee7 -------------------- Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 From rjones at redhat.com Fri Feb 15 10:26:14 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 15 Feb 2008 10:26:14 +0000 Subject: [Fedora-xen] xen vif rate limit. In-Reply-To: <47B4B684.70500@ispbrasil.com.br> References: <47B4B684.70500@ispbrasil.com.br> Message-ID: <47B568C6.4090703@redhat.com> itamar wrote: > anyone know how to put xen vif rate limit to work ? > > http://xenbits.xensource.com/xen-unstable.hg?rev/dadadf9aeee7 Interesting feature. We don't expose this feature through libvirt, so you'd have to use Xen configuration files directly. Alternatives would including doing class-based queuing in the dom0 using something like 'tc'. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From sa212+fcxen at cyconix.com Sat Feb 16 01:12:49 2008 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Sat, 16 Feb 2008 01:12:49 +0000 Subject: [Fedora-xen] DVD not mountable on FC8 DomU? Message-ID: <47B63891.7050501@cyconix.com> I have an FC8 Dom0 which has identical setups for a Centos 5 and an FC8 DomU (both HVM). However, I can't mount a (file) DVD on the FC8 DomU, but I can do this on the Centos 5 (and various other) DomU's. The FC8 config file contains: disk = [ 'phy:/dev/VG_Guests/FC8-64-001,ioemu:hda,w' , 'file:/dumps/ISO/FC8-64/FC8-64.ISO,hdc:cdrom,r'] The Centos config file is identical, except that the 'FC8' strings are changed. FC8 installed Ok using this cdrom line, and it also boots up from this "DVD" if I change the boot order in the config file. The FC8 DomU /etc/fstab contains: /dev/sr0 /media/dvd auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 This line is identical for the FC8 Dom0, the Centos 5 DomU, and the FC8 DomU, except that Centos 5 uses /dev/hdc instead of /dev/sr0. Any ideas why I can't mount the DVD on the FC8 DomU? mount reports that the filesystem is read-only, so it's getting some of the way there, but it then complains that the options are wrong: > mount: block device /dev/sr0 is write-protected, mounting read-only > mount: wrong fs type, bad option, bad superblock on /dev/sr0, > missing codepage or helper program, or other error I've tried various different options and filesystems without luck. The DVD disk file itself is Ok, because I can still boot up from it. One other thing I tried was changing the cdrom line in the config file to 'file:/dumps/ISO/FC8-64/FC8-64.ISO,sr0:cdrom,r' but this doesn't help - after booting, the FC8 DomU doesn't have a DVD at all in /dev; the /dev/sr0 and /dev/cdrom entries have disappeared. Thanks - Evan From orion at cora.nwra.com Thu Feb 21 22:08:19 2008 From: orion at cora.nwra.com (Orion Poplawski) Date: Thu, 21 Feb 2008 15:08:19 -0700 Subject: [Fedora-xen] rawhide guests on F-8 host Message-ID: <47BDF653.3070905@cora.nwra.com> I just build a F-8 x86_64 guest on a F-8 x86_64 host, then did a yum upgrade to rawhide. Now the domain will not start. Is this expected? [2008-02-21 14:47:07 2774] DEBUG (XendBootloader:100) Launching bootloader as ['/usr/bin/pygrub', '--output=/var/run/xend/boot/xenbl.23509', '/export/data1/xen_disk_fdev_x86_64']. [2008-02-21 14:47:12 2103] DEBUG (XendDomainInfo:1640) _initDomain:shadow_memory=0x0, memory_static_max=0x20000000, memory_static_min=0x0. [2008-02-21 14:47:12 2103] DEBUG (balloon:116) Balloon: 528696 KiB free; need 524288; done. [2008-02-21 14:47:12 2103] INFO (image:129) buildDomain os=linux dom=2 vcpus=2 [2008-02-21 14:47:12 2103] DEBUG (image:198) domid = 2 [2008-02-21 14:47:12 2103] DEBUG (image:199) memsize = 512 [2008-02-21 14:47:12 2103] DEBUG (image:200) image = /var/run/xend/boot/boot_kernel.vlVqWs [2008-02-21 14:47:12 2103] DEBUG (image:201) store_evtchn = 1 [2008-02-21 14:47:12 2103] DEBUG (image:202) console_evtchn = 2 [2008-02-21 14:47:12 2103] DEBUG (image:203) cmdline = ro root=LABEL=/ console=xvc0 [2008-02-21 14:47:12 2103] DEBUG (image:204) ramdisk = /var/run/xend/boot/boot_ramdisk.WvuY8R [2008-02-21 14:47:12 2103] DEBUG (image:205) vcpus = 2 [2008-02-21 14:47:12 2103] DEBUG (image:206) features = [2008-02-21 14:47:12 2103] INFO (XendDomainInfo:1458) createDevice: console : {'devid': 0, 'protocol': 'vt100', 'location': '2', 'uuid': '8ee7025a-6ed3-ba11-1f3d-589420bd567b'} [2008-02-21 14:47:12 2103] DEBUG (DevController:117) DevController: writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/2/0'} to /local/domain/2/device/console/0. [2008-02-21 14:47:12 2103] DEBUG (DevController:119) DevController: writing {'domain': 'xenfdev', 'protocol': 'vt100', 'uuid': '8ee7025a-6ed3-ba11-1f3d-589420bd567b', 'frontend': '/local/domain/2/device/console/0', 'state': '1', 'location': '2', 'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/console/2/0. [2008-02-21 14:47:12 2103] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid': 'a4f5058f-f598-0c07-9bff-9a930b73c629', 'bootable': 1, 'devid': 51712, 'driver': 'paravirtualised', 'dev': 'xvda:disk', 'uname': 'file:/export/data1/xen_disk_fdev_x86_64', 'mode': 'w', 'backend': '0'} [2008-02-21 14:47:12 2103] DEBUG (DevController:117) DevController: writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/2/51712'} to /local/domain/2/device/vbd/51712. [2008-02-21 14:47:12 2103] DEBUG (DevController:119) DevController: writing {'domain': 'xenfdev', 'frontend': '/local/domain/2/device/vbd/51712', 'uuid': 'a4f5058f-f598-0c07-9bff-9a930b73c629', 'dev': 'xvda', 'state': '1', 'params': '/export/data1/xen_disk_fdev_x86_64', 'mode': 'w', 'online': '1', 'frontend-id': '2', 'type': 'file'} to /local/domain/0/backend/vbd/2/51712. [2008-02-21 14:47:12 2103] INFO (XendDomainInfo:1458) createDevice: vif : {'bridge': 'eth0', 'uuid': '8c47fd72-2fe1-da66-236c-59f501b5c465', 'script': 'vif-bridge', 'devid': 0, 'mac': '40:00:00:00:00:01', 'backend': '0'} [2008-02-21 14:47:12 2103] DEBUG (DevController:117) DevController: writing {'mac': '40:00:00:00:00:01', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/2/0'} to /local/domain/2/device/vif/0. [2008-02-21 14:47:12 2103] DEBUG (DevController:119) DevController: writing {'bridge': 'eth0', 'domain': 'xenfdev', 'handle': '0', 'uuid': '8c47fd72-2fe1-da66-236c-59f501b5c465', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/2/device/vif/0', 'mac': '40:00:00:00:00:01', 'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/vif/2/0. [2008-02-21 14:47:13 2103] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '75d3d53b-8a9c-d5bd-cdc4-207b894c6ac6', 'on_reboot': 'restart', 'start_time': '1203630433.0', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'vcpus': '2', 'vcpu_avail': '3', 'image': "(linux (kernel ) (notes (FEATURES 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel') (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 18446744071562067968) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071564189696) (LOADER generic) (SUSPEND_CANCEL 1) (ENTRY 18446744071564165120) (XEN_VERSION xen-3.0)))", 'name': 'xenfdev'} [2008-02-21 14:47:13 2103] DEBUG (XendDomainInfo:956) Storing domain details: {'console/ring-ref': '196480', 'image/entry': '18446744071564165120', 'console/port': '2', 'store/ring-ref': '196481', 'image/loader': 'generic', 'vm': '/vm/75d3d53b-8a9c-d5bd-cdc4-207b894c6ac6', 'control/platform-feature-multiprocessor-suspend': '1', 'image/guest-os': 'linux', 'cpu/1/availability': 'online', 'image/features/writable-descriptor-tables': '1', 'image/virt-base': '18446744071562067968', 'memory/target': '524288', 'image/guest-version': '2.6', 'image/features/supervisor-mode-kernel': '1', 'console/limit': '1048576', 'image/paddr-offset': '18446744071562067968', 'image/hypercall-page': '18446744071564189696', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': '1', 'image/features/writable-page-tables': '1', 'image/features/auto-translated-physmap': '1', 'name': 'xenfdev', 'domid': '2', 'image/xen-version': 'xen-3.0', 'store/port': '1'} [2008-02-21 14:47:13 2103] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2008-02-21 14:47:13 2103] WARNING (XendDomainInfo:1203) Domain has crashed: name=xenfdev id=2. [2008-02-21 14:47:13 2103] ERROR (XendDomainInfo:1333) VM xenfdev restarting too fast (6.067748 seconds since the last restart). Refusing to restart to avoid loops. -- 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 Fri Feb 22 18:26:10 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 22 Feb 2008 18:26:10 +0000 Subject: [Fedora-xen] rawhide guests on F-8 host In-Reply-To: <47BDF653.3070905@cora.nwra.com> References: <47BDF653.3070905@cora.nwra.com> Message-ID: <1203704770.26315.7.camel@muff> Hi, On Thu, 2008-02-21 at 15:08 -0700, Orion Poplawski wrote: > I just build a F-8 x86_64 guest on a F-8 x86_64 host, then did a yum > upgrade to rawhide. Now the domain will not start. Is this expected? Thanks for reporting, I can reproduce here. Try this older kernel for now: http://koji.fedoraproject.org/koji/buildinfo?buildID=32046 More details filed here: https://bugzilla.redhat.com/show_bug.cgi?id=434556 FWIW, I got this stack trace by setting the "on_crash" action for the guest to "preserve" and then when it had crashed, I did: $> /usr/lib64/xen/bin/xenctx -s /boot/System.map-2.6.21.7-2895.fc9xen 1 Cheers, Mark. From orion at cora.nwra.com Fri Feb 22 19:07:29 2008 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 22 Feb 2008 12:07:29 -0700 Subject: [Fedora-xen] rawhide guests on F-8 host In-Reply-To: <1203704770.26315.7.camel@muff> References: <47BDF653.3070905@cora.nwra.com> <1203704770.26315.7.camel@muff> Message-ID: <47BF1D71.9020001@cora.nwra.com> Mark McLoughlin wrote: > Hi, > > On Thu, 2008-02-21 at 15:08 -0700, Orion Poplawski wrote: >> I just build a F-8 x86_64 guest on a F-8 x86_64 host, then did a yum >> upgrade to rawhide. Now the domain will not start. Is this expected? > > Thanks for reporting, I can reproduce here. Try this older kernel for > now: > > http://koji.fedoraproject.org/koji/buildinfo?buildID=32046 Is there any way to install this into my currently dead domain? -- 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 raveenr at gmail.com Fri Feb 22 19:13:26 2008 From: raveenr at gmail.com (Naveen R) Date: Sat, 23 Feb 2008 00:43:26 +0530 Subject: [Fedora-xen] domU stops at --> EXT3 FS on sda1, internal journal Message-ID: <5aa25b3c0802221113m397e05dbsb0c4219721145592@mail.gmail.com> Hello everyone, i am using fedora 7 and tried to run the xen images available at jailtime.org site and was able to start the os but it stops after the following log and will not proceed any further. The state in virt-manager shows its running but the console stops after the following. Can anyone tell me whats the problem. Thanks in advance. Using config file "/xen/debian.4-0/debian.4-0.xen3.cfg". Started domain debian.4-0 Linux version 2.6.20-2925.9.fc7xen ( kojibuilder at xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 000000000bc00000 end: 000000000bc00000 type: 1 Xen: 0000000000000000 - 000000000bc00000 (usable) 0MB HIGHMEM available. 188MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 48128 Normal 48128 -> 48128 HighMem 48128 -> 48128 early_node_map[1] active PFN ranges 0: 0 -> 48128 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 47752 Kernel command line: root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c135f000 soft=c133f000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1804.083 MHz processor. Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1064 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: cc800000-f4ffe000, maxmem 2d7fe000 Memory: 168448k/192512k available (2030k kernel code, 15688k reserved, 1079k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xcc800000 - 0xf4ffe000 ( 647 MB) lowmem : 0xc0000000 - 0xcbc00000 ( 188 MB) .init : 0xc130e000 - 0xc133b000 ( 180 kB) .data : 0xc11fb8b9 - 0xc1309714 (1079 kB) .text : 0xc1000000 - 0xc11fb8b9 (2030 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4512.90 BogoMIPS (lpj=9025800) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources BUG: at kernel/fork.c:994 copy_process() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x16/0x18 [] copy_process+0x195/0x1245 [] do_fork+0x50/0x117 [] kernel_thread+0x8e/0x96 [] __call_usermodehelper+0x2d/0x46 [] run_workqueue+0x89/0x145 [] worker_thread+0xd5/0x102 [] kthread+0xb3/0xdc [] kernel_thread_helper+0x7/0x10 ======================= 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 interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb 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: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 6, 262144 bytes) TCP bind hash table entries: 4096 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7272k freed IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1202740570.370:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks 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 input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface 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 TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Registering block device major 8 blkfront: sda1: barriers enabled blkfront: sda2: barriers enabled USB Universal Host Controller Interface driver v3.0 ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver SCSI subsystem initialized register_blkdev: cannot get major 8 for sd libata version 2.00 loaded. netfront: Initialising virtual ethernet driver. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Adding 65528k swap on /dev/sda2. Priority:-1 extents:1 across:65528k EXT3 FS on sda1, internal journal -------------- next part -------------- An HTML attachment was scrubbed... URL: From deshantm at gmail.com Sat Feb 23 03:08:34 2008 From: deshantm at gmail.com (Todd Deshane) Date: Fri, 22 Feb 2008 22:08:34 -0500 Subject: [Fedora-xen] domU stops at --> EXT3 FS on sda1, internal journal In-Reply-To: <5aa25b3c0802221113m397e05dbsb0c4219721145592@mail.gmail.com> References: <5aa25b3c0802221113m397e05dbsb0c4219721145592@mail.gmail.com> Message-ID: <1e16a9ed0802221908q123941ebg7e4ee655475d2448@mail.gmail.com> Hi, On Fri, Feb 22, 2008 at 2:13 PM, Naveen R wrote: > Hello everyone, i am using fedora 7 and tried to run the xen images > available at jailtime.org site and was able to start the os but it stops > after the following log and will not proceed any further. The state in > virt-manager shows its running but the console stops after the following. > Can anyone tell me whats the problem. Thanks in advance. > Try to Add the following line the guest config file: extra="xencons=tty" Best Regards, Todd > Using config file "/xen/debian.4-0/debian.4-0.xen3.cfg". > Started domain debian.4-0 > Linux version 2.6.20-2925.9.fc7xen ( > kojibuilder at xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 > (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007 > BIOS-provided physical RAM map: > sanitize start > sanitize bail 0 > copy_e820_map() start: 0000000000000000 size: 000000000bc00000 end: > 000000000bc00000 type: 1 > Xen: 0000000000000000 - 000000000bc00000 (usable) > 0MB HIGHMEM available. > 188MB LOWMEM available. > NX (Execute Disable) protection: active > Zone PFN ranges: > DMA 0 -> 48128 > Normal 48128 -> 48128 > HighMem 48128 -> 48128 > early_node_map[1] active PFN ranges > 0: 0 -> 48128 > ACPI in unprivileged domain disabled > Built 1 zonelists. Total pages: 47752 > Kernel command line: root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c135f000 soft=c133f000 > PID hash table entries: 1024 (order: 10, 4096 bytes) > Xen reported: 1804.083 MHz processor. > Console: colour dummy device 80x25 > Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar > ... MAX_LOCKDEP_SUBCLASSES: 8 > ... MAX_LOCK_DEPTH: 30 > ... MAX_LOCKDEP_KEYS: 2048 > ... CLASSHASH_SIZE: 1024 > ... MAX_LOCKDEP_ENTRIES: 8192 > ... MAX_LOCKDEP_CHAINS: 16384 > ... CHAINHASH_SIZE: 8192 > memory used by lock dependency info: 1064 kB > per task-struct memory footprint: 1200 bytes > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) > Software IO TLB disabled > vmalloc area: cc800000-f4ffe000, maxmem 2d7fe000 > Memory: 168448k/192512k available (2030k kernel code, 15688k reserved, > 1079k data, 180k init, 0k highmem) > virtual kernel memory layout: > fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) > pkmap : 0xf5000000 - 0xf5200000 (2048 kB) > vmalloc : 0xcc800000 - 0xf4ffe000 ( 647 MB) > lowmem : 0xc0000000 - 0xcbc00000 ( 188 MB) > .init : 0xc130e000 - 0xc133b000 ( 180 kB) > .data : 0xc11fb8b9 - 0xc1309714 (1079 kB) > .text : 0xc1000000 - 0xc11fb8b9 (2030 kB) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 4512.90 BogoMIPS > (lpj=9025800) > Security Framework v1.0.0 initialized > SELinux: Initializing. > SELinux: Starting in permissive mode > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 512 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 512K (64 bytes/line) > Checking 'hlt' instruction... OK. > SMP alternatives: switching to UP code > Freeing SMP alternatives: 11k freed > Brought up 1 CPUs > Grant table initialized > NET: Registered protocol family 16 > Brought up 1 CPUs > PCI: Fatal: No config space access function found > PCI: setting up Xen PCI frontend stub > Setting up standard PCI resources > BUG: at kernel/fork.c:994 copy_process() > [] show_trace_log_lvl+0x1a/0x2f > [] show_trace+0x12/0x14 > [] dump_stack+0x16/0x18 > [] copy_process+0x195/0x1245 > [] do_fork+0x50/0x117 > [] kernel_thread+0x8e/0x96 > [] __call_usermodehelper+0x2d/0x46 > [] run_workqueue+0x89/0x145 > [] worker_thread+0xd5/0x102 > [] kthread+0xb3/0xdc > [] kernel_thread_helper+0x7/0x10 > ======================= > 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 interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > 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: 2048 (order: 1, 8192 bytes) > TCP established hash table entries: 8192 (order: 6, 262144 bytes) > TCP bind hash table entries: 4096 (order: 5, 131072 bytes) > TCP: Hash tables configured (established 8192 bind 4096) > TCP reno registered > checking if image is initramfs... it is > Freeing initrd memory: 7272k freed > IA-32 Microcode Update Driver: v1.14-xen > audit: initializing netlink socket (disabled) > audit(1202740570.370:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > 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 > input: Macintosh mouse button emulation as /class/input/input0 > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > usbcore: registered new interface driver libusual > usbcore: registered new interface driver hiddev > usbcore: registered new interface 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 > TCP bic registered > Initializing XFRM netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2050 > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762k > Registering block device major 8 > blkfront: sda1: barriers enabled > blkfront: sda2: barriers enabled > USB Universal Host Controller Interface driver v3.0 > ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > libata version 2.00 loaded. > netfront: Initialising virtual ethernet driver. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Adding 65528k swap on /dev/sda2. Priority:-1 extents:1 across:65528k > EXT3 FS on sda1, internal journal > > > -- > 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 raveenr at gmail.com Sat Feb 23 10:36:21 2008 From: raveenr at gmail.com (Naveen R) Date: Sat, 23 Feb 2008 16:06:21 +0530 Subject: [Fedora-xen] domU stops at --> EXT3 FS on sda1, internal journal In-Reply-To: <1e16a9ed0802221908q123941ebg7e4ee655475d2448@mail.gmail.com> References: <5aa25b3c0802221113m397e05dbsb0c4219721145592@mail.gmail.com> <1e16a9ed0802221908q123941ebg7e4ee655475d2448@mail.gmail.com> Message-ID: <5aa25b3c0802230236p3d6881aci128cfb964eb3f867@mail.gmail.com> On Sat, Feb 23, 2008 at 8:38 AM, Todd Deshane wrote: > Hi, > > On Fri, Feb 22, 2008 at 2:13 PM, Naveen R wrote: > > > Hello everyone, i am using fedora 7 and tried to run the xen images > > available at jailtime.org site and was able to start the os but it stops > > after the following log and will not proceed any further. The state in > > virt-manager shows its running but the console stops after the following. > > Can anyone tell me whats the problem. Thanks in advance. > > > > > > Try to Add the following line the guest config file: > > extra="xencons=tty" > > Best Regards, > Todd > > > Thanks Todd i tried that but it the problem was not solved these are the last few lines after adding that.. USB Universal Host Controller Interface driver v3.0 SCSI subsystem initialized register_blkdev: cannot get major 8 for sd netfront: Initialising virtual ethernet driver. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. BUG: at kernel/lockdep.c:1858 trace_hardirqs_on() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x16/0x18 [] trace_hardirqs_on+0xc4/0x143 [] restore_all+0x3b/0x3e ======================= EXT3 FS on sda1, internal journal Adding 65528k swap on /dev/sda2. Priority:-1 extents:1 across:65528k and the list shows this [root at localhost ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 334 1 r----- 292.4 fedora.fc8 2 128 1 -b---- 10.3 -------------- next part -------------- An HTML attachment was scrubbed... URL: From deshantm at gmail.com Sat Feb 23 21:29:16 2008 From: deshantm at gmail.com (Todd Deshane) Date: Sat, 23 Feb 2008 16:29:16 -0500 Subject: [Fedora-xen] domU stops at --> EXT3 FS on sda1, internal journal In-Reply-To: <5aa25b3c0802230236p3d6881aci128cfb964eb3f867@mail.gmail.com> References: <5aa25b3c0802221113m397e05dbsb0c4219721145592@mail.gmail.com> <1e16a9ed0802221908q123941ebg7e4ee655475d2448@mail.gmail.com> <5aa25b3c0802230236p3d6881aci128cfb964eb3f867@mail.gmail.com> Message-ID: <1e16a9ed0802231329w2fde0a76v4802c9af0f93d7aa@mail.gmail.com> On Sat, Feb 23, 2008 at 5:36 AM, Naveen R wrote: > > > On Sat, Feb 23, 2008 at 8:38 AM, Todd Deshane wrote: > > > Hi, > > > > On Fri, Feb 22, 2008 at 2:13 PM, Naveen R wrote: > > > > > Hello everyone, i am using fedora 7 and tried to run the xen images > > > available at jailtime.org site and was able to start the os but it > > > stops after the following log and will not proceed any further. The state in > > > virt-manager shows its running but the console stops after the following. > > > Can anyone tell me whats the problem. Thanks in advance. > > > > > > > > > > > Try to Add the following line the guest config file: > > > > extra="xencons=tty" > > > > Best Regards, > > Todd > > > > > > > Thanks Todd i tried that but it the problem was not solved these are the > last few lines after adding that.. > Since the errors are dealing with irqs, one thing might be to try using noirqbalance. I haven't used it much, but you could try adding noirqbalance to your xen hypervisor (kernel) command line in grub. It might be a general linux command line option that you could add in extra of your domU or even for the dom0 kernel, but I am not sure about the later two. Todd > > USB Universal Host Controller Interface driver v3.0 > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > netfront: Initialising virtual ethernet driver. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > BUG: at kernel/lockdep.c:1858 trace_hardirqs_on() > [] show_trace_log_lvl+0x1a/0x2f > [] show_trace+0x12/0x14 > [] dump_stack+0x16/0x18 > [] trace_hardirqs_on+0xc4/0x143 > [] restore_all+0x3b/0x3e > ======================= > EXT3 FS on sda1, internal journal > Adding 65528k swap on /dev/sda2. Priority:-1 extents:1 across:65528k > > and the list shows this > > [root at localhost ~]# xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 334 1 r----- > 292.4 > fedora.fc8 2 128 1 -b---- > 10.3 > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From NAGIN at il.ibm.com Mon Feb 25 09:36:47 2008 From: NAGIN at il.ibm.com (Kenneth Nagin) Date: Mon, 25 Feb 2008 11:36:47 +0200 Subject: [Fedora-xen] failure to retrieve ministrg2.img in guest boot Message-ID: I successful created a XEN guest in fedora 8. However, the guest will not boot. The failure occurs shortly after setting up the IP network settings. The error message claims that it can not retrieve ministg2.img. "failure to retrieve http://download.fedora.redhat.com //pub/fedora/linux/releases/8/Fedora/i386/os/ministrg2.img." Notice that the error message reads "//pub". However, the my input for the path had only one forward slash.. Of course, I could not have gotten this far in the install with a faulty path. In xend-debug.log read: File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: Thanks in advance for any help on how to resolve this issue.. Kenneth Nagin From markmc at redhat.com Mon Feb 25 10:22:31 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 25 Feb 2008 10:22:31 +0000 Subject: [Fedora-xen] rawhide guests on F-8 host In-Reply-To: <47BF1D71.9020001@cora.nwra.com> References: <47BDF653.3070905@cora.nwra.com> <1203704770.26315.7.camel@muff> <47BF1D71.9020001@cora.nwra.com> Message-ID: <1203934951.13831.23.camel@muff> Hi, This build should fix the problem for you: http://koji.fedoraproject.org/koji/buildinfo?buildID=39764 On Fri, 2008-02-22 at 12:07 -0700, Orion Poplawski wrote: > Mark McLoughlin wrote: > > Hi, > > > > On Thu, 2008-02-21 at 15:08 -0700, Orion Poplawski wrote: > >> I just build a F-8 x86_64 guest on a F-8 x86_64 host, then did a yum > >> upgrade to rawhide. Now the domain will not start. Is this expected? > > > > Thanks for reporting, I can reproduce here. Try this older kernel for > > now: > > > > http://koji.fedoraproject.org/koji/buildinfo?buildID=32046 > > Is there any way to install this into my currently dead domain? Well, hopefully you still have the F-8 kernel installed and you can just run that e.g. by doing "virsh console foo" before the grub timeout expires and choosing the older kernel. Alternatively, you could mount the /boot partition and change the default in grub.conf e.g. $> losetup /dev/loop0 /xen/foo.img $> kpartx -av /dev/loop0 $> mount /dev/mapper/loop0p1 /tmp/foo $> emacs /boot/grub/grub.conf $> umount /tmp/foo $> kpartx -d /dev/loop0 $> losetup -d /dev/loop0 Once you've booted with a working kernel, then you can upgrade to the newer one. If you don't have any working kernel in the domain, you could try something like this: $> losetup /dev/loop0 /xen/foo.img $> kpartx -av /dev/loop0 $> vgscan $> vgchange -ay VolGroup00 $> mount /dev/VolGroup00/LogVol00 /tmp/foo $> mount /dev/mapper/loop0p1 /tmp/foo/boot $> chroot /tmp/foo yum --nogpgcheck localinstall kernel-xen-...rpm $> chroot mkinitrd --with xenblk -f /boot/initrd-2.6.21.7....rpm 2.6.21.7... $> umount /tmp/foo/boot $> umount /tmp/foo $> vgchange -an VolGroup00 $> kpartx -d /dev/loop0 $> losetup -d /dev/loop0 Or maybe easier, boot the dead domain with a rescue CD. Cheers, Mark. From terry at gotzon.com Mon Feb 25 16:40:23 2008 From: terry at gotzon.com (Terry Gotzon) Date: Mon, 25 Feb 2008 11:40:23 -0500 Subject: [Fedora-xen] How to re-reading the xen guest config file Message-ID: What I am trying to do is add additional memory or CPU's to a running xen guest that is already at the maximum allocated from build time. Currently, I edit the config file for the guest and increase the memory or cpu and then shutdown and start the VM. What I would like to do is re-read the config file without having to restart the server. Does anyone know of a way to do this, if possible? Thanks Terry -------------- next part -------------- An HTML attachment was scrubbed... URL: From yabraham2 at gmail.com Tue Feb 26 15:26:31 2008 From: yabraham2 at gmail.com (yonas Abraham) Date: Tue, 26 Feb 2008 10:26:31 -0500 Subject: [Fedora-xen] VCL for xen? Message-ID: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> Hi, I am looking for open source application that does similar to NC states Virtual Computing Library (VCL) for xen management. I have seen ovirt.org, but it seems to require hardware virtualization, which I don't have. any pointers will be appreciated. /yonas From m3freak at thesandhufamily.ca Wed Feb 27 02:15:51 2008 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Tue, 26 Feb 2008 21:15:51 -0500 Subject: [Fedora-xen] domU auto start order Message-ID: <1204078551.13088.3.camel@krs.systemsaligned.com> Hi All, Is it possible to auto start domU's listed in /etc/xen/auto in a particular order? I imagine it is, but my reading comprehension or my searching skills suck, because I can't find anything about this. Thanks, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.22.14-72.fc6 i686 GNU/Linux 21:12:35 up 1 day, 51 min, 2 users, load average: 1.69, 0.73, 0.49 From bhkwan at thoughtworks.com Wed Feb 27 02:27:17 2008 From: bhkwan at thoughtworks.com (Barrow H Kwan) Date: Tue, 26 Feb 2008 20:27:17 -0600 Subject: [Fedora-xen] domU auto start order In-Reply-To: <1204078551.13088.3.camel@krs.systemsaligned.com> Message-ID: this is how I did. files in /etc/xen/auto is just a symbolic link to /etc/xen. eg /etc/xen/myvm01, /etc/xen/myvm02, /etc/xen/myvm03, to start the VM in the order of 02 -> 01 -> 03, I create a link under /etc/xen/auto /etc/xen/auto/1myvm02 -> /etc/xen/myvm02 /etc/xen/auto/2myvm01 -> /etc/xen/myvm01 /etc/xen/auto/3myvm03 -> /etc/xen/myvm03 I think there is a better way to do it... ================= Barrow Kwan ThoughtWorks, Inc. New from ThoughtWorks: Mingle, an Agile project management application. Mingle. Project Intelligence. Powerfully Simple. More at http://studios.thoughtworks.com Kanwar Ranbir Sandhu Sent by: fedora-xen-bounces at redhat.com 02/26/08 06:15 PM To fedora-xen at redhat.com cc Subject [Fedora-xen] domU auto start order Hi All, Is it possible to auto start domU's listed in /etc/xen/auto in a particular order? I imagine it is, but my reading comprehension or my searching skills suck, because I can't find anything about this. Thanks, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.22.14-72.fc6 i686 GNU/Linux 21:12:35 up 1 day, 51 min, 2 users, load average: 1.69, 0.73, 0.49 -- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5256 bytes Desc: S/MIME Cryptographic Signature URL: From sputhenp at redhat.com Thu Feb 28 14:43:43 2008 From: sputhenp at redhat.com (Sadique Puthen) Date: Thu, 28 Feb 2008 20:13:43 +0530 Subject: [Fedora-xen] How to re-reading the xen guest config file In-Reply-To: References: Message-ID: <47C6C89F.2020600@redhat.com> Terry Gotzon wrote: > What I am trying to do is add additional memory or CPU's to a running > xen guest that is already at the maximum allocated from build time. > Currently, I edit the config file for the guest and increase the > memory or cpu and then shutdown and start the VM. If the guest has reached "maxmem" configured via the configuration file, you should restart your guest to allocate more memory. What you can do is configure "maxmem" to the maximum available memory and adjust the current memory when you need it using "virsh setmem " 1048576 512000 Here memory is the maxmemory and currentMemory is what the guest has been allocated currently. --Sadique > What I would like to do is re-read the config file without having to > restart the server. Does anyone know of a way to do this, if possible? > > Thanks > Terry > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From aklspec at yahoo.com Thu Feb 28 18:00:29 2008 From: aklspec at yahoo.com (Akl Spec) Date: Thu, 28 Feb 2008 10:00:29 -0800 (PST) Subject: [Fedora-xen] no guest configuration file in /etc/xen Message-ID: <735874.54139.qm@web45706.mail.sp1.yahoo.com> Hi All, I am newbie to Xen. I installed xen-3.1.0-13.fc8 on fc8 and configured two fedora guest domains, one with virt-manager and the other with virt-installer. Both the virtual servers are up and i can boot them successfully, but both the installation didn't create the guest configuration file in /etc/xen directory(docs says configuration file will be created here). Can anybody please help me to find out those files?? Thanks in advance. AKL --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aclark at digitalfairway.com Thu Feb 28 18:07:28 2008 From: aclark at digitalfairway.com (Aaron Clark) Date: Thu, 28 Feb 2008 13:07:28 -0500 Subject: [Fedora-xen] no guest configuration file in /etc/xen In-Reply-To: <735874.54139.qm@web45706.mail.sp1.yahoo.com> References: <735874.54139.qm@web45706.mail.sp1.yahoo.com> Message-ID: <47C6F860.3090900@digitalfairway.com> Akl Spec wrote: > Hi All, > > I am newbie to Xen. I installed xen-3.1.0-13.fc8 on fc8 and configured > two fedora guest domains, one with virt-manager and the other with > virt-installer. Both the virtual servers are up and i can boot them > successfully, but both the installation didn't create the guest > configuration file in /etc/xen directory(docs says configuration file > will be created here). > > Can anybody please help me to find out those files?? > > Thanks in advance. > > AKL I believe in 3.1 the configuration files were moved into an internal configuration database instead. There should be something regarding this in the release notes on xen.org. HTH, Aaron From mdehaan at redhat.com Thu Feb 28 22:44:33 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Thu, 28 Feb 2008 17:44:33 -0500 Subject: [Fedora-xen] VCL for xen? In-Reply-To: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> References: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> Message-ID: <47C73951.3080902@redhat.com> yonas Abraham wrote: > Hi, > > I am looking for open source application that does similar to NC > states Virtual Computing Library (VCL) for xen management. I have > seen ovirt.org, but it seems to require hardware virtualization, which > I don't have. > > any pointers will be appreciated. > > /yonas > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > If you are happy with some lower level tooling (and building some of the stuff yourself), Func offers remote virt control using libvirt modules for Xen (incl. paravirt) as well as KVM, as well as remote hooks for installation via koan (see below) -- and is very interested in new modules / tweaks from the people who use it. https://fedorahosted.org/func You can also use Cobbler/koan to provide the missing provisioning half (so Func for control and Cobbler for installation) http://cobbler.et.redhat.com I would suspect eventually ovirt will support other virt types since libvirt makes this possible. It's also planning on integrating Cobbler support in the future. These solutions are more CLI/batch/scripting oriented though if you need to customize your own solution for specific things (like the VCL case) you may want that anyway -- I'm not too familiar with the VCL to say for sure. --Michael From mdehaan at redhat.com Thu Feb 28 22:45:57 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Thu, 28 Feb 2008 17:45:57 -0500 Subject: [Fedora-xen] VCL for xen? In-Reply-To: <47C73951.3080902@redhat.com> References: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> <47C73951.3080902@redhat.com> Message-ID: <47C739A5.5030606@redhat.com> Michael DeHaan wrote: > yonas Abraham wrote: >> Hi, >> >> I am looking for open source application that does similar to NC >> states Virtual Computing Library (VCL) for xen management. I have >> seen ovirt.org, but it seems to require hardware virtualization, which >> I don't have. >> >> any pointers will be appreciated. >> >> /yonas >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> > > If you are happy with some lower level tooling (and building some of > the stuff yourself), Func offers > remote virt control using libvirt modules for Xen (incl. paravirt) as > well as KVM, as well as remote hooks > for installation via koan (see below) -- and is very interested in new > modules / tweaks from the people who use it. > > https://fedorahosted.org/func > > You can also use Cobbler/koan to provide the missing provisioning half > (so Func for control and Cobbler for installation) > > http://cobbler.et.redhat.com > > I would suspect eventually ovirt will support other virt types since > libvirt makes this possible. It's also planning on integrating > Cobbler support in the future. > > These solutions are more CLI/batch/scripting oriented though if you > need to customize your own solution for specific > things (like the VCL case) you may want that anyway -- I'm not too > familiar with the VCL to say for sure. > > --Michael > > I should add that Cobbler /does/ have a Web user interface. Func does have one in development though it has a ways to go. Still usable from the command line/API/etc. From sa212+fcxen at cyconix.com Fri Feb 29 11:42:31 2008 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Fri, 29 Feb 2008 11:42:31 +0000 Subject: [Fedora-xen] Prebuilt images for non-Fedora DomU's? Message-ID: <47C7EFA7.5030202@cyconix.com> I've just had a go at installing the Debian 4.0 jailtime image on a Fedora 8 Dom0, but had no luck. I've just posted on the xen list about this, but the summary is that the debian image has an empty /boot directory, the jailtime config file doesn't use pygrub, and the config file expects to find "/boot/vmlinuz-2.6-xen" on the Dom0, which of course I haven't got on Fedora 8. Has anyone had any luck installing prebuilt "foreign" distributions on Fedora 8, or do you all roll your own DomU's? If you have found any usable images, can you give me a URL? I'm looking for Debian 4.0 or Centos 5.0 or, failing that, Ubuntu 6.0.6 or Gentoo 2006.1. I haven't tried virt-install because the FC7 docs say "With Fedora 7, installation of Fedora 7 guests using anaconda is supported". Presumably this means that it doesn't work for non-Fedora DomU's? Thanks - Evan