From kwan at digitalhermit.com Sat Apr 1 00:17:10 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Fri, 31 Mar 2006 19:17:10 -0500 (EST) Subject: [Fedora-xen] HD corruption?? Message-ID: <28707.64.132.126.227.1143850630.squirrel@digitalhermit.com> Not sure at this moment if it's the XenU kernel or something with LVM... Yesterday I installed the Xen0 kernel on my primary desktop to try to test xen migration. I built out a couple 4G logical volumes and ran a couple kickstart installations. At one point I tried to expand my /home filesystem (it's on a /dev/rootvg/home_lv LVM partition). It failed, and then my /home seems to have been remounted as read-only. Long story short, on a reboot the fsck.ext3 informs that the filesystem is larger than the disk and fsck just gives hundreds of errors. I'm going to blow away that LV and try to rebuild it tomorrow, but just curious if anyone else has seen any disk corruption? -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From sct at redhat.com Sat Apr 1 02:39:25 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 31 Mar 2006 21:39:25 -0500 Subject: [Fedora-xen] Problems with Xen + FC5 + Thinkpad In-Reply-To: <20060329143317.7efcd1bc@aud.vb.futz.org> References: <442AB732.1070208@redhat.com> <20060329143317.7efcd1bc@aud.vb.futz.org> Message-ID: <1143859166.3383.1.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-03-29 at 14:33 -0500, Robert Story wrote: > Did you do the part about updating grub to include 'init 3' to disable X? If > so, go back and delete the 'init' (you just need '3'). This fixed the dom0 > kernel hang I had. > I asked someone in the #fedora irc channel to fix this, but it's still there. Please open a bugzilla for this so we can look into it. There is nothing fundamentally incompatible between Xen and X: my Xen desktop, running X, had an uptime of over 8 days when I shut it down earlier today. init 3 is *not* needed in general; if you have a specific hardware config that isn't working under Xen with X, then that's something that needs debugged. Thanks, Stephen From sct at redhat.com Sat Apr 1 02:41:01 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 31 Mar 2006 21:41:01 -0500 Subject: [Fedora-xen] Problems with e1000 drivers with kernel 2.6.15... In-Reply-To: <2d90b1800603290934o7257a8aw1f8801d158def919@mail.gmail.com> References: <2d90b1800603290934o7257a8aw1f8801d158def919@mail.gmail.com> Message-ID: <1143859262.3383.3.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-03-29 at 19:34 +0200, Thomas Uhl wrote: > I am testing xen on a preproduction Intel box. The standard kernel of > FC5 (2.6.15-1.2054) does not detect the embedded e1000 NICs in my > setup. So I tried kernel 2.6.16-1.2102 from rawhide. It worked. When > will we see a "xenified" 2.6.16 kernel in rawhide? When It's Done. :) Upstream linux-2.6 has merged a bunch of stuff recently which conflicts with Xen, but we're sorting out the resulting tangle at present. --Stephen From sct at redhat.com Sat Apr 1 02:43:12 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 31 Mar 2006 21:43:12 -0500 Subject: [Fedora-xen] Disk problems on FC5 In-Reply-To: <442BCBB4.7090906@redhat.com> References: <442BCBB4.7090906@redhat.com> Message-ID: <1143859393.3383.5.camel@orbit.scot.redhat.com> Hi, On Thu, 2006-03-30 at 07:14 -0500, Brad Smith wrote: > I set up Xen on a freshly-installed FC5 system, configured the guest using xenguest-install.py and > then began an installation via VNC. However, as soon as I got to the partitioning phase I received > an error that the partition table for my disk couldn't be read. I opted to ignore this as I've seen > that error even on real systems and have proceeded without incident. However, the installer > continued to produce errors about not being able to find the disk, being unable to read the > partition table, etc and eventually just died. Looking at the disk file I told Xen to create (I gave > it 4096 as the size) it appears to have a size of 0. Is that the way it should be? No! The disk size is specified in GB, though, so you just asked for a 4TB file, which is beyond ext3's tiny little brains. Try something a little smaller. :-) Yes, we should deal with this error better. --Stephen From sct at redhat.com Sat Apr 1 02:47:35 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 31 Mar 2006 21:47:35 -0500 Subject: [Fedora-xen] HD corruption?? In-Reply-To: <28707.64.132.126.227.1143850630.squirrel@digitalhermit.com> References: <28707.64.132.126.227.1143850630.squirrel@digitalhermit.com> Message-ID: <1143859656.3383.9.camel@orbit.scot.redhat.com> Hi, On Fri, 2006-03-31 at 19:17 -0500, Kwan Lowe wrote: > Yesterday I installed the Xen0 kernel on my primary desktop to try to test xen > migration. I built out a couple 4G logical volumes and ran a couple kickstart > installations. At one point I tried to expand my /home filesystem (it's on a > /dev/rootvg/home_lv LVM partition). It failed, and then my /home seems to have been > remounted as read-only. Long story short, on a reboot the fsck.ext3 informs that the > filesystem is larger than the disk and fsck just gives hundreds of errors. Do you have any record of exactly what went wrong --- kernel error logs, etc? It sounds as if the growth of the LV wasn't propagated to disk, which is bad news. Was /home exported to any of the guests? > I'm going > to blow away that LV and try to rebuild it tomorrow, but just curious if anyone else > has seen any disk corruption? I haven't seen *any* such problems during all the time I've been using and developing on Xen. But virtual storage does give you new ways of shooting yourself in the foot, so there may well be missing safety-nets in some of the tools surrounding Xen. We'd need to work out what went wrong first here to determine how best to guard against it. Cheers, Stephen From yongkang.you at intel.com Sat Apr 1 03:27:41 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Sat, 1 Apr 2006 11:27:41 +0800 Subject: [Fedora-xen] Problem booting jailtime images Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20CB@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: Murat I??k [mailto:muratisik at bilgiguvenlik.com] >Sent: 2006?4?1? 4:04 >To: fedora-xen at redhat.com >Cc: You, Yongkang >Subject: RE: [Fedora-xen] Problem booting jailtime images > >Hello, > > >[root at muratisik fedora]# cat fedora.fc4.xen.cfg >kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xen0" I didn't try to use a xen0 kernel to boot xenU before. I am not sure if it is okay. But I think you can try vmlinuz-2.6.16-1.2080_FC5xenU which comes from another Xen RPMs. >memory = 128 >name = "fedora.fc4" >nics = 1 >dhcp = "dhcp" >disk = ['file:/xen/fedora/fedora.fc4.img,sda1,w', >'file:/xen/fedora/fedora.swap,sda2,w'] Although I think this config won't cause the error you meet, I suggest firstly let us try only use 1 disk for "/" and remove the swap disk config in here and fstab. If it can boot, then try to add swap back. :) >root = "/dev/sda1 ro" > >[root at muratisik fedora]# mount -o loop fedora.fc4.img /mnt/ > >[root at muratisik fedora]# cat /mnt/etc/fstab ># This file is edited by fstab-sync - see 'man fstab-sync' for details >/dev/sda1 / ext3 defaults 1 1 >/dev/sda2 none swap sw 0 0 >none /dev/pts devpts >gid=5,mode=620 0 0 >none /dev/shm tmpfs defaults 0 0 >none /proc proc defaults 0 0 >none /sys sysfs defaults 0 0 > >[root at muratisik fedora]# umount /mnt/ > >[root at muratisik fedora]# xm create fedora.fc4.xen.cfg -c > >and the error appears: > >... >md: ... autorun DONE. >VFS: Cannot open root device "sda1" or unknown-block(0,0) >Please append a correct "root=" boot option >Kernel panic - not syncing: VFS: Unable to mount root fs on >unknown-block(0,0) > [] panic+0x3c/0x190 > [] mount_block_root+0x19c/0x1aa > [] mount_root+0x49/0x4e > [] prepare_namespace+0xc0/0xf1 > [] init+0x23e/0x2fe > [] init+0x0/0x2fe > [] kernel_thread_helper+0x5/0xb > > >Then I changed both image's fstab to hda1 and hda2 , also editted cfg to >match hdas. and I get the same error. any ideas? is there any more >information (log, config, debug vs.) I can supply? Maybe you can try another thing. Is your image file's dev/ folder empty? If so, please mount the xenU image file, and copy your local /dev/* to image file's dev/ . My xenU dev/ has all device file prepared. ;) > >have a nice day. > Best Regards, Yongkang (Kangkang) ?? From brads at redhat.com Sat Apr 1 16:04:23 2006 From: brads at redhat.com (Brad Smith) Date: Sat, 01 Apr 2006 11:04:23 -0500 Subject: [Fedora-xen] xend (still) hanging on thinkpad T30 under fc5 Message-ID: <442EA487.3000702@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I posted earlier about xend hanging when I tried to boot the xen0 kernel under FC5 on my Thinkpad T30. I've tried again with a fresh install (last time it was an upgrade) and selinux disabled (last time was set to permissive) and I'm still having the same problem: Booting into runlevel 3 with rhgb off, the boot process hangs at "Starting xend" after a message about the bridging firewall. The keyboard is still responsive so it's not the OS hanging, just xend. Attached is the xend.log generated by attempting to boot (xend-debug.log is empty). If anyone can offer assistance I'd really appreciate it. - --Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFELqRoDvp49DvQ8kcRAq7kAJ9yp59M+pUJbpKTwPx2Aoo2Z/nQOwCcCsK9 h90iuYpU1XSb0BxaZqjMCrk= =btkn -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: text/x-log Size: 1513 bytes Desc: not available URL: From hiro24 at gmail.com Sat Apr 1 20:40:21 2006 From: hiro24 at gmail.com (Chris Hall) Date: Sat, 1 Apr 2006 15:40:21 -0500 Subject: [Fedora-xen] SIGSEGV on xenguest-install.py Message-ID: Anybody seen this yet? I tried googling and got nothing. I run through the xenguest-install.py while booted up to the xen0 kernel provided with FC5. It asks all the normal questions, and begins the text based installation. I get somewhere past network configuration (doesn't seem to matter what I put here) and while it's trying to determine host and domain information, after a few seconds to up to a minute or two later, it seg faults out with an error "Loader Received SIGSEGV!", and shuts down the virtual machine in the window. /var/log/xend-debug.log reveals the following: File "/usr/sbin/xend", line 93, in main return daemon.start() File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 199, in start self.run(w and os.fdopen(w, 'w') or None) File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 301, in run status.write('1') ValueError: I/O operation on closed file Any ideas what could be causing this? I've thus far tried removing and reinstalling the xen kernel and the xen package. Didn't seem to work. -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From sshinde at redhat.com Sat Apr 1 23:30:50 2006 From: sshinde at redhat.com (Shashhin Shinde) Date: Sun, 02 Apr 2006 01:30:50 +0200 Subject: [Fedora-xen] HD corruption?? In-Reply-To: <1143859656.3383.9.camel@orbit.scot.redhat.com> References: <28707.64.132.126.227.1143850630.squirrel@digitalhermit.com> <1143859656.3383.9.camel@orbit.scot.redhat.com> Message-ID: <442F0D2A.9020207@redhat.com> Hi , I had an interesting observation the other day with FC5 and xen. I create a 512M Logical volume and exported it to xen guest. When I ran fdisk on it the size of the logical volume shown inside guest was 536MB , which was more than original size of exported logical volume. lvdisplay on the host confirmed the size to be 512MB Thought might be interesting in this context. Regards, Shashin. Stephen C. Tweedie wrote: > Hi, > > On Fri, 2006-03-31 at 19:17 -0500, Kwan Lowe wrote: > > >> Yesterday I installed the Xen0 kernel on my primary desktop to try to test xen >> migration. I built out a couple 4G logical volumes and ran a couple kickstart >> installations. At one point I tried to expand my /home filesystem (it's on a >> /dev/rootvg/home_lv LVM partition). It failed, and then my /home seems to have been >> remounted as read-only. Long story short, on a reboot the fsck.ext3 informs that the >> filesystem is larger than the disk and fsck just gives hundreds of errors. >> > > Do you have any record of exactly what went wrong --- kernel error logs, > etc? It sounds as if the growth of the LV wasn't propagated to disk, > which is bad news. Was /home exported to any of the guests? > > >> I'm going >> to blow away that LV and try to rebuild it tomorrow, but just curious if anyone else >> has seen any disk corruption? >> > > I haven't seen *any* such problems during all the time I've been using > and developing on Xen. But virtual storage does give you new ways of > shooting yourself in the foot, so there may well be missing safety-nets > in some of the tools surrounding Xen. We'd need to work out what went > wrong first here to determine how best to guard against it. > > Cheers, > Stephen > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From okajima at digitalinfra.co.jp Sun Apr 2 11:49:00 2006 From: okajima at digitalinfra.co.jp (Jun OKAJIMA) Date: Sun, 02 Apr 2006 20:49:00 +0900 Subject: [Fedora-xen] pygrub failed Message-ID: <200604021149.AA00968@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Hello, FC5 Xen folks. When I tried to install Xen3.0 on FC5, it has failed in making a guest OS image. It seems to be because that pygrub.py can not recognize my dom0 menu.lst correctly. Or, maybe it is wrong that I used LVM, but this is default of current FC5 (Why?). BTW, I am testing FC5 Xen dom0 on VMware 5.5.1, and it runs, although many guys have reported that it has a lot of trouble. For me, the problem is not VMware or dom0, but installer of domU. Any help? --- Okajima, Jun. Tokyo, Japan. --------------------------- [root at localhost ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 164 1 r----- 427.8 [root at localhost ~]# xenguest-install.py What is the name of your virtual machine? FC5_1 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /XEN/FC5_1.img What is the install location? http://ring.sakura.ad.jp/archives/linux/fedora/linux/core/5/i386/os/ Starting install... Using config file "/etc/xen/FC5_1". Error: Error creating domain: The privileged domain did not balloon! If your install has exited, you can restart your guest by running 'xm create -c FC5_1'. Otherwise, you can reconnect to the console by running 'xm console FC5_1' [root at localhost ~]# xm create -c FC5_1 Using config file "/etc/xen/FC5_1". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 139, in get_config raise RuntimeError, "Unable to read filesystem" RuntimeError: Unable to read filesystem Error: Boot loader didn't return any data! [root at localhost ~]# cat /etc/xen/ FC5_1 scripts/ xmexample.vti auto/ xend-config.sxp xmexample1 qemu-ifup xmexample.hvm xmexample2 [root at localhost ~]# cat /etc/xen/FC5_1 # Automatically generated xen config file name = "FC5_1" memory = "256" disk = [ 'file:/XEN/FC5_1.img,xvda,w' ] vif = [ 'mac=00:16:3e:60:8f:ea' ] bootloader="/usr/bin/pygrub" on_reboot = 'restart' on_crash = 'restart' [root at localhost ~]# cat /boot/grub/menu.lst # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=2 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.16-1.2080_FC5xenU) root (hd0,0) kernel /vmlinuz-2.6.16-1.2080_FC5xenU ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.16-1.2080_FC5xenU.img title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol00 rhgb quiet module /initrd-2.6.16-1.2080_FC5xen0.img title Fedora Core (2.6.16-1.2080_FC5) root (hd0,0) kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.16-1.2080_FC5.img title Fedora Core (2.6.15-1.2054_FC5) root (hd0,0) kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.15-1.2054_FC5.img [root at localhost ~]# cat /proc/partitions major minor #blocks name 3 0 8388608 hda 3 1 104391 hda1 3 2 8281507 hda2 253 0 7831552 dm-0 253 1 393216 dm-1 [root at localhost ~]# xm dmesg __ __ _____ ___ ___ \ \/ /___ _ __ |___ / / _ \ / _ \ \ // _ \ '_ \ |_ \| | | | | | | / \ __/ | | | ___) | |_| | |_| | /_/\_\___|_| |_| |____(_)___(_)___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0.0 (bhcompile at build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) Tue Mar 28 03:35:03 EST 2006 Latest ChangeSet: unavailable (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009f800 (usable) (XEN) 000000000009f800 - 00000000000a0000 (reserved) (XEN) 00000000000dc000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000000bef0000 (usable) (XEN) 000000000bef0000 - 000000000befc000 (ACPI data) (XEN) 000000000befc000 - 000000000bf00000 (ACPI NVS) (XEN) 000000000bf00000 - 000000000c000000 (usable) (XEN) 00000000fec00000 - 00000000fec10000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000fffe0000 - 0000000100000000 (reserved) (XEN) System RAM: 191MB (196156kB) (XEN) Xen heap: 10MB (10344kB) (XEN) Using scheduler: Simple EDF Scheduler (sedf) (XEN) PAE disabled. (XEN) found SMP MP-table at 000f6ce0 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f6c70 (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x0bef7c02 (XEN) ACPI: FADT (v001 INTEL 440BX 0x06040000 PTL 0x000f4240) @ 0x0befbf14 (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @ 0x0befbf88 (XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x0befbfd8 (XEN) ACPI: DSDT (v001 PTLTD Custom 0x06040000 MSFT 0x0100000d) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 15:12 APIC version 17 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Initializing CPU#0 (XEN) Detected 1599.572 MHz processor. (XEN) CPU0: AMD Flush Filter disabled (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 128K (64 bytes/line) (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: AMD Sempron(tm) Processor 2600+ stepping 02 (XEN) Total of 1 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 1 CPUs (XEN) Machine check exception polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Domain 0 kernel supports features = { 0000001f }. (XEN) Domain 0 kernel requires features = { 00000000 }. (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0a000000->0b000000 (37859 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c0455b7c (XEN) Init. ramdisk: c0456000->c07e2200 (XEN) Phys-Mach map: c07e3000->c080bf8c (XEN) Start info: c080c000->c080d000 (XEN) Page tables: c080d000->c0811000 (XEN) Boot stack: c0811000->c0812000 (XEN) TOTAL: c0000000->c0c00000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Dom0 has maximum 1 VCPUs (XEN) Initrd len 0x38c200, start at 0xc0456000 (XEN) Scrubbing Free RAM: ..done. (XEN) Xen trace buffers: disabled (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen). [root at localhost ~]# cat /etc/redhat-release Fedora Core release 5 (Bordeaux) [root at localhost ~]# From winston at stdout.org Sun Apr 2 16:28:38 2006 From: winston at stdout.org (Winston Chang) Date: Sun, 2 Apr 2006 12:28:38 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: <200604021149.AA00968@bbb-jz5c7z9hn9y.digitalinfra.co.jp> References: <200604021149.AA00968@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: I believe the error "Error: Error creating domain: The privileged domain did not balloon!" happens when you don't have enough available memory for the domU to boot. The xenguest-install.py script tells you to restart the domain by running "xm create -c xxxx', but I think the error message is just a generic one that is printed if the script crashes out, and it it is the wrong thing to do in this case. When I had the same problem, I had to allocate less memory to dom0 and re-run the xenguest-install script. I see you have about 196MB of RAM. Since the FC5 script needs 256MB of RAM, I don't think you'll be able to install it unless you increase the amount of RAM you have. But since the machine is a virtual one in VMWare, this shouldn't be too difficult. --Winston On Apr 2, 2006, at 7:49 AM, Jun OKAJIMA wrote: > > Hello, FC5 Xen folks. > > When I tried to install Xen3.0 on FC5, it has failed in making a > guest OS image. > It seems to be because that pygrub.py can not recognize my dom0 > menu.lst correctly. > Or, maybe it is wrong that I used LVM, but this is default of > current FC5 (Why?). > > BTW, I am testing FC5 Xen dom0 on VMware 5.5.1, and it runs, although > many guys have reported that it has a lot of trouble. > For me, the problem is not VMware or dom0, but installer of domU. > > Any help? > > --- Okajima, Jun. Tokyo, Japan. > > > > --------------------------- > > [root at localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 164 1 r----- 427.8 > [root at localhost ~]# xenguest-install.py > What is the name of your virtual machine? FC5_1 > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /XEN/FC5_1.img > What is the install location? http://ring.sakura.ad.jp/archives/ > linux/fedora/linux/core/5/i386/os/ > > > Starting install... > Using config file "/etc/xen/FC5_1". > Error: Error creating domain: The privileged domain did not balloon! > If your install has exited, you can restart your guest by running > 'xm create -c FC5_1'. Otherwise, you can reconnect to the console > by running 'xm console FC5_1' > [root at localhost ~]# xm create -c FC5_1 > Using config file "/etc/xen/FC5_1". > Traceback (most recent call last): > File "/usr/bin/pygrub", line 256, in ? > cf = get_config(file, isconfig) > File "/usr/bin/pygrub", line 139, in get_config > raise RuntimeError, "Unable to read filesystem" > RuntimeError: Unable to read filesystem > Error: Boot loader didn't return any data! > [root at localhost ~]# cat /etc/xen/ > FC5_1 scripts/ xmexample.vti > auto/ xend-config.sxp xmexample1 > qemu-ifup xmexample.hvm xmexample2 > [root at localhost ~]# cat /etc/xen/FC5_1 > # Automatically generated xen config file > name = "FC5_1" > memory = "256" > disk = [ 'file:/XEN/FC5_1.img,xvda,w' ] > vif = [ 'mac=00:16:3e:60:8f:ea' ] > bootloader="/usr/bin/pygrub" > > on_reboot = 'restart' > on_crash = 'restart' > [root at localhost ~]# cat /boot/grub/menu.lst > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to > this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 > # initrd /initrd-version.img > #boot=/dev/hda > default=2 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora Core (2.6.16-1.2080_FC5xenU) > root (hd0,0) > kernel /vmlinuz-2.6.16-1.2080_FC5xenU ro root=/dev/ > VolGroup00/LogVol00 rhgb quiet > initrd /initrd-2.6.16-1.2080_FC5xenU.img > title Fedora Core (2.6.16-1.2080_FC5xen0) > root (hd0,0) > kernel /xen.gz-2.6.16-1.2080_FC5 > module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ > VolGroup00/LogVol00 rhgb quiet > module /initrd-2.6.16-1.2080_FC5xen0.img > title Fedora Core (2.6.16-1.2080_FC5) > root (hd0,0) > kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=/dev/VolGroup00/ > LogVol00 rhgb quiet > initrd /initrd-2.6.16-1.2080_FC5.img > title Fedora Core (2.6.15-1.2054_FC5) > root (hd0,0) > kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/ > LogVol00 rhgb quiet > initrd /initrd-2.6.15-1.2054_FC5.img > [root at localhost ~]# cat /proc/partitions > major minor #blocks name > > 3 0 8388608 hda > 3 1 104391 hda1 > 3 2 8281507 hda2 > 253 0 7831552 dm-0 > 253 1 393216 dm-1 > [root at localhost ~]# xm dmesg > __ __ _____ ___ ___ > \ \/ /___ _ __ |___ / / _ \ / _ \ > \ // _ \ '_ \ |_ \| | | | | | | > / \ __/ | | | ___) | |_| | |_| | > /_/\_\___|_| |_| |____(_)___(_)___/ > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 3.0.0 (bhcompile at build.redhat.com) (gcc version 4.1.0 > 20060304 (Red Hat 4.1.0-3)) Tue > Mar 28 03:35:03 EST 2006 > Latest ChangeSet: unavailable > > (XEN) Physical RAM map: > (XEN) 0000000000000000 - 000000000009f800 (usable) > (XEN) 000000000009f800 - 00000000000a0000 (reserved) > (XEN) 00000000000dc000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000000bef0000 (usable) > (XEN) 000000000bef0000 - 000000000befc000 (ACPI data) > (XEN) 000000000befc000 - 000000000bf00000 (ACPI NVS) > (XEN) 000000000bf00000 - 000000000c000000 (usable) > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000fffe0000 - 0000000100000000 (reserved) > (XEN) System RAM: 191MB (196156kB) > (XEN) Xen heap: 10MB (10344kB) > (XEN) Using scheduler: Simple EDF Scheduler (sedf) > (XEN) PAE disabled. > (XEN) found SMP MP-table at 000f6ce0 > (XEN) DMI present. > (XEN) Using APIC driver default > (XEN) ACPI: RSDP (v000 PTLTD ) @ > 0x000f6c70 > (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) > @ 0x0bef7c02 > (XEN) ACPI: FADT (v001 INTEL 440BX 0x06040000 PTL 0x000f4240) > @ 0x0befbf14 > (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) > @ 0x0befbf88 > (XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) > @ 0x0befbfd8 > (XEN) ACPI: DSDT (v001 PTLTD Custom 0x06040000 MSFT 0x0100000d) > @ 0x00000000 > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > (XEN) Processor #0 15:12 APIC version 17 > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) Initializing CPU#0 > (XEN) Detected 1599.572 MHz processor. > (XEN) CPU0: AMD Flush Filter disabled > (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/ > line) > (XEN) CPU: L2 Cache: 128K (64 bytes/line) > (XEN) Intel machine check architecture supported. > (XEN) Intel machine check reporting enabled on CPU#0. > (XEN) CPU0: AMD Sempron(tm) Processor 2600+ stepping 02 > (XEN) Total of 1 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) Platform timer is 1.193MHz PIT > (XEN) Brought up 1 CPUs > (XEN) Machine check exception polling timer started. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Domain 0 kernel supports features = { 0000001f }. > (XEN) Domain 0 kernel requires features = { 00000000 }. > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0a000000->0b000000 (37859 pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0100000->c0455b7c > (XEN) Init. ramdisk: c0456000->c07e2200 > (XEN) Phys-Mach map: c07e3000->c080bf8c > (XEN) Start info: c080c000->c080d000 > (XEN) Page tables: c080d000->c0811000 > (XEN) Boot stack: c0811000->c0812000 > (XEN) TOTAL: c0000000->c0c00000 > (XEN) ENTRY ADDRESS: c0100000 > (XEN) Dom0 has maximum 1 VCPUs > (XEN) Initrd len 0x38c200, start at 0xc0456000 > (XEN) Scrubbing Free RAM: ..done. > (XEN) Xen trace buffers: disabled > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > input to Xen). > > [root at localhost ~]# cat /etc/redhat-release > Fedora Core release 5 (Bordeaux) > [root at localhost ~]# > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From okajima at digitalinfra.co.jp Sun Apr 2 16:40:01 2006 From: okajima at digitalinfra.co.jp (Jun OKAJIMA) Date: Mon, 03 Apr 2006 01:40:01 +0900 Subject: [Fedora-xen] pygrub failed In-Reply-To: References: Message-ID: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> >I believe the error "Error: Error creating domain: The privileged >domain did not balloon!" happens when you don't have enough available >memory for the domU to boot. The xenguest-install.py script tells >you to restart the domain by running "xm create -c xxxx', but I think >the error message is just a generic one that is printed if the script >crashes out, and it it is the wrong thing to do in this case. > >When I had the same problem, I had to allocate less memory to dom0 >and re-run the xenguest-install script. I see you have about 196MB >of RAM. Since the FC5 script needs 256MB of RAM, I don't think >you'll be able to install it unless you increase the amount of RAM >you have. But since the machine is a virtual one in VMWare, this >shouldn't be too difficult. > Thank you for replying. Unfortunately, I tried same stuff with 512MB mem but failed. What I suspect now is, a disk image would have to be formatted. xenguest-install.py just makes plain empty sparse file, but is this enough? I suspect it should be formatted and partitioned and so on. You succeeded to do an install on FC5? How you did it? Check the code of pygrub. See this: 116 fs = None 117 for fstype in grub.fsys.fstypes.values(): 118 if fstype.sniff_magic(fn, offset): 119 fs = fstype.open_fs(fn, offset) 120 break 121 122 if fs is not None: (snip) 138 else: 139 raise RuntimeError, "Unable to read filesystem" What happened here is, in short, like this: # Check diskimage formatted as described in grub config 117 for fstype in grub.fsys.fstypes.values(): 118 if fstype.sniff_magic(fn, offset): # If not formatted properly, raise error. 138 else: 139 raise RuntimeError, "Unable to read filesystem" --- Okajima, Jun. Tokyo, Japan. ------------- [root at localhost ~]# cat -n /usr/bin/pygrub 1 #!/usr/bin/python 2 # 3 # pygrub - simple python-based bootloader for Xen 4 # 5 # Copyright 2005 Red Hat, Inc. 6 # Jeremy Katz 7 # 8 # This software may be freely redistributed under the terms of the GNU 9 # general public license. 10 # 11 # You should have received a copy of the GNU General Public License 12 # along with this program; if not, write to the Free Software 13 # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. 14 # 15 16 import os, sys, string, struct, tempfile 17 import logging 18 19 import curses, _curses, curses.wrapper 20 import getopt 21 22 sys.path = [ '/usr/lib/python' ] + sys.path 23 24 import grub.GrubConf 25 import grub.fsys 26 27 PYGRUB_VER = 0.3 28 29 30 def draw_window(): 31 stdscr = curses.initscr() 32 if hasattr(curses, 'use_default_colors'): 33 curses.use_default_colors() 34 try: 35 curses.curs_set(0) 36 except _curses.error: 37 pass 38 39 stdscr.addstr(1, 4, "pyGRUB version %s" %(PYGRUB_VER,)) 40 41 win = curses.newwin(10, 74, 2, 1) 42 win.box() 43 win.refresh() 44 45 stdscr.addstr(12, 5, "Use the U and D keys to select which entry is highlighted.") 46 stdscr.addstr(13, 5, "Press enter to boot the selected OS. 'e' to edit the") 47 stdscr.addstr(14, 5, "commands before booting, 'a' to modify the kernel arguments ") 48 stdscr.addstr(15, 5, "before booting, or 'c' for a command line.") 49 stdscr.addch(12, 13, curses.ACS_UARROW) 50 stdscr.addch(12, 19, curses.ACS_DARROW) 51 (y, x) = stdscr.getmaxyx() 52 stdscr.move(y - 1, x - 1) 53 54 stdscr.refresh() 55 return (stdscr, win) 56 57 def fill_entries(win, cfg, selected): 58 y = 0 59 60 for i in cfg.images: 61 if (0, y) > win.getmaxyx(): 62 break 63 if y == selected: 64 attr = curses.A_REVERSE 65 else: 66 attr = 0 67 win.addstr(y + 1, 2, i.title.ljust(70), attr) 68 y += 1 69 win.refresh() 70 71 def select(win, line): 72 win.attron(curses.A_REVERSE) 73 win.redrawln(line + 1, 1) 74 win.refresh() 75 76 def is_disk_image(file): 77 fd = os.open(file, os.O_RDONLY) 78 buf = os.read(fd, 512) 79 os.close(fd) 80 81 if len(buf) >= 512 and struct.unpack("H", buf[0x1fe: 0x200]) == (0xaa55,): 82 return True 83 return False 84 85 SECTOR_SIZE=512 86 def get_active_offset(file): 87 """Find the offset for the start of the first active partition in the 88 disk image file.""" 89 fd = os.open(file, os.O_RDONLY) 90 buf = os.read(fd, 512) 91 for poff in (446, 462, 478, 494): # partition offsets 92 # active partition has 0x80 as the first byte 93 if struct.unpack("= len(cf.images): 204 selected = len(cf.images) - 1 205 206 if selected >= 0: 207 return selected 208 209 if __name__ == "__main__": 210 sel = None 211 212 def run_main(scr, *args): 213 global sel 214 sel = main(cf) 215 216 def usage(): 217 print >> sys.stderr, "Usage: %s [-q|--quiet] [--output=] [--entry=] " % (sys.argv[0],) 218 219 try: 220 opts, args = getopt.gnu_getopt(sys.argv[1:], 'qh::', 221 ["quiet", "help", "output=", "entry=", 222 "isconfig"]) 223 except getopt.GetoptError: 224 usage() 225 sys.exit(1) 226 227 if len(args) < 1: 228 usage() 229 sys.exit(1) 230 file = args[0] 231 232 output = None 233 entry = None 234 interactive = True 235 isconfig = False 236 for o, a in opts: 237 if o in ("-q", "--quiet"): 238 interactive = False 239 elif o in ("-h", "--help"): 240 usage() 241 sys.exit() 242 elif o in ("--output",): 243 output = a 244 elif o in ("--entry",): 245 entry = a 246 # specifying the entry to boot implies non-interactive 247 interactive = False 248 elif o in ("--isconfig",): 249 isconfig = True 250 251 if output is None or output == "-": 252 fd = sys.stdout.fileno() 253 else: 254 fd = os.open(output, os.O_WRONLY) 255 256 cf = get_config(file, isconfig) 257 if interactive: 258 curses.wrapper(run_main) 259 else: 260 sel = cf.default 261 262 # set the entry to boot as requested 263 if entry is not None: 264 idx = get_entry_idx(cf, entry) 265 if idx is not None and idx > 0 and idx < len(cf.images): 266 sel = idx 267 268 img = cf.images[sel] 269 print "Going to boot %s" %(img.title) 270 print " kernel: %s" %(img.kernel[1],) 271 if img.initrd: 272 print " initrd: %s" %(img.initrd[1],) 273 274 offset = 0 275 if is_disk_image(file): 276 offset = get_active_offset(file) 277 if offset == -1: 278 raise RuntimeError, "Unable to find active partition on disk" 279 280 # read the kernel and initrd onto the hostfs 281 fs = None 282 for fstype in grub.fsys.fstypes.values(): 283 if fstype.sniff_magic(file, offset): 284 fs = fstype.open_fs(file, offset) 285 break 286 287 if fs is None: 288 raise RuntimeError, "Unable to open filesystem" 289 290 kernel = fs.open_file(img.kernel[1],).read() 291 (tfd, fn) = tempfile.mkstemp(prefix="vmlinuz.", dir="/var/lib/xen") 292 os.write(tfd, kernel) 293 os.close(tfd) 294 sxp = "linux (kernel %s)" %(fn,) 295 296 if img.initrd: 297 initrd = fs.open_file(img.initrd[1],).read() 298 (tfd, fn) = tempfile.mkstemp(prefix="initrd.", dir="/var/lib/xen") 299 os.write(tfd, initrd) 300 os.close(tfd) 301 sxp += "(ramdisk %s)" %(fn,) 302 else: 303 initrd = None 304 sxp += "(args '%s')" %(img.args,) 305 306 sys.stdout.flush() 307 os.write(fd, sxp) 308 [root at localhost ~]# From meyering at redhat.com Sat Apr 1 09:56:24 2006 From: meyering at redhat.com (Jim Meyering) Date: Sat, 01 Apr 2006 11:56:24 +0200 Subject: [Fedora-xen] Disk problems on FC5 In-Reply-To: <1143859393.3383.5.camel@orbit.scot.redhat.com> (Stephen C. Tweedie's message of "Fri, 31 Mar 2006 21:43:12 -0500") References: <442BCBB4.7090906@redhat.com> <1143859393.3383.5.camel@orbit.scot.redhat.com> Message-ID: <878xqpfwl3.fsf@rho.meyering.net> "Stephen C. Tweedie" wrote: ... > No! The disk size is specified in GB, though, so you just asked for a > 4TB file, which is beyond ext3's tiny little brains. Try something a > little smaller. :-) > > Yes, we should deal with this error better. One way to avoid the problem is to require a suffix on the size arguments, e.g. 2.6GB, 3200MiB, etc. Then there's no possibility for confusion. From kzak at redhat.com Sun Apr 2 21:31:16 2006 From: kzak at redhat.com (Karel Zak) Date: Sun, 2 Apr 2006 23:31:16 +0200 Subject: [Fedora-xen] pygrub failed In-Reply-To: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> References: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: <20060402213116.GA6492@petra.dvoda.cz> On Po, dub 03, 2006 at 01:40:01 +0900, Jun OKAJIMA wrote: > Unfortunately, I tried same stuff with 512MB mem but failed. > What I suspect now is, a disk image would have to be formatted. > xenguest-install.py just makes plain empty sparse file, but is this > enough? I suspect it should be formatted and partitioned and so on. No. The empty file is enough, because xenguest-install.py doesn't use pygrub for domU installation boot. You need prepare your virtual disk by anaconda which is started by xenguest-install.py. The pygrub script is possible use for already __successfully__ installed domU only. Karel -- Karel Zak From winston at stdout.org Mon Apr 3 02:09:48 2006 From: winston at stdout.org (Winston Chang) Date: Sun, 2 Apr 2006 22:09:48 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> References: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: The installer will create the disk image and partition it. If you do not successfully run to the installer, "xm create -c xxxx" will not work. The script gives bad instructions when an error occurs. The Xen hypervisor takes 32MB of RAM (I think), so you have to make sure that your dom0 gets less than 224MB. I gave mine 192MB, with the following in grub.conf: kernel /xen.gz-2.6.15-1.2054_FC5 dom0_mem=196608 In my opinion, the xenguest-install.py method isn't very good at this point. - The installer gives poor feedback when something goes wrong, like when memory is too low. - pygrub crashes if your terminal emulation is a little weird - It creates a whole disk image instead of importing partitions. This makes it difficult to access domU filesystems from dom0, but this is often necessary for management. - It doesn't provide an option for creating images on LVM volumes. An easier solution might be to use the FC5 image from jailtime.org. If you use the images from their site, keep in mind that you have to use a kernel from outside of the image; the kernel would have to be readable from your dom0. If you use the stock FC5-xenU kernel, it does not have the xennet driver compiled in. You would have to install the kernel-xenU package onto the domU disk image to provide the necessary driver (assuming the disk image is mounted at /mnt/tmp): yum --installroot=/mnt/tmp install kernel-xenU And add the following to the domU's /etc/modprobe.conf: alias eth0 xennet Or you could use a kernel from xensource that has the xennet driver compiled into the kernel. I don't know why the developers decided to take the driver out of the kernel. Pretty much everyone would want networking on their domU machines, and adding it in this way is just more complicated. --Winston On Apr 2, 2006, at 12:40 PM, Jun OKAJIMA wrote: > >> I believe the error "Error: Error creating domain: The privileged >> domain did not balloon!" happens when you don't have enough available >> memory for the domU to boot. The xenguest-install.py script tells >> you to restart the domain by running "xm create -c xxxx', but I think >> the error message is just a generic one that is printed if the script >> crashes out, and it it is the wrong thing to do in this case. >> >> When I had the same problem, I had to allocate less memory to dom0 >> and re-run the xenguest-install script. I see you have about 196MB >> of RAM. Since the FC5 script needs 256MB of RAM, I don't think >> you'll be able to install it unless you increase the amount of RAM >> you have. But since the machine is a virtual one in VMWare, this >> shouldn't be too difficult. >> > > > Thank you for replying. > Unfortunately, I tried same stuff with 512MB mem but failed. > What I suspect now is, a disk image would have to be formatted. > xenguest-install.py just makes plain empty sparse file, but is this > enough? I suspect it should be formatted and partitioned and so on. > You succeeded to do an install on FC5? How you did it? > > Check the code of pygrub. > See this: > 116 fs = None > 117 for fstype in grub.fsys.fstypes.values(): > 118 if fstype.sniff_magic(fn, offset): > 119 fs = fstype.open_fs(fn, offset) > 120 break > 121 > 122 if fs is not None: > (snip) > 138 else: > 139 raise RuntimeError, "Unable to read filesystem" > > What happened here is, in short, like this: > > # Check diskimage formatted as described in grub config > 117 for fstype in grub.fsys.fstypes.values(): > 118 if fstype.sniff_magic(fn, offset): > # If not formatted properly, raise error. > 138 else: > 139 raise RuntimeError, "Unable to read filesystem" > > --- Okajima, Jun. Tokyo, Japan. > > > ------------- > [root at localhost ~]# cat -n /usr/bin/pygrub > 1 #!/usr/bin/python > 2 # > 3 # pygrub - simple python-based bootloader for Xen > 4 # > 5 # Copyright 2005 Red Hat, Inc. > 6 # Jeremy Katz > 7 # > 8 # This software may be freely redistributed under the terms > of the GNU > 9 # general public license. > 10 # > 11 # You should have received a copy of the GNU General Public > License > 12 # along with this program; if not, write to the Free Software > 13 # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. > 14 # > 15 > 16 import os, sys, string, struct, tempfile > 17 import logging > 18 > 19 import curses, _curses, curses.wrapper > 20 import getopt > 21 > 22 sys.path = [ '/usr/lib/python' ] + sys.path > 23 > 24 import grub.GrubConf > 25 import grub.fsys > 26 > 27 PYGRUB_VER = 0.3 > 28 > 29 > 30 def draw_window(): > 31 stdscr = curses.initscr() > 32 if hasattr(curses, 'use_default_colors'): > 33 curses.use_default_colors() > 34 try: > 35 curses.curs_set(0) > 36 except _curses.error: > 37 pass > 38 > 39 stdscr.addstr(1, 4, "pyGRUB version %s" %(PYGRUB_VER,)) > 40 > 41 win = curses.newwin(10, 74, 2, 1) > 42 win.box() > 43 win.refresh() > 44 > 45 stdscr.addstr(12, 5, "Use the U and D keys to select > which entry is highlighted.") > 46 stdscr.addstr(13, 5, "Press enter to boot the selected > OS. 'e' to edit the") > 47 stdscr.addstr(14, 5, "commands before booting, 'a' to > modify the kernel arguments ") > 48 stdscr.addstr(15, 5, "before booting, or 'c' for a > command line.") > 49 stdscr.addch(12, 13, curses.ACS_UARROW) > 50 stdscr.addch(12, 19, curses.ACS_DARROW) > 51 (y, x) = stdscr.getmaxyx() > 52 stdscr.move(y - 1, x - 1) > 53 > 54 stdscr.refresh() > 55 return (stdscr, win) > 56 > 57 def fill_entries(win, cfg, selected): > 58 y = 0 > 59 > 60 for i in cfg.images: > 61 if (0, y) > win.getmaxyx(): > 62 break > 63 if y == selected: > 64 attr = curses.A_REVERSE > 65 else: > 66 attr = 0 > 67 win.addstr(y + 1, 2, i.title.ljust(70), attr) > 68 y += 1 > 69 win.refresh() > 70 > 71 def select(win, line): > 72 win.attron(curses.A_REVERSE) > 73 win.redrawln(line + 1, 1) > 74 win.refresh() > 75 > 76 def is_disk_image(file): > 77 fd = os.open(file, os.O_RDONLY) > 78 buf = os.read(fd, 512) > 79 os.close(fd) > 80 > 81 if len(buf) >= 512 and struct.unpack("H", buf[0x1fe: > 0x200]) == (0xaa55,): > 82 return True > 83 return False > 84 > 85 SECTOR_SIZE=512 > 86 def get_active_offset(file): > 87 """Find the offset for the start of the first active > partition in the > 88 disk image file.""" > 89 fd = os.open(file, os.O_RDONLY) > 90 buf = os.read(fd, 512) > 91 for poff in (446, 462, 478, 494): # partition offsets > 92 # active partition has 0x80 as the first byte > 93 if struct.unpack(" 94 return struct.unpack(" [0] * SECTOR_SIZE > 95 return -1 > 96 > 97 def get_config(fn, isconfig = False): > 98 if not os.access(fn, os.R_OK): > 99 raise RuntimeError, "Unable to access %s" %(fn,) > 100 > 101 cf = grub.GrubConf.GrubConfigFile() > 102 > 103 if isconfig: > 104 # set the config file and parse it > 105 cf.filename = fn > 106 cf.parse() > 107 return cf > 108 > 109 offset = 0 > 110 if is_disk_image(fn): > 111 offset = get_active_offset(fn) > 112 if offset == -1: > 113 raise RuntimeError, "Unable to find active > partition on disk" > 114 > 115 # open the image and read the grub config > 116 fs = None > 117 for fstype in grub.fsys.fstypes.values(): > 118 if fstype.sniff_magic(fn, offset): > 119 fs = fstype.open_fs(fn, offset) > 120 break > 121 > 122 if fs is not None: > 123 grubfile = None > 124 for f in ("/boot/grub/menu.lst", "/boot/grub/ > grub.conf", > 125 "/grub/menu.lst", "/grub/grub.conf"): > 126 if fs.file_exist(f): > 127 grubfile = f > 128 break > 129 if grubfile is None: > 130 raise RuntimeError, "we couldn't find /boot/grub > {menu.lst,grub.conf} " + \ > 131 "in the image provided. halt!" > 132 f = fs.open_file(grubfile) > 133 buf = f.read() > 134 f.close() > 135 fs.close() > 136 # then parse the grub config > 137 cf.parse(buf) > 138 else: > 139 raise RuntimeError, "Unable to read filesystem" > 140 > 141 return cf > 142 > 143 def get_entry_idx(cf, entry): > 144 # first, see if the given entry is numeric > 145 try: > 146 idx = string.atoi(entry) > 147 return idx > 148 except ValueError: > 149 pass > 150 > 151 # it's not, now check the labels for a match > 152 for i in range(len(cf.images)): > 153 if entry == cf.images[i].title: > 154 return i > 155 > 156 return None > 157 > 158 def main(cf = None): > 159 mytime = 0 > 160 timeout = int(cf.timeout) > 161 > 162 (stdscr, win) = draw_window() > 163 stdscr.timeout(1000) > 164 selected = cf.default > 165 > 166 while (timeout == -1 or mytime < int(timeout)): > 167 if timeout != -1 and mytime != -1: > 168 stdscr.addstr(20, 5, "Will boot selected entry > in %2d seconds" > 169 %(int(timeout) - mytime)) > 170 else: > 171 stdscr.addstr(20, 5, " " * 80) > 172 > 173 fill_entries(win, cf, selected) > 174 c = stdscr.getch() > 175 if mytime != -1: > 176 mytime += 1 > 177 # if c == ord('q'): > 178 # selected = -1 > 179 # break > 180 if c == ord('c'): > 181 # FIXME: needs to go to command line mode > 182 continue > 183 elif c == ord('a'): > 184 # FIXME: needs to go to append mode > 185 continue > 186 elif c == ord('e'): > 187 # FIXME: needs to go to edit mode > 188 continue > 189 elif c in (curses.KEY_ENTER, ord('\n'), ord('\r')): > 190 break > 191 elif c == curses.KEY_UP: > 192 mytime = -1 > 193 selected -= 1 > 194 elif c == curses.KEY_DOWN: > 195 mytime = -1 > 196 selected += 1 > 197 else: > 198 pass > 199 > 200 # bound at the top and bottom > 201 if selected < 0: > 202 selected = 0 > 203 elif selected >= len(cf.images): > 204 selected = len(cf.images) - 1 > 205 > 206 if selected >= 0: > 207 return selected > 208 > 209 if __name__ == "__main__": > 210 sel = None > 211 > 212 def run_main(scr, *args): > 213 global sel > 214 sel = main(cf) > 215 > 216 def usage(): > 217 print >> sys.stderr, "Usage: %s [-q|--quiet] [-- > output=] [--entry=] " % > (sys.argv[0],) > 218 > 219 try: > 220 opts, args = getopt.gnu_getopt(sys.argv[1:], 'qh::', > 221 ["quiet", "help", > "output=", "entry=", > 222 "isconfig"]) > 223 except getopt.GetoptError: > 224 usage() > 225 sys.exit(1) > 226 > 227 if len(args) < 1: > 228 usage() > 229 sys.exit(1) > 230 file = args[0] > 231 > 232 output = None > 233 entry = None > 234 interactive = True > 235 isconfig = False > 236 for o, a in opts: > 237 if o in ("-q", "--quiet"): > 238 interactive = False > 239 elif o in ("-h", "--help"): > 240 usage() > 241 sys.exit() > 242 elif o in ("--output",): > 243 output = a > 244 elif o in ("--entry",): > 245 entry = a > 246 # specifying the entry to boot implies non- > interactive > 247 interactive = False > 248 elif o in ("--isconfig",): > 249 isconfig = True > 250 > 251 if output is None or output == "-": > 252 fd = sys.stdout.fileno() > 253 else: > 254 fd = os.open(output, os.O_WRONLY) > 255 > 256 cf = get_config(file, isconfig) > 257 if interactive: > 258 curses.wrapper(run_main) > 259 else: > 260 sel = cf.default > 261 > 262 # set the entry to boot as requested > 263 if entry is not None: > 264 idx = get_entry_idx(cf, entry) > 265 if idx is not None and idx > 0 and idx < len > (cf.images): > 266 sel = idx > 267 > 268 img = cf.images[sel] > 269 print "Going to boot %s" %(img.title) > 270 print " kernel: %s" %(img.kernel[1],) > 271 if img.initrd: > 272 print " initrd: %s" %(img.initrd[1],) > 273 > 274 offset = 0 > 275 if is_disk_image(file): > 276 offset = get_active_offset(file) > 277 if offset == -1: > 278 raise RuntimeError, "Unable to find active > partition on disk" > 279 > 280 # read the kernel and initrd onto the hostfs > 281 fs = None > 282 for fstype in grub.fsys.fstypes.values(): > 283 if fstype.sniff_magic(file, offset): > 284 fs = fstype.open_fs(file, offset) > 285 break > 286 > 287 if fs is None: > 288 raise RuntimeError, "Unable to open filesystem" > 289 > 290 kernel = fs.open_file(img.kernel[1],).read() > 291 (tfd, fn) = tempfile.mkstemp(prefix="vmlinuz.", dir="/ > var/lib/xen") > 292 os.write(tfd, kernel) > 293 os.close(tfd) > 294 sxp = "linux (kernel %s)" %(fn,) > 295 > 296 if img.initrd: > 297 initrd = fs.open_file(img.initrd[1],).read() > 298 (tfd, fn) = tempfile.mkstemp(prefix="initrd.", > dir="/var/lib/xen") > 299 os.write(tfd, initrd) > 300 os.close(tfd) > 301 sxp += "(ramdisk %s)" %(fn,) > 302 else: > 303 initrd = None > 304 sxp += "(args '%s')" %(img.args,) > 305 > 306 sys.stdout.flush() > 307 os.write(fd, sxp) > 308 > [root at localhost ~]# From benjy.grogan at gmail.com Mon Apr 3 09:59:54 2006 From: benjy.grogan at gmail.com (Benjy Grogan) Date: Mon, 3 Apr 2006 05:59:54 -0400 Subject: [Fedora-xen] Puzzled by Xen Message-ID: Hello: I've read that Xen will allow servers that typically operate at 15% to 25% CPU capacity to operate at up to 80% with virtualization. Does that mean that CPU usage will reach 80% instead of a lowly 15% to 25%? Does CPU capacity equate CPU usage? Instead of putting more work on different host OSes within Xen why not put all of that work in one single OS to achieve that 80% CPU usage? I've been reading up on Xen, and still this basic question puzzles me. Is there something that I'm not getting about virtualization? Benji PS: To me CPU usage is when you look at the system monitor and see the load. From qwejohn at gmail.com Mon Apr 3 10:45:03 2006 From: qwejohn at gmail.com (John Que) Date: Mon, 3 Apr 2006 13:45:03 +0300 Subject: [Fedora-xen] Error in fedora quick start for Xen Message-ID: Hello, I am following the instructions on Fedora Xen Quickstart page: http://www.fedoraproject.org/wiki/FedoraXenQuickstart?highlight=%28xen%29 First thing, I want to say that the size for the fedora.img is not enough now (I assume it was enough in the past) because , after running (according to the instructions): dd if=/dev/zero of=fedora.img bs=1M count=1 seek=1024 ... ... then running : yum -c http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y groupinstall Base gave me an error because of not enough space. so I started the process whole over again from the beginning (and this took more than an hour), this time allocating 2 giga: dd if=/dev/zero of=fedora.img bs=1M count=1 seek=2048 So maybe this should be corrected in that web page. I have a question: Can the size of a file which was created thus (dd if=/dev/zero of=fedora.img bs=1M count=1 seek=1024) be changed ***without*** causing a damage to its contents? In case there is such a way, how can it be done ? Regards, John From okajima at digitalinfra.co.jp Mon Apr 3 11:24:03 2006 From: okajima at digitalinfra.co.jp (Jun OKAJIMA) Date: Mon, 03 Apr 2006 20:24:03 +0900 Subject: jailtime.org failed also (was:Re: [Fedora-xen] pygrub failed) In-Reply-To: References: Message-ID: <200604031124.AA00976@bbb-jz5c7z9hn9y.digitalinfra.co.jp> >The installer will create the disk image and partition it. If you do >not successfully run to the installer, "xm create -c xxxx" will not >work. The script gives bad instructions when an error occurs. > >The Xen hypervisor takes 32MB of RAM (I think), so you have to make >sure that your dom0 gets less than 224MB. I gave mine 192MB, with >the following in grub.conf: > kernel /xen.gz-2.6.15-1.2054_FC5 dom0_mem=196608 > > >In my opinion, the xenguest-install.py method isn't very good at this >point. >- The installer gives poor feedback when something goes wrong, like >when memory is too low. >- pygrub crashes if your terminal emulation is a little weird >- It creates a whole disk image instead of importing partitions. >This makes it difficult to access domU filesystems from dom0, but >this is often necessary for management. >- It doesn't provide an option for creating images on LVM volumes. > > > >An easier solution might be to use the FC5 image from jailtime.org. >If you use the images from their site, keep in mind that you have to >use a kernel from outside of the image; the kernel would have to be >readable from your dom0. > >If you use the stock FC5-xenU kernel, it does not have the xennet >driver compiled in. You would have to install the kernel-xenU >package onto the domU disk image to provide the necessary driver >(assuming the disk image is mounted at /mnt/tmp): > yum --installroot=/mnt/tmp install kernel-xenU >And add the following to the domU's /etc/modprobe.conf: > alias eth0 xennet > >Or you could use a kernel from xensource that has the xennet driver >compiled into the kernel. I don't know why the developers decided to >take the driver out of the kernel. Pretty much everyone would want >networking on their domU machines, and adding it in this way is just >more complicated. > > > Thank you for suggestive advise. but, I have been still working on the issue. I tried to use a ready made image from jailtime.org, but still it does not work. Why os.path.isfile(self.kernel) fails? --- Okajima, Jun. Tokyo, Japan. ------------- [root at localhost okajima]# xm create -c fedora.fc5.xen.cfg Using config file "fedora.fc5.xen.cfg". Warning: The nics option is deprecated. Please use an empty vif entry instead: vif = [ '' ] Error: Error creating domain: Kernel image does not exist: /boot/vmlinuz-2.6.16-1.2080_FC5xenU [root at localhost okajima]# ls -la /boot/vmlinuz-2.6.16-1.2080_FC5xenU -rw-r--r-- 1 root root 1232494 Mar 28 18:38 /boot/vmlinuz-2.6.16-1.2080_FC5xenU [root at localhost okajima]# md5sum /boot/vmlinuz-2.6.16-1.2080_FC5xenU 242c2a1cfeb924481ba57e983cbe801e /boot/vmlinuz-2.6.16-1.2080_FC5xenU [root at localhost okajima]# ls -l /usr/lib/xen/boot/ total 160 -rwxr-xr-x 1 root root 153797 Mar 9 14:20 hvmloader [root at localhost okajima]# md5sum /usr/lib/xen/boot/hvmloader 2bbd4cf936aa8bde3ab6b6fe31362ff0 /usr/lib/xen/boot/hvmloader [root at localhost okajima]# cat fedora.fc5.xen.cfg kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" #kernel = "/boot/vmlinuz-2.6-xenU" memory = 128 name = "fedora.fc5" nics = 1 dhcp = "dhcp" disk = ['file:/home/okajima/fedora.fc5.img,sda1,w', 'file:/home/okajima/fedora.swap,sda2,w'] root = "/dev/sda1 ro" [root at localhost okajima]# grep -3 -ir "Kernel image does not exist" /usr/lib/python2.4/site-packages/ * Binary file /usr/lib/python2.4/site-packages/xen/xend/image.pyo matches -- /usr/lib/python2.4/site-packages/xen/xend/image.py- # Set params and call buildDomain(). /usr/lib/python2.4/site-packages/xen/xend/image.py- /usr/lib/python2.4/site-packages/xen/xend/image.py- if not os.path.isfile(self.kernel): /usr/lib/python2.4/site-packages/xen/xend/image.py: raise VmError('Kernel image does not exist: %s' % self.kernel) /usr/lib/python2.4/site-packages/xen/xend/image.py- if self.ramdisk and not os.path.isfile (self.ramdisk): /usr/lib/python2.4/site-packages/xen/xend/image.py- raise VmError('Kernel ramdisk does not exist: %s' % self.ramdisk) /usr/lib/python2.4/site-packages/xen/xend/image.py- if len(self.cmdline) >= MAX_GUEST_CMDLINE: Binary file /usr/lib/python2.4/site-packages/xen/xend/image.pyc matches [root at localhost okajima]# From okajima at digitalinfra.co.jp Mon Apr 3 11:16:01 2006 From: okajima at digitalinfra.co.jp (Jun OKAJIMA) Date: Mon, 03 Apr 2006 20:16:01 +0900 Subject: [Fedora-xen] pygrub failed In-Reply-To: <20060402213116.GA6492@petra.dvoda.cz> References: <20060402213116.GA6492@petra.dvoda.cz> Message-ID: <200604031116.AA00974@bbb-jz5c7z9hn9y.digitalinfra.co.jp> >> Unfortunately, I tried same stuff with 512MB mem but failed. >> What I suspect now is, a disk image would have to be formatted. >> xenguest-install.py just makes plain empty sparse file, but is this >> enough? I suspect it should be formatted and partitioned and so on. > > No. The empty file is enough, because xenguest-install.py doesn't use > pygrub for domU installation boot. You need prepare your virtual disk > by anaconda which is started by xenguest-install.py. The pygrub > script is possible use for already __successfully__ installed domU > only. > Ummm... You mean I have to start anaconda/XenU stuff first, but I dont have felt that I have succeeded to do so, although I dont have understanded what xenguest-install.py does yet. --- Okajima, Jun. Tokyo, Japan. From loony at loonybin.org Mon Apr 3 10:41:06 2006 From: loony at loonybin.org (Peter Arremann) Date: Mon, 3 Apr 2006 06:41:06 -0400 Subject: [Fedora-xen] Puzzled by Xen In-Reply-To: References: Message-ID: <200604030641.06330.loony@loonybin.org> On Monday 03 April 2006 05:59, Benjy Grogan wrote: > Hello: > > I've read that Xen will allow servers that typically operate at 15% to > 25% CPU capacity to operate at up to 80% with virtualization. Does > that mean that CPU usage will reach 80% instead of a lowly 15% to 25%? > Does CPU capacity equate CPU usage? Instead of putting more work on > different host OSes within Xen why not put all of that work in one > single OS to achieve that 80% CPU usage? > > I've been reading up on Xen, and still this basic question puzzles me. > Is there something that I'm not getting about virtualization? > > Benji > > PS: To me CPU usage is when you look at the system monitor and see the > load. The purpose of Xen is to utilitze your servers better. If you had 4 identical servers that all ran at 10% cpu utilization, then if you put them together into one box using xen, you'll have theoretically 40% usage of 1 system and 3 to do other things with. Xen of course has some overhead, so you will probably see 45% total usage or such. The reason why you want to do that is obvious - less servers needed to get the same work done. Power, air conditioning, space and so on all add to the cost of purchasing a server. If you can add all these services onto one server, you're better off doing so most of the time. But very often you will find, that it is not possible. What if your servers are part of different NIS domains? One OS image can only be part of 1 NIS domain at the time... What if each server is running a different instance of a program on the same port? There are lots of reasons. Most can be worked around, but over time the number and difficulty needed for those work arounds will add up and you will find it much easier to go with Xen. Management is another reason to go with xen. You can very easily migrate OS images around as needed in xen. So if your workload changes, you can move some work to another server easily without having to do major re configurations in your OS. Security is also a good point. If you're running an app like apache that is fairly common and well tested, you're usually OK. Now add in some other app that is listening on the network but isn't hit directly by your customer (thing DB or custom apps). If you have only 1 instance of your OS running, both apps are on the customer facing network. If you run xen, you can play tricks and have only the apache portion exposed, while the communications with the other app is done over a private network that the users don't have direct access too. Compatibility is yet another reason. You can run any xen based domU on any dom0 - at least in theory... Right now you'll run into issues with xen2 and xen3 version and stuff - but some day you'll be able to run Solaris x86 and Netbsd ontop of you fedora dom0. In the end, Xen doesn't do anything you couldn't in a perfect open source world do in a single OS instance. It just makes things a lot easier and keeps you from doing a ton of extra work to get things running. Peter. From muratisik at bilgiguvenlik.com Mon Apr 3 13:48:38 2006 From: muratisik at bilgiguvenlik.com (Murat =?iso-8859-9?Q?I=FE=FDk?=) Date: Mon, 3 Apr 2006 16:48:38 +0300 (EEST) Subject: [Fedora-xen] RE: Problem booting jailtime images Message-ID: <45020.195.174.105.65.1144072118.squirrel@webmail.bilcag.net> hello, "I didn't try to use a xen0 kernel to boot xenU before. I am not sure if it is okay. But I think you can try vmlinuz-2.6.16-1.2080_FC5xenU which comes from another Xen RPMs." thanks very much for the xenU - xen0 tip. a simple typo error costs so many problems... however, now when I run xm create fedora.fc4.xen.cfg -c the virtual machines boot freezes at: ... md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 132k freed my /var/log/xend.log is: [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:177) XendDomainInfo.create(['vm', ['name', 'fedora.fc4'], ['memory', '128'], ['vcpus', '1'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif']]]) [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:283) parseConfig: config is ['vm', ['name', 'fedora.fc4'], ['memory', '128'], ['vcpus', '1'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif']]] [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:379) parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1 ro']], 'on_poweroff': None, 'cpus': None, 'name': 'fedora.fc4', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname', 'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev', 'sda2'], ['mode', 'w']]), ('vif', ['vif'])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1142) XendDomainInfo.construct: None 0 [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1174) XendDomainInfo.initDomain: 1 1.0 [2006-04-03 16:45:08 xend] DEBUG (balloon:88) Balloon: free 30; need 129. [2006-04-03 16:45:08 xend] DEBUG (balloon:97) Balloon: setting dom0 target to 364. [2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:923) Setting memory target of domain Domain-0 (0) to 364 MiB. [2006-04-03 16:45:09 xend] DEBUG (balloon:84) Balloon: free 129; need 129; done. [2006-04-03 16:45:09 xend] INFO (image:135) buildDomain os=linux dom=1 vcpus=1 [2006-04-03 16:45:09 xend] DEBUG (image:173) dom = 1 [2006-04-03 16:45:09 xend] DEBUG (image:174) image = /boot/vmlinuz-2.6.16-1.2080_FC5xenU [2006-04-03 16:45:09 xend] DEBUG (image:175) store_evtchn = 1 [2006-04-03 16:45:09 xend] DEBUG (image:176) console_evtchn = 2 [2006-04-03 16:45:09 xend] DEBUG (image:177) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro [2006-04-03 16:45:09 xend] DEBUG (image:178) ramdisk = [2006-04-03 16:45:09 xend] DEBUG (image:179) vcpus = 1 [2006-04-03 16:45:09 xend] DEBUG (image:180) features = [2006-04-03 16:45:09 xend] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' [2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController: writing {'virtual-device': '2049', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/2049'} to /local/domain/1/device/vbd/2049. [2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController: writing {'domain': 'fedora.fc4', 'frontend': '/local/domain/1/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': '/xen/fedora/fedora.fc4.img', 'mode': 'w', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/2049. [2006-04-03 16:45:09 xend] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' [2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController: writing {'virtual-device': '2050', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/2050'} to /local/domain/1/device/vbd/2050. [2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController: writing {'domain': 'fedora.fc4', 'frontend': '/local/domain/1/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': '/xen/fedora/fedora.swap', 'mode': 'w', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/2050. [2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:3d:ec:05', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController: writing {'mac': '00:16:3e:3d:ec:05', 'state': '1', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'frontend-id': '1', 'domain': 'fedora.fc4', 'frontend': '/local/domain/1/device/vif/0'} to /local/domain/0/backend/vif/1/0. [2006-04-03 16:45:09 xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details: {'ssidref': '0', 'uuid': 'be967607-af8e-0d14-956f-42443528af54', 'on_reboot': 'restart', 'start_time': '1144071909.98', 'on_poweroff': 'destroy', 'name': 'fedora.fc4', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '128', 'on_crash': 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6.16-1.2080_FC5xenU) (ip :1.2.3.4::::eth0:dhcp) (root '/dev/sda1 ro'))", 'maxmem': '128'} [2006-04-03 16:45:09 xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: {'console/ring-ref': '27070', 'console/port': '2', 'name': 'fedora.fc4', 'console/limit': '1048576', 'vm': '/vm/be967607-af8e-0d14-956f-42443528af54', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '131072', 'store/ring-ref': '116136', 'store/port': '1'} [2006-04-03 16:45:09 xend] DEBUG (DevController:132) Waiting for devices vif. [2006-04-03 16:45:09 xend] DEBUG (DevController:138) Waiting for 0. [2006-04-03 16:45:09 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-04-03 16:45:10 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-04-03 16:45:10 xend] DEBUG (DevController:417) hotplugStatusCallback 1. [2006-04-03 16:45:10 xend] DEBUG (DevController:132) Waiting for devices usb. [2006-04-03 16:45:10 xend] DEBUG (DevController:132) Waiting for devices vbd. [2006-04-03 16:45:10 xend] DEBUG (DevController:138) Waiting for 2049. [2006-04-03 16:45:10 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2006-04-03 16:45:11 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2006-04-03 16:45:11 xend] DEBUG (DevController:417) hotplugStatusCallback 1. [2006-04-03 16:45:11 xend] DEBUG (DevController:138) Waiting for 2050. [2006-04-03 16:45:11 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status. [2006-04-03 16:45:12 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status. [2006-04-03 16:45:12 xend] DEBUG (DevController:417) hotplugStatusCallback 1. [2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices pci. [2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices ioports. [2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices vtpm. [2006-04-03 16:45:12 xend] INFO (XendDomain:360) Domain fedora.fc4 (1) unpaused. my cfg is: kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" memory = 128 name = "fedora.fc4" nics = 1 dhcp = "dhcp" disk = ['file:/xen/fedora/fedora.fc4.img,sda1,w', 'file:/xen/fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro" Any ideas? I guess I am missing something but I cant find. Thanks in advance. have a nice day -- Murat Isik www.bilgiguvenlik.com From wsouto at gmail.com Mon Apr 3 14:25:43 2006 From: wsouto at gmail.com (Walter Souto) Date: Mon, 3 Apr 2006 11:25:43 -0300 Subject: [Fedora-xen] Problems with network interfaces Message-ID: Hi everybody, I'm new to that list and I did read the archives to see if somebody have something like my problem but I can't find anything. I did a clean install of FC5 and Xen using yum. Then I did create one guest using pyguest-install. Everything runs ok. The guest works, but I have experimented some kind of problem with the network of the guest. I can't ping the domain0 and the domain0 can't ping the guest. But how I did keep trying more two or three times and the guest start to responding. Tried again and no response, tried again and have response... So I'm lost here. I did make another guest by copying the image of the first guest, change the mac addr on the config file (in the /etc/xen) and changing hostname, IP addr and mac addr to the same that used in the config file for the new guest. I did create the two guests and they work ok, but the same problem still occurs. One time I have the two guests responding, then, one of the two are working and the other not... The machine is an old PIII600EB with 768Mb RAM. Each guest was created with 256Mb and the domain0 itself has 235Mb. Maybe that machine is not sufice to run Xen with two guests. I'll apreciate any help. TIA, -- Walter. From menguy at transgene.fr Mon Apr 3 14:56:42 2006 From: menguy at transgene.fr (Guillaume Menguy) Date: Mon, 3 Apr 2006 16:56:42 +0200 Subject: [Fedora-xen] FC5 Xen Guest install failed Message-ID: <006d01c6572e$d1ed74b0$802114ac@tg1309313> Hi, Strictly following the FedoraXenQuickstartFC5 wiki (http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5), I get blocked at the following step : /usr/sbin/xenguest-install.py -n fc5template -f /xenimg/fc5template -s 6 -r 512 -l http://xen1 The installation starts and a few seconds after the network configuration, I get : loader received SIGSEGV!. Backtrace: [0x8049865] [0xad2420] [0x8063ca0] [0x805e5e1] [0x804ad21] [0x80cae75] [0x8048131] install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /proc done /dev/pts done /sys done /tmp/ramfs done you may safely reboot your system If your install has exited, you can restart your guest by running 'xm create -c fc5template'. Otherwise, you can reconnect to the console by running 'xm console fc5template' xend.log says : ... [2006-04-03 16:23:35 xend] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' ... I tried on another server with a new install : same problem. Server has 2 Gb RAM and enouth disk space. Thanks for any help. Guillaume Menguy CIO - Transgene -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.hankin at gmail.com Mon Apr 3 15:07:31 2006 From: scott.hankin at gmail.com (Scott D Hankin) Date: Mon, 3 Apr 2006 11:07:31 -0400 Subject: [Fedora-xen] FC5 Xen Guest install failed In-Reply-To: <006d01c6572e$d1ed74b0$802114ac@tg1309313> References: <006d01c6572e$d1ed74b0$802114ac@tg1309313> Message-ID: Howdy - I had a similar problem and fixed it by changing '-l http://sitename' to '-l http://1.2.3.4' (i.e., the IP address for sitename). It was almost like the installer couldn't look up sitename once the networking was started, and failed badly as a result. On 4/3/06, Guillaume Menguy wrote: > > Hi, > > Strictly following the FedoraXenQuickstartFC5 wiki ( > http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5), I get blocked > at the following step : > > /usr/sbin/xenguest-install.py -n fc5template -f /xenimg/fc5template -s 6 > -r 512 -l http://xen1 > The installation starts and a few seconds after the network configuration, > I get : > > loader received SIGSEGV!. Backtrace: > [0x8049865] > [0xad2420] > [0x8063ca0] > [0x805e5e1] > [0x804ad21] > [0x80cae75] > [0x8048131] > install exited abnormally > sending termination signals...done > sending kill signals...done > disabling swap... > unmounting filesystems... > /proc done > /dev/pts done > /sys done > /tmp/ramfs done > you may safely reboot your system > If your install has exited, you can restart your guest by running > 'xm create -c fc5template'. Otherwise, you can reconnect to the console > by running 'xm console fc5template' > xend.log says : > ... > [2006-04-03 16:23:35 xend] DEBUG (blkif:24) exception looking up device > number for xvda: [Errno 2] No such file or directory: '/dev/xvda' > ... > > I tried on another server with a new install : same problem. Server has 2 > Gb RAM and enouth disk space. > Thanks for any help. > > Guillaume Menguy > CIO - Transgene > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Scott ----------------------------- In the beginning, there was nothing, then God said, "Let there be light." And there was light. There was still nothing, but you could see it a lot better. -------------- next part -------------- An HTML attachment was scrubbed... URL: From menguy at transgene.fr Mon Apr 3 15:25:38 2006 From: menguy at transgene.fr (Guillaume Menguy) Date: Mon, 3 Apr 2006 17:25:38 +0200 Subject: [Fedora-xen] FC5 Xen Guest install failed In-Reply-To: Message-ID: <000001c65732$dcb37e90$802114ac@tg1309313> Thank you for your answer. But I already tried this without success. Looks more like a guest root filesystem problem i guess. Guillaume _____ De : Scott D Hankin [mailto:scott.hankin at gmail.com] Envoy? : lundi 3 avril 2006 17:08 ? : Guillaume Menguy Cc : fedora-xen at redhat.com Objet : Re: [Fedora-xen] FC5 Xen Guest install failed Howdy - I had a similar problem and fixed it by changing '-l http://sitename' to '-l http://1.2.3.4' (i.e., the IP address for sitename). It was almost like the installer couldn't look up sitename once the networking was started, and failed badly as a result. On 4/3/06, Guillaume Menguy wrote: Hi, Strictly following the FedoraXenQuickstartFC5 wiki (http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5 ), I get blocked at the following step : /usr/sbin/xenguest-install.py -n fc5template -f /xenimg/fc5template -s 6 -r 512 -l http://xen1 The installation starts and a few seconds after the network configuration, I get : loader received SIGSEGV!. Backtrace: [0x8049865] [0xad2420] [0x8063ca0] [0x805e5e1] [0x804ad21] [0x80cae75] [0x8048131] install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /proc done /dev/pts done /sys done /tmp/ramfs done you may safely reboot your system If your install has exited, you can restart your guest by running 'xm create -c fc5template'. Otherwise, you can reconnect to the console by running 'xm console fc5template' xend.log says : ... [2006-04-03 16:23:35 xend] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' ... I tried on another server with a new install : same problem. Server has 2 Gb RAM and enouth disk space. Thanks for any help. Guillaume Menguy CIO - Transgene -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Scott ----------------------------- In the beginning, there was nothing, then God said, "Let there be light." And there was light. There was still nothing, but you could see it a lot better. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aleksander.adamowski.redhat at altkom.com.pl Mon Apr 3 16:01:32 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Mon, 03 Apr 2006 18:01:32 +0200 Subject: [Fedora-xen] 2.6.15-1.2054_FC5xen0 - no network for guest domains In-Reply-To: <1143838809.3477.24.camel@orbit.scot.redhat.com> References: <441B041E.6060204@altkom.com.pl> <1142889317.21593.41.camel@orbit.scot.redhat.com> <442BA843.9010700@altkom.com.pl> <1143838809.3477.24.camel@orbit.scot.redhat.com> Message-ID: <443146DC.70100@altkom.com.pl> Stephen C. Tweedie wrote: >OK, could you open a bugzilla for this please? We probably want to fix >this at some point, even though you've been able to work around it for >now. > > Got it: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187776 -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From gianni.bassini at provincia.cremona.it Mon Apr 3 15:04:22 2006 From: gianni.bassini at provincia.cremona.it (Gianni Bassini - Provincia di Cremona) Date: Mon, 03 Apr 2006 17:04:22 +0200 Subject: [Fedora-xen] SIGSEGV on xenguest-install.py Message-ID: <44313976.5070403@provincia.cremona.it> I have the same problem... -- -- ----------------------------------------------------- ing. Gianni Bassini (MNE Cefriel 2001) System Administrator - Webmaster Provincia di Cremona C.so Vittorio Emanuele II, 17 - 26100 Cremona (CR) tel 0372-406246 - gianni.bassini at provincia.cremona.it ----------------------------------------------------- From jmorris at redhat.com Mon Apr 3 16:18:04 2006 From: jmorris at redhat.com (James Morris) Date: Mon, 3 Apr 2006 12:18:04 -0400 (EDT) Subject: [Fedora-xen] pygrub failed In-Reply-To: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: On Mon, 3 Apr 2006, Jun OKAJIMA wrote: > What happened here is, in short, like this: > > # Check diskimage formatted as described in grub config > 117 for fstype in grub.fsys.fstypes.values(): > 118 if fstype.sniff_magic(fn, offset): > # If not formatted properly, raise error. > 138 else: > 139 raise RuntimeError, "Unable to read filesystem" I'm also seeing an error raised here, after a successful anaconda over vnc install, without any memory issues. I've since mounted the partition from the image and it seems ok. Perhaps something not quite right in the fs image detection code? - James -- James Morris From sct at redhat.com Mon Apr 3 18:37:50 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 14:37:50 -0400 Subject: [Fedora-xen] "xm create" error: /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' In-Reply-To: <442BBFC8.4060700@altkom.com.pl> References: <442BBFC8.4060700@altkom.com.pl> Message-ID: <1144089470.3563.37.camel@orbit.scot.redhat.com> Hi, On Thu, 2006-03-30 at 13:23 +0200, Aleksander Adamowski wrote: > Introduction: when one installs a Xen guest using xenguest-install.py, > at the end of the installation the guest is shutdown and > xenguest-install.py prints out instructions to start it up with "xm > create -c GUEST_NAME". > > The instructions are wrong - the parameter to "-c" switch is a file > name, so a full path is needed. No, "-c" just means "attach to the console", it doesn't take a filename. And "xm create -c $GUESTNAME" works fine for me. > If one proceeds according to the instructions, and the current working > directory isn't /etc/xen, an unhelpful error will occur: > [root at domzero2 xen]# xm create -c svn > Using config file "svn". This means that it is picking up another file named "svn" in the current directory, not in /etc/xen. If it was picking up an /etc/xen/svn file, it would say so on that "Using config file" line. This is not a bug, you've given it an existing file to work on, but it's not a valid config file, so you get an error. Cheers, Stephen From sct at redhat.com Mon Apr 3 18:42:23 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 14:42:23 -0400 Subject: [Fedora-xen] HD corruption?? In-Reply-To: <442F0D2A.9020207@redhat.com> References: <28707.64.132.126.227.1143850630.squirrel@digitalhermit.com> <1143859656.3383.9.camel@orbit.scot.redhat.com> <442F0D2A.9020207@redhat.com> Message-ID: <1144089744.3563.39.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-04-02 at 01:30 +0200, Shashhin Shinde wrote: > I had an interesting observation the other day with FC5 and xen. I > create a 512M Logical volume > and exported it to xen guest. When I ran fdisk on it the size of the > logical volume shown inside guest > was 536MB , which was more than original size of exported logical > volume. lvdisplay on the host confirmed the size to be 512MB > Thought might be interesting in this context. Sounds like the difference between binary and decimal "MB": 512*1024*1024/1000/1000 is 536 and a bit. --Stephen From sct at redhat.com Mon Apr 3 18:48:10 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 14:48:10 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: <200604031116.AA00974@bbb-jz5c7z9hn9y.digitalinfra.co.jp> References: <20060402213116.GA6492@petra.dvoda.cz> <200604031116.AA00974@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: <1144090090.3563.42.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-03 at 20:16 +0900, Jun OKAJIMA wrote: > > No. The empty file is enough, because xenguest-install.py doesn't use > > pygrub for domU installation boot. You need prepare your virtual disk > > by anaconda which is started by xenguest-install.py. The pygrub > > script is possible use for already __successfully__ installed domU > > only. > Ummm... You mean I have to start anaconda/XenU stuff first, Yes, but... > but I dont have felt that I have succeeded to do so, although > I dont have understanded what xenguest-install.py does yet. You don't have to start it yourself: xenguest-install.py will do it for you automatically. --Stephen From sct at redhat.com Mon Apr 3 18:58:31 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 14:58:31 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: References: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> Message-ID: <1144090711.3563.52.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-04-02 at 22:09 -0400, Winston Chang wrote: > The installer will create the disk image and partition it. If you do > not successfully run to the installer, "xm create -c xxxx" will not > work. The script gives bad instructions when an error occurs. > > The Xen hypervisor takes 32MB of RAM (I think), so you have to make > sure that your dom0 gets less than 224MB. I gave mine 192MB, with > the following in grub.conf: > kernel /xen.gz-2.6.15-1.2054_FC5 dom0_mem=196608 Actually, you should be able to do that manually with xm mem-set 0 192 to balloon the dom0 down to 192MB. It won't balloon automatically below 256MB, but can do so if explicitly told to. > In my opinion, the xenguest-install.py method isn't very good at this > point. > - The installer gives poor feedback when something goes wrong, like > when memory is too low. Agreed, it could well be improved. > - pygrub crashes if your terminal emulation is a little weird > - It creates a whole disk image instead of importing partitions. > This makes it difficult to access domU filesystems from dom0, but > this is often necessary for management. That's just part of the goal of making the domU environment as similar as possible to the dom0. Having a single disk image passed in means you can keep boot info, root fs and swap all in the same place in the host OS. > - It doesn't provide an option for creating images on LVM volumes. If you already have an LVM volume, you can simply specify that and it just works (most of my test xen installs are to LVM.) > Or you could use a kernel from xensource that has the xennet driver > compiled into the kernel. I don't know why the developers decided to > take the driver out of the kernel. The default networking with Xen uses netfront/back and bridging, so that's what we compile in. Is there really a strong need for xennet too? > Pretty much everyone would want > networking on their domU machines, and adding it in this way is just > more complicated. With FC-5 default networking, things just work (though it definitely can interact badly with more complex networking setups); what exactly is complicated and needs fixed? --Stephen From sct at redhat.com Mon Apr 3 19:00:31 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 15:00:31 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: References: Message-ID: <1144090832.3563.55.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-03 at 12:18 -0400, James Morris wrote: > On Mon, 3 Apr 2006, Jun OKAJIMA wrote: > > > What happened here is, in short, like this: > > > > # Check diskimage formatted as described in grub config > > 117 for fstype in grub.fsys.fstypes.values(): > > 118 if fstype.sniff_magic(fn, offset): > > # If not formatted properly, raise error. > > 138 else: > > 139 raise RuntimeError, "Unable to read filesystem" > > I'm also seeing an error raised here, after a successful anaconda over vnc > install, without any memory issues. I've since mounted the partition from > the image and it seems ok. > > Perhaps something not quite right in the fs image detection code? Hmm --- did you create a manual partition layout, or did you just use the default one provided by the installer? If it's a manual layout, then the problem may be that you (or the installer) didn't set the "active" flag on the partition containing the kernel images. pygrub looks for that to know which partition to try booting from. --Stephen From thomas.uhl at gmail.com Mon Apr 3 19:00:38 2006 From: thomas.uhl at gmail.com (Thomas Uhl) Date: Mon, 3 Apr 2006 21:00:38 +0200 Subject: [Fedora-xen] Fwd: Problems with e1000 drivers with kernel 2.6.15... In-Reply-To: <2d90b1800604030223g517f9c2bmfb4a66b2c98c6bab@mail.gmail.com> References: <2d90b1800603290934o7257a8aw1f8801d158def919@mail.gmail.com> <2d90b1800604030223g517f9c2bmfb4a66b2c98c6bab@mail.gmail.com> Message-ID: <2d90b1800604031200x531e7e34r2b4f101b6c277dd6@mail.gmail.com> FYI: same problem with kernel-xen0-2.6.16-1.2080_FC5. Perhaps I should mention that I am booting the 64 bit version. Yours Tom On 3/29/06, Thomas Uhl wrote: > Hi! > > I am testing xen on a preproduction Intel box. The standard kernel of > FC5 (2.6.15-1.2054) does not detect the embedded e1000 NICs in my > setup. So I tried kernel 2.6.16-1.2102 from rawhide. It worked. When > will we see a "xenified" 2.6.16 kernel in rawhide? > > Yours > Tom > > Here the dmesg output with kernel 2.6.16... > > Intel(R) PRO/1000 Network Driver - version 7.0.33-k2-NAPI > Copyright (c) 1999-2005 Intel Corporation. > ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 19 > PCI: Setting latency timer of device 0000:05:00.0 to 64 > e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) > From jmorris at redhat.com Mon Apr 3 19:57:13 2006 From: jmorris at redhat.com (James Morris) Date: Mon, 3 Apr 2006 15:57:13 -0400 (EDT) Subject: [Fedora-xen] pygrub failed In-Reply-To: <1144090832.3563.55.camel@orbit.scot.redhat.com> Message-ID: On Mon, 3 Apr 2006, Stephen C. Tweedie wrote: > Hmm --- did you create a manual partition layout, or did you just use > the default one provided by the installer? It was a standard layout, although I did select minimal packages (shouldn't affect it, I hope). > If it's a manual layout, then the problem may be that you (or the > installer) didn't set the "active" flag on the partition containing the > kernel images. pygrub looks for that to know which partition to try > booting from. # fdisk -l xt4-disk last_lba(): I don't know how to handle files with mode 81ed You must set cylinders. You can do this from the extra functions menu. Disk xt4-disk: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System xt4-disk1 * 1 13 104391 83 Linux xt4-disk2 14 261 1992060 8e Linux LVM # losetup -o 32256 /dev/loop0 xt4-disk # fsck.ext3 -v /dev/loop0 e2fsck 1.38 (30-Jun-2005) /boot: clean, 32/26104 files, 12598/104388 blocks Look ok? - James -- James Morris From sct at redhat.com Mon Apr 3 20:34:30 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 03 Apr 2006 16:34:30 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: References: Message-ID: <1144096470.9387.10.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-03 at 15:57 -0400, James Morris wrote: > # fdisk -l xt4-disk > last_lba(): I don't know how to handle files with mode 81ed > You must set cylinders. > You can do this from the extra functions menu. > > Disk xt4-disk: 0 MB, 0 bytes > 255 heads, 63 sectors/track, 0 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes That's all normal; > > Device Boot Start End Blocks Id System > xt4-disk1 * 1 13 104391 83 Linux > xt4-disk2 14 261 1992060 8e Linux LVM looks fine. Hmm. > # losetup -o 32256 /dev/loop0 xt4-disk > # fsck.ext3 -v /dev/loop0 > e2fsck 1.38 (30-Jun-2005) > /boot: clean, 32/26104 files, 12598/104388 blocks Does it seem to contain the correct boot files? --Stephen From jmorris at redhat.com Mon Apr 3 20:45:13 2006 From: jmorris at redhat.com (James Morris) Date: Mon, 3 Apr 2006 16:45:13 -0400 (EDT) Subject: [Fedora-xen] pygrub failed In-Reply-To: <1144096470.9387.10.camel@orbit.scot.redhat.com> Message-ID: On Mon, 3 Apr 2006, Stephen C. Tweedie wrote: > > # losetup -o 32256 /dev/loop0 xt4-disk > > # fsck.ext3 -v /dev/loop0 > > e2fsck 1.38 (30-Jun-2005) > > /boot: clean, 32/26104 files, 12598/104388 blocks > > Does it seem to contain the correct boot files? Yes, as far as I can tell: # ls -l total 3456 -rw-r--r-- 1 root root 28213 Mar 14 16:58 config-2.6.15-1.2054_FC5xenU drwxr-xr-x 2 root root 1024 Mar 30 19:32 grub -rw-r--r-- 1 root root 1601303 Mar 30 19:31 initrd-2.6.15-1.2054_FC5xenU.img drwx------ 2 root root 12288 Mar 30 19:26 lost+found -rw-r--r-- 1 root root 637784 Mar 14 16:58 System.map-2.6.15-1.2054_FC5xenU -rw-r--r-- 1 root root 1232540 Mar 14 16:58 vmlinuz-2.6.15-1.2054_FC5xenU # ls -l grub total 203 -rw-r--r-- 1 root root 64 Mar 30 19:32 device.map -rw-r--r-- 1 root root 7424 Mar 30 19:32 e2fs_stage1_5 -rw-r--r-- 1 root root 7328 Mar 30 19:32 fat_stage1_5 -rw-r--r-- 1 root root 6592 Mar 30 19:32 ffs_stage1_5 -rw------- 1 root root 621 Mar 30 19:32 grub.conf -rw-r--r-- 1 root root 6592 Mar 30 19:32 iso9660_stage1_5 -rw-r--r-- 1 root root 8032 Mar 30 19:32 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Mar 30 19:32 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 6752 Mar 30 19:32 minix_stage1_5 -rw-r--r-- 1 root root 9056 Mar 30 19:32 reiserfs_stage1_5 -rw-r--r-- 1 root root 7028 Feb 28 23:41 splash.xpm.gz -rw-r--r-- 1 root root 512 Mar 30 19:32 stage1 -rw-r--r-- 1 root root 102332 Mar 30 19:32 stage2 -rw-r--r-- 1 root root 6944 Mar 30 19:32 ufs2_stage1_5 -rw-r--r-- 1 root root 6144 Mar 30 19:32 vstafs_stage1_5 -rw-r--r-- 1 root root 8768 Mar 30 19:32 xfs_stage1_5 -- James Morris From winston at stdout.org Mon Apr 3 21:16:11 2006 From: winston at stdout.org (Winston Chang) Date: Mon, 3 Apr 2006 17:16:11 -0400 Subject: [Fedora-xen] pygrub failed In-Reply-To: <1144090711.3563.52.camel@orbit.scot.redhat.com> References: <200604021640.AA00969@bbb-jz5c7z9hn9y.digitalinfra.co.jp> <1144090711.3563.52.camel@orbit.scot.redhat.com> Message-ID: <47104559-1F80-4040-86E8-479E09884425@stdout.org> >> - It creates a whole disk image instead of importing partitions. >> This makes it difficult to access domU filesystems from dom0, but >> this is often necessary for management. > > That's just part of the goal of making the domU environment as similar > as possible to the dom0. Having a single disk image passed in > means you > can keep boot info, root fs and swap all in the same place in the host > OS. I understand the motivation here, but it does make it much harder to manipulate the domU filesystem from dom0. I personally couldn't figure out how to mount a domU partition when using the whole-disk method. I imagine that it's even more complicated when the domU has its own LVM volumes. This issue aside, I do like the idea of having a single disk image for each domU, though, since it keeps things simple. It's nice to have the kernel, swap partition, and main partition (and whatever else) all in one place. But it seems very inelegant to use the ancient DOS partitioning scheme and then put LVM on top of it. Things would be simpler if a domU could start out with LVM right on top of the disk image, like if you ran 'pvcreate /dev/sda' in the domU. Then you wouldn't need a separate /boot partition; it could be just another LVM volume. I know that this is problematic for "real" installations of Linux, because of the BIOS <1024 cylinder limitation (is that still an issue?), and because grub doesn't understand LVM. But the first limitation simply doesn't exist with a domU under Xen (I hope), and the second can be worked around -- I imagine that making pygrub understand LVM would be easier than making grub understand LVM, since there aren't the same memory/space limitations. In short, why emulate all crufty old mechanics of booting and partitioning a PC when Xen provides a way to (finally) avoid it? You would lose the ability to image a domU disk image right onto a real disk and then boot a real machine with that disk, but I think that's the only thing, and it's pretty minor. >> - It doesn't provide an option for creating images on LVM volumes. > > If you already have an LVM volume, you can simply specify that and it > just works (most of my test xen installs are to LVM.) That's good to know... The script doesn't make it clear that it has that capability. If I remember right, I tried that, and the config file said file:/dev/VolGroup00/fc5_root, or something like that instead of phy:.., which seems like an error. (I was still having other Xen problems so I never got it working this way.) The LVM volume already has a size, so what happens when you specify a disk image size to the installer script? >> Or you could use a kernel from xensource that has the xennet driver >> compiled into the kernel. I don't know why the developers decided to >> take the driver out of the kernel. > > The default networking with Xen uses netfront/back and bridging, so > that's what we compile in. Is there really a strong need for xennet > too? I'm not an expert on Xen network drivers... All I know is that when I booted the jailtime.org FC5 image (and a Centos 4.2 image that I created myself) using the stock FC5 xenU kernel, that it would say there was no eth0 on boot. I managed to get eth0 to show up by loading the xennet kernel module, as recommended by someone on the xensource xen-users list. If there's way to get a domU's eth0 to show up using the stock XenU kernel and without loading a module, that would be great. How would I do this? --Winston From brads at redhat.com Mon Apr 3 21:48:53 2006 From: brads at redhat.com (Brad Smith) Date: Mon, 03 Apr 2006 17:48:53 -0400 Subject: [Fedora-xen] Xend requires a net connection? Message-ID: <44319845.6090705@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have finally gotten xen working on my FC5 system (the subject of a couple of prior emails to this list). The reason xend kept hanging seems to be that it requires a net connection to start. If eth0 is down or has had an IP assigned but isn't actually connected to the network, xend just hangs while starting. But if I connect to the network first everything works. I didn't see anything about this on the wiki, so can someone please provide more information? Is it just trying to resolve a name or something? If so, I'd like to know so I can configure my systems such that running xen while offline is an option. I tried stracing it but haven't been able to figure out what's going on. Thanks, - --Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEMZhFDvp49DvQ8kcRAvAcAJ0cCohkp2eoPlDHN5mvC0hrjAkrqwCeJk3V m0VchQ8IIhQhF7X1UmPJmZ4= =beyc -----END PGP SIGNATURE----- From esmithmail at gmail.com Tue Apr 4 04:19:47 2006 From: esmithmail at gmail.com (Eric Smith) Date: Mon, 3 Apr 2006 23:19:47 -0500 Subject: [Fedora-xen] no eth0 device Message-ID: <820bc1260604032119q2799768ex3c1168991be5c40e@mail.gmail.com> Hi, With clean FC5 install followed by yum upgrade, and after installing xen, kernel-xen0, and kernel-xenU: I boot into kernel-xen0 ok, xend starts, things like xm list work, but my eth0 device is not found at boot time. Booting into the non-xen kernel and it works as expected. eth0 is Broadcom 4400 10/100BaseT Ethernet. Perhaps I'm missing the main xen documentation, but I didn't see anything about this in the quickstart guide. Thank you for your help, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From yongkang.you at intel.com Tue Apr 4 05:11:46 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 4 Apr 2006 13:11:46 +0800 Subject: [Fedora-xen] no eth0 device Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20E3@pdsmsx402.ccr.corp.intel.com> Hi Smith, I guess your NIC driver isn?t built into default Xen0 kernel or as Xen0 modules. If so, you have to rebuild your Xen kernel alone. :-( Best Regards, Yongkang (Kangkang) ?? ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Eric Smith Sent: 2006?4?4? 12:20 To: fedora-xen at redhat.com Subject: [Fedora-xen] no eth0 device Hi, With clean FC5 install followed by yum upgrade, and after installing xen, kernel-xen0, and kernel-xenU: I boot into kernel-xen0 ok, xend starts, things like xm list work, but my eth0 device is not found at boot time. Booting into the non-xen kernel and it works as expected. eth0 is Broadcom 4400 10/100BaseT Ethernet. Perhaps I'm missing the main xen documentation, but I didn't see anything about this in the quickstart guide. Thank you for your help, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianni.bassini at provincia.cremona.it Tue Apr 4 08:13:28 2006 From: gianni.bassini at provincia.cremona.it (Gianni Bassini - Provincia di Cremona) Date: Tue, 04 Apr 2006 10:13:28 +0200 Subject: [Fedora-xen] Re: SIGSEGV on xenguest-install.py Message-ID: <44322AA8.20507@provincia.cremona.it> solved i copied the entire dvd on the host disks into the html dir and used the host httpd Bye Gianni -- -- ----------------------------------------------------- ing. Gianni Bassini (MNE Cefriel 2001) System Administrator - Webmaster Provincia di Cremona C.so Vittorio Emanuele II, 17 - 26100 Cremona (CR) tel 0372-406246 - gianni.bassini at provincia.cremona.it ----------------------------------------------------- From rstory-l at 2006.revelstone.com Tue Apr 4 11:36:37 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 4 Apr 2006 07:36:37 -0400 Subject: [Fedora-xen] yum update removes modules for running dom0 kernel! Message-ID: <20060404073637.139f19ec@aud.vb.futz.org> Anyone else noticed that yum update removes modules for running dom0 kernel!?!?! I've created a bug report here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187894 From rstory-l at 2006.revelstone.com Tue Apr 4 12:17:53 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 4 Apr 2006 08:17:53 -0400 Subject: [Fedora-xen] Problems with Xen + FC5 + Thinkpad In-Reply-To: <1143859166.3383.1.camel@orbit.scot.redhat.com> References: <442AB732.1070208@redhat.com> <20060329143317.7efcd1bc@aud.vb.futz.org> <1143859166.3383.1.camel@orbit.scot.redhat.com> Message-ID: <20060404081753.0cc083c4@aud.vb.futz.org> On Fri, 31 Mar 2006 21:39:25 -0500 Stephen wrote: SCT> > Did you do the part about updating grub to include 'init 3' to disable SCT> > X? If so, go back and delete the 'init' (you just need '3'). This fixed SCT> > the dom0 kernel hang I had. SCT> SCT> > I asked someone in the #fedora irc channel to fix this, but it's still SCT> > there. SCT> SCT> Please open a bugzilla for this so we can look into it. There is SCT> nothing fundamentally incompatible between Xen and X: my Xen desktop, SCT> running X, had an uptime of over 8 days when I shut it down earlier SCT> today. init 3 is *not* needed in general; Note that I wasn't complaining about X, which does work, but about the wiki page suggesting to add 'init 3' to the boot args to boot into run level 3. That's wrong, and causes the kernel to hang on boot. A simple '3' is needed to boot into run level 3. Still want a bug report? It should be fixed, because a newbie isn't going to know this, and will think xen doesn't work. From rstory-l at 2006.revelstone.com Tue Apr 4 12:34:00 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 4 Apr 2006 08:34:00 -0400 Subject: [Fedora-xen] Problems with network interfaces In-Reply-To: References: Message-ID: <20060404083400.6fdd7d50@aud.vb.futz.org> On Mon, 3 Apr 2006 11:25:43 -0300 Walter wrote: WS> The machine is an old PIII600EB with 768Mb RAM. Each guest was created WS> with 256Mb and the domain0 itself has 235Mb. Maybe that machine is not WS> sufice to run Xen with two guests. That's not it.. I've got 2 guests running on a PIII 450 w/768MB of RAM. From menguy at transgene.fr Tue Apr 4 13:06:31 2006 From: menguy at transgene.fr (Guillaume Menguy) Date: Tue, 4 Apr 2006 15:06:31 +0200 Subject: [Fedora-xen] FC5 Xen Guest install failed In-Reply-To: <000001c65732$dcb37e90$802114ac@tg1309313> Message-ID: <007901c657e8$986ae7d0$802114ac@tg1309313> Problem solved. Same problem as "SIGSEGV on xenguest-install.py" topic. I solved it by running the HTTP source server on another machine. Using the dom0 itself crashed the installation process just after the IP configuration. Did anyone else encounter the same problem ? Maybe the Wiki should be updated... Thanks, Guillaume _____ De : Scott D Hankin [mailto:scott.hankin at gmail.com] Envoy? : lundi 3 avril 2006 17:08 ? : Guillaume Menguy Cc : fedora-xen at redhat.com Objet : Re: [Fedora-xen] FC5 Xen Guest install failed Howdy - I had a similar problem and fixed it by changing '-l http://sitename' to '-l http://1.2.3.4' (i.e., the IP address for sitename). It was almost like the installer couldn't look up sitename once the networking was started, and failed badly as a result. On 4/3/06, Guillaume Menguy wrote: Hi, Strictly following the FedoraXenQuickstartFC5 wiki (http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5 ), I get blocked at the following step : /usr/sbin/xenguest-install.py -n fc5template -f /xenimg/fc5template -s 6 -r 512 -l http://xen1 The installation starts and a few seconds after the network configuration, I get : loader received SIGSEGV!. Backtrace: [0x8049865] [0xad2420] [0x8063ca0] [0x805e5e1] [0x804ad21] [0x80cae75] [0x8048131] install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /proc done /dev/pts done /sys done /tmp/ramfs done you may safely reboot your system If your install has exited, you can restart your guest by running 'xm create -c fc5template'. Otherwise, you can reconnect to the console by running 'xm console fc5template' xend.log says : ... [2006-04-03 16:23:35 xend] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' ... I tried on another server with a new install : same problem. Server has 2 Gb RAM and enouth disk space. Thanks for any help. Guillaume Menguy CIO - Transgene -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Scott ----------------------------- In the beginning, there was nothing, then God said, "Let there be light." And there was light. There was still nothing, but you could see it a lot better. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at heilpern.com Tue Apr 4 15:24:55 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Tue, 4 Apr 2006 11:24:55 -0400 (EDT) Subject: [Fedora-xen] Networking problem with host Message-ID: <18382127.21144164295430.JavaMail.root@heilpern.com> An HTML attachment was scrubbed... URL: From yongkang.you at intel.com Tue Apr 4 15:27:46 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 4 Apr 2006 23:27:46 +0800 Subject: [Fedora-xen] yum update removes modules for running dom0 kernel! Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20EB@pdsmsx402.ccr.corp.intel.com> Em~ I have read your bug. I am curious that if yum update has installed 2.6.16-1.2080_FC5, why the error still report: Could not load /lib/modules/2.6.15-1.2054_FC5xen0/modules.dep: No such file or directory Did you reboot the machine with new installed kernel? Is there /lib/modules/2.6.16-1.2080_FC5xen0 there? Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Robert Story >Sent: 2006?4?4? 19:37 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] yum update removes modules for running dom0 kernel! > >Anyone else noticed that yum update removes modules for running dom0 >kernel!?!?! > >I've created a bug report here: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187894 > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From bench at silentmedia.com Tue Apr 4 16:52:08 2006 From: bench at silentmedia.com (Ben) Date: Tue, 4 Apr 2006 09:52:08 -0700 (PDT) Subject: [Fedora-xen] Networking problem with host In-Reply-To: <18382127.21144164295430.JavaMail.root@heilpern.com> References: <18382127.21144164295430.JavaMail.root@heilpern.com> Message-ID: Xen plays with your networking a lot, and the default way it does things seems quite awkward to me if you have more than a single interface. I've found this to be quite helpful: http://wiki.xensource.com/xenwiki/XenNetworkingSuse?highlight=%28XenNetworking%29 On Tue, 4 Apr 2006, Mark A Heilpern wrote: > Hello, > > I'm using FC5 and have near zero experience with Xen, and I'm running into a problem I can't locate answers for. > > First... my system without Xen running: I have two ethernet interfaces, eth0 and eth1, where eth1 is connected to the internet and eth0 is my private > NAT'd network; this system is my firewall. I'm using Firestarter to configure things and I'm able to connect FC5 to any location I wish, internal and > external, and my internal machines are able to connect to the firewall as well as the internet. Both eth0 and eth1 are configured as static IPs, and > all machines in my private network are static IPs ( > > > Now, my firewall is also running other services and I'm interested in moving these services to their own virtual guest machines eventually. First > though, I think I should be able to boot into a Xen-enabled kernel and have the same level of functionality I currently have without Xen. My kernel > boots fine and seems to operate but I'm not able to do much with networking... I can't connect to any machine (through eth0 or eth1) from my Xen0 > kernel, and my private network machines cannot connect to my firewall or through my firewall. > > I see many posts where people have guest O/S networking issues... but in my case I haven't even reached the stage of trying to create a guest O/S. > > Thanks for any tips towards my getting this resolved! > > > From sct at redhat.com Tue Apr 4 17:08:25 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 04 Apr 2006 13:08:25 -0400 Subject: [Fedora-xen] no eth0 device In-Reply-To: <820bc1260604032119q2799768ex3c1168991be5c40e@mail.gmail.com> References: <820bc1260604032119q2799768ex3c1168991be5c40e@mail.gmail.com> Message-ID: <1144170505.3411.2.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-03 at 23:19 -0500, Eric Smith wrote: > I boot into kernel-xen0 ok, xend starts, things like xm list work, but > my eth0 device is not found at boot time. Booting into the non-xen > kernel and it works as expected. eth0 is Broadcom 4400 10/100BaseT > Ethernet. Unfortunately, when we were building for FC5, this module was not buildable for the Xen kernels: I've opened https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187929 to keep track of it. --Stephen From muratisik at bilgiguvenlik.com Tue Apr 4 21:36:10 2006 From: muratisik at bilgiguvenlik.com (Murat =?iso-8859-9?Q?I=FE=FDk?=) Date: Wed, 5 Apr 2006 00:36:10 +0300 (EEST) Subject: [Fedora-xen] guest domain boot hangs at "Freeing unused kernel memory:" Message-ID: <50234.195.174.105.65.1144186570.squirrel@webmail.bilcag.net> hello, I am using fc4 image from http://jailtime.org/download:fedora:fc4 on fc5 with xen. however when I run "xm create fedora.fc4.xen.cfg -c", the boot sequence hangs at "Freeing unused kernel memory:". my cfg is: kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" memory = 128 name = "fedora.fc4" vif = [''] dhcp = "dhcp" disk = ['file:/xen/fedora/fedora.fc4.img,sda1,w', 'file:/xen/fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro" I found this about the problem: http://wiki.xensource.com/xenwiki/XenFaq#head-ea8b39d71e49cc16d287257de4c482f99d883097 however I checked for the devs and they are there: mount -o loop fedora.fc4.img /mnt/ ls -alh /mnt/dev/ total 8.0K drwxr-xr-x 2 root root 4.0K Sep 22 2005 . drwxr-xr-x 21 root root 4.0K Feb 10 08:07 .. crw------- 1 root root 5, 1 Sep 22 2005 console prw------- 1 root root 0 Apr 27 2005 initctl crw-rw-rw- 1 root root 1, 3 Sep 22 2005 null crw-rw-rw- 1 root root 5, 0 Sep 22 2005 tty crw-rw-rw- 1 root root 1, 5 Sep 22 2005 zero Also the lines [2006-04-05 00:29:27 xend] DEBUG (blkif:24) exception looking up device number for sda2: [Errno 2] No such file or directory: '/dev/sda2' and [2006-04-05 00:29:27 xend] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' are interesting since all files are in place. Any ideas? have a nice day. -- Murat I??k www.bilgiguvenlik.com From matbayer.web at web.de Tue Apr 4 11:15:57 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Tue, 04 Apr 2006 13:15:57 +0200 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <266916042@web.de> Hi, i have a brand new system with VT technology (HP XW4300).i am running FC5 with XEN kernel 2.6.16-1.2080_FC5xen0 on it.on the harddisk (/dev/sda) there are two partitions. sda1 has a native windows XP system installed while sda2 is /boot and sda3 is / for the FC5 system. now i want to run the windows system under xen control using the installed windows system on the first partition. what would i need to configure to make this work ?how does the config file needs to look like ?is there a documentation available on how to make windows run unmodified under xen ? any hints welcome ! Thanks. SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at heilpern.com Wed Apr 5 02:20:07 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Tue, 4 Apr 2006 22:20:07 -0400 (EDT) Subject: [Fedora-xen] Networking problem with host In-Reply-To: Message-ID: <9497985.01144203607337.JavaMail.root@heilpern.com> Thanks for the response, I definitely appreciate it. What I'm seeing is from boot to boot into the Xen0 kernel, it seems to be random which network card gets assigned to eth0 and which to eth1. I haven't rebooted enough since upgrading to FC5 to know if this is tied to the Xen kernel or just an FC5 thing, but I never saw it with FC4. My modprobe.conf contains alias lines for eth0 and 1, binding them to specific drivers (the cards are not identical), but I guess this isn't being honored. Has anyone else seen anything like this? ------------------------- Original Message: From: Ben To: Mark A Heilpern Date: Tuesday, April 4 2006 01:52 PM Subject: Re: [Fedora-xen] Networking problem with host Xen plays with your networking a lot, and the default way it does things seems quite awkward to me if you have more than a single interface. I've found this to be quite helpful: http://wiki.xensource.com/xenwiki/XenNetworkingSuse?highlight=%28XenNetworking%29 On Tue, 4 Apr 2006, Mark A Heilpern wrote: > Hello, > > I'm using FC5 and have near zero experience with Xen, and I'm running into a problem I can't locate answers for. > > First... my system without Xen running: I have two ethernet interfaces, eth0 and eth1, where eth1 is connected to the internet and eth0 is my private > NAT'd network; this system is my firewall. I'm using Firestarter to configure things and I'm able to connect FC5 to any location I wish, internal and > external, and my internal machines are able to connect to the firewall as well as the internet. Both eth0 and eth1 are configured as static IPs, and > all machines in my private network are static IPs ( > > > Now, my firewall is also running other services and I'm interested in moving these services to their own virtual guest machines eventually. First > though, I think I should be able to boot into a Xen-enabled kernel and have the same level of functionality I currently have without Xen. My kernel > boots fine and seems to operate but I'm not able to do much with networking... I can't connect to any machine (through eth0 or eth1) from my Xen0 > kernel, and my private network machines cannot connect to my firewall or through my firewall. > > I see many posts where people have guest O/S networking issues... but in my case I haven't even reached the stage of trying to create a guest O/S. > > Thanks for any tips towards my getting this resolved! > > > From yongkang.you at intel.com Wed Apr 5 05:12:51 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 5 Apr 2006 13:12:51 +0800 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20ED@pdsmsx402.ccr.corp.intel.com> Hi Matthias, I think the bootloader is installed at /dev/sda, which can select to boot the Windows XP partition right? You can modify /etc/xen/xmexample.hvm to change to following configuration and create the VMX with it. disk = [ 'phy:/dev/sda,ioemu:hda,w' ] sdl=1 vnc=0 vncviewer=0 Creating Windows VMX has no difference with other unmodified Linux. Best Regards, Yongkang (Kangkang) ?? ________________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer Sent: 2006?4?4? 19:16 To: fedora-xen at redhat.com Subject: [Fedora-xen] configuration for windows image with VT machine Hi, ? i have a brand new system with VT technology (HP XW4300). i am running FC5 with XEN kernel 2.6.16-1.2080_FC5xen0 on it. on the harddisk (/dev/sda) there are two partitions. sda1 has a native windows XP system installed while sda2 is /boot and sda3 is / for the FC5 system. ? now i want to run the windows system under xen control using the installed windows system on the first partition. ? what would i need to configure to make this work ? how does the config file needs to look like ? is there a documentation available on how to make windows run unmodified under xen ? ? any hints welcome ! ? Thanks. ! SMS schreiben mit WEB.DE FreeMail - einfach, schnell und??? kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192?? From gregor.pirnaver at email.si Wed Apr 5 13:04:36 2006 From: gregor.pirnaver at email.si (Gregor Pirnaver) Date: Wed, 5 Apr 2006 15:04:36 +0200 Subject: [Fedora-xen] Can't boot xen0 with ACPI enabled Message-ID: <20060405130442.E0C648B89D@www1.email.si> Computer booting to xen0 hangs if I don't disable ACPI (computer has two Xeon processors). Even "acpi=ht" doesn't work. The last lines displayed are many messages like: ... PCI: BRIDGE ... IO window: disabled MEM window: disabled PREFETCH window: disabled ... and before that two lines with something like: PCI: Cannot allocate resource region 4 of device ... With ACPI disabled it boots normally: /boot/grub/menu.lst: ... title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 acpi=off module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol00 module /initrd-2.6.16-1.2080_FC5xen0.img ... Is there anything I can do to get hyper-threading working? ____________________ http://www.email.si/ From rstory-l at 2006.revelstone.com Wed Apr 5 14:58:12 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Wed, 5 Apr 2006 10:58:12 -0400 Subject: [Fedora-xen] yum update removes modules for running dom0 kernel! In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575044A20EB@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575044A20EB@pdsmsx402.ccr.corp.intel.com> Message-ID: <20060405105812.02e41aac@aud.vb.futz.org> On Tue, 4 Apr 2006 23:27:46 +0800 Yongkang wrote: YY> I am curious that if yum update has installed 2.6.16-1.2080_FC5, why the YY> error still report: Could not YY> load /lib/modules/2.6.15-1.2054_FC5xen0/modules.dep: No such file or YY> directory YY> YY> Did you reboot the machine with new installed kernel? Is YY> there /lib/modules/2.6.16-1.2080_FC5xen0 there? That directory does exist, but no, I haven't rebooted. That's the point - the modules for the current running kernel were deleted! From rstory-l at 2006.revelstone.com Wed Apr 5 15:02:03 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Wed, 5 Apr 2006 11:02:03 -0400 Subject: [Fedora-xen] Networking problem with host In-Reply-To: <9497985.01144203607337.JavaMail.root@heilpern.com> References: <9497985.01144203607337.JavaMail.root@heilpern.com> Message-ID: <20060405110203.68a5bcc7@aud.vb.futz.org> On Tue, 4 Apr 2006 22:20:07 -0400 (EDT) Mark wrote: MAH> What I'm seeing is from boot to boot into the Xen0 kernel, it seems to be MAH> random which network card gets assigned to eth0 and which to eth1. Check out 'man iftab'... it can tie interfaces to specific mac addresses.. Don't know how it interacts with xen, though... From yongkang.you at intel.com Wed Apr 5 15:42:04 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 5 Apr 2006 23:42:04 +0800 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20F6@pdsmsx402.ccr.corp.intel.com> Aha, you miss the 'ioemu' in disk option. Please try with this: disk = [ 'phy:/dev/sda,ioemu:hda,w' ] if still can not, please paste /var/log/xend.log and /var/log/xend-debug.log. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: Matthias Bayer [mailto:matbayer.web at web.de] >Sent: 2006?4?5? 23:34 >To: fedora-xen at redhat.com; You, Yongkang >Subject: RE: [Fedora-xen] configuration for windows image with VT machine > >Hi Yonkang, > >you are right, grub is installed on /dev/sda and i can choose which OS i want to >boot. > >i still can't boot the windows system from my first partition using this config file >(any ideas what's wrong here ?). > >name = "WinXPPro_xendom1_local" >builder = "hvm" >memory = "512" >disk = [ 'phy:/dev/sda,hda,w' ] >vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:63:72:e2' ] >on_reboot = 'restart' >on_crash = 'restart' >kernel = '/usr/lib/xen/boot/hvmloader' >device_model = '/usr/lib/xen/bin/qemu-dm' >sdl = 1 # use SDL for graphics >vnc = 0 # use VNC for graphics >vncviewer = 0 # spawn vncviewer by default > >if i create the domain with 'xm create WinXPPro_xendom1_local' everything >looks good, no errors shown. >xm list shows: > >Name ID Mem(MiB) VCPUs State Time(s) >Domain-0 0 2504 2 r----- 320.7 >WinXPPro_xendom1_local 4 512 1 -b---- 0.0 > >also, where can is see why it stops and how far the boot process went ? >any hints very welcome ! > >regards, >Matthias > > > > >> Hi Matthias, >> >> I think the bootloader is installed at /dev/sda, which can select to boot the >Windows XP partition right? >> You can modify /etc/xen/xmexample.hvm to change to following >configuration and create the VMX with it. >> disk = [ 'phy:/dev/sda,ioemu:hda,w' ] >> sdl=1 >> vnc=0 >> vncviewer=0 >> >> Creating Windows VMX has no difference with other unmodified Linux. >> >> Best Regards, >> Yongkang (Kangkang) ?????? >> ________________________________________ >> From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >> Sent: 2006???4???4??? 19:16 >> To: fedora-xen at redhat.com >> Subject: [Fedora-xen] configuration for windows image with VT machine >> >> Hi, >> >> i have a brand new system with VT technology (HP XW4300). >> i am running FC5 with XEN kernel 2.6.16-1.2080_FC5xen0 on it. >> on the harddisk (/dev/sda) there are two partitions. sda1 has a native >windows XP system installed while sda2 is /boot and sda3 is / for the FC5 >system. >> >> now i want to run the windows system under xen control using the installed >windows system on the first partition. >> >> what would i need to configure to make this work ? >> how does the config file needs to look like ? >> is there a documentation available on how to make windows run unmodified >under xen ? >> >> any hints welcome ! >> >> Thanks. >> >> >> ! >> >> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 >> >> > > >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From matbayer.web at web.de Wed Apr 5 16:37:11 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 05 Apr 2006 18:37:11 +0200 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <268074309@web.de> Aha, RIGHT ! thanks for this !! little mistake here .. now i am a step further but now the following happens: i create the domain, see the window poping up, grub shows up and then - no matter whats written within grub - boots my linux system (which is my Dom0) again :-( ????? i changed the boot order within grub to default to the windows system (because selecting by hand in the upcoming window is very very slow ...) but still boots my linux system .... which grub is used, i changed some entries withing grub of Dom0 but the changes are not reflected when creating the domain ? after selecting by hand i can choose the windows entry and boot the system. :-) ... BUT ... i hangs after a while, i cannot connect to it and it's not pinging .... i selected 'safe mode' during startup of the windows system and the last entry i see is: multi(0)\disk(0)\rdisk(0)\partition(1)\Windows\system32\drivers\Mup.sys hmm.. the logfile for the domain shows: set_map result i 3ff result bd2a5 HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $ ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (5375 MBytes) ata0 slave: Unknown device ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom ata1 slave: Unknown device Booting from Hard Disk... int13_harddisk: function 41, unmapped device for ELDL=81 int13_harddisk: function 08, unmapped device for ELDL=81 *** int 15h function AX=00C0, BX=0000 not yet supported! *** int 15h function AX=5300, BX=0000 not yet supported! *** int 15h function AX=5304, BX=0000 not yet supported! unsupported PCI BIOS function 0x0E *** int 15h function AX=5300, BX=0000 not yet supported! int13_harddisk: function 15, unmapped device for ELDL=81 xm list shows that the created windows domain is still consuming time. Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2504 2 r----- 1391.7 WinXPPro_xendom1_local 17 512 1 ------ 104.5 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2504 2 r----- 1467.3 WinXPPro_xendom1_local 17 512 1 ------ 528.2 another hint for me ? thanks, Matthias > Aha, you miss the 'ioemu' in disk option. > Please try with this: > disk = [ 'phy:/dev/sda,ioemu:hda,w' ] > > if still can not, please paste /var/log/xend.log and /var/log/xend-debug.log. > > Best Regards, > Yongkang (Kangkang) ?????? > > >-----Original Message----- > >From: Matthias Bayer [mailto:matbayer.web at web.de] > >Sent: 2006???4???5??? 23:34 > >To: fedora-xen at redhat.com; You, Yongkang > >Subject: RE: [Fedora-xen] configuration for windows image with VT machine > > > >Hi Yonkang, > > > >you are right, grub is installed on /dev/sda and i can choose which OS i want to > >boot. > > > >i still can't boot the windows system from my first partition using this config file > >(any ideas what's wrong here ?). > > > >name = "WinXPPro_xendom1_local" > >builder = "hvm" > >memory = "512" > >disk = [ 'phy:/dev/sda,hda,w' ] > >vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:63:72:e2' ] > >on_reboot = 'restart' > >on_crash = 'restart' > >kernel = '/usr/lib/xen/boot/hvmloader' > >device_model = '/usr/lib/xen/bin/qemu-dm' > >sdl = 1 # use SDL for graphics > >vnc = 0 # use VNC for graphics > >vncviewer = 0 # spawn vncviewer by default > > > >if i create the domain with 'xm create WinXPPro_xendom1_local' everything > >looks good, no errors shown. > >xm list shows: > > > >Name ID Mem(MiB) VCPUs State Time(s) > >Domain-0 0 2504 2 r----- 320.7 > >WinXPPro_xendom1_local 4 512 1 -b---- 0.0 > > > >also, where can is see why it stops and how far the boot process went ? > >any hints very welcome ! > > > >regards, > >Matthias > > > > > > > > > >> Hi Matthias, > >> > >> I think the bootloader is installed at /dev/sda, which can select to boot the > >Windows XP partition right? > >> You can modify /etc/xen/xmexample.hvm to change to following > >configuration and create the VMX with it. > >> disk = [ 'phy:/dev/sda,ioemu:hda,w' ] > >> sdl=1 > >> vnc=0 > >> vncviewer=0 > >> > >> Creating Windows VMX has no difference with other unmodified Linux. > >> > >> Best Regards, > >> Yongkang (Kangkang) ?????? > >> ________________________________________ > >> From: fedora-xen-bounces at redhat.com > >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer > >> Sent: 2006???4???4??? 19:16 > >> To: fedora-xen at redhat.com > >> Subject: [Fedora-xen] configuration for windows image with VT machine > >> > >> Hi, > >> > >> i have a brand new system with VT technology (HP XW4300). > >> i am running FC5 with XEN kernel 2.6.16-1.2080_FC5xen0 on it. > >> on the harddisk (/dev/sda) there are two partitions. sda1 has a native > >windows XP system installed while sda2 is /boot and sda3 is / for the FC5 > >system. > >> > >> now i want to run the windows system under xen control using the installed > >windows system on the first partition. > >> > >> what would i need to configure to make this work ? > >> how does the config file needs to look like ? > >> is there a documentation available on how to make windows run unmodified > >under xen ? > >> > >> any hints welcome ! > >> > >> Thanks. > >> > >> > >> ! > >> > >> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > >> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > >> > >> > > > > > >______________________________________________________________ > >_ > >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From matbayer.web at web.de Wed Apr 5 15:34:08 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 05 Apr 2006 17:34:08 +0200 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <268046122@web.de> Hi Yonkang, you are right, grub is installed on /dev/sda and i can choose which OS i want to boot. i still can't boot the windows system from my first partition using this config file (any ideas what's wrong here ?). name = "WinXPPro_xendom1_local" builder = "hvm" memory = "512" disk = [ 'phy:/dev/sda,hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:63:72:e2' ] on_reboot = 'restart' on_crash = 'restart' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib/xen/bin/qemu-dm' sdl = 1 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default if i create the domain with 'xm create WinXPPro_xendom1_local' everything looks good, no errors shown. xm list shows: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2504 2 r----- 320.7 WinXPPro_xendom1_local 4 512 1 -b---- 0.0 also, where can is see why it stops and how far the boot process went ? any hints very welcome ! regards, Matthias > Hi Matthias, > > I think the bootloader is installed at /dev/sda, which can select to boot the Windows XP partition right? > You can modify /etc/xen/xmexample.hvm to change to following configuration and create the VMX with it. > disk = [ 'phy:/dev/sda,ioemu:hda,w' ] > sdl=1 > vnc=0 > vncviewer=0 > > Creating Windows VMX has no difference with other unmodified Linux. > > Best Regards, > Yongkang (Kangkang) ?????? > ________________________________________ > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer > Sent: 2006???4???4??? 19:16 > To: fedora-xen at redhat.com > Subject: [Fedora-xen] configuration for windows image with VT machine > > Hi, > > i have a brand new system with VT technology (HP XW4300). > i am running FC5 with XEN kernel 2.6.16-1.2080_FC5xen0 on it. > on the harddisk (/dev/sda) there are two partitions. sda1 has a native windows XP system installed while sda2 is /boot and sda3 is / for the FC5 system. > > now i want to run the windows system under xen control using the installed windows system on the first partition. > > what would i need to configure to make this work ? > how does the config file needs to look like ? > is there a documentation available on how to make windows run unmodified under xen ? > > any hints welcome ! > > Thanks. > > > ! > > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From James.Reuter at hp.com Wed Apr 5 21:25:20 2006 From: James.Reuter at hp.com (Reuter, Jim) Date: Wed, 5 Apr 2006 15:25:20 -0600 Subject: [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? Message-ID: <9B832BEB407A774AA0520CCFC232219709BE7DB9@CXOEXC11.AMERICAS.CPQCORP.NET> Reposted from fedora-list...I did not even know fedora-xen existed until a coworker pointed it out, it's not listed on Fedora Portal. I have not seen any answers for this on fedora-list. > ______________________________________________ > From: Reuter, Jim > Sent: Wednesday, April 05, 2006 10:59 AM > To: 'fedora-list at redhat.com' > Subject: Anyone using VT-x (vmx, hvm, ...)? > > I've installed FC5 32 and 64 bit versions on a VT-x capable Xeon > server. I can install paravirtualized guests using > /usr/sbin/xenguest-install.py per the quickstart guide with no > problems. But if I try to install a fully virtualized FC5 or Windows > XP guest using the VT-x (vmx) capability and an ISO install image, xm > shows that a guest started, but I can never connect to a console or > vnc session to see what it is doing or go through the OS install. > Even the xenguest-install.py script fails at the point of trying to > connect the console. > > The error is "xenconsole: Could not read from tty store: No such file > or directory". > > I'm at a loss to know how to proceed or debug this. Any help would be > appreciated. Is anyone even using FC5 on VT-x systems? The lists > seem to be very quiet on this topic. > > Thanks, > Jim Reuter > James.reuter at hp.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at heilpern.com Wed Apr 5 22:59:51 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Wed, 5 Apr 2006 18:59:51 -0400 (EDT) Subject: [Fedora-xen] installation problem with the guest Message-ID: <30134161.01144277992018.JavaMail.root@heilpern.com> An HTML attachment was scrubbed... URL: From matbayer.web at web.de Thu Apr 6 07:53:56 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 06 Apr 2006 09:53:56 +0200 Subject: [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? Message-ID: <268736177@web.de> Hi Jim, i am using fedora-xen and VT on an new HP XW4300 workstation and i am running fully virtualized Windows systems on it. i had the same problems as you and therefore i used a 'workaround' to get the things running: i just installed 'qemu' and installed the windows system from an ISO file under qemu and then started it under xen control later - works perfect for me here. if you need more information on what i have done exactly just let me know. there are some 'tricks' that can make your life much easier using this way of installation as the graphical output is very slow after the system comes up and you use VNC to connect to it .. i haven't tried fully virtualized linux systems so far but i am going to do this soon .... regards, Matthias *Von:* "Reuter, Jim" *Gesendet:* 05.04.06 23:26:09 *An:* *Betreff:* [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? Reposted from fedora-list I did not even know fedora-xen existed until a coworker pointed it out, it's not listed on Fedora Portal. I have not seen any answers for this on fedora-list. ______________________________________________ *From: * Reuter, Jim *Sent: * Wednesday, April 05, 2006 10:59 AM *To: * 'fedora-list at redhat.com' *Subject: * Anyone using VT-x (vmx, hvm, ...)? I've installed FC5 32 and 64 bit versions on a VT-x capable Xeon server. I can install paravirtualized guests using /usr/sbin/xenguest-install.py per the quickstart guide with no problems. But if I try to install a fully virtualized FC5 or Windows XP guest using the VT-x (vmx) capability and an ISO install image, xm shows that a guest started, but I can never connect to a console or vnc session to see what it is doing or go through the OS install. Even the xenguest-install.py script fails at the point of trying to connect the console. The error is "xenconsole: Could not read from tty store: No such file or directory". I'm at a loss to know how to proceed or debug this. Any help would be appreciated. Is anyone even using FC5 on VT-x systems? The lists seem to be very quiet on this topic. Thanks, Jim Reuter James.reuter at hp.com--Fedora-xen mailing listFedora-xen at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-xen SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] -------------- next part -------------- An HTML attachment was scrubbed... URL: From roger at gwch.net Thu Apr 6 08:07:27 2006 From: roger at gwch.net (Roger Grosswiler) Date: Thu, 6 Apr 2006 10:07:27 +0200 (CEST) Subject: [Fedora-xen] Still having Memory recommendations? Message-ID: <14648.193.223.193.103.1144310847.squirrel@www.gwch.net> Hey, is xen still needing 256 mb per DomU to install? How much ram is is using for Dom0? Thanks, Roger From yongkang.you at intel.com Thu Apr 6 08:35:16 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 6 Apr 2006 16:35:16 +0800 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A2100@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >Sent: 2006?4?6? 0:37 >To: fedora-xen at redhat.com; You, Yongkang >Subject: RE: [Fedora-xen] configuration for windows image with VT machine > > >another hint for me ? EM~. I remember I can start up a Windows XP SP2 disk image file in the FC5 IA32, which is kernel-xen0-2.6.15-1.2032_FC5.i686.rpm kernel-xenU-2.6.15-1.2032_FC5.i686.rpm xen-3.0.1-3.i386.rpm I am not sure of the problem you met. Is it SP1 or SP2? A little trouble suggestion is to get latest Xen source 9543, build/install it. I know there are a lot of bugs fixing, such as installation etc. And this version should be a good one for basic VMX. (It can start up Redhat distributions, Windows XP SP1/SP2 and finish a lot of installation.) If really want it, I can give some helps. While, I am also very eager for the FC5 great updating RPMs for Xen. The update RPMs will bring many conveniences for end users. Maybe Xen 3.0.2 will be in FC5 update soon, as it is very closing. :) > >thanks, >Matthias > > Best Regards, Yongkang (Kangkang) ?? From veillard at redhat.com Thu Apr 6 08:51:03 2006 From: veillard at redhat.com (Daniel Veillard) Date: Thu, 6 Apr 2006 04:51:03 -0400 Subject: [Fedora-xen] Still having Memory recommendations? In-Reply-To: <14648.193.223.193.103.1144310847.squirrel@www.gwch.net> References: <14648.193.223.193.103.1144310847.squirrel@www.gwch.net> Message-ID: <20060406085103.GG22325@redhat.com> On Thu, Apr 06, 2006 at 10:07:27AM +0200, Roger Grosswiler wrote: > Hey, > > is xen still needing 256 mb per DomU to install? How much ram is is using > for Dom0? It's not Xen which requires this. It's the fact that you run a full fedora system. Actually 256 is in my tests a bit low for running the installer/anaconda (it slows down installation), but once the domain image is set-up if you don't have much services running on the guest it's possible to lower the domain memory use (edit the config file in /etc/xen for this, sutdown the domain, balloon the memory used by Dom0 if needed and restart the domain, that's the simplest). Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From matbayer.web at web.de Thu Apr 6 09:03:02 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 06 Apr 2006 11:03:02 +0200 Subject: [Fedora-xen] configuration for windows image with VT machine Message-ID: <268796023@web.de> Hi again, the windows system is SP2 with latest patches. i see really strange behaviour with the grub boot entries - i have removed the DomU kernel entries and after a reboot now when i want to start the installed windows system the changed entries are active but the startup immediately crashes after the popup windows shows up - moving back the entries and starting the system under xen control doesn't reflect the changes within grub but the system tries starting again ......but fails with the old problem. looks like xend does not recognize changes of grub inside DomU without a restart ....... so .. i have no more ideas how to make this work .. windows using a 'file' instead booting from the real partition works fine. maybe upgrading fixes some of this problems, hopefully. any more help very welcome :-) regards, matthias *Von:* "You, Yongkang" *Gesendet:* 06.04.06 10:35:27 *An:* *Betreff:* RE: [Fedora-xen] configuration for windows image with VT machine >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >Sent: 2006??4??6?? 0:37 >To: fedora-xen at redhat.com; You, Yongkang >Subject: RE: [Fedora-xen] configuration for windows image with VT machine > > >another hint for me ? EM~. I remember I can start up a Windows XP SP2 disk image file in the FC5 IA32, which is kernel-xen0-2.6.15-1.2032_FC5.i686.rpm kernel-xenU-2.6.15-1.2032_FC5.i686.rpm xen-3.0.1-3.i386.rpm I am not sure of the problem you met. Is it SP1 or SP2? A little trouble suggestion is to get latest Xen source 9543, build/install it. I know there are a lot of bugs fixing, such as installation etc. And this version should be a good one for basic VMX. (It can start up Redhat distributions, Windows XP SP1/SP2 and finish a lot of installation.) If really want it, I can give some helps. While, I am also very eager for the FC5 great updating RPMs for Xen. The update RPMs will bring many conveniences for end users. Maybe Xen 3.0.2 will be in FC5 update soon, as it is very closing. :) > >thanks, >Matthias > > Best Regards, Yongkang (Kangkang) ???? SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] -------------- next part -------------- An HTML attachment was scrubbed... URL: From matbayer.web at web.de Thu Apr 6 09:25:09 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 06 Apr 2006 11:25:09 +0200 Subject: [Fedora-xen] fully virtualized FC5 installation fails Message-ID: <268817281@web.de> Hi, i am running FC5 with default Xen3.0.1-4 and kernel 2.6.16-1.2080_FC5xen0. i tried installing a fully virtualized FC5 using xenguest-install.py and a FC5 ISO dvd as source. the installation starts but then stops at: Starting guest... ['/usr/sbin/xm', 'create', '-c', 'cdrom=/nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso', 'boot=d', '/etc/xen/FC5_licht_fullvt'] Using config file "/etc/xen/FC5_licht_fullvt". Started domain FC5_licht_fullvt connection via vnc to the doamin shows the last message: Mount-cash hash table entries :512 (before SElinux was initialized...) xend.log shows: [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:177) XendDomainInfo.create(['vm', ['name', 'FC5_licht_fullvt'], ['memory', '512'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', '1'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['vcpus', '1'], ['cdrom', '/nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso'], ['boot', 'd'], ['serial', 'pty'], ['vnc', '1'], ['display', ':0.0'], ['xauthority', '/root/.xauthWrAenw']]], ['device', ['vbd', ['uname', 'file:/images/FC5_licht_fullvt.img'], ['dev', 'ioemu:hda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:1d:13:7f'], ['type', 'ioemu']]]]) [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:283) parseConfig: config is ['vm', ['name', 'FC5_licht_fullvt'], ['memory', '512'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', '1'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['vcpus', '1'], ['cdrom', '/nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso'], ['boot', 'd'], ['serial', 'pty'], ['vnc', '1'], ['display', ':0.0'], ['xauthority', '/root/.xauthWrAenw']]], ['device', ['vbd', ['uname', 'file:/images/FC5_licht_fullvt.img'], ['dev', 'ioemu:hda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:1d:13:7f'], ['type', 'ioemu']]]] [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:379) parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash': 'restart', 'on_reboot': 'restart', 'image': ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['vcpus', '1'], ['cdrom', '/nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso'], ['boot', 'd'], ['serial', 'pty'], ['vnc', '1'], ['display', ':0.0'], ['xauthority', '/root/.xauthWrAenw']], 'on_poweroff': None, 'cpus': None, 'name': 'FC5_licht_fullvt', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['uname', 'file:/images/FC5_licht_fullvt.img'], ['dev', 'ioemu:hda'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:1d:13:7f'], ['type', 'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:1142) XendDomainInfo.construct: None 0 [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:1174) XendDomainInfo.initDomain: 8 1.0 [2006-04-06 11:16:55 xend] DEBUG (image:266) args: cdrom, val: /nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso [2006-04-06 11:16:55 xend] DEBUG (image:266) args: boot, val: d [2006-04-06 11:16:55 xend] DEBUG (image:266) args: fda, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: fdb, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: nic-ne2000, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: enable-audio, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: localtime, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: serial, val: pty [2006-04-06 11:16:55 xend] DEBUG (image:266) args: std-vga, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: isa, val: None [2006-04-06 11:16:55 xend] DEBUG (image:266) args: vcpus, val: 1 [2006-04-06 11:16:55 xend] DEBUG (balloon:84) Balloon: free 654; need 518; done. [2006-04-06 11:16:55 xend] INFO (image:135) buildDomain os=hvm dom=8 vcpus=1 [2006-04-06 11:16:55 xend] DEBUG (image:224) dom = 8 [2006-04-06 11:16:55 xend] DEBUG (image:225) image = /usr/lib/xen/boot/hvmloader [2006-04-06 11:16:55 xend] DEBUG (image:226) store_evtchn = 1 [2006-04-06 11:16:55 xend] DEBUG (image:227) memsize = 512 [2006-04-06 11:16:55 xend] DEBUG (image:228) vcpus = 1 [2006-04-06 11:16:55 xend] DEBUG (image:229) pae = 0 [2006-04-06 11:16:55 xend] DEBUG (image:230) acpi = 0 [2006-04-06 11:16:55 xend] DEBUG (image:231) apic = 0 [2006-04-06 11:16:55 xend] DEBUG (image:392) hvm shutdown watch registered [2006-04-06 11:16:55 xend] INFO (image:351) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '8', '-m', '512', '-cdrom', '/nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso', '-boot', 'd', '-serial', 'pty', '-vcpus', '1', '-domain-name', 'FC5_licht_fullvt', '-hda', '/images/FC5_licht_fullvt.img', '-macaddr', '00:16:3e:1d:13:7f', '-bridge', 'xenbr0', '-nics', '1', '-vnc', '-k', 'en-us', '-vncport', '5908'] [2006-04-06 11:16:55 xend] INFO (image:353) device model pid: 3287 [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details: {'ssidref': '0', 'uuid': '8a1bee18-c8be-c801-18ce-8954d8e1d27b', 'on_reboot': 'restart', 'start_time': '1144315015.72', 'on_poweroff': 'destroy', 'name': 'FC5_licht_fullvt', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 'restart', 'image': '(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (vcpus 1) (cdrom /nfsmount/ISO/Fedora/FC5/FC-5-i386-DVD.iso) (boot d) (serial pty) (vnc 1) (display :0.0) (xauthority /root/.xauthWrAenw))', 'maxmem': '512'} [2006-04-06 11:16:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: {'console/port': '2', 'name': 'FC5_licht_fullvt', 'console/limit': '1048576', 'vm': '/vm/8a1bee18-c8be-c801-18ce-8954d8e1d27b', 'domid': '8', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '740585', 'store/port': '1'} [2006-04-06 11:16:55 xend] DEBUG (image:415) hvm_shutdown fired, shutdown reason=None [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices vif. [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices usb. [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices vbd. [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices pci. [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices ioports. [2006-04-06 11:16:56 xend] DEBUG (DevController:132) Waiting for devices vtpm. [2006-04-06 11:16:56 xend] INFO (XendDomain:360) Domain FC5_licht_fullvt (8) unpaused. as always - any hep very much welcome :-) regards, Matthias _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From mark at heilpern.com Thu Apr 6 20:03:01 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Thu, 6 Apr 2006 16:03:01 -0400 (EDT) Subject: [Fedora-xen] installation problem with the guest In-Reply-To: <30134161.01144277992018.JavaMail.root@heilpern.com> Message-ID: <1244800.61144353781218.JavaMail.root@heilpern.com> Sorry for the re-post. It's been pointed out to me that my original email was in HTML mode, where many people's readers will not display properly. Repeated in plain text mode: Ok, I've got my Domain0 networking assignments fixed I think. (I went with the HWADDR= approach, which is 2 for 2 so far). I'm not having significant luck though with my guest installation, following the instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC5. When I run xenguest-install.py it boots into the FC5 install program. Once that's running it asks language, country, but it's unable to find the files needed for the actual FC5 install though. The connection choices are nfs, http, and ftp, and I've tried nfs and http before deciding the problem is likely to be that networking isn't crossing the bridge. Is there any way to check this? I'm arriving at this conclusion because I cannot see any log indications of the connection attempts (using a static IP of 192.168.2.250 for the guest; my Domain0's eth0 is 192.168.2.1)... I also tried setting the guest to use dhcp to obtain an address during the install and it fails to get an address. What occurs to me: how would Xen know which address to bind a bridge to? Perhaps there is a step I need to do? I know nothing yet about setting up a bridge. While the installer is running, the output of my ifconfig is as shown below. Eth0 and eth1 are the real interfaces; I find it interesting that all interfaces including xenbr0 show some activity. Thanks again for any thoughts on this... Mark eth0 Link encap:Ethernet HWaddr 00:10:DC:F2:70:17 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:dcff:fef2:7017/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3024 errors:0 dropped:0 overruns:0 frame:0 TX packets:3480 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:409347 (399.7 KiB) TX bytes:816956 (797.8 KiB) Interrupt:17 Base address:0x4000 eth1 Link encap:Ethernet HWaddr 00:90:47:03:B8:63 inet addr:myinternetip Bcast:myinternetbcast Mask:255.255.255.252 inet6 addr: fe80::290:47ff:fe03:b863/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:699 errors:0 dropped:0 overruns:0 frame:0 TX packets:601 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:165595 (161.7 KiB) TX bytes:170365 (166.3 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4425 errors:0 dropped:0 overruns:0 frame:0 TX packets:4425 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13915749 (13.2 MiB) TX bytes:13915749 (13.2 MiB) peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:674 errors:0 dropped:0 overruns:0 frame:0 TX packets:718 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:165738 (161.8 KiB) TX bytes:185932 (181.5 KiB) Interrupt:18 Base address:0x6000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:601 errors:0 dropped:0 overruns:0 frame:0 TX packets:702 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:170365 (166.3 KiB) TX bytes:165833 (161.9 KiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:37 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2052 (2.0 KiB) TX bytes:730 (730.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:129 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12722 (12.4 KiB) TX bytes:468 (468.0 b) From philipp.jaggi at snct.lu Thu Apr 6 07:41:12 2006 From: philipp.jaggi at snct.lu (Philipp =?ISO-8859-2?Q?J=E4ggi?=) Date: Thu, 6 Apr 2006 09:41:12 +0200 Subject: [Fedora-xen] Fedora Core 5 Xen xenconfig migration from FC4 Message-ID: Hello out there Till last week I hab my testserver running fine with Fedora Core 4 and xen 3. At monday I had the idea to use the new Fedora Core 5 with his new xen implementation. It's nice to create a guest with their new xenguest-install.py script, but I need my old xen domU configurations. Especially I have to run a Fedora Core 4 Guest, because Oracle 10g is not running on FC5 (glibc problem). But when I try to use my old configurations, I get an error message while booting: Error: Error creating domain: Kernel image does not exist: /boot/vmlinuz-2.6.16-1.2080_FC5XenU So, the file exists, that's not the problem. I tried also to use the xen-sysm.... variant. But nothing worked. I used also the ramdisk option. My domU config file looks like: kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" memory = 256 name = "sweb01" extra = "selinux=0 3" disk = ['phy:VolGroup00/root.sweb01,sda1,w' ,'phy:VolGroup00/log.sweb01,sda3,w' ,'phy:VolGroup00/swap.sweb01,sda2,w' ] root = "/dev/sda1" ### N E T W O R K vif = [ 'bridge=xenbr-pub' , 'bridge=xenbr-int' ] Hope sombody has a migration guide Xen FC4 to FC5 for me.:-) By the way, I don't understand how to install now a FC4 in this new FC5 environment. Is it possible to do this with the xenguest-install script??? bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi at snct.lu -------------- next part -------------- An HTML attachment was scrubbed... URL: From matbayer.web at web.de Fri Apr 7 07:50:19 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Fri, 07 Apr 2006 09:50:19 +0200 Subject: [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? Message-ID: <269757232@web.de> Hi JIm, i have installed windows also from ISO to a virtual disk file as well as tried to boot an already installed windows from a partition. running the virtual disk file worked fine, still trying to boot the windows system from my first partition .... my actual and working config file looks like this: name = "WinXPPro_gabel" builder = "hvm" memory = "512" disk = [ 'file:/images/WinXP_gabel.img,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:63:73:f2' ] on_reboot = 'restart' on_crash = 'restart' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib/xen/bin/qemu-dm' sdl = 0 # use SDL for graphics vnc = 1 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 0 # don't use graphics serial='pty' # enable serial console to your second question: i am running latest updates from official fedora site, means kernel-xenU-2.6.16-1.2080_FC5 xen-3.0.1-4 kernel-xen0-2.6.16-1.2080_FC5 hope that helps, let me know if you need anything else and let me know if yopu manage to make it work to boot windows from another disk .... regards, Matthias > Thanks. My system is a Proliant server, which has pluggable disks, so I probably don't even need to use qemu. I can just pop out the FC5 disks and pop in a windows disk and do a real install. > > > > I saw the thread with your line of questions, it looks like you installed Windows to a disk partition, not to a virtual disk file. I was trying to get the VT-x virtual machine to do the install from an ISO to a virtual file, but could not even connect to a console. > > > > I'll do some installs to removable disks and play around with that to see what happens. > > > > Could you send me your latest working xen conf file for the Windows VM so I can check that against mine? I know you posted a copy of one in the list, but that was before you got things working, so maybe it is no longer current. > > > > thanks, > > Jim > > > ----------------------------------------------------------------- > From: Matthias Bayer [mailto:matbayer.web at web.de] > Sent: Thursday, April 06, 2006 1:54 AM > To: Reuter, Jim; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? > > > > > > Hi Jim, > > > i am using fedora-xen and VT on an new HP XW4300 workstation and i am running fully virtualized Windows systems on it. > > > i had the same problems as you and therefore i used a 'workaround' to get the things running: > > > i just installed 'qemu' and installed the windows system from an ISO file under qemu and then started it under xen control later - works perfect for me here. > > > if you need more information on what i have done exactly just let me know. there are some 'tricks' that can make your life much easier using this way of installation as the graphical output is very slow after the system comes up and you use VNC to connect to it .. > > > i haven't tried fully virtualized linux systems so far but i am going to do this soon .... > > > > > > regards, > > > Matthias > > > > > > > > > > > > > > > > ----------------------------------------------------------------- > Von: "Reuter, Jim" > Gesendet: 05.04.06 23:26:09 > An: > Betreff: [Fedora-xen] Anyone using VT-x (vmx, hvm, ...)? > > > > Reposted from fedora-list I did not even know fedora-xen existed until a coworker pointed it out, it's not listed on Fedora Portal. > > > I have not seen any answers for this on fedora-list. > > > ______________________________________________ > From: Reuter, Jim > Sent: Wednesday, April 05, 2006 10:59 AM > To: 'fedora-list at redhat.com' > Subject: Anyone using VT-x (vmx, hvm, ...)? > > > I've installed FC5 32 and 64 bit versions on a VT-x capable Xeon server. I can install paravirtualized guests using /usr/sbin/xenguest-install.py per the quickstart guide with no problems. But if I try to install a fully virtualized FC5 or Windows XP guest using the VT-x (vmx) capability and an ISO install image, xm shows that a guest started, but I can never connect to a console or vnc session to see what it is doing or go through the OS install. Even the xenguest-install.py script fails at the point of trying to connect the console. > > > The error is "xenconsole: Could not read from tty store: No such file or directory". > > > I'm at a loss to know how to proceed or debug this. Any help would be appreciated. Is anyone even using FC5 on VT-x systems? The lists seem to be very quiet on this topic. > > > Thanks, > Jim Reuter > James.reuter at hp.com > > ----------------------------------------------------------------- > --Fedora-xen mailing listFedora-xen at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From thingsmith at comcast.net Fri Apr 7 17:02:45 2006 From: thingsmith at comcast.net (Harry Smith) Date: Fri, 07 Apr 2006 10:02:45 -0700 Subject: [Fedora-xen] Stuck on Xen Guest Install at the Anaconda point. Message-ID: <6.2.5.6.2.20060407094028.01e44790@comcast.net> I am stuck on how to do the anaconda definition for the location of core tree (btw what is a core tree anyway). I have tried both NFS and FTP using local assets but I can not seem to make a location that is compliant with the anaconda format. The other part of the problem is that I need to set up Xen and FC 5 on some machine prohibited from Internet access. 1. Since I have a DVD version of FC5, I tried to NFS export the mounted DVD. This started the install but seem to have problems with finishing something about not being able to find start2. 2. I have a NAS which is also an ftp server however the same rules blocking access to the Internet also requires I have a user name password for the FTP server. I copied everything on the DVD to a directory on the ftp server. I am having two problems with FTP. 1. I can not figure out how to pass the user name and password. 2. I am getting an undefined URL. (ftp://192.168.1.104/linux_view/OS_x86). However this can be accessed from dom0 and it looks like it is trying to do some type of authentication. Any help or pointers to understand would be appreciated. Harry From raul.saura at gmail.com Fri Apr 7 18:14:08 2006 From: raul.saura at gmail.com (Raul Saura) Date: Fri, 7 Apr 2006 20:14:08 +0200 Subject: [Fedora-xen] Network problem during FC5 XEN Guest install Message-ID: Hello, I'm trying to create a xen-guest install using xenguest-install.py script, following the indications from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5. I've had to shrink mi xen0 domain to 128MB in order to allow guest to start install, otherwise I get the "The privileged domain did not balloon!" error-message. I've exported the FC5 DVD through NFS from the xen0 domain itself hoping it will be visible from the guest during the install process. Now I'm in the first stage of the anaconda Installer and DHCP IP learning does not seems to work, in fact no network seems to be available from the guest, because when I manually configure an IP, the guest can not see the NFS export either... I've been tcpduming for a while, and I can not see any traffic from/to the guest. But in fact I don't even known if i should be seeing any traffic from the xen0 eth0 interface, should I? Any help will be welcomed. Thanks a lot. Raul. -------------- next part -------------- An HTML attachment was scrubbed... URL: From raul.saura at gmail.com Fri Apr 7 18:33:25 2006 From: raul.saura at gmail.com (Raul Saura) Date: Fri, 7 Apr 2006 20:33:25 +0200 Subject: [Fedora-xen] Network problem during FC5 XEN Guest install (more info) Message-ID: Hi, again. I've forgoted to note that I've had to disable SELinux in order to get xend daemon running. Is this normal? thank again. Ra?l. ---------- Forwarded message ---------- From: Raul Saura Date: Apr 7, 2006 8:14 PM Subject: Network problem during FC5 XEN Guest install To: fedora-xen at redhat.com Hello, I'm trying to create a xen-guest install using xenguest-install.py script, following the indications from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 . I've had to shrink mi xen0 domain to 128MB in order to allow guest to start install, otherwise I get the "The privileged domain did not balloon!" error-message. I've exported the FC5 DVD through NFS from the xen0 domain itself hoping it will be visible from the guest during the install process. Now I'm in the first stage of the anaconda Installer and DHCP IP learning does not seems to work, in fact no network seems to be available from the guest, because when I manually configure an IP, the guest can not see the NFS export either... I've been tcpduming for a while, and I can not see any traffic from/to the guest. But in fact I don't even known if i should be seeing any traffic from the xen0 eth0 interface, should I? Any help will be welcomed. Thanks a lot. Raul. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Fri Apr 7 18:37:33 2006 From: bench at silentmedia.com (Ben) Date: Fri, 7 Apr 2006 11:37:33 -0700 Subject: [Fedora-xen] Stuck on Xen Guest Install at the Anaconda point. In-Reply-To: <6.2.5.6.2.20060407094028.01e44790@comcast.net> References: <6.2.5.6.2.20060407094028.01e44790@comcast.net> Message-ID: The "core tree" is the directory tree for the core of Fedora. In other words, it's what you see if you look here: http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/ On Apr 7, 2006, at 10:02 AM, Harry Smith wrote: > > I am stuck on how to do the anaconda definition for the location of > core tree (btw what is a core tree anyway). > > I have tried both NFS and FTP using local assets but I can not seem > to make a location that is compliant with the anaconda format. > The other part of the problem is that I need to set up Xen and FC 5 > on some machine prohibited from Internet access. > > 1. Since I have a DVD version of FC5, I tried to NFS export the > mounted DVD. This started the install but seem to have problems > with finishing something about not being able to find start2. > > 2. I have a NAS which is also an ftp server however the same rules > blocking access to the Internet also requires I have a user name > password for the FTP server. I copied everything on the DVD to a > directory on the ftp server. I am having two problems with FTP. > > 1. I can not figure out how to pass the user name and password. > 2. I am getting an undefined URL. (ftp://192.168.1.104/linux_view/ > OS_x86). However this can be accessed from dom0 and it looks > like it is trying to do some type of authentication. > > > Any help or pointers to understand would be appreciated. > > Harry > > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From mark at heilpern.com Fri Apr 7 19:14:43 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Fri, 7 Apr 2006 15:14:43 -0400 (EDT) Subject: [Fedora-xen] Network problem during FC5 XEN Guest install In-Reply-To: Message-ID: <30914645.81144437283435.JavaMail.root@heilpern.com> For what it's worth I'm having the exact same problem you are... no solution for me yet. In my case my dom0 has two physical ethernet interfaces and a Firestarter-managed firewall letting my local traffic (on eth0) NAT out to the internet (eth1), blocking most ports on eth1 from the outside world. I haven't explored enough to determine if either multiple eth's or the firewall are contributing towards my problem. I've failed both with DHCP in the guest as well as with a static IP for it. The IP I've used statically is 192.168.2.250 (where my eth0 device is 192.168.2.1). Is there anywhere I can download a guest disk image pre-installed? ----- Original Message -----From: Raul Saura To: Cc: Date: Friday, April 7 2006 02:20 PMSubject: [Fedora-xen] Network problem during FC5 XEN Guest installHello, I'm trying to create a xen-guest install using xenguest-install.py script, following the indications from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 . I've had to shrink mi xen0 domain to 128MB in order to allow guest to start install, otherwise I get the "The privileged domain did not balloon!" error-message. I've exported the FC5 DVD through NFS from the xen0 domain itself hoping it will be visible from the guest during the install process. Now I'm in the first stage of the anaconda Installer and DHCP IP learning does not seems to work, in fact no network seems to be available from the guest, because when I manually configure an IP, the guest can not see the NFS export either... I've been tcpduming for a while, and I can not see any traffic from/to the guest. But in fact I don't even known if i should be seeing any traffic from the xen0 eth0 interface, should I? Any help will be welcomed. Thanks a lot. Raul. -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From raul.saura at gmail.com Fri Apr 7 23:08:11 2006 From: raul.saura at gmail.com (Raul Saura) Date: Sat, 8 Apr 2006 01:08:11 +0200 Subject: [Fedora-xen] Network problem during FC5 XEN Guest install (more on this...) Message-ID: Sorry guys, but I'm back with this... I've noticed that once the xen-guest is running a new ethenet interface is waked UP and it's binded to the internal switch: [root at localhost ~]# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif1.0 You can even see the MAC of the virtual interface of the guest: [root at localhost ~]# brctl showmacs xenbr0 port no mac addr is local? ageing timer 1 00:16:3e:71:08:b4 no 6.22 1 fe:ff:ff:ff:ff:ff yes 0.00 But this setup is missing a second interface to bridge with, isn't it? In fact DHCP request are not being honored with this setup so I've tried to manually add the physical ethernet interface of xen0: [root at localhost ~]# brctl addif xenbr0 eth0 Having done so, the bridge can actually see both segments, now [root at localhost ~]# brctl showmacs xenbr0 port no mac addr is local? ageing timer 2 00:0e:a6:ce:7c:0e yes 0.00 2 00:10:db:4d:ab:02 no 0.63 1 00:16:3e:71:08:b4 no 42.57 1 fe:ff:ff:ff:ff:ff yes 0.00 And even ports number make sense: [root at localhost ~]# brctl showstp xenbr0 xenbr0 bridge id 8000.000ea6ce7c0e designated root 8000.000ea6ce7c0e root port 0 path cost 0 max age 20.00 bridge max age 20.00 hello time 2.00 bridge hello time 2.00 forward delay 0.00 bridge forward delay 0.00 ageing time 300.01 hello timer 1.72 tcn timer 0.00 topology change timer 4.02 gc timer 0.06 flags TOPOLOGY_CHANGE TOPOLOGY_CHANGE_DETECTED eth0 (2) port id 8002 state forwarding designated root 8000.000ea6ce7c0e path cost 19 designated bridge 8000.000ea6ce7c0e message age timer 0.00 designated port 8002 forward delay timer 0.00 designated cost 0 hold timer 0.72 flags vif1.0 (1) port id 8001 state forwarding designated root 8000.000ea6ce7c0e path cost 100 designated bridge 8000.000ea6ce7c0e message age timer 0.00 designated port 8001 forward delay timer 0.00 designated cost 0 hold timer 0.72 flags And in fact, now DHCP assignement worked, and the guest got his IP during the install process, we can see my Netscreen DHCP server leases report: 172.20.76.11 00163e7108b4 23 hour 57 minute So at least layer2 connectivity is working with the outside world, but the guest can not yet mount the NFS share, nor xen0 can ping the xen-guest 172.20.76.11 newly assigned IP address. Nor can other external boxes ping the xen-guest, by the way... IPTABLES is disabled, and its modules unloaded, and SELinux is also disabled... Isn't this somewhat wierd? Thanks... On 4/7/06, Raul Saura wrote: > > Hi, again. > > I've forgoted to note that I've had to disable SELinux in order to get > xend daemon running. > > Is this normal? > > thank again. > > Ra?l. > > ---------- Forwarded message ---------- > From: Raul Saura > Date: Apr 7, 2006 8:14 PM > Subject: Network problem during FC5 XEN Guest install > To: fedora-xen at redhat.com > > Hello, > > I'm trying to create a xen-guest install using xenguest-install.pyscript, following the indications from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 > . > I've had to shrink mi xen0 domain to 128MB in order to allow guest to > start install, otherwise I get the "The privileged domain did not balloon!" > error-message. > I've exported the FC5 DVD through NFS from the xen0 domain itself hoping > it will be visible from the guest during the install process. > > Now I'm in the first stage of the anaconda Installer and DHCP IP learning > does not seems to work, in fact no network seems to be available from the > guest, because when I manually configure an IP, the guest can not see the > NFS export either... > > I've been tcpduming for a while, and I can not see any traffic from/to the > guest. But in fact I don't even known if i should be seeing any traffic from > the xen0 eth0 interface, should I? > > Any help will be welcomed. > > Thanks a lot. > > Raul. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmorgan at gmi-mr.com Fri Apr 7 23:14:56 2006 From: dmorgan at gmi-mr.com (Duncan Morgan) Date: Fri, 7 Apr 2006 16:14:56 -0700 Subject: [Fedora-xen] eth0 not coming up on domU Message-ID: <00bd01c65a99$1598a820$3c09080a@dmmobile> Hello, I have FC5 with xen-3.0.1-4 and kernels kernel-xen0-2.6.16-1.2080_FC5 kernel-xenU-2.6.16-1.2080_FC5 and I have successfully (I hope) built a white box linux 3.2 guest which uses the domU kernel. The guest boots properly and shows eth0 as having come up yet it is not up and won't come up. I've tried assigning static IPs and using DHCP (DHCP on the network works well). Has anybody seen this before? Is there a change that the netfront driver is either not loading or not enabled? Thanks in advance, Duncan From lists at benrey.is-a-geek.net Sat Apr 8 07:09:30 2006 From: lists at benrey.is-a-geek.net (Jed Reynolds) Date: Sat, 08 Apr 2006 00:09:30 -0700 Subject: [Fedora-xen] anaconda install -- getting networking right Message-ID: <443761AA.90503@benrey.is-a-geek.net> I'm trying to do a local install, I've copied my 4 b5 cds to /var/www/html/rpmcache and turned indexing on in apache. For reference, my laptop's ip address is 192.168.45.3. SELinux disabled; service iptables stop; Stuff I didn't see in the quickstart that slowed me down included: - a pretty quick example of how anaconda expects the install directories. Having used User Mode Linux and those various yum-based install hacks, I started off just by copying all the rpms into one directory, and realized that it actually wanted all the files on the cds. - should I expect dhcp from anaconda to work OOTB? Not so much. Is there a host configuration I need? Does host need to run dhcpd? Am I running as if the host is my gateway? If I'm bridged, I wouldn't think so, but if I can't get a dhcp lease off the network, what's blocking me? - an example of sane network numbers to use. Comming from a UML background, I'm used to setting up a 10-network behind a tun device. Now I have a bridged network connection, so I'm guessing I can just use the next logical lan address, 192.168.45.202. However, I can't tell why my anaconda can't contact 192.168.45.201. It's not worth specifying 127.0.0.1 from anaconda. Was it an error to specify http://localhost/rpmcache/ on the command line python script? Tried again with http://192.168.45.201/rpmcache/disk1/, no connection to httpd server. Is this install process not intended to interact with dom0 port 80? I'm sure there's prolly something simple that I've skipped, but I can't see it. Is there a way to diagnose the network connection? I admit to not having scrutinized the list closely, but I don't see any posts in the archives discussing my issue. I've gotten so much further this time than with FC4+Xen, it's not crashing and freezing my machine, I can't be far away. Help appreciated. TIA. Jed From lists at benrey.is-a-geek.net Sat Apr 8 07:26:21 2006 From: lists at benrey.is-a-geek.net (Jed Reynolds) Date: Sat, 08 Apr 2006 00:26:21 -0700 Subject: [Fedora-xen] extending size of image Message-ID: <4437659D.60006@benrey.is-a-geek.net> John writes: > So maybe this should be corrected in that web page. > I have a question: > Can the size of a file which was created thus > (dd if=/dev/zero of=fedora.img bs=1M count=1 seek=1024) > be changed ***without*** causing a damage to its contents? > In case there is such a way, how can it be done ? > Regards, > John When managing UML images, I typically create a new image of the same size and then rsync across them. This is not the most efficient, but it is the most reliable. I've tried changing the seek parameter of an image using dd for an image, but I've found that resizing filesystem often fails or does not take effect. You could try changing the seek of the image and then running resize2fs against it, but I'd bet you $1 you'd lose that data. Safer to try something like this: dd if=/dev/zero of=additional.img ... cat fedora.img additional.img > new.img resize2fs new.img I'm sure there's other ways. I've seen this discussed on the user-mode-linux.org site. Jed From lists at benrey.is-a-geek.net Sat Apr 8 07:30:23 2006 From: lists at benrey.is-a-geek.net (Jed Reynolds) Date: Sat, 08 Apr 2006 00:30:23 -0700 Subject: [Fedora-xen] re: anaconda install -- getting networking right Message-ID: <4437668F.6050504@benrey.is-a-geek.net> Ah--I had not looked at April archives (but March, earlier...) when composing previous message. I suspect I need to look into debugging the bridging...but not tonight. From denis.forveille at gmail.com Sat Apr 8 01:09:33 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Fri, 07 Apr 2006 21:09:33 -0400 Subject: [Fedora-xen] Gnome desktop in domU? (aka xorg and startx problems in domU) Message-ID: <44370D4D.5070106@gmail.com> An HTML attachment was scrubbed... URL: From raul.saura at gmail.com Sat Apr 8 16:23:47 2006 From: raul.saura at gmail.com (Raul Saura) Date: Sat, 8 Apr 2006 18:23:47 +0200 Subject: [Fedora-xen] Fwd: Network problem during FC5 XEN Guest install (the last one...) Message-ID: Sorry for the mail-flood but I finally got It working and I think someone else could find this useful. The root of the problem was that no peth0 interface was created on Dom0, after reading xensources wiki and doing "brctl show" made it clear. I still dont't know why this was happening but I think It was somehow related with SELinux or netplugd. I reinstalled FC5 without SELinux nor iptables, and xenguest-install.py just worked as expected, and the DomU guest got DHCP and reached the NFS mount-point exported in the Dom0 Itsef. Maybe some smart developers should take look at this. regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From raul.saura at gmail.com Sat Apr 8 18:16:00 2006 From: raul.saura at gmail.com (Raul Saura) Date: Sat, 8 Apr 2006 20:16:00 +0200 Subject: [Fedora-xen] Gnome desktop in domU? (aka xorg and startx problems in domU) Message-ID: Denis, You can not run X on a DomU as the guest has no video hardware available, but you can do the following: run "Xvnc :0" on DomU, this will start an X server that uses a pseudo-frame buffer as video-hardware and serves that framebuffer via vnc protocol. now run "gnome-session" on DomU to start the whole gnome desktop infraestructure on the guest OS (as gdm will do) Now, from dom0 that is the only one with a physical screen attached at, launch vncviewer and connect to domU-ip-address:0, this will show the remote virtual desktop. hope this helps. Raul. ---------- Forwarded message ---------- From: Denis Forveille To: fedora-xen at redhat.com Date: Fri, 07 Apr 2006 21:09:33 -0400 Subject: [Fedora-xen] Gnome desktop in domU? (aka xorg and startx problems in domU) I'm experimenting with xen on FC5 (as domU and dom0). The idea is to have a machine running dom0 with 4 guests, one of the guest would be my workstation/desktop (with gnome running), the others guests would be application/file/utilities servers. I would like to perform something like: - logon to the domU via ssh, from dom0 for example (I also have tried it with "xm console domU" from dom0, the result is the same) - run "startx" : that should bring the standard logon screen - after login, use the gnome desktop as from a standard standalone workstation But this does not work: startx does not start (first because the xorg.confis not created. I've tried to run "X -configuration" to create xorg.conf, but the command fails also to create the xorg.conf file) BTW, on dom0 "startx" and the gnome desktop run perfectly Q: - Is it possible to configure X and run "startx" in a domU (I've read somewhere on the net that this is not possible...). If so how to do it? - What is the best way to get a full gnome desktop workstation that would run in domU like a standalone workstation? I've tried the "vnc" solution, it works great but have limitations (at least for me). and would greatly prefer what I described previsoulsy: (I don't know how to get the logon screen with vnc, the screen resolution can not be easily choosen/changed, the desktop to be somewhat "slower" than the "local" desktop) Thanks in advance for any advice or pointer. (I'm not really a newbee with linux, but I'm far from an expert...) -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From tedkaz at optonline.net Sat Apr 8 21:55:33 2006 From: tedkaz at optonline.net (Ted Kaczmarek) Date: Sat, 08 Apr 2006 17:55:33 -0400 Subject: [Fedora-xen] Tracebacks Message-ID: <3FDD18ED-AFDE-4358-856B-F146F8F99576@optonline.net> When try to use either sda1/sda2 sdb1/sdb2 root/swap combo I get tracebacks when launching domu. netfront: Initialising virtual ethernet driver. Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can't get major 8 with name sd NET: Registered protocol family 2 Unable to handle kernel NULL pointer dereference at virtual address 00000104 printing eip: c0222268 *pde = ma 00000000 pa 55555000 Oops: 0002 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010086 (2.6.12.6-xenU) EIP is at blk_start_queue+0x8/0x60 eax: 00000000 ebx: 00000000 ecx: fbf8c000 edx: 00000000 esi: cbc24aa0 edi: c1278000 ebp: c1279f9c esp: c1279f30 ds: 007b es: 007b ss: 0069 Process xenwatch (pid: 7, threadinfo=c1278000 task=c1226560) Stack: 00000004 cbc08000 c023507e 00000000 cbc08000 c0234f98 cbc08000 00000000 00000004 00000000 00000200 cbc08000 c02c50a0 c1279f78 c02ce518 c02c3a9f c1279f7c 00000000 00000000 00000200 00b00000 c02333e0 c02327a7 cbc08000 Call Trace: [] kick_pending_request_queues+0x1e/0x40 [] connect+0xe8/0x130 [] otherend_changed+0x0/0xa0 [] xenwatch_thread+0x87/0x140 [] autoremove_wake_function+0x0/0x60 [] xenwatch_thread+0x0/0x140 [] kthread+0xc7/0xd0 [] kthread+0x0/0xd0 [] kernel_thread_helper+0x5/0x18 Code: 00 00 00 8b 44 24 04 8b 48 60 ff e1 8d b4 26 00 00 00 00 81 44 24 04 a0 00 00 00 e9 d3 25 00 00 8d 76 00 53 83 ec 04 8b 5c 24 0c 0f ba b3 04 01 00 00 02 f0 0f ba ab 04 01 00 00 06 19 c0 85 <6>IP: routing cache hash table of 2048 buckets, 16Kbytes I switched to using hda1/hda2 combo and the domU came up. This may be particular to my mobo setup, have seen this type of problem on and off since testing the hg stuff before 3.0 was released. disk = [ 'phy:VolGroup01/debian,hda1,w' , 'phy:VolGroup01/ debswap,hda2,w'] The part that really messes with me is the domU is a debian image from jailtime.org and its fstab is dev/sdd1 / ext3 errors=remount-ro 0 1 /dev/sdd2 none swap sw 0 0 proc /proc proc defaults 0 0 I am a tad out of the loop, but from what I recall in the past the fstab had to match what was provided in the domU's config. kernel-xenU-2.6.16-1.2080_FC5 kernel-xen0-2.6.16-1.2080_FC5 This also was a yum upgrade. Should I bugzilla this or is the target still moving :-) Regards, Ted From henning_sprang at gmx.de Sat Apr 8 22:50:42 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Sun, 09 Apr 2006 00:50:42 +0200 Subject: [Fedora-xen] problems with using xen-get.org images in fc5 Message-ID: <44383E42.5010705@gmx.de> Hi, apart from the FC5 xen install script, I just tried to use the fedory 5 Image from xen-get.org on a fedora5 host system. xend is started (the fc5 install script which takes so long runs at the same time). I adjusted the locations of my disk files from the template config that came with the cen-get image to match my kernel and disk image file locations. When trying to start the vm, I get the error: "Error: Error creating domain: Kernel image does not exist: /boot/vmlinuz-2.6.16-1.2080_FC5xenU" But the file is definitely at exactly this location - I just asked a colleague for help but he also couldN#t see any error. I saw that the xen config file generated by the fedora5 install script for fc5 domU (/usr/sbin/xenguest-install.py) seems to create a very different looking config file than the ones I ever saw in any howto or documentation, so I suspect fc5 added some patches to the xen start scripts and I must make my config file "somehow" else, but I don't see how. Is it impossible to use a "standard" xen config file in fc5 with the fc5 provided xen packages? Henning From mark at heilpern.com Sat Apr 8 23:05:03 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Sat, 8 Apr 2006 19:05:03 -0400 (EDT) Subject: [Fedora-xen] Network problem during FC5 XEN Guest install In-Reply-To: <30914645.81144437283435.JavaMail.root@heilpern.com> Message-ID: <27423221.01144537504266.JavaMail.root@heilpern.com> After seeing what others with similar problems have posted, I've learned that my problem seems to be with Xen's pethX creation procedure... but I'm not sure how to convince Xen to do things just a little differently. As a recap, my system has two ethernet devices: My lan: eth0, 192.168.2.X The Internet: eth1 When I reboot and Xen has created its various interfaces, I get peth1 as a part of my xenbr0 device. This is a problem though since I need my guest machines to be tied to the lan, not the internet -- but there is no peth0 device to service this. I've tried swapping which card is which eth through mac assignment but this just caused a peth0 to be created (mapping again to my internet ethX device) and no peth1. I also tried swapping which device gets the lan address vs. my external address, and the pethX device being created is consistantly finding my internet device. How can I change the way pethX is created? ------------------------- Original Message: From: Mark A Heilpern To: fedora-xen at redhat.com Date: Friday, April 7 2006 03:14 PM Subject: Re: [Fedora-xen] Network problem during FC5 XEN Guest install For what it's worth I'm having the exact same problem you are... no solution for me yet. In my case my dom0 has two physical ethernet interfaces and a Firestarter-managed firewall letting my local traffic (on eth0) NAT out to the internet (eth1), blocking most ports on eth1 from the outside world. I haven't explored enough to determine if either multiple eth's or the firewall are contributing towards my problem. I've failed both with DHCP in the guest as well as with a static IP for it. The IP I've used statically is 192.168.2.250 (where my eth0 device is 192.168.2.1). Is there anywhere I can download a guest disk image pre-installed? ----- Original Message -----From: Raul Saura To: Cc: Date: Friday, April 7 2006 02:20 PMSubject: [Fedora-xen] Network problem during FC5 XEN Guest installHello, I'm trying to create a xen-guest install using xenguest-install.py script, following the indications from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 . I've had to shrink mi xen0 domain to 128MB in order to allow guest to start install, otherwise I get the "The privileged domain did not balloon!" error-message. I've exported the FC5 DVD through NFS from the xen0 domain itself hoping it will be visible from the guest during the install process. Now I'm in the first stage of the anaconda Installer and DHCP IP learning does not seems to work, in fact no network seems to be available from the guest, because when I manually configure an IP, the guest can not see the NFS export either... I've been tcpduming for a while, and I can not see any traffic from/to the guest. But in fact I don't even known if i should be seeing any traffic from the xen0 eth0 interface, should I? Any help will be welcomed. Thanks a lot. Raul. -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From sfolkwil at redhat.com Sun Apr 9 00:08:37 2006 From: sfolkwil at redhat.com (Sam Folk-Williams) Date: Sat, 8 Apr 2006 20:08:37 -0400 Subject: [Fedora-xen] Gnome desktop in domU? (aka xorg and startx problems in domU) In-Reply-To: <44370D4D.5070106@gmail.com> References: <44370D4D.5070106@gmail.com> Message-ID: <20060409000837.GB2069@xander.rdu.redhat.com> BTW, please do not send html mail to these lists. Many of us use text only mail readers and having to sift through html means people either wont be able to read your note or they wont respond. Right now you can't use native X the way you desire, that will probably come at some point in the future. VNC generally works well if you tweak it a bit. For example. you can configure VNC to start automatically for certain users at boot time. See these articles for more info: http://www.redhat.com/magazine/006apr05/features/vnc/ http://www.redhat.com/magazine/007may05/features/vnc/ -Sam On Fri, Apr 07, 2006 at 09:09:33PM -0400, Denis Forveille wrote: > > > > > > > > I'm experimenting with xen on FC5 > (as domU and dom0).
>
> The idea is to have a machine running dom0 with 4 guests, one of the > guest would be my > workstation/desktop (with gnome running), the others guests would be > application/file/utilities servers.
>
> I would like to perform something > like:
> - logon to the domU via ssh, from dom0 for example ( size="-1">I also have tried it with "xm console > domU" from dom0, the result is the same)
> - run "startx" : that should bring > the standard logon screen
> - after login, use the gnome desktop as from a standard standalone > workstation
>
> But this does not work: startx does not start (first because the > xorg.conf is not created. I've tried to run "X -configuration" to > create xorg.conf, but  the command fails also to create the xorg.conf > file)
> BTW, on dom0 "startx" and the gnome desktop run perfectly
>
> Q:
> - Is it possible to configure X and run "startx" in a domU (I've read > somewhere on the net that this is not possible...). If so how to do it?
> - What is the best > way to get a full gnome desktop workstation that would run in domU like > a standalone workstation?
>
> I've tried the "vnc" solution, it works great but have limitations (at > least for me). and would greatly prefer what I described previsoulsy:
> (I don't know how to get the logon screen with vnc, the screen > resolution can not be easily choosen/changed,  the desktop to be > somewhat "slower" than the "local" desktop)
>
> Thanks in advance for any advice or pointer.
>
> (I'm not really a > newbee with linux, but I'm far from an expert...)
> > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- ? Sam Folk-Williams, RHCE ? Red Hat Global Support Services ? Phone: 919/754-4558 ? Cell: 919/943-9623 ? Fax: 919/754-3708 ? GPG ID: 1B0D46BA From tedkaz at optonline.net Sun Apr 9 00:50:13 2006 From: tedkaz at optonline.net (Ted Kaczmarek) Date: Sat, 08 Apr 2006 20:50:13 -0400 Subject: [Fedora-xen] Reminder post :-) Message-ID: <672066AF-E191-4A1E-9B5F-DB6DC3CD239A@optonline.net> xm info still doesn't provide changeset info, I know I posted about this before but that was quite some time back. Will open a bug up on this as IMHO changeset info can be most valuable. [root at inyoureyes]/etc/xen# xm info system : Linux host : inyoureyes.linsolutions.com release : 2.6.16-1.2080_FC5xen0 version : #1 SMP Tue Mar 28 04:13:51 EST 2006 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 1796 hw_caps : 0383fbff:c1cbfbff:00000000:00000020 total_memory : 2048 free_memory : 1328 xen_major : 3 xen_minor : 0 xen_extra : .0 xen_caps : xen-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.0 20060304 (Red Hat 4.1.0-3) cc_compile_by : bhcompile cc_compile_domain : build.redhat.com cc_compile_date : Tue Mar 28 03:35:03 EST 2006 Regards, ted From henning_sprang at gmx.de Sun Apr 9 01:15:38 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Sun, 09 Apr 2006 03:15:38 +0200 Subject: [Fedora-xen] problems with using xen-get.org images in fc5 In-Reply-To: <44383E42.5010705@gmx.de> References: <44383E42.5010705@gmx.de> Message-ID: <4438603A.9070606@gmx.de> Hi, Henning Sprang wrote: > [...] > When trying to start the vm, I get the error: > "Error: Error creating domain: Kernel image does not exist: > /boot/vmlinuz-2.6.16-1.2080_FC5xenU" I further investigated that. Fedora seems to require to explicitly set the bootloader to pygrub in the domU config. When doing so, I get the error: [root at localhost ~]# xm create -c basic-debian Using config file "/etc/xen/basic-debian". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 119, in get_config fs = fstype.open_fs(fn, offset) File "/usr/lib/python2.4/site-packages/grub/fsys/ext2/__init__.py", line 35, in open_fs return Ext2Fs(fn, offset = offset) ValueError: unable to open file Error: Boot loader didn't return any data! Which seems to be further described here: http://lists.xensource.com/archives/html/xen-users/2006-03/msg00721.html But I cannot find a solution. Does that mean I cannot use xen images created in block devices the "normal" way all howto's about xen describe? What Do I have to do to create a xen domU manually, or use a xen disk image created on another machine/distribution on Fedora? Why is Fedora not able to recognize the kernel variable in the config file correctly as it is usually done on other distributions? Henning From bench at silentmedia.com Sun Apr 9 01:49:54 2006 From: bench at silentmedia.com (Ben) Date: Sat, 8 Apr 2006 18:49:54 -0700 Subject: [Fedora-xen] Network problem during FC5 XEN Guest install In-Reply-To: <27423221.01144537504266.JavaMail.root@heilpern.com> References: <27423221.01144537504266.JavaMail.root@heilpern.com> Message-ID: I've said it before, but I had significant problems with anything more than trivial network setups using the default Xen scripts. I gave up, followed steps similar to these: http://wiki.xensource.com/xenwiki/XenNetworkingSuse?highlight=% 28XenNetworking%29 and things have been working pretty well ever since. On Apr 8, 2006, at 4:05 PM, Mark A Heilpern wrote: > After seeing what others with similar problems have posted, I've > learned that my problem seems to be with Xen's pethX creation > procedure... but I'm not sure how to convince Xen to do things just > a little differently. From raul.saura at gmail.com Sun Apr 9 08:56:34 2006 From: raul.saura at gmail.com (Raul Saura) Date: Sun, 9 Apr 2006 10:56:34 +0200 Subject: [Fedora-xen] Network problem during FC5 XEN Guest install In-Reply-To: <27423221.01144537504266.JavaMail.root@heilpern.com> References: <30914645.81144437283435.JavaMail.root@heilpern.com> <27423221.01144537504266.JavaMail.root@heilpern.com> Message-ID: Mark, You have to way to affect DomU networkin setup: 1) Modifying Xen-guest config file, take a look at http://wiki.xensource.com/xenwiki/XenNetworking#head-4f6aecaa0342826a7259cd08948266093cca4365 2) Manually adding or deleting interfaces to the bridges via brctl, thus selecting witch peth is connected to which vif. hope this help Raul On 4/9/06, Mark A Heilpern wrote: > > After seeing what others with similar problems have posted, I've learned > that my problem seems to be with Xen's pethX creation procedure... but I'm > not sure how to convince Xen to do things just a little differently. > > As a recap, my system has two ethernet devices: > My lan: eth0, 192.168.2.X > The Internet: eth1 > > When I reboot and Xen has created its various interfaces, I get peth1 as a > part of my xenbr0 device. This is a problem though since I need my guest > machines to be tied to the lan, not the internet -- but there is no peth0 > device to service this. I've tried swapping which card is which eth through > mac assignment but this just caused a peth0 to be created (mapping again to > my internet ethX device) and no peth1. I also tried swapping which device > gets the lan address vs. my external address, and the pethX device being > created is consistantly finding my internet device. > > How can I change the way pethX is created? > > ------------------------- > Original Message: > From: Mark A Heilpern > To: fedora-xen at redhat.com > Date: Friday, April 7 2006 03:14 PM > Subject: Re: [Fedora-xen] Network problem during FC5 XEN Guest install > For what it's worth I'm having the exact same problem you are... no > solution for me yet. > > In my case my dom0 has two physical ethernet interfaces and a > Firestarter-managed firewall letting my local traffic (on eth0) NAT out to > the internet (eth1), blocking most ports on eth1 from the outside world. I > haven't explored enough to determine if either multiple eth's or the > firewall are contributing towards my problem. I've failed both with DHCP in > the guest as well as with a static IP for it. The IP I've used statically is > 192.168.2.250 (where my eth0 device is 192.168.2.1). > > > Is there anywhere I can download a guest disk image pre-installed? > > > > > ----- Original Message -----From: Raul Saura To: < > fedora-xen at redhat.com>Cc: Date: Friday, April 7 2006 02:20 PMSubject: > [Fedora-xen] Network problem during FC5 XEN Guest installHello, > > I'm trying to create a xen-guest install using xenguest-install.pyscript, following the indications from > http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 > . > I've had to shrink mi xen0 domain to 128MB in order to allow guest to > start install, otherwise I get the "The privileged domain did not balloon!" > error-message. > I've exported the FC5 DVD through NFS from the xen0 domain itself hoping > it will be visible from the guest during the install process. > > > Now I'm in the first stage of the anaconda Installer and DHCP IP learning > does not seems to work, in fact no network seems to be available from the > guest, because when I manually configure an IP, the guest can not see the > NFS export either... > > > I've been tcpduming for a while, and I can not see any traffic from/to the > guest. But in fact I don't even known if i should be seeing any traffic from > the xen0 eth0 interface, should I? > > Any help will be welcomed. > > > Thanks a lot. > > Raul. > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > 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 henning_sprang at gmx.de Sun Apr 9 10:51:59 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Sun, 09 Apr 2006 12:51:59 +0200 Subject: [Fedora-xen] problems with using xen-get.org images in fc5 In-Reply-To: <8B7BFED8-D729-4A83-8C19-FFC167EA9063@optonline.net> References: <44383E42.5010705@gmx.de> <4438603A.9070606@gmx.de> <8B7BFED8-D729-4A83-8C19-FFC167EA9063@optonline.net> Message-ID: <4438E74F.3040200@gmx.de> Ted Kaczmarek wrote: > > Paste your domU config and an ls of /boot, that should help. "broken" domU config: #kernel = "/boot/vmlinuz-2.6-xenU" kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" ramdisk= "/boot/initrd-1.6.16-1.2080_FC5xenU.img" memory = 128 name = "fedora.fc5" #nics = 1 vif = [ '' ] dhcp = "dhcp" disk = ['file:/var/xen/xen-get-fedora/fedora.fc5.img,sda1,w', 'file:/var/xen/xen-get-fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro" #bootloader="/usr/bin/pygrub" like this, I get: Using config file "/etc/xen/xen-get-fedora". Error: Error creating domain: Kernel image does not exist: /boot/vmlinuz-2.6.16-1.2080_FC5xenU [root at localhost ~]# ls -l /boot/ total 12741 -rw-r--r-- 1 root root 63847 Mar 14 22:19 config-2.6.15-1.2054_FC5smp -rw-r--r-- 1 root root 59663 Mar 28 11:27 config-2.6.16-1.2080_FC5xen0 -rw-r--r-- 1 root root 28213 Mar 28 11:38 config-2.6.16-1.2080_FC5xenU drwxr-xr-x 2 root root 1024 Apr 8 14:42 grub -rw-r--r-- 1 root root 1788626 Apr 8 11:40 initrd-2.6.15-1.2054_FC5smp.img -rw-r--r-- 1 root root 1790016 Apr 8 12:26 initrd-2.6.16-1.2080_FC5xen0.img -rw-r--r-- 1 root root 1601032 Apr 8 12:26 initrd-2.6.16-1.2080_FC5xenU.img drwx------ 2 root root 12288 Apr 8 13:35 lost+found -rw-r--r-- 1 root root 831559 Mar 14 22:19 System.map-2.6.15-1.2054_FC5smp -rw-r--r-- 1 root root 814854 Mar 28 11:27 System.map-2.6.16-1.2080_FC5xen0 -rw-r--r-- 1 root root 637766 Mar 28 11:38 System.map-2.6.16-1.2080_FC5xenU -rw-r--r-- 1 root root 1564844 Mar 14 22:19 vmlinuz-2.6.15-1.2054_FC5smp -rw-r--r-- 1 root root 1529298 Mar 28 11:27 vmlinuz-2.6.16-1.2080_FC5xen0 -rw-r--r-- 1 root root 1232494 Mar 28 11:38 vmlinuz-2.6.16-1.2080_FC5xenU -rw-r--r-- 1 root root 265927 Mar 28 10:35 xen.gz-2.6.16-1.2080_FC5 -rwxr-xr-x 1 root root 734680 Mar 28 12:04 xen-syms-2.6.16-1.2080_FC5 When I remove the comment before the bootloader line, I get: Using config file "/etc/xen/xen-get-fedora". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 119, in get_config fs = fstype.open_fs(fn, offset) File "/usr/lib/python2.4/site-packages/grub/fsys/ext2/__init__.py", line 35, in open_fs return Ext2Fs(fn, offset = offset) ValueError: unable to open file Error: Boot loader didn't return any data! The working config generated by the fedora5 script described in the wiki looks like: # Automatically generated xen config file name = "fedora-simple" memory = "256" disk = [ 'file:/var/xen/fedora-simple,xvda,w' ] vif = [ 'mac=00:16:3e:16:03:83' ] bootloader="/usr/bin/pygrub" on_reboot = 'restart' on_crash = 'restart' > > > I have no problems with any of the images from jailtime.org > or any of the ones I spun using rpm. These are the same images that I had > running on Xen since pre 3.0 from hg checkouts sometime in November of > last year. I'll see if I can try the same with a jailtime image instead. This can take a while because the hardware I had for testing will not be available much longer. Henning From mark at heilpern.com Sun Apr 9 13:01:06 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Sun, 9 Apr 2006 09:01:06 -0400 (EDT) Subject: [Fedora-xen] Network problem during FC5 XEN Guest install In-Reply-To: Message-ID: <16334564.01144587666303.JavaMail.root@heilpern.com> My problem though is between my eth0 and eth1 real hardware devices, only a single pethX device is being created (by the kernel?)... Generally eth0 is my internal lan, so I need a peth0 device but it's just not there (ifconfig -a shows peth1 but not peth0). If I swap IP configurations between eth0 and eth1, or if I swap MAC bindings, the pethX device that's created is always the one tied to the internet (this is the most frustrating aspect since I can't seem to move around the problem). Thus when eth0 is my internet link and eth1 is my lan, I end up with a peth0 but no peth1. Is there a way after the fact to cause the kernel to create a new pethX device? I don't mind if I have to build a custom network-bridge script for each guest, but if I can't get a pethX device that corresponds to my lan I can't network to my guests in a reasonable way. Maybe I can abandon use of a bridge and instead spawn a new network for each vethX? That sounds quite a hassle but perhaps it can work. The problem I see then is the IP address of a machine must change to be on a unique network according to the xen id the guest receives. Thanks for the responses... Mark From henning at sprang.de Sat Apr 8 22:45:00 2006 From: henning at sprang.de (Henning Sprang) Date: Sun, 09 Apr 2006 00:45:00 +0200 Subject: [Fedora-xen] trouble with xen domU install script xenguest-install.py Message-ID: <44383CEC.4070403@sprang.de> Hi, I try to use xen on fedora, by going the way the fedora5 xen howto in the wiki describes. I installed the packages, xend seems to run fine, the xen ethernet interfaces seem to be there. I then run the script /usr/sbin/xenguest-install.py It seems to take 8-9 hours to complete - is there something I can do to make that faster? I also had major troubles with the install vm not getting a dhcp address, but instead of telling me so, after the dhcp condig failed I got no error, but the network config screen appeared again and again. Henning From veillard at redhat.com Sun Apr 9 14:11:42 2006 From: veillard at redhat.com (Daniel Veillard) Date: Sun, 9 Apr 2006 10:11:42 -0400 Subject: [Fedora-xen] trouble with xen domU install script xenguest-install.py In-Reply-To: <44383CEC.4070403@sprang.de> References: <44383CEC.4070403@sprang.de> Message-ID: <20060409141142.GA22325@redhat.com> On Sun, Apr 09, 2006 at 12:45:00AM +0200, Henning Sprang wrote: > Hi, > I try to use xen on fedora, by going the way the fedora5 xen howto in > the wiki describes. > > I installed the packages, xend seems to run fine, the xen ethernet > interfaces seem to be there. > > I then run the script /usr/sbin/xenguest-install.py > > It seems to take 8-9 hours to complete - is there something I can do to > make that faster? Give more RAM to the guest, 380MBytes intead of the 256MB minimum speed up thing a lot. Then reduce memory, see the previous posts on this list about this. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From denis.forveille at gmail.com Sun Apr 9 19:59:05 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Sun, 09 Apr 2006 15:59:05 -0400 Subject: [Fedora-xen] Gnome desktop in domU? (aka xorg and startx problems in domU) In-Reply-To: References: Message-ID: <44396789.9000302@gmail.com> An HTML attachment was scrubbed... URL: From denis.forveille at gmail.com Sun Apr 9 20:44:26 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Sun, 09 Apr 2006 16:44:26 -0400 Subject: [Fedora-xen] need advices on how to install domU with xenguest-install Message-ID: <4439722A.4030705@gmail.com> After reading instructions from from the "FedoraXenQuickstartFC5" doc and the xen user manual, I'm using the xenguest-install script to install my domUs. However, I have some questions on how you guys, perform installations of your domU servers: This is what I'm doing: - on dom0, create one lvg per domU (/dev/vg/domU1,/dev/vg/domU2,etc..) - format the lvg with "mkfs -t ext3 /dev/vg/domU1" - run xenguest-install, answering "/dev/vg/domU1" to the "What would you like to use as the disk (path)" question The goals is to be able later to mount that lvg and copy files from/to it (when the associated domU is down of course...) and later to clone it to create other domUs from it.. Anaconda starts fine, but I always get a message saying that the file system is not valid and it has to be reinitialised... Q: Is that normal? "/dev/vg/domU1" IS correct and the fs IS correct before running xenguest-install (checked by mount/copy/umount..) Then with diskdruid, I create only one partition in xvda (mount="/", fs=ext3). Anaconda gives a warning saying that there is no swap partition defined... Q: Is there a way to run xenguest-install and specify another lvg for the swap partition? Q: What guy do you do? do You define a swap partition? do you initially not define a swap partition and then, when he domU is installed, modify the domU configuration file to add another lvg for the swap, start the domU and configure there the swap partition? (It would be possible with disk druid to build another structure in the lvg (with "/boot", "/" and swap partition...) but I'll not be able to use the lvg from dom0 later, I guess. Remember, i want to be able to mount the lvg from dom0 when the domU is down) Then comes grub... - When anaconda ask for it, how do you configure grub on domU. Do you: 1) install it on the MBR of first disk (MBR of the disk with is mapped to the lvg?) 2) install it in first block of first partition (see remark above..) 3) don't install it, and after installation of domU. copy the kernel in /boot of dom0, update the domU configuration file to set the kernel and root parameter It seems that option 3 is the only one if I want to be able to mount the lvg from dom0 later... Q: what guys do you recommend there? I also tried to install FC5 by booting from the DVD on an lvg directly (in "/dev/vg/domU1"), but was not able to start it as a domU... Installation is OK, I used the existing "/boot" partition when asked for it (the one used by dom0)and tried to create a domU. My domU started but I had a lot of problems.. Most of them because I didn't manage to install FC5 in the lvg with the FC5xenU kernel (I checked all the menus where packages and selected and dint find any entry to choose the kernel). The standard kerne lwas installed. I successfully boot the domU with the xenU kernel (parameter kernel pointing to it in /boot in domu config file), but in domU there is no corresponding /lib/module dir... and because of that, thenetwork does not start ..(I stop here..) Q: is there a way to install FC5 this way (boot from DVD) and force it to install the FC5xenU kernel instead of the standard FC5 kernel? MANY MANY thaks for sharing. (Sorry for the loooonnng post..) From tedkaz at optonline.net Sun Apr 9 23:50:29 2006 From: tedkaz at optonline.net (Ted Kaczmarek) Date: Sun, 09 Apr 2006 19:50:29 -0400 Subject: [Fedora-xen] problems with using xen-get.org images in fc5 In-Reply-To: <4438E74F.3040200@gmx.de> References: <44383E42.5010705@gmx.de> <4438603A.9070606@gmx.de> <8B7BFED8-D729-4A83-8C19-FFC167EA9063@optonline.net> <4438E74F.3040200@gmx.de> Message-ID: <2C47BAB5-570A-4203-B91C-0719EFCFCC7A@optonline.net> On Apr 9, 2006, at 6:51 AM, Henning Sprang wrote: > Ted Kaczmarek wrote: >> Paste your domU config and an ls of /boot, that should help. > > "broken" domU config: > > #kernel = "/boot/vmlinuz-2.6-xenU" > kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" > ramdisk= "/boot/initrd-1.6.16-1.2080_FC5xenU.img" > memory = 128 > name = "fedora.fc5" > #nics = 1 > vif = [ '' ] > dhcp = "dhcp" > disk = ['file:/var/xen/xen-get-fedora/fedora.fc5.img,sda1,w', > 'file:/var/xen/xen-get-fedora/fedora.swap,sda2,w'] > root = "/dev/sda1 ro" > > #bootloader="/usr/bin/pygrub" > > > like this, I get: > > Using config file "/etc/xen/xen-get-fedora". > Error: Error creating domain: Kernel image does not exist: /boot/ > vmlinuz-2.6.16-1.2080_FC5xenU DomU booted right up for me, I pasted my domU config. I am passing selinux=0 to kernel on boot, otherwise I had all kinds of bad behavior. # Kernel image file. kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU" # Initial memory allocation (in megabytes) for the new domain. memory = 256 # A name for your domain. All domains must have different names. name = "idom11" #----------------------------------------------------------------------- ----- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. #disk = [ 'phy:VolGroup01/debian,sdb1,w' ] disk = ['file:/media/hdb1/jailtime/fedora.fc5.img,sda1,w', 'file:/ media/hdb1/jailtime/fedora.swap,sda2,w'] #----------------------------------------------------------------------- ----- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set root device. root = "/dev/sda1" # Sets runlevel 4. #extra = "r0 3 vdso=0" extra = "ro selinux=0 3" # Which CPU to start domain on? #cpu = 1 # leave to Xen to pick # Number of Virtual CPUS to use, default is 1 vcpus = 2 vif = ['' ,''] # Set if you want dhcp to allocate the IP address. ip='off' on_poweroff = 'destroy' on_reboot = 'restart' #on_crash = 'restart' on_crash = 'destroy' Regards, Ted From roger at gwch.net Mon Apr 10 08:17:30 2006 From: roger at gwch.net (Roger Grosswiler) Date: Mon, 10 Apr 2006 10:17:30 +0200 (CEST) Subject: [Fedora-xen] Migration of a DomU Message-ID: <43144.193.73.106.103.1144657050.squirrel@www.gwch.net> Hey, is it possible to migrate easily a DomU from one machine to another - using complete different hardware? Thanks, Roger From okajima at digitalinfra.co.jp Mon Apr 10 09:36:06 2006 From: okajima at digitalinfra.co.jp (Jun OKAJIMA) Date: Mon, 10 Apr 2006 18:36:06 +0900 Subject: [Fedora-xen] Migration of a DomU In-Reply-To: <43144.193.73.106.103.1144657050.squirrel@www.gwch.net> References: <43144.193.73.106.103.1144657050.squirrel@www.gwch.net> Message-ID: <200604100936.AA01020@bbb-jz5c7z9hn9y.digitalinfra.co.jp> > >is it possible to migrate easily a DomU from one machine to another - >using complete different hardware? > Yes, migration does not rely on H/W type. One issue is, dont use SSE/MMX, unless both PC have same func. --- Okajima, Jun. Tokyo, Japan. From aleksander.adamowski.redhat at altkom.com.pl Mon Apr 10 10:12:09 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Mon, 10 Apr 2006 12:12:09 +0200 Subject: [Fedora-xen] hald, dbus-daemon (messagebus service) - does a guest domain need those? Message-ID: <443A2F79.6050806@altkom.com.pl> Hi! I've noticed that a guest domain installed using xenguest-install.py has the HAL daemon and mesagebus dbus-daemon daemons active, eating up memory. Are those daemons really needed for minimal server installation? AFAIK, they are related to management of hardware and for desktop environments, while a guest domain is usually: 1. run on "virtual hardware" (no hot plugged devices, the hardware seen from the domain's perspective is quite uniform) 2. used for server, not dekstop environments I've disabled those 2 services, rebooted the guest domain and it works fine - so is it OK to disable those permanently? Or do I risk some problems occuring? Maybe it's a good idea to make Anaconda disable those services upon install by default? -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From vmm at datamarkets.com.ar Mon Apr 10 12:46:06 2006 From: vmm at datamarkets.com.ar (Victor Mihalik) Date: Mon, 10 Apr 2006 09:46:06 -0300 Subject: [Fedora-xen] ... Please... Help Me!! Message-ID: <443A538E.5090006@datamarkets.com.ar> Hi People, I've problems when I want to use a pci device within a guest machine. I try modify grub.conf and put physdev_dom0_hide and pciback.hide in the line of kernel and module but it does not happen anything. Somebody knows the way to make this? Thanks a lot Victor From dmorgan at gmi-mr.com Mon Apr 10 20:20:27 2006 From: dmorgan at gmi-mr.com (Duncan Morgan) Date: Mon, 10 Apr 2006 13:20:27 -0700 Subject: [Fedora-xen] eth0 not coming up in domU Message-ID: <000501c65cdc$376c9020$6401a8c0@dmmobile> Hello, I have a FC5 dom0 and have set up a White Box Linux 3.2 domU and the eth0 will not come up in this domain. I see the following error message ifup eth0 modprobe: QM_MODULES: Function not implemented modprobe: QM_MODULES: Function not implemented e100 device eth0 does not seem to be present, delaying initialization. The peth0 and xenbr0 are running in dom0 and appear to be configured correctly. I understand that the error message is about modules.conf versus modprobe.com but I'm told that this error message is irrelevant since the unprivileged kernel does not load modules. Thanks in advance for any help with this? Duncan From henning_sprang at gmx.de Mon Apr 10 22:24:08 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 11 Apr 2006 00:24:08 +0200 Subject: [Fedora-xen] trouble with xen domU install script xenguest-install.py In-Reply-To: <20060409141142.GA22325@redhat.com> References: <44383CEC.4070403@sprang.de> <20060409141142.GA22325@redhat.com> Message-ID: <443ADB08.5050609@gmx.de> Daniel Veillard wrote: > [...] > Give more RAM to the guest, 380MBytes intead of the 256MB minimum > speed up thing a lot. Then reduce memory, see the previous posts on this list > about this. > Hmm, it turned out that using a local mirror somebody made available for me made it a lot faster. Unfortunately this wasn't possible to see esaily. But one more reason was that I didn't know that I have to be very careful because fc5 trys to install a lot of software by default. Even removing all software selections I still get a 470MB installation. But that seems to be a fedora generic question and has nothing to do with xen. Henning From henning_sprang at gmx.de Mon Apr 10 22:30:35 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 11 Apr 2006 00:30:35 +0200 Subject: [Fedora-xen] need advices on how to install domU with xenguest-install In-Reply-To: <4439722A.4030705@gmail.com> References: <4439722A.4030705@gmail.com> Message-ID: <443ADC8B.2040104@gmx.de> Denis Forveille wrote: > [...] > This is what I'm doing: > - on dom0, create one lvg per domU (/dev/vg/domU1,/dev/vg/domU2,etc..) > - format the lvg with "mkfs -t ext3 /dev/vg/domU1" > - run xenguest-install, answering "/dev/vg/domU1" to the "What would > you like to use as the disk (path)" question The one time I used the script, successfully, I gave a location in the file system and the script generated a large file(which wasn't existing before!) that was used as a block device itself, where it created lvm volumes and partitions for files and swap. I don't know if you can feed some options into the script to change that behaviour and use an lvm volume instead of a location for a file, never looked into it or tried to run it with --help. From gregor.pirnaver at email.si Tue Apr 11 08:35:26 2006 From: gregor.pirnaver at email.si (Gregor Pirnaver) Date: Tue, 11 Apr 2006 10:35:26 +0200 Subject: [Fedora-xen] How to use xenguest-install.py to install to LVM? Message-ID: <20060411083530.A12108B7BD@www1.email.si> This is what I am doing: # lvcreate -L32768 -nroot.webserver VolGroup00 # mkfs -t ext3 /dev/VolGroup00/root.webserver # xenguest-install.py What is the name of your virtual machine? webserver How much RAM should be allocated (in megabytes)? 512 What would you like to use as the disk (path)? /dev/VolGroup00/root.webserver What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/ The problem is that Fedora installation doesn't treat /dev/VolGroup00/root.webserver as a partion but like a whole disk. How can I change this? Or how else should I do it? BTW is there a way to mount "xvda" paritions? ____________________ http://www.email.si/ From shyamal at flashmail.com Tue Apr 11 07:51:02 2006 From: shyamal at flashmail.com (shyamal thatte) Date: Tue, 11 Apr 2006 13:21:02 +0530 Subject: [Fedora-xen] Error creating Domain Message-ID: <443B5FE6.9060600@flashmail.com> Hi, Need help please XEN 3.0.1 on FC4 is domain 0. Installed FC4 on /dev/hda8 separate installation. When trying to 'xm create ' fails with error 0 There does not seem to be a Xen 3 User kernel. Can one create it ? Attached please find the xend logs and configuration file Thanks in advance for your help. Regards Shyamal -------------- next part -------------- A non-text attachment was scrubbed... Name: xend-debug.log Type: text/x-log Size: 995 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: text/x-log Size: 5151 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: oratest URL: From henning_sprang at gmx.de Tue Apr 11 12:44:58 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 11 Apr 2006 14:44:58 +0200 (MEST) Subject: [Fedora-xen] Error creating Domain References: <443B5FE6.9060600@flashmail.com> Message-ID: <27136.1144759498@www047.gmx.net> > --- Urspr?ngliche Nachricht --- > [...] > > XEN 3.0.1 on FC4 is domain 0. > > Installed FC4 on /dev/hda8 separate installation. What do you mean with the last sentence? Do you mean the domU FC4 which you put into hda8? How exactly did you install xen on FC4? I wonder that the references to the python files in your error logs point to pathes starting with /var/tmp, which is not exactly a nice location to install pythong scripts. Henning From henning_sprang at gmx.de Tue Apr 11 12:48:54 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 11 Apr 2006 14:48:54 +0200 (MEST) Subject: [Fedora-xen] How to use xenguest-install.py to install to LVM? References: <20060411083530.A12108B7BD@www1.email.si> Message-ID: <16995.1144759734@www079.gmx.net> Hi, > --- Urspr?ngliche Nachricht --- > [...] > The problem is that Fedora installation doesn't treat > /dev/VolGroup00/root.webserver as a partion but like a whole disk. How can > I > change this? Or how else should I do it? There was somebody else having problems with the fedory python script. I don't have a fedory install in front of me right now. I'd look into the python script to see if it accepts any options to do something else but the default, which is it creates a file as block device at the location you give there. The other solution is just create your domU on your own with the older howto in the fedora wiki (the one which is not suffixed with "5"). Henning From matbayer.web at web.de Tue Apr 11 14:05:32 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Tue, 11 Apr 2006 16:05:32 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <273241936@web.de> Hi, i have serveral DomU's running under Xen xen-3.0.1-4 kernel-xen0-2.6.16-1.2080_FC5. i have paravirtualized and fully virtualized systems (windows and linux). now the problem is whenever i start 2 fully virtualized systems in parallel (first start one then if this runs try to start the other one) the computer completely crashes and reboots, no more log entries... nothing. does anybody now how to debug such a problem ? for couriosity this occurs only on one system, i have a second system with a very similar setup and here i can start 2 fully virtualized (windows) systems in parallel without problem. any ideas ? regards, Matthias _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From katzj at redhat.com Tue Apr 11 14:36:19 2006 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 11 Apr 2006 10:36:19 -0400 Subject: [Fedora-xen] How to use xenguest-install.py to install to LVM? In-Reply-To: <20060411083530.A12108B7BD@www1.email.si> References: <20060411083530.A12108B7BD@www1.email.si> Message-ID: <1144766179.3875.1.camel@aglarond.local> On Tue, 2006-04-11 at 10:35 +0200, Gregor Pirnaver wrote: > The problem is that Fedora installation doesn't treat > /dev/VolGroup00/root.webserver as a partion but like a whole disk. How can I > change this? Or how else should I do it? Yes, as it turns out, the entire OS expects to have _disks_, not partitions. And going through and changing those assumptions isn't that reasonable. Instead, you export disks and things work. > BTW is there a way to mount "xvda" paritions? You can use device-mapper (via, eg, kpartx) or lomount for mounting partitions on an arbitrary block device like this Jeremy From yongkang.you at intel.com Tue Apr 11 14:53:14 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 11 Apr 2006 22:53:14 +0800 Subject: [Fedora-xen] Error creating Domain Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A212A@pdsmsx402.ccr.corp.intel.com> What's your configuration for xenU? Did you give a right disk option? Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of shyamal thatte >Sent: 2006?4?11? 15:51 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Error creating Domain > >Hi, > >Need help please > >XEN 3.0.1 on FC4 is domain 0. > >Installed FC4 on /dev/hda8 separate installation. > >When trying to 'xm create ' fails with error 0 >There does not seem to be a Xen 3 User kernel. Can one create it ? > >Attached please find the xend logs and configuration file > >Thanks in advance for your help. > >Regards >Shyamal From sct at redhat.com Tue Apr 11 15:09:50 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 11 Apr 2006 11:09:50 -0400 Subject: [Fedora-xen] eth0 not coming up in domU In-Reply-To: <000501c65cdc$376c9020$6401a8c0@dmmobile> References: <000501c65cdc$376c9020$6401a8c0@dmmobile> Message-ID: <1144768190.4006.1.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-10 at 13:20 -0700, Duncan Morgan wrote: > I have a FC5 dom0 and have set up a White Box Linux 3.2 domU and the eth0 > will not come up in this domain. Which domU kernel? If it's not a recent (post-Xen-3.0.0) one, you may be out of luck: XenSource changed the domU ABI before the final 3.0.0 release. --Stephen From sct at redhat.com Tue Apr 11 15:18:07 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 11 Apr 2006 11:18:07 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: <273241936@web.de> References: <273241936@web.de> Message-ID: <1144768687.4006.3.camel@orbit.scot.redhat.com> Hi, On Tue, 2006-04-11 at 16:05 +0200, Matthias Bayer wrote: > i have serveral DomU's running under Xen xen-3.0.1-4 kernel-xen0-2.6.16-1.2080_FC5. > i have paravirtualized and fully virtualized systems (windows and linux). > now the problem is whenever i start 2 fully virtualized systems in parallel (first start one then if this runs try to start the other one) the computer completely crashes and reboots, no more log entries... nothing. > > does anybody now how to debug such a problem ? With serial console, usually. There are also a number of upstream Xen updates for VMX, and we're putting together an update which may help there. Cheers, Stephen From Alex.Upton at instinet.com Tue Apr 11 15:24:35 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Tue, 11 Apr 2006 11:24:35 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: I have a similar issue on a Dell Power Edge 1850 running: Fedora Core 5 2.6.16-1.2080_FC5xen0 xen-3.0.1-4 Except my issue appears to affect the parent host as well. It seems to be relevant during any increased NIC utilization. If I'm copying data to or from a virtualized host the parent system will black screen without any kernel dump info, thus all i/o is halted and the only solution is a reboot. Any thoughts? -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Stephen C. Tweedie Sent: Tuesday, April 11, 2006 11:18 AM To: matbayer.web at web.de Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] two fully virtualized systems crashing Hi, On Tue, 2006-04-11 at 16:05 +0200, Matthias Bayer wrote: > i have serveral DomU's running under Xen xen-3.0.1-4 kernel-xen0-2.6.16-1.2080_FC5. > i have paravirtualized and fully virtualized systems (windows and linux). > now the problem is whenever i start 2 fully virtualized systems in parallel (first start one then if this runs try to start the other one) the computer completely crashes and reboots, no more log entries... nothing. > > does anybody now how to debug such a problem ? With serial console, usually. There are also a number of upstream Xen updates for VMX, and we're putting together an update which may help there. Cheers, Stephen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** From sct at redhat.com Tue Apr 11 15:41:58 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 11 Apr 2006 11:41:58 -0400 Subject: [Fedora-xen] need advices on how to install domU with xenguest-install In-Reply-To: <4439722A.4030705@gmail.com> References: <4439722A.4030705@gmail.com> Message-ID: <1144770119.4006.7.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-04-09 at 16:44 -0400, Denis Forveille wrote: > This is what I'm doing: > - on dom0, create one lvg per domU (/dev/vg/domU1,/dev/vg/domU2,etc..) > - format the lvg with "mkfs -t ext3 /dev/vg/domU1" The domU is expecting a *disk* image, including partitioning information, not just a single filesystem. > Anaconda starts fine, but I always get a message saying that the file > system is not valid and it has to be reinitialised... Right, it can't find the partition table so it creates a fresh one. > The goals is to be able later to mount that lvg and copy files from/to > it (when the associated domU is down of course...) and later to clone it > to create other domUs from it.. You can use "lomount" to mount a single partition from within the disk image (or manually use losetup or dmsetup to set a mapping to the partition.) --Stephen From Alex.Upton at instinet.com Tue Apr 11 21:07:18 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Tue, 11 Apr 2006 17:07:18 -0400 Subject: [Fedora-xen] Multiple virtual to physical nic setup docs Message-ID: All, I'm looking for documentation that can tell me how I can do the following with xen. basically I have a dual homed system, and want all virtual eth0 nics to utilize the real physical eth0 nic, and would like all virtual eth1 nics to use the real physical eth1 nic. as of now I have this: in my /etc/xen/host1 vif = [ 'mac=0a:00:00:00:00:01', 'mac=0b:00:00:00:00:01'] in my /etc/xen/xend-config.sxp (network-script 'network-bridge bridge=br0 netdev=eth0') (network-script 'network-bridge bridge=br1 netdev=eth1') on the virtual host i ssh in through the virtual eth0 interface then when i issue a tcpdump on the virtual eth1 i see real traffic for the real physical eth1, however when assigning an address on the virtual eth1, i can't ping it from outside the virtual environment. Any direction to specific setup docs would be greatly appreciated. Thanks, -Alex ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From sct at redhat.com Tue Apr 11 21:22:46 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 11 Apr 2006 17:22:46 -0400 Subject: [Fedora-xen] Tracebacks In-Reply-To: <3FDD18ED-AFDE-4358-856B-F146F8F99576@optonline.net> References: <3FDD18ED-AFDE-4358-856B-F146F8F99576@optonline.net> Message-ID: <1144790567.14984.0.camel@orbit.scot.redhat.com> Hi, On Sat, 2006-04-08 at 17:55 -0400, Ted Kaczmarek wrote: > EFLAGS: 00010086 (2.6.12.6-xenU) The 2.6.12 bits are now getting very old in the tooth; can you try with an FC5-based 2.6.16 kernel? Thanks, Stephen From dmorgan at gmi-mr.com Tue Apr 11 22:01:44 2006 From: dmorgan at gmi-mr.com (Duncan Morgan) Date: Tue, 11 Apr 2006 15:01:44 -0700 Subject: [Fedora-xen] eth0 not coming up in domU In-Reply-To: <1144768190.4006.1.camel@orbit.scot.redhat.com> Message-ID: <004801c65db3$85590250$3c09080a@dmmobile> Stephen, Kernel is 2.6.16-1.2080_FC5.xenU I've found that the problem was caused because the 2.4 based guest OS (White Box Linux) didn't support modprobe.conf so didn't load the CONFIG_XEN_NETDEV_FRONTEND Module. I've recompiled the kernel so that this module is built in and it resolved the issue. Thanks for your reply, Duncan -----Original Message----- From: Stephen C. Tweedie [mailto:sct at redhat.com] Sent: Tuesday, April 11, 2006 8:10 AM To: dmorgan at gmi-mr.com Cc: fedora-xen at redhat.com; Stephen Tweedie Subject: Re: [Fedora-xen] eth0 not coming up in domU Hi, On Mon, 2006-04-10 at 13:20 -0700, Duncan Morgan wrote: > I have a FC5 dom0 and have set up a White Box Linux 3.2 domU and the eth0 > will not come up in this domain. Which domU kernel? If it's not a recent (post-Xen-3.0.0) one, you may be out of luck: XenSource changed the domU ABI before the final 3.0.0 release. --Stephen From sct at redhat.com Wed Apr 12 03:17:12 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 11 Apr 2006 23:17:12 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: References: Message-ID: <1144811832.6151.22.camel@orbit.scot.redhat.com> Hi, On Tue, 2006-04-11 at 11:24 -0400, Alex.Upton at instinet.com wrote: > If I'm copying data to or from a virtualized host the parent system will > black screen without any kernel dump info, thus all i/o is halted and the > only solution is a reboot. > > Any thoughts? The original problem described a spontaneous reboot, not a "black screen" (what exactly do you mean by that, btw? The screen saver kicks in?) And what do you mean by kernel dump info --- HV VGA output, dmesg logs, or what? Thanks, Stephen From denis.forveille at gmail.com Wed Apr 12 03:20:23 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Tue, 11 Apr 2006 23:20:23 -0400 Subject: [Fedora-xen] How to use xenguest-install.py to install to LVM? In-Reply-To: <20060411083530.A12108B7BD@www1.email.si> References: <20060411083530.A12108B7BD@www1.email.si> Message-ID: <443C71F7.1020104@gmail.com> An HTML attachment was scrubbed... URL: From Alex.Upton at instinet.com Wed Apr 12 12:18:31 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Wed, 12 Apr 2006 08:18:31 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: Sorry, black screen meaning that all VGA output is disabled. And generally if there's a kernel panic or something core dumps there's a log to trace the errors back. In this scenario there isn't. And I should clarify the reboot as well, its not a software initiated reboot, it's a hard reboot. Admittedly very odd! Thanks, -Alex -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Stephen C. Tweedie Sent: Tuesday, April 11, 2006 11:17 PM To: Alex Upton Cc: fedora-xen at redhat.com Subject: RE: [Fedora-xen] two fully virtualized systems crashing Hi, On Tue, 2006-04-11 at 11:24 -0400, Alex.Upton at instinet.com wrote: > If I'm copying data to or from a virtualized host the parent system > will black screen without any kernel dump info, thus all i/o is halted > and the only solution is a reboot. > > Any thoughts? The original problem described a spontaneous reboot, not a "black screen" (what exactly do you mean by that, btw? The screen saver kicks in?) And what do you mean by kernel dump info --- HV VGA output, dmesg logs, or what? Thanks, Stephen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** From sct at redhat.com Wed Apr 12 14:43:08 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 12 Apr 2006 10:43:08 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: References: Message-ID: <1144852989.3337.1.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-04-12 at 08:18 -0400, Alex.Upton at instinet.com wrote: > Sorry, black screen meaning that all VGA output is disabled. > > And generally if there's a kernel panic or something core dumps there's a > log to trace the errors back. In this scenario there isn't. In that sort of situation, serial console is often the best way to try to capture information when using Xen. I've just added a section on it to the FC5 Xen wiki: http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 which should be helpful in setting this up. Thanks, Stephen From Alex.Upton at instinet.com Wed Apr 12 14:48:13 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Wed, 12 Apr 2006 10:48:13 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: Ahh very helpful! Most appreciated, Thanks! Don't suppose you have any docs or know where I can read up on multi-nic setup? The documentaton on the official xen wiki leaves much to be desired. -Alex -----Original Message----- From: Stephen C. Tweedie [mailto:sct at redhat.com] Sent: Wednesday, April 12, 2006 10:43 AM To: Alex Upton Cc: fedora-xen at redhat.com; sct at redhat.com Subject: RE: [Fedora-xen] two fully virtualized systems crashing Hi, On Wed, 2006-04-12 at 08:18 -0400, Alex.Upton at instinet.com wrote: > Sorry, black screen meaning that all VGA output is disabled. > > And generally if there's a kernel panic or something core dumps > there's a log to trace the errors back. In this scenario there isn't. In that sort of situation, serial console is often the best way to try to capture information when using Xen. I've just added a section on it to the FC5 Xen wiki: http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 which should be helpful in setting this up. Thanks, Stephen ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** From sct at redhat.com Wed Apr 12 15:02:19 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 12 Apr 2006 11:02:19 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: References: Message-ID: <1144854139.3337.7.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-04-12 at 10:48 -0400, Alex.Upton at instinet.com wrote: > Most appreciated, Thanks! > > Don't suppose you have any docs or know where I can read up on multi-nic > setup? The documentaton on the official xen wiki leaves much to be > desired. Not offhand, sorry. --Stephen From matbayer.web at web.de Wed Apr 12 15:03:06 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 12 Apr 2006 17:03:06 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <274230687@web.de> Hi Stephen, thanks a lot for sharing this information - very helpful ! i will shortly give it a try. thanks, Matthias > -----Urspr?ngliche Nachricht----- > Von: "Stephen C. Tweedie" > Gesendet: 12.04.06 16:43:32 > An: Alex.Upton at instinet.com > CC: fedora-xen at redhat.com > Betreff: RE: [Fedora-xen] two fully virtualized systems crashing > Hi, > > On Wed, 2006-04-12 at 08:18 -0400, Alex.Upton at instinet.com wrote: > > Sorry, black screen meaning that all VGA output is disabled. > > > > And generally if there's a kernel panic or something core dumps there's a > > log to trace the errors back. In this scenario there isn't. > > In that sort of situation, serial console is often the best way to try > to capture information when using Xen. I've just added a section on it > to the FC5 Xen wiki: > > http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 > > which should be helpful in setting this up. > > Thanks, > Stephen > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From bench at silentmedia.com Wed Apr 12 15:08:54 2006 From: bench at silentmedia.com (Ben) Date: Wed, 12 Apr 2006 08:08:54 -0700 Subject: [Fedora-xen] Multiple virtual to physical nic setup docs In-Reply-To: References: Message-ID: <63E79B0C-043B-4730-AACA-0B3884B4FFAC@silentmedia.com> I too would like to see documentation on how to do it with the default configuration. But in the mean time, you could just replace the default xen networking scripts with your own. That's why I did, and I have no complaints yet. On Apr 11, 2006, at 2:07 PM, Alex.Upton at instinet.com wrote: > All, > > I'm looking for documentation that can tell me how I can do the > following with xen. > > basically I have a dual homed system, and want all virtual eth0 > nics to utilize the real physical eth0 nic, and would like all > virtual eth1 nics to use the real physical eth1 nic. > > as of now I have this: > > in my /etc/xen/host1 > vif = [ 'mac=0a:00:00:00:00:01', > 'mac=0b:00:00:00:00:01'] > > in my /etc/xen/xend-config.sxp > (network-script 'network-bridge bridge=br0 netdev=eth0') > (network-script 'network-bridge bridge=br1 netdev=eth1') > > > on the virtual host i ssh in through the virtual eth0 interface > > then when i issue a tcpdump on the virtual eth1 i see real traffic > for the real physical eth1, however when assigning an address on > the virtual eth1, i can't ping it from outside the virtual > environment. > > > Any direction to specific setup docs would be greatly appreciated. > > Thanks, > -Alex > > > > > > > ***************************************************************** > <<>> > > In compliance with applicable rules and regulations, Instinet > reviews and archives incoming and outgoing email communications, > copies of which may be produced at the request of regulators. > This message is intended only for the personal and confidential > use of the recipients named above. If the reader of this email > is not the intended recipient, you have received this email in > error and any review, dissemination, distribution or copying is > strictly prohibited. If you have received this email in error, > please notify the sender immediately by return email and > permanently delete the copy you received. > > Instinet accepts no liability for any content contained in the > email, or any errors or omissions arising as a result of email > transmission. Any opinions contained in this email constitute > the sender's best judgment at this time and are subject to change > without notice. Instinet does not make recommendations of a > particular security and the information contained in this email > should not be considered as a recommendation, an offer or a > solicitation of an offer to buy and sell securities. > > ***************************************************************** > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From matbayer.web at web.de Wed Apr 12 15:29:13 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 12 Apr 2006 17:29:13 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <274254211@web.de> Hi, ok , now setup for serial console works fine, now here comes the output, hope somebody can help in interpreting .... see attached xendebug.txt file. hope for any help or suggestions! regards, Matthias > -----Urspr?ngliche Nachricht----- > Von: "Stephen C. Tweedie" > Gesendet: 12.04.06 17:02:39 > An: Alex.Upton at instinet.com > CC: fedora-xen at redhat.com > Betreff: RE: [Fedora-xen] two fully virtualized systems crashing > Hi, > > On Wed, 2006-04-12 at 10:48 -0400, Alex.Upton at instinet.com wrote: > > > Most appreciated, Thanks! > > > > Don't suppose you have any docs or know where I can read up on multi-nic > > setup? The documentaton on the official xen wiki leaves much to be > > desired. > > Not offhand, sorry. > > --Stephen > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xendebug.txt URL: From sct at redhat.com Wed Apr 12 19:58:55 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 12 Apr 2006 15:58:55 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: <274254211@web.de> References: <274254211@web.de> Message-ID: <1144871935.8799.14.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote: > > (0 of 1)XEN) DOM > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space > 000f03 > (XEN) Shadow table counts: l1=0 l2=0 hl2=0 This looks like the hypervisor ran out of memory. How much memory do you have, and how much is being given to each domain? --Stephen From sct at redhat.com Wed Apr 12 20:56:25 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 12 Apr 2006 16:56:25 -0400 Subject: [Fedora-xen] How to use xenguest-install.py to install to LVM? In-Reply-To: <443C71F7.1020104@gmail.com> References: <20060411083530.A12108B7BD@www1.email.si> <443C71F7.1020104@gmail.com> Message-ID: <1144875385.8799.21.camel@orbit.scot.redhat.com> Hi, On Tue, 2006-04-11 at 23:20 -0400, Denis Forveille wrote: > Maybe there is a faster way to do it Install to an LVM should Just Work --- I have half a dozen different Xen guests on different LVs on one of my boxes. The default setup partitions the LV as a disk, not as a single filesystem, true; but if you want to share the data with the dom0, then you can do so easily with lomount (it's easiest if you don't get the domU to set up its own LVM on top if you're going to do this.) --Stephen From sct at redhat.com Wed Apr 12 20:57:22 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 12 Apr 2006 16:57:22 -0400 Subject: [Fedora-xen] ... Please... Help Me!! In-Reply-To: <443A538E.5090006@datamarkets.com.ar> References: <443A538E.5090006@datamarkets.com.ar> Message-ID: <1144875442.8799.23.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-04-10 at 09:46 -0300, Victor Mihalik wrote: > I've problems when I want to use a pci device within a guest machine. I > try modify grub.conf and put physdev_dom0_hide and pciback.hide in the > line of kernel and module but it does not happen anything. The FC5 xen kernels don't have the PCI front/backend driver enabled. --Stephen From matbayer.web at web.de Thu Apr 13 07:30:04 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 13 Apr 2006 09:30:04 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <274903677@web.de> I have 4 GB of RAM, each DomU has 512 MB and i only try to run 2 windows DomU's ! total used free shared buffers cached Mem: 3501056 684452 2816604 0 69520 347260 -/+ buffers/cache: 267672 3233384 Swap: 2096440 0 2096440 do i need to configure something elswhere to give the hypervisor more memory ? can i create any other debugs that may be helpful to find the problem ? regards, Matthias > Hi, > > On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote: > > > > (0 of 1)XEN) DOM > > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space > > 000f03 > > (XEN) Shadow table counts: l1=0 l2=0 hl2=0 > > This looks like the hypervisor ran out of memory. How much memory do > you have, and how much is being given to each domain? > > --Stephen > > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From yongkang.you at intel.com Thu Apr 13 07:35:34 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 13 Apr 2006 15:35:34 +0800 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A2149@pdsmsx402.ccr.corp.intel.com> Hi Matthias, >Mem: 3501056 684452 2816604 0 69520 I am not quite clear about the dom0 memory. Is it 3.5G? How large the memory apply to dom0? I mean how about dom0_mem=. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >Sent: 2006?4?13? 15:30 >To: Stephen C. Tweedie >Cc: fedora-xen at redhat.com >Subject: RE: [Fedora-xen] two fully virtualized systems crashing > > > >I have 4 GB of RAM, each DomU has 512 MB and i only try to run 2 >windows DomU's ! > > total used free shared buffers >cached >Mem: 3501056 684452 2816604 0 69520 >347260 >-/+ buffers/cache: 267672 3233384 >Swap: 2096440 0 2096440 > >do i need to configure something elswhere to give the hypervisor more >memory ? >can i create any other debugs that may be helpful to find the problem ? > >regards, >Matthias > >> Hi, >> >> On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote: >> > >> > (0 of 1)XEN) DOM >> > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space >> > 000f03 >> > (XEN) Shadow table counts: l1=0 l2=0 hl2=0 >> >> This looks like the hypervisor ran out of memory. How much memory do >> you have, and how much is being given to each domain? >> >> --Stephen >> >> > > >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From matbayer.web at web.de Thu Apr 13 08:03:19 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 13 Apr 2006 10:03:19 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <274931474@web.de> OK - found the problem ! setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the problem !! before i haven't specified anything - so if i understand it right all the memory would belong to Dom0 and every DomU that starts 'grabs' a bit until Dom0-min-mem is reached. so does this behaviour then indicate that something with balooning is buggy ?? thanks Stephen and Yongkang for the help so far ! Matthias > -----Urspr?ngliche Nachricht----- > Von: "You, Yongkang" > Gesendet: 13.04.06 09:35:54 > An: "Stephen C. Tweedie" > CC: > Betreff: RE: [Fedora-xen] two fully virtualized systems crashing > Hi Matthias, > > >Mem: 3501056 684452 2816604 0 69520 > I am not quite clear about the dom0 memory. Is it 3.5G? > > How large the memory apply to dom0? I mean how about dom0_mem=. > > Best Regards, > Yongkang (Kangkang) ???? > > >-----Original Message----- > >From: fedora-xen-bounces at redhat.com > >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer > >Sent: 2006??4??13?? 15:30 > >To: Stephen C. Tweedie > >Cc: fedora-xen at redhat.com > >Subject: RE: [Fedora-xen] two fully virtualized systems crashing > > > > > > > >I have 4 GB of RAM, each DomU has 512 MB and i only try to run 2 > >windows DomU's ! > > > > total used free shared buffers > >cached > >Mem: 3501056 684452 2816604 0 69520 > >347260 > >-/+ buffers/cache: 267672 3233384 > >Swap: 2096440 0 2096440 > > > >do i need to configure something elswhere to give the hypervisor more > >memory ? > >can i create any other debugs that may be helpful to find the problem ? > > > >regards, > >Matthias > > > >> Hi, > >> > >> On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote: > >> > > >> > (0 of 1)XEN) DOM > >> > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space > >> > 000f03 > >> > (XEN) Shadow table counts: l1=0 l2=0 hl2=0 > >> > >> This looks like the hypervisor ran out of memory. How much memory do > >> you have, and how much is being given to each domain? > >> > >> --Stephen > >> > >> > > > > > >______________________________________________________________ > >_ > >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > > > >-- > >Fedora-xen mailing list > >Fedora-xen at redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-xen _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From yongkang.you at intel.com Thu Apr 13 08:27:03 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 13 Apr 2006 16:27:03 +0800 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A214B@pdsmsx402.ccr.corp.intel.com> Em~. Sounds true. "xm info" can show how large the memory Xen can recognize (total_memory) and how many free memory is left (free_memory) . I think the total_memory of your machine is only 2.5G. It means Xen can only know there is 2.5G memory, except you run a PAE enabled Xen. Xen0 usually doesn't need too much memory. I suggest you can use 512M or 1024M. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: Matthias Bayer [mailto:matbayer.web at web.de] >Sent: 2006?4?13? 16:03 >To: sct at redhat.com; You, Yongkang >Cc: fedora-xen at redhat.com >Subject: RE: [Fedora-xen] two fully virtualized systems crashing > >OK - found the problem ! >setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the >problem !! >before i haven't specified anything - so if i understand it right all the memory >would belong to Dom0 and every DomU that starts 'grabs' a bit until >Dom0-min-mem is reached. >so does this behaviour then indicate that something with balooning is >buggy ?? > >thanks Stephen and Yongkang for the help so far ! >Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: "You, Yongkang" >> Gesendet: 13.04.06 09:35:54 >> An: "Stephen C. Tweedie" >> CC: >> Betreff: RE: [Fedora-xen] two fully virtualized systems crashing > > >> Hi Matthias, >> >> >Mem: 3501056 684452 2816604 0 69520 >> I am not quite clear about the dom0 memory. Is it 3.5G? >> >> How large the memory apply to dom0? I mean how about dom0_mem=. >> >> Best Regards, >> Yongkang (Kangkang) ???? >> >> >-----Original Message----- >> >From: fedora-xen-bounces at redhat.com >> >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >> >Sent: 2006??4??13?? 15:30 >> >To: Stephen C. Tweedie >> >Cc: fedora-xen at redhat.com >> >Subject: RE: [Fedora-xen] two fully virtualized systems crashing >> > >> > >> > >> >I have 4 GB of RAM, each DomU has 512 MB and i only try to run 2 >> >windows DomU's ! >> > >> > total used free shared buffers >> >cached >> >Mem: 3501056 684452 2816604 0 69520 >> >347260 >> >-/+ buffers/cache: 267672 3233384 >> >Swap: 2096440 0 2096440 >> > >> >do i need to configure something elswhere to give the hypervisor more >> >memory ? >> >can i create any other debugs that may be helpful to find the problem ? >> > >> >regards, >> >Matthias >> > >> >> Hi, >> >> >> >> On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote: >> >> > >> >> > (0 of 1)XEN) DOM >> >> > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space >> >> > 000f03 >> >> > (XEN) Shadow table counts: l1=0 l2=0 hl2=0 >> >> >> >> This looks like the hypervisor ran out of memory. How much memory do >> >> you have, and how much is being given to each domain? >> >> >> >> --Stephen >> >> >> >> >> > >> > >> >>____________________________________________________________ >__ >> >_ >> >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >> >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 >> > >> >-- >> >Fedora-xen mailing list >> >Fedora-xen at redhat.com >> >https://www.redhat.com/mailman/listinfo/fedora-xen > > >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From rmortimer at bluechiptechnology.co.uk Thu Apr 13 10:30:46 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Thu, 13 Apr 2006 11:30:46 +0100 Subject: [Fedora-xen] Running FC4 Guest on FC5 Message-ID: <007501c65ee5$537276d0$5f00000a@rmortimer> I can set up and run FC5 guests on FC5 but I want to run a FC4 guest under FC5 to trial zimbra. I have tried the FC4 howto and made a FC4 image but I can't get to boot. The new xen config file seems to use a python bootloader and the old system references a kernel to use. Does the boot kernel for the guest have to reside on the host as well as the guest? Are there docs on the Python boot system? Any pointers welcome Robert From wsouto at gmail.com Thu Apr 13 13:37:44 2006 From: wsouto at gmail.com (Walter Souto) Date: Thu, 13 Apr 2006 10:37:44 -0300 Subject: [Fedora-xen] How to configure eth0 via xen config files Message-ID: Hi, I have one host with two guests. All of them are FC5 and working just fine (since I don't have firewall enabled at the host). So, I was wondering if there is a method to give the guest the IP (and gateway/dns) when Xen boot the virtual machine. And if there's a way to do this, how can I configure the guests to take the IP (and gateway/dns)? TIA, -- Walter. From listxenusers at in-tuition.net Thu Apr 13 13:57:44 2006 From: listxenusers at in-tuition.net (In-Tuition Xen) Date: Thu, 13 Apr 2006 14:57:44 +0100 Subject: [Fedora-xen] Running FC4 Guest on FC5 Message-ID: Robert Mortimer scribbled on 13 April 2006 11:31: > I can set up and run FC5 guests on FC5 but I want to run a FC4 guest > under FC5 to trial zimbra. I have tried the FC4 howto and made a FC4 > image but I can't get to boot. > > The new xen config file seems to use a python bootloader and the old > system references a kernel to use. > > Does the boot kernel for the guest have to reside on the host as well > as the guest? > Are there docs on the Python boot system? I'm currently doing this. I've got a couple of FC4 domU's running on a FC5 dom0. You need the kernel image on the host (dom0) and the guest (domU), and obviously entered in the xen config file. My domU's were actually built on a FC4 dom0 and then transferred across once my FC5 dom0 was built so I don't know if the build process is what's causing your problem. Matt. From rmortimer at bluechiptechnology.co.uk Thu Apr 13 15:20:53 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Thu, 13 Apr 2006 16:20:53 +0100 Subject: [Fedora-xen] Running FC4 Guest on FC5 In-Reply-To: Message-ID: <000901c65f0d$dac5af80$5f00000a@rmortimer> > Robert Mortimer scribbled on 13 April 2006 11:31: > > I can set up and run FC5 guests on FC5 but I want to run a FC4 guest > > under FC5 to trial zimbra. I have tried the FC4 howto and made a FC4 > > image but I can't get to boot. > > > > The new xen config file seems to use a python bootloader and the old > > system references a kernel to use. > > > > Does the boot kernel for the guest have to reside on the host as well > > as the guest? > > Are there docs on the Python boot system? > > I'm currently doing this. I've got a couple of FC4 domU's running on a > FC5 dom0. You need the kernel image on the host (dom0) and the guest > (domU), and obviously entered in the xen config file. > > My domU's were actually built on a FC4 dom0 and then transferred across > once my FC5 dom0 was built so I don't know if the build process is > what's causing your problem. > > Matt. > Thanks Matt. I think I need to move the FC4 kernel image to the host (dom0) and then I will try the standard FC4 xen config (no pyboot). The new FC5 script is good because it lets you install live into a virtual machine rather than make an image and hope that it starts!. Robert PS are your images file based or partitions? From listxenusers at in-tuition.net Thu Apr 13 17:06:27 2006 From: listxenusers at in-tuition.net (In-Tuition Xen) Date: Thu, 13 Apr 2006 18:06:27 +0100 Subject: [Fedora-xen] Running FC4 Guest on FC5 Message-ID: Robert Mortimer scribbled on 13 April 2006 16:21: >> Robert Mortimer scribbled on 13 April 2006 11:31: >>> I can set up and run FC5 guests on FC5 but I want to run a FC4 guest >>> under FC5 to trial zimbra. I have tried the FC4 howto and made a FC4 >>> image but I can't get to boot. >>> >>> The new xen config file seems to use a python bootloader and the old >>> system references a kernel to use. >>> >>> Does the boot kernel for the guest have to reside on the host as >>> well as the guest? Are there docs on the Python boot system? >> >> I'm currently doing this. I've got a couple of FC4 domU's running >> on a FC5 dom0. You need the kernel image on the host (dom0) and the >> guest (domU), and obviously entered in the xen config file. >> >> My domU's were actually built on a FC4 dom0 and then transferred >> across once my FC5 dom0 was built so I don't know if the build >> process is what's causing your problem. >> >> Matt. >> > Thanks Matt. > > I think I need to move the FC4 kernel image to the host (dom0) and > then I will > try the standard FC4 xen config (no pyboot). The new FC5 script is > good because > it lets you install live into a virtual machine rather than make an > image and > hope that it starts!. > > Robert > PS are your images file based or partitions? Hi Robert, I've only been using xen in FC5 for a few days and haven't had time to play around much so I'm not familiar with the new scripts. I created my config files manually and just copied the domU's across along with the kernel image. My DomU's are file based because they do little IO and I find them easier to manage this way. I did convert one to LVM just to check it worked, and if I ever need the IO performance I'll take this route. In case it helps, my domU xen configs look like (I've got two bridged nics setup): kernel ="/boot/vmlinuz-2.6.12.6-xen3_12.1_fc4" memory = 128 name = "xendev" vcpus = 2 vif = [ 'mac=FE:FD:25:63:74:49,bridge=xenbr0', 'mac=FE:FD:3D:49:28:26,bridge=xenbr1' ] disk = ['file:/xenimages/xendev.img,sda1,w'] root = "/dev/sda1" extra = "ro selinux=0 3" Matt. From wsouto at gmail.com Thu Apr 13 17:41:46 2006 From: wsouto at gmail.com (Walter Souto) Date: Thu, 13 Apr 2006 14:41:46 -0300 Subject: [Fedora-xen] How to configure eth0 via xen config files In-Reply-To: <000a01c65f0d$db7d66c0$5f00000a@rmortimer> References: <000a01c65f0d$db7d66c0$5f00000a@rmortimer> Message-ID: Hi, > I think you can either configure the guest with static information or > use DHCP. I may have missed something in the question though. > No you didn't. Maybe my question don't make sense... But It's exactly what I'm doing now. So, if I need to replicate about 20 guests, each one with your own static IP, I can use DHCP and enforce IP's using mac addr. But, is it possible to do this using the Xen configuration files for the vm's? Just to get somethings a bit simple avoiding DHCP. And thanks for your answer. -- Walter. From sct at redhat.com Thu Apr 13 19:43:45 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Thu, 13 Apr 2006 15:43:45 -0400 Subject: [Fedora-xen] two fully virtualized systems crashing In-Reply-To: <274931474@web.de> References: <274931474@web.de> Message-ID: <1144957426.3422.23.camel@orbit.scot.redhat.com> Hi, On Thu, 2006-04-13 at 10:03 +0200, Matthias Bayer wrote: > setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the problem !! > before i haven't specified anything - so if i understand it right all the memory would belong to Dom0 and every DomU that starts 'grabs' a bit until Dom0-min-mem is reached. > so does this behaviour then indicate that something with balooning is buggy ?? Yes, it might do: could you open a bugzilla with exact steps to reproduce this so that we can track it, please? Many thanks, Stephen From matbayer.web at web.de Thu Apr 13 20:55:32 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 13 Apr 2006 22:55:32 +0200 Subject: [Fedora-xen] two fully virtualized systems crashing Message-ID: <275734547@web.de> done ! https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188948 [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188948] thanks again for all the help and hints ! Matthias *Von:* "Stephen C. Tweedie" *Gesendet:* 13.04.06 21:43:53 *An:* Matthias Bayer *CC:* "You, Yongkang" , fedora-xen at redhat.com, Stephen Tweedie *Betreff:* RE: [Fedora-xen] two fully virtualized systems crashing Hi, On Thu, 2006-04-13 at 10:03 +0200, Matthias Bayer wrote: > setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the problem !! > before i haven't specified anything - so if i understand it right all the memory would belong to Dom0 and every DomU that starts 'grabs' a bit until Dom0-min-mem is reached. > so does this behaviour then indicate that something with balooning is buggy ?? Yes, it might do: could you open a bugzilla with exact steps to reproduce this so that we can track it, please? Many thanks, Stephen SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfu at kaneda.iguw.tuwien.ac.at Fri Apr 14 13:01:00 2006 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Fri, 14 Apr 2006 15:01:00 +0200 Subject: [Fedora-xen] xen + lvm + backup ? Message-ID: <443F9D0C.4070207@kaneda.iguw.tuwien.ac.at> Hi, I wonder how to perform a backup (in Dom0) of several DomU's running in a Dom0. fact: a filesystem that is used by a DomU should not be mounted in Dom0 when the DomU is running and accessing it/writing to it. possible solution would be to shutdown DomU, backup its file systems in Dom0 and restart DomU. If the DomU uses devices which are LVM volumes in dom0, a possible scenario could be: - create a snapshot in Dom0 of the LVM volume which is used by DomU - mount the snapshot volume in Dom0 - back it up in Dom0 - unmount & remove the snapshot in Dom0. could this work ? regards, rainer. From rfu at kaneda.iguw.tuwien.ac.at Fri Apr 14 17:44:10 2006 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Fri, 14 Apr 2006 19:44:10 +0200 Subject: [Fedora-xen] no eth0 in guest Message-ID: <443FDF6A.3090007@kaneda.iguw.tuwien.ac.at> Hi, I'm running FC5 with the current 2.6.16-1.2080_FC5xen0 kernel in Dom0. I managed to set up several guests: 1) image-file based FC5 installed via xenguest-install.py. this one has the eth0 device and a working network, but I don't want to use the image file, but LVM volumes (which seems not possible with xenguest-install.py) 2) a centos 4.2 based on an image file I downloaded from a web site. this one has no eth0 device in the guest, therefore networking doesn't work. 3) FC4 using LVM volumes, installed via "yum -c http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y groupinstall Base". this one also has no eth0 device in the guest. 4) FC5 using LVM volumes, installed via "yum --installroot=/mnt/ -y groupinstall base". this one also has no eth0 device in the guest. in the latter case, ifconfig in Dom0 looks like this: eth0 Link encap:Ethernet HWaddr 00:01:02:B5:F8:90 inet addr:192.168.5.10 Bcast:192.168.5.255 Mask:255.255.255.0 inet6 addr: fe80::201:2ff:feb5:f890/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:855425 errors:0 dropped:0 overruns:0 frame:0 TX packets:995199 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:568177794 (541.8 MiB) TX bytes:467490312 (445.8 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:855428 errors:0 dropped:0 overruns:1 frame:0 TX packets:995245 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:568177957 (541.8 MiB) TX bytes:468158849 (446.4 MiB) Interrupt:9 Base address:0xe000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:995199 errors:0 dropped:0 overruns:0 frame:0 TX packets:855427 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:467490312 (445.8 MiB) TX bytes:568177962 (541.8 MiB) vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:2715 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:359 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41441 (40.4 KiB) TX bytes:468 (468.0 b) domain config file: name = "fc5" memory = "128" kernel="/boot/vmlinuz-2.6.16-1.2080_FC5xenU" vif = [ 'mac=00:16:3e:4c:77:fa' ] disk = [ 'phy:/dev/vg_data/lv_fc5_root,sda1,w', 'phy:/dev/vg_data/lv_fc5_data,sda2,w', 'phy:/dev/vg_data/lv_fc5_swap,sda3,w' ] root="/dev/sda1" extra = "ro selinux=0 3" on startup, the FC5 domain doesn't complain about missing kernel modules etc. I also installed the kernel-xenU-2.6.16-1.2080_FC5.i686.rpm in the guest, but that didn't help. any idea what I have to do to get an eth0 in the guest ? tnx in advance. From rfu at kaneda.iguw.tuwien.ac.at Fri Apr 14 19:18:40 2006 From: rfu at kaneda.iguw.tuwien.ac.at (Rainer Fuegenstein) Date: Fri, 14 Apr 2006 21:18:40 +0200 Subject: [Fedora-xen] no eth0 in guest In-Reply-To: <443FDF6A.3090007@kaneda.iguw.tuwien.ac.at> References: <443FDF6A.3090007@kaneda.iguw.tuwien.ac.at> Message-ID: <443FF590.7020201@kaneda.iguw.tuwien.ac.at> "modprobe xennet" solved the problem. > Hi, > > I'm running FC5 with the current 2.6.16-1.2080_FC5xen0 kernel in Dom0. I > managed to set up several guests: > > 1) image-file based FC5 installed via xenguest-install.py. this one has > the eth0 device and a working network, but I don't want to use the image > file, but LVM volumes (which seems not possible with xenguest-install.py) > > 2) a centos 4.2 based on an image file I downloaded from a web site. > this one has no eth0 device in the guest, therefore networking doesn't > work. > > 3) FC4 using LVM volumes, installed via "yum -c > http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y > groupinstall Base". this one also has no eth0 device in the guest. > > 4) FC5 using LVM volumes, installed via "yum --installroot=/mnt/ -y > groupinstall base". this one also has no eth0 device in the guest. > > in the latter case, ifconfig in Dom0 looks like this: > > eth0 Link encap:Ethernet HWaddr 00:01:02:B5:F8:90 > inet addr:192.168.5.10 Bcast:192.168.5.255 Mask:255.255.255.0 > inet6 addr: fe80::201:2ff:feb5:f890/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:855425 errors:0 dropped:0 overruns:0 frame:0 > TX packets:995199 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:568177794 (541.8 MiB) TX bytes:467490312 (445.8 MiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:855428 errors:0 dropped:0 overruns:1 frame:0 > TX packets:995245 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:568177957 (541.8 MiB) TX bytes:468158849 (446.4 MiB) > Interrupt:9 Base address:0xe000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:995199 errors:0 dropped:0 overruns:0 frame:0 > TX packets:855427 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:467490312 (445.8 MiB) TX bytes:568177962 (541.8 MiB) > > vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:2715 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:359 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:41441 (40.4 KiB) TX bytes:468 (468.0 b) > > domain config file: > > name = "fc5" > memory = "128" > kernel="/boot/vmlinuz-2.6.16-1.2080_FC5xenU" > vif = [ 'mac=00:16:3e:4c:77:fa' ] > disk = [ 'phy:/dev/vg_data/lv_fc5_root,sda1,w', > 'phy:/dev/vg_data/lv_fc5_data,sda2,w', > 'phy:/dev/vg_data/lv_fc5_swap,sda3,w' ] > root="/dev/sda1" > extra = "ro selinux=0 3" > > on startup, the FC5 domain doesn't complain about missing kernel modules > etc. I also installed the kernel-xenU-2.6.16-1.2080_FC5.i686.rpm in the > guest, but that didn't help. > > any idea what I have to do to get an eth0 in the guest ? > > tnx in advance. > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From jklein at saugus.k12.ca.us Fri Apr 14 20:19:36 2006 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 14 Apr 2006 13:19:36 -0700 Subject: [Fedora-xen] Xen and GFS Message-ID: I'm trying to get Xen to work in a using GFS on a SAN and FC5, but am not having much luck. It looks like GFS can't get a lock on the xvd file, for some reason, and I can't figure it out. I am able to read and write to GFS in any other way, from all the nodes, without problem. Can't install directly to the GFS volume, and if I install on a local drive, copy to GFS volume, and load, I end up with a read only file system. Log below. Any assistance would be greatly appreciated. Apr 14 10:47:36 blade1 kernel: GFS: fsid=alpha:gfs1.1: time = 1145036856 Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: warning: assertion "gfs_glock_is_locked_by_me(ip->i_gl)" failed Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: function = gfs_prepare_write Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: file = /usr/ src/build/729060-x86_64/BUILD/xen0/src/gfs/ops_address.c, line = 329 From thingsmith at comcast.net Sat Apr 15 03:12:05 2006 From: thingsmith at comcast.net (thingsmith at comcast.net) Date: Sat, 15 Apr 2006 03:12:05 +0000 Subject: [Fedora-xen] Need 6 VIF in a DomU but not succeeding Message-ID: <041520060312.5300.4440648500098780000014B42200750744089B07039C090207089B@comcast.net> I am trying to have figure Xen 3.0 / FC 5 but seem to be having network problems. I need to confiure DomU to have 6 network interfaces (vif). 4 of the interfaces need to communication in one network but 6 differnt sub nets 2 interfaces in a completely different network. For example, there would one interface each of the four subnets in192.168.1.0/26. The other two would be in 192.168.2.0/25. In the configuration file I have the 4 vifs 192.168.1.0/26 into a single xenbr0. Each of the 192.168.2.0/25 are in differnt briges. In a non-Xen environment I have used overlays on a single NIC. I tried the same in Xen but it seems to count the overlays as vifs. The best that I have been able to do is 3 vifs Any suggestion would be greatly appreciated. -- Harry Smith thingsmith at comcast.net From felipe.alfaro at gmail.com Sat Apr 15 16:56:21 2006 From: felipe.alfaro at gmail.com (Felipe Alfaro Solana) Date: Sat, 15 Apr 2006 18:56:21 +0200 Subject: [Fedora-xen] Xen and LVM Message-ID: <6f6293f10604150956y682e9aecna6e12ee5a8ceb996@mail.gmail.com> Hello. I'm having problems using xenguest-install.py when trying to install a FC5 DomU into an LVM volume: # xm create -c Download Using config file "/etc/xen/Download". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 119, in get_config fs = fstype.open_fs(fn, offset) File "/usr/lib/python2.4/site-packages/grub/fsys/ext2/__init__.py", line 35, in open_fs return Ext2Fs(fn, offset = offset) ValueError: unable to open file Error: Boot loader didn't return any data! The volume was formatted by using mkfs.ext3. # stat /dev/Main/Download File: `/dev/Main/Download' -> `/dev/mapper/Main-Download' Size: 25 Blocks: 0 IO Block: 4096 symbolic link Device: fh/15d Inode: 5571 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2006-04-15 18:51:46.000000000 +0200 Modify: 2006-04-15 18:36:13.501729841 +0200 Change: 2006-04-15 18:36:13.501729841 +0200 This is the domain configuration file: # Automatically generated xen config file name = "Download" memory = "256" disk = [ 'phy:Main/Download,xvda,w' ] #disk = [ 'phy:/dev/Main/Download,xvda,w' ] vif = [ 'mac=00:16:3e:0c:b1:ef' ] bootloader="/usr/bin/pygrub" on_reboot = 'restart' on_crash = 'restart' Any ideas? Thanks. From thingsmith at comcast.net Sat Apr 15 20:58:50 2006 From: thingsmith at comcast.net (thingsmith at comcast.net) Date: Sat, 15 Apr 2006 20:58:50 +0000 Subject: [Fedora-xen] Mac Address Confusion Message-ID: <041520062058.6891.44415E8A000E8CC600001AEB2200737478089B07039C090207089B@comcast.net> I am confused about XEN mac addresses. The Xen wiki is confusing it said not to use mac address starting with 00 but the default is 00:16:3e What is the correct mac address range to use? -- Harry Smith thingsmith at comcast.net From igeorgex at googlemail.com Sun Apr 16 19:19:41 2006 From: igeorgex at googlemail.com (George) Date: Sun, 16 Apr 2006 21:19:41 +0200 Subject: [Fedora-xen] xm save/migrate doesn't work Message-ID: Hi, I tried to use the "xm save" and "xm migrate" feature of Xen on FC5 (all updates installed, kernel is 2.6.16-1.2080_FC5xen0) but a "xm save" fails with the message (from the xend.log): -------------------------- [2006-04-16 20:39:12 xend] DEBUG (XendCheckpoint:79) [xc_save]: /usr/lib64/xen/bin/xc_save 10 17 27 0 0 0 [2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:226) Unable to get platform info.: 9 [2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:98) Save failed on domain fc5test (27). Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 92, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 217, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_save 10 17 27 0 0 0 failed -------------------------- The same problem exists with "xm migrate" because it calls a "xm save". It looks like this problem is releated to FC5 and Xen because on other (non FC5) platforms it works. Are there any workarounds for this problem? From ssrini at linuxmail.org Mon Apr 17 06:22:20 2006 From: ssrini at linuxmail.org (Srinivasan S) Date: Mon, 17 Apr 2006 14:22:20 +0800 Subject: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5 Message-ID: <20060417062220.5F09D7B5E3@ws5-10.us4.outblaze.com> Hi Folks, I have FC5 installed with Xen 3.x from the official xensource.com tarball. The dom0 boots perfectly. I have a multiboot system with FC5 installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on /dev/hdc1. Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. (I had this working earlier in FC4 and Xen 2.x without issues) The configuration file I use is : /etc/xen/suseguest (contents) kernel = "/boot/vmlinuz-2.6.16-xen" memory = 100 name = "suseguest" vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2'] gateway = "192.168.1.1" netmask = "255.255.255.0" disk = ['file:/dev/hdc3,hdc3,w'] root = "/dev/hdc3 rw" (As a variation to the above I also tried vif=[''] etc with no avail) On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of errors on module load that modules.dep file is not found etc .. However the boot process continues uninterrupted and Iam finally provided the terminal login prompt. Iam also able to successfully login. After logging in, however an ifconfig reveals that the virtual if 192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) .. I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with the same result. (To remove the modules.dep problem, I also copied the files from my FC5 /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but networking still does not work) The dom0 ifconfig reveals that the bridge and peth0 etc are all setup properly. All help to get this "networking issue" resolved is appreciated. Regards Srini -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze From henning_sprang at gmx.de Mon Apr 17 11:00:08 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Mon, 17 Apr 2006 13:00:08 +0200 Subject: [Fedora-xen] Error creating Domain In-Reply-To: <443BB855.2080901@flashmail.com> References: <443B5FE6.9060600@flashmail.com> <27136.1144759498@www047.gmx.net> <443BB855.2080901@flashmail.com> Message-ID: <44437538.8080609@gmx.de> Sorry, I am bit slow: shyamal thatte wrote: > Hi, > > installed xen 3.0.1 from the xen-3.0-x86_32-fc4.bin.tar provided on > xensource. > installed the 3 RPM's within it > 1) xen-3.0.1-64.1_fc4.i386.rpm 2) > xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm > 3) xen-devel-3.0.1-64.1_fc4.i386.rpm > .... there is no User kernel RPM included with xen 3 Sorry, I don't know about that bin.tra package - does ist actualkly contain 3 rpm's then? Sounds a bit weird... You don't always need two xen kernels, it's possible to mae one kernel that can be used for domU and dom0. > > After reboot into the 2.6.12_xen3 kernel I can see DOM 0 > > I did a fresh install of FC4 into /dev/hda8 with root on the same system > I installed vmlinuz-2.6.12-1.1390_FC4xenU into it > > When I try to start the guest domain on /dev/hda8 I get the errors and > it does not start. What errrs are you exactly getting? > Should I install xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm on /dev/hda8 > and try and boot it as a guest domain ? Yes, I'd try to install the same kernel rpm in domU as in dom0! Henning From deshantm at gmail.com Mon Apr 17 13:54:10 2006 From: deshantm at gmail.com (Todd Deshane) Date: Mon, 17 Apr 2006 09:54:10 -0400 Subject: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5 In-Reply-To: <20060417062220.5F09D7B5E3@ws5-10.us4.outblaze.com> References: <20060417062220.5F09D7B5E3@ws5-10.us4.outblaze.com> Message-ID: <1e16a9ed0604170654q5a14750co4a3da5e0faf367a4@mail.gmail.com> did you try: modprobe xennet On 4/17/06, Srinivasan S wrote: > > Hi Folks, > > I have FC5 installed with Xen 3.x from the official xensource.comtarball. The dom0 boots perfectly. I have a multiboot system with FC5 > installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on > /dev/hdc1. > > Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. (I > had this working earlier in FC4 and Xen 2.x without issues) > > The configuration file I use is : /etc/xen/suseguest (contents) > > kernel = "/boot/vmlinuz-2.6.16-xen" > memory = 100 > name = "suseguest" > vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2'] > gateway = "192.168.1.1" > netmask = "255.255.255.0" > disk = ['file:/dev/hdc3,hdc3,w'] > root = "/dev/hdc3 rw" > > (As a variation to the above I also tried vif=[''] etc with no avail) > > On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of > errors > on module load that modules.dep file is not found etc .. However the boot > process continues uninterrupted and Iam finally provided the terminal > login > prompt. Iam also able to successfully login. > > After logging in, however an ifconfig reveals that the virtual if > 192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) .. > > I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with the > same > result. > > (To remove the modules.dep problem, I also copied the files from my FC5 > /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but networking > still does not work) > > The dom0 ifconfig reveals that the bridge and peth0 etc are all setup > properly. > All help to get this "networking issue" resolved is appreciated. > > Regards > Srini > > -- > _______________________________________________ > Check out the latest SMS services @ http://www.linuxmail.org > This allows you to send and receive SMS through your mailbox. > > Powered by Outblaze > > -- > 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 ssrini at linuxmail.org Mon Apr 17 15:48:08 2006 From: ssrini at linuxmail.org (Srinivasan S) Date: Mon, 17 Apr 2006 21:48:08 +0600 Subject: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5 Message-ID: <20060417154809.2D105437C0@ws5-1.us4.outblaze.com> I just tried .. Message is: FATAL Module xennet not found Any idea where I can get this from ? Cheers Srini > ----- Original Message ----- > From: "Todd Deshane" > To: "Srinivasan S" > Subject: Re: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5 > Date: Mon, 17 Apr 2006 09:54:10 -0400 > > > did you try: modprobe xennet > > On 4/17/06, Srinivasan S wrote: > > > > Hi Folks, > > > > I have FC5 installed with Xen 3.x from the official > > xensource.comtarball. The dom0 boots perfectly. I have a > > multiboot system with FC5 > > installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on > > /dev/hdc1. > > > > Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. (I > > had this working earlier in FC4 and Xen 2.x without issues) > > > > The configuration file I use is : /etc/xen/suseguest (contents) > > > > kernel = "/boot/vmlinuz-2.6.16-xen" > > memory = 100 > > name = "suseguest" > > vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2'] > > gateway = "192.168.1.1" > > netmask = "255.255.255.0" > > disk = ['file:/dev/hdc3,hdc3,w'] > > root = "/dev/hdc3 rw" > > > > (As a variation to the above I also tried vif=[''] etc with no avail) > > > > On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of > > errors > > on module load that modules.dep file is not found etc .. However the boot > > process continues uninterrupted and Iam finally provided the terminal > > login > > prompt. Iam also able to successfully login. > > > > After logging in, however an ifconfig reveals that the virtual if > > 192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) .. > > > > I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with the > > same > > result. > > > > (To remove the modules.dep problem, I also copied the files from my FC5 > > /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but networking > > still does not work) > > > > The dom0 ifconfig reveals that the bridge and peth0 etc are all setup > > properly. > > All help to get this "networking issue" resolved is appreciated. > > > > Regards > > Srini > > > > -- > > _______________________________________________ > > Check out the latest SMS services @ http://www.linuxmail.org > > This allows you to send and receive SMS through your mailbox. > > > > Powered by Outblaze > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze From deshantm at gmail.com Mon Apr 17 16:22:02 2006 From: deshantm at gmail.com (Todd Deshane) Date: Mon, 17 Apr 2006 12:22:02 -0400 Subject: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5 In-Reply-To: <20060417154809.2D105437C0@ws5-1.us4.outblaze.com> References: <20060417154809.2D105437C0@ws5-1.us4.outblaze.com> Message-ID: <1e16a9ed0604170922y4daa7f1fh903a44b52e39ebe@mail.gmail.com> It looks like you should be able to get this in: [directory of xen kerne]/drivers/xen/netfront/xennet.o On 4/17/06, Srinivasan S wrote: > > I just tried .. > > Message is: FATAL Module xennet not found > > Any idea where I can get this from ? > > Cheers > Srini > > ----- Original Message ----- > > From: "Todd Deshane" > > To: "Srinivasan S" > > Subject: Re: [Fedora-xen] FC5/Xen -> Running other OS as Guest within > FC5 > > Date: Mon, 17 Apr 2006 09:54:10 -0400 > > > > > > did you try: modprobe xennet > > > > On 4/17/06, Srinivasan S wrote: > > > > > > Hi Folks, > > > > > > I have FC5 installed with Xen 3.x from the official > > > xensource.comtarball. The dom0 boots perfectly. I have a > > > multiboot system with FC5 > > > installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on > > > /dev/hdc1. > > > > > > Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. > (I > > > had this working earlier in FC4 and Xen 2.x without issues) > > > > > > The configuration file I use is : /etc/xen/suseguest (contents) > > > > > > kernel = "/boot/vmlinuz-2.6.16-xen" > > > memory = 100 > > > name = "suseguest" > > > vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2'] > > > gateway = "192.168.1.1" > > > netmask = "255.255.255.0" > > > disk = ['file:/dev/hdc3,hdc3,w'] > > > root = "/dev/hdc3 rw" > > > > > > (As a variation to the above I also tried vif=[''] etc with no avail) > > > > > > On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of > > > errors > > > on module load that modules.dep file is not found etc .. However the > boot > > > process continues uninterrupted and Iam finally provided the terminal > > > login > > > prompt. Iam also able to successfully login. > > > > > > After logging in, however an ifconfig reveals that the virtual if > > > 192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) .. > > > > > > I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with > the > > > same > > > result. > > > > > > (To remove the modules.dep problem, I also copied the files from my > FC5 > > > /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but > networking > > > still does not work) > > > > > > The dom0 ifconfig reveals that the bridge and peth0 etc are all setup > > > properly. > > > All help to get this "networking issue" resolved is appreciated. > > > > > > Regards > > > Srini > > > > > > -- > > > _______________________________________________ > > > Check out the latest SMS services @ http://www.linuxmail.org > > > This allows you to send and receive SMS through your mailbox. > > > > > > Powered by Outblaze > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > -- > _______________________________________________ > Check out the latest SMS services @ http://www.linuxmail.org > This allows you to send and receive SMS through your mailbox. > > Powered by Outblaze > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tedkaz at optonline.net Tue Apr 18 08:26:24 2006 From: tedkaz at optonline.net (Ted Kaczmarek) Date: Tue, 18 Apr 2006 04:26:24 -0400 Subject: [Fedora-xen] xm save/migrate doesn't work In-Reply-To: References: Message-ID: <5B90E0EC-8CB8-492B-9AA5-491505329B68@optonline.net> On Apr 16, 2006, at 3:19 PM, George wrote: > Hi, > > I tried to use the "xm save" and "xm migrate" feature of Xen on FC5 > (all updates installed, kernel is 2.6.16-1.2080_FC5xen0) but a "xm > save" fails with the message (from the xend.log): > > -------------------------- > [2006-04-16 20:39:12 xend] DEBUG (XendCheckpoint:79) [xc_save]: > /usr/lib64/xen/bin/xc_save 10 17 27 0 0 0 > [2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:226) Unable to get > platform info.: 9 > [2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:98) Save failed on > domain fc5test (27). > Traceback (most recent call last): > File "/usr/lib64/python2.4/site-packages/xen/xend/ > XendCheckpoint.py", > line 92, in save > forkHelper(cmd, fd, saveInputHandler, False) > File "/usr/lib64/python2.4/site-packages/xen/xend/ > XendCheckpoint.py", > line 217, in forkHelper > raise XendError("%s failed" % string.join(cmd)) > XendError: /usr/lib64/xen/bin/xc_save 10 17 27 0 0 0 failed > -------------------------- > > The same problem exists with "xm migrate" because it calls a "xm > save". It looks like this problem is releated to FC5 and Xen because > on other (non FC5) platforms it works. > > Are there any workarounds for this problem? > > I have a similar issue, have you opened a bug up on this yet? Regards, Ted From dmessina at cise.ufl.edu Tue Apr 18 08:48:03 2006 From: dmessina at cise.ufl.edu (Daniel Messina) Date: Tue, 18 Apr 2006 04:48:03 -0400 Subject: [Fedora-xen] domU dhcp failure with default bridging Message-ID: <17db4c1e0604180148v63f71d9u666ce66cbafd9776@mail.gmail.com> I'm trying to walk through the FC5Xen Quickstart, but keep running into this problem, I've come accross the same problem on a x86_64 and seperate i386 machine. After anaconda launches, I reach the Configure TCP/IP screen. My home network is setup for DHCP. I can't proceed past here. Here's the output of brctl show: xenbr0 8000.feffffffffff yes peth0 vif0.0 vif1.0 I have uninstalled iptables and selinux is set to permissive, trying to duplicate conditions from previous posts to no avail. Thanks for any help! -------------- next part -------------- An HTML attachment was scrubbed... URL: From igeorgex at googlemail.com Tue Apr 18 12:26:50 2006 From: igeorgex at googlemail.com (George) Date: Tue, 18 Apr 2006 14:26:50 +0200 Subject: [Fedora-xen] xm save/migrate doesn't work In-Reply-To: <5B90E0EC-8CB8-492B-9AA5-491505329B68@optonline.net> References: <5B90E0EC-8CB8-492B-9AA5-491505329B68@optonline.net> Message-ID: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188361 is exactly the problem I have, I tried the patch from the Bug Comments and at least the "xm save" works now but I still have trouble with the "xm migrate" (kernel panic). On 4/18/06, Ted Kaczmarek wrote: > > I have a similar issue, have you opened a bug up on this yet? > > > Regards, > > Ted > From dmessina at cise.ufl.edu Tue Apr 18 13:41:16 2006 From: dmessina at cise.ufl.edu (Daniel Messina) Date: Tue, 18 Apr 2006 09:41:16 -0400 Subject: [Fedora-xen] Re: domU dhcp failure with default bridging In-Reply-To: <17db4c1e0604180148v63f71d9u666ce66cbafd9776@mail.gmail.com> References: <17db4c1e0604180148v63f71d9u666ce66cbafd9776@mail.gmail.com> Message-ID: <17db4c1e0604180641q3e5003a9h1067ce3f8f3aea4f@mail.gmail.com> I added netplugd into my startup services and rebooted. Not sure how, but peth0 and vif0.0 disappeared, leaving eth0 and vif1.0. brctrl showed a setup resembling a previous post on this same topic. xenbr0 ... vif1.0 I added eth0 to the bridge. The result is a working domU, but at the expense of dom0's network connection, which ceased at this point. Currently I am using a seperate machine to vnc into the origninal, and will try to get vif0.0 to reappear On 4/18/06, Daniel Messina wrote: > > I'm trying to walk through the FC5Xen Quickstart, but keep running into > this problem, > > I've come accross the same problem on a x86_64 and seperate i386 machine. > > After anaconda launches, I reach the Configure TCP/IP screen. My home > network is setup for DHCP. > > I can't proceed past here. > > Here's the output of brctl show: > xenbr0 8000.feffffffffff yes peth0 > vif0.0 > vif1.0 > > I have uninstalled iptables and selinux is set to permissive, trying to > duplicate conditions from previous posts to no avail. > > Thanks for any help! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmortimer at bluechiptechnology.co.uk Tue Apr 18 14:22:13 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Tue, 18 Apr 2006 15:22:13 +0100 Subject: [Fedora-xen] Running FC4 on FC5 Message-ID: <000d01c662f3$7ce11aa0$5f00000a@rmortimer> I am attempting to run an FC4 image on an FC5 machine I have prepped the image as per the FC4 quick start my xen config is as follows kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU" memory = 100 name = "vm01" vcpus = 1 vif= ['mac=FE:FD:25:63:74:49'] disk = [ 'file:/root/VM/fedora.img,sda1,w' ] root = "/dev/sda1" extra = "ro selinux=0 3" All I get is # xm create vm01 Using config file "vm01". Error: Error creating domain: (22, 'Invalid argument') Has anyone got a simple 1 NIC guest config for FC4 on FC5 I see that the new FC5 uses An init image as part of the boot A python based boot loader and a python based install script Is there any way to hack this lot to do an install like the FC5/FC5 one? How are the init images built? Will the new installer do other guest OS's in the future? Robert From raul.saura at gmail.com Tue Apr 18 14:24:12 2006 From: raul.saura at gmail.com (Raul Saura) Date: Tue, 18 Apr 2006 16:24:12 +0200 Subject: [Fedora-xen] Re: domU dhcp failure with default bridging In-Reply-To: <17db4c1e0604180641q3e5003a9h1067ce3f8f3aea4f@mail.gmail.com> References: <17db4c1e0604180148v63f71d9u666ce66cbafd9776@mail.gmail.com> <17db4c1e0604180641q3e5003a9h1067ce3f8f3aea4f@mail.gmail.com> Message-ID: Daniel, I had exactly the same problem. Once I activated netplugd peth0 vanished, and didn't come back, even after netplugd was disabled. Have you tried to disable selinux via boot param "selinux=0"? This seemed to help some other users. hope this helps. Ra?l. On 4/18/06, Daniel Messina wrote: > > I added netplugd into my startup services and rebooted. Not sure how, but > peth0 and vif0.0 disappeared, leaving eth0 and vif1.0. > > brctrl showed a setup resembling a previous post on this same topic. > > xenbr0 ... vif1.0 > > I added eth0 to the bridge. The result is a working domU, but at the > expense of dom0's network connection, which ceased at this point. > > Currently I am using a seperate machine to vnc into the origninal, and > will try to get vif0.0 to reappear > > > On 4/18/06, Daniel Messina wrote: > > > > I'm trying to walk through the FC5Xen Quickstart, but keep running into > > this problem, > > > > I've come accross the same problem on a x86_64 and seperate i386 > > machine. > > > > After anaconda launches, I reach the Configure TCP/IP screen. My home > > network is setup for DHCP. > > > > I can't proceed past here. > > > > Here's the output of brctl show: > > xenbr0 8000.feffffffffff yes peth0 > > vif0.0 > > vif1.0 > > > > I have uninstalled iptables and selinux is set to permissive, trying to > > duplicate conditions from previous posts to no avail. > > > > Thanks for any help! > > > > > > > -- > 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 matbayer.web at web.de Tue Apr 18 15:43:37 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Tue, 18 Apr 2006 17:43:37 +0200 Subject: [Fedora-xen] monitoring tools/ statistical information about Xen Message-ID: <279158616@web.de> Hi, i'd like to do some performance tests as well as collect statistical information about usage of my xen system. i know there are the 'native' tools like 'xm' commands or some native linux commands like vmstat,top... xentop gives very good information but does somebody know how to track xentop output over time (days) to a file ? what i want to achive is collecting data about the usage of each DomU, network statistics, performance statistics of the DomU's, CPU/memory usage of each DomU as well as from Dom0. any recommendations about tools ? any ideas about the xentop/top output catching ? regards, Matthias SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] -------------- next part -------------- An HTML attachment was scrubbed... URL: From twendt at online.de Tue Apr 18 18:01:56 2006 From: twendt at online.de (Timo Wendt) Date: Tue, 18 Apr 2006 20:01:56 +0200 Subject: [Fedora-xen] PCI devices in domU Message-ID: Hi, I am trying to use PCI devices in guests. My grub.conf includes the following: title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,4) kernel /xen.gz-2.6.16-1.2080_FC5 module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ VolGroup00/LogVol00 rhgb pciback.hide=(02:09.0)(02:0e.0) module /initrd-2.6.16-1.2080_FC5xen0.img It doesn't work though: Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb pciback.hide=(02:09.0)(02:0e.0) Unknown boot option `pciback.hide=(02:09.0)(02:0e.0)': ignoring Is something not compiled into the kernel that is needed here? I would appreciate any help. Timo From kzak at redhat.com Tue Apr 18 20:10:59 2006 From: kzak at redhat.com (Karel Zak) Date: Tue, 18 Apr 2006 22:10:59 +0200 Subject: [Fedora-xen] monitoring tools/ statistical information about Xen In-Reply-To: <279158616@web.de> References: <279158616@web.de> Message-ID: <20060418201059.GK12297@petra.dvoda.cz> On Tue, Apr 18, 2006 at 05:43:37PM +0200, Matthias Bayer wrote: > > i'd like to do some performance tests as well as collect statistical > information about usage of my xen system. > > i know there are the 'native' tools like 'xm' commands or some > native linux commands like vmstat,top... There is the 'virsh' too. (Now probably in FC5 only.) > xentop gives very good information but does somebody know how to > track xentop output over time (days) to a file ? > > what i want to achive is collecting data about the usage of each > DomU, network statistics, performance statistics of the DomU's, > CPU/memory usage of each DomU as well as from Dom0. > > any recommendations about tools ? any ideas about the xentop/top > output catching ? See libvirt.org -- there's python binding for libvirt, so you can write a script which will collect some statistics. I think that you can work with virtual domains like with normal physical machines. It means you can try collect data about it by some monitor tools like nagios or whatever. Karel -- Karel Zak From kzak at redhat.com Tue Apr 18 20:15:18 2006 From: kzak at redhat.com (Karel Zak) Date: Tue, 18 Apr 2006 22:15:18 +0200 Subject: [Fedora-xen] monitoring tools/ statistical information about Xen In-Reply-To: <279158616@web.de> References: <279158616@web.de> Message-ID: <20060418201518.GL12297@petra.dvoda.cz> Se also http://skaya.enix.org/wiki/XenStats Karel On Tue, Apr 18, 2006 at 05:43:37PM +0200, Matthias Bayer wrote: > > > Hi, > > i'd like to do some performance tests as well as collect statistical information about usage of my xen system. > > i know there are the 'native' tools like 'xm' commands or some native linux commands like vmstat,top... > > xentop gives very good information but does somebody know how to track xentop output over time (days) to a file ? > > what i want to achive is collecting data about the usage of each DomU, network statistics, performance statistics of the DomU's, CPU/memory usage of each DomU as well as from Dom0. > > any recommendations about tools ? any ideas about the xentop/top output catching ? > > regards, > > Matthias > > > > > > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Karel Zak From igeorgex at googlemail.com Tue Apr 18 22:48:08 2006 From: igeorgex at googlemail.com (George) Date: Wed, 19 Apr 2006 00:48:08 +0200 Subject: [Fedora-xen] PCI devices in domU In-Reply-To: References: Message-ID: I have the same problem and found a bug report in bugzilla https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188771 It looks like the pciback.hide option is missing in FC5. On 4/18/06, Timo Wendt wrote: > Hi, > > I am trying to use PCI devices in guests. My grub.conf includes the > following: > > title Fedora Core (2.6.16-1.2080_FC5xen0) > root (hd0,4) > kernel /xen.gz-2.6.16-1.2080_FC5 > module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ > VolGroup00/LogVol00 rhgb pciback.hide=(02:09.0)(02:0e.0) > module /initrd-2.6.16-1.2080_FC5xen0.img > > It doesn't work though: > > Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb > pciback.hide=(02:09.0)(02:0e.0) > Unknown boot option `pciback.hide=(02:09.0)(02:0e.0)': ignoring > > Is something not compiled into the kernel that is needed here? > > I would appreciate any help. > > Timo From dmessina at cise.ufl.edu Wed Apr 19 03:02:30 2006 From: dmessina at cise.ufl.edu (Daniel Messina) Date: Tue, 18 Apr 2006 23:02:30 -0400 Subject: [Fedora-xen] Re: domU dhcp failure with default bridging In-Reply-To: <17db4c1e0604180641q3e5003a9h1067ce3f8f3aea4f@mail.gmail.com> References: <17db4c1e0604180148v63f71d9u666ce66cbafd9776@mail.gmail.com> <17db4c1e0604180641q3e5003a9h1067ce3f8f3aea4f@mail.gmail.com> Message-ID: <17db4c1e0604182002v7afdeaeek39cdcbbfba54d52d@mail.gmail.com> I have replicated the same situation on a second machine. For those it may help here goes. FC5 quickinstall Loadis the python installer without a hitch, however, when it tries to connect to my dhcp client, it cannot connect. brctrl show -> says that xenbr0 connects peth0, vif0.0, and vif1.0. Adding the services, Netmanager and Netmanager Dispatcher, then either restarting networking, or rebooting (not sure which i did) causes the following changes brctrl show -> says that xenbr0 connects only vif1.0 ifconfig only eth0, lo, and xenbr0 are listed The following will add networking to your domU, but remove it from dom0 brctrl addif xenbr0 eth0 I'd like for networking to still work in both dom0, and dom1, but for now I'll be happy I can proceed with installation. On 4/18/06, Daniel Messina wrote: > > I added netplugd into my startup services and rebooted. Not sure how, but > peth0 and vif0.0 disappeared, leaving eth0 and vif1.0. > > brctrl showed a setup resembling a previous post on this same topic. > > xenbr0 ... vif1.0 > > I added eth0 to the bridge. The result is a working domU, but at the > expense of dom0's network connection, which ceased at this point. > > Currently I am using a seperate machine to vnc into the origninal, and > will try to get vif0.0 to reappear > > > On 4/18/06, Daniel Messina wrote: > > > > I'm trying to walk through the FC5Xen Quickstart, but keep running into > > this problem, > > > > I've come accross the same problem on a x86_64 and seperate i386 > > machine. > > > > After anaconda launches, I reach the Configure TCP/IP screen. My home > > network is setup for DHCP. > > > > I can't proceed past here. > > > > Here's the output of brctl show: > > xenbr0 8000.feffffffffff yes peth0 > > vif0.0 > > vif1.0 > > > > I have uninstalled iptables and selinux is set to permissive, trying to > > duplicate conditions from previous posts to no avail. > > > > Thanks for any help! > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssrini at linuxmail.org Wed Apr 19 04:49:15 2006 From: ssrini at linuxmail.org (Srinivasan S) Date: Wed, 19 Apr 2006 10:49:15 +0600 Subject: [Fedora-xen] General question on running guests in FC5/Xen Message-ID: <20060419044915.AC7517B5EF@ws5-10.us4.outblaze.com> Hi First of all apologies for making all of you read this long email. I have posted to multiple lists to get my setup running. Inspite of enthusiastic help I have not got it running yet and hence this fundamental doubt. I had a system running FC4 and Xen 2.x. The same system had normal installations of Suse and Ubuntu. I had a running setup wherin I started xen0 in FC4 and was able to run the installed Suse and Ubuntu as guests within FC4. (This worked perfectly and I was able to connect to the guests using both RealVNC and FreeNX.) I have now upgraded to FC and have been attempting to get the same setup running. I first tried with the official Xen tarballs. Not successful, I then tried yesterday with the FC5 xen kernels. No success. The problem in both cases is that Suse and Ubuntu guests load but virtual networking does not work. Only lo interface is up. On the main FC5 xen0 domain, I am able to see vifx.x being added as and when a guest boots up, but the guest itself is without an interface. Various searches on Google finally got me one hint on loading module xennet (for FC5) which I did in modprobe.conf. Same result. Search on web got me guides to load guests from images, starting guest installs from fedora, debian etc but could not find any info on running already installed linux distros within Xen. The closet was in the xen manual which explains how to make an image of an installed linux distro and then running the image within xen. Question: Is what Iam trying to achieve possibly with Xen 3.x (since it worked with 2.x) ? If yes can anyone help ? My guest config file is a very simple one : kernel = << Tried both the xen kernel and the FC5 xenU kernel >> memory = 100 name = "suseguest" vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2'] Also tried vif= [''] gateway = "192.168.1.1" netmask = "255.255.255.0" disk = ['phy:hdc3,hdc3,w'] Also tried disk = ['file:/dev/hdc3,hdc3,w'] root = "/dev/hdc3 rw" Please note that OpenSUSE is installed on /dev/hdc3 All help is appreciated in resolving this. Thanks and Best Regards Srini -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze From rmortimer at bluechiptechnology.co.uk Wed Apr 19 09:06:41 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Wed, 19 Apr 2006 10:06:41 +0100 Subject: [Fedora-xen] Running FC4 on FC5 In-Reply-To: Message-ID: <002601c66390$9370ee10$5f00000a@rmortimer> Dear Robert First of all, I've had the same questions and problems as you have now. This style of none documentation by the fedora team is just a shame for the whole open source community! Probably Jeremy Katz is too busy by meeting his new board members friends, so that he has no more time to write just a little documentation with explanations, not just a unusable mini mini howto. What the big problem is behind the FC5 and Xen implementation is, that the xen guys at fedora have no idea what SELinux is doing. So, finally they made an implementation of xen and SELinux that is not usable. If you don't want to spend two weeks configuring your SELinux, you have to decide, if you use in future SELinux or Xen (By the way, the same issues you have with httpd and SELinux). So my personal proposal is, that you just disable SELinux wherever you find it on your FC5 installation. After disabling SELinux (you have to reboot so that everything works fine, => Oh I like this old nice M$ Win95 style of system management) you can use your xen config as you posted in your mail. With the xenguest-install.py script you can't install FC4 or another distribution, because the FC5 guys made an adaptation of the anaconda system installer. By the way, this is a nice feature, because you can now kickstart your FC5 installation. If you want to install a new non FC5 guest, do it in the old style. Create your devices with LVM and perform a yum groupinstall with --installdir=yourdevice. The Point is I have done this I have FC4 images. I have copied the fc4 domU kernel and modules to the Dom0 and still I can not find a config that boots As you can see, Fedora Core 5 is a typical example for bad IT Management. They tried to do a lot of thing in a short time. So several teams worked on different things and now, nothing really fits together. The whole implementation of the SELinux is a disaster. So for professional use, you have to go back to Fedora Core 4. Also because the oracle stuff is not working with the new glibc (it's not possible to start the listener... :-(). I by myself have to use FC5, because I need to kickstart my xen installation and need apache 2.2. If you don't need those features, use CentOS or the original RHES. Hope I gave you the right hints. bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 "Robert Mortimer" Sent by: fedora-xen-bounces at redhat.com 04/18/2006 04:22 PM To cc Subject [Fedora-xen] Running FC4 on FC5 I am attempting to run an FC4 image on an FC5 machine I have prepped the image as per the FC4 quick start my xen config is as follows kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU" memory = 100 name = "vm01" vcpus = 1 vif= ['mac=FE:FD:25:63:74:49'] disk = [ 'file:/root/VM/fedora.img,sda1,w' ] root = "/dev/sda1" extra = "ro selinux=0 3" All I get is # xm create vm01 Using config file "vm01". Error: Error creating domain: (22, 'Invalid argument') Has anyone got a simple 1 NIC guest config for FC4 on FC5 I see that the new FC5 uses An init image as part of the boot A python based boot loader and a python based install script Is there any way to hack this lot to do an install like the FC5/FC5 one? How are the init images built? Will the new installer do other guest OS's in the future? Robert -- 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 matbayer.web at web.de Wed Apr 19 09:32:38 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 19 Apr 2006 11:32:38 +0200 Subject: =?iso-8859-15?Q?Re:_[Fedora-xen]_monitoring_tools/_statistical_informa?= =?iso-8859-15?Q?tion_about_Xen?= Message-ID: <279708792@web.de> Thanks Karel for these links, i will look into them soon ! Matthias > -----Urspr?ngliche Nachricht----- > Von: Karel Zak > Gesendet: 18.04.06 22:15:25 > An: Matthias Bayer > CC: fedora-xen at redhat.com > Betreff: Re: [Fedora-xen] monitoring tools/ statistical information about Xen > > Se also http://skaya.enix.org/wiki/XenStats > > Karel > > On Tue, Apr 18, 2006 at 05:43:37PM +0200, Matthias Bayer wrote: > > > > > > Hi, > > > > i'd like to do some performance tests as well as collect statistical information about usage of my xen system. > > > > i know there are the 'native' tools like 'xm' commands or some native linux commands like vmstat,top... > > > > xentop gives very good information but does somebody know how to track xentop output over time (days) to a file ? > > > > what i want to achive is collecting data about the usage of each DomU, network statistics, performance statistics of the DomU's, CPU/memory usage of each DomU as well as from Dom0. > > > > any recommendations about tools ? any ideas about the xentop/top output catching ? > > > > regards, > > > > Matthias > > > > > > > > > > > > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > > kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192] > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > -- > Karel Zak _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From gregor.pirnaver at email.si Wed Apr 19 12:40:45 2006 From: gregor.pirnaver at email.si (Gregor Pirnaver) Date: Wed, 19 Apr 2006 14:40:45 +0200 Subject: [Fedora-xen] Device 2049 (vbd) could not be connected. Message-ID: <20060419124058.20EFF8B956@www1.email.si> DomainU starts only the first time. After running "xm shutdown ..." I get this error: # xm create webserver Using config file "webserveer". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. How can I fix this? ____________________ http://www.email.si/ From rmortimer at bluechiptechnology.co.uk Wed Apr 19 13:41:25 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Wed, 19 Apr 2006 14:41:25 +0100 Subject: [Fedora-xen] Running FC4 on FC5 In-Reply-To: Message-ID: <000201c663b6$f3f930f0$5f00000a@rmortimer> I have the boot image (FC4 domU) in /boot And the modules in the modules dir I also have FC4 domU installed on the FC4 Guest -----Original Message----- From: Philipp J?ggi [mailto:philipp.jaggi at snct.lu] Sent: 19 April 2006 11:19 To: Robert Mortimer Subject: RE: [Fedora-xen] Running FC4 on FC5 You've got the FC4 Xen kernel installed in your dom0? bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi at snct.lu "Robert Mortimer" 04/19/2006 11:48 AM To Philipp J?ggi cc Subject RE: [Fedora-xen] Running FC4 on FC5 Yes -----Original Message----- From: Philipp J?ggi [mailto:philipp.jaggi at snct.lu] Sent: 19 April 2006 10:43 To: Robert Mortimer Subject: RE: [Fedora-xen] Running FC4 on FC5 You disabled SELinux and rebooted the machine? bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi at snct.lu "Robert Mortimer" Sent by: fedora-xen-bounces at redhat.com 04/19/2006 11:06 AM To Philipp J?ggi cc fedora-xen-bounces at redhat.com, fedora-xen at redhat.com Subject RE: [Fedora-xen] Running FC4 on FC5 Dear Robert First of all, I've had the same questions and problems as you have now. This style of none documentation by the fedora team is just a shame for the whole open source community! Probably Jeremy Katz is too busy by meeting his new board members friends, so that he has no more time to write just a little documentation with explanations, not just a unusable mini mini howto. What the big problem is behind the FC5 and Xen implementation is, that the xen guys at fedora have no idea what SELinux is doing. So, finally they made an implementation of xen and SELinux that is not usable. If you don't want to spend two weeks configuring your SELinux, you have to decide, if you use in future SELinux or Xen (By the way, the same issues you have with httpd and SELinux). So my personal proposal is, that you just disable SELinux wherever you find it on your FC5 installation. After disabling SELinux (you have to reboot so that everything works fine, => Oh I like this old nice M$ Win95 style of system management) you can use your xen config as you posted in your mail. With the xenguest-install.py script you can't install FC4 or another distribution, because the FC5 guys made an adaptation of the anaconda system installer. By the way, this is a nice feature, because you can now kickstart your FC5 installation. If you want to install a new non FC5 guest, do it in the old style. Create your devices with LVM and perform a yum groupinstall with --installdir=yourdevice. The Point is I have done this I have FC4 images. I have copied the fc4 domU kernel and modules to the Dom0 and still I can not find a config that boots As you can see, Fedora Core 5 is a typical example for bad IT Management. They tried to do a lot of thing in a short time. So several teams worked on different things and now, nothing really fits together. The whole implementation of the SELinux is a disaster. So for professional use, you have to go back to Fedora Core 4. Also because the oracle stuff is not working with the new glibc (it's not possible to start the listener... :-(). I by myself have to use FC5, because I need to kickstart my xen installation and need apache 2.2. If you don't need those features, use CentOS or the original RHES. Hope I gave you the right hints. bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 "Robert Mortimer" Sent by: fedora-xen-bounces at redhat.com 04/18/2006 04:22 PM To cc Subject [Fedora-xen] Running FC4 on FC5 I am attempting to run an FC4 image on an FC5 machine I have prepped the image as per the FC4 quick start my xen config is as follows kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU" memory = 100 name = "vm01" vcpus = 1 vif= ['mac=FE:FD:25:63:74:49'] disk = [ 'file:/root/VM/fedora.img,sda1,w' ] root = "/dev/sda1" extra = "ro selinux=0 3" All I get is # xm create vm01 Using config file "vm01". Error: Error creating domain: (22, 'Invalid argument') Has anyone got a simple 1 NIC guest config for FC4 on FC5 I see that the new FC5 uses An init image as part of the boot A python based boot loader and a python based install script Is there any way to hack this lot to do an install like the FC5/FC5 one? How are the init images built? Will the new installer do other guest OS's in the future? Robert -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- 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 matbayer.web at web.de Wed Apr 19 15:07:21 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Wed, 19 Apr 2006 17:07:21 +0200 Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 Message-ID: <279960444@web.de> Hi, i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and kernel-xen0-2.6.16-1.2080_FC5. i have several paravirtualized and fully virtualized images from another xen system which was 'normal' 32 bit installation (same version). running the fully virtualized DomU images created under 32 bit Dom0 works fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to 'device_model = '/usr/lib64/xen/bin/qemu-dm'. now i want to start my formerly created paravirtualized DomU systems (here one FC5 system) under the new 64-bit system but i get the following error when starting: [root at tuxine xen]# xm create FC5_messer Using config file "FC5_messer". Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) kernel: /vmlinuz-2.6.16-1.2080_FC5xenU initrd: /initrd-2.6.16-1.2080_FC5xenU.img Error: Error creating domain: (22, 'Invalid argument') attached are the xend.log and xend-debug.log files. hope somebody can give me a hint what's wrong. regards, Matthias _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: text/x-log Size: 4277 bytes Desc: not available URL: From rafiq.ahamed at hp.com Thu Apr 20 05:34:42 2006 From: rafiq.ahamed at hp.com (Ahamed K, Rafiq (HP)) Date: Thu, 20 Apr 2006 01:34:42 -0400 Subject: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2 Message-ID: <0B5B70C578796045A2F555952837914C018DD231@tayexc13.americas.cpqcorp.net> I can see that Windows Loads in VM and when I run in safe mode it reaches until loading multi(0)\disk(0)\rdisk(0)\partition(1)\Windows\system32\drivers\Mup.sys After this it hangs.Attached is the qemulog. Note : These VM's are running out of a complete disk (/dev/sdb), which has working installation of Windows on it! I am running FC5 along with Xen 3.0.2 (tried unstable too) on Intel XEON VT-x server! Any help would be great! Rafiq -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu-dm.5858.log Type: application/octet-stream Size: 1596 bytes Desc: qemu-dm.5858.log URL: From yongkang.you at intel.com Thu Apr 20 07:58:31 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 20 Apr 2006 15:58:31 +0800 Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A21A0@pdsmsx402.ccr.corp.intel.com> Hi Matthias, The first step your trying is okay: either IA32 or X86_64(EM64T) full-virtualization VMX can run in X86_64 Host. But IA32 paravirtulization XenU can only run in IA32 Xen0. :) Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >Sent: 2006?4?19? 23:07 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > >Hi, > >i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and >kernel-xen0-2.6.16-1.2080_FC5. >i have several paravirtualized and fully virtualized images from another xen >system which was 'normal' 32 bit installation (same version). > >running the fully virtualized DomU images created under 32 bit Dom0 works >fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to >'device_model = '/usr/lib64/xen/bin/qemu-dm'. >now i want to start my formerly created paravirtualized DomU systems (here >one FC5 system) under the new 64-bit system but i get the following error >when starting: > >[root at tuxine xen]# xm create FC5_messer >Using config file "FC5_messer". >Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) > kernel: /vmlinuz-2.6.16-1.2080_FC5xenU > initrd: /initrd-2.6.16-1.2080_FC5xenU.img >Error: Error creating domain: (22, 'Invalid argument') > >attached are the xend.log and xend-debug.log files. > >hope somebody can give me a hint what's wrong. > >regards, >Matthias >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From matbayer.web at web.de Thu Apr 20 09:09:23 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Thu, 20 Apr 2006 11:09:23 +0200 Subject: =?iso-8859-15?Q?RE:_[Fedora-xen]_running_32-bit_paravirtualized_DomU_u?= =?iso-8859-15?Q?nder_64-bit_Dom0?= Message-ID: <280665605@web.de> that's what i thought but i was not sure :-) ok, thanks for this info yonkang ! Matthias > -----Urspr?ngliche Nachricht----- > Von: "You, Yongkang" > Gesendet: 20.04.06 09:59:52 > An: > Betreff: RE: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > Hi Matthias, > > The first step your trying is okay: either IA32 or X86_64(EM64T) full-virtualization VMX can run in X86_64 Host. > > But IA32 paravirtulization XenU can only run in IA32 Xen0. :) > > Best Regards, > Yongkang (Kangkang) ???? > > >-----Original Message----- > >From: fedora-xen-bounces at redhat.com > >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer > >Sent: 2006??4??19?? 23:07 > >To: fedora-xen at redhat.com > >Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > > > >Hi, > > > >i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and > >kernel-xen0-2.6.16-1.2080_FC5. > >i have several paravirtualized and fully virtualized images from another xen > >system which was 'normal' 32 bit installation (same version). > > > >running the fully virtualized DomU images created under 32 bit Dom0 works > >fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to > >'device_model = '/usr/lib64/xen/bin/qemu-dm'. > >now i want to start my formerly created paravirtualized DomU systems (here > >one FC5 system) under the new 64-bit system but i get the following error > >when starting: > > > >[root at tuxine xen]# xm create FC5_messer > >Using config file "FC5_messer". > >Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) > > kernel: /vmlinuz-2.6.16-1.2080_FC5xenU > > initrd: /initrd-2.6.16-1.2080_FC5xenU.img > >Error: Error creating domain: (22, 'Invalid argument') > > > >attached are the xend.log and xend-debug.log files. > > > >hope somebody can give me a hint what's wrong. > > > >regards, > >Matthias > >______________________________________________________________ > >_ > >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From yongkang.you at intel.com Thu Apr 20 13:23:45 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 20 Apr 2006 21:23:45 +0800 Subject: [Fedora-xen] Device 2049 (vbd) could not be connected. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A21A3@pdsmsx402.ccr.corp.intel.com> I am not sure if it is related with loop device is occupied. Could you try "losetup /dev/loop0" to see if loop0 isn't released. If not, release it manually by "losetup -d /dev/loop0". Or try to change the disk config file to: disk = [ 'phy:/dev/loop0,...' ] I don't know if this bug is fixed by latest xen. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Gregor Pirnaver >Sent: 2006?4?19? 20:41 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Device 2049 (vbd) could not be connected. > >DomainU starts only the first time. After running "xm shutdown ..." I get this >error: > > ># xm create webserver >Using config file "webserveer". >Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. > > >How can I fix this? > >____________________ >http://www.email.si/ > > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From Axel.Thimm at ATrpms.net Thu Apr 20 12:15:36 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 20 Apr 2006 14:15:36 +0200 Subject: [Fedora-xen] Re: initscripts, xen and bonding In-Reply-To: <20060224231311.GP21359@neu.nirvana> References: <20060224231311.GP21359@neu.nirvana> Message-ID: <20060420121536.GJ4113@neu.nirvana> Hi, I'm retrying to get bonding and xen working with FC5: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189473 The summary is that o xend at boot time does not attach anything to xenbr, the network is other than the added broken xenbr unaltered. So at least booting into kernel-xen0 doesn't hook you off the wire anymore (as it was with FC5t3) o after calling xend restart the bridge is almost properly set up, only the slaves of the bond interface get lost in the process Anyone know how to fix/workaround these issues? Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tony.clark at rsp.com.au Thu Apr 20 14:05:24 2006 From: tony.clark at rsp.com.au (Tony Clark) Date: Thu, 20 Apr 2006 23:35:24 +0930 Subject: [Fedora-xen] FC5 - serial console - no characters received by host? Message-ID: <018FB09B-473B-482B-9974-2B79F421B34C@rsp.com.au> Hi there, I've been working with the FC5 Xen stuff for the past few weeks after trawling many options for building a redundant server farm; It's a great build and congratulations to all who put this together. I have a little issue with my serial console which is putting hte brakes on deployment though: I want to use the serial console on com2 (the default on the Intel mainboard I use) to give me the grub console, Xen console and Linux consoles. I've had this working fine on previous releases from SuSE and others and on the current hardware. When happens at the moment is that the machine boots, gives me the grub menu, where I can choose my boot system (so it's hearing my keystrokes) but once it proceeds into the Xen and ultimately Linux, it doesn't want to hear keystrokes from me any more: I can't CTRL-A (x3) and get the Xen console, nor the linux console which is configured in /etc/inittab. I see the boot messages go past and get a login prompt, but no keystrokes get through or can control the machine. It's making it tricky to send the box to co-lo as I can't get serial control if I take down the network, or Hypervisor control to reboot Dom0. My rpms are: kernel-xen0-2.6.16-1.2080_FC5 xen-3.0.1-4 and my grub.conf is: default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console # title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ VolGroup00/LogVol00 rhgb selinux=0 module /initrd-2.6.16-1.2080_FC5xen0.img I'd appreciate any guidance on silly things I may have done here; I'm banging my head on this one. Many thanks, Tony tony clark director - tony.clark at rsp.com.au --------------------------------------------------------------- rising sun pictures - www.rsp.com.au redefining visual effects delivery --------------------------------------------------------------- address level 1 / 133 gouger street adelaide south australia 5000 --------------------------------------------------------------- adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 sydney ph +61 2 9338 6400 fax +61 2 9338 6401 --------------------------------------------------------------- rising sun research - http://research.rsp.com.au --------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mike.Kent at indystar.com Thu Apr 20 14:14:07 2006 From: Mike.Kent at indystar.com (Mike.Kent at indystar.com) Date: Thu, 20 Apr 2006 10:14:07 -0400 Subject: [Fedora-xen] Re: initscripts, xen and bonding In-Reply-To: <20060420121536.GJ4113@neu.nirvana> Message-ID: I'm using Fedora 4 and wound up fixing it manually for now, if we decide to keep xen we'll write a boot script to do it. Basically, both bond0 and pbond0 must be active at the same time, so leave your bond0 setup as is. Copy /etc/sysconfig/network-scripts/ifcfg-bond0 to ifcfg-pbond0 and rename the Device value (not sure this step is necessary). Reboot and on bootup, do: sudo ifconfig pbond0 (IP address) network (255.255.255.x) broadcast (your address) sudo ifenslave pbond0 eth0 sudo ifenslave pbond0 eth1 The 3 addresses above are the same as used by bond0. Axel Thimm Sent by: fedora-xen-bounces at redhat.com 04/20/06 08:15 AM Please respond to fedora-xen at redhat.com To fedora-xen at redhat.com cc Subject [Fedora-xen] Re: initscripts, xen and bonding Hi, I'm retrying to get bonding and xen working with FC5: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189473 The summary is that o xend at boot time does not attach anything to xenbr, the network is other than the added broken xenbr unaltered. So at least booting into kernel-xen0 doesn't hook you off the wire anymore (as it was with FC5t3) o after calling xend restart the bridge is almost properly set up, only the slaves of the bond interface get lost in the process Anyone know how to fix/workaround these issues? Thanks! -- Axel.Thimm at ATrpms.net -- 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: att24w91.dat Type: application/octet-stream Size: 196 bytes Desc: not available URL: From yongkang.you at intel.com Thu Apr 20 14:14:02 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 20 Apr 2006 22:14:02 +0800 Subject: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2 Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A21A4@pdsmsx402.ccr.corp.intel.com> Hi Rafig, So you have tried Windows 2003 and 2000? And they all hang with the same phenomena? Did you try to get the serial output when VMX hang? The qemu-log seemed okay. Could you tell more information such as Xen0 memory size and the VMX config you used? These could help developers to shoot the bug. And you can also report bugs to Xen directly. :-) I didn?t try them before. But I am sure someone has successful experience of creating Windows XP VMX with Xen 3.0.2/ Best Regards, Yongkang (Kangkang) ?? ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ahamed K, Rafiq (HP) Sent: 2006?4?20? 13:35 To: fedora-xen at redhat.com Subject: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2 I can see that Windows Loads in VM and when I run in safe mode it reaches until loading multi(0)\disk(0)\rdisk(0)\partition(1)\Windows\system32\drivers\Mup.sys After this it hangs.Attached is the qemulog. Note : These VM's are running out of a complete disk (/dev/sdb), which has working installation of Windows on it! I am running FC5 along with Xen 3.0.2 (tried unstable too) on Intel XEON VT-x server! Any help would be great! Rafiq -------------- next part -------------- An HTML attachment was scrubbed... URL: From yongkang.you at intel.com Thu Apr 20 14:24:40 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 20 Apr 2006 22:24:40 +0800 Subject: [Fedora-xen] FC5 - serial console - no characters received by host? Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A21A5@pdsmsx402.ccr.corp.intel.com> Hi Tony, There is a bug about this issue. Please have a look at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 If want to use serial port input, I have to disable SMP. Following is a workable grub config to enable serial out input, but the kernel will be UP. I am not sure if there is any better solution. title Fedora Core 5 root (hd0,0) kernel /boot/xen.gz-xxx_FC5 dom0_mem=262144 com0=115200,8n1 apci=off module /boot/vmlinuz-xxx_FC5hypervisor ro root=/dev/sda1 console=ttyS0 console=tty0 pci=noapci module /boot/initrd-xxx_FC5hypervisor.img Best Regards, Yongkang (Kangkang) ?? ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Tony Clark Sent: 2006?4?20? 22:05 To: fedora-xen at redhat.com Subject: [Fedora-xen] FC5 - serial console - no characters received by host? Hi there, I've been working with the FC5 Xen stuff for the past few weeks after trawling many options for building a redundant server farm; It's a great build and congratulations to all who put this together. I have a little issue with my serial console which is putting hte brakes on deployment though: I want to use the serial console on com2 (the default on the Intel mainboard I use) to give me the grub console, Xen console and Linux consoles. I've had this working fine on previous releases from SuSE and others and on the current hardware. When happens at the moment is that the machine boots, gives me the grub menu, where I can choose my boot system (so it's hearing my keystrokes) but once it proceeds into the Xen and ultimately Linux, it doesn't want to hear keystrokes from me any more: I can't CTRL-A (x3) and get the Xen console, nor the linux console which is configured in /etc/inittab. I see the boot messages go past and get a login prompt, but no keystrokes get through or can control the machine. It's making it tricky to send the box to co-lo as I can't get serial control if I take down the network, or Hypervisor control to reboot Dom0. My rpms are: kernel-xen0-2.6.16-1.2080_FC5 xen-3.0.1-4 and my grub.conf is: default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console # title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=0 module /initrd-2.6.16-1.2080_FC5xen0.img I'd appreciate any guidance on silly things I may have done here; I'm banging my head on this one. Many thanks, Tony tony clark director - tony.clark at rsp.com.au --------------------------------------------------------------- rising sun pictures - www.rsp.com.au redefining visual effects delivery --------------------------------------------------------------- address level 1 / 133 gouger street adelaide south australia 5000 --------------------------------------------------------------- adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 sydney ph +61 2 9338 6400 fax +61 2 9338 6401 --------------------------------------------------------------- rising sun research - http://research.rsp.com.au --------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From nathan-fedoraxen at nrp.com Fri Apr 21 03:16:15 2006 From: nathan-fedoraxen at nrp.com (Nathan) Date: Thu, 20 Apr 2006 21:16:15 -0600 Subject: [Fedora-xen] FC5 - serial console - no characters received by host? In-Reply-To: <018FB09B-473B-482B-9974-2B79F421B34C@rsp.com.au> References: <018FB09B-473B-482B-9974-2B79F421B34C@rsp.com.au> Message-ID: <20060421031615.GA20680@shuttle.nrp.com> I ran into the same problem too, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185744 boot with pnpacpi=off on the kernel command line and it should work (serial console works fine for me though I'm using com1 at 115200). Thanks again to James Morris for finding the workaround for this one! Nathan On Thu, Apr 20, 2006 at 11:35:24PM +0930, Tony Clark wrote: > Hi there, > > I've been working with the FC5 Xen stuff for the past few weeks after > trawling many options for building a redundant server farm; It's a > great build and congratulations to all who put this together. > > I have a little issue with my serial console which is putting hte > brakes on deployment though: I want to use the serial console on com2 > (the default on the Intel mainboard I use) to give me the grub > console, Xen console and Linux consoles. I've had this working fine > on previous releases from SuSE and others and on the current hardware. > > When happens at the moment is that the machine boots, gives me the > grub menu, where I can choose my boot system (so it's hearing my > keystrokes) but once it proceeds into the Xen and ultimately Linux, > it doesn't want to hear keystrokes from me any more: I can't CTRL-A > (x3) and get the Xen console, nor the linux console which is > configured in /etc/inittab. I see the boot messages go past and get > a login prompt, but no keystrokes get through or can control the > machine. > > It's making it tricky to send the box to co-lo as I can't get serial > control if I take down the network, or Hypervisor control to reboot > Dom0. > > My rpms are: > > kernel-xen0-2.6.16-1.2080_FC5 > xen-3.0.1-4 > > and my grub.conf is: > > default=0 > timeout=5 > #splashimage=(hd0,0)/grub/splash.xpm.gz > #hiddenmenu > # > serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 > terminal --timeout=10 serial console > # > title Fedora Core (2.6.16-1.2080_FC5xen0) > root (hd0,0) > kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 > com2=9600,8n1 console=com2,vga sync_console > module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ > VolGroup00/LogVol00 rhgb selinux=0 > module /initrd-2.6.16-1.2080_FC5xen0.img > > I'd appreciate any guidance on silly things I may have done here; I'm > banging my head on this one. > > Many thanks, > > Tony > > > tony clark > director - tony.clark at rsp.com.au > --------------------------------------------------------------- > rising sun pictures - www.rsp.com.au > redefining visual effects delivery > --------------------------------------------------------------- > address level 1 / 133 gouger street > adelaide south australia 5000 > --------------------------------------------------------------- > adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 > sydney ph +61 2 9338 6400 fax +61 2 9338 6401 > --------------------------------------------------------------- > rising sun research - http://research.rsp.com.au > --------------------------------------------------------------- > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From tony.clark at rsp.com.au Fri Apr 21 03:54:23 2006 From: tony.clark at rsp.com.au (Tony Clark) Date: Fri, 21 Apr 2006 13:24:23 +0930 Subject: [Fedora-xen] FC5 - serial console - no characters received by host? In-Reply-To: <20060421031615.GA20680@shuttle.nrp.com> References: <018FB09B-473B-482B-9974-2B79F421B34C@rsp.com.au> <20060421031615.GA20680@shuttle.nrp.com> Message-ID: Thanks to both Yongkang and Nathan for their quick responses on this; I tried both approaches and they did everything I needed. My boot options now follow this message for the record and I have a happy serial console. Tony title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console,acpi=off module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ VolGroup00/LogVol00 rhgb selinux=0 pci=noacpi console=tty0 console=ttyS0 module /initrd-2.6.16-1.2080_FC5xen0.img title Fedora Core (2.6.16-1.2080_FC5xen0 PNP) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ VolGroup00/LogVol00 rhgb selinux=0 console=tty0 console=ttyS0 pnpacpi=off module /initrd-2.6.16-1.2080_FC5xen0.img On 21/04/2006, at 12:46 PM, Nathan wrote: > I ran into the same problem too, see > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185744 > > boot with pnpacpi=off on the kernel command line and it should work > (serial console works fine for me though I'm using com1 at 115200). > > Thanks again to James Morris for finding the workaround for this one! > > Nathan > > On Thu, Apr 20, 2006 at 11:35:24PM +0930, Tony Clark wrote: >> Hi there, >> >> I've been working with the FC5 Xen stuff for the past few weeks after >> trawling many options for building a redundant server farm; It's a >> great build and congratulations to all who put this together. >> >> I have a little issue with my serial console which is putting hte >> brakes on deployment though: I want to use the serial console on com2 >> (the default on the Intel mainboard I use) to give me the grub >> console, Xen console and Linux consoles. I've had this working fine >> on previous releases from SuSE and others and on the current >> hardware. >> >> When happens at the moment is that the machine boots, gives me the >> grub menu, where I can choose my boot system (so it's hearing my >> keystrokes) but once it proceeds into the Xen and ultimately Linux, >> it doesn't want to hear keystrokes from me any more: I can't CTRL-A >> (x3) and get the Xen console, nor the linux console which is >> configured in /etc/inittab. I see the boot messages go past and get >> a login prompt, but no keystrokes get through or can control the >> machine. >> >> It's making it tricky to send the box to co-lo as I can't get serial >> control if I take down the network, or Hypervisor control to reboot >> Dom0. >> >> My rpms are: >> >> kernel-xen0-2.6.16-1.2080_FC5 >> xen-3.0.1-4 >> >> and my grub.conf is: >> >> default=0 >> timeout=5 >> #splashimage=(hd0,0)/grub/splash.xpm.gz >> #hiddenmenu >> # >> serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 >> terminal --timeout=10 serial console >> # >> title Fedora Core (2.6.16-1.2080_FC5xen0) >> root (hd0,0) >> kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 >> com2=9600,8n1 console=com2,vga sync_console >> module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ >> VolGroup00/LogVol00 rhgb selinux=0 >> module /initrd-2.6.16-1.2080_FC5xen0.img >> >> I'd appreciate any guidance on silly things I may have done here; I'm >> banging my head on this one. >> >> Many thanks, >> >> Tony >> >> >> tony clark >> director - tony.clark at rsp.com.au >> --------------------------------------------------------------- >> rising sun pictures - www.rsp.com.au >> redefining visual effects delivery >> --------------------------------------------------------------- >> address level 1 / 133 gouger street >> adelaide south australia 5000 >> --------------------------------------------------------------- >> adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 >> sydney ph +61 2 9338 6400 fax +61 2 9338 6401 >> --------------------------------------------------------------- >> rising sun research - http://research.rsp.com.au >> --------------------------------------------------------------- >> >> >> > >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen tony clark director - tony.clark at rsp.com.au --------------------------------------------------------------- rising sun pictures - www.rsp.com.au redefining visual effects delivery --------------------------------------------------------------- address level 1 / 133 gouger street adelaide south australia 5000 --------------------------------------------------------------- adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 sydney ph +61 2 9338 6400 fax +61 2 9338 6401 --------------------------------------------------------------- rising sun research - http://research.rsp.com.au --------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From shyamal at flashmail.com Tue Apr 11 14:08:21 2006 From: shyamal at flashmail.com (shyamal thatte) Date: Tue, 11 Apr 2006 19:38:21 +0530 Subject: [Fedora-xen] Error creating Domain In-Reply-To: <27136.1144759498@www047.gmx.net> References: <443B5FE6.9060600@flashmail.com> <27136.1144759498@www047.gmx.net> Message-ID: <443BB855.2080901@flashmail.com> Hi, installed xen 3.0.1 from the xen-3.0-x86_32-fc4.bin.tar provided on xensource. installed the 3 RPM's within it 1) xen-3.0.1-64.1_fc4.i386.rpm 2) xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm 3) xen-devel-3.0.1-64.1_fc4.i386.rpm .... there is no User kernel RPM included with xen 3 After reboot into the 2.6.12_xen3 kernel I can see DOM 0 I did a fresh install of FC4 into /dev/hda8 with root on the same system I installed vmlinuz-2.6.12-1.1390_FC4xenU into it When I try to start the guest domain on /dev/hda8 I get the errors and it does not start. Should I install xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm on /dev/hda8 and try and boot it as a guest domain ? Thanks for your help Shyamal Henning Sprang wrote: >>--- Urspr?ngliche Nachricht --- >>[...] >> >>XEN 3.0.1 on FC4 is domain 0. >> >>Installed FC4 on /dev/hda8 separate installation. >> >> > >What do you mean with the last sentence? Do you mean the domU FC4 which you >put into hda8? > >How exactly did you install xen on FC4? I wonder that the references to the >python files in your error logs point to pathes starting with /var/tmp, >which is not exactly a nice location to install pythong scripts. > >Henning > > > From philipp.jaggi at snct.lu Thu Apr 13 07:19:33 2006 From: philipp.jaggi at snct.lu (Philipp =?ISO-8859-2?Q?J=E4ggi?=) Date: Thu, 13 Apr 2006 09:19:33 +0200 Subject: [Fedora-xen] Vnet Support In-Reply-To: <274254211@web.de> Message-ID: Hello Does somebody know if Fedora 5 will support Vnets (Domain Virtual Networking) by default? As I saw, the default installation doesn't have this feature included. bye Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.jaggi at snct.lu Fri Apr 14 06:06:53 2006 From: philipp.jaggi at snct.lu (Philipp =?ISO-8859-2?Q?J=E4ggi?=) Date: Fri, 14 Apr 2006 08:06:53 +0200 Subject: [Fedora-xen] How to configure eth0 via xen config files In-Reply-To: Message-ID: Hello Walter Can't you kickstart your guest? Like this, you can specify everything from the beginning. bye Philipp "Walter Souto" Sent by: fedora-xen-bounces at redhat.com 04/13/2006 02:41 PM To fedora-xen at redhat.com cc Subject Re: [Fedora-xen] How to configure eth0 via xen config files Hi, > I think you can either configure the guest with static information or > use DHCP. I may have missed something in the question though. > No you didn't. Maybe my question don't make sense... But It's exactly what I'm doing now. So, if I need to replicate about 20 guests, each one with your own static IP, I can use DHCP and enforce IP's using mac addr. But, is it possible to do this using the Xen configuration files for the vm's? Just to get somethings a bit simple avoiding DHCP. And thanks for your answer. -- Walter. -- 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 jklein at saugus.k12.ca.us Fri Apr 14 18:14:14 2006 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 14 Apr 2006 11:14:14 -0700 Subject: [Fedora-xen] FC5 Xen and GFS Message-ID: <484DE4D1-087F-46F7-8AFF-D3FE8AF32E2A@saugus.k12.ca.us> I'm trying to get Xen to work in a using GFS on a SAN and FC5, but am not having much luck. It looks like GFS can't get a lock on the xvd file, for some reason, and I can't figure it out. I am able to read and write to GFS in any other way, from all the nodes, without problem. Can't install directly to the GFS volume, and if I install on a local drive, copy to GFS volume, and load, I end up with a read only file system. Log below. Any assistance would be greatly appreciated. Apr 14 10:47:36 blade1 kernel: GFS: fsid=alpha:gfs1.1: time = 1145036856 Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: warning: assertion "gfs_glock_is_locked_by_me(ip->i_gl)" failed Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: function = gfs_prepare_write Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: file = /usr/ src/build/729060-x86_64/BUILD/xen0/src/gfs/ops_address.c, line = 329 From shyamal at flashmail.com Mon Apr 17 12:32:33 2006 From: shyamal at flashmail.com (shyamal thatte) Date: Mon, 17 Apr 2006 18:02:33 +0530 Subject: [Fedora-xen] Error creating Domain In-Reply-To: <44437538.8080609@gmx.de> References: <443B5FE6.9060600@flashmail.com> <27136.1144759498@www047.gmx.net> <443BB855.2080901@flashmail.com> <44437538.8080609@gmx.de> Message-ID: <44438AE1.7070305@flashmail.com> Hi, Think I got a bit further today. Got to know that in xen 3 the Dom0 and DomU kernels are the same. Present config 1) Dom0 -- installed on /dev/hda1 2) DomU -- installed on /dev/hda8, swap /dev/hda6 xen 3 rpm's installed on DomU 3) Create console device using MAKEDEV in domU The DomU starts to boot. but does a kernel panic. Attached please find the related conf and log files. The kernel panic is in xenU_panic.txt Please could you help. Regards Shyamal Henning Sprang wrote: > Sorry, I am bit slow: > > > shyamal thatte wrote: > >> Hi, >> >> installed xen 3.0.1 from the xen-3.0-x86_32-fc4.bin.tar provided on >> xensource. >> installed the 3 RPM's within it >> 1) xen-3.0.1-64.1_fc4.i386.rpm 2) >> xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm >> 3) xen-devel-3.0.1-64.1_fc4.i386.rpm >> .... there is no User kernel RPM included with xen 3 > > > Sorry, I don't know about that bin.tra package - does ist actualkly > contain 3 rpm's then? Sounds a bit weird... > > You don't always need two xen kernels, it's possible to mae one kernel > that can be used for domU and dom0. > > >> >> After reboot into the 2.6.12_xen3 kernel I can see DOM 0 >> >> I did a fresh install of FC4 into /dev/hda8 with root on the same system >> I installed vmlinuz-2.6.12-1.1390_FC4xenU into it >> >> When I try to start the guest domain on /dev/hda8 I get the errors >> and it does not start. > > > What errrs are you exactly getting? > >> Should I install xen-kernel-2.6.12-xen3_64.1_fc4.i686.rpm on >> /dev/hda8 and try and boot it as a guest domain ? > > > Yes, I'd try to install the same kernel rpm in domU as in dom0! > > > Henning > -------------- next part -------------- A non-text attachment was scrubbed... Name: xend_170406.log Type: text/x-log Size: 25872 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xend-debug_170406.log Type: text/x-log Size: 18 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: oratest URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xenU_panic.txt URL: From philipp.jaggi at snct.lu Wed Apr 19 06:51:16 2006 From: philipp.jaggi at snct.lu (Philipp =?ISO-8859-2?Q?J=E4ggi?=) Date: Wed, 19 Apr 2006 08:51:16 +0200 Subject: [Fedora-xen] Running FC4 on FC5 In-Reply-To: <000d01c662f3$7ce11aa0$5f00000a@rmortimer> Message-ID: Dear Robert First of all, I've had the same questions and problems as you have now. This style of none documentation by the fedora team is just a shame for the whole open source community! Probably Jeremy Katz is too busy by meeting his new board members friends, so that he has no more time to write just a little documentation with explanations, not just a unusable mini mini howto. What the big problem is behind the FC5 and Xen implementation is, that the xen guys at fedora have no idea what SELinux is doing. So, finally they made an implementation of xen and SELinux that is not usable. If you don't want to spend two weeks configuring your SELinux, you have to decide, if you use in future SELinux or Xen (By the way, the same issues you have with httpd and SELinux). So my personal proposal is, that you just disable SELinux wherever you find it on your FC5 installation. After disabling SELinux (you have to reboot so that everything works fine, => Oh I like this old nice M$ Win95 style of system management) you can use your xen config as you posted in your mail. With the xenguest-install.py script you can't install FC4 or another distribution, because the FC5 guys made an adaptation of the anaconda system installer. By the way, this is a nice feature, because you can now kickstart your FC5 installation. If you want to install a new non FC5 guest, do it in the old style. Create your devices with LVM and perform a yum groupinstall with --installdir=yourdevice. As you can see, Fedora Core 5 is a typical example for bad IT Management. They tried to do a lot of thing in a short time. So several teams worked on different things and now, nothing really fits together. The whole implementation of the SELinux is a disaster. So for professional use, you have to go back to Fedora Core 4. Also because the oracle stuff is not working with the new glibc (it's not possible to start the listener... :-(). I by myself have to use FC5, because I need to kickstart my xen installation and need apache 2.2. If you don't need those features, use CentOS or the original RHES. Hope I gave you the right hints. bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 "Robert Mortimer" Sent by: fedora-xen-bounces at redhat.com 04/18/2006 04:22 PM To cc Subject [Fedora-xen] Running FC4 on FC5 I am attempting to run an FC4 image on an FC5 machine I have prepped the image as per the FC4 quick start my xen config is as follows kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU" memory = 100 name = "vm01" vcpus = 1 vif= ['mac=FE:FD:25:63:74:49'] disk = [ 'file:/root/VM/fedora.img,sda1,w' ] root = "/dev/sda1" extra = "ro selinux=0 3" All I get is # xm create vm01 Using config file "vm01". Error: Error creating domain: (22, 'Invalid argument') Has anyone got a simple 1 NIC guest config for FC4 on FC5 I see that the new FC5 uses An init image as part of the boot A python based boot loader and a python based install script Is there any way to hack this lot to do an install like the FC5/FC5 one? How are the init images built? Will the new installer do other guest OS's in the future? Robert -- 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 kim.gabrielsen at get2net.dk Fri Apr 21 14:32:10 2006 From: kim.gabrielsen at get2net.dk (Kim Gabrielsen) Date: Fri, 21 Apr 2006 16:32:10 +0200 Subject: [Fedora-xen] using centos 4.3 ad guest Message-ID: Hi, I have successfully installed Xen with fedora core 5 and i have installed a guest system running fedora core 5. The guest is running without problems. I'm now trying to install a guest based on centos 4.3. i create the guest system using xenguest-install.py and the process is like this: What is the name of your virtual machine? centos How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /xen/centos What is the install location? http://mirror.fysik.dtu.dk/linux/centos/4.3/os/i386/ Invalid URL location given but why does it give me an 'Invalid URL location given' error message? I can see the URL in my browser and i can see the centos install tree. i have tried with nfs also using my local centos install tree using: nfs:miraculix:/usr/public/distributions/centos43_i386 but it fails. if i use nfs:miraculix:/usr/public/distributions/fedora5_i386 it woks perfectly and was the install tree i used for creating my first guest system. im using the latest xen version. hope someone can help me cause i'm pretty much stuck here and i don't see much point in using xen if i can only run guest systems based on fedora 5. br kim gabrielsen From brandon.deyoung at gmail.com Fri Apr 21 21:35:51 2006 From: brandon.deyoung at gmail.com (Brandon DeYoung) Date: Fri, 21 Apr 2006 14:35:51 -0700 Subject: [Fedora-xen] Newbie help Message-ID: Hi All, I'm trying to get RHEL 3 to run as a guest domain and am not sure where to start. I have installed FC5 and am able to get FC5 guest domains running using the niffty tools developed by the Fedora folks. I can't find a howto anywhere on running RHEL 3 (or 4) as a guest domain. I'm planning to use these to do some integration testing, so would like to get these guests as close to RHEL 3 as possible i.e. using a 2.4 kernel, etc.. Any advise is helpful, if someone has found or written a howto, that is even better. Thanks in advance, ~Brandon -------------- next part -------------- An HTML attachment was scrubbed... URL: From nacho at estudio-verona.com Sat Apr 22 18:24:18 2006 From: nacho at estudio-verona.com (Ignacio Verona) Date: Sat, 22 Apr 2006 20:24:18 +0200 Subject: [Fedora-xen] Running FC4 as guest in FC5 Xen Message-ID: <444A74D2.90203@estudio-verona.com> Hi, this is my first post to the list, and I've been reading it for a while. Although there are some posts regarding how to instal FC4 as a guest in FC5, I'm not able to get it running. FC5 guest is ok, but how do I install an FC4? I've followed all the steps for the FC4 QuickStart, I don't know which kernel should I load. First, if using the kernel installed with my FC5 installation (vmlinuz-2.6.16-1.2096_FC5xen0) the kernel boots, but then it hangs because it doesn't find the root fs (sda1). I've tried to do a chroot into my fc4 minimum installation (under /mnt) and install the vmlinuz-2.6.13-1.1532_FC4xenU, copy it to the host machine and put it into the configuration, but then, when booting the guest I get a message saying that the argument is invalid. Looking the logs, y see this: ERROR: Will only load images built for Xen v3.0 ERROR: Actually saw: 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic' ERROR: Error constructing guest OS So, what are the exact steps (or the steps which differ from the FC4 XenQuickStart) that should I take in order to get FC4 running under FC5? Thanks a lot in advance, Ignacio. From jblsoundz04 at gmail.com Sun Apr 23 18:10:29 2006 From: jblsoundz04 at gmail.com (Jon Stone) Date: Sun, 23 Apr 2006 13:10:29 -0500 Subject: [Fedora-xen] MAC to IP, iptables security for xen guests? Message-ID: With each xen guest having its own virtual MAC address, is it possible at the dom0 level to set iptable rulesets which act as ip based access control lists per guest? Essentially the concept would be to limit the IP address per Xen guest, at the host level, so that a guest domain would not be able to assign itself the IP address of dom0 and create IP conflicts. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.forveille at gmail.com Mon Apr 24 00:18:58 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Sun, 23 Apr 2006 20:18:58 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? Message-ID: <444C1972.6020708@gmail.com> Does anyone has e detailed procedure to change the size (ie increase) of the file that is used as the "xvda" disk by a domU? This is the file created by the "xenguest-install" script (or the one created as in section 6.2 of the xen user's manual for the file-backed VBDs scenario). Thanks in advance From bench at silentmedia.com Mon Apr 24 00:19:26 2006 From: bench at silentmedia.com (Ben) Date: Sun, 23 Apr 2006 17:19:26 -0700 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <444C1972.6020708@gmail.com> References: <444C1972.6020708@gmail.com> Message-ID: <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> Yeah, you use LVM and grow you logical volume size, then expand it in the guest domain. I'm not sure, but I suspect you'd have to restart your guest before you can expand it. On Apr 23, 2006, at 5:18 PM, Denis Forveille wrote: > Does anyone has e detailed procedure to change the size (ie > increase) of the file that is used as the "xvda" disk by a domU? > This is the file created by the "xenguest-install" script (or the > one created as in section 6.2 of the xen user's manual for the file- > backed VBDs scenario). > > Thanks in advance > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From matbayer.web at web.de Mon Apr 24 07:38:28 2006 From: matbayer.web at web.de (Matthias Bayer) Date: Mon, 24 Apr 2006 09:38:28 +0200 Subject: [Fedora-xen] PAE and FC5 Xen on 32-bit system Message-ID: <284038954@web.de> Hi, i have a 32-bit FC5 system running with default xen from FC5 (kernel-xen0-2.6.16-1.2096_FC5 & xen-3.0.1-4). my system has 4GB of memory but xm info only shows 3584MB available. i know i need PAE support but the question is if there is a PAE enabled kernel from FC5 32-bit xen systems available already or if i can turn on PAE support easily somehow. for me it's important to stay 'supported' and use only 'officialy availbale' packages. if there is no such a PAE enabled version available can somebody explain what exactly needs to be done to turn PAE support on, i searched the web and found lots of different instructions but i am not sure which one is the 'correct' one ? thanks for any help ! regards, Matthias _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 From rstory-l at 2006.revelstone.com Mon Apr 24 12:26:07 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Mon, 24 Apr 2006 08:26:07 -0400 Subject: [Fedora-xen] Running FC4 as guest in FC5 Xen In-Reply-To: <444A74D2.90203@estudio-verona.com> References: <444A74D2.90203@estudio-verona.com> Message-ID: <20060424082607.53d13458@aud.vb.futz.org> On Sat, 22 Apr 2006 20:24:18 +0200 Ignacio wrote: IV> First, if using the kernel installed with my FC5 installation IV> (vmlinuz-2.6.16-1.2096_FC5xen0) the kernel boots, but then it hangs IV> because it doesn't find the root fs (sda1). Never use a dom0 kernel for a guest. Why not use the FC5 domU kernel? That's what I'm using for my CentOS 4.3 guest, and it works fine. From rstory-l at 2006.revelstone.com Mon Apr 24 12:28:57 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Mon, 24 Apr 2006 08:28:57 -0400 Subject: [Fedora-xen] using centos 4.3 ad guest In-Reply-To: References: Message-ID: <20060424082857.283b57da@aud.vb.futz.org> On Fri, 21 Apr 2006 16:32:10 +0200 Kim wrote: KG> I'm now trying to install a guest based on centos 4.3. KG> KG> i create the guest system using xenguest-install.py The fedora script is just for installing fedora guests. If you want other guest, you'll have to create them some other way. I built my CentOS 4.3 guest system using rpmstrap, w/instructions from a page I found via google. There are also messages in the archives about using rpm and yum, pointing them to a mounted image for their root. From rmortimer at bluechiptechnology.co.uk Mon Apr 24 15:01:56 2006 From: rmortimer at bluechiptechnology.co.uk (Robert Mortimer) Date: Mon, 24 Apr 2006 16:01:56 +0100 Subject: [Fedora-xen] using centos 4.3 ad guest In-Reply-To: <20060424082857.283b57da@aud.vb.futz.org> Message-ID: <000d01c667b0$07693c00$5f00000a@rmortimer> > > On Fri, 21 Apr 2006 16:32:10 +0200 Kim wrote: > KG> I'm now trying to install a guest based on centos 4.3. > KG> > KG> i create the guest system using xenguest-install.py > > The fedora script is just for installing fedora guests. If you want other > guest, you'll have to create them some other way. I built my > CentOS 4.3 guest > system using rpmstrap, w/instructions from a page I found via > google. There > are also messages in the archives about using rpm and yum, > pointing them to a > mounted image for their root. To be more specific xenguest-install.py will only install FC5 images at the moment as it relies on updates to anaconda. The HOWTO for Xen FC4 is on the fedora WIKKI and provides an insight into producing OS images. Alternatively go to http://jailtime.org/ Robert > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From chitlesh at fedoraproject.org Mon Apr 24 15:19:11 2006 From: chitlesh at fedoraproject.org (Chitlesh GOORAH) Date: Mon, 24 Apr 2006 17:19:11 +0200 Subject: [Fedora-xen] vFUDCon: virtual FUDCon Message-ID: <13dbfe4f0604240819g2aaa9d1cn4f4a2b054596cbc3@mail.gmail.com> Hello everyone, We have launched the vFUDCon Project, a FUDCon that is virtual, of course, but will be accesible with multimedia medium only. http://fedoraproject.org/wiki/FedoraEvents/vFUDCon? >From this sub project of Fedora Marketing we hope, that local ambassadors can extends their marketing perspective through any multimedia medium. The French ambassadors have scheduled one this thursday, on IRC. http://fedoraproject.org/wiki/FedoraEvents/vFUDCon/01France Announcements will be done these following days. (already started on linuxfr) Any suggestions are welcome. Regards, Chitlesh Goorah -- http://clunixchit.blogspot.com From bob at detroittechgroup.com Mon Apr 24 16:58:33 2006 From: bob at detroittechgroup.com (bob at detroittechgroup.com) Date: Mon, 24 Apr 2006 09:58:33 -0700 Subject: [Fedora-xen] Error message about memory on xm create Message-ID: <20060424095833.73511e384f1d3e9456851a98c8601e27.a6678ff554.wbe@email.secureserver.net> An HTML attachment was scrubbed... URL: From chris at base2technology.com Mon Apr 24 18:07:30 2006 From: chris at base2technology.com (Chris Hirsch) Date: Mon, 24 Apr 2006 12:07:30 -0600 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> References: <444C1972.6020708@gmail.com> <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> Message-ID: <444D13E2.8060409@base2technology.com> Ben wrote: > Yeah, you use LVM and grow you logical volume size, then expand it > in the guest domain. I'm not sure, but I suspect you'd have to > restart your guest before you can expand it. But isn't the xvda just a file containing partitions and the like? I've actually been wanting to do this myself WITH LVM. I'd LOVE to have lvm extend the file itself. I did find the trick extending an image: dd if=/dev/zero bs=1024 count=3500000 >> fedora.fc5.img resize2fs -f fedora.fc5.img and thats works great...The way I understand the xvda file is that you'd have to copy out anything that is after the main image resize the image (like above) and then append the old stuff back to the end of the disk. I'd assume "stuff" here to mean something like swap. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Mon Apr 24 18:13:56 2006 From: bench at silentmedia.com (Ben) Date: Mon, 24 Apr 2006 11:13:56 -0700 (PDT) Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <444D13E2.8060409@base2technology.com> References: <444C1972.6020708@gmail.com> <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> <444D13E2.8060409@base2technology.com> Message-ID: Sorry, I should have been more clear. When you create the domU, you need to give it an LVM logical volume. As far as the domU is concerned, it's just a disk. But from the dom0 side, it's an easily expandible partition. After you grow it, use tools on the domU side to expand the filesystem. There's really no point in trying to expand a swap partition because you can just make another one. On Mon, 24 Apr 2006, Chris Hirsch wrote: > Ben wrote: >> Yeah, you use LVM and grow you logical volume size, then expand it >> in the guest domain. I'm not sure, but I suspect you'd have to >> restart your guest before you can expand it. > But isn't the xvda just a file containing partitions and the like? > I've actually been wanting to do this myself WITH LVM. I'd LOVE to > have lvm extend the file itself. > > I did find the trick extending an image: > dd if=/dev/zero bs=1024 count=3500000 >> fedora.fc5.img > resize2fs -f fedora.fc5.img > > and thats works great...The way I understand the xvda file is that > you'd have to copy out anything that is after the main image resize > the image (like above) and then append the old stuff back to the end > of the disk. I'd assume "stuff" here to mean something like swap. > > Chris > > From ryan.hofschneider.ctr at metnet.navy.mil Tue Apr 25 00:18:24 2006 From: ryan.hofschneider.ctr at metnet.navy.mil (Ryan Hofschneider) Date: Mon, 24 Apr 2006 17:18:24 -0700 Subject: [Fedora-xen] eth0 not coming up in domU Message-ID: <2ED713C5-9A95-4515-AFBA-2E84E39851F4@metnet.navy.mil> On April 11, 2006 at 15:01:44 -0700 dmorgan at gmi-mr com wrote: > Kernel is 2.6.16-1.2080_FC5.xenU > > I've found that the problem was caused because the 2.4 based guest > OS (White > Box Linux) didn't support modprobe.conf so didn't load the > > CONFIG_XEN_NETDEV_FRONTEND > > Module. I've recompiled the kernel so that this module is built in > and it > resolved the issue. Is there any reason why this module isn't built into the kernel by default, so folks setting up 2.4-based guest operating systems (e.g, RHEL3) can avoid building a custom kernel? Is there an easier way that I have overlooked? Thanks, Ryan From denis.forveille at gmail.com Tue Apr 25 00:29:59 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Mon, 24 Apr 2006 20:29:59 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: References: <444C1972.6020708@gmail.com> <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> <444D13E2.8060409@base2technology.com> Message-ID: <444D6D87.2000006@gmail.com> An HTML attachment was scrubbed... URL: From katzj at redhat.com Tue Apr 25 00:41:57 2006 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 24 Apr 2006 20:41:57 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <444D6D87.2000006@gmail.com> References: <444C1972.6020708@gmail.com> <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> <444D13E2.8060409@base2technology.com> <444D6D87.2000006@gmail.com> Message-ID: <1145925717.2834.3.camel@aglarond.local> On Mon, 2006-04-24 at 20:29 -0400, Denis Forveille wrote: > After that I'm stucked: > - I cant expand the filesystem for "/" from domU: "fdisk" gives the > correct (new) size for "/dev/xvda", but I can't use parted or > rezise2fs on "/dev/xvda1" as it is mounted... Take a look at ext2online for online resizing of ext[23] filesystems > - Maybe, from dom0, a combination of "lomount" and "parted" or > "resize2fs" or other tools could do the job but I don't know how to do > it. Take a look at kpartx (I think it's in the device-mapper-multipath package for whatever reason, but that's neither here nor there) -- it'll let you set up device mapper devices based on a partition table if you want to do manipulation of guest filesystems from dom0 Jeremy From mark at heilpern.com Tue Apr 25 01:27:45 2006 From: mark at heilpern.com (Mark A Heilpern) Date: Mon, 24 Apr 2006 21:27:45 -0400 (EDT) Subject: [Fedora-xen] Multihomed networking In-Reply-To: Message-ID: <6367834.51145928465537.JavaMail.root@heilpern.com> Is anyone using FC5 Xen with an FC5 guest, where the Dom0 has two ethernet devices (succesfully)? My system has eth0 as a 192.168.2.x network, eth1 as my static Internet address, and iptables NAT between them. All real machines on my home network can get out just fine. My guest VM, also a 192.168.2.x address, is able to reach other machines on my internal network without problem, but trying to access the internet doesn't work. At first I thought it was an iptables configuration issue on the Dom0 machine, but I don't think so anymore. As a test, I inserted at the top of every table a rule to emit a log message when any machine on my net tried to access a specific remote host; performing a wget command in the guest VM shows my outbound SYN, shows an incoming SYN+ACK from the remote host (so outbound masquarading must be working?) and an outbound ACK (so incoming demasquarading must be working?)... I never receive another packet from the remote host (until quite a while later, when I receive FIN). If I try the same exercise with a real host on my network, I get a normal data stream in/out. Also, traceroute from the guest VM doesn't work exactly as I would expect. I would expect the results of one to be quite similar to those from my Dom0 machine, but consistantly I am missing responses along the path. For example: >From dom0: [root at heilpern ~]# traceroute www.yahoo.com traceroute to www.yahoo.com (216.109.117.106), 30 hops max, 40 byte packets 1 [my cable modem] 2 10.106.32.1 (10.106.32.1) 8.279 ms 11.786 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 ae-0-0.bbr2.Washington1.Level3.net (4.68.128.210) 45.855 ms * * 8 ae-21-54.car1.Washington1.Level3.net (4.68.121.114) 35.593 ms ae-21-56.car1.Washington1.Level3.net (4.68.121.178) 35.382 ms 41.539 ms 9 4.79.228.2 (4.79.228.2) 40.073 ms 39.931 ms * 10 * * * 11 * * * 12 * p21.www.dcn.yahoo.com (216.109.117.106) 35.227 ms * >From the guest VM: [root at testvm ~]# traceroute www.yahoo.com traceroute to www.yahoo.com (216.109.117.106), 30 hops max, 40 byte packets 1 192.168.2.1 (192.168.2.1) 0.000 ms 0.000 ms 0.000 ms 2 [my cable modem] 3 10.106.32.1 (10.106.32.1) 9.910 ms 13.919 ms * 4 * * * 5 * * * 6 * * * 7 * * * 8 ae-0-0.bbr2.Washington1.Level3.net (4.68.128.210) 48.307 ms * * 9 ae-11-51.car1.Washington1.Level3.net (4.68.121.18) 37.938 ms 42.377 ms ae-21-54.car1.Washington1.Level3.net (4.68.121.114) 43.048 ms 10 4.79.228.2 (4.79.228.2) 45.568 ms 43.918 ms * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * [root at testvm ~]# This is pretty repeatable. Any thoughts? Here are my Dom0 configurations: [root at heilpern ~]# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif2.0 [root at heilpern ~]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:10:DC:F2:70:17 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:dcff:fef2:7017/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:733780 errors:0 dropped:0 overruns:0 frame:0 TX packets:822036 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:87799449 (83.7 MiB) TX bytes:207088442 (197.4 MiB) [root at heilpern ~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:90:47:03:B8:63 inet addr:[my IP] Bcast:[my BCAST IP] Mask:255.255.255.252 inet6 addr: fe80::290:47ff:fe03:b863/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:829216 errors:0 dropped:0 overruns:0 frame:0 TX packets:556902 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:169446616 (161.5 MiB) TX bytes:85050877 (81.1 MiB) Interrupt:18 [root at heilpern ~]# iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination (temporary wide-open rules): [root at heilpern ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain INBOUND (0 references) target prot opt source destination Chain LOG_FILTER (0 references) target prot opt source destination Chain LSI (0 references) target prot opt source destination Chain LSO (0 references) target prot opt source destination Chain OUTBOUND (0 references) target prot opt source destination Thanks in advance... Mark From bench at silentmedia.com Tue Apr 25 02:03:55 2006 From: bench at silentmedia.com (Ben) Date: Mon, 24 Apr 2006 19:03:55 -0700 Subject: [Fedora-xen] Multihomed networking In-Reply-To: <6367834.51145928465537.JavaMail.root@heilpern.com> References: <6367834.51145928465537.JavaMail.root@heilpern.com> Message-ID: <5015C55C-134A-43CE-AF29-24ED18CB7F0A@silentmedia.com> Yes, but not with the default xen bridging scripts. On Apr 24, 2006, at 6:27 PM, Mark A Heilpern wrote: > Is anyone using FC5 Xen with an FC5 guest, where the Dom0 has two > ethernet devices (succesfully)? > > My system has eth0 as a 192.168.2.x network, eth1 as my static > Internet address, and iptables NAT between them. All real machines > on my home network can get out just fine. > > My guest VM, also a 192.168.2.x address, is able to reach other > machines on my internal network without problem, but trying to > access the internet doesn't work. At first I thought it was an > iptables configuration issue on the Dom0 machine, but I don't think > so anymore. As a test, I inserted at the top of every table a rule > to emit a log message when any machine on my net tried to access a > specific remote host; performing a wget command in the guest VM > shows my outbound SYN, shows an incoming SYN+ACK from the remote > host (so outbound masquarading must be working?) and an outbound > ACK (so incoming demasquarading must be working?)... I never > receive another packet from the remote host (until quite a while > later, when I receive FIN). If I try the same exercise with a real > host on my network, I get a normal data stream in/out. > > Also, traceroute from the guest VM doesn't work exactly as I would > expect. I would expect the results of one to be quite similar to > those from my Dom0 machine, but consistantly I am missing responses > along the path. For example: > > >> From dom0: > [root at heilpern ~]# traceroute www.yahoo.com > traceroute to www.yahoo.com (216.109.117.106), 30 hops max, 40 byte > packets > 1 [my cable modem] > 2 10.106.32.1 (10.106.32.1) 8.279 ms 11.786 ms * > 3 * * * > 4 * * * > 5 * * * > 6 * * * > 7 ae-0-0.bbr2.Washington1.Level3.net (4.68.128.210) 45.855 ms * * > 8 ae-21-54.car1.Washington1.Level3.net (4.68.121.114) 35.593 ms > ae-21-56.car1.Washington1.Level3.net (4.68.121.178) 35.382 ms > 41.539 ms > 9 4.79.228.2 (4.79.228.2) 40.073 ms 39.931 ms * > 10 * * * > 11 * * * > 12 * p21.www.dcn.yahoo.com (216.109.117.106) 35.227 ms * > > >> From the guest VM: > [root at testvm ~]# traceroute www.yahoo.com > traceroute to www.yahoo.com (216.109.117.106), 30 hops max, 40 byte > packets > 1 192.168.2.1 (192.168.2.1) 0.000 ms 0.000 ms 0.000 ms > 2 [my cable modem] > 3 10.106.32.1 (10.106.32.1) 9.910 ms 13.919 ms * > 4 * * * > 5 * * * > 6 * * * > 7 * * * > 8 ae-0-0.bbr2.Washington1.Level3.net (4.68.128.210) 48.307 ms * * > 9 ae-11-51.car1.Washington1.Level3.net (4.68.121.18) 37.938 ms > 42.377 ms ae-21-54.car1.Washington1.Level3.net (4.68.121.114) > 43.048 ms > 10 4.79.228.2 (4.79.228.2) 45.568 ms 43.918 ms * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > [root at testvm ~]# > > > > This is pretty repeatable. > > Any thoughts? > > > Here are my Dom0 configurations: > [root at heilpern ~]# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif2.0 > [root at heilpern ~]# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:10:DC:F2:70:17 > inet addr:192.168.2.1 Bcast:192.168.2.255 Mask: > 255.255.255.0 > inet6 addr: fe80::210:dcff:fef2:7017/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:733780 errors:0 dropped:0 overruns:0 frame:0 > TX packets:822036 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:87799449 (83.7 MiB) TX bytes:207088442 (197.4 MiB) > > [root at heilpern ~]# ifconfig eth1 > eth1 Link encap:Ethernet HWaddr 00:90:47:03:B8:63 > inet addr:[my IP] Bcast:[my BCAST IP] Mask:255.255.255.252 > inet6 addr: fe80::290:47ff:fe03:b863/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:829216 errors:0 dropped:0 overruns:0 frame:0 > TX packets:556902 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:169446616 (161.5 MiB) TX bytes:85050877 (81.1 MiB) > Interrupt:18 > > [root at heilpern ~]# iptables -t nat -L > Chain PREROUTING (policy ACCEPT) > target prot opt source destination > > Chain POSTROUTING (policy ACCEPT) > target prot opt source destination > MASQUERADE all -- anywhere anywhere > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > (temporary wide-open rules): > [root at heilpern ~]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > Chain INBOUND (0 references) > target prot opt source destination > > Chain LOG_FILTER (0 references) > target prot opt source destination > > Chain LSI (0 references) > target prot opt source destination > > Chain LSO (0 references) > target prot opt source destination > > Chain OUTBOUND (0 references) > target prot opt source destination > > > > Thanks in advance... > Mark > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From denis.forveille at gmail.com Tue Apr 25 02:45:22 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Mon, 24 Apr 2006 22:45:22 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <1145925717.2834.3.camel@aglarond.local> References: <444C1972.6020708@gmail.com> <1A819EA1-8CF3-466D-B878-2B73B7356F10@silentmedia.com> <444D13E2.8060409@base2technology.com> <444D6D87.2000006@gmail.com> <1145925717.2834.3.camel@aglarond.local> Message-ID: <444D8D42.3090505@gmail.com> Thanks, but I still miss how to grow the partition inside the disk inside the lvg (lvg -> /dev/xvda -> /dev/xvda1) To summarize, the steps should be (from dom0): 1) grow the lvg used for domU (=/dev/xvda from the domU point of view) -> lvextend -L +1024 /dev/vg_domU/lv_FC55 2) grow the partition used by "/" in the lvg (/dev/xvda1) with parted -> parted /dev/mapper/vg_domU-lv_FC55 -> resize 1 32kB 9664MB (This does not work, see below) 3) resize the fs with resize2fs (from dom0) or with ext2online from domU (thanks to Jeremy) -> resize2fs /dev/mapper/vg_domU-lv_FC55 Here's the output from parted: Using /dev/mapper/vg_domU-lv_FC55 (parted) print Disk geometry for /dev/mapper/vg_domU-lv_FC55: 0kB - 9664MB Disk label type: msdos Number Start End Size Type File system Flags 1 32kB 8587MB 8587MB primary ext3 boot (parted) resize 1 Start? [32kB]? 32kB End? [8587MB]? 9660MB Error: File system has an incompatible feature enabled. Is there a tool other than parted I could use to resize the partition /dev/xvda1 inside the lvg? Jeremy Katz wrote: > On Mon, 2006-04-24 at 20:29 -0400, Denis Forveille wrote: > >> After that I'm stucked: >> - I cant expand the filesystem for "/" from domU: "fdisk" gives the >> correct (new) size for "/dev/xvda", but I can't use parted or >> rezise2fs on "/dev/xvda1" as it is mounted... >> > > Take a look at ext2online for online resizing of ext[23] filesystems > > >> - Maybe, from dom0, a combination of "lomount" and "parted" or >> "resize2fs" or other tools could do the job but I don't know how to do >> it. >> > > Take a look at kpartx (I think it's in the device-mapper-multipath > package for whatever reason, but that's neither here nor there) -- it'll > let you set up device mapper devices based on a partition table if you > want to do manipulation of guest filesystems from dom0 > > Jeremy > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From lennu at propoint.fi Tue Apr 25 13:16:42 2006 From: lennu at propoint.fi (Len Merikanto) Date: Tue, 25 Apr 2006 16:16:42 +0300 (EEST) Subject: [Fedora-xen] Hello. Problem with FC5 DomU and yum and other crap Message-ID: <35468.194.29.192.3.1145971002.squirrel@hiili.webmail.cutery.fi> Linux fc5_pristine 2.6.12.6-xenU #2 SMP Tue Apr 4 01:58:00 Local time zone must be set--see zic m x86_64 x86_64 x86_64 GNU/Linux [root at fc5_pristine ~]# yum install joe follows a big flood of: Error: Missing Dependency: libc.so.6(GLIBC_2.3) is needed by package openssl Error: Missing Dependency: libc.so.6(GLIBC_2.1.3) is needed by package nmap Error: Missing Dependency: libc.so.6(GLIBC_2.2) is needed by package slang Error: Missing Dependency: libc.so.6(GLIBC_2.1) is needed by package e2fsprogs Error: Missing Dependency: libresolv.so.2 is needed by package openssl Error: Missing Dependency: libc.so.6(GLIBC_2.1.3) is needed by package krb5-libs Error: Missing Dependency: libc.so.6(GLIBC_2.1) is needed by package perl Error: Missing Dependency: libc.so.6(GLIBC_2.3) is needed by package SysVinit Error: Missing Dependency: libc.so.6(GLIBC_2.2) is needed by package python Error: Missing Dependency: libm.so.6(GLIBC_2.0) is needed by package tcl Error: Missing Dependency: libc.so.6(GLIBC_2.2) is needed by package beecrypt Error: Missing Dependency: libdl.so.2 is needed by package libuser Error: Missing Dependency: libc.so.6(GLIBC_2.1.3) is needed by package e2fsprogs-libs Error: Missing Dependency: libc.so.6(GLIBC_2.4) is needed by package vim-minimal Error: Missing Dependency: libc.so.6(GLIBC_2.3) is needed by package wireless-tools Error: Missing Dependency: libc.so.6(GLIBC_2.3) is needed by package bzip2 Error: Missing Dependency: libc.so.6(GLIBC_2.0) is needed by package ethtool Error: Missing Dependency: libc.so.6(GLIBC_2.1) is needed by package net-tools Error: Missing Dependency: libc.so.6(GLIBC_2.1.1) is needed by package cpio now what might be wrong or everything? never got fedora go this bad :O Anything i try to install bitches the same. i am using Dom0 as gentoo and FC5 DomU image is from jail site... Anyone seen ever anything similar and how to fix this? ive trie fiddling with yum conf and repos but nothing helps.. thnaks in advance... -- Len Merikanto From lamont at gurulabs.com Tue Apr 25 17:14:52 2006 From: lamont at gurulabs.com (Lamont R. Peterson) Date: Tue, 25 Apr 2006 11:14:52 -0600 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <1145925717.2834.3.camel@aglarond.local> References: <444C1972.6020708@gmail.com> <444D6D87.2000006@gmail.com> <1145925717.2834.3.camel@aglarond.local> Message-ID: <200604251114.53256.lamont@gurulabs.com> On Monday 24 April 2006 06:41pm, Jeremy Katz wrote: > On Mon, 2006-04-24 at 20:29 -0400, Denis Forveille wrote: > > After that I'm stucked: > > - I cant expand the filesystem for "/" from domU: "fdisk" gives the > > correct (new) size for "/dev/xvda", but I can't use parted or > > rezise2fs on "/dev/xvda1" as it is mounted... > > Take a look at ext2online for online resizing of ext[23] filesystems Is ext2online supposed to work for ext2 filesystems? I have read that it only worked for ext3. I've tried it with ext2 (created using mke2fs on RHEL4) and it never worked. [snip] -- Lamont R. Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] GPG Key fingerprint: F98C E31A 5C4C 834A BCAB 8CB3 F980 6C97 DC0D D409 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lamont at gurulabs.com Tue Apr 25 17:18:39 2006 From: lamont at gurulabs.com (Lamont R. Peterson) Date: Tue, 25 Apr 2006 11:18:39 -0600 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <444D8D42.3090505@gmail.com> References: <444C1972.6020708@gmail.com> <1145925717.2834.3.camel@aglarond.local> <444D8D42.3090505@gmail.com> Message-ID: <200604251118.39492.lamont@gurulabs.com> On Monday 24 April 2006 08:45pm, Denis Forveille wrote: > Thanks, but I still miss how to grow the partition inside the disk > inside the lvg (lvg -> /dev/xvda -> /dev/xvda1) I don't have partitions inside of the LVs in dom0. It works great for all distros (SUSE 9.x/10.0, SLES8/9, RHEL3/4, CentOS3/4, FC2/3/4/5, Gentoo, Ubuntu). Just make the LV the partition for the domU guests. Then, you don't have to worry about a partition table from either dom0 or domU and the guests don't care about it either. [snip] -- Lamont R. Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] GPG Key fingerprint: F98C E31A 5C4C 834A BCAB 8CB3 F980 6C97 DC0D D409 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Alex.Upton at instinet.com Tue Apr 25 17:18:50 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Tue, 25 Apr 2006 13:18:50 -0400 Subject: [Fedora-xen] Multiple virtual to physical nic setup docs PLEASE! Message-ID: Hello All, I'm using FC5 with the following setup: 2.6.16-1.2080_FC5xen0 xen-3.0.1-4 I have a dual homed system, and would like all virtual eth0 nics to utilize the real physical eth0 nic, and would like all virtual eth1 nics to use the real physical eth1 nic. as of now I have this: in my /etc/xen/host1 vif = [ 'mac=0a:00:00:00:00:01', 'mac=0b:00:00:00:00:01'] in my /etc/xen/xend-config.sxp (network-script 'network-bridge bridge=br0 netdev=eth0') (network-script 'network-bridge bridge=br1 netdev=eth1') brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 brctl addbr xenbr1 brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 xenbr1 8000.000000000000 no can't get port info: Function not implemented On the virtual host i ssh in through the virtual eth0 interface successfully, then when i issue a tcpdump on the virtual eth1 i see real traffic for the real physical eth1, however when assigning an address on the virtual eth1, i can not access it from outside the virtual environment. Any direction to specific setup docs or any advice would be greatly appreciated! Thanks, -Alex ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Tue Apr 25 18:48:47 2006 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 25 Apr 2006 14:48:47 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <200604251114.53256.lamont@gurulabs.com> References: <444C1972.6020708@gmail.com> <444D6D87.2000006@gmail.com> <1145925717.2834.3.camel@aglarond.local> <200604251114.53256.lamont@gurulabs.com> Message-ID: <1145990927.9680.71.camel@orodruin.boston.redhat.com> On Tue, 2006-04-25 at 11:14 -0600, Lamont R. Peterson wrote: > On Monday 24 April 2006 06:41pm, Jeremy Katz wrote: > > On Mon, 2006-04-24 at 20:29 -0400, Denis Forveille wrote: > > > After that I'm stucked: > > > - I cant expand the filesystem for "/" from domU: "fdisk" gives the > > > correct (new) size for "/dev/xvda", but I can't use parted or > > > rezise2fs on "/dev/xvda1" as it is mounted... > > > > Take a look at ext2online for online resizing of ext[23] filesystems > > Is ext2online supposed to work for ext2 filesystems? I have read that it only > worked for ext3. I've tried it with ext2 (created using mke2fs on RHEL4) and > it never worked. I thought the support went in, but I could be mistaken. As it turns out, I never create ext2 filesystems anymore :) Jeremy From nacho at estudio-verona.com Tue Apr 25 22:17:04 2006 From: nacho at estudio-verona.com (Ignacio Verona) Date: Wed, 26 Apr 2006 00:17:04 +0200 Subject: [Fedora-xen] Problems saving Domain with "xm save" Message-ID: <444E9FE0.3000602@estudio-verona.com> Hi, I'm trying to make a backup image of one of my guest OS, using the command "xm save" as said in the Wiki and in the Xen documentation, but the execution of the command is as follows: [root at aguilaM ~]# xm save aguilaz /xenM/backup/aguilaz-backup2.chk Error: /usr/lib/xen/bin/xc_save 10 17 1 0 0 0 failed Is this a known bug? I haven't found anything related to that. Thanks, Ignacio From igeorgex at googlemail.com Tue Apr 25 23:02:20 2006 From: igeorgex at googlemail.com (George) Date: Wed, 26 Apr 2006 01:02:20 +0200 Subject: [Fedora-xen] Problems saving Domain with "xm save" In-Reply-To: <444E9FE0.3000602@estudio-verona.com> References: <444E9FE0.3000602@estudio-verona.com> Message-ID: https://www.redhat.com/archives/fedora-xen/2006-April/msg00151.html On 4/26/06, Ignacio Verona wrote: > Hi, > > I'm trying to make a backup image of one of my guest OS, using the > command "xm save" as said in the Wiki and in the Xen documentation, but > the execution of the command is as follows: > > [root at aguilaM ~]# xm save aguilaz /xenM/backup/aguilaz-backup2.chk > Error: /usr/lib/xen/bin/xc_save 10 17 1 0 0 0 failed > > Is this a known bug? I haven't found anything related to that. > > Thanks, > Ignacio From yongkang.you at intel.com Wed Apr 26 05:14:19 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 26 Apr 2006 13:14:19 +0800 Subject: [Fedora-xen] PAE and FC5 Xen on 32-bit system Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A21E3@pdsmsx402.ccr.corp.intel.com> You can achieve this by rebuild Xen source with PAE enabled. The command is: "make XEN_TARGET_X86_PAE=y" Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Matthias Bayer >Sent: 2006?4?24? 15:38 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] PAE and FC5 Xen on 32-bit system > >Hi, > >i have a 32-bit FC5 system running with default xen from FC5 >(kernel-xen0-2.6.16-1.2096_FC5 & xen-3.0.1-4). >my system has 4GB of memory but xm info only shows 3584MB available. >i know i need PAE support but the question is if there is a PAE enabled kernel >from FC5 32-bit xen systems available already or if i can turn on PAE support >easily somehow. for me it's important to stay 'supported' and use only 'officialy >availbale' packages. > >if there is no such a PAE enabled version available can somebody explain >what exactly needs to be done to turn PAE support on, i searched the web and >found lots of different instructions but i am not sure which one is the 'correct' >one ? > >thanks for any help ! > >regards, >Matthias > > >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From EJacobsh at connectknowledge.com Wed Apr 26 17:17:06 2006 From: EJacobsh at connectknowledge.com (Eric Jacobshagen) Date: Wed, 26 Apr 2006 11:17:06 -0600 Subject: [Fedora-xen] File operation causes kernel panic Message-ID: Hello, I'm having a problem with a Dell server (PowerEdge 2850) and a recently installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). Whenever I try to copy a larger file (128MB) to the server over the network, the server crashes (register dump on the console, remote sessions stop responding). This happens consistently with Anaconda, Samba and WinSCP3. It has happened with yum twice, although it works most of the time. When I reboot the server with a kernel that does not include Xen (2.6.16-1.2096_FC5), the copying works. I need some help figuring out what my next steps should be. I don't see anything unusual in the xend.log (see below). The xend-debug.log is empty. Is there some other place I should look? Are there any other diagnostic tools to use? Thanks for you help. Eric Jacobshagen CONNECT: The Knowledge Network xend.log: [xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [xend.XendDomainInfo] DEBUG (XendDomainInfo:199) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 24271818792L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details: {'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '512', 'on_crash': 'restart', 'maxmem': '512'} [xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '524288', 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid':'0'} [xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO (SrvServer:114) unix path=/var/lib/xend/xend-socket From Alex.Upton at instinet.com Wed Apr 26 17:25:18 2006 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Wed, 26 Apr 2006 13:25:18 -0400 Subject: [Fedora-xen] File operation causes kernel panic Message-ID: I recently experienced the same issue and noticed that it was related to my snmpd flipping out. I'm not sure if its just a buggy version of snmpd that ships with FC5 or if it's an overall issue with SNMPD and virtualized environments. Disabling snmpd resolved it for me, however I'm hoping this issue is resolved some day. Hope this helps. -Alex -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of EJacobsh at connectknowledge.com Sent: Wednesday, April 26, 2006 1:17 PM To: fedora-xen at redhat.com Subject: [Fedora-xen] File operation causes kernel panic Hello, I'm having a problem with a Dell server (PowerEdge 2850) and a recently installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). Whenever I try to copy a larger file (128MB) to the server over the network, the server crashes (register dump on the console, remote sessions stop responding). This happens consistently with Anaconda, Samba and WinSCP3. It has happened with yum twice, although it works most of the time. When I reboot the server with a kernel that does not include Xen (2.6.16-1.2096_FC5), the copying works. I need some help figuring out what my next steps should be. I don't see anything unusual in the xend.log (see below). The xend-debug.log is empty. Is there some other place I should look? Are there any other diagnostic tools to use? Thanks for you help. Eric Jacobshagen CONNECT: The Knowledge Network xend.log: [xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [xend.XendDomainInfo] DEBUG (XendDomainInfo:199) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 24271818792L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details: {'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '512', 'on_crash': 'restart', 'maxmem': '512'} [xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '524288', 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid':'0'} [xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO (SrvServer:114) unix path=/var/lib/xend/xend-socket -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** From EJacobsh at connectknowledge.com Wed Apr 26 17:30:07 2006 From: EJacobsh at connectknowledge.com (Eric Jacobshagen) Date: Wed, 26 Apr 2006 11:30:07 -0600 Subject: [Fedora-xen] File operation causes kernel panic In-Reply-To: Message-ID: Unfortunately for me, I am not running smnpd... -Eric Alex.Upton at instinet.com wrote on 04/26/2006 11:25:18 AM: > I recently experienced the same issue and noticed that it was related to > my snmpd flipping out. > > I'm not sure if its just a buggy version of snmpd that ships with FC5 or > if it's an overall issue with SNMPD and virtualized environments. > > Disabling snmpd resolved it for me, however I'm hoping this issue is > resolved some day. > > Hope this helps. > -Alex > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of EJacobsh at connectknowledge.com > Sent: Wednesday, April 26, 2006 1:17 PM > To: fedora-xen at redhat.com > Subject: [Fedora-xen] File operation causes kernel panic > > Hello, > I'm having a problem with a Dell server (PowerEdge 2850) and a recently > installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). Whenever > I try to copy a larger file (128MB) to the server over the network, the > server crashes (register dump on the console, remote sessions stop > responding). > > This happens consistently with Anaconda, Samba and WinSCP3. It has > happened with yum twice, although it works most of the time. > > When I reboot the server with a kernel that does not include Xen > (2.6.16-1.2096_FC5), the copying works. > > I need some help figuring out what my next steps should be. I don't see > anything unusual in the xend.log (see below). The xend-debug.log is > empty. Is there some other place I should look? Are there any other > diagnostic tools to use? > > Thanks for you help. > > Eric Jacobshagen > CONNECT: The Knowledge Network > > xend.log: > > [xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO > (SrvDaemon:289) Xend changeset: unavailable . > [xend.XendDomainInfo] DEBUG (XendDomainInfo:199) > XendDomainInfo.recreate({'paused': 0, 'cpu_time': 24271818792L, 'ssidref': > > 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0], > 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb': > > -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, > 'online_vcpus': 2, 'blocked': 0}) > [xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID > 00000000-0000-0000-0000-000000000000. > [xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for > existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing > VM details: > {'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000', > 'on_reboot': 'restart', on_poweroff': 'destroy', 'name': 'Domain-0', > 'vcpus': '2', 'vcpu_avail': '3', 'memory': '512', 'on_crash': 'restart', > 'maxmem': '512'} > [xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: > {'cpu/0/availability': 'online', 'memory/target': '524288', > 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': > '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid':'0'} > [xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO > (SrvServer:114) unix path=/var/lib/xend/xend-socket > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > ***************************************************************** > <<>> > > In compliance with applicable rules and regulations, Instinet > reviews and archives incoming and outgoing email communications, > copies of which may be produced at the request of regulators. > This message is intended only for the personal and confidential > use of the recipients named above. If the reader of this email > is not the intended recipient, you have received this email in > error and any review, dissemination, distribution or copying is > strictly prohibited. If you have received this email in error, > please notify the sender immediately by return email and > permanently delete the copy you received. > > Instinet accepts no liability for any content contained in the > email, or any errors or omissions arising as a result of email > transmission. Any opinions contained in this email constitute > the sender's best judgment at this time and are subject to change > without notice. Instinet does not make recommendations of a > particular security and the information contained in this email > should not be considered as a recommendation, an offer or a > solicitation of an offer to buy and sell securities. > > ***************************************************************** > From c.reiter at gmx.net Wed Apr 26 18:22:43 2006 From: c.reiter at gmx.net (Christian Reiter) Date: Wed, 26 Apr 2006 20:22:43 +0200 Subject: [Fedora-xen] Multiple virtual to physical nic setup docs PLEASE! In-Reply-To: References: Message-ID: <444FBA73.4090304@gmx.net> Hi Alex! May this link can help you: http://lists.xensource.com/archives/html/xen-users/2006-03/msg00109.html chris Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From dmourati at gmail.com Wed Apr 26 18:40:21 2006 From: dmourati at gmail.com (Demetri Mouratis) Date: Wed, 26 Apr 2006 11:40:21 -0700 Subject: [Fedora-xen] Xen Crash at Boot on Dell PE 830 Running FC 5 Message-ID: <3cc2cbc40604261140s1b147e8ft8d76ff62603ed4c0@mail.gmail.com> [cross posted to xen-users at lists.xensource.com] Greetings, I'm having some trouble getting my new workstation, a Dell PE 830, up and running Xen on Fedora Core 5. The last step I see in the boot process is udev which completes with the standard [OK], then my monitor turns blank and looses any signal from my machine. If necessary, I could connect a serial port to get additional info on exactly where it is crashing. I'm using this machine as my desktop so I'd like to run X in the dom0 if possible. Please let me know if doing so is considered poor form with Xen. I've gone through the install process on an older Dell workstation successfully following the Fedora Xen Quickstart FC 5 guide here: http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 The only way I've been able to work around this issue is to edit my /etc/inittab and set the default run level to 3 in which case the machine comes up clean. I've verified that selinux is disabled as I've seen some info to the effect that selinux and the nvidia drivers may have some issue. I'm hoping I can pass some argument at boot time to make this work or otherwise tweak something in the bios to get the xen kernel to boot and support X. Thanks in advance for any hints or tips. Here's the output of /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping : 9 cpu MHz : 2800.198 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr lahf_lm bogomips : 5606.72 processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping : 9 cpu MHz : 2800.198 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr lahf_lm bogomips : 5600.31 And my grub.conf: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol01 # initrd /initrd-version.img #boot=/dev/sda default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz- 2.6.16-1.2080_FC5 module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol01 rhgb quiet module /initrd-2.6.16-1.2080_FC5xen0.img title Fedora Core (2.6.15-1.2054_FC5smp) root (hd0,0) kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/VolGroup00/LogVol01 rhgb quiet initrd /initrd-2.6.15-1.2054_FC5smp.img -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.reiter at gmx.net Wed Apr 26 20:34:16 2006 From: c.reiter at gmx.net (Christian Reiter) Date: Wed, 26 Apr 2006 22:34:16 +0200 Subject: [Fedora-xen] Xen Crash at Boot on Dell PE 830 Running FC 5 In-Reply-To: <3cc2cbc40604261140s1b147e8ft8d76ff62603ed4c0@mail.gmail.com> References: <3cc2cbc40604261140s1b147e8ft8d76ff62603ed4c0@mail.gmail.com> Message-ID: <444FD948.2040802@gmx.net> Hi! In my Case (HP DL145 Single SingleCore Opteron) it was helpful to turn of acpi and apic: Try changing your grub.conf to: ==============grub.conf============== title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz- 2.6.16-1.2080_FC5 noacpi noapic acpi=off module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol01 noacpi noapic acpi=off module /initrd-2.6.16-1.2080_FC5xen0.img ==============End of grub.conf============== HTH, chris Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From denis.forveille at gmail.com Wed Apr 26 23:00:16 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Wed, 26 Apr 2006 19:00:16 -0400 Subject: [Fedora-xen] How to expand the file created by xenguest-install? In-Reply-To: <200604251118.39492.lamont@gurulabs.com> References: <444C1972.6020708@gmail.com> <1145925717.2834.3.camel@aglarond.local> <444D8D42.3090505@gmail.com> <200604251118.39492.lamont@gurulabs.com> Message-ID: <444FFB80.2030801@gmail.com> An HTML attachment was scrubbed... URL: From kwan at digitalhermit.com Thu Apr 27 00:31:33 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Wed, 26 Apr 2006 20:31:33 -0400 (EDT) Subject: [Fedora-xen] Expanding a VBD in FC5 In-Reply-To: <444FFB80.2030801@gmail.com> References: <444C1972.6020708@gmail.com> <1145925717.2834.3.camel@aglarond.local> <444D8D42.3090505@gmail.com> <200604251118.39492.lamont@gurulabs.com> <444FFB80.2030801@gmail.com> Message-ID: <50302.192.168.8.28.1146097893.squirrel@digitalhermit.com> Okay... I think I've figured out how to do this.. Problem: I created a volume backed DomU on a 3G logical volume. The DomU itself used LVM to manage disks. I needed to expand the disk (i.e., the LVM on the Dom0). The previous workaround was to add another LV in the Dom0 and assign it to the DomU. This created a second xvdb in the domU. I used standard LVM tools to create a PV and assign it to the original volume group. E.g.: My xm-fc5-005 initially contained: name = "xm-fc5-005" memory = "256" disk = [ 'phy:/dev/rootvg/xm-fc4-005_lv,xvda,w'] vif = [ 'mac=00:16:3e:20:48:ae' ] bootloader="/usr/bin/pygrub" I added another disk by creating a new LV in dom0 and assigning with: disk = [ 'phy:/dev/rootvg/xm-fc4-005_lv,xvda,w',\ 'phy:/dev/rootvg/xm-fc5-005_lv2,xvdb,w' ] The above works fine, and is probably no less efficient than the method that follows, but it felt kind of kludgey to add space that way. The second method is to lvresize the original VBD and use pvresize in the domU: lvresize -L +1G /dev/rootvg/xm-fc4-005_lv Then in the domU: First, determine the PV device by running pvdisplay and getting the PV Name. In this case, xvda2. Next resize it: pvresize --setphysicalvolumesize 4G /dev/xvda2 pvresize appears to only be available in FC5... alas. If you're not running LVMs inside the domU, you'd use parted (or qparted) to resize. -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From phil at pricom.com.au Fri Apr 28 01:06:39 2006 From: phil at pricom.com.au (Philip Rhoades) Date: Fri, 28 Apr 2006 11:06:39 +1000 Subject: [Fedora-xen] Old serial mouse problem Message-ID: <1146186399.29318.13.camel@prix.pricom.com.au> People, I have been using a Logitech Serial Mouseman for some years quite happily on various RHx and now FC5 but I have to manually fix: /etc/sysconfig/mouse: FULLNAME="Generic - 3 Button Mouse (serial)" MOUSETYPE="Microsoft" XEMU3="no" XMOUSETYPE="Microsoft" IMOUSETYPE="ms" DEVICE=/dev/ttyS0 usually /etc/X11/x.org is OK with: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "yes" EndSection but when I try and boot vmlinuz-2.6.16-1.2080_FC5xen0 I don't get a mouse . . How do I fix this? (short of upgrading to a PS2 mouse). Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:(0)411-185-652 Fax: +61:(0)2-8221-9599 E-mail: phil at pricom.com.au From yongkang.you at intel.com Fri Apr 28 07:07:48 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 28 Apr 2006 15:07:48 +0800 Subject: [Fedora-xen] Old serial mouse problem Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A2200@pdsmsx402.ccr.corp.intel.com> Just have a quickly check. The default Xen0 kernel doesn't build in Serial Mouse. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Philip Rhoades >Sent: 2006?4?28? 9:07 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Old serial mouse problem > >People, > >I have been using a Logitech Serial Mouseman for some years quite >happily on various RHx and now FC5 but I have to manually fix: > >/etc/sysconfig/mouse: > >FULLNAME="Generic - 3 Button Mouse (serial)" >MOUSETYPE="Microsoft" >XEMU3="no" >XMOUSETYPE="Microsoft" >IMOUSETYPE="ms" >DEVICE=/dev/ttyS0 > >usually /etc/X11/x.org is OK with: > >Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "IMPS/2" > Option "Device" "/dev/input/mice" > Option "ZAxisMapping" "4 5" > Option "Emulate3Buttons" "yes" >EndSection > >but when I try and boot vmlinuz-2.6.16-1.2080_FC5xen0 I don't get a >mouse . . > >How do I fix this? (short of upgrading to a PS2 mouse). > >Thanks, > >Phil. >-- >Philip Rhoades > >Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) >GPO Box 3411 >Sydney NSW 2001 >Australia >Mobile: +61:(0)411-185-652 >Fax: +61:(0)2-8221-9599 >E-mail: phil at pricom.com.au > > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen