From tony at emitony.com Wed Nov 1 20:18:51 2006 From: tony at emitony.com (Tony Coffman) Date: Wed, 1 Nov 2006 15:18:51 -0500 (EST) Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 Message-ID: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> Has anybody already done any writeups on the process to get a FC5 Xen0 moved to FC6? I've been running a semi-production Fedora+Xen rig since FC4. The last transition (FC4/Xen2 - FC5/Xen3pre) was pretty much a PITA and this next step seems to be more of the same so I'd like to help out by documenting it as I run through it. Regards, --Tony Coffman From kamal.behpoornia at intel.com Wed Nov 1 23:29:56 2006 From: kamal.behpoornia at intel.com (Behpoornia, Kamal) Date: Wed, 1 Nov 2006 15:29:56 -0800 Subject: [Fedora-xen] Installing winXP using virtual manager Message-ID: I am trying to install WinXP as a virtual machine on Fedora 6. I go through the steps using the Virtual manager in Fed6. It gets to the point where WinXP installation needs to reboot to proceed with the installation. Once it shuts down I am no longer able to start it and continue with the installation. What do I need to do after it reboots in the Virtual manager? How do I get it to start again? Thank you, - Kam -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob at comwifinet.com Wed Nov 1 23:51:28 2006 From: rob at comwifinet.com (rob at comwifinet.com) Date: Wed, 1 Nov 2006 18:51:28 -0500 Subject: [Fedora-xen] Patch for Bugzilla 211090 works great Message-ID: <380-220061131235128761@M2W040.mail2web.com> Daniel's patch worked great on our 2.6.18-1.2200.fc5xen0 i386 this evening. Thank you. -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . From m3freak at rogers.com Thu Nov 2 00:30:52 2006 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Wed, 01 Nov 2006 19:30:52 -0500 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> Message-ID: <1162427452.8227.13.camel@krs> On Wed, 2006-11-01 at 15:18 -0500, Tony Coffman wrote: > Has anybody already done any writeups on the process to get a FC5 Xen0 > moved to FC6? > > I've been running a semi-production Fedora+Xen rig since FC4. The last > transition (FC4/Xen2 - FC5/Xen3pre) was pretty much a PITA and this next > step seems to be more of the same so I'd like to help out by documenting > it as I run through it. If you don't have anything running in dom0, shouldn't it be fairly straight forward? Assuming that you're using LVM for your domU(s): 1. Backup domU(s) 2. Backup domO 3. Install FC6 (leave domU(s) alone) 4. Boo with xen kernel 5. Edit domU configs so that "kernel" and "ramdisk" point to the new kernel. 6. Boot domU(s) My domO used to be a RHEL 4 box running the xen packages from xensource. I converted it to a FC5 box earlier this year. It was painless. The domUs came up right away. Of course, my setup is fairly simple. Right now, I have three domUs, and one bridge. I'd be interested in hearing exactly what problems you had when you made the switch from FC4 to FC5. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 19:18:51 up 3 days, 13:48, 3 users, load average: 0.55, 0.60, 0.62 From javahollic at gmail.com Thu Nov 2 11:15:20 2006 From: javahollic at gmail.com (axb) Date: Thu, 02 Nov 2006 11:15:20 +0000 Subject: [Fedora-xen] Ubuntu/virt-manager ? Message-ID: <1162466121.18078.8.camel@localhost.localdomain> Greetings! I've been trying to get virt-manager running on AMD64 Ubuntu 6.10, both virt-manager-0.2.5 and libvirt-0.1.8 compile and install successfully but I cant run virt manager, I get some seeingly simple error: Traceback (most recent call last): File "/usr/local/share/virt-manager/virt-manager.py", line 104, in ? from virtManager.engine import vmmEngine File "/usr/local/share/virt-manager/virtManager/engine.py", line 33, in ? from virtManager.create import vmmCreate File "/usr/local/share/virt-manager/virtManager/create.py", line 25, in ? import virtinst ImportError: No module named virtinst The libvert libraries are in /usr/local/lib, and similar under /usr/local/lib/python2.4/site-packages. Im a python noob, and have tried updating the PYTHONPATH to include these to folders explicity, also adding the following to virt-manager.py : sys.path.append('/usr/local/lib/python2.4/site-packages') sys.path.append('/usr/local/lib') None of this seem to make any difference. Im sure there will be other problems, but this seems such a basic problem - I just dont know how to fix it. Anyone got an idea? Thanks. andy From tony at emitony.com Thu Nov 2 16:24:03 2006 From: tony at emitony.com (Tony Coffman) Date: Thu, 02 Nov 2006 11:24:03 -0500 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <1162427452.8227.13.camel@krs> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> Message-ID: <454A1BA3.7080606@emitony.com> Kanwar Ranbir Sandhu wrote: > If you don't have anything running in dom0, shouldn't it be fairly > straight forward? Assuming that you're using LVM for your domU(s): > > 1. Backup domU(s) > 2. Backup domO > 3. Install FC6 (leave domU(s) alone) > 4. Boo with xen kernel > 5. Edit domU configs so that "kernel" and "ramdisk" point to the new > kernel. > 6. Boot domU(s) > > My domO used to be a RHEL 4 box running the xen packages from xensource. > I converted it to a FC5 box earlier this year. It was painless. The > domUs came up right away. > > Of course, my setup is fairly simple. Right now, I have three domUs, > and one bridge. > > I'd be interested in hearing exactly what problems you had when you made > the switch from FC4 to FC5. > > Regards, > > Ranbir > Thanks for your response. I suppose I'm little bit of a neatnik. I like to have my domU kernels installed into both the dom0 and into the domU. I install them into the domU so that I don't have to manually copy modules into the domU everytime I make a kernel change. With your process above how do you handle the absence of the xennet kernel module in your domU's? Or did you just upgrade the domU's at the same time? I do use LVM for guests and there is nothing running in dom0. Since FC6 DomU kernel won't run on FC5 dom0 I'm thinking about one of these approaches Approach A - Upgrade domU's first, then upgrade dom0 1. Upgrade domU's to FC6 over time but continue to run an FC5 domU kernel. This requires that I uninstall HAL in the domU's due to an RPM dependancy requirement but that works for my purposes (simple servers). 2. Upgrade the dom0 to FC6 and then switch my Fedora domU's to run the FC6 domU kernel Approach B - Upgrade the dom0 first then upgrade the domU's 1. Upgrade (or perform a parallel fresh install) of the dom0 with FC6. 2. Run the FC6 domU kernel in all domU's. This will probably involved copying some kernel modules manually into the filesystem for each domU (xennet and maybe the framebuffer console modules? I haven't tried this yet so I'm not sure.) 3. Upgrade the domU's over time to FC6. This whole approach only really deals with Fedora domU's. I have a few others guests that I boot occasionally that I leave out of this discussion to keep it focused on the Fedora issues involved. For the FC4 -> FC5 transition I used approach B with great success. I used that because I needed time to get the domU's migrated on a scheduled basis. It'll be interesting to see if there are any additional issues. I'm looking forward to XEN ABI and API stability in the future as it should really make some of these issues easier to deal with. Regards, --Tony Coffman From berrange at redhat.com Thu Nov 2 19:11:39 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 2 Nov 2006 19:11:39 +0000 Subject: [Fedora-xen] Ubuntu/virt-manager ? In-Reply-To: <1162466121.18078.8.camel@localhost.localdomain> References: <1162466121.18078.8.camel@localhost.localdomain> Message-ID: <20061102191139.GE4786@redhat.com> On Thu, Nov 02, 2006 at 11:15:20AM +0000, axb wrote: > Greetings! > > I've been trying to get virt-manager running on AMD64 Ubuntu 6.10, both > virt-manager-0.2.5 and libvirt-0.1.8 compile and install successfully > but I cant run virt manager, I get some seeingly simple error: > > Traceback (most recent call last): > File "/usr/local/share/virt-manager/virt-manager.py", line 104, in ? > from virtManager.engine import vmmEngine > File "/usr/local/share/virt-manager/virtManager/engine.py", line 33, > in ? > from virtManager.create import vmmCreate > File "/usr/local/share/virt-manager/virtManager/create.py", line 25, > in ? > import virtinst > ImportError: No module named virtinst As well as virt-manager & libvirt, you need to install python-virtinst which provides a higher level API around libvirt for provisioning guest virtual machines. The mercurial repo is here: http://hg.et.redhat.com/virt/applications/virtinst--devel Or you can get the tar.gz from the src.rpm files in FC6. Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From acathrow at redhat.com Thu Nov 2 21:13:24 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Thu, 02 Nov 2006 16:13:24 -0500 Subject: [Fedora-xen] Installing winXP using virtual manager In-Reply-To: References: Message-ID: <1162502004.21543.9.camel@amd.cathrow.org> Presuming that you called your domain "winXP" and your winxp install image is in /opt/disks/ and is called winxp.iso Run "xm list" do verify that the domain is not running. Edit /etc/xen/winXP file. you'll have a line for disk that looks something like: disk=[ 'file:/my/vm/location/disk.img,ioemu:hda,w',] Edit that line to include your winxp cd. disk=[ 'file:/my/vm/location/disk.img,ioemu:hda,w','file:/opt/disks/winxp.iso,hdc:cdrom,r',] If you have a boot= line then make sure it's boot = 'c' Then start the domain with xm create winXP On Wed, 2006-11-01 at 15:29 -0800, Behpoornia, Kamal wrote: > I am trying to install WinXP as a virtual machine on Fedora 6. > > > > I go through the steps using the Virtual manager in Fed6. It gets to > the point where WinXP installation needs to reboot to proceed with the > installation. Once it shuts down I am no longer able to start it and > continue with the installation. > > > > What do I need to do after it reboots in the Virtual manager? How do I > get it to start again? > > > > Thank you, > > - Kam > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From robin-lists at robinbowes.com Thu Nov 2 21:30:49 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Thu, 02 Nov 2006 21:30:49 +0000 Subject: [Fedora-xen] xenguest-install.py with multiple disks? Message-ID: Hi, I've successfully used xenguest-install.py to do a kickstart install of FC5 as follows: xenguest-install.py --name=guest1 --file=/dev/vg01/lv_guest1_vm --ram=384 --location=http://mirrors.kernel.org/fedora/core/5/i386/os/ --extra-args="ip=192.168.23.229 netmask=255.255.255.248 gateway=192.168.23.225 dns=192.168.2.203,192.168.2.204 ks=http://example.com/kickstart/guest1-fc5.cfg" This presents a lv to the guest and the kickstart config does all the partioning (I use lvm in kickstart too!). However, I've decided that the best way to use multiple partitions with xen guests is to define them as logical volumes on the Dom0 host and pass them to the DomU guest as separate partitions. e.g. lvcreate --name guest1_root --size 1.2G /dev/vg01 lvcreate --name guest1_usr --size 800M /dev/vg01 lvcreate --name guest1_home --size 5G /dev/vg01 lvcreate --name guest1_var --size 15G /dev/vg01 lvcreate --name guest1_swap --size 2G /dev/vg01 Then the Xen guest disk configuration would be something like: disk = [ 'phy:/dev/vg01/guest1_root,xvda1,w', 'phy:/dev/vg01/guest1_usr,xvda2,w', 'phy:/dev/vg01/guest1_home,xvda3,w', 'phy:/dev/vg01/guest1_var,xvda4,w', 'phy:/dev/vg01/guest1_swap,xvda5,w' ] i.e. each lv on the Dom0 will appear as a separate partition inside the DomU guest. The benefit of this is that all partition management will be done in Dom0, e.g. To increase a partition size, I can shutdown the guest, increase the lv size, grow the FS and restart the guest. My question is: How can I specify multiple disks for the Xen0 guest and launch a kickstart installation? Thanks for any thoughts. R. From bench at silentmedia.com Thu Nov 2 21:53:50 2006 From: bench at silentmedia.com (Ben) Date: Thu, 2 Nov 2006 13:53:50 -0800 (PST) Subject: [Fedora-xen] xenguest-install.py with multiple disks? In-Reply-To: References: Message-ID: I wrote it a while ago, but check out the hacked verison of xenguest-install.py I attached here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185860 I assume it would still work.... On Thu, 2 Nov 2006, Robin Bowes wrote: > Hi, > > I've successfully used xenguest-install.py to do a kickstart install of > FC5 as follows: > > xenguest-install.py --name=guest1 --file=/dev/vg01/lv_guest1_vm > --ram=384 --location=http://mirrors.kernel.org/fedora/core/5/i386/os/ > --extra-args="ip=192.168.23.229 netmask=255.255.255.248 > gateway=192.168.23.225 dns=192.168.2.203,192.168.2.204 > ks=http://example.com/kickstart/guest1-fc5.cfg" > > This presents a lv to the guest and the kickstart config does all the > partioning (I use lvm in kickstart too!). > > However, I've decided that the best way to use multiple partitions with > xen guests is to define them as logical volumes on the Dom0 host and > pass them to the DomU guest as separate partitions. > > e.g. > lvcreate --name guest1_root --size 1.2G /dev/vg01 > lvcreate --name guest1_usr --size 800M /dev/vg01 > lvcreate --name guest1_home --size 5G /dev/vg01 > lvcreate --name guest1_var --size 15G /dev/vg01 > lvcreate --name guest1_swap --size 2G /dev/vg01 > > Then the Xen guest disk configuration would be something like: > > disk = [ 'phy:/dev/vg01/guest1_root,xvda1,w', > 'phy:/dev/vg01/guest1_usr,xvda2,w', > 'phy:/dev/vg01/guest1_home,xvda3,w', > 'phy:/dev/vg01/guest1_var,xvda4,w', > 'phy:/dev/vg01/guest1_swap,xvda5,w' ] > > i.e. each lv on the Dom0 will appear as a separate partition inside the > DomU guest. The benefit of this is that all partition management will be > done in Dom0, e.g. To increase a partition size, I can shutdown the > guest, increase the lv size, grow the FS and restart the guest. > > My question is: > > How can I specify multiple disks for the Xen0 guest and launch a > kickstart installation? > > Thanks for any thoughts. > > R. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From mfreemon at ncsa.uiuc.edu Thu Nov 2 23:15:56 2006 From: mfreemon at ncsa.uiuc.edu (Mike Freemon) Date: Thu, 02 Nov 2006 17:15:56 -0600 Subject: [Fedora-xen] Console Hang On Boot Using 2.6.18-1.2200.fc5xenU In-Reply-To: <45350169.2030001@freedomics.com> References: <45350169.2030001@freedomics.com> Message-ID: <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> Was there any responses on this email from 10/17? I'm seeing the same problem on my system: # uname -a Linux grids1 2.6.18-1.2200.fc5xen0 #1 SMP Sat Oct 14 17:49:47 EDT 2006 i686 i686 i386 GNU/Linux # rpm -qa|grep xen kernel-xenU-2.6.18-1.2200.fc5 xen-3.0.3-1.fc5 kernel-xen0-devel-2.6.18-1.2200.fc5 kernel-xenU-devel-2.6.18-1.2200.fc5 kernel-xen0-2.6.18-1.2200.fc5 - Mike At 10/17/2006 10:14 AM Tuesday, Stan Larson wrote: >Sorry if this is a repeat. I haven't found searchable archives for this >forum yet. > >1. I installed FC5 + xen on a base system and performed "yum -y upgrade". >2. I then created and booted a DomU using the original FC5 disk. So far, >so good. >3. In the DomU, I performed "yum -y upgrade" and rebooted the DomU using >the new kernel, 2.6.18-1.2200.fc5xenU. > >The DomU boots OK, but returns control or starts a shell. The console >starts all services and then just hangs. I can ssh into the domain >from another window and all is well. If I break from the console using >CRTL-] and then return using xm console, I'm still stuck. If I boot to >the old kernel (the one provided by the FC5 install disk, aka >2.6.15-1.2054_FC5xenU) the problem doesn't occur. > >Any suggestions? > >-- >Stan Larson >I/S Manager >Freedom Sales & Marketing >P: (727) 835-1150 >F: (727) 835-1151 >stan at freedomics.com >www.freedomics.com > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From berrange at redhat.com Thu Nov 2 23:25:05 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 2 Nov 2006 23:25:05 +0000 Subject: [Fedora-xen] Console Hang On Boot Using 2.6.18-1.2200.fc5xenU In-Reply-To: <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> References: <45350169.2030001@freedomics.com> <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> Message-ID: <20061102232505.GB30017@redhat.com> On Thu, Nov 02, 2006 at 05:15:56PM -0600, Mike Freemon wrote: > Was there any responses on this email from 10/17? I'm seeing the same > problem on my system: I posted a reply to the same problem reported in another thread - I mised this thread originally. The solution is to install new kudzu in the DomU from updates-testing. This new kudzu ensures that the agetty process gets spawned on the xvc0 console as well as the paravirt framebuffer. > # uname -a > Linux grids1 2.6.18-1.2200.fc5xen0 #1 SMP Sat Oct 14 17:49:47 EDT 2006 i686 > i686 i386 GNU/Linux > > # rpm -qa|grep xen > kernel-xenU-2.6.18-1.2200.fc5 > xen-3.0.3-1.fc5 > kernel-xen0-devel-2.6.18-1.2200.fc5 > kernel-xenU-devel-2.6.18-1.2200.fc5 > kernel-xen0-2.6.18-1.2200.fc5 > > > At 10/17/2006 10:14 AM Tuesday, Stan Larson wrote: > >Sorry if this is a repeat. I haven't found searchable archives for this > >forum yet. > > > >1. I installed FC5 + xen on a base system and performed "yum -y upgrade". > >2. I then created and booted a DomU using the original FC5 disk. So far, > >so good. > >3. In the DomU, I performed "yum -y upgrade" and rebooted the DomU using > >the new kernel, 2.6.18-1.2200.fc5xenU. > > > >The DomU boots OK, but returns control or starts a shell. The console > >starts all services and then just hangs. I can ssh into the domain > >from another window and all is well. If I break from the console using > >CRTL-] and then return using xm console, I'm still stuck. If I boot to > >the old kernel (the one provided by the FC5 install disk, aka > >2.6.15-1.2054_FC5xenU) the problem doesn't occur. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jeff_301 at msn.com Thu Nov 2 22:52:48 2006 From: jeff_301 at msn.com (Jeff Stockett) Date: Thu, 2 Nov 2006 16:52:48 -0600 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 Message-ID: My notebook has a Turion 64 x2 processor, 2GB of RAM, FC 6 x86-64, and booting the WinXP VM off the CD works fine (setup copies over all the files to the virtual HDD), but when the VM attempts to reboot off the hard drive, it fails/hangs. Running "xm dmesg" gives: (XEN) (GUEST: 3) (XEN) (GUEST: 3) ata0-0: PCHS=8322/16/63 translation=lba LCHS=522/255/63 (XEN) (GUEST: 3) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (4096 MBytes) (XEN) (GUEST: 3) ata0 slave: Unknown device (XEN) (GUEST: 3) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom (XEN) (GUEST: 3) ata1 slave: Unknown device (XEN) (GUEST: 3) (XEN) (GUEST: 3) Booting from Hard Disk... (XEN) (GUEST: 3) unsupported PCI BIOS function 0x0E (XEN) (GUEST: 3) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) (GUEST: 3) *** int 15h function AX=E980, BX=00F2 not yet supported! (XEN) hvm_vioapic_write_indirect: version register read only (XEN) hvm_vioapic_write_indirect: version register read only (XEN) hvm_vioapic_write_indirect: version register read only (XEN) This hvm_vlapic is for P4, no work for De-assert init I see from googling, that this bug has been reported once before (last month with a rawhide build) - but no answers. A little further googling indicates that one possible workaround might be to hit F5 (when it is asking for F6 to load drivers) during the setup process and specify the computer as not having APIC but the version of VNC or whatever console emulator that comes with Virtual Machine Manager doesn't seem to pass function keys thru (F2, F5, or F6 don't appear to work). I'm at a loss on where to go from here, except to perhaps start compiling everything from latest sources (which would be alot of trouble). Advice??? Below is my winxp VM config file: name = "winxp" builder = "hvm" memory = "256" disk = [ 'phy:/dev/vg0/domuwinxp,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ] boot = 'c' vif = [ 'type=ioemu, mac=00:16:3e:45:71:31, bridge=xenbr0', ] uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' From berrange at redhat.com Thu Nov 2 23:31:56 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 2 Nov 2006 23:31:56 +0000 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 In-Reply-To: References: Message-ID: <20061102233156.GC30017@redhat.com> On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett wrote: > > I see from googling, that this bug has been reported once before > (last month with a rawhide build) - but no answers. A little further > googling indicates that one possible workaround might be to hit F5 > (when it is asking for F6 to load drivers) during the setup process > and specify the computer as not having APIC but the version of VNC > or whatever console emulator that comes with Virtual Machine Manager > doesn't seem to pass function keys thru (F2, F5, or F6 don't appear > to work). I'm at a loss on where to go from here, except to perhaps > start compiling everything from latest sources (which would be alot > of trouble). > > builder = "hvm" > memory = "256" > disk = [ 'phy:/dev/vg0/domuwinxp,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ] > boot = 'c' > vif = [ 'type=ioemu, mac=00:16:3e:45:71:31, bridge=xenbr0', ] > uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2" > device_model = "/usr/lib64/xen/bin/qemu-dm" > kernel = "/usr/lib/xen/boot/hvmloader" > vnc=1 > vncunused=1 > apic=1 > acpi=1 Try toggling these last two settings here - one of the 4 different combos of acpi & apic may well help. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From adrian at creative.net.au Thu Nov 2 23:53:03 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Fri, 3 Nov 2006 07:53:03 +0800 Subject: [Fedora-xen] Console Hang On Boot Using 2.6.18-1.2200.fc5xenU In-Reply-To: <20061102232505.GB30017@redhat.com> References: <45350169.2030001@freedomics.com> <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> <20061102232505.GB30017@redhat.com> Message-ID: <20061102235302.GT15618@skywalker.creative.net.au> On Thu, Nov 02, 2006, Daniel P. Berrange wrote: > On Thu, Nov 02, 2006 at 05:15:56PM -0600, Mike Freemon wrote: > > Was there any responses on this email from 10/17? I'm seeing the same > > problem on my system: > > I posted a reply to the same problem reported in another thread - I mised > this thread originally. The solution is to install new kudzu in the DomU > from updates-testing. This new kudzu ensures that the agetty process gets > spawned on the xvc0 console as well as the paravirt framebuffer. If you're like me and run non-Redhat guests under FC5 + redhat xen kernels you'll have to do it maunally: /etc/inittab: (assuming you're using getty and not already using 'co' in your inittab) co:2345:respawn:/sbin/getty 38400 xvc0 and add xvc0 to /etc/securetty so you can login as root on the console. michelle:~# uname -a Linux michelle 2.6.18-1.2200.fc5xenU #1 SMP Sat Oct 14 18:06:38 EDT 2006 i686 GNU/Linux michelle:~# cat /etc/debian_version 3.1 michelle:~# Adrian From robin-lists at robinbowes.com Fri Nov 3 00:16:52 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 03 Nov 2006 00:16:52 +0000 Subject: [Fedora-xen] Re: xenguest-install.py with multiple disks? In-Reply-To: References: Message-ID: Ben wrote: > I wrote it a while ago, but check out the hacked verison of > xenguest-install.py I attached here: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185860 > > I assume it would still work.... It sure does! I updated it to include some of the changes added to the more recent xenguest-install.py (uuid stuff, mainly). One small snag... I ran it as follows: xenguest-install-md.py --bridges="xenbr0" --file="/dev/vg01/guest1_root /dev/vg01/guest1_usr /dev/vg01/guest1_home /dev/vg01/guest1_var /dev/vg01/guest1_swap" --name=guest1 --ram=256 --location=http://mirrors.kernel.org/fedora/core/5/i386/os/ --extra-args="ip=192.168.23.230 netmask=255.255.255.248 gateway=192.168.23.225 dns=192.168.2.203,192.168.2.204 ks=http://example.com/kickstart/guest1-fc5.cfg" Each of the defined partitions were mapped as a physical disk in the guest, i.e. xvda, xvdb, xvdc, etc. I'd like them to appear as xvda1, xvda2, xvda3, etc. Any idea how to change the code to do that? Thanks, R. From bench at silentmedia.com Fri Nov 3 00:25:45 2006 From: bench at silentmedia.com (Ben) Date: Thu, 2 Nov 2006 16:25:45 -0800 (PST) Subject: [Fedora-xen] Re: xenguest-install.py with multiple disks? In-Reply-To: References: Message-ID: On Fri, 3 Nov 2006, Robin Bowes wrote: > Each of the defined partitions were mapped as a physical disk in the > guest, i.e. xvda, xvdb, xvdc, etc. > > I'd like them to appear as xvda1, xvda2, xvda3, etc. > > Any idea how to change the code to do that? Er, woops, sorry, didn't read your original post close enough. No, I have no idea how you would do that, or even if it's possible, or even *why* you would want to do that? From jeff_301 at msn.com Fri Nov 3 01:32:51 2006 From: jeff_301 at msn.com (Jeff Stockett) Date: Thu, 2 Nov 2006 19:32:51 -0600 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 Message-ID: Yep - I already tried that with the following results: apic acpi 1 1 VM hangs with aforementioned apic error 0 1 VM crashes 1 0 VM crashes 0 0 VM hangs with aforementioned apic error I can post the dmesg info for the crash cases if you think that would be helpful. I may try grabbing vncclient from somewhere and seeing if I can get the F5 hack to work on a fresh reinstall. I think Xen will be quite handy once the kinks are worked out and applaud the Fedora team for attempting to make it easy and including it in FC6. Thanks for your help. --J ---------------------------------------- > Date: Thu, 2 Nov 2006 23:31:56 +0000 > From: berrange at redhat.com > To: jeff_301 at msn.com > CC: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] problems installing winxp with full virtualization on FC6 > > On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett wrote: > > > > I see from googling, that this bug has been reported once before > > (last month with a rawhide build) - but no answers. A little further > > googling indicates that one possible workaround might be to hit F5 > > (when it is asking for F6 to load drivers) during the setup process > > and specify the computer as not having APIC but the version of VNC > > or whatever console emulator that comes with Virtual Machine Manager > > doesn't seem to pass function keys thru (F2, F5, or F6 don't appear > > to work). I'm at a loss on where to go from here, except to perhaps > > start compiling everything from latest sources (which would be alot > > of trouble). > > > > builder = "hvm" > > memory = "256" > > disk = [ 'phy:/dev/vg0/domuwinxp,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ] > > boot = 'c' > > vif = [ 'type=ioemu, mac=00:16:3e:45:71:31, bridge=xenbr0', ] > > uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2" > > device_model = "/usr/lib64/xen/bin/qemu-dm" > > kernel = "/usr/lib/xen/boot/hvmloader" > > vnc=1 > > vncunused=1 > > apic=1 > > acpi=1 > > Try toggling these last two settings here - one of the 4 different combos > of acpi & apic may well help. > > Regards, > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| > |=- Perl modules: http://search.cpan.org/~danberr/ -=| > |=- Projects: http://freshmeat.net/~danielpb/ -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Nov 3 02:32:48 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 3 Nov 2006 02:32:48 +0000 Subject: [Fedora-xen] Re: xenguest-install.py with multiple disks? In-Reply-To: References: Message-ID: <20061103023248.GA15152@redhat.com> On Fri, Nov 03, 2006 at 12:16:52AM +0000, Robin Bowes wrote: > Ben wrote: > > I wrote it a while ago, but check out the hacked verison of > > xenguest-install.py I attached here: > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185860 > > > > I assume it would still work.... > > It sure does! > > I updated it to include some of the changes added to the more recent > xenguest-install.py (uuid stuff, mainly). > > One small snag... > > I ran it as follows: > > xenguest-install-md.py --bridges="xenbr0" --file="/dev/vg01/guest1_root > /dev/vg01/guest1_usr /dev/vg01/guest1_home /dev/vg01/guest1_var > /dev/vg01/guest1_swap" --name=guest1 --ram=256 > --location=http://mirrors.kernel.org/fedora/core/5/i386/os/ > --extra-args="ip=192.168.23.230 netmask=255.255.255.248 > gateway=192.168.23.225 dns=192.168.2.203,192.168.2.204 > ks=http://example.com/kickstart/guest1-fc5.cfg" > > Each of the defined partitions were mapped as a physical disk in the > guest, i.e. xvda, xvdb, xvdc, etc. Yes, each 'disk' defined in the guest config file maps to a single block device in the guest - hence they appear as distinct device nodes > I'd like them to appear as xvda1, xvda2, xvda3, etc. Then you want multiple partitions instead of multiple disks. > Any idea how to change the code to do that? Define a single disk file in the host & pass it to the guest, and within the guest split it up into multiple partitions. Nb, this doesn't prevent you from accessing individual parititions in the host if you want to - see th kpartx tool http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184aece3efe822be0ef6dd1871cd Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From suyashjape at gmail.com Fri Nov 3 08:26:46 2006 From: suyashjape at gmail.com (suyash jape) Date: Fri, 3 Nov 2006 00:26:46 -0800 Subject: [Fedora-xen] Fwd: FC5 kickstart Error 11 error creating domain (Resource temporarily unavailable) In-Reply-To: <16314edc0611030025s1ea6c7fet90af0dc2619514e0@mail.gmail.com> References: <16314edc0611030025s1ea6c7fet90af0dc2619514e0@mail.gmail.com> Message-ID: <16314edc0611030026i2c236f1ep94dc7409b892cac4@mail.gmail.com> ---------- Forwarded message ---------- From: suyash jape Date: Nov 3, 2006 12:25 AM Subject: FC5 kickstart Error 11 error creating domain (Resource temporarily unavailable) To: xen-users at lists.xensource.com Hi everyone.. I'm trying to automate creation of a DomainU using kickstart utility in Fedora core 5.The command is "xenguest-install.py " along with parameters like VM name,ram, install location . I was able to create a Domain using usual "xm create" command ....but i'm getting the following error with xenguest-install.py >Error 11 error creating domain ('Resource temporarily unavailable') I tried freeing up RAM and disk space...the parameters seem to be correct and resources are available.... If anyone has any idea about the solution (or any links which will lead to the same) ...please let me know Thanks a lot......... -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario at verbelen.org Fri Nov 3 09:24:27 2006 From: mario at verbelen.org (Mario Verbelen) Date: Fri, 03 Nov 2006 10:24:27 +0100 Subject: [Fedora-xen] cobbler problem virt_mem virt_file_size Message-ID: <1162545867.7108.7.camel@leo> Hi, As you can see below there is a bug when you don't use the default virt_ram virt_file_size Even when I give it to the profile add the settings are correctly saved (/var/lib/cobbler/profiles) but when cobbler list you don't see your setting when using koan he also doesn't see the setting my problem is that i don't have 512MB free memory so it fails cobbler profile add --name=fc6test --distro=fc6test --virt-file-size=3 --virt-ram=96 cobbler list defaults kernel options : append devfs=nomount ramdisk_size=16438 lang= vga=788 ksdevice=eth0 distro 1 : fc6test kernel : /boot/vmlinuz-2.6.18-1.2798.fc6xen initrd : /boot/initrd-2.6.18-1.2798.fc6xen.img kernel options : architecture : x86 ks metadata : distro 2 : var_www_cobbler_localmirror_fc6_images_pxeboot kernel : /var/www/cobbler/localmirror/fc6/images/pxeboot/vmlinuz initrd : /var/www/cobbler/localmirror/fc6/images/pxeboot/initrd.img kernel options : architecture : x86 ks metadata : profile 1 : fc6test distro : fc6test kickstart : /etc/cobbler/default.ks kernel options : ks metadata : virt name : fc6test virt file size : virt ram : virt paravirt : profile 2 : var_www_cobbler_localmirror_fc6_images_pxeboot distro : var_www_cobbler_localmirror_fc6_images_pxeboot kickstart : /etc/cobbler/kickstart_fc5.ks kernel options : ks metadata : tree=http://127.0.0.1/localmirror/fc6 virt name : var_www_cobbler_localmirror_fc6_images_pxeboot virt file size : virt ram : virt paravirt : There are no configured System records. koan --virt --profile=fc6test --server=localhost - processing profile: fc6test - fetching configuration for profile: fc6test - url=http://localhost/cobbler/profiles/fc6test - {'kickstart': 'http://127.0.0.1/cobbler/kickstarts/fc6test/ks.cfg', 'name': 'fc6test', 'virt_ram': '', 'virt_paravirt': '', 'kernel_options': 'lang ksdevice=eth0 vga=788 devfs=nomount ramdisk_size=16438', 'virt_name': 'fc6test', 'virt_file_size': '', 'distro': 'fc6test', 'ks_meta': ''} - fetching configuration for distro: fc6test - url=http://localhost/cobbler/distros/fc6test - {'kernel': '/boot/vmlinuz-2.6.18-1.2798.fc6xen', 'ks_meta': '', 'kernel_options': 'lang ksdevice=eth0 vga=788 devfs=nomount ramdisk_size=16438', 'initrd': '/boot/initrd-2.6.18-1.2798.fc6xen.img', 'arch': 'x86', 'name': 'fc6test'} - downloading initrd initrd-2.6.18-1.2798.fc6xen.img to /tmp/initrd-2.6.18-1.2798.fc6xen.img - url=http://localhost/cobbler/images/fc6test/initrd-2.6.18-1.2798.fc6xen.img - downloading kernel vmlinuz-2.6.18-1.2798.fc6xen to /tmp/vmlinuz-2.6.18-1.2798.fc6xen - url=http://localhost/cobbler/images/fc6test/vmlinuz-2.6.18-1.2798.fc6xen - kernel saved = /tmp/vmlinuz-2.6.18-1.2798.fc6xen - initrd saved = /tmp/initrd-2.6.18-1.2798.fc6xen.img - invalid RAM size specified, defaulting to 256 MB - invalid file size specified, defaulting to 1 GB libvir: Xen Daemon error : GET operation failed: No such domain 6 libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 262144 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only -15940 KiB free.') Failed to create domain fc6test Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/koan/app.py", line 96, in main k.run() File "/usr/lib/python2.4/site-packages/koan/app.py", line 154, in run self.do_virt() File "/usr/lib/python2.4/site-packages/koan/app.py", line 295, in do_virt return self.do_net_install("/tmp",after_download) File "/usr/lib/python2.4/site-packages/koan/app.py", line 253, in do_net_install after_download(self, distro_data, profile_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 294, in after_download self.do_virt_net_install(profile_data, distro_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 574, in do_virt_net_install extra=kextra File "/usr/lib/python2.4/site-packages/koan/virtcreate.py", line 196, in start_paravirt_install dom = conn.createLinux(cfgxml, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed') libvirtError: virDomainCreateLinux() failed cat /var/lib/cobbler/profiles --- - distro: &1 var_www_cobbler_localmirror_fc6_images_pxeboot kernel_options: '' kickstart: /etc/cobbler/kickstart_fc5.ks ks_meta: 'tree=http://127.0.0.1/localmirror/fc6' name: *1 virt_file_size: '' virt_name: *1 virt_paravirt: '' virt_ram: '' - distro: fc6test kernel_options: '' kickstart: /etc/cobbler/default.ks ks_meta: '' name: fc6test virt_file_size: 3 virt_name: virtguest virt_paravirt: True virt_ram: 96 From tomas at jikos.cz Fri Nov 3 15:52:10 2006 From: tomas at jikos.cz (Tomas Kouba) Date: Fri, 03 Nov 2006 16:52:10 +0100 Subject: [Fedora-xen] guest boot error: could not find filesystem '/dev/root' Message-ID: <454B65AA.8040108@jikos.cz> Hi, I have installed FC5 (didn't have FC6 media in hand) into a loop-mounted file. I used yum --installroot=/path/ . I have copied modules of the xen kernel into the guest filesystem. Everything went ok. But the kernel does not boot. I use these params in xmdefconfig: kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xen.img" (AFAIK there is no xenU kernels anymore). The guest boot ends with these lines: Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! This problem was presented in this mailing list a while ago: "This is the "blkfront bug", where the initrd scripts try to mount the root filesystem before the vbd disks are attached to the guest domain. " with a remark that it should be fixed now (kernel-xen-2.6.17-1 with a revision number >= 2558) Is it back again or I do something stupid here? Can this be caused by something else? thanks for any advice -- Tomas Kouba From kamal.behpoornia at intel.com Fri Nov 3 19:22:28 2006 From: kamal.behpoornia at intel.com (Behpoornia, Kamal) Date: Fri, 3 Nov 2006 11:22:28 -0800 Subject: [Fedora-xen] Installing winXP using XM config file Message-ID: I have created a config file for installing WinXP as a VM. See listing at the end. I am not able to install WinXP. Here's what happens: 1- I have created my config file 2- I copy the WinXP ISO image to /tmp 3- I issue "xm create myconfig" ==> domain starts. Nothing else comes up on the screen. 4- I issue "xm list" and I see my new VM listed, but the status is 'b' for blocked. However, if I set the boot param in the config file to "d" and issue "create" the domain starts. The status is 'r' but still nothing else happens. Can someone help please? Thank you, - Kamal ******** content of my Config file ***************** import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' name = "Windows_XP" builder = "hvm" memory = "500" disk = [ 'phy:/dev/VG_Guests/WinXP,hda,w', ] vif = [ 'type=ioemu, bridge=xenbr0', ] device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" cdrom = "/tmp/WINXP.iso" boot = "c" sdl=1 stdvga=1 vnc=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' From shobha.ranganathan at intel.com Fri Nov 3 19:26:14 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Fri, 3 Nov 2006 11:26:14 -0800 Subject: [Fedora-xen] Installing winXP using XM config file Message-ID: See if this works with vnc=0. You have it set to 1 in your config file I had a similar problem with FC5 guest. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Behpoornia, Kamal Sent: Friday, November 03, 2006 11:22 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] Installing winXP using XM config file I have created a config file for installing WinXP as a VM. See listing at the end. I am not able to install WinXP. Here's what happens: 1- I have created my config file 2- I copy the WinXP ISO image to /tmp 3- I issue "xm create myconfig" ==> domain starts. Nothing else comes up on the screen. 4- I issue "xm list" and I see my new VM listed, but the status is 'b' for blocked. However, if I set the boot param in the config file to "d" and issue "create" the domain starts. The status is 'r' but still nothing else happens. Can someone help please? Thank you, - Kamal ******** content of my Config file ***************** import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' name = "Windows_XP" builder = "hvm" memory = "500" disk = [ 'phy:/dev/VG_Guests/WinXP,hda,w', ] vif = [ 'type=ioemu, bridge=xenbr0', ] device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" cdrom = "/tmp/WINXP.iso" boot = "c" sdl=1 stdvga=1 vnc=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From karl at athabascau.ca Fri Nov 3 19:52:36 2006 From: karl at athabascau.ca (Karl Stevens) Date: Fri, 03 Nov 2006 12:52:36 -0700 Subject: [Fedora-xen] FC6+xen guest boot issue Message-ID: <454B9E04.9070705@athabascau.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I'm trying to set up Xen using FC6 as dom0, and am having zero success getting any guest OS to run. I've read the quickstart guide, but it's of little use because it makes two very large assumptions: 1. I want to install FC6 as a guest. 2. The hardware has internet access. I want to have RH7.3 running as a guest (but I'll settle for *anything* right now), and the machine I want to install on is behind a firewall, and has no internet access at all. I've tried the Documentation at xensource.com, and even tried downloading images from jailtime.org - no matter what I do, I encounter the following error: 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) (I've tried both hda1 and sda1 as root, neither one works.) The xen config I'm using is as follows: kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" memory = 256 name = "test" vif = [ '' ] disk = ['file:/xen/test.img,sda1,w','file:/xen/test.swap,sda2,w'] root = "/dev/sda1 ro" The file /xen/test.img exists, is not mounted by dom0, and contains a linux system (verified via mount -o loop, and umounted before I try to run xm create.) According to the Xen documentation, I believe this should work. Is there a fc6-specific initrd that I need? Is there any documentation that might provide some insight on installing non-FC6 guests onto a FC6 dom0? Thanks, Karl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFS54Dr6qWhNgoahURAlzNAKCBsyDXeQjAqM8LRHOqqDiSY2+pGQCgv5tY 8lH7mxu89YYArlQFevoxchg= =aiVh -----END PGP SIGNATURE----- __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- From aatrof at gmail.com Fri Nov 3 22:14:16 2006 From: aatrof at gmail.com (Aleksander Trofimowicz) Date: Fri, 3 Nov 2006 23:14:16 +0100 Subject: [Fedora-xen] hvm mode and windows xp (xen 3.0.3-rc3) Message-ID: <759d30a60611031414o593050e5iefbac2c40bf0748b@mail.gmail.com> hello, I'm a bit of a failure at running windows xp in the hvm mode. to be honest nothing went the way it should have on my notebook with turion 64 x2 processor inside. first i was unable to install windows. the only combination of parameters which did not lead to freeze in text phase of instalation of the xp system was acpi=1, apic=1 and vcpu=2. but even that combination resulted in an error message produced by windows installer somewhere in the middle of instalation process. i used qemu alone to install the system without any problems. btw win xp runs surprisingly fast with that emulator. second at windows startup all that could be seen was a blank screen of console. if i tried to run in safe mode, initial text messages appeared, but i was unable to choose the right option, because i had no control over my keyboard (as if key events went unnoticed). and it took ages to reach the counter to zero (which supposed to be set to 30 s - that amount of time you have to decide what mode windows should run in). afterwards well known blank screen appeared. that's all. i tried in vain any reasonable combinatiation of the following domain parameters: acpi, apic and vcpu (eg. apic=0 and vcpu=2 was excluded). the rest were unchanged. i use fedora core 6: xen 3.0.3-rc3 and kernel 2.6.18.1 with a 3 patches that improve thermal and fan control (more details at http://bugzilla.kernel.org/show_bug.cgi?id=7122 and http://bugzilla.kernel.org/show_bug.cgi?id=5534). however using unpatched kernel results in the same behaviour of windows domain. i attached several dumps which you might find useful. any clue what went wrong? -- aleksander -------------- next part -------------- A non-text attachment was scrubbed... Name: xen.info Type: application/octet-stream Size: 1014 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xen.dmesg.init Type: application/octet-stream Size: 6162 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xen.dmesg.winxp.startup Type: application/octet-stream Size: 3935 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xen.dmesg.winxp.startup.with.acpi Type: application/octet-stream Size: 4086 bytes Desc: not available URL: From parsley at linuxjedi.org Fri Nov 3 22:39:29 2006 From: parsley at linuxjedi.org (David Parsley) Date: Fri, 3 Nov 2006 17:39:29 -0500 Subject: [Fedora-xen] hvm mode and windows xp (xen 3.0.3-rc3) In-Reply-To: <759d30a60611031414o593050e5iefbac2c40bf0748b@mail.gmail.com> References: <759d30a60611031414o593050e5iefbac2c40bf0748b@mail.gmail.com> Message-ID: <6b4bb8650611031439j24e11fderf42a734dee116323@mail.gmail.com> Hi, On 11/3/06, Aleksander Trofimowicz wrote: > hello, > > I'm a bit of a failure at running windows xp in the hvm mode. to be > honest nothing went the way it should have on my notebook with turion > 64 x2 processor inside. Just a quick note: I had good luck installing WinXP on FC6 today. Dunno if it'll help you, but I've attached my config file. The big thing that made it work for me: when the Windows installer asks you to press F6 to load drivers, press F5, and select 'Standard PC ...(something)'. Once I did that, it worked great. -- David L. Parsley Linux Systems Engineer, James Madison University "If I have seen further, it is by standing on ye shoulders of giants" - Isaac Newton -------------- next part -------------- A non-text attachment was scrubbed... Name: WinXP Type: application/octet-stream Size: 634 bytes Desc: not available URL: From cruzinthegalaxie at gmail.com Sat Nov 4 12:49:25 2006 From: cruzinthegalaxie at gmail.com (Alex Barger) Date: Sat, 4 Nov 2006 07:49:25 -0500 Subject: [Fedora-xen] Re:FC6+xen guest boot issue Message-ID: <9a858dbe0611040449g732b8270r46802088541bfbb4@mail.gmail.com> Karl, I was in the same spot you are in a couple of days ago. The problem you mention is because you don't have an initrd to tell the kernel what to mount after the kernel boots up. The trick I found is when you make the initrd to use these extra options # mkinitrd --with=xennet --preload=xenblk /boot/$KERNEL-$DOMNAME.img $KERNEL I found these instructions to work out pretty well for building an image ( http://fedoraproject.org/wiki/FedoraXenQuickstart#head-d8c5e7b0f9f95e248fbcb12e26f2e9c3b33f3dbc), except the writer does not use initrd. I don't understand how that works. But I followed the instructions and made an initrd and copied it to my host /boot and then put this line in the xen user config file and it worked for me: ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xenU.img" Since you dont have an internet connection, you could copy the files from the RH7.3 cd's to your drive and then start apache on your local computer. I don't know if 7.3 works with yum, it has been ages since I used that version. You could then make your own yum conf with $HOSTIP = the ip address of your host computer [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log exclude=*-debuginfo gpgcheck=0 obsoletes=1 reposdir=/dev/null [base] name=Fedora Core 4 - $basearch - Base mirrorlist=http://$HOSTIP/mirrors enabled=1 [updates-released] name=Fedora Core 4 - $basearch - Released Updates mirrorlist=http://$HOSTIP/mirrors enabled=1 Then make a file called mirrors and in it, something like http://$HOSTIP/RH7.3/ Then install like that doc describes.... yum -c http://$HOSTIP/yum-xen.conf --installroot=/mnt -y groupinstall Base A few questions What do you have in your /xen/test.img? Is something preloaded there? Why RH 7.3? Or should I not ask. If that doesn't work out for you. I am working on doing a normal install to a Qemu image and then converting the image to a xen bootable image. After I work that out, you might be able do the same with RH7.3 -Alex B Disclaimer: If anything I say is wrong, it is only my interpretation of the information I had at the time. From: Karl Stevens Subject: [Fedora-xen] FC6+xen guest boot issue To: fedora-xen at redhat.com Message-ID: < 454B9E04.9070705 at athabascau.ca> Content-Type: text/plain; charset=ISO-8859-1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I'm trying to set up Xen using FC6 as dom0, and am having zero success getting any guest OS to run. I've read the quickstart guide, but it's of little use because it makes two very large assumptions: 1. I want to install FC6 as a guest. 2. The hardware has internet access. I want to have RH7.3 running as a guest (but I'll settle for *anything* right now), and the machine I want to install on is behind a firewall, and has no internet access at all. I've tried the Documentation at xensource.com, and even tried downloading images from jailtime.org - no matter what I do, I encounter the following error: 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) (I've tried both hda1 and sda1 as root, neither one works.) The xen config I'm using is as follows: kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" memory = 256 name = "test" vif = [ '' ] disk = ['file:/xen/test.img,sda1,w','file:/xen/test.swap,sda2,w'] root = "/dev/sda1 ro" The file /xen/test.img exists, is not mounted by dom0, and contains a linux system (verified via mount -o loop, and umounted before I try to run xm create.) According to the Xen documentation, I believe this should work. Is there a fc6-specific initrd that I need? Is there any documentation that might provide some insight on installing non-FC6 guests onto a FC6 dom0? Thanks, Karl -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Sat Nov 4 23:27:41 2006 From: bench at silentmedia.com (Ben) Date: Sat, 4 Nov 2006 15:27:41 -0800 Subject: [Fedora-xen] AVC errors on xen domU Message-ID: <8C4E9045-4687-42E6-9ED2-6E3CE31F13DE@silentmedia.com> I recently upgraded some dom0 and domU machines to the 2.6.18-1.2200 kernel, now that the new xen packages are out which let it work. While it works well enough, on the domU machines I'm now seeing this: avc: denied { getattr } for pid=19349 comm="agetty" name="xvc0" dev=tmpfs ino=1614 scontext=system_u:system_r:getty_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file whenever init tries to spawn the console. I have these selinux versions installed: libselinux-1.30.3-4.fc5 selinux-policy-2.3.7-2.fc5 selinux-policy-targeted-2.3.7-2.fc5 From wsouto at gmail.com Sun Nov 5 15:42:33 2006 From: wsouto at gmail.com (Walter Souto) Date: Sun, 5 Nov 2006 13:42:33 -0200 Subject: [Fedora-xen] How to duplicate virtual machines installed on a entire partition? Message-ID: Hi, First, I'm sorry if that subject has been explored here before. I'd check the list on a few last months and found nothing, so... I'm currently using FC6 and did use virt-manager to install one vm on a partition /dev/sda5 (not a file) using the default layout inside this filesystem. So, there's a way to duplicate the entire /dev/sda5 to /dev/sda6 for example? I think I can copy the entire partition using gnu-parted or something, but I'm not sure if it's the best way. What I'm looking for is a way to create a image of the entire filesystem that I can simple restore to another partition and boot it up with xen. What you guys usually doing about that? I'm not sure if dump can do that, so I tried dump without sucess (I'm not know what I'm doing for sure). TIA, -- Walter. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hua.Zhang at Sun.COM Sun Nov 5 17:22:58 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Mon, 06 Nov 2006 01:22:58 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager Message-ID: <454E1DF2.90703@sun.com> Hi all, I am a little confused on the Pre-requisites for virt-manager, because I am finding two: 1. at http://virt-manager.et.redhat.com/faq.html, under "What other libraries are needed prior to installing "Virtual Machine Manager"?" 2. and find another one under "Pre-requisites" at http://virt-manager.et.redhat.com/download.html I am thinking 2 is a general one for all version of virt-manager, and 1 is exactly indicating the requirement before running latest virt-manger. is it correct? I am not in this alias, could you please reply me directly? thanks... Regards, Henry From robin-lists at robinbowes.com Sun Nov 5 19:06:07 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Sun, 05 Nov 2006 19:06:07 +0000 Subject: [Fedora-xen] Re: Console Hang On Boot Using 2.6.18-1.2200.fc5xenU In-Reply-To: <20061102235302.GT15618@skywalker.creative.net.au> References: <45350169.2030001@freedomics.com> <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> <20061102232505.GB30017@redhat.com> <20061102235302.GT15618@skywalker.creative.net.au> Message-ID: Adrian Chadd wrote: > On Thu, Nov 02, 2006, Daniel P. Berrange wrote: >> On Thu, Nov 02, 2006 at 05:15:56PM -0600, Mike Freemon wrote: >>> Was there any responses on this email from 10/17? I'm seeing the same >>> problem on my system: >> I posted a reply to the same problem reported in another thread - I mised >> this thread originally. The solution is to install new kudzu in the DomU >> from updates-testing. This new kudzu ensures that the agetty process gets >> spawned on the xvc0 console as well as the paravirt framebuffer. What version is this? I don't see any upgrades available for kudzu on updates-testing: # rpm -q kudzu kudzu-1.2.34.5-1 # yum --enablerepo=updates-testing upgrade kudzu ... Could not find update match for kudzu No Packages marked for Update/Obsoletion > If you're like me and run non-Redhat guests under FC5 + redhat xen kernels > you'll have to do it maunally: > > /etc/inittab: (assuming you're using getty and not already using 'co' > in your inittab) > > co:2345:respawn:/sbin/getty 38400 xvc0 > > and add xvc0 to /etc/securetty so you can login as root on the console. /etc/inittab contains: # Run gettys in standard runlevels co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav xvc0 is in /etc/securetty I see this in the console: Starting HAL daemon: [ OK ] INIT: Id "co" respawning too fast: disabled for 5 minutes INIT: no more processes left in this runlevel INIT: Id "co" respawning too fast: disabled for 5 minutes INIT: Id "co" respawning too fast: disabled for 5 minutes Ah, this looks like an SELinux issue: # audit2allow -i /var/log/audit/audit.log -l allow getty_t device_t:chr_file getattr; This fixes it: chcon --reference=/dev/tty0 /dev/xvc0 or chcon -t tty_device_t /dev/xvc0 R. From berrange at redhat.com Sun Nov 5 20:44:52 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 5 Nov 2006 20:44:52 +0000 Subject: [Fedora-xen] Re: Console Hang On Boot Using 2.6.18-1.2200.fc5xenU In-Reply-To: References: <45350169.2030001@freedomics.com> <6.0.0.22.2.20061102171304.040b7780@pop.ncsa.uiuc.edu> <20061102232505.GB30017@redhat.com> <20061102235302.GT15618@skywalker.creative.net.au> Message-ID: <20061105204452.GA27599@redhat.com> On Sun, Nov 05, 2006 at 07:06:07PM +0000, Robin Bowes wrote: > Adrian Chadd wrote: > > On Thu, Nov 02, 2006, Daniel P. Berrange wrote: > >> On Thu, Nov 02, 2006 at 05:15:56PM -0600, Mike Freemon wrote: > >>> Was there any responses on this email from 10/17? I'm seeing the same > >>> problem on my system: > >> I posted a reply to the same problem reported in another thread - I mised > >> this thread originally. The solution is to install new kudzu in the DomU > >> from updates-testing. This new kudzu ensures that the agetty process gets > >> spawned on the xvc0 console as well as the paravirt framebuffer. [snip] > # Run gettys in standard runlevels > co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav > > xvc0 is in /etc/securetty > > I see this in the console: > Starting HAL daemon: [ OK ] > INIT: Id "co" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > INIT: Id "co" respawning too fast: disabled for 5 minutes > INIT: Id "co" respawning too fast: disabled for 5 minutes > > Ah, this looks like an SELinux issue: > > # audit2allow -i /var/log/audit/audit.log -l > allow getty_t device_t:chr_file getattr; > > This fixes it: > chcon --reference=/dev/tty0 /dev/xvc0 > > or > > chcon -t tty_device_t /dev/xvc0 If you want it to reliably persist across reboots then the semanage tool is very handy: # ls -lZ /dev/xvc0 crw--w---- root tty root:object_r:device_t /dev/xvc0 # semanage fcontext -a -t tty_device_t -f -c /dev/xvc0 # restorecon /dev/xvc0 # ls -lZ /dev/xvc0 crw--w---- root tty system_u:object_r:tty_device_t /dev/xvc0 I opened a bug about the SELinux policy problem - bz 213277 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Sun Nov 5 20:48:21 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 5 Nov 2006 20:48:21 +0000 Subject: [Fedora-xen] How to duplicate virtual machines installed on a entire partition? In-Reply-To: References: Message-ID: <20061105204821.GB27599@redhat.com> On Sun, Nov 05, 2006 at 01:42:33PM -0200, Walter Souto wrote: > Hi, > > First, I'm sorry if that subject has been explored here before. I'd check > the list on a few last months and found nothing, so... > > I'm currently using FC6 and did use virt-manager to install one vm on a > partition /dev/sda5 (not a file) using the default layout inside this > filesystem. So, there's a way to duplicate the entire /dev/sda5 to /dev/sda6 > for example? I think I can copy the entire partition using gnu-parted or > something, but I'm not sure if it's the best way. If you ensure that sda5 & sda6 are *absolutely* identical in their size (check number of blocks allocated to each in fdisk), then you ought to simple be able to copy one to the other using dd. eg dd if=/dev/sda5 of=/dev/sda6 Be very careful not to typo there though :-) > What I'm looking for is a way to create a image of the entire filesystem > that I can simple restore to another partition and boot it up with xen. What > you guys usually doing about that? I'm not sure if dump can do that, so I > tried dump without sucess (I'm not know what I'm doing for sure). You can also just copy the partition to a file, which you can then move around at will, eg dd if=/dev/sda5 of=/path/to/some/file.img You could even then just run a VM off 'file.img' using the regular Xen file image driver (file: or tap:aio: in xen config file for disks). Regards Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Sun Nov 5 20:52:01 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 5 Nov 2006 20:52:01 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <454E1DF2.90703@sun.com> References: <454E1DF2.90703@sun.com> Message-ID: <20061105205201.GC27599@redhat.com> On Mon, Nov 06, 2006 at 01:22:58AM +0800, Henry Zhang wrote: > Hi all, > > I am a little confused on the Pre-requisites for virt-manager, because I > am finding two: > > 1. at http://virt-manager.et.redhat.com/faq.html, under "What other > libraries are needed prior to installing "Virtual Machine Manager"?" > > 2. and find another one under "Pre-requisites" at > http://virt-manager.et.redhat.com/download.html > > I am thinking 2 is a general one for all version of virt-manager, and 1 > is exactly indicating the requirement before running latest virt-manger. > is it correct? The list on the download.html page is more up2date / accurate - I'll fix the list under the faq.html to match this. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From ccrayne at crayne.org Mon Nov 6 02:47:26 2006 From: ccrayne at crayne.org (Charles A. Crayne) Date: Sun, 5 Nov 2006 18:47:26 -0800 Subject: [Fedora-xen] FC6 Xen kernel will not boot Message-ID: <20061105184726.4b969f1d@heimdall.crayne.org> Attempting to boot 2.6.18-1.2798.fc6xen appears to be OK up to the point where it issues 'scrubbing free ram' and 'xen trace buffer disabled' and then hangs. What have I probably done wrong? -- Chuck From bendube1999 at hotmail.com Mon Nov 6 03:22:14 2006 From: bendube1999 at hotmail.com (=?iso-8859-1?B?QmVub+50IER1Yuk=?=) Date: Sun, 05 Nov 2006 22:22:14 -0500 Subject: [Fedora-xen] DomU always failed: sda1 frontend doesn't find backend Message-ID: Hi, I've try many guest image to run side by side with Dom0 (FC6), even the last FC6-xen image from jailtime.org but no one succeed. Note: I manage the xen's cfg file to point to this kernel: /boot/vmlinuz-2.6.18-1.2798.fc6xen Here is a part of what I have in /var/log/xen/xend..log: [2006-11-05 15:15:36 xend.XendDomainInfo 2531] DEBUG (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None , 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.18-1.2798.fc6xen'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1 ro'], ['vncunused', 1], ['display', ':0.0'], ['xauthority', '/tmp /.gdmDUT4HT']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'fedora.fc6', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memor y': 128, 'device': [('vbd', ['vbd', ['uname', 'file:/xen/fedora/fedora.fc6.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-11-05 15:15:36 xend.XendDomainInfo 2531] DEBUG (XendDomainInfo:1253) XendDomainInfo.construct: None [2006-11-05 15:15:36 xend.XendDomainInfo 2531] DEBUG (XendDomainInfo:1285) XendDomainInfo.initDomain: 5 1.0 [2006-11-05 15:15:36 xend 2531] INFO (image:214) configuring linux guest [2006-11-05 15:15:36 xend 2531] DEBUG (balloon:127) Balloon: 1288252 KiB free; need 131072; done. [2006-11-05 15:15:36 xend 2531] INFO (image:138) buildDomain os=linux dom=5 vcpus=1 [2006-11-05 15:15:36 xend 2531] DEBUG (image:193) dom = 5 [2006-11-05 15:15:36 xend 2531] DEBUG (image:194) image = /boot/vmlinuz-2.6.18-1.2798.fc6xen [2006-11-05 15:15:36 xend 2531] DEBUG (image:195) store_evtchn = 1 [2006-11-05 15:15:36 xend 2531] DEBUG (image:196) console_evtchn = 2 [2006-11-05 15:15:36 xend 2531] DEBUG (image:197) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro [2006-11-05 15:15:36 xend 2531] DEBUG (image:198) ramdisk = [2006-11-05 15:15:36 xend 2531] DEBUG (image:199) vcpus = 1 [2006-11-05 15:15:36 xend 2531] DEBUG (image:200) features = [2006-11-05 15:15:37 xend 2531] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' [2006-11-05 15:15:37 xend 2531] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '2049', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain /0/backend/vbd/5/2049'} to /local/domain/5/device/vbd/2049. [2006-11-05 15:15:37 xend 2531] DEBUG (DevController:112) DevController: writing {'domain': 'fedora.fc6', 'frontend': '/local/domain/5/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params ': '/xen/fedora/fedora.fc6.img', 'mode': 'w', 'online': '1', 'frontend-id': '5', 'type': 'file'} to /local/domain/0/backend/vbd/5/2049. A part of xen-hotplug.log xenstore-read: couldn't read path backend/vbd/5/2050/node xenstore-read: couldn't read path backend/vbd/5/2049/node What can I do or try? Ben _________________________________________________________________ Achetez ce que vous voulez, quand vous voulez sur Sympatico / MSN Magasiner http://magasiner.sympatico.msn.ca/content/shp/?ctId=101,ptnrid=176,ptnrdata=081805 From berrange at redhat.com Mon Nov 6 04:45:43 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 6 Nov 2006 04:45:43 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <454EA329.9020705@sun.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> Message-ID: <20061106044542.GA28547@redhat.com> On Mon, Nov 06, 2006 at 10:51:21AM +0800, Henry Zhang wrote: > Thanks, Dan. > > so for "pygtk2 >= 1.99.12-6", it means 1.99.12 - 1.6? > And I can say if we want virt-manager to run, pygtk2 1.99.12 can be OK, > right? These version numbers refer to the RPM versions - so 1.99.12-6 refers to pygtk2 1.99.12, with RPM release number 6. So for non-RPM builds just look at the first component - 1.99.12 > BTW, I found these 2 requirements are different, for example, I can't > find Matplotlib in download.html. So could you mind giving me a total > list, including Pre-requisites and its earlist version, on what we need > to build and run virt-manager? Again, the 'download.html' page is the most accurate - it does not list matplotlib since we no longer have that as a requirement, the faq.html page is outdated in this respect. The version numbers documented are the earliest that I have personally tested & verified against. It may well run fine against even earlier versions - I just haven't had opportunity to verify - if you find it does work against earlier versions of particular software let me know & i'll update the docs. > Daniel P. Berrange ??????: > >On Mon, Nov 06, 2006 at 01:22:58AM +0800, Henry Zhang wrote: > >> > >>I am a little confused on the Pre-requisites for virt-manager, because I > >>am finding two: > >> > >>1. at http://virt-manager.et.redhat.com/faq.html, under "What other > >>libraries are needed prior to installing "Virtual Machine Manager"?" > >> > >>2. and find another one under "Pre-requisites" at > >>http://virt-manager.et.redhat.com/download.html > >> > >>I am thinking 2 is a general one for all version of virt-manager, and 1 > >>is exactly indicating the requirement before running latest virt-manger. > >>is it correct? > >> > > > >The list on the download.html page is more up2date / accurate - I'll fix > >the list under the faq.html to match this. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Hua.Zhang at Sun.COM Mon Nov 6 02:51:21 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Mon, 06 Nov 2006 10:51:21 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061105205201.GC27599@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> Message-ID: <454EA329.9020705@sun.com> Thanks, Dan. so for "pygtk2 >= 1.99.12-6", it means 1.99.12 - 1.6? And I can say if we want virt-manager to run, pygtk2 1.99.12 can be OK, right? BTW, I found these 2 requirements are different, for example, I can't find Matplotlib in download.html. So could you mind giving me a total list, including Pre-requisites and its earlist version, on what we need to build and run virt-manager? Thanks again.... Regards, Henry Daniel P. Berrange ??: > On Mon, Nov 06, 2006 at 01:22:58AM +0800, Henry Zhang wrote: > >> Hi all, >> >> I am a little confused on the Pre-requisites for virt-manager, because I >> am finding two: >> >> 1. at http://virt-manager.et.redhat.com/faq.html, under "What other >> libraries are needed prior to installing "Virtual Machine Manager"?" >> >> 2. and find another one under "Pre-requisites" at >> http://virt-manager.et.redhat.com/download.html >> >> I am thinking 2 is a general one for all version of virt-manager, and 1 >> is exactly indicating the requirement before running latest virt-manger. >> is it correct? >> > > The list on the download.html page is more up2date / accurate - I'll fix > the list under the faq.html to match this. > > Regards, > Dan. > From laurent at unipress.be Mon Nov 6 10:30:50 2006 From: laurent at unipress.be (Laurent van der Straten) Date: Mon, 06 Nov 2006 11:30:50 +0100 Subject: [Fedora-xen] FC6 + Xen Lost Network when Virtual manager Start In-Reply-To: <20061106073743.1A0B873354@hormel.redhat.com> References: <20061106073743.1A0B873354@hormel.redhat.com> Message-ID: <1162809050.3664.6.camel@itweb.unipress.be> Hi I've problem with FC6 and Xen when I start a vm , i lost the net connection. configuration : Quadri Dual Core pacifica with 32 GB RAM and 2x Broadcom GbE. when I start the machine a make a ping , all work perfectly but when i open the virt manager ( so connection on xen daemon ) no ping can go out. any idea ? -- ********************************************************************** Laurent van der Straten Network/Operation Systems/Support Rue Th?odore Verhaegen, 196 202 1060 Bruxelles Belgium Tel: +32 2 533 99 84 Fax: +32 2 523 24 96 Skype ID: Sephirod URL: www.up-servers.com ********************************************************************** From robin-lists at robinbowes.com Mon Nov 6 12:19:40 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Mon, 06 Nov 2006 12:19:40 +0000 Subject: [Fedora-xen] DomU network doesn't start automatically Message-ID: Hi, I'm running 2.6.17-1.2187_FC5xen0 as my host and 2.6.18-1.2200.fc5xenU in the guest. I'm finding that the network doesn't start when I start the guest. If I login (through the console) and manually start it, it works fine. e.g.: service network start Any idea what might cause this and how to fix it? R. From laurent.mylists at gmail.com Mon Nov 6 14:11:51 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Mon, 6 Nov 2006 15:11:51 +0100 Subject: [Fedora-xen] FC6 and Xen for full virtualization Message-ID: Hi, I'm a new FC user. I'm trying to install FC6 with Xen for full Virtualization (on an AMD 3800+ X2). When I try to create a new VM with virt-manager using an image file, the creation interrupts with a Domain creating error. Xen log gives an error like "fime image does not exist". Even if I create this file before with dd, I obtain the same error. Please do I have an idea about what happens ? Any idea would be very very appreciated, thanks laurent -------------- next part -------------- An HTML attachment was scrubbed... URL: From m3freak at rogers.com Mon Nov 6 14:54:02 2006 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Mon, 06 Nov 2006 09:54:02 -0500 Subject: [Fedora-xen] FC6+xen guest boot issue In-Reply-To: <454B9E04.9070705@athabascau.ca> References: <454B9E04.9070705@athabascau.ca> Message-ID: <1162824842.19199.1.camel@krs> On Fri, 2006-11-03 at 12:52 -0700, Karl Stevens wrote: > kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" > memory = 256 > name = "test" > vif = [ '' ] > disk = ['file:/xen/test.img,sda1,w','file:/xen/test.swap,sda2,w'] > root = "/dev/sda1 ro" You're missing the ramdisk parameter. Here's what one of my domUs looks like: kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" ramdisk = "/boot/initrd-2.6.17-1.2174_FC5xenU.img" memory = 96 name = "posty" root = "/dev/sda1 ro" disk = [ "phy:vg00/posty,sda1,w","phy:vg00/swap2,sda2,w" ] vif = [ "mac=00:16:3E:66:94:9C,bridge=xenbr0" ] cpus = "0-1" vcpus = 1 extra = "enforcing=0" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" HTH, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 09:52:19 up 8 days, 4:21, 3 users, load average: 0.39, 0.47, 0.48 From m3freak at rogers.com Mon Nov 6 14:58:09 2006 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Mon, 06 Nov 2006 09:58:09 -0500 Subject: [Fedora-xen] FC6+xen guest boot issue In-Reply-To: <454B9E04.9070705@athabascau.ca> References: <454B9E04.9070705@athabascau.ca> Message-ID: <1162825089.19199.6.camel@krs> On Fri, 2006-11-03 at 12:52 -0700, Karl Stevens wrote: > I want to have RH7.3 running as a guest (but I'll settle for *anything* > right now), and the machine I want to install on is behind a firewall, > and has no internet access at all. I forgot to mention that running RH7.3 as a paravirtualized domU won't work since the Xen 3.0 series doesn't have support for the 2.4 kernels (which is what RH7.3 uses, IIRC). You'll need to run RH7.3 as a hvm domain (fully virtualized), and you'll need those fancy new CPUs with virtualization support (don't know anything about those...). Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 09:54:52 up 8 days, 4:23, 3 users, load average: 0.45, 0.44, 0.46 From karl at athabascau.ca Mon Nov 6 16:19:16 2006 From: karl at athabascau.ca (Karl Stevens) Date: Mon, 06 Nov 2006 09:19:16 -0700 Subject: [Fedora-xen] FC6+xen guest boot issue In-Reply-To: <1162824842.19199.1.camel@krs> References: <454B9E04.9070705@athabascau.ca> <1162824842.19199.1.camel@krs> Message-ID: <454F6084.6040702@athabascau.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kanwar Ranbir Sandhu wrote: > You're missing the ramdisk parameter. Thanks - I tried it with the ramdisk, didn't help. Ramdisk loads, then the vm hangs when it goes to switch to the "real" filesystem (because it doesn't recognize it.) > Here's what one of my domUs looks like: > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" This is probably why: you're using FC5, not FC6. FC6 does away with separate dom0 and domU kernels. > I forgot to mention that running RH7.3 as a paravirtualized domU won't > work since the Xen 3.0 series doesn't have support for the 2.4 kernels Sorry to correct you, but xensource.com has a domU kernel for RHEL 3 (which runs 2.4) I downloaded and used this kernel, and it works (solved my problem.) I would have rather done things the "Red Hat endorsed" way, but I'm just happy I've got it running. Thanks for your replies - -Karl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFT2CEr6qWhNgoahURAuEoAKCERzsxZzrnWrGlJkAPJnCnA3GioQCgipLl rhmyTi4A4X23nTk8f2l1e80= =ZJTb -----END PGP SIGNATURE----- __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- From m3freak at rogers.com Mon Nov 6 20:13:28 2006 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Mon, 06 Nov 2006 15:13:28 -0500 Subject: [Fedora-xen] FC6+xen guest boot issue In-Reply-To: <454F6084.6040702@athabascau.ca> References: <454B9E04.9070705@athabascau.ca> <1162824842.19199.1.camel@krs> <454F6084.6040702@athabascau.ca> Message-ID: <1162844008.19199.11.camel@krs> On Mon, 2006-11-06 at 09:19 -0700, Karl Stevens wrote: > > Here's what one of my domUs looks like: > > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" > > This is probably why: you're using FC5, not FC6. FC6 does away with > separate dom0 and domU kernels. I should have mentioned that my dom0 is a FC5 box. I haven't moved it over to FC6 for fear of not having any bootable domUs. Though, it would be just as easy to go back to FC5 if that happened. > > I forgot to mention that running RH7.3 as a paravirtualized domU won't > > work since the Xen 3.0 series doesn't have support for the 2.4 kernels > > Sorry to correct you, but xensource.com has a domU kernel for RHEL 3 > (which runs 2.4) I didn't know that! Well, that's certainly helpful. But, what if one is running a RHEL 4? Or some other distro that has a 2.6 kernel? > I downloaded and used this kernel, and it works (solved my problem.) I > would have rather done things the "Red Hat endorsed" way, but I'm just > happy I've got it running. Glad to hear it. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 15:09:35 up 8 days, 9:38, 3 users, load average: 0.22, 0.34, 0.34 From berrange at redhat.com Mon Nov 6 20:25:58 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 6 Nov 2006 20:25:58 +0000 Subject: [Fedora-xen] FC6+xen guest boot issue In-Reply-To: <1162844008.19199.11.camel@krs> References: <454B9E04.9070705@athabascau.ca> <1162824842.19199.1.camel@krs> <454F6084.6040702@athabascau.ca> <1162844008.19199.11.camel@krs> Message-ID: <20061106202557.GA30710@redhat.com> On Mon, Nov 06, 2006 at 03:13:28PM -0500, Kanwar Ranbir Sandhu wrote: > On Mon, 2006-11-06 at 09:19 -0700, Karl Stevens wrote: > > > Here's what one of my domUs looks like: > > > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" > > > > This is probably why: you're using FC5, not FC6. FC6 does away with > > separate dom0 and domU kernels. > > I should have mentioned that my dom0 is a FC5 box. I haven't moved it > over to FC6 for fear of not having any bootable domUs. Though, it would > be just as easy to go back to FC5 if that happened. For x86_64 life is easy - FC5 & FC6 are compatible with each others Xen guests. For i686 though things are troublesome. The original xen0 & xenU kernels from FC5 are non-PAE. The xen kernel in FC6 meanwhile is PAE only. You can't mix & match PAE with non-PAE between host & guest. Thus to allow people to mix FC5 & FC6 the more recent kernel errata for FC5 also contain a PAE enabled kernel -xen which can be used instead of the old -xen0 & -xenU > > > I forgot to mention that running RH7.3 as a paravirtualized domU won't > > > work since the Xen 3.0 series doesn't have support for the 2.4 kernels > > > > Sorry to correct you, but xensource.com has a domU kernel for RHEL 3 > > (which runs 2.4) > > I didn't know that! Well, that's certainly helpful. But, what if one > is running a RHEL 4? Or some other distro that has a 2.6 kernel? If you're using x86_64 then you shouldn't have any trouble using DomU kernels from any other xen-ified distro. For i686 just make sure you get the PAE stuff matched up correctly. WRT to RHEL-4, a future errata will provide an officially supported Xen guest kernel for the 2.6.9 tree that is in RHEL-4. > > I downloaded and used this kernel, and it works (solved my problem.) I > > would have rather done things the "Red Hat endorsed" way, but I'm just > > happy I've got it running. Given the age of the RHEL-3 kernel & the stage RHEL-3 is at in its product support lifecycle, it is not practical to provide an officially supported paravirt guest kernel. So either using xensource's unofficial 2.4 backport is one option, or using fully-virt HVM for the regular RHEL-3 kernel is another more supportable option. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jeff_301 at msn.com Mon Nov 6 21:55:14 2006 From: jeff_301 at msn.com (Jeff Stockett) Date: Mon, 6 Nov 2006 15:55:14 -0600 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 In-Reply-To: <6b4bb8650611061337m3d840e85v76df61fd9bc90003@mail.gmail.com> References: <6b4bb8650611061337m3d840e85v76df61fd9bc90003@mail.gmail.com> Message-ID: Yes, but for some reason on my system, the function keys don't work during install. I don't know if it is because it is a laptop or what - but pressing F2, F5, F6, etc. at the appropriate times does nothing during during setup. I'll bet it does have something to do with it being a laptop and the key mappings for the function keys perhaps. Were you on a laptop or normal keyboard??? -----Original Message----- From: david.parsley at gmail.com [mailto:david.parsley at gmail.com] On Behalf Of David Parsley Sent: Monday, November 06, 2006 3:38 PM To: Jeff Stockett Subject: Re: [Fedora-xen] problems installing winxp with full virtualization on FC6 Hi Jeff, Dunno if this will work as well for you as it did for me, but here's what I did: When the XP installer asks you to press F6 to load drivers, instead press F5, and select 'Standard PC ...'. Apparently this instructs the XP installer to use drivers for a simpler machine architecture. Regards, David On 11/2/06, Jeff Stockett wrote: > > Yep - I already tried that with the following results: > > apic acpi > 1 1 VM hangs with aforementioned apic error > 0 1 VM crashes > 1 0 VM crashes > 0 0 VM hangs with aforementioned apic error > > I can post the dmesg info for the crash cases if you think that would be helpful. I may try grabbing vncclient from somewhere and seeing if I can get the F5 hack to work on a fresh reinstall. I think Xen will be quite handy once the kinks are worked out and applaud the Fedora team for attempting to make it easy and including it in FC6. Thanks for your help. --J > > ---------------------------------------- > > Date: Thu, 2 Nov 2006 23:31:56 +0000 > > From: berrange at redhat.com > > To: jeff_301 at msn.com > > CC: fedora-xen at redhat.com > > Subject: Re: [Fedora-xen] problems installing winxp with full virtualization on FC6 > > > > On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett wrote: > > > > > > I see from googling, that this bug has been reported once before > > > (last month with a rawhide build) - but no answers. A little further > > > googling indicates that one possible workaround might be to hit F5 > > > (when it is asking for F6 to load drivers) during the setup process > > > and specify the computer as not having APIC but the version of VNC > > > or whatever console emulator that comes with Virtual Machine Manager > > > doesn't seem to pass function keys thru (F2, F5, or F6 don't appear > > > to work). I'm at a loss on where to go from here, except to perhaps > > > start compiling everything from latest sources (which would be alot > > > of trouble). > > > > > > builder = "hvm" > > > memory = "256" > > > disk = [ 'phy:/dev/vg0/domuwinxp,hda,w', 'phy:/dev/hdb,hdc:cdrom,r' ] > > > boot = 'c' > > > vif = [ 'type=ioemu, mac=00:16:3e:45:71:31, bridge=xenbr0', ] > > > uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2" > > > device_model = "/usr/lib64/xen/bin/qemu-dm" > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > vnc=1 > > > vncunused=1 > > > apic=1 > > > acpi=1 > > > > Try toggling these last two settings here - one of the 4 different combos > > of acpi & apic may well help. > > > > Regards, > > Dan. > > -- > > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| > > |=- Perl modules: http://search.cpan.org/~danberr/ -=| > > |=- Projects: http://freshmeat.net/~danielpb/ -=| > > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- David L. Parsley Linux Systems Engineer, James Madison University "If I have seen further, it is by standing on ye shoulders of giants" - Isaac Newton From florian.heigl at gmail.com Mon Nov 6 20:00:39 2006 From: florian.heigl at gmail.com (Florian Heigl) Date: Mon, 6 Nov 2006 21:00:39 +0100 Subject: [Fedora-xen] 32bit PAE capable kernel Message-ID: <77abe410611061200k1bb93faerdc3aaa78d31fa8a0@mail.gmail.com> Hello, I am testing cobbler (http://cobbler.et.redhat.com) for automated kickstarting of FC5/FC6 domUs on my current host with uses a dom0 build with XEN_TARGET_X86_PAE=y as it has >4GB memory. While I found 'various' Fedora - PAE kernels they all seem to be for 64bit/PAE systems, or maybe I missed one. I need something that can run on a 32bit/PAE host and boot via PXE; I could use a non-Fedora kernel, but I don't like the idea of messing in the OS's guts. - Is there an officially supported kernel? - Is there an not-supported but current and tested kernel? I don't know if it's possible, but using names like x86_32 and x86_32p might make things a bit easier. (I would have searched list archives, but there are none, so I only skimmed over the last few months emails and didn't see anything helpful) Regards, Florian -- 'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen' From berrange at redhat.com Mon Nov 6 22:29:19 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 6 Nov 2006 22:29:19 +0000 Subject: [Fedora-xen] 32bit PAE capable kernel In-Reply-To: <77abe410611061200k1bb93faerdc3aaa78d31fa8a0@mail.gmail.com> References: <77abe410611061200k1bb93faerdc3aaa78d31fa8a0@mail.gmail.com> Message-ID: <20061106222919.GB30710@redhat.com> On Mon, Nov 06, 2006 at 09:00:39PM +0100, Florian Heigl wrote: > Hello, > > I am testing cobbler (http://cobbler.et.redhat.com) for automated > kickstarting > of FC5/FC6 domUs on my current host with uses a dom0 build with > XEN_TARGET_X86_PAE=y as it has >4GB memory. > While I found 'various' Fedora - PAE kernels they all seem to be for > 64bit/PAE > systems, or maybe I missed one. Look under the i386 architecture on the Fedora download sites > > I need something that can run on a 32bit/PAE host and boot via PXE; > I could use a non-Fedora kernel, but I don't like the idea of messing in the > OS's guts. > > - Is there an officially supported kernel? In Fedora Core 5, the i686 kernels (kernel-xen0 kernel-xenU) were non-PAE. We later pushed an errata (kernel-xen) which *is* PAE. In Fedora Core 6, all kernels are PAE - we no longer support non-PAE > - Is there an not-supported but current and tested kernel? The FC6 kernel is in the 'kernel-xen' RPM here: http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/ The FC5 errata kernel is 'kernel-xen' RPM here: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/i386/ Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From parsley at linuxjedi.org Tue Nov 7 01:31:14 2006 From: parsley at linuxjedi.org (David Parsley) Date: Mon, 6 Nov 2006 20:31:14 -0500 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 In-Reply-To: References: <6b4bb8650611061337m3d840e85v76df61fd9bc90003@mail.gmail.com> Message-ID: <6b4bb8650611061731t1d1c6059g33b1a9143a4bd440@mail.gmail.com> On 11/6/06, Jeff Stockett wrote: > Yes, but for some reason on my system, the function keys don't work during > install. I don't know if it is because it is a laptop or what - but > pressing F2, F5, F6, etc. at the appropriate times does nothing during > during setup. I'll bet it does have something to do with it being a laptop > and the key mappings for the function keys perhaps. > > Were you on a laptop or normal keyboard??? Normal keyboard. If you're using sdl, try vnc, or vice-versa. Or try plugging in a USB keyboard. Good luck. David -- David L. Parsley Linux Systems Engineer, James Madison University "If I have seen further, it is by standing on ye shoulders of giants" - Isaac Newton From jeff at kreska.org Tue Nov 7 12:04:53 2006 From: jeff at kreska.org (Jeff) Date: Tue, 07 Nov 2006 06:04:53 -0600 Subject: [Fedora-xen] enlarge file backed filesystem Message-ID: <45507665.7080809@kreska.org> I have created an xp domain and fc6 domain but I picked too small of size for the image. My xp domain is using a physical device (logical volume) and my fc6 domain is using a file for the mapped disk. Isn't there a way to enlarge the filesystem of the guest by enlarging the backing file/device? If so, what exactly do you do to enlarge the backing file/dev? --- Thanks, Jeff From adrian at creative.net.au Tue Nov 7 13:37:03 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Tue, 7 Nov 2006 21:37:03 +0800 Subject: [Fedora-xen] memory issues with FC5.2200 kernels Message-ID: <20061107133703.GA1133@skywalker.creative.net.au> hiya, I've just upgraded a production Xen to FC5.2200 + the Xen userspace stuff and its exhibiting some nasty problems. A couple of hours uptime is followed by all domU networking stopping. Here's dmesg in dom0: xen_net: Memory squeeze in netback driver. printk: 4 messages suppressed. xen_net: Memory squeeze in netback driver. printk: 4 messages suppressed. And xm dmesg: (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) Googling has shown inconclusive results - a couple of possible fixes but no explanation why (and no consistent fix.) Any ideas? Thanks, Adrian From adrian at creative.net.au Tue Nov 7 13:38:50 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Tue, 7 Nov 2006 21:38:50 +0800 Subject: [Fedora-xen] Re: [Xen-users] memory issues with FC5.2200 kernels In-Reply-To: <20061107133703.GA1133@skywalker.creative.net.au> References: <20061107133703.GA1133@skywalker.creative.net.au> Message-ID: <20061107133850.GB1133@skywalker.creative.net.au> I should add this from xm dmesg: Xen version 3.0-unstable (brewbuilder at build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) Sat Oct 14 16:56:23 EDT 2006 Latest ChangeSet: unavailable (XEN) Command line: /xen.gz-2.6.18-1.2200.fc5 (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009fc00 (usable) (XEN) 000000000009fc00 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007eff0000 (usable) (XEN) 000000007eff0000 - 000000007eff3000 (ACPI NVS) (XEN) 000000007eff3000 - 000000007f000000 (ACPI data) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffff0000 - 0000000100000000 (reserved) (XEN) System RAM: 2031MB (2080316kB) (XEN) Xen heap: 9MB (10108kB) (XEN) PAE disabled. Thanks, adrian On Tue, Nov 07, 2006, Adrian Chadd wrote: > hiya, > > I've just upgraded a production Xen to FC5.2200 + the Xen userspace > stuff and its exhibiting some nasty problems. A couple of hours uptime > is followed by all domU networking stopping. > > Here's dmesg in dom0: > > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > > And xm dmesg: > > (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (0 of 63) > > Googling has shown inconclusive results - a couple of possible fixes but no explanation > why (and no consistent fix.) > > Any ideas? > > Thanks, > > > Adrian > > > _______________________________________________ > Xen-users mailing list > Xen-users at lists.xensource.com > http://lists.xensource.com/xen-users From Mats.Petersson at amd.com Tue Nov 7 13:42:31 2006 From: Mats.Petersson at amd.com (Petersson, Mats) Date: Tue, 7 Nov 2006 14:42:31 +0100 Subject: [Fedora-xen] RE: [Xen-users] memory issues with FC5.2200 kernels In-Reply-To: <20061107133703.GA1133@skywalker.creative.net.au> Message-ID: <907625E08839C4409CE5768403633E0B018E16CC@sefsexmb1.amd.com> > -----Original Message----- > From: xen-users-bounces at lists.xensource.com > [mailto:xen-users-bounces at lists.xensource.com] On Behalf Of > Adrian Chadd > Sent: 07 November 2006 13:37 > To: fedora-xen at redhat.com > Cc: xen-users at lists.xensource.com > Subject: [Xen-users] memory issues with FC5.2200 kernels > > hiya, > > I've just upgraded a production Xen to FC5.2200 + the Xen userspace > stuff and its exhibiting some nasty problems. A couple of hours uptime > is followed by all domU networking stopping. > > Here's dmesg in dom0: > > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > > And xm dmesg: > > (XEN) (file=memory.c, line=66) Could not allocate order=0 > extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 > extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 > extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 > extent: id=0 memflags=0 (0 of 63) > (XEN) (file=memory.c, line=66) Could not allocate order=0 > extent: id=0 memflags=0 (0 of 63) It is trying to allocate one page in "increase_reservation", and failing... I don't know WHY this is failing (I suspect the heap may have a memory leak, perhaps)? What is your DomU doing when you see this problem? -- Mats > > Googling has shown inconclusive results - a couple of > possible fixes but no explanation > why (and no consistent fix.) > > Any ideas? > > Thanks, > > > Adrian > > > _______________________________________________ > Xen-users mailing list > Xen-users at lists.xensource.com > http://lists.xensource.com/xen-users > > > From acathrow at redhat.com Tue Nov 7 14:16:56 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Tue, 07 Nov 2006 09:16:56 -0500 Subject: [Fedora-xen] enlarge file backed filesystem In-Reply-To: <45507665.7080809@kreska.org> References: <45507665.7080809@kreska.org> Message-ID: <1162909016.7552.19.camel@amd.cathrow.org> Ouch, It's possible but not nice. Obviously the first step is to back up your existing file before you try any of this .... First step is you need to enlarge the file itself. Use dd to to this for example dd if=/dev/zero of=myImage.img seek=***** bs=1M count=1 The seek value should be big enough to seek past the current data so we don't overwrite anything - so for example make it a 2gb past the end of the file. You now have a larger sparse file. At this point you have a larger disk but your partition table is out of whack. So you need to use a tool like parted/gparted to change the partition table. You can also use fdisk if you're feeling brave. These tools won't work directly on a file, so you'll need to create a block device for that image, you can use kpartx for this, see the link below http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184aece3efe822be0ef6dd1871cd When you've enlarged the partition to the correct size then you'll need to resize the ntfs file system - for this you'll need ntfsresize. http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html Good luck, don't forget the backup ! Aic On Tue, 2006-11-07 at 06:04 -0600, Jeff wrote: > I have created an xp domain and fc6 domain but I picked too small of > size for the image. > > My xp domain is using a physical device (logical volume) and my fc6 > domain is using a file for the mapped disk. > > Isn't there a way to enlarge the filesystem of the guest by enlarging > the backing file/device? If so, what exactly do you do to enlarge the > backing file/dev? > > --- > Thanks, > Jeff > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From aatrof at gmail.com Tue Nov 7 15:19:58 2006 From: aatrof at gmail.com (Aleksander Trofimowicz) Date: Tue, 7 Nov 2006 16:19:58 +0100 Subject: [Fedora-xen] hvm mode and windows xp (xen 3.0.3-rc3) In-Reply-To: <6b4bb8650611031439j24e11fderf42a734dee116323@mail.gmail.com> References: <759d30a60611031414o593050e5iefbac2c40bf0748b@mail.gmail.com> <6b4bb8650611031439j24e11fderf42a734dee116323@mail.gmail.com> Message-ID: <759d30a60611070719h100ae19cie9738c513e6559a5@mail.gmail.com> On 03/11/06, David Parsley wrote: > > > I'm a bit of a failure at running windows xp in the hvm mode. to be > > honest nothing went the way it should have on my notebook with turion > > 64 x2 processor inside. > > Just a quick note: I had good luck installing WinXP on FC6 today. > Dunno if it'll help you, but I've attached my config file. The big > thing that made it work for me: when the Windows installer asks you > to press F6 to load drivers, press F5, and select 'Standard PC > ...(something)'. > thanks for the hint. i guess all the problems i faced with during win 2k/xp setup have their origins in static hal that is chosen at the very beginning and probably because of the way xen handles presence of acpi in a hvm domain. nevertheless a general rule for those who just want that os running without bells and whistles is to install windows without acpi support (to do so 'standard pc' or 'standard pc with c-step i486' should be selected). btw i still have to use qemu to install windows xp properly. otherwise i'm unable to select an appropriate hal after pressing f5 key, as 'up' and 'down' keys don't respond regardless of graphical interface (sdl or vnc) i use. strange, isn't it? -- aleksander From adrian at creative.net.au Tue Nov 7 15:26:21 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Tue, 7 Nov 2006 23:26:21 +0800 Subject: [Fedora-xen] Re: [Xen-users] memory issues with FC5.2200 kernels In-Reply-To: <907625E08839C4409CE5768403633E0B018E16CC@sefsexmb1.amd.com> References: <20061107133703.GA1133@skywalker.creative.net.au> <907625E08839C4409CE5768403633E0B018E16CC@sefsexmb1.amd.com> Message-ID: <20061107152621.GC1133@skywalker.creative.net.au> On Tue, Nov 07, 2006, Petersson, Mats wrote: > It is trying to allocate one page in "increase_reservation", and > failing... the domU or dom0? > I don't know WHY this is failing (I suspect the heap may have a memory > leak, perhaps)? > > What is your DomU doing when you see this problem? No idea. I've got half a dozen domU's here all running various tasks each (smtp, dns, www, etc.) so its difficult to pin down what each is doing. Adrian From Mats.Petersson at amd.com Tue Nov 7 15:26:24 2006 From: Mats.Petersson at amd.com (Petersson, Mats) Date: Tue, 7 Nov 2006 16:26:24 +0100 Subject: [Fedora-xen] RE: [Xen-users] memory issues with FC5.2200 kernels In-Reply-To: <20061107152621.GC1133@skywalker.creative.net.au> Message-ID: <907625E08839C4409CE5768403633E0B018E16D1@sefsexmb1.amd.com> > -----Original Message----- > From: Adrian Chadd [mailto:adrian at creative.net.au] > Sent: 07 November 2006 15:26 > To: Petersson, Mats > Cc: fedora-xen at redhat.com; xen-users at lists.xensource.com > Subject: Re: [Xen-users] memory issues with FC5.2200 kernels > > On Tue, Nov 07, 2006, Petersson, Mats wrote: > > > It is trying to allocate one page in "increase_reservation", and > > failing... > > the domU or dom0? The one with "id=0", so Dom0. > > > I don't know WHY this is failing (I suspect the heap may > have a memory > > leak, perhaps)? > > > > What is your DomU doing when you see this problem? > > No idea. I've got half a dozen domU's here all running > various tasks each > (smtp, dns, www, etc.) so its difficult to pin down what each > is doing. That makes debugging it quite difficult... Perhaps you can set up a machine for testing to find out what's causing it, if there's some pattern to it, etc, etc. -- Mats > > > > Adrian > > > > From bench at silentmedia.com Tue Nov 7 16:58:26 2006 From: bench at silentmedia.com (Ben) Date: Tue, 7 Nov 2006 08:58:26 -0800 (PST) Subject: [Fedora-xen] enlarge file backed filesystem In-Reply-To: <45507665.7080809@kreska.org> References: <45507665.7080809@kreska.org> Message-ID: If you're using LVM on your domU than it should be pretty easy to just add another file-backed disk to your domU and expand its size that way.... On Tue, 7 Nov 2006, Jeff wrote: > I have created an xp domain and fc6 domain but I picked too small of size for > the image. > > My xp domain is using a physical device (logical volume) and my fc6 domain is > using a file for the mapped disk. > > Isn't there a way to enlarge the filesystem of the guest by enlarging the > backing file/device? If so, what exactly do you do to enlarge the backing > file/dev? > > --- > Thanks, > Jeff > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From bench at silentmedia.com Tue Nov 7 17:04:32 2006 From: bench at silentmedia.com (Ben) Date: Tue, 7 Nov 2006 09:04:32 -0800 (PST) Subject: [Fedora-xen] enlarge file backed filesystem In-Reply-To: References: <45507665.7080809@kreska.org> Message-ID: Woops, I guess I should work on my reading comprehension.... of course you're not using LVM if you've got an XP domU. On Tue, 7 Nov 2006, Ben wrote: > If you're using LVM on your domU than it should be pretty easy to just add > another file-backed disk to your domU and expand its size that way.... > > On Tue, 7 Nov 2006, Jeff wrote: > >> I have created an xp domain and fc6 domain but I picked too small of size >> for the image. >> >> My xp domain is using a physical device (logical volume) and my fc6 domain >> is using a file for the mapped disk. >> >> Isn't there a way to enlarge the filesystem of the guest by enlarging the >> backing file/device? If so, what exactly do you do to enlarge the backing >> file/dev? >> >> --- >> Thanks, >> Jeff >> >> -- >> 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 paul at xelerance.com Tue Nov 7 18:47:39 2006 From: paul at xelerance.com (Paul Wouters) Date: Tue, 7 Nov 2006 19:47:39 +0100 (CET) Subject: [Fedora-xen] enlarge file backed filesystem In-Reply-To: References: <45507665.7080809@kreska.org> Message-ID: > > Isn't there a way to enlarge the filesystem of the guest by enlarging the > > backing file/device? If so, what exactly do you do to enlarge the backing > > file/dev? For ext3 I use (in this case adding 1GB): dd if=/dev/zero bs=1M count=1024 >> file.image e2fsck -f file.image resize2fs file.image e2fsck -f file.image Paul From master at bradleyland.com Tue Nov 7 21:21:46 2006 From: master at bradleyland.com (master at bradleyland.com) Date: Tue, 7 Nov 2006 13:21:46 -0800 (PST) Subject: [Fedora-xen] FC6/Xen -- any show-stopping issues? Message-ID: <34004.204.174.64.37.1162934506.squirrel@www.bradleyland.com> I upgraded one of my boxes from FC4 (worked great with xen) to FC5 and have waited for months for the issues with iptables/NAT/kernel crash to be sorted out and corrected. Now all seems well; FC5 and xen seem ready to go. But... FC6 is available. So I'm trying to decide if I should go with FC5/xen or upgrade to FC6/xen (since this box isn't being used yet). Before I commit the box to production, I'd prefer upgrading to FC6/xen so I don't need to upgrade it in 4-6 months. Are there any known, nasty show-stoppers with FC6 and xen? or with FC6 in general? This machine will be used to host several VMs: firewall, web server, mail server, dns, squid, etc. 32 bit, only Fedora FCx dom0 and guests. Thanks, Dave From berrange at redhat.com Tue Nov 7 21:30:55 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 7 Nov 2006 21:30:55 +0000 Subject: [Fedora-xen] FC6/Xen -- any show-stopping issues? In-Reply-To: <34004.204.174.64.37.1162934506.squirrel@www.bradleyland.com> References: <34004.204.174.64.37.1162934506.squirrel@www.bradleyland.com> Message-ID: <20061107213055.GC25965@redhat.com> On Tue, Nov 07, 2006 at 01:21:46PM -0800, master at bradleyland.com wrote: > I upgraded one of my boxes from FC4 (worked great with xen) to FC5 and > have waited for months for the issues with iptables/NAT/kernel crash to be > sorted out and corrected. Now all seems well; FC5 and xen seem ready to > go. > > But... FC6 is available. So I'm trying to decide if I should go with > FC5/xen or upgrade to FC6/xen (since this box isn't being used yet). > > Before I commit the box to production, I'd prefer upgrading to FC6/xen so > I don't need to upgrade it in 4-6 months. > > Are there any known, nasty show-stoppers with FC6 and xen? or with FC6 in > general? With the latest errata we pushed to FC5, the Xen stacks & kernels on both FC5 and FC6 are practically identical[1] - they're both running 2.6.18 kernels with Xen 3.0.3 hypervisor & kernel & userspace bits. So in terms of guest OS compatability, stability,performance, etc you shouldn't see any difference between Xen in FC5 & FC6 (assuming both a fully yum update'd). Thus I'd recommend FC6 since you'll get a longer lifetime before needing to do another major upgrade. Regards, Dan. [1] In fact FC5 is currently a couple of changesets ahead of FC6, but we'll have an errata for FC6 to update this soon... -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From itamar at ispbrasil.com.br Tue Nov 7 21:41:38 2006 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 7 Nov 2006 19:41:38 -0200 Subject: [Fedora-xen] enlarge file backed filesystem References: <45507665.7080809@kreska.org> Message-ID: <00cb01c702b7$85fd28e0$0a00000a@ispbrasil> this is the correct way to resize dd if=/dev/zero of=root_fs.ext3 bs=1 count=1 seek=2G conv=notrunc e2fsck -f root_fs.ext3 -y resize2fs -p root_fs.ext3 replace root_fs.ext3 with the filesystem name replace 2g with new size of the filesystem image more details here http://user-mode-linux.sourceforge.net/resize.html -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 > >> > Isn't there a way to enlarge the filesystem of the guest by enlarging >> > the >> > backing file/device? If so, what exactly do you do to enlarge the >> > backing >> > file/dev? > > For ext3 I use (in this case adding 1GB): > > dd if=/dev/zero bs=1M count=1024 >> file.image > e2fsck -f file.image > resize2fs file.image > e2fsck -f file.image > > Paul > From adrian at creative.net.au Wed Nov 8 01:21:54 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Wed, 8 Nov 2006 09:21:54 +0800 Subject: [Fedora-xen] Re: [Xen-users] memory issues with FC5.2200 kernels In-Reply-To: <907625E08839C4409CE5768403633E0B018E16D1@sefsexmb1.amd.com> References: <20061107152621.GC1133@skywalker.creative.net.au> <907625E08839C4409CE5768403633E0B018E16D1@sefsexmb1.amd.com> Message-ID: <20061108012154.GA6893@skywalker.creative.net.au> On Tue, Nov 07, 2006, Petersson, Mats wrote: > > the domU or dom0? > > The one with "id=0", so Dom0. Duh. :) > > No idea. I've got half a dozen domU's here all running > > various tasks each > > (smtp, dns, www, etc.) so its difficult to pin down what each > > is doing. > > That makes debugging it quite difficult... > > Perhaps you can set up a machine for testing to find out what's causing > it, if there's some pattern to it, etc, etc. I've got two test Xen servers which were running FC5.2200 Xen just fine. I've been bitten by previous networking bugs with the FC5 kernels (specifically kernel panics in the netblk stuff) which people have noticed but I can't see any fixes for. I hadn't seen any panics during my testing over two weeks so I moved this one production server over. Adrian From paul at xelerance.com Wed Nov 8 05:06:57 2006 From: paul at xelerance.com (Paul Wouters) Date: Wed, 8 Nov 2006 06:06:57 +0100 (CET) Subject: [Fedora-xen] FC6/Xen -- any show-stopping issues? In-Reply-To: <34004.204.174.64.37.1162934506.squirrel@www.bradleyland.com> References: <34004.204.174.64.37.1162934506.squirrel@www.bradleyland.com> Message-ID: On Tue, 7 Nov 2006, master at bradleyland.com wrote: > Are there any known, nasty show-stoppers with FC6 and xen? or with FC6 in > general? For me, broken or severely degraded /dev/random support. Paul -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From jeff at kreska.org Wed Nov 8 11:53:08 2006 From: jeff at kreska.org (Jeff) Date: Wed, 08 Nov 2006 05:53:08 -0600 Subject: [Fedora-xen] enlarge file backed filesystem In-Reply-To: <1162909016.7552.19.camel@amd.cathrow.org> References: <45507665.7080809@kreska.org> <1162909016.7552.19.camel@amd.cathrow.org> Message-ID: <4551C524.8080609@kreska.org> I guess I don't understand how to fix the partition size using unix tools. Here is what I tried for a ntfs file backed system: #add a gig to file dd if=/dev/zero bs=1M count=1024 >> file.image parted file.image Disk /vserver/images/xp.img: 3171MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 2093MB 2093MB primary ntfs boot 2093MB 3171MB 1078MB Free Space (parted) resize 1 32.3kB 3171MB No Implementation: Support for opening ntfs file systems is not implemented yet. Not sure how to fix partition table and image is not bootable at this point. I tryed ntfsresize ntfsresize v1.13.1 (libntfs 9:0:0) Device name : /dev/mapper/loop1p1 NTFS volume version: 3.1 Cluster size : 2048 bytes Current volume size: 2093253120 bytes (2094 MB) Current device size: 2093253120 bytes (2094 MB) New volume size : 2999996928 bytes (3000 MB) ERROR: New size can't be bigger than the device size. If you want to enlarge NTFS then first enlarge the device size by e.g. fdisk. Andrew Cathrow wrote: > Ouch, > It's possible but not nice. > > Obviously the first step is to back up your existing file before you try > any of this .... > > First step is you need to enlarge the file itself. > Use dd to to this for example > dd if=/dev/zero of=myImage.img seek=***** bs=1M count=1 > > The seek value should be big enough to seek past the current data so we > don't overwrite anything - so for example make it a 2gb past the end of > the file. > You now have a larger sparse file. > At this point you have a larger disk but your partition table is out of > whack. > So you need to use a tool like parted/gparted to change the partition > table. You can also use fdisk if you're feeling brave. > These tools won't work directly on a file, so you'll need to create a > block device for that image, you can use kpartx for this, see the link > below > http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184aece3efe822be0ef6dd1871cd > > When you've enlarged the partition to the correct size then you'll need > to resize the ntfs file system - for this you'll need ntfsresize. > http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html > > Good luck, don't forget the backup ! > > Aic > > > > > On Tue, 2006-11-07 at 06:04 -0600, Jeff wrote: > >> I have created an xp domain and fc6 domain but I picked too small of >> size for the image. >> >> My xp domain is using a physical device (logical volume) and my fc6 >> domain is using a file for the mapped disk. >> >> Isn't there a way to enlarge the filesystem of the guest by enlarging >> the backing file/device? If so, what exactly do you do to enlarge the >> backing file/dev? >> >> --- >> Thanks, >> Jeff >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> > > From valmirpas at brturbo.com.br Wed Nov 8 14:55:06 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 12:55:06 -0200 Subject: [Fedora-xen] HI Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error Type: application/octet-stream Size: 310 bytes Desc: not available URL: From valmirpas at brturbo.com.br Wed Nov 8 14:50:59 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 12:50:59 -0200 Subject: [Fedora-xen] INSTALL WINDOWS XP - VIRTU-MANAGER - KERNEL-XEN Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error Type: application/octet-stream Size: 310 bytes Desc: not available URL: From valmirpas at brturbo.com.br Wed Nov 8 14:58:51 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 12:58:51 -0200 Subject: [Fedora-xen] HI, CAN YOU HELP ME? Message-ID: I AM FROM BRAZIL, IN STATE OF SAINT CATARINE, CITY ITAPEMA..... And I use VMware Workstation 5.5, but dont runs on FEDORA-XEN, And I like install Windows XP on kernel XEN because I dont want have two KERNELS in my Fedora Core 6.0, then occors in step 3 one error that I dont know what to do? If the poossibel to send to me one PDF, ARTICLE that example me what I DO?????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From riel at redhat.com Wed Nov 8 16:13:52 2006 From: riel at redhat.com (Rik van Riel) Date: Wed, 08 Nov 2006 11:13:52 -0500 Subject: [Fedora-xen] HI In-Reply-To: References: Message-ID: <45520240.1080307@redhat.com> valmirpas at brturbo.com.br wrote: > EROR ON VIRT-MANAGER It would help if you told us what you were trying to do, what went wrong, exactly what the error message was, what configuration you were running, etc... A 3 word error "description" is not going to be useful to anybody. -- All Rights Reversed From valmirpas at brturbo.com.br Wed Nov 8 14:46:30 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 12:46:30 -0200 Subject: [Fedora-xen] VIRT-MANAGER Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error Type: application/octet-stream Size: 310 bytes Desc: not available URL: From itamar at ispbrasil.com.br Wed Nov 8 16:24:51 2006 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 8 Nov 2006 14:24:51 -0200 Subject: [Fedora-xen] HI, CAN YOU HELP ME? References: Message-ID: <004e01c70352$6f5f32e0$0a00000a@ispbrasil> seu ingles ? ruim demais meu filho. escreve em portugues mesmo. nomes de pessoas, cidades etc.. nao devem ser traduzidos para o ingles. vc mora na santa catarina n? ? fa?a um cursinho de ingles, ir? te ajudar bastante. -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: valmirpas at brturbo.com.br To: Berrange, Daniel ; FEDORA-XEN Cc: Valmir Passero Sent: Wednesday, November 08, 2006 12:58 PM Subject: [Fedora-xen] HI, CAN YOU HELP ME? I AM FROM BRAZIL, IN STATE OF SAINT CATARINE, CITY ITAPEMA..... And I use VMware Workstation 5.5, but dont runs on FEDORA-XEN, And I like install Windows XP on kernel XEN because I dont want have two KERNELS in my Fedora Core 6.0, then occors in step 3 one error that I dont know what to do? If the poossibel to send to me one PDF, ARTICLE that example me what I DO?????? ------------------------------------------------------------------------------ -- 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 itamar at ispbrasil.com.br Wed Nov 8 16:22:26 2006 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 8 Nov 2006 14:22:26 -0200 Subject: [Fedora-xen] VIRT-MANAGER References: Message-ID: <002b01c70352$1910ee10$0a00000a@ispbrasil> qual mensagem ? please don't send attched files. -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: valmirpas at brturbo.com.br To: fedora-xen at redhat.com Cc: valmirpas at brturbo.com.br Sent: Wednesday, November 08, 2006 12:46 PM Subject: [Fedora-xen] VIRT-MANAGER I WANT INSTALL WINDOWS XP ON KERNEL-XEN... BUT THIS MESSAGE OCCURS...ANEXO!!!!! ------------------------------------------------------------------------------ -- 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 cristina.tanzitolenti at provincia.cremona.it Wed Nov 8 15:47:58 2006 From: cristina.tanzitolenti at provincia.cremona.it (Cristina Tanzi Tolenti) Date: Wed, 08 Nov 2006 16:47:58 +0100 Subject: [Fedora-xen] error with virt-manager Message-ID: <4551FC2E.8070807@provincia.cremona.it> Hi, I would like to create a FC4 guest over my new FC6 domain, so I use virt-manager...when I finish the wizard I have this error: Guest Install Error ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Date: Wed, 08 Nov 2006 15:37:00 GMT Server: Apache/2.0.52 (Red Hat) Last-Modified: Wed, 08 Nov 2006 15:16:09 GMT ETag: "2896fb-1051-cc6be040" Accept-Ranges: bytes Content-Length: 4177 Connection: close Content-Type: text/html; charset=UTF-8 Why? this is the summary: machine name: lokildap virtualization method: paravirtualized installation source: http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/ kickstart source: Disk image /xen/fedora/fc4 disk size: 4000mb Maximum memory: 256 mb Initial memory: 128mb Virtual CPU: 1 thank you -- ------------------------------------------------- Cristina Tanzi Tolenti CED - Provincia di Cremona C.so V.Emanuele II, 17 - 26100 Cremona tel. 0372/406362 e-mail cristina.tanzitolenti at provincia.cremona.it ------------------------------------------------- From berrange at redhat.com Wed Nov 8 17:39:51 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 8 Nov 2006 17:39:51 +0000 Subject: [Fedora-xen] error with virt-manager In-Reply-To: <4551FC2E.8070807@provincia.cremona.it> References: <4551FC2E.8070807@provincia.cremona.it> Message-ID: <20061108173951.GD21987@redhat.com> On Wed, Nov 08, 2006 at 04:47:58PM +0100, Cristina Tanzi Tolenti wrote: > Hi, > > I would like to create a FC4 guest over my new FC6 domain, so I use > virt-manager...when I finish the wizard I have this error: > > Guest Install Error > ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Date: Wed, > 08 Nov 2006 15:37:00 GMT > Server: Apache/2.0.52 (Red Hat) > Last-Modified: Wed, 08 Nov 2006 15:16:09 GMT > ETag: "2896fb-1051-cc6be040" > Accept-Ranges: bytes > Content-Length: 4177 > Connection: close > Content-Type: text/html; charset=UTF-8 > > Why? It is trying to fetch the Xen kernel from the download location. Since FC4 does not support Xen there is no kernel to fetch & this you get this 404 error. We should do better reporting in this case really. > this is the summary: > machine name: lokildap > virtualization method: paravirtualized > installation source: > http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/ > kickstart source: > Disk image /xen/fedora/fc4 > disk size: 4000mb > Maximum memory: 256 mb > Initial memory: 128mb > Virtual CPU: 1 Since FC4 has no Xen support you'll need to do a fully-virtualized install instead (assuming you have VT support in your CPU) Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From calimeral at gmail.com Wed Nov 8 18:59:46 2006 From: calimeral at gmail.com (Cyril Olivier) Date: Wed, 8 Nov 2006 12:59:46 -0600 Subject: [Fedora-xen] Cannot input in guest console Message-ID: <99ef937b0611081059g41c865eaib6ff35cee0fa292d@mail.gmail.com> I create succesfully a FC6 guest, but in console i see the output of the guest but i cannot input anything. xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 366 1 r----- 464.9 fedora.fc6 1 128 1 -b---- 16.4 The guest is in state bloscked, but it doesn't seems to be the problem. Do i need to do something special to take control of guest via console ? Thank you, Cyrille -------------- next part -------------- An HTML attachment was scrubbed... URL: From valmirpas at brturbo.com.br Wed Nov 8 19:09:22 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 17:09:22 -0200 Subject: [Fedora-xen] virt-manager (Fedora Core 6.0) Message-ID: ERROR:Invalid URL location given:[Errno 4] OError: -------------- next part -------------- A non-text attachment was scrubbed... Name: valmirpas.vcf Type: text/x-vcard Size: 183 bytes Desc: Card for URL: From valmirpas at brturbo.com.br Wed Nov 8 19:17:00 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 17:17:00 -0200 Subject: [Fedora-xen] virt-manager (Fedora Core 6.0) Message-ID: ERROR:Invalid URL location given:[Errno 4] OError: -------------- next part -------------- A non-text attachment was scrubbed... Name: valmirpas.vcf Type: text/x-vcard Size: 183 bytes Desc: Card for URL: From berrange at redhat.com Wed Nov 8 19:32:55 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 8 Nov 2006 19:32:55 +0000 Subject: [Fedora-xen] Re: virt-manager (Fedora Core 6.0) In-Reply-To: References: Message-ID: <20061108193255.GG21987@redhat.com> Please post the contents of /root/.virt-manager/virt-manager.log which will contain more useful debug information than this. On Wed, Nov 08, 2006 at 05:17:00PM -0200, valmirpas at brturbo.com.br wrote: > ERROR:Invalid URL location given:[Errno 4] OError: ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: > Date: Web, 08 Nov 2006 17:51:15 GMT > Server: Apache/2.2.3(Fedora) > Content-Length: 304 > Connection:close > Content-Type:text/html;cahrset==iso-8859-1 > (I PUT ONE URL==http://127.0.0.1/win/setup.exe) > (DIRECTORY IS==/var/www/html/win/..............<<<---WINDOW XP PROFESSIONAL Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From valmirpas at brturbo.com.br Wed Nov 8 19:11:04 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 17:11:04 -0200 Subject: [Fedora-xen] Enc: virt-manager (Fedora Core 6.0) Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: valmirpas at brturbo.com.br Subject: virt-manager (Fedora Core 6.0) Date: Wed, 08 Nov 2006 17:09:22 -0200 Size: 3345 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: valmirpas.vcf Type: text/x-vcard Size: 183 bytes Desc: Card for URL: From valmirpas at brturbo.com.br Wed Nov 8 20:35:47 2006 From: valmirpas at brturbo.com.br (valmirpas at brturbo.com.br) Date: Wed, 08 Nov 2006 18:35:47 -0200 Subject: [Fedora-xen] Re: virt-manager (Fedora Core 6.0) - (virt-manager.log) Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log-virt.log Type: text/x-log Size: 3072 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: valmirpas.vcf Type: text/x-vcard Size: 183 bytes Desc: Card for URL: From javahollic at gmail.com Thu Nov 9 09:30:58 2006 From: javahollic at gmail.com (Andy Brook) Date: Thu, 9 Nov 2006 09:30:58 +0000 Subject: [Fedora-xen] Ubuntu/virt-manager ? In-Reply-To: <20061102191139.GE4786@redhat.com> References: <1162466121.18078.8.camel@localhost.localdomain> <20061102191139.GE4786@redhat.com> Message-ID: Thanks for that Dan, I downloaded the source RPM, but there isn't a clue on how to install it - I'm a python noob, so any advice on where to put the .py's would be great! thanks andy On 02/11/06, Daniel P. Berrange wrote: > > On Thu, Nov 02, 2006 at 11:15:20AM +0000, axb wrote: > > Greetings! > > > > I've been trying to get virt-manager running on AMD64 Ubuntu 6.10, both > > virt-manager-0.2.5 and libvirt-0.1.8 compile and install successfully > > but I cant run virt manager, I get some seeingly simple error: > > > > Traceback (most recent call last): > > File "/usr/local/share/virt-manager/virt-manager.py", line 104, in ? > > from virtManager.engine import vmmEngine > > File "/usr/local/share/virt-manager/virtManager/engine.py", line 33, > > in ? > > from virtManager.create import vmmCreate > > File "/usr/local/share/virt-manager/virtManager/create.py", line 25, > > in ? > > import virtinst > > ImportError: No module named virtinst > > As well as virt-manager & libvirt, you need to install python-virtinst > which provides a higher level API around libvirt for provisioning guest > virtual machines. The mercurial repo is here: > > http://hg.et.redhat.com/virt/applications/virtinst--devel > > Or you can get the tar.gz from the src.rpm files in FC6. > > Dan > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=| > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kzak at redhat.com Thu Nov 9 09:54:49 2006 From: kzak at redhat.com (Karel Zak) Date: Thu, 9 Nov 2006 10:54:49 +0100 Subject: [Fedora-xen] problems installing winxp with full virtualization on FC6 In-Reply-To: References: Message-ID: <20061109095449.GD4324@petra.dvoda.cz> On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett wrote: I successfully tried install WinXP last week. $ xenguest-install -n winxp-i686-full -r 500 -f /org/xen/winxp-i686-full.img -s 4 --vnc -v -c /dev/scd0 # rpm -q xen kernel-xen python-xeninst xen-3.0.3-0.1.rc3 kernel-xen-2.6.18-1.2798.fc6 python-xeninst-0.93.0-1 The *final* domain config (generated by xenquest-install): # Automatically generated xen config file name = "winxp-i686-full" builder = "hvm" memory = "500" disk = [ 'file:/xen/winxp-i686-full.img,hda,w', ] vif = [ 'type=ioemu, mac=00:16:3e:2d:ec:27, bridge=xenbr0', ] uuid = "42f399ce-699a-fafc-4e18-37e17f49aabd" device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' > I see from googling, that this bug has been reported once before > (last month with a rawhide build) - but no answers. A little further > googling indicates that one possible workaround might be to hit F5 > (when it is asking for F6 to load drivers) during the setup process I've used this trick too. The key F5 works for me in vncviewer (vnc-4.1.1-39.fc5 -- my workstation is FC5, the server with Xen is FC6). The Windows installer allows to select some install profiles if you press F5 -- but things probably depend on XP version, because the menu for F5 contains different profiles in different XP versions (I've used Czech XP edition and there was two profiles only). > Advice??? Don't use Close Source Operation Systems :-) Karel -- Karel Zak From kzak at redhat.com Thu Nov 9 10:36:39 2006 From: kzak at redhat.com (Karel Zak) Date: Thu, 9 Nov 2006 11:36:39 +0100 Subject: [Fedora-xen] FC6 and Xen for full virtualization In-Reply-To: References: Message-ID: <20061109103639.GF4324@petra.dvoda.cz> On Mon, Nov 06, 2006 at 03:11:51PM +0100, Laurent Flesch wrote: > Hi, > > I'm a new FC user. > I'm trying to install FC6 with Xen for full Virtualization (on an AMD 3800+ > X2). > > When I try to create a new VM with virt-manager using an image file, the > creation interrupts with a Domain creating error. Xen log gives an error > like "fime image does not exist". Even if I create this file before with dd, > I obtain the same error. > > Please do I have an idea about what happens ? selinux? Try: setenforce 0 karel -- Karel Zak From davidsen at tmr.com Wed Nov 8 02:06:01 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Tue, 07 Nov 2006 21:06:01 -0500 Subject: [Fedora-xen] I broke down and did it Message-ID: Tinight I broke down and ordered an upgrade package to get a CPU with real virtualization. I really want to be able to run a small Windows machine for a single application, this seems to get me there. What do people do about XP wanting to register? Or do I leave the app on 98SE? -- Bill Davidsen Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion. From cristina.tanzitolenti at provincia.cremona.it Thu Nov 9 11:23:02 2006 From: cristina.tanzitolenti at provincia.cremona.it (Cristina Tanzi Tolenti) Date: Thu, 09 Nov 2006 12:23:02 +0100 Subject: [Fedora-xen] error with virt-manager In-Reply-To: <20061108173951.GD21987@redhat.com> References: <4551FC2E.8070807@provincia.cremona.it> <20061108173951.GD21987@redhat.com> Message-ID: <45530F96.7030806@provincia.cremona.it> Daniel P. Berrange ha scritto: > On Wed, Nov 08, 2006 at 04:47:58PM +0100, Cristina Tanzi Tolenti wrote: > >> Hi, >> >> I would like to create a FC4 guest over my new FC6 domain, so I use >> virt-manager...when I finish the wizard I have this error: >> >> Guest Install Error >> ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Date: Wed, >> 08 Nov 2006 15:37:00 GMT >> Server: Apache/2.0.52 (Red Hat) >> Last-Modified: Wed, 08 Nov 2006 15:16:09 GMT >> ETag: "2896fb-1051-cc6be040" >> Accept-Ranges: bytes >> Content-Length: 4177 >> Connection: close >> Content-Type: text/html; charset=UTF-8 >> >> Why? >> > > It is trying to fetch the Xen kernel from the download location. Since > FC4 does not support Xen there is no kernel to fetch & this you get this > 404 error. We should do better reporting in this case really. > > >> this is the summary: >> machine name: lokildap >> virtualization method: paravirtualized >> installation source: >> http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/ >> kickstart source: >> Disk image /xen/fedora/fc4 >> disk size: 4000mb >> Maximum memory: 256 mb >> Initial memory: 128mb >> Virtual CPU: 1 >> > > Since FC4 has no Xen support you'll need to do a fully-virtualized > install instead (assuming you have VT support in your CPU) > > Regards, > Dan. > Unfortunately my CPU don't support VT, and if I try RHEL4.4 instead of FC4? thany you -------------- next part -------------- An HTML attachment was scrubbed... URL: From bstein at redhat.com Thu Nov 9 10:06:45 2006 From: bstein at redhat.com (Brian Stein) Date: Thu, 09 Nov 2006 05:06:45 -0500 Subject: [Fedora-xen] error with virt-manager In-Reply-To: <45530F96.7030806@provincia.cremona.it> References: <4551FC2E.8070807@provincia.cremona.it> <20061108173951.GD21987@redhat.com> <45530F96.7030806@provincia.cremona.it> Message-ID: <1163066805.3413.4.camel@localhost.localdomain> On Thu, 2006-11-09 at 12:23 +0100, Cristina Tanzi Tolenti wrote: > Daniel P. Berrange ha scritto: > > On Wed, Nov 08, 2006 at 04:47:58PM +0100, Cristina Tanzi Tolenti wrote: > > > > > Hi, > > > > > > I would like to create a FC4 guest over my new FC6 domain, so I use > > > virt-manager...when I finish the wizard I have this error: > > > > > > Guest Install Error > > > ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Date: Wed, > > > 08 Nov 2006 15:37:00 GMT > > > Server: Apache/2.0.52 (Red Hat) > > > Last-Modified: Wed, 08 Nov 2006 15:16:09 GMT > > > ETag: "2896fb-1051-cc6be040" > > > Accept-Ranges: bytes > > > Content-Length: 4177 > > > Connection: close > > > Content-Type: text/html; charset=UTF-8 > > > > > > Why? > > > > > > > It is trying to fetch the Xen kernel from the download location. Since > > FC4 does not support Xen there is no kernel to fetch & this you get this > > 404 error. We should do better reporting in this case really. > > ... > > Unfortunately my CPU don't support VT, and if I try RHEL4.4 instead of > FC4? There will be a pv kernel in RHEL4.5, but currently this would fail in the same way. From xmlsec at gmail.com Thu Nov 9 13:18:53 2006 From: xmlsec at gmail.com (Kenneth Jensen) Date: Thu, 9 Nov 2006 14:18:53 +0100 Subject: [Fedora-xen] No network on FC6 host system Message-ID: I just upgraded a Xen host system from FC5 to FC6, and with that I lost networking... When I boot the system without starting the xend service, networking is fine. I have removed all iptables rules, so there is just "-j ACCEPT" for INPUT, OUTPUT and FORWARD chains. Everything is A-OK. When I start the xend service, it brings up the vif0.1 and the peth1 and connects them with xenbr1. Then I lose all connectivity. Atfer that, I can ifup and ifdown all day, play with brctl and whatnot - nothing seems to help but rebooting the system. I even tried removing all xen software, remove the config directory, reboot the system and then installing the whole thing again - to get the default configs. And before that, my configs were pretty straight-forward - nothing fancy. I keep thinking I overlooked something obvious... Any hints? --- Cheers, Kenneth From berrange at redhat.com Thu Nov 9 13:33:14 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 13:33:14 +0000 Subject: [Fedora-xen] Ubuntu/virt-manager ? In-Reply-To: References: <1162466121.18078.8.camel@localhost.localdomain> <20061102191139.GE4786@redhat.com> Message-ID: <20061109133314.GB10217@redhat.com> On Thu, Nov 09, 2006 at 09:30:58AM +0000, Andy Brook wrote: > Thanks for that Dan, > I downloaded the source RPM, but there isn't a clue on how to install it - > I'm a python noob, so any advice on where to put the .py's would be great! > thanks Regular python install procedure is basically: # python setup.py install Which will copy python bits to the correct places > > On 02/11/06, Daniel P. Berrange wrote: > > > >On Thu, Nov 02, 2006 at 11:15:20AM +0000, axb wrote: > >> Greetings! > >> > >> I've been trying to get virt-manager running on AMD64 Ubuntu 6.10, both > >> virt-manager-0.2.5 and libvirt-0.1.8 compile and install successfully > >> but I cant run virt manager, I get some seeingly simple error: > >> > >> Traceback (most recent call last): > >> File "/usr/local/share/virt-manager/virt-manager.py", line 104, in ? > >> from virtManager.engine import vmmEngine > >> File "/usr/local/share/virt-manager/virtManager/engine.py", line 33, > >> in ? > >> from virtManager.create import vmmCreate > >> File "/usr/local/share/virt-manager/virtManager/create.py", line 25, > >> in ? > >> import virtinst > >> ImportError: No module named virtinst > > > >As well as virt-manager & libvirt, you need to install python-virtinst > >which provides a higher level API around libvirt for provisioning guest > >virtual machines. The mercurial repo is here: > > > >http://hg.et.redhat.com/virt/applications/virtinst--devel > > > >Or you can get the tar.gz from the src.rpm files in FC6. > > Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From javahollic at gmail.com Thu Nov 9 13:58:34 2006 From: javahollic at gmail.com (axb) Date: Thu, 09 Nov 2006 13:58:34 +0000 Subject: [Fedora-xen] AMD64 Ubuntu/virt-manager ? In-Reply-To: <20061109133314.GB10217@redhat.com> References: <1162466121.18078.8.camel@localhost.localdomain> <20061102191139.GE4786@redhat.com> <20061109133314.GB10217@redhat.com> Message-ID: <1163080714.31928.16.camel@localhost.localdomain> Thanks Dan, original error now gone, However I now get the following which looks like it could be a 64bitness problem, after running 'virt-manager' I get:- Traceback (most recent call last): File "/usr/local/share/virt-manager/virt-manager.py", line 61, in ? import gtk File "/var/lib/python-support/python2.4/gtk-2.0/gtk/__init__.py", line 48, in ? from gtk import _gtk File "/usr/lib/python2.5/site-packages/cairo/__init__.py", line 1, in ? from _cairo import * ImportError: /usr/lib/python2.5/site-packages/cairo/_cairo.so: undefined symbol: Py_InitModule4_64 --------- I've checked installed cairo libs; I have libcairo2 & libcairo2-dev, libcairo-directfb as well as python-cairo/python-cairo-dev all to no avail. Again stumped, andy. From berrange at redhat.com Thu Nov 9 14:28:13 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 14:28:13 +0000 Subject: [Fedora-xen] Re: AMD64 Ubuntu/virt-manager ? In-Reply-To: <1163080714.31928.16.camel@localhost.localdomain> References: <1162466121.18078.8.camel@localhost.localdomain> <20061102191139.GE4786@redhat.com> <20061109133314.GB10217@redhat.com> <1163080714.31928.16.camel@localhost.localdomain> Message-ID: <20061109142813.GA5223@redhat.com> On Thu, Nov 09, 2006 at 01:58:34PM +0000, axb wrote: > Thanks Dan, original error now gone, > However I now get the following which looks like it could be a 64bitness > problem, after running 'virt-manager' I get:- > > Traceback (most recent call last): > File "/usr/local/share/virt-manager/virt-manager.py", line 61, in ? > import gtk > File "/var/lib/python-support/python2.4/gtk-2.0/gtk/__init__.py", line > 48, in ? > from gtk import _gtk > File "/usr/lib/python2.5/site-packages/cairo/__init__.py", line 1, > in ? > from _cairo import * > ImportError: /usr/lib/python2.5/site-packages/cairo/_cairo.so: undefined > symbol: Py_InitModule4_64 > > --------- > > I've checked installed cairo libs; I have libcairo2 & libcairo2-dev, > libcairo-directfb as well as python-cairo/python-cairo-dev all to no > avail. Looks like your python install is fubar - that stack trace has some paths from python 2.4 and some from 2.5 While it may be source level compatible for the most part, its certainly not ABI compatible so I can't see a GTK for python 2.4 working with a Cairo for python 2.5 Regards, Dan, -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at paulororke.net Thu Nov 9 14:35:27 2006 From: paul at paulororke.net (Paul O'rorke) Date: Thu, 09 Nov 2006 06:35:27 -0800 Subject: [Fedora-xen] dissapearing guests Message-ID: <45533CAF.1080800@paulororke.net> maybe I've missed something but if I reboot or shutdown a guest domain I can't start it again. xm --list doesn't show the domain. From the Virtual Machine Manager (FC6) if I go : File --> Restore saved machine (Restore a saved machine from a filesystem image) and pint to /vm/webserver I get a dialogue box stating: *Error restoring domain '/vm/webserver'. Is the domain already running?* Similary if I try to restore from the disk file with xm restore I get the following: *# xm restore /vm/webserver* *Error: Restore failed* *Usage: xm restore * *Restore a domain from a saved state.* I'm guessing that the disk file is not the correct file to restore from - ?? but I can't find anywhere documentation on how to open these machines. This is my first bash at virtualization in Xen so I appologize if I've missed something in the docs. What can I do to open this guest? -------------- next part -------------- An HTML attachment was scrubbed... URL: From markwiz at us.ibm.com Thu Nov 9 14:32:46 2006 From: markwiz at us.ibm.com (Mark Wisner) Date: Thu, 9 Nov 2006 09:32:46 -0500 Subject: [Fedora-xen] What source RPM contains the virt manager source? Message-ID: I am looking for the source for virt manager. What source RPM would I find it in? Thanks, Mark K. Wisner Advisory Software Engineer IBM Linux Technology Center 3039 Cornwallis Rd RTP, NC 27709 Tel. 919-754-4274 Cell 919-649-5813 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.mylists at gmail.com Thu Nov 9 15:23:59 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Thu, 9 Nov 2006 16:23:59 +0100 Subject: [Fedora-xen] FC6 : Xen and HVM => console unavailable error Message-ID: Hi all, I am desperately trying to user Xen on FC6. When I try to create an HVM with virt-manager, the domain seems to start but no graphical window opens. I only have a virt-manager window with "Console currently unavailable" error. I found not special message in xen logs. Please, could you help me ? I really would like making it to work ! Thanks a lot -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Nov 9 15:35:16 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 15:35:16 +0000 Subject: [Fedora-xen] What source RPM contains the virt manager source? In-Reply-To: References: Message-ID: <20061109153516.GB5223@redhat.com> On Thu, Nov 09, 2006 at 09:32:46AM -0500, Mark Wisner wrote: > I am looking for the source for virt manager. What source RPM would I find > it in? The cunningly named 'virt-manager' RPM :-) http://download.fedora.devel.redhat.com/pub/fedora/linux/core/6/source/SRPMS/virt-manager-0.2.3-2.fc6.src.rpm There's a newer release up on the website though that's not pushed to Fedora yet: http://virt-manager.et.redhat.com/download.html Or go straight for the mercurial source repo: http://virt-manager.et.redhat.com/scmrepo.html Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From chris at base2technology.com Thu Nov 9 15:55:29 2006 From: chris at base2technology.com (Chris Hirsch) Date: Thu, 09 Nov 2006 08:55:29 -0700 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <454A1BA3.7080606@emitony.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> Message-ID: <45534F71.5090504@base2technology.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm about to go down the same route. I have FC5 domU's and I was thinking about trying the in-place upgrade from FC5->FC6 for each domU. Does anybody have any experience with this? I don't think it would be to bad given that all of my domU's are console only so no X or anything to deal with. Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFU09w1ba7yLNz0PERAojdAJ4mYbvkVdSqMji0Mnlz+bAizgE7rACfcJdu xBU/Zb8yPZfrA/K2GXFu/FU= =qnjf -----END PGP SIGNATURE----- From xmlsec at gmail.com Thu Nov 9 15:57:28 2006 From: xmlsec at gmail.com (Kenneth Jensen) Date: Thu, 9 Nov 2006 16:57:28 +0100 Subject: [Fedora-xen] Xen + FC6 on Centrino = no go? Message-ID: Oh, another question - just to confirm my fears... I seem to be unable to boot my laptop with Intel Pentium M cpu into the FC6 Xen kernel. While googling for a solution, I have found that the Fedora Wiki says this about Xen on FC6: "To run i386 guests requires a CPU with the PAE extension. " That essentially means that I have to build my own kernel if I intend to continue running Xen, right? (alternatively choose another distro...) Why has support for the xen0/xenU type kernel been cancelled in FC6? (Sorry if this has been discussed before, I couldn't find much about it) --- Cheers, Kenneth From berrange at redhat.com Thu Nov 9 16:03:17 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 16:03:17 +0000 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <45534F71.5090504@base2technology.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> Message-ID: <20061109160317.GC5223@redhat.com> On Thu, Nov 09, 2006 at 08:55:29AM -0700, Chris Hirsch wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm about to go down the same route. I have FC5 domU's and I was > thinking about trying the in-place upgrade from FC5->FC6 for each domU. > Does anybody have any experience with this? I don't think it would be to > bad given that all of my domU's are console only so no X or anything to > deal with. If you are on x86_64 you shouldn't see any Xen specific proiblems with doing upgrades. i386 is a little more complicated though because we switched from non-PAE to PAE in the Xen kernels - so if you were to upgrade your host without first preparing your guests you'll be unable to boot the guests after the upgrade. The solution is fairly simple though - the latest FC5 errata also provides a 'kernel-xen' RPM which is PAE enabled. So before upgrading your host, just make sure you have done 'yum install kernel-xen' in each of your guests. This will let your FC5 guests contonue working on an FC6 host - you can then upgrade your guests to FC6 at will. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jmorris at redhat.com Thu Nov 9 16:22:29 2006 From: jmorris at redhat.com (James Morris) Date: Thu, 9 Nov 2006 11:22:29 -0500 (EST) Subject: [Fedora-xen] FC6 and Xen for full virtualization In-Reply-To: <20061109103639.GF4324@petra.dvoda.cz> Message-ID: On Thu, 9 Nov 2006, Karel Zak wrote: > On Mon, Nov 06, 2006 at 03:11:51PM +0100, Laurent Flesch wrote: > > Hi, > > > > I'm a new FC user. > > I'm trying to install FC6 with Xen for full Virtualization (on an AMD 3800+ > > X2). > > > > When I try to create a new VM with virt-manager using an image file, the > > creation interrupts with a Domain creating error. Xen log gives an error > > like "fime image does not exist". Even if I create this file before with dd, > > I obtain the same error. > > > > Please do I have an idea about what happens ? > > selinux? Try: setenforce 0 If this fixes the issue, please submit a bugzilla so it can be fixed properly. Disabling SELinux is not a bugfix, It's papering over the problem, reducing the security of the system, and helping to ensure that the problem doesn't get fixed. - James -- James Morris From phung at cs.columbia.edu Thu Nov 9 21:39:27 2006 From: phung at cs.columbia.edu (Dan B. Phung) Date: Thu, 09 Nov 2006 16:39:27 -0500 Subject: [Fedora-xen] virt-manager make check errors and connection errors Message-ID: <4553A00F.4040801@ncl.cs.columbia.edu> I'm using virt-manager-0.2.5 on a Debian system. I installed these packages per the prerequisites using aptitude: aptitude install python-gtk2 python-gtk2-dev python-gnome2 python-gnome2-dev python-dbus python-vte python-glade2 python-urlgrabber I installed libvirt from the cvs sources and I aliened and installed python-virtinst-0.96.0-1.noarch.rpm. 'make check' for virt-manager complained about some rhpl exceptions, so I commented out these lines. src/virtManager/create.py - from rhpl.exception import installExceptionHandler - from rhpl.translate import _, N_, textdomain, utf8 the 'make check' didn't seem to complain afterwards...but this could be where I screwed things up :) So I do a 'make install' and try running it and try to connect to the local Xen host and get: Unable to open a connection to the Xen hypervisor/daemon. Verify that: - A Xen host kernel was booted - The Xen service has been started I have verified that I'm booted in Xen and that xend has been started. here's my log: blade06:~:) cat .virt-manager/virt-manager.log Thu, 09 Nov 2006 16:42:16 WARNING No support for gnome-keyring Thu, 09 Nov 2006 16:42:16 WARNING Could not connection to session bus, disabling DBus service exceptions.RuntimeError DBus session/starter bus address not defined Thu, 09 Nov 2006 16:42:34 ERROR Unable to open connection to hypervisor URI 'xen': libvirt.libvirtError virConnectOpenReadOnly() failed no support for hypervisor can someone point out the err in my ways? -dan From berrange at redhat.com Thu Nov 9 22:08:48 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 22:08:48 +0000 Subject: [Fedora-xen] virt-manager make check errors and connection errors In-Reply-To: <4553A00F.4040801@ncl.cs.columbia.edu> References: <4553A00F.4040801@ncl.cs.columbia.edu> Message-ID: <20061109220848.GH5223@redhat.com> On Thu, Nov 09, 2006 at 04:39:27PM -0500, Dan B. Phung wrote: > I'm using virt-manager-0.2.5 on a Debian system. I installed these > packages per the prerequisites using aptitude: > aptitude install python-gtk2 python-gtk2-dev python-gnome2 > python-gnome2-dev python-dbus python-vte python-glade2 python-urlgrabber > > I installed libvirt from the cvs sources and I aliened and installed > python-virtinst-0.96.0-1.noarch.rpm. > > 'make check' for virt-manager complained about some rhpl exceptions, so > I commented out these lines. > > src/virtManager/create.py > - from rhpl.exception import installExceptionHandler > - from rhpl.translate import _, N_, textdomain, utf8 I've no idea how this got into the python code - those imports are some Red Hat specific python helper modules, which I was explicitly trying to avoid in virt-manager. I'm about to put up a 0.2.6 release which will remove this crack rock :-) Removing them was a safe thing to do. > So I do a 'make install' and try running it and try to connect to the > local Xen host and get: > Unable to open a connection to the Xen hypervisor/daemon. > > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > > I have verified that I'm booted in Xen and that xend has been started. > > here's my log: > blade06:~:) cat .virt-manager/virt-manager.log > Thu, 09 Nov 2006 16:42:16 WARNING No support for gnome-keyring > Thu, 09 Nov 2006 16:42:16 WARNING Could not connection to session bus, > disabling DBus service exceptions.RuntimeError DBus session/starter bus > address not defined > Thu, 09 Nov 2006 16:42:34 ERROR Unable to open connection to > hypervisor URI 'xen': libvirt.libvirtError virConnectOpenReadOnly() > failed no support for hypervisor Check the /etc/xen/xend-config.sxp file. Is it configured to have either of these settings set to yes: (xend-http-server yes) (xend-unix-server yes) I strongly recommend setting unix to yes & http to no nbecause http server has *zero* authentication :-( Once you've done this, also make sure that $prefix/libexec/libvirt_proxy is made setuid root - this allows virt-manager to run as an unprivileged user in read-only mode. You still need to run virt-manager as root if you want to do read-write operations. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From calimeral at gmail.com Thu Nov 9 23:13:28 2006 From: calimeral at gmail.com (Cyril Olivier) Date: Thu, 9 Nov 2006 17:13:28 -0600 Subject: [Fedora-xen] Re: Cannot input in guest console In-Reply-To: <99ef937b0611081059g41c865eaib6ff35cee0fa292d@mail.gmail.com> References: <99ef937b0611081059g41c865eaib6ff35cee0fa292d@mail.gmail.com> Message-ID: <99ef937b0611091513v76be0169o5d8e75b7d9b835bf@mail.gmail.com> Hi, i am a newbie on xen, i am sorry if this has already been answerd, i haven't find similar problem in the archive. in console i see the output of the guest but i cannot input anything. i send the configuration file and the inittab of the guest. inittab id:3:initdefault: si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 ca::ctrlaltdel:/sbin/shutdown -t3 -r now pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" 1:2345:respawn:/sbin/mingetty tty1 x:5:once:/etc/X11/prefdm -nodaemon Configuration file kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xen-guest1.img" memory = 128 name = "fc6" vif = [ '' ] dhcp = "dhcp" disk = ['file:/vm/fc6.img,sda1,w', 'file:/vm/swap,sda2,w'] root = "/dev/sda1 ro" Maybe it's a basic problem... nevetheless i would really apreciate help. Cyril -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha.ranganathan at intel.com Thu Nov 9 23:16:02 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Thu, 9 Nov 2006 15:16:02 -0800 Subject: [Fedora-xen] FC6 and xen-3.0.3 -- Is xen missing rfb directory ? Message-ID: I am trying to build Xen in FC6. when I did "make world pae=y", It gives me an error in xenfb.c in tools/xenfb/ directoty that file rfb/rfb.h is not available in tools/xenfb/ directory. This is true. I commented it out in xenfb.c. I am trying to rebuild the Xen sources Is this known issue ? Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Nov 9 23:29:50 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 9 Nov 2006 23:29:50 +0000 Subject: [Fedora-xen] FC6 and xen-3.0.3 -- Is xen missing rfb directory ? In-Reply-To: References: Message-ID: <20061109232950.GJ5223@redhat.com> On Thu, Nov 09, 2006 at 03:16:02PM -0800, Ranganathan, Shobha wrote: > I am trying to build Xen in FC6. when I did "make world pae=y", We don't typically use 'make world' in Fedora Xen builds because that builds the ancient 2.6.16 kernels from upstream Xen. Instead the Xen kernels for Fedora are based on the current 2.6.18 tree and the source for these is distributed in the kernel src.rpm. The 'xen' RP is only used for building userspace - we better to just to 'make tools' instead of 'make world'. > It gives me an error in xenfb.c in tools/xenfb/ directoty that file > rfb/rfb.h is not available in tools/xenfb/ directory. This is true. > > > > I commented it out in xenfb.c. I am trying to rebuild the Xen sources > > Is this known issue ? You need to build libvncserver first, eg in the RPM spec we do: # pushd LibVNCServer-0.8.2 # ./configure # make -C libvncserver # vncdir=`pwd` # popd # sed -i -e "s;libvncserver-config;${vncdir}/libvncserver-config;" tools/xenfb/Makefile Before going in to building any of the Xen bits Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Thu Nov 9 23:52:08 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Thu, 9 Nov 2006 15:52:08 -0800 Subject: [Fedora-xen] How do you build xen in FC6 ? Message-ID: I am being told that "make world pae=y" is not recent Fedora way to build Xen. I was always following the README that accompanies the Xen sources. I very appreciate if someone can educate me on how to build Xen from xen-3.0.3-0.1.rc3.src.rpm in Fc6 ? Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Nov 10 00:00:10 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 00:00:10 +0000 Subject: [Fedora-xen] How do you build xen in FC6 ? In-Reply-To: References: Message-ID: <20061110000010.GK5223@redhat.com> On Thu, Nov 09, 2006 at 03:52:08PM -0800, Ranganathan, Shobha wrote: > I am being told that "make world pae=y" is not recent Fedora way to > build Xen. > > > > I was always following the README that accompanies the Xen sources. > > > > I very appreciate if someone can educate me on how to build Xen from > xen-3.0.3-0.1.rc3.src.rpm in Fc6 ? Look at the '%build' section in the RPM spec file - that contains the complete list of commands run when building Xen in Fedora. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Nov 10 00:19:02 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 00:19:02 +0000 Subject: [Fedora-xen] virt-manager 0.2.6 release Message-ID: <20061110001902.GM5223@redhat.com> I'm pleased to announce the 0.2.6 release of 'Virtual Machine Manager' aka 'virt-manager' is available for download: http://virt-manager.et.redhat.com/download.html The release focus has been on major bug fixing. This is also the first release in which (partial) translations are available for the UI in approximately 20 languages - thanks to the Fedora i18n team for excellant progress on this. It is now possible to control the virt-manager UI with command line arguments as well as the DBus API & DBus activation is no longer used by default which fixes interaction with GNOME keyring & AT-SPI accesibility. Numerous UI issues were fixed / clarified, particularly in the graphical console and new VM creation wizard. There are updated screenshots of the UI on the project website: http://virt-manager.et.redhat.com/screenshots.html As ever, report bugs against the 'virt-manager' component in the Red Hat Bugzilla server. Work is also underway to address the frequently requested feature of management for inactive domains. Since this is not supported by XenD on any current release we're aiming to add support for loading config files straight out of /etc/xen into libvirt & virt-manager. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From florian.heigl at gmail.com Fri Nov 10 00:41:02 2006 From: florian.heigl at gmail.com (Florian Heigl) Date: Fri, 10 Nov 2006 01:41:02 +0100 Subject: [Fedora-xen] fc6: xennet module issue with kickstart Message-ID: <77abe410611091641k573c52caja294629c7ba8ccc@mail.gmail.com> Hello, I found one more little issue to stumble over :) I tried (among others) the following kernel: kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly rsynced) images/xen/ directory. When the domU is created it comes up properly, and automatically preloads the xenvbd module, but not xennet. I extracted the initrd and found the xennet module there, but it seems not possible to load it from the network driver dialog (it's not listed). I'm confused as I also tried an fc5 kernel + initrd, and also a rhel5 beta kernel+initrd. I think the issue is somewhere with the initrd, but don't really found a hook to change anything, maybe short of rebuilding the initrd using --preload xennet If You're successfully installing FC6 domU's from within xen, please speak up! the following are the relevant settings from the domU configfile kernel = "/mnt/xendistro_temp//vmlinuz" ramdisk = "/mnt/xendistro_temp/initrd.img" extra = "ks=http://192.168.199.4/ks_fc6.cfg" ip = "192.168.199.5" netmask = "255.255.255.0" gateway = "192.168.199.1" # single line :) disk = [ 'phy:/dev/evms/ll-kickme_root,hda,w', 'phy:/dev/evms/ll-kickme_rootmir,hdb,w', 'phy:/dev/evms/ll-kickme_swap,hdc,w', 'phy:/dev/evms/ll-kickme_home,hdd,w' ] vif = [ 'type=ioemu, bridge=xenbr1' ] Florian -- 'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen' -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Nov 10 00:48:26 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 00:48:26 +0000 Subject: [Fedora-xen] fc6: xennet module issue with kickstart In-Reply-To: <77abe410611091641k573c52caja294629c7ba8ccc@mail.gmail.com> References: <77abe410611091641k573c52caja294629c7ba8ccc@mail.gmail.com> Message-ID: <20061110004826.GN5223@redhat.com> On Fri, Nov 10, 2006 at 01:41:02AM +0100, Florian Heigl wrote: > Hello, > > I found one more little issue to stumble over :) > > I tried (among others) the following kernel: > kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly > rsynced) images/xen/ directory. > > When the domU is created it comes up properly, and automatically preloads > the xenvbd module, > but not xennet. I extracted the initrd and found the xennet module there, > but it seems not possible > to load it from the network driver dialog (it's not listed). I'm confused as > I also tried an fc5 kernel + initrd, and also > a rhel5 beta kernel+initrd. I think the issue is somewhere with the initrd, > but don't really found a hook to > change anything, maybe short of rebuilding the initrd using --preload xennet The error message about not finding a network driver is actually a little misleading in the Xen case. What it actually means is that the Dom0 host failed to create the backend interface for the virtual NIC - so there was nothing for the xennet driver to talk to. > If You're successfully installing FC6 domU's from within xen, please speak > up! > > the following are the relevant settings from the domU configfile > kernel = "/mnt/xendistro_temp//vmlinuz" > ramdisk = "/mnt/xendistro_temp/initrd.img" > extra = "ks=http://192.168.199.4/ks_fc6.cfg" > ip = "192.168.199.5" > netmask = "255.255.255.0" > gateway = "192.168.199.1" > # single line :) > disk = [ 'phy:/dev/evms/ll-kickme_root,hda,w', > 'phy:/dev/evms/ll-kickme_rootmir,hdb,w', > 'phy:/dev/evms/ll-kickme_swap,hdc,w', > 'phy:/dev/evms/ll-kickme_home,hdd,w' ] > vif = [ 'type=ioemu, bridge=xenbr1' ] This is your problem - 'type=ioemu' is only relevant for fully-virt guests, but you're trying to do parav-irt install - just remove the type param & it will probably work. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From m3freak at rogers.com Fri Nov 10 00:47:09 2006 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Thu, 09 Nov 2006 19:47:09 -0500 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <20061109160317.GC5223@redhat.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> Message-ID: <1163119629.8745.4.camel@krs> On Thu, 2006-11-09 at 16:03 +0000, Daniel P. Berrange wrote: > The solution is fairly simple though - the latest FC5 errata also provides a > 'kernel-xen' RPM which is PAE enabled. So before upgrading your host, just > make sure you have done 'yum install kernel-xen' in each of your guests. > This will let your FC5 guests contonue working on an FC6 host - you can then > upgrade your guests to FC6 at will. I don't understand this. Why does kernel-xen have to be installed in the guest? Doesn't the guest just use the xen kernel running in dom0? I'm obviously missing something here. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 19:42:26 up 11 days, 14:10, 3 users, load average: 0.54, 0.64, 0.56 From berrange at redhat.com Fri Nov 10 01:04:12 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 01:04:12 +0000 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <1163119629.8745.4.camel@krs> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> <1163119629.8745.4.camel@krs> Message-ID: <20061110010412.GO5223@redhat.com> On Thu, Nov 09, 2006 at 07:47:09PM -0500, Kanwar Ranbir Sandhu wrote: > On Thu, 2006-11-09 at 16:03 +0000, Daniel P. Berrange wrote: > > The solution is fairly simple though - the latest FC5 errata also provides a > > 'kernel-xen' RPM which is PAE enabled. So before upgrading your host, just > > make sure you have done 'yum install kernel-xen' in each of your guests. > > This will let your FC5 guests contonue working on an FC6 host - you can then > > upgrade your guests to FC6 at will. > > I don't understand this. Why does kernel-xen have to be installed in > the guest? Doesn't the guest just use the xen kernel running in dom0? > I'm obviously missing something here. It doesn't *have* to be installed in the guest - that's just way we deal with it in Fedora. The overriding strategy for Xen in Fedora is that we want to make installing, upgrading, managing the operating system in a guest a close to what you do on bare metal as possible[1] - so all your existing Linux knowledge still applies - this makes it easier for people who don't know Xen to get started. Basically the way it works is thus: - In the guest OS a regular rpm install of the kernel-xen is done. So a regular grub config is written to the boot sector of the virtual disk pointing to the kernel inside the image. - When booting the guest from Dom0, we run 'pygrub' which pulls the grub config from the DomU filesystem & uses that to extract the guest kernel to a temporay file /var/lib/xen - The DomU is then booted off the temp file in /var/lib/xen So, yes for the actual boot process the kernel is located in Dom0. The other nice thing about this is that the DomU it self contained - you can move the filesystem image anywhere & no have to worry about carting around a separate kernel image file to go with it. Then again, some people may like to have a single kernel image in the Dom0 whcih they use to boot all their guest images. If you want to manage your guests that way, simply add the 'kernel=/foo/bar/wizz' parameter to the guest config, and remove the pygrub config option. Dan. [1] Other examples.... - using regular Anaconda for installing the DomU rather than fragile install into a chroot shell scripts other distro use. - adding the paravirt framebuffer to Xen so you have a fully graphical console -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From florian.heigl at gmail.com Fri Nov 10 01:08:01 2006 From: florian.heigl at gmail.com (Florian Heigl) Date: Fri, 10 Nov 2006 02:08:01 +0100 Subject: [Fedora-xen] fc6: xennet module issue with kickstart In-Reply-To: <20061110004826.GN5223@redhat.com> References: <77abe410611091641k573c52caja294629c7ba8ccc@mail.gmail.com> <20061110004826.GN5223@redhat.com> Message-ID: <77abe410611091708o7f84a023n4deabf2a08e2da27@mail.gmail.com> Hi Daniel, 2006/11/10, Daniel P. Berrange : > > On Fri, Nov 10, 2006 at 01:41:02AM +0100, Florian Heigl wrote: > > Hello, > > > > I found one more little issue to stumble over :) > > > > I tried (among others) the following kernel: > > kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly > > rsynced) images/xen/ directory. > > > > When the domU is created it comes up properly, and automatically > preloads > > the xenvbd module, > > but not xennet. I extracted the initrd and found the xennet module > there, [...] snipped myself out > 'phy:/dev/evms/ll-kickme_home,hdd,w' ] > > vif = [ 'type=ioemu, bridge=xenbr1' ] > > This is your problem - 'type=ioemu' is only relevant for fully-virt > guests, but you're trying to do parav-irt install - just remove the > type param & it will probably work. Thank You _again_, You pointed me at the right thing. I am currently trying to figure out why I added it in the first place, my template doesn't have it. I think it was about the type=ioemu vif being cleared from the bridge more reliable than the standard vif. i.e. just now root at xen-host3 /etc/xen/configs/linlab# xm create -c ll-kickme Using config file "ll-kickme". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. this happened after a successful boot, so my spirit is up anyway) I feel a bit stupid, having wasted a few hours on this. on the other had it still fed google. :) -- 'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen' -------------- next part -------------- An HTML attachment was scrubbed... URL: From phung at cs.columbia.edu Fri Nov 10 01:43:35 2006 From: phung at cs.columbia.edu (Dan B. Phung) Date: Thu, 09 Nov 2006 20:43:35 -0500 Subject: [Fedora-xen] virt-manager make check errors and connection errors In-Reply-To: <20061109220848.GH5223@redhat.com> References: <4553A00F.4040801@ncl.cs.columbia.edu> <20061109220848.GH5223@redhat.com> Message-ID: <4553D947.70102@ncl.cs.columbia.edu> awesome, it works! kinda....as root it can list the vms, but as a regular user it repeats this message: libvir: error : operation failed: xenProxyListDomains which files does virt-manager require suid perms? thanks, dan Daniel P. Berrange wrote: > On Thu, Nov 09, 2006 at 04:39:27PM -0500, Dan B. Phung wrote: > >> I'm using virt-manager-0.2.5 on a Debian system. I installed these >> packages per the prerequisites using aptitude: >> aptitude install python-gtk2 python-gtk2-dev python-gnome2 >> python-gnome2-dev python-dbus python-vte python-glade2 python-urlgrabber >> >> I installed libvirt from the cvs sources and I aliened and installed >> python-virtinst-0.96.0-1.noarch.rpm. >> >> 'make check' for virt-manager complained about some rhpl exceptions, so >> I commented out these lines. >> >> src/virtManager/create.py >> - from rhpl.exception import installExceptionHandler >> - from rhpl.translate import _, N_, textdomain, utf8 >> > > I've no idea how this got into the python code - those imports are some > Red Hat specific python helper modules, which I was explicitly trying to > avoid in virt-manager. I'm about to put up a 0.2.6 release which will > remove this crack rock :-) Removing them was a safe thing to do. > > >> So I do a 'make install' and try running it and try to connect to the >> local Xen host and get: >> Unable to open a connection to the Xen hypervisor/daemon. >> >> Verify that: >> - A Xen host kernel was booted >> - The Xen service has been started >> >> I have verified that I'm booted in Xen and that xend has been started. >> >> here's my log: >> blade06:~:) cat .virt-manager/virt-manager.log >> Thu, 09 Nov 2006 16:42:16 WARNING No support for gnome-keyring >> Thu, 09 Nov 2006 16:42:16 WARNING Could not connection to session bus, >> disabling DBus service exceptions.RuntimeError DBus session/starter bus >> address not defined >> Thu, 09 Nov 2006 16:42:34 ERROR Unable to open connection to >> hypervisor URI 'xen': libvirt.libvirtError virConnectOpenReadOnly() >> failed no support for hypervisor >> > > Check the /etc/xen/xend-config.sxp file. Is it configured to have either > of these settings set to yes: > > (xend-http-server yes) > (xend-unix-server yes) > > I strongly recommend setting unix to yes & http to no nbecause http > server has *zero* authentication :-( > > Once you've done this, also make sure that $prefix/libexec/libvirt_proxy > is made setuid root - this allows virt-manager to run as an unprivileged > user in read-only mode. You still need to run virt-manager as root if > you want to do read-write operations. > > Regards, > Dan. > From berrange at redhat.com Fri Nov 10 01:52:13 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 01:52:13 +0000 Subject: [Fedora-xen] virt-manager make check errors and connection errors In-Reply-To: <4553D947.70102@ncl.cs.columbia.edu> References: <4553A00F.4040801@ncl.cs.columbia.edu> <20061109220848.GH5223@redhat.com> <4553D947.70102@ncl.cs.columbia.edu> Message-ID: <20061110015213.GP5223@redhat.com> On Thu, Nov 09, 2006 at 08:43:35PM -0500, Dan B. Phung wrote: > awesome, it works! kinda....as root it can list the vms, but as a > regular user it repeats this message: > > libvir: error : operation failed: xenProxyListDomains > > which files does virt-manager require suid perms? It only needs setuid root on the '/usr/libexec/libvirt_proxy' command. This command is laucnhed automatically by libvirt when needed, but if you want to debug you can also launch it manually ahead of time. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at xelerance.com Fri Nov 10 04:08:56 2006 From: paul at xelerance.com (Paul Wouters) Date: Fri, 10 Nov 2006 05:08:56 +0100 (CET) Subject: [Fedora-xen] Booting rootfs instead of disk image, question on xen modules Message-ID: hi, I am trying to boot using a rootfs image, instead of a disk image. Just because it is much easier to mount filesystems, then to go calculate offsets for mounting. Also, because I have various xen2 filesystems I want to use without building virtual disk images. On FC5, using kernel= with a *xenU image works fine. On FC6, using the *xen kernel image, this does not work. (using known working fc5 xen kernels on fc6 also didn't work, but I expected that, due to differences in the xen hypervisor) Instead of using bootloader="/usr/bin/pygrub" I manaully set the kernel, ramdisk and extra flags, eg: disk = [ 'file:/xen/qtopia.xelerance.net/qtopia.ext3.img,xvda1,w' ] kernel="/boot/vmlinuz-2.6.18-1.2798.fc6xen" root="/dev/xvda1 ro" extra="ro selinux=0 3 root=/dev/xvda1 initrd=/boot/initrd-2.6.18-1.2798.fc6xen.img" ramdisk="/boot/initrd-2.6.18-1.2798.fc6xen.img" (also tried using hda1 instead of xvda1) But when I boot, I see the following: [...] XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 356k Red Hat nash version 5.1.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading ahci.ko module Loading ata_piix.ko module Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! It seems the xenblck and xennet drivers are not being loaded? And indeed, dissecting the initrd file, I don't see them. However, grepping the config shows they are now inline: # grep XENB /boot/config-2.6.18-1.2798.fc6xen CONFIG_XEN_XENBUS_DEV=y So I am not sure why xen is not picking up the settings - though pygrub can find them. The same machine boots fine with pygrub, so it must be something that I'm doing wrong myself. but even running xm create -n configname did not give me a clue on what it is that I'm doing wrong. I've attached the output of xm create -n below. Using config file "/etc/xen/qtopia.xelerance.net". (vm (name qtopia.xelerance.net) (memory 256) (on_reboot restart) (on_crash restart) (vcpus 1) (uuid 10000007-f66d-374b-29fc-364cd7761111) (image (linux (kernel /boot/vmlinuz-2.6.18-1.2798.fc6xen) (ramdisk /boot/initrd-2.6.18-1.2798.fc6xen.img) (root '/dev/xvda1 ro') (args 'ro selinux=0 3 root=/dev/xvda1 initrd=/boot/initrd-2.6.18-1.2798.fc6xen.img' ) (vncunused 1) (xauthority /root/.Xauthority) ) ) (device (vbd (uname file:/xen/qtopia.xelerance.net/qtopia.ext3.img) (dev xvda1) (mode w) ) ) (device (vif (bridge xenbr0) (mac 00:16:3e:7a:0e:57))) ) Paul From paul at xelerance.com Fri Nov 10 05:56:11 2006 From: paul at xelerance.com (Paul Wouters) Date: Fri, 10 Nov 2006 06:56:11 +0100 (CET) Subject: [Fedora-xen] Problem found with workaround, was Re: Booting rootfs instead of disk image, question on xen modules In-Reply-To: References: Message-ID: On Fri, 10 Nov 2006, Paul Wouters wrote: [ ExecSum since it's a long post: xenU created from xenguest-isntall.py has different initrd from dom0 though with the same version/build/rpmsig, and rpm has a nasty bug] Following up on myself, since i now know what happened: > Loading ohci-hcd.ko module > Loading ehci-hcd.ko module > Loading jbd.ko module > Loading ext3.ko module > Loading scsi_mod.ko module > SCSI subsystem initialized Note the missing "Loading xenblk" which was visible in the boot of the guest that was started with pygrub using a disk image created on the dom0 with xenguest-install.py. I decided to find out where it got loaded from. It couldn't be from the filesystem, so it had to be initrd. But both were using the same initrd? Well sort of. pygrub extracted one from the diskimage, and I grabbed it from /boot on the dom0. What I found were two different initrd files with the SAME build number. I copied it from xenU to dom0: [root at echelon boot]# ls -l initrd-2.6.18-1.2798.fc6*xen* -rw------- 1 root root 2177639 Nov 10 00:00 initrd-2.6.18-1.2798.fc6xen.img-from-xenguest-install -rw------- 1 root root 1522165 Oct 28 00:34 initrd-2.6.18-1.2798.fc6xen.img-from-dom0 The original date of the xenguest=install version before i copied it was: "Oct 28 16:37" [root at echelon boot]# md5sum initrd-2.6.18-1.2798.fc6*xen* 8b06aa9e364bd1ac5379e652095a4d3e initrd-2.6.18-1.2798.fc6xen.img-from-xenguest-install 6b591a095b5d4e55641d30c25702e272 initrd-2.6.18-1.2798.fc6xen.img-from-dom0 They both claim to come from the package kernel-xen-2.6.18-1.2798.fc6 Both the diskimage based xen's rpm -V, and the rpm -V on the dom0 claimed the package was not altered? Checking the rpms, I find both as: # rpm -qi kernel-xen-2.6.18-1.2798.fc6 Name : kernel-xen Relocations: (not relocatable) Version : 2.6.18 Vendor: Red Hat, Inc. Release : 1.2798.fc6 Build Date: Mon 16 Oct 2006 03:57:26 PM EDT Install Date: Sat 28 Oct 2006 04:37:14 PM EDT Build Host: hs20-bc2-4.build.redhat.com Group : System Environment/Kernel Source RPM: kernel-2.6.18-1.2798.fc6.src.rpm Size : 46862330 License: GPLv2 So how can they both verify to the same version, with rpm -V not complaining, while containing different initrd images, yet having the same build date? Just to show what I did, so that I won't go insane: [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img kernel-xen-2.6.18-1.2798.fc6 [root at echelon boot]# rpm -qa|grep kernel-xen kernel-xen-devel-2.6.18-1.2798.fc6 kernel-xen-devel-2.6.18-1.2741.fc6 kernel-xen-2.6.18-1.2741.fc6 kernel-xen-2.6.18-1.2798.fc6 [root at echelon boot]# ls -l /boot/initrd-2.6.18-1.2798.fc6* -rw------- 1 root root 1521809 Oct 28 00:36 /boot/initrd-2.6.18-1.2798.fc6.img -rw------- 1 root root 2177639 Nov 10 00:30 /boot/initrd-2.6.18-1.2798.fc6xen.img -rw------- 1 root root 1522165 Oct 28 00:34 /boot/initrd-2.6.18-1.2798.fc6xen.img-broken -rw------- 1 root root 2177639 Nov 10 00:28 /boot/initrd-2.6.18-1.2798.fc6xen.img-from-xenguest [root at echelon boot]# rpm -V kernel-xen-2.6.18-1.2798.fc6 [root at echelon boot]# cp /boot/initrd-2.6.18-1.2798.fc6xen.img-broken /boot/initrd-2.6.18-1.2798.fc6xen.img [root at echelon boot]# ls -l /boot/initrd-2.6.18-1.2798.fc6* -rw------- 1 root root 1521809 Oct 28 00:36 /boot/initrd-2.6.18-1.2798.fc6.img -rw------- 1 root root 1522165 Nov 10 00:35 /boot/initrd-2.6.18-1.2798.fc6xen.img -rw------- 1 root root 1522165 Oct 28 00:34 /boot/initrd-2.6.18-1.2798.fc6xen.img-broken -rw------- 1 root root 2177639 Nov 10 00:28 /boot/initrd-2.6.18-1.2798.fc6xen.img-from-xenguest [root at echelon boot]# rpm -V kernel-xen-2.6.18-1.2798.fc6 [root at echelon boot]# So either rpm is broken in -qf mode, or it is broken in -V mode... [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img kernel-xen-2.6.18-1.2798.fc6 [root at echelon boot]# rpm -ql kernel-xen-2.6.18-1.2798.fc6 |grep initrd [root at echelon boot]# And as a test: [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img-broken file /boot/initrd-2.6.18-1.2798.fc6xen.img-broken is not owned by any package I guess it is rpm -qf that is broken? Or some advanced "should never be visible" magic is in use. Replacing the dom0 version with the xenguest installed version fixed my problem. The rootfs based xen now boots fine. And this leads me to a final question. Why are the xen modules loaded through initrd to begin with? kernel size can't be an issue, since all hardware drivers are gone from the xenU - only the xen virtual drivers are needed. Can't we just build that stuff inline, and save ourselves a lot of trouble booting. It might not be the elegant CS theoretical perfect solution, but it works in many more practical situations, like this one with a voodoo initrd-2.6.18.-1.2798.fc6xen.img appearing. Paul From clalance at redhat.com Fri Nov 10 13:50:16 2006 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 10 Nov 2006 08:50:16 -0500 Subject: [Fedora-xen] Problem found with workaround, was Re: Booting rootfs instead of disk image, question on xen modules In-Reply-To: References: Message-ID: <45548398.8020901@redhat.com> Paul Wouters wrote: > On Fri, 10 Nov 2006, Paul Wouters wrote: > > [ ExecSum since it's a long post: xenU created from xenguest-isntall.py > has different initrd from dom0 though with the same version/build/rpmsig, > and rpm has a nasty bug] > > Following up on myself, since i now know what happened: > >> Loading ohci-hcd.ko module >> Loading ehci-hcd.ko module >> Loading jbd.ko module >> Loading ext3.ko module >> Loading scsi_mod.ko module >> SCSI subsystem initialized > > Note the missing "Loading xenblk" which was visible in the boot of the guest > that was started with pygrub using a disk image created on the dom0 with > xenguest-install.py. > > I decided to find out where it got loaded from. It couldn't be from > the filesystem, so it had to be initrd. But both were using the same > initrd? Well sort of. pygrub extracted one from the diskimage, and > I grabbed it from /boot on the dom0. What I found were two different > initrd files with the SAME build number. I copied it from xenU to dom0: > > [root at echelon boot]# ls -l initrd-2.6.18-1.2798.fc6*xen* > -rw------- 1 root root 2177639 Nov 10 00:00 initrd-2.6.18-1.2798.fc6xen.img-from-xenguest-install > -rw------- 1 root root 1522165 Oct 28 00:34 initrd-2.6.18-1.2798.fc6xen.img-from-dom0 > > The original date of the xenguest=install version before i copied it was: "Oct 28 16:37" > > [root at echelon boot]# md5sum initrd-2.6.18-1.2798.fc6*xen* > 8b06aa9e364bd1ac5379e652095a4d3e initrd-2.6.18-1.2798.fc6xen.img-from-xenguest-install > 6b591a095b5d4e55641d30c25702e272 initrd-2.6.18-1.2798.fc6xen.img-from-dom0 > > They both claim to come from the package kernel-xen-2.6.18-1.2798.fc6 > > Both the diskimage based xen's rpm -V, and the rpm -V on the dom0 > claimed the package was not altered? > > Checking the rpms, I find both as: > > # rpm -qi kernel-xen-2.6.18-1.2798.fc6 > Name : kernel-xen Relocations: (not relocatable) > Version : 2.6.18 Vendor: Red Hat, Inc. > Release : 1.2798.fc6 Build Date: Mon 16 Oct 2006 03:57:26 PM EDT > Install Date: Sat 28 Oct 2006 04:37:14 PM EDT Build Host: hs20-bc2-4.build.redhat.com > Group : System Environment/Kernel Source RPM: kernel-2.6.18-1.2798.fc6.src.rpm > Size : 46862330 License: GPLv2 > > So how can they both verify to the same version, with rpm -V not complaining, > while containing different initrd images, yet having the same build date? > > Just to show what I did, so that I won't go insane: > > [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img > kernel-xen-2.6.18-1.2798.fc6 > [root at echelon boot]# rpm -qa|grep kernel-xen > kernel-xen-devel-2.6.18-1.2798.fc6 > kernel-xen-devel-2.6.18-1.2741.fc6 > kernel-xen-2.6.18-1.2741.fc6 > kernel-xen-2.6.18-1.2798.fc6 > [root at echelon boot]# ls -l /boot/initrd-2.6.18-1.2798.fc6* > -rw------- 1 root root 1521809 Oct 28 00:36 /boot/initrd-2.6.18-1.2798.fc6.img > -rw------- 1 root root 2177639 Nov 10 00:30 /boot/initrd-2.6.18-1.2798.fc6xen.img > -rw------- 1 root root 1522165 Oct 28 00:34 /boot/initrd-2.6.18-1.2798.fc6xen.img-broken > -rw------- 1 root root 2177639 Nov 10 00:28 /boot/initrd-2.6.18-1.2798.fc6xen.img-from-xenguest > [root at echelon boot]# rpm -V kernel-xen-2.6.18-1.2798.fc6 > [root at echelon boot]# cp /boot/initrd-2.6.18-1.2798.fc6xen.img-broken /boot/initrd-2.6.18-1.2798.fc6xen.img > [root at echelon boot]# ls -l /boot/initrd-2.6.18-1.2798.fc6* > -rw------- 1 root root 1521809 Oct 28 00:36 /boot/initrd-2.6.18-1.2798.fc6.img > -rw------- 1 root root 1522165 Nov 10 00:35 /boot/initrd-2.6.18-1.2798.fc6xen.img > -rw------- 1 root root 1522165 Oct 28 00:34 /boot/initrd-2.6.18-1.2798.fc6xen.img-broken > -rw------- 1 root root 2177639 Nov 10 00:28 /boot/initrd-2.6.18-1.2798.fc6xen.img-from-xenguest > [root at echelon boot]# rpm -V kernel-xen-2.6.18-1.2798.fc6 > [root at echelon boot]# > > So either rpm is broken in -qf mode, or it is broken in -V mode... > > [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img > kernel-xen-2.6.18-1.2798.fc6 > [root at echelon boot]# rpm -ql kernel-xen-2.6.18-1.2798.fc6 |grep initrd > [root at echelon boot]# > > And as a test: > [root at echelon boot]# rpm -qf /boot/initrd-2.6.18-1.2798.fc6xen.img-broken > file /boot/initrd-2.6.18-1.2798.fc6xen.img-broken is not owned by any package > > I guess it is rpm -qf that is broken? Or some advanced "should never be visible" > magic is in use. > > Replacing the dom0 version with the xenguest installed version fixed my > problem. The rootfs based xen now boots fine. > > And this leads me to a final question. Why are the xen modules loaded > through initrd to begin with? kernel size can't be an issue, since all > hardware drivers are gone from the xenU - only the xen virtual drivers > are needed. Can't we just build that stuff inline, and save ourselves > a lot of trouble booting. It might not be the elegant CS theoretical > perfect solution, but it works in many more practical situations, like > this one with a voodoo initrd-2.6.18.-1.2798.fc6xen.img appearing. > > Paul > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Paul, The reason that you are seeing two different initrd's is that the initrd is actually packaged as a file in the RPM. Since everyone's hardware is different, including every single driver in an initrd would be a little silly. After the kernel is finished installing, it runs "mkinitrd", looking at your hardware (specifically, /etc/modprobe.conf) and generating an initrd for your particular hardware. In this case, because mkinitrd was run on the dom0, it crucially included the modules needed to run dom0, but not the ones necessary for domU (like, as you said, xenblk and xennet). As far as why they are modules to begin with; I'm not 100% sure, but the policy tends to be to make everything as modular as possible. This cuts down on the size of the kernel, which is, in fact, a concern. Anyway, I hope that helps, and I'm glad you got it working. Chris Lalancette From rodger at thompsonprint.com Fri Nov 10 13:54:27 2006 From: rodger at thompsonprint.com (Rodger Haynes) Date: Fri, 10 Nov 2006 08:54:27 -0500 Subject: Me too - Re: [Fedora-xen] dissapearing guests In-Reply-To: <45533CAF.1080800@paulororke.net> References: <45533CAF.1080800@paulororke.net> Message-ID: <45548493.2020005@thompsonprint.com> I am experiencing the same problem on a new Dell Optiplex GX520. I'm new at this as well. Paul O'rorke wrote: > maybe I've missed something but if I reboot or shutdown a guest domain > I can't start it again. xm --list doesn't show the domain. From the > Virtual Machine Manager (FC6) if I go : File --> Restore saved > machine (Restore a saved machine from a filesystem image) and pint to > /vm/webserver I get a dialogue box stating: > > *Error restoring domain '/vm/webserver'. Is the domain already > running?* > > > Similary if I try to restore from the disk file with xm restore I get > the following: > > *# xm restore /vm/webserver* > *Error: Restore failed* > *Usage: xm restore * > > *Restore a domain from a saved state.* > > > I'm guessing that the disk file is not the correct file to restore > from - ?? but I can't find anywhere documentation > on how to open these machines. > > This is my first bash at virtualization in Xen so I appologize if I've > missed something in the docs. What can I do to open this guest? > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Rodger Haynes Thompson Printing & Lithographing Paris, ON N3L 3K4 519-442-7804 x210 From berrange at redhat.com Fri Nov 10 14:01:34 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 14:01:34 +0000 Subject: Me too - Re: [Fedora-xen] dissapearing guests In-Reply-To: <45548493.2020005@thompsonprint.com> References: <45533CAF.1080800@paulororke.net> <45548493.2020005@thompsonprint.com> Message-ID: <20061110140134.GA19736@redhat.com> On Fri, Nov 10, 2006 at 08:54:27AM -0500, Rodger Haynes wrote: > I am experiencing the same problem on a new Dell Optiplex GX520. I'm new > at this as well. > > Paul O'rorke wrote: > >maybe I've missed something but if I reboot or shutdown a guest domain > >I can't start it again. xm --list doesn't show the domain. From the > >Virtual Machine Manager (FC6) if I go : File --> Restore saved > >machine (Restore a saved machine from a filesystem image) and pint to > >/vm/webserver I get a dialogue box stating: > > > > *Error restoring domain '/vm/webserver'. Is the domain already > > running?* > > > > > >Similary if I try to restore from the disk file with xm restore I get > >the following: > > > > *# xm restore /vm/webserver* > > *Error: Restore failed* > > *Usage: xm restore * > > > > *Restore a domain from a saved state.* > > > > > >I'm guessing that the disk file is not the correct file to restore > >from - ?? but I can't find anywhere documentation > >on how to open these machines. No, the 'restore' functionality is for re-activating a suspended VM that has previously been saved out to disk with 'save'. Think of it as equivalent of 'hibernate to disk' on your laptop. If you shutdown/reboot the domain then 'restore' is not what you want instead you want 'create' which is equivalent of cold boot on a laptop. eg, 'xm create '. Unfortunately once you shutdown a domain, XenD looses all knowledge of it - that's why 'xm list' didn't show it, and virt-manager can't see it. Rest assured the domain is stilon disk - the config file is kept in /etc/xen. If you use 'xm create' then it loads the config file into XenD and boots the domain. We're actively working on getting support for inactivate domains into virt-manager which will help resolve the confusion in this area. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From rodger at thompsonprint.com Fri Nov 10 14:18:24 2006 From: rodger at thompsonprint.com (Rodger Haynes) Date: Fri, 10 Nov 2006 09:18:24 -0500 Subject: Me too - Re: [Fedora-xen] dissapearing guests In-Reply-To: <20061110140134.GA19736@redhat.com> References: <45533CAF.1080800@paulororke.net> <45548493.2020005@thompsonprint.com> <20061110140134.GA19736@redhat.com> Message-ID: <45548A30.4050104@thompsonprint.com> Thanks - that works great! Daniel P. Berrange wrote: > On Fri, Nov 10, 2006 at 08:54:27AM -0500, Rodger Haynes wrote: > >> I am experiencing the same problem on a new Dell Optiplex GX520. I'm new >> at this as well. >> >> Paul O'rorke wrote: >> >>> maybe I've missed something but if I reboot or shutdown a guest domain >>> I can't start it again. xm --list doesn't show the domain. From the >>> Virtual Machine Manager (FC6) if I go : File --> Restore saved >>> machine (Restore a saved machine from a filesystem image) and pint to >>> /vm/webserver I get a dialogue box stating: >>> >>> *Error restoring domain '/vm/webserver'. Is the domain already >>> running?* >>> >>> >>> Similary if I try to restore from the disk file with xm restore I get >>> the following: >>> >>> *# xm restore /vm/webserver* >>> *Error: Restore failed* >>> *Usage: xm restore * >>> >>> *Restore a domain from a saved state.* >>> >>> >>> I'm guessing that the disk file is not the correct file to restore >>> >> >from - ?? but I can't find anywhere documentation >> >>> on how to open these machines. >>> > > No, the 'restore' functionality is for re-activating a suspended VM > that has previously been saved out to disk with 'save'. Think of it > as equivalent of 'hibernate to disk' on your laptop. > > If you shutdown/reboot the domain then 'restore' is not what you want > instead you want 'create' which is equivalent of cold boot on a laptop. > eg, 'xm create '. > > Unfortunately once you shutdown a domain, XenD looses all knowledge of > it - that's why 'xm list' didn't show it, and virt-manager can't see > it. Rest assured the domain is stilon disk - the config file is kept > in /etc/xen. If you use 'xm create' then it loads the config file into > XenD and boots the domain. > > We're actively working on getting support for inactivate domains into > virt-manager which will help resolve the confusion in this area. > > Regards, > Dan. > -- Rodger Haynes Thompson Printing & Lithographing Paris, ON N3L 3K4 519-442-7804 x210 From ben at benevans.demon.co.uk Fri Nov 10 14:50:43 2006 From: ben at benevans.demon.co.uk (Ben Evans) Date: Fri, 10 Nov 2006 14:50:43 -0000 Subject: [Fedora-xen] No console and other woes Xen and FC6 Message-ID: <005f01c704d7$9ad99920$0c00a8c0@amd> OK, I'm using (or trying to use) Xen on FC6, everything completely bog standard. I'm obviously really missing something because I've been going nowhere. I can fire up the vm manager GUI, configure a new vm, drop FC6 on it (and obviously see the domain-0), both the Xen demons are running. However, after the vm tries to reboot during the install, it *disappears* from the vm manager, and try as I might I can't find a way to restart the vm. So then I tried saving the sate of the vm before rebooting it, using the "save" menu item, which I presume squirts some kind of state image to disk. However, I can't get on the console of a saved and restored machine using the virtual machine manager, I just get a message saying "The console is currently unavailable" despite the fact that the vm manger quite happily says the vm is running. Also, the vm manager *deletes* the state image without offering you the opportunity to preserve it as soon as you "restore" it! I think the menu terminology used for this user interface is not very well thought out really. Perhaps "Irretrievably Break" would be a better label than "Restore" on the menu for this item? Anyway, I'm sure it's all good stuff, I just need to find out how to make it work before chucking the computer off my fifth floor balcony. Any advice gratefully received.. Cheers Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From job317 at mailvault.com Fri Nov 10 15:22:11 2006 From: job317 at mailvault.com (Job 317) Date: Fri, 10 Nov 2006 16:22:11 00100 (CET) Subject: [Fedora-xen] Xen guests on FC5 Message-ID: <20061110152212.29F9FB643D0@gateway.mailvault.com> Hi list, Can someone please direct me to tutorials or descriptions of installing any of the following guest OSes in Xen with a FC5 xen0: FreeBSD OpenBSD NetBSD Solaris Intel 10 So far I have only used the FC5 tutorial for installint an FC4 guest which worked quite well. Thanks, Job From veillard at redhat.com Fri Nov 10 15:31:54 2006 From: veillard at redhat.com (Daniel Veillard) Date: Fri, 10 Nov 2006 10:31:54 -0500 Subject: [Fedora-xen] No console and other woes Xen and FC6 In-Reply-To: <005f01c704d7$9ad99920$0c00a8c0@amd> References: <005f01c704d7$9ad99920$0c00a8c0@amd> Message-ID: <20061110153154.GC2116@redhat.com> On Fri, Nov 10, 2006 at 02:50:43PM -0000, Ben Evans wrote: > OK, I'm using (or trying to use) Xen on FC6, everything completely bog > standard. I'm obviously really missing something because I've been going > nowhere. > > > > I can fire up the vm manager GUI, configure a new vm, drop FC6 on it (and > obviously see the domain-0), both the Xen demons are running. However, after > the vm tries to reboot during the install, it *disappears* from the vm > manager, and try as I might I can't find a way to restart the vm. this is being worked on. At this point you need to run 'xm create $vm_name' as root to start an halted domain. > Also, the vm manager *deletes* the state image without offering you the > opportunity to preserve it as soon as you "restore" it! That's normal. The state of the system is also tied to the state of the disk images. If you were to restore, halt, and restart from the restore point you would just run off filesystems in a different state and nearly garanteed to corrupt the disk images. > I think the menu terminology used for this user interface is not very well > thought out really. Perhaps "Irretrievably Break" would be a better label > than "Restore" on the menu for this item? Save and Restore are the canonical names for those operation you would find in operating system courses. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard at redhat.com Fri Nov 10 15:33:21 2006 From: veillard at redhat.com (Daniel Veillard) Date: Fri, 10 Nov 2006 10:33:21 -0500 Subject: [Fedora-xen] Xen guests on FC5 In-Reply-To: <20061110152212.29F9FB643D0@gateway.mailvault.com> References: <20061110152212.29F9FB643D0@gateway.mailvault.com> Message-ID: <20061110153320.GD2116@redhat.com> On Fri, Nov 10, 2006 at 04:22:11PM +0000, Job 317 wrote: > Hi list, > > Can someone please direct me to tutorials or descriptions of installing > any of the following guest OSes in Xen with a FC5 xen0: > > FreeBSD > OpenBSD > NetBSD > Solaris Intel 10 I don't think those have been ported to Xen 3.0.x yet. Best asked on the mailing for those communities though. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From russell at flora.ca Fri Nov 10 17:50:48 2006 From: russell at flora.ca (Russell McOrmond) Date: Fri, 10 Nov 2006 12:50:48 -0500 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <20061110010412.GO5223@redhat.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> <1163119629.8745.4.camel@krs> <20061110010412.GO5223@redhat.com> Message-ID: <4554BBF8.2030302@flora.ca> Daniel P. Berrange wrote: > Then again, some people may like to have a single kernel image in the Dom0 > whcih they use to boot all their guest images. If you want to manage your > guests that way, simply add the 'kernel=/foo/bar/wizz' parameter to the > guest config, and remove the pygrub config option. Quick note: This assumes a statically linked kernel. You still have to install the matching kernel modules into the guest filesystem, and IMHO the easiest way to do that is to just install the kernel package that contains them. I really believe that for the average setup that pygrub is a great time saver. I just wish it were finished and had some of the missing features that grub has (IE: ability to on-the-fly edit a config and boot, which avoids having to fiddle with the Xen config in order to go into single user mode. -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From berrange at redhat.com Fri Nov 10 18:19:54 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 18:19:54 +0000 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <4554BBF8.2030302@flora.ca> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> <1163119629.8745.4.camel@krs> <20061110010412.GO5223@redhat.com> <4554BBF8.2030302@flora.ca> Message-ID: <20061110181954.GE19736@redhat.com> On Fri, Nov 10, 2006 at 12:50:48PM -0500, Russell McOrmond wrote: > Daniel P. Berrange wrote: > >Then again, some people may like to have a single kernel image in the Dom0 > >whcih they use to boot all their guest images. If you want to manage your > >guests that way, simply add the 'kernel=/foo/bar/wizz' parameter to the > >guest config, and remove the pygrub config option. > > Quick note: This assumes a statically linked kernel. You still have to > install the matching kernel modules into the guest filesystem, and IMHO > the easiest way to do that is to just install the kernel package that > contains them. > > I really believe that for the average setup that pygrub is a great > time saver. I just wish it were finished and had some of the missing > features that grub has (IE: ability to on-the-fly edit a config and > boot, which avoids having to fiddle with the Xen config in order to go > into single user mode. Urm, you can already do that. xm create -c foo Will popup the familiar grub menu - select an entry, press 'e' to edit it, append 'S', and then boot - just as with regular grub. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Nov 10 18:28:01 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 18:28:01 +0000 Subject: [Fedora-xen] [berrange@redhat.com: Fedora Core 6 Test Update: virt-manager-0.2.6-1.fc6] Message-ID: <20061110182801.GF19736@redhat.com> If anyone is interested in testing out the new 0.2.6 release of virt-manager I have it available in the 'updates-testing' repository for FC6. If there's no bad regressions uncovered I aim to push it to 'updates' within the next week. Regards, Dan. ----- Forwarded message from Daniel Berrange ----- > Date: Fri, 10 Nov 2006 09:46:21 -0500 > From: "Daniel Berrange" > To: fedora-test-list at redhat.com > Subject: Fedora Core 6 Test Update: virt-manager-0.2.6-1.fc6 > > --------------------------------------------------------------------- > Fedora Test Update Notification > FEDORA-2006-1210 > 2006-11-10 > --------------------------------------------------------------------- > > Product : Fedora Core 6 > Name : virt-manager > Version : 0.2.6 > Release : 1.fc6 > Summary : Virtual Machine Manager > Description : > Virtual Machine Manager provides a graphical tool for administering > virtual machines such as Xen. It uses libvirt as the backend management > API. > > --------------------------------------------------------------------- > Update Information: > > Updated to new 0.2.6 release: > > The release focus has been on major bug fixing. This is also > the first release in which (partial) translations are > available for the UI in approximately 20 languages - thanks > to the Fedora i18n team for excellant progress on this. It > is now possible to control the virt-manager UI with command > line arguments as well as the DBus API & it DBus activation > is no longer used by default which fixes interaction with > GNOME keyring & AT-SPI accesibility. Numerous UI issues were > fixed / clarified, particularly in the graphical console and > new VM creation wizard. > > > --------------------------------------------------------------------- > * Thu Nov 9 2006 Daniel P. Berrange - 0.2.6-1.fc6 > - Imported translations from Fedora i18n repository > - Make (most) scrollbar policies automatic > - Set busy cursor while creating new VMs > - Preference for controlling keygrab policy > - Preference for when to automatically open console (bz 211385) > - Re-try VNC connection attempt periodically in case VNC daemon > hasn't finished starting up > - Added activation of URLs for about dialog (bz 210782) > - Improved error reporting when connecting to HV (bz 211229) > - Add command line args to open specific windows > - Don't skip para/full virt wizard step - instead gray out full > virt option & tell user why > - Change 'physical' to 'logical' when refering to host CPUs > - Include hostname in titlebar > - Disable wizard sensitivity while creating VM > * Thu Oct 19 2006 Daniel P. Berrange - 0.2.5-1.fc6 > - Switch to use python-virtinst instead of python-xeninst due to > renaming of original package > - Disable keyboard accelerators when grabbing mouse to avoid things like > Ctrl-W closing the local window, instead of remote window bz 210364 > - Fix host memory reporting bz 211281 > - Remove duplicate application menu entry bz 211230 > - Fix duplicated mnemonics (bz 208408) > - Use blktap backed disks if available > - Use a drop down list to remember past URLs (bz 209479) > - Remove unused help button from preferences dialog (bz 209251) > - Fix exception when no VNC graphics is defined > - Force immediate refresh of VMs after creating a new one > - Improve error reporting if run on a kernel without Xen (bz 209122) > - More fixes to avoid stuck modifier keys on focus-out (bz 207949) > > --------------------------------------------------------------------- > This update can be downloaded from: > http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/ > > 70dad2bb5b6f3588147a8d6e6e37f87a83703416 SRPMS/virt-manager-0.2.6-1.fc6.src.rpm > 70dad2bb5b6f3588147a8d6e6e37f87a83703416 noarch/virt-manager-0.2.6-1.fc6.src.rpm > 9ccdc589489c0801062b6fe6f3753f86e73310c6 x86_64/debug/virt-manager-debuginfo-0.2.6-1.fc6.x86_64.rpm > 7adcd56a8be24ce6b6e62b9789a4ab21ba0c8563 x86_64/virt-manager-0.2.6-1.fc6.x86_64.rpm > 49ed4dd798ff8f40954aa48cab0b5f9dfef1ed71 i386/virt-manager-0.2.6-1.fc6.i386.rpm > c14b8a218299777a94c8b512d4309beb19f77104 i386/debug/virt-manager-debuginfo-0.2.6-1.fc6.i386.rpm > > This update can be installed with the 'yum' update program. Use 'yum update > package-name' at the command line. For more information, refer to 'Managing > Software with yum,' available at http://fedora.redhat.com/docs/yum/. > --------------------------------------------------------------------- > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > ----- End forwarded message ----- -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at paulororke.net Fri Nov 10 18:51:41 2006 From: paul at paulororke.net (Paul O'Rorke) Date: Fri, 10 Nov 2006 10:51:41 -0800 Subject: Me too - Re: [Fedora-xen] dissapearing guests In-Reply-To: <45548A30.4050104@thompsonprint.com> References: <45533CAF.1080800@paulororke.net> <45548493.2020005@thompsonprint.com> <20061110140134.GA19736@redhat.com> <45548A30.4050104@thompsonprint.com> Message-ID: <4554CA3D.8050000@paulororke.net> Great when there is a simple fix. Thanks soooo much. Is this documented somewhere and I missed it? Rodger Haynes wrote: > Thanks - that works great! > > Daniel P. Berrange wrote: >> On Fri, Nov 10, 2006 at 08:54:27AM -0500, Rodger Haynes wrote: >> >>> I am experiencing the same problem on a new Dell Optiplex GX520. I'm >>> new at this as well. >>> >>> Paul O'rorke wrote: >>> >>>> maybe I've missed something but if I reboot or shutdown a guest >>>> domain I can't start it again. xm --list doesn't show the domain. >>>> From the Virtual Machine Manager (FC6) if I go : File --> Restore >>>> saved machine (Restore a saved machine from a filesystem image) >>>> and pint to /vm/webserver I get a dialogue box stating: >>>> >>>> *Error restoring domain '/vm/webserver'. Is the domain already >>>> running?* >>>> >>>> >>>> Similary if I try to restore from the disk file with xm restore I >>>> get the following: >>>> >>>> *# xm restore /vm/webserver* >>>> *Error: Restore failed* >>>> *Usage: xm restore * >>>> >>>> *Restore a domain from a saved state.* >>>> >>>> >>>> I'm guessing that the disk file is not the correct file to restore >>>> >>> >from - ?? but I can't find anywhere >>> documentation >>>> on how to open these machines. >> >> No, the 'restore' functionality is for re-activating a suspended VM >> that has previously been saved out to disk with 'save'. Think of it >> as equivalent of 'hibernate to disk' on your laptop. >> >> If you shutdown/reboot the domain then 'restore' is not what you want >> instead you want 'create' which is equivalent of cold boot on a laptop. >> eg, 'xm create '. >> Unfortunately once you shutdown a domain, XenD looses all knowledge of >> it - that's why 'xm list' didn't show it, and virt-manager can't see >> it. Rest assured the domain is stilon disk - the config file is kept >> in /etc/xen. If you use 'xm create' then it loads the config file into >> XenD and boots the domain. >> >> We're actively working on getting support for inactivate domains into >> virt-manager which will help resolve the confusion in this area. >> >> Regards, >> Dan. >> > From russell at flora.ca Fri Nov 10 20:12:13 2006 From: russell at flora.ca (Russell McOrmond) Date: Fri, 10 Nov 2006 15:12:13 -0500 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <20061110181954.GE19736@redhat.com> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> <1163119629.8745.4.camel@krs> <20061110010412.GO5223@redhat.com> <4554BBF8.2030302@flora.ca> <20061110181954.GE19736@redhat.com> Message-ID: <4554DD1D.6050703@flora.ca> Daniel P. Berrange wrote: > Urm, you can already do that. > > xm create -c foo > > Will popup the familiar grub menu - select an entry, press 'e' to edit > it, append 'S', and then boot - just as with regular grub. Thank you. I didn't test with the recent upgrade of the Xen package that has a new (and much improved) pygrub. This is great, and deals with one of the missing pieces with the previous version. Note: The version of pygrub from xen-3.0.2-3.FC5 had a lot of "# FIXME:" comments in it where the edit/etc functions are now in xen-3.0.3-1.fc5. -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From berrange at redhat.com Fri Nov 10 20:17:47 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 20:17:47 +0000 Subject: [Fedora-xen] Upgrade FC5 Xen -> FC6 In-Reply-To: <4554DD1D.6050703@flora.ca> References: <53812.24.75.124.5.1162412331.squirrel@mail.emitony.com> <1162427452.8227.13.camel@krs> <454A1BA3.7080606@emitony.com> <45534F71.5090504@base2technology.com> <20061109160317.GC5223@redhat.com> <1163119629.8745.4.camel@krs> <20061110010412.GO5223@redhat.com> <4554BBF8.2030302@flora.ca> <20061110181954.GE19736@redhat.com> <4554DD1D.6050703@flora.ca> Message-ID: <20061110201746.GI19736@redhat.com> On Fri, Nov 10, 2006 at 03:12:13PM -0500, Russell McOrmond wrote: > Daniel P. Berrange wrote: > >Urm, you can already do that. > > > > xm create -c foo > > > >Will popup the familiar grub menu - select an entry, press 'e' to edit > >it, append 'S', and then boot - just as with regular grub. > > Thank you. I didn't test with the recent upgrade of the Xen package > that has a new (and much improved) pygrub. This is great, and deals > with one of the missing pieces with the previous version. > > Note: The version of pygrub from xen-3.0.2-3.FC5 had a lot of "# FIXME:" > comments in it where the edit/etc functions are now in xen-3.0.3-1.fc5. Yes, that version of xen from FC5 was really a work-in-progress snapshot of the xen-unstable tree, halfway between 3.0.2 & 3.0.3. Jeremy & others did alot of work to improve pygrub intime for xen 3.0.3 / FC6 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jochen.wiedmann at gmail.com Fri Nov 10 22:56:18 2006 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Fri, 10 Nov 2006 23:56:18 +0100 Subject: [Fedora-xen] Disk image does not exist Message-ID: Hi, I am trying to create a new guest using virt-manager. I have verified that pae and hvm are present. xend and xendomains have been started. In virt-manager, I have entered the following data: Name: fc6-guest Fully Virtualized CD-ROM (FC6 DVD is in the drive) Simple file, location /var/xen/win/data (file exists with size of 5GB) VM Max Memory = Startup Memory = 800MB, 1 CPU However, when I try to finish, I receive the error message Error creating domain: Disk image does not exist: /var/xen/win/data' (See log file below.) I have tried both the fc6 virt-manager and the rawhide virt-manager. Any ideas, what might be wrong? Thanks, Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'fc6-guest'], ['memory', '800'], ['maxmem', '800'], ['vcpus', '1'], ['uuid', 'ab3b46b4-8826-018f-a97b-e7d85865df16'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['boot', 'd'], ['acpi', '1'], ['apic', '1'], ['pae', '1'], ['vnc', '1'], ['vncunused', '1']]], ['device', ['vbd', ['dev', 'hda:disk'], ['uname', 'file:/var/xen/win/data'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'phy:/dev/hdc'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:11:e8:be'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']]]]) [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'fc6-guest'], ['memory', '800'], ['maxmem', '800'], ['vcpus', '1'], ['uuid', 'ab3b46b4-8826-018f-a97b-e7d85865df16'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['boot', 'd'], ['acpi', '1'], ['apic', '1'], ['pae', '1'], ['vnc', '1'], ['vncunused', '1']]], ['device', ['vbd', ['dev', 'hda:disk'], ['uname', 'file:/var/xen/win/data'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'phy:/dev/hdc'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:11:e8:be'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']]]] [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, 'uuid': 'ab3b46b4-8826-018f-a97b-e7d85865df16', 'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None, 'image': ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['boot', 'd'], ['acpi', '1'], ['apic', '1'], ['pae', '1'], ['vnc', '1'], ['vncunused', '1']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'fc6-guest', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 800, 'device': [('vbd', ['vbd', ['dev', 'hda:disk'], ['uname', 'file:/var/xen/win/data'], ['mode', 'w']]), ('vbd', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'phy:/dev/hdc'], ['mode', 'r']]), ('vif', ['vif', ['mac', '00:16:3e:11:e8:be'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': 800} [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:1253) XendDomainInfo.construct: None [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:1285) XendDomainInfo.initDomain: 5 1.0 [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: boot, val: d [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: fda, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: fdb, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: soundhw, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: localtime, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: serial, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: std-vga, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: isa, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: vcpus, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: acpi, val: 1 [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: usb, val: None [2006-11-10 23:46:55 xend 3028] DEBUG (image:379) args: usbdevice, val: None [2006-11-10 23:46:55 xend.XendDomainInfo 3028] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1298, in initDomain self.info['device']) File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 47, in create return findImageHandlerClass(imageConfig)(vm, imageConfig, deviceConfig) File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 77, in __init__ self.configure(imageConfig, deviceConfig) File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 314, in configure self.dmargs = self.parseDeviceModelArgs(imageConfig, deviceConfig) File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 391, in parseDeviceModelArgs raise VmError('Disk image does not exist: %s' % VmError: Disk image does not exist: /var/xen/win/data [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=5 [2006-11-10 23:46:55 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(5) [2006-11-10 23:46:55 xend 3028] ERROR (SrvBase:88) Request create failed. Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 82, in op_create raise XendError("Error creating domain: " + str(ex)) XendError: Error creating domain: Disk image does not exist: /var/xen/win/data From berrange at redhat.com Fri Nov 10 23:04:58 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 10 Nov 2006 23:04:58 +0000 Subject: [Fedora-xen] Disk image does not exist In-Reply-To: References: Message-ID: <20061110230458.GK19736@redhat.com> On Fri, Nov 10, 2006 at 11:56:18PM +0100, Jochen Wiedmann wrote: > Hi, > > I am trying to create a new guest using virt-manager. I have verified > that pae and hvm are present. xend and xendomains have been started. > In virt-manager, I have entered the following data: > > Name: fc6-guest > Fully Virtualized > CD-ROM (FC6 DVD is in the drive) > Simple file, location /var/xen/win/data (file exists with size of 5GB) > VM Max Memory = Startup Memory = 800MB, 1 CPU > > However, when I try to finish, I receive the error message > > Error creating domain: Disk image does not exist: /var/xen/win/data' The default SELinux policy on FC6 only labels /xen with neccesary context to allow XenD access to the disk. So if you want to store your images under /var/xen then you need to either symlink this to /xen, or better add your path to the policy, eg # semanage fcontext -a -f "" -t xen_image_t '/var/xen(/.*)?' # restorecon -R /var/xen Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jochen.wiedmann at gmail.com Sat Nov 11 01:04:58 2006 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Sat, 11 Nov 2006 02:04:58 +0100 Subject: [Fedora-xen] VM has gone after reboot Message-ID: Hi, I have successfully created a fully virtualized VM using virt-manager on FC6, using virt-manager 2.0.6 from FC7. I was able to boot the installation disk and install the operating system. Everything went fine until the machine was rebooting. At that point my console window broke down. I noticed the following message in my local terminal window, which started virt-manager: libvir: Xen Daemon error : GET operation failed: No such domain win libvir: Xen Daemon error : GET operation failed: No such domain 1 libvir: error : library call virDomainGetXMLDesc failed, possibly not supported Traceback (most recent call last): File "/var/tmp/virt-manager-0.2.6-1-root-root/usr/share/virt-manager/./virtManager/details.py", line 287, in refresh_resources File "/var/tmp/virt-manager-0.2.6-1-root-root/usr/share/virt-manager/./virtManager/domain.py", line 202, in vcpu_max_count TypeError: int() argument must be a string or a number In xend.log, I only found the following message: libvir: Xen Daemon error : GET operation failed: No such domain win libvir: Xen Daemon error : GET operation failed: No such domain 1 libvir: error : library call virDomainGetXMLDesc failed, possibly not supported Traceback (most recent call last): File "/var/tmp/virt-manager-0.2.6-1-root-root/usr/share/virt-manager/./virtManager/details.py", line 287, in refresh_resources File "/var/tmp/virt-manager-0.2.6-1-root-root/usr/share/virt-manager/./virtManager/domain.py", line 202, in vcpu_max_count TypeError: int() argument must be a string or a number As a consequence, the VM has gone from virt-manager, which only allows me to create a new VM. Any ideas how to go on? Thanks, Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) From shobha.ranganathan at intel.com Sat Nov 11 02:49:02 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Fri, 10 Nov 2006 18:49:02 -0800 Subject: [Fedora-xen] virt-manager just exits and virt-install errors out in FC6 host OS Message-ID: I have a FC6 host OS. I am trying to install unmodified guest using /usr/sbin/virt-manager. I get a GUI and I connect to local Xen host and Click on Connect. That is it . Nothing else happens Also /usr/sbin/virt-install gives me error that virConnectOpen() failed. Any ideas on what is happening ? Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From job317 at mailvault.com Sat Nov 11 19:44:44 2006 From: job317 at mailvault.com (Job 317) Date: Sat, 11 Nov 2006 20:44:44 00100 (CET) Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting Message-ID: <20061111194444.864F6B642A6@gateway.mailvault.com> Hi list, I have seen this topic written about on a number of sites but none of the suggested fixed have worked for me. I have a FC5 box with 1GB RAM and the latest xen-3.0.3-1.fc5 package as well as kernel-xen0 and kernel-xenU-2.6.18-1.2239.fc5 installed. I followed the install instructions at http://www.fedoraproject.org/wiki/FedoraXenQuickstart to install Fedora Core 4 as a xen guest and have booted into the xen0 kernel. My guest has 256 MB RAM. Here's the config: kernel="/boot/vmlinuz-2.6.18-1.2239.fc5xenU" memory = 256 name = "rawhide" vif = [ '', 'bridge=xenbr0' ] disk = ['file:/root/XEN/fedora.img,sda1,w'] root = "/dev/sda1" extra = "ro selinux=0 3" When I type "xm create -c rawhide" in a KDE Konsole window, my guest starts to boot but does not finish. I have tried adding "echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf" as one web site suggested. No luck. I tried adding vnc=1 and vnclisten="127.0.0.1" to my xen guest config file but no luck. I am logged in as root when I run xm. Here is the screen printout when I boot my VM: [root at localhost ~]# xm create -c rawhide Using config file "/etc/xen/rawhide". Started domain rawhide Linux version 2.6.18-1.2239.fc5xenU (brewbuilder at hs20-bc1-7.build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 SMP Fri Nov 10 14:15:41 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/sda1 ro selinux=0 3 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c06dd000 soft=c06bd000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 1196.467 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-fb3fe000, maxmem 33ffe000 Memory: 255292k/270336k available (1719k kernel code, 6540k reserved, 633k data, 144k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy. Probably due to long platform interrupts. Consider using "lpj=" boot option. Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs xen_mem: Initialising balloon driver. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 6, 327680 bytes) TCP bind hash table entries: 8192 (order: 5, 163840 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1163273992.613:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 481F17AAEB289250 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.18-1.2239.fc5xenU (brewbuilder at hs20-bc1-7.build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 SMP Fri Nov 10 14:15:41 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/sda1 ro selinux=0 3 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c06dd000 soft=c06bd000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 1196.467 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-fb3fe000, maxmem 33ffe000 Memory: 255292k/270336k available (1719k kernel code, 6540k reserved, 633k data, 144k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy. Probably due to long platform interrupts. Consider using "lpj=" boot option. Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs xen_mem: Initialising balloon driver. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 6, 327680 bytes) TCP bind hash table entries: 8192 (order: 5, 163840 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1163273992.613:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 481F17AAEB289250 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx Registering block device major 8 ide-floppy driver 0.99.newide i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/vif/1 md: Autodetecting RAID arrays. md: autorun ... 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: 144k freed Write protecting the kernel read-only data: 258k 4gb seg fixup, process init (pid 1), cs:ip 73:007a65e5 4gb seg fixup, process init (pid 1), cs:ip 73:0075184e 4gb seg fixup, process init (pid 1), cs:ip 73:007c199e 4gb seg fixup, process init (pid 1), cs:ip 73:00750554 4gb seg fixup, process init (pid 1), cs:ip 73:00750562 4gb seg fixup, process init (pid 1), cs:ip 73:007a6322 4gb seg fixup, process init (pid 1), cs:ip 73:0074ae9c 4gb seg fixup, process init (pid 1), cs:ip 73:007adeda 4gb seg fixup, process init (pid 1), cs:ip 73:0071527c 4gb seg fixup, process init (pid 1), cs:ip 73:00750554 modprobe: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory INIT: version 2.85 booting /etc/rc.d/rc.sysinit: line 78: /dev/tty1: Read-only file system /etc/rc.d/rc.sysinit: line 78: /dev/tty2: Read-only file system /etc/rc.d/rc.sysinit: line 78: /dev/tty3: Read-only file system /etc/rc.d/rc.sysinit: line 78: /dev/tty4: Read-only file system /etc/rc.d/rc.sysinit: line 78: /dev/tty5: Read-only file system /etc/rc.d/rc.sysinit: line 78: /dev/tty6: Read-only file system /etc/rc.d/rc.sysinit: line 82: /dev/tty7: Read-only file system /etc/rc.d/rc.sysinit: line 83: /dev/tty8: Read-only file system Welcome to Fedora Core Press 'I' to enter interactive startup. Starting udev:[ OK ] Initializing hardware... storage network audio done[ OK ] Setting clock : Sat Nov 11 14:40:07 EST 2006 [ OK ] Setting hostname localhost: [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 /dev/sda1: clean, 26465/262656 files, 220368/524288 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] Enabling swap space: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Checking for new hardwaremodprobe: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory mmap /dev/mem: Bad address mmap /dev/mem: Bad address modprobe: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory [ OK ] Starting pcmcia: Starting PCMCIA services: FATAL: Could not load /lib/modules/2.6.18-1.2239.fc5xenU/modules.dep: No such file or directory [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Networking not configured - exiting Can't open RFCOMM control socket: Address family not supported by protocol Starting automount: printk: 571702 messages suppressed. 4gb seg fixup, process S28autofs (pid 543), cs:ip 73:0074cf6e [ OK ] Starting cups: [ OK ] Starting sshd: [ OK ] Starting sendmail: [ OK ] Starting sm-client: [ OK ] Starting console mouse services: [ OK ] Starting crond: [ OK ] Starting anacron: [ OK ] Starting atd: [ OK ] Starting system message bus: [ OK ] Starting HAL daemon: [ OK ] printk: 446257 messages suppressed. 4gb seg fixup, process udevsend (pid 735), cs:ip 73:002eb5e5 printk: 574719 messages suppressed. 4gb seg fixup, process sendmail (pid 646), cs:ip 73:00382554 printk: 15 messages suppressed. Any suggestions? Thanks, Job From berrange at redhat.com Sat Nov 11 22:29:08 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 11 Nov 2006 22:29:08 +0000 Subject: [Fedora-xen] virt-manager just exits and virt-install errors out in FC6 host OS In-Reply-To: References: Message-ID: <20061111222908.GA18678@redhat.com> On Fri, Nov 10, 2006 at 06:49:02PM -0800, Ranganathan, Shobha wrote: > I have a FC6 host OS. I am trying to install unmodified guest using > /usr/sbin/virt-manager. > > I get a GUI and I connect to local Xen host and Click on Connect. > > > > That is it . Nothing else happens > > > > Also /usr/sbin/virt-install gives me error that virConnectOpen() failed. Sounds very much like XenD is not running - 'service xend start' should resolve the issue. If it doesn't, check if you can run 'virsh list' and if not, post the output / errror to this list. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From adrian at creative.net.au Sun Nov 12 02:01:42 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Sun, 12 Nov 2006 10:01:42 +0800 Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting In-Reply-To: <20061111194444.864F6B642A6@gateway.mailvault.com> References: <20061111194444.864F6B642A6@gateway.mailvault.com> Message-ID: <20061112020142.GW31801@skywalker.creative.net.au> On Sat, Nov 11, 2006, Job 317 wrote: > Hi list, > > I have seen this topic written about on a number of sites but none of > the suggested fixed have worked for me. You need to do one or more of this in the DomUs: * do the nosegneg stuff as you've siad; but it doesn't work for me with Debian/Ubuntu guests for some reason (shrug, I haven't looked into it that much) * Install Xen-friendly (ie, nosegneg) libc libraries * Make sure /lib/tls ain't there. I've deleted /lib/tls and rebooted; its quietened down substantially. It'd be nice if the printk were disable'able somehow as it really does seem to stop things booting from time to time.. adrian From dbond at nrggos.com.au Sun Nov 12 02:13:23 2006 From: dbond at nrggos.com.au (Bond, Darryl) Date: Sun, 12 Nov 2006 12:13:23 +1000 Subject: [Fedora-xen] VLANs on DomU domains Message-ID: <0C8700BB853BC3439ABEBCCDA916256C10B91F@gpsmail.gps.local> I am setting up a box with FC6 + xen with FC6 for the DomU guests. I have a server with 4 gigabit ports and I want to use 802.1Q vlans on one of the gig ports. I have the VLANs configured in Dom0 without any addresses attached to them. How do I make the VLANs available to the guests? I want to make 4 VLANs available to each guest. I have thought of a few alternatives but I cannot get any to work. 1. Bridge the tagged 802.1Q stream from the Gig port through to the guests and configure eth0.x. on the guests 2. Create a bridge on Dom0 for each VLAN so that they appear as eth0...eth3 on the guests. The xen documentation is minimal for configuring VLANs. Is there a (FC6) supported way of configuring them? Regards Darryl __________________________________________________________________________________ DISCLAIMER The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company. From master at bradleyland.com Sun Nov 12 05:06:50 2006 From: master at bradleyland.com (master at bradleyland.com) Date: Sat, 11 Nov 2006 21:06:50 -0800 (PST) Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting In-Reply-To: <20061112020142.GW31801@skywalker.creative.net.au> References: <20061111194444.864F6B642A6@gateway.mailvault.com> <20061112020142.GW31801@skywalker.creative.net.au> Message-ID: <4102.192.168.1.2.1163308010.squirrel@www.bradleyland.com> I've done all of that without success. Any other ideas? I've renamed /lib/tls to /lib/tls.disabled and echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf Behavior is still the same, makes the console unusable. This is FC5 with all the latest updates. From adrian at creative.net.au Sun Nov 12 05:17:29 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Sun, 12 Nov 2006 13:17:29 +0800 Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting In-Reply-To: <4102.192.168.1.2.1163308010.squirrel@www.bradleyland.com> References: <20061111194444.864F6B642A6@gateway.mailvault.com> <20061112020142.GW31801@skywalker.creative.net.au> <4102.192.168.1.2.1163308010.squirrel@www.bradleyland.com> Message-ID: <20061112051729.GZ31801@skywalker.creative.net.au> On Sat, Nov 11, 2006, master at bradleyland.com wrote: > I've done all of that without success. Any other ideas? Hm, are these programs all compiled statically? I get a few things complaining about seg fixups (mostly nash-hotplug from the ramdisk image) but the above fixed it for me. I moved it from /lib/tls to /tls.{12345etc} just in case. It shouldn't pick up stuff in /lib/* but who knows.. I also have to redo it all from time to time whenever debian/ubuntu update the libc packages. It really would be nice if the printk was a run/boot time option, perhaps something quenchable via a boot parameter. Some of us want to run Xen with older, non-FC domU's and this kind of stuff just breaks it. Adrian From master at bradleyland.com Sun Nov 12 06:05:30 2006 From: master at bradleyland.com (master at bradleyland.com) Date: Sat, 11 Nov 2006 22:05:30 -0800 (PST) Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting In-Reply-To: <20061112051729.GZ31801@skywalker.creative.net.au> References: <20061111194444.864F6B642A6@gateway.mailvault.com> <20061112020142.GW31801@skywalker.creative.net.au> <4102.192.168.1.2.1163308010.squirrel@www.bradleyland.com> <20061112051729.GZ31801@skywalker.creative.net.au> Message-ID: <1736.192.168.1.2.1163311530.squirrel@www.bradleyland.com> Working now... The solution was to create a file: /etc/ld.so.conf.d/kernelcap-2.6.18-1.2200.fc5.conf and put "hwcap 0 nosegneg" in it. Nothing else worked. Been silent ever since. This was from a prior suggestion from Dan that I overlooked. From adrian at creative.net.au Sun Nov 12 06:13:09 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Sun, 12 Nov 2006 14:13:09 +0800 Subject: [Fedora-xen] 4gb seg fixup messages during boot; xen guest not booting In-Reply-To: <1736.192.168.1.2.1163311530.squirrel@www.bradleyland.com> References: <20061111194444.864F6B642A6@gateway.mailvault.com> <20061112020142.GW31801@skywalker.creative.net.au> <4102.192.168.1.2.1163308010.squirrel@www.bradleyland.com> <20061112051729.GZ31801@skywalker.creative.net.au> <1736.192.168.1.2.1163311530.squirrel@www.bradleyland.com> Message-ID: <20061112061309.GB31801@skywalker.creative.net.au> On Sat, Nov 11, 2006, master at bradleyland.com wrote: > Working now... > > The solution was to create a file: > > /etc/ld.so.conf.d/kernelcap-2.6.18-1.2200.fc5.conf > > and put "hwcap 0 nosegneg" in it. > > Nothing else worked. Been silent ever since. Nice. Sorry, what was the domU platform again? Adrian From denis.forveille at gmail.com Sun Nov 12 18:17:49 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Sun, 12 Nov 2006 13:17:49 -0500 Subject: [Fedora-xen] Win Xp 32 bit as guest in Message-ID: <4557654D.80206@gmail.com> Q: - is it possible to run an instance of Win XP SP2 32bits as a guest on a x86_64 FC6 fully updated dom0? (CPU = AMD x2 4600 with pacifica...) I successfully installed Win XP in an lvm logical volume. Everything worked fine and at the end, I got the request from XP asking to remove the CD and reboot... Then, when I try to start the guest (after changing the line from boot=d to boot=c in the config file), the only thing I see is a black screen. (the windows resize itself and then a black screen...) "xm top" shows that the guest consumes 0% CPU... I think I've tried almost every combination of parameters in the config files (pae, acpi,sdl...) during installation and after... Also, I've seen that others have post similar problems in this forum, but none of them have answers/workarounds to my problem. Does anyone succeeded in running such a combination (ie XP SP2 32 bits in a 64bit FC6)? Or maybe the problems comes from the fcat that I installed windows in an lvm instead of in a file? Thx in advance From shonorio at gmail.com Sun Nov 12 20:21:37 2006 From: shonorio at gmail.com (Solli Honorio) Date: Sun, 12 Nov 2006 18:21:37 -0200 Subject: [Fedora-xen] No graphic desktop on XEN Message-ID: <12d1f4ee0611121221l32888cepa65224646630915f@mail.gmail.com> Hi, I'm running FC 6 with gnome desktop very well on a Power Edge 6850, but when I run with Xen kernel the gnome desktop doesn't work, just a black screen. It's same behavior if I boot with level 3 and try to start gdm. I'm worrying about gnome desktop just to help-me to install and manage a guest SO. Do I need do something more to get gnome desktop working on Xen kernel ? Thanks, Solli Honorio -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha.ranganathan at intel.com Mon Nov 13 02:17:57 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Sun, 12 Nov 2006 18:17:57 -0800 Subject: [Fedora-xen] No mouse and KB activity in FC5 guest OS in FC6 xen host setup Message-ID: Here is the configuration of unmodified guest FC5 in FC6 Xen host. I have a iMac running FC6 Xen in x86 mode and FC5 as unmodified guest I get a graphics for unmodified guest which allows me login. But then no mouse and keyboard is active after logging me into FC5 unmodified guest. What is wrong ? I also tried adding nographic=1 options and usb=1 and sdl=1. I always created it again. But absolutely no mouse/KB activity. Any tip/trick is greatly appreciated as I am not making forward progress.. # Automatically generated xen config file name = "xenbox_G1FC5" builder = "hvm" memory = "256" uuid = "e56c658f-a4f2-3c10-3bb1-93a1e519bd69" disk = [ 'file:/root/xenguest4,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:42:1c:1f' ] 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 apic=1 acpi=1 pae=1 nographic = 0 # don't use graphics serial='pty' # enable serial console Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From shonorio at gmail.com Mon Nov 13 11:13:51 2006 From: shonorio at gmail.com (Solli Honorio) Date: Mon, 13 Nov 2006 09:13:51 -0200 Subject: [Fedora-xen] No graphic desktop on XEN In-Reply-To: <1163390868.2749.443.camel@dragon.valuecommerce.ne.jp> References: <12d1f4ee0611121221l32888cepa65224646630915f@mail.gmail.com> <1163390868.2749.443.camel@dragon.valuecommerce.ne.jp> Message-ID: <12d1f4ee0611130313n3c225b9kffe79ed33c808a71@mail.gmail.com> On 11/13/06, Naoki wrote: > > When you say "just a black screen", is the system locked at that point? > Can you break out of X and continue using the system as normal? And is > there anything in the 'dmesg' ? > Noaki, thanks for your attention.... Yes, I've access just by ssh and no more terminal console, even after I've set screen resolution to most low that I had option on Fedora. I attached the output of dmesg of Xen and no Xen environment because I'm not able to find anything that could answer whit strange behavior, if could help-me I will appreciate. Thanks Solli On Sun, 2006-11-12 at 18:21 -0200, Solli Honorio wrote: > > Hi, I'm running FC 6 with gnome desktop very well on a Power Edge 6850, > but when I run with Xen kernel the gnome desktop doesn't work, just a black > screen. It's same behavior if I boot with level 3 and try to start gdm. > > I'm worrying about gnome desktop just to help-me to install and manage a > guest SO. Do I need do something more to get gnome desktop working on Xen > kernel ? > > Thanks, > > Solli Honorio > > --Fedora-xen mailing listFedora-xen at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-xen > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Linux version 2.6.18-1.2798.fc6 (brewbuilder at hs20-bc2-3.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:54:20 EDT 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 00000000cfbc0000 (usable) BIOS-e820: 00000000cfbc0000 - 00000000cfbcfc00 (ACPI data) BIOS-e820: 00000000cfbcfc00 - 00000000cfbff000 (reserved) BIOS-e820: 00000000cfc00000 - 00000000d0000000 (reserved) BIOS-e820: 00000000e0000000 - 00000000fec90000 (reserved) BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000130000000 (usable) Warning only 4GB will be used. Use a PAE enabled kernel. 3200MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000fe710 Using x86 segment limits to approximate NX protection On node 0 totalpages: 1048576 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 819200 pages, LIFO batch:31 DMI 2.3 present. Using APIC driver default ACPI: RSDP (v000 DELL ) @ 0x000fcd80 ACPI: RSDT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fcd94 ACPI: FADT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fce14 ACPI: MADT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fce88 ACPI: SPCR (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fcfe4 ACPI: HPET (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd034 ACPI: MCFG (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd06c ACPI: SRAT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd0a8 ACPI: DSDT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000e) @ 0x00000000 ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x08] enabled) Processor #8 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x0e] enabled) Processor #14 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x09] enabled) Processor #9 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x04] lapic_id[0x0f] enabled) Processor #15 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0c] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x0a] disabled) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x06] disabled) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0d] disabled) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x05] disabled) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0b] disabled) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x03] disabled) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x07] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x01] address[0xfec85000] gsi_base[32]) IOAPIC[1]: apic_id 1, version 32, address 0xfec85000, GSI 32-55 ACPI: IOAPIC (id[0x02] address[0xfec85800] gsi_base[64]) IOAPIC[2]: apic_id 2, version 32, address 0xfec85800, GSI 64-87 ACPI: IOAPIC (id[0x03] address[0xfec86000] gsi_base[96]) IOAPIC[3]: apic_id 3, version 32, address 0xfec86000, GSI 96-119 ACPI: IOAPIC (id[0x04] address[0xfec86800] gsi_base[128]) IOAPIC[4]: apic_id 4, version 32, address 0xfec86800, GSI 128-151 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 5 I/O APICs ACPI: HPET id: 0xffffffff base: 0xfed00000 Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Detected 3159.136 MHz processor. Built 1 zonelists. Total pages: 1048576 Kernel command line: ro root=/dev/VG_xen/LV_dom0 rhgb quiet mapped APIC to ffffd000 (fee00000) mapped IOAPIC to ffffc000 (fec00000) mapped IOAPIC to ffffb000 (fec85000) mapped IOAPIC to ffffa000 (fec85800) mapped IOAPIC to ffff9000 (fec86000) mapped IOAPIC to ffff8000 (fec86800) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c079f000 soft=c077f000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 3361852k/4194304k available (2105k kernel code, 40416k reserved, 844k data, 240k init, 2486016k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. hpet0: at MMIO 0xfed00000 (virtual 0xf8800000), IRQs 2, 8, 0 hpet0: 3 64-bit timers, 14318180 Hz Using HPET for base-timer Calibrating delay using timer specific routine.. 6323.53 BogoMIPS (lpj=12647072) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 monitor/mwait feature present. using mwait in idle threads. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 4 CPU: After all inits, caps: bfebf3ff 20100000 00000000 00000180 0000659d 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (24) available Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code ACPI: Core revision 20060707 CPU0: Intel(R) Xeon(TM) MP CPU 3.16GHz stepping 01 SMP alternatives: switching to SMP code Booting processor 1/9 eip 3000 CPU 1 irqstacks, hard=c07a0000 soft=c0780000 Initializing CPU#1 Calibrating delay using timer specific routine.. 6317.55 BogoMIPS (lpj=12635101) CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 monitor/mwait feature present. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 4 CPU: After all inits, caps: bfebf3ff 20100000 00000000 00000180 0000659d 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel P4/Xeon Extended MCE MSRs (24) available CPU1: Intel(R) Xeon(TM) MP CPU 3.16GHz stepping 01 SMP alternatives: switching to SMP code Booting processor 2/14 eip 3000 CPU 2 irqstacks, hard=c07a1000 soft=c0781000 Initializing CPU#2 Calibrating delay using timer specific routine.. 6317.81 BogoMIPS (lpj=12635638) CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 monitor/mwait feature present. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 7 CPU: After all inits, caps: bfebf3ff 20100000 00000000 00000180 0000659d 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#2. CPU2: Intel P4/Xeon Extended MCE MSRs (24) available CPU2: Intel(R) Xeon(TM) MP CPU 3.16GHz stepping 01 SMP alternatives: switching to SMP code Booting processor 3/15 eip 3000 CPU 3 irqstacks, hard=c07a2000 soft=c0782000 Initializing CPU#3 Calibrating delay using timer specific routine.. 6317.80 BogoMIPS (lpj=12635609) CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000659d 00000000 00000000 monitor/mwait feature present. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 7 CPU: After all inits, caps: bfebf3ff 20100000 00000000 00000180 0000659d 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#3. CPU3: Intel P4/Xeon Extended MCE MSRs (24) available CPU3: Intel(R) Xeon(TM) MP CPU 3.16GHz stepping 01 Total of 4 processors activated (25276.71 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 checking TSC synchronization across 4 CPUs: passed. Brought up 4 CPUs sizeof(vma)=84 bytes sizeof(page)=32 bytes sizeof(inode)=424 bytes sizeof(dentry)=148 bytes sizeof(ext3inode)=600 bytes sizeof(buffer_head)=52 bytes sizeof(skbuff)=172 bytes sizeof(task_struct)=1392 bytes migration_cost=74,735 checking if image is initramfs... it is Freeing initrd memory: 2285k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using MMCONFIG Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: Device [M4] status [0000000c]: functional but not present; setting present ACPI: Device [M2] status [0000000c]: functional but not present; setting present ACPI: Device [M5] status [0000000c]: functional but not present; setting present ACPI: Device [M3] status [0000000c]: functional but not present; setting present ACPI: Device [M1] status [0000000c]: functional but not present; setting present ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0880-08bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 PCI: PXH quirk detected, disabling MSI for SHPC device PCI: PXH quirk detected, disabling MSI for SHPC device Boot video device is 0000:16:00.0 PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI.DOBA._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI.DOBB._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.PXA0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.PXA2._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PDLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PICH._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 12 devices usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: 00:07: ioport range 0x800-0x87f could not be reserved pnp: 00:07: ioport range 0x880-0x8bf has been reserved pnp: 00:07: ioport range 0x8c0-0x8df has been reserved pnp: 00:07: ioport range 0xc00-0xc1f has been reserved pnp: 00:07: ioport range 0xc10-0xc1f has been reserved pnp: 00:07: ioport range 0xca0-0xca7 has been reserved pnp: 00:07: ioport range 0xca9-0xcab has been reserved pnp: 00:07: ioport range 0xcad-0xcaf has been reserved PCI: Bridge: 0000:00:01.0 IO window: e000-efff MEM window: dfe00000-dfefffff PREFETCH window: db000000-dbffffff PCI: Bridge: 0000:00:02.0 IO window: d000-dfff MEM window: dfd00000-dfdfffff PREFETCH window: da000000-daffffff PCI: Bridge: 0000:00:03.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:04.0 IO window: c000-cfff MEM window: dfc00000-dfcfffff PREFETCH window: d9000000-d9ffffff PCI: Bridge: 0000:00:05.0 IO window: b000-bfff MEM window: dfb00000-dfbfffff PREFETCH window: d8000000-d8ffffff PCI: Bridge: 0000:0e:00.0 IO window: disabled. MEM window: dfa00000-dfafffff PREFETCH window: dc100000-dc1fffff PCI: Bridge: 0000:0e:00.2 IO window: a000-afff MEM window: df800000-df9fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:06.0 IO window: 9000-afff MEM window: df600000-dfafffff PREFETCH window: dc100000-dc1fffff PCI: Bridge: 0000:13:00.0 IO window: disabled. MEM window: df400000-df5fffff PREFETCH window: dc000000-dc0fffff PCI: Bridge: 0000:13:00.2 IO window: 8000-8fff MEM window: df200000-df3fffff PREFETCH window: df100000-df1fffff PCI: Bridge: 0000:00:07.0 IO window: 8000-8fff MEM window: df100000-df5fffff PREFETCH window: dc000000-dc0fffff PCI: Bridge: 0000:00:1e.0 IO window: 7000-7fff MEM window: def00000-df0fffff PREFETCH window: d0000000-d7ffffff PCI: Setting latency timer of device 0000:00:01.0 to 64 PCI: Setting latency timer of device 0000:00:02.0 to 64 PCI: Setting latency timer of device 0000:00:03.0 to 64 PCI: Setting latency timer of device 0000:00:04.0 to 64 PCI: Setting latency timer of device 0000:00:05.0 to 64 PCI: Setting latency timer of device 0000:00:06.0 to 64 ACPI: PCI Interrupt 0000:0e:00.0[A] -> GSI 16 (level, low) -> IRQ 169 PCI: Setting latency timer of device 0000:0e:00.0 to 64 PCI: Setting latency timer of device 0000:0e:00.2 to 64 PCI: Setting latency timer of device 0000:00:07.0 to 64 PCI: Setting latency timer of device 0000:13:00.0 to 64 PCI: Setting latency timer of device 0000:13:00.2 to 64 PCI: Setting latency timer of device 0000:00:1e.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 9, 2621440 bytes) TCP bind hash table entries: 65536 (order: 8, 1310720 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered apm: BIOS not found. audit: initializing netlink socket (disabled) audit(1163414777.176:1): initialized highmem bounce pool size: 64 pages Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key EAA0802BFF323905 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) PCI: Setting latency timer of device 0000:00:01.0 to 64 pcie_portdrv_probe->Dev[2601:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:01.0:pcie00] Allocate Port Service[0000:00:01.0:pcie01] Allocate Port Service[0000:00:01.0:pcie02] PCI: Setting latency timer of device 0000:00:02.0 to 64 pcie_portdrv_probe->Dev[2608:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:02.0:pcie00] Allocate Port Service[0000:00:02.0:pcie01] Allocate Port Service[0000:00:02.0:pcie02] PCI: Setting latency timer of device 0000:00:03.0 to 64 pcie_portdrv_probe->Dev[2603:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:03.0:pcie00] Allocate Port Service[0000:00:03.0:pcie01] PCI: Setting latency timer of device 0000:00:04.0 to 64 pcie_portdrv_probe->Dev[2604:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:04.0:pcie00] Allocate Port Service[0000:00:04.0:pcie01] Allocate Port Service[0000:00:04.0:pcie02] PCI: Setting latency timer of device 0000:00:05.0 to 64 pcie_portdrv_probe->Dev[2605:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:05.0:pcie00] Allocate Port Service[0000:00:05.0:pcie01] Allocate Port Service[0000:00:05.0:pcie02] PCI: Setting latency timer of device 0000:00:06.0 to 64 pcie_portdrv_probe->Dev[2606:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:06.0:pcie00] Allocate Port Service[0000:00:06.0:pcie01] PCI: Setting latency timer of device 0000:00:07.0 to 64 pcie_portdrv_probe->Dev[2607:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:07.0:pcie00] Allocate Port Service[0000:00:07.0:pcie01] ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x5 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x6 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x7 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x8 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x9 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xa ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xb ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xc ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xd ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xe ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xf ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x10 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac hpet_resources: 0xfed00000 is busy Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH5: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: Unable to derive IRQ for device 0000:00:1f.1 ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI ICH5: chipset revision 2 ICH5: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: TEAC CD-ROM CD-224E, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... Probing IDE interface ide1... ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode ACPI: (supports S0 S4 S5) Time: tsc clocksource has been installed. Freeing unused kernel memory: 240k freed Write protecting the kernel read-only data: 370k USB Universal Host Controller Interface driver v3.0 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169 PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 169, io base 0x00006ce0 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 50 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 50, io base 0x00006cc0 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 58 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 58, io base 0x00006ca0 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 66 PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:1d.7: debug port 1 PCI: cache line size of 128 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: irq 66, io mem 0xdff00000 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) SCSI subsystem initialized megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006) megaraid: probe new device 0x1000:0x1960:0x1028:0x0518: bus 15:slot 2:func 0 ACPI: PCI Interrupt 0000:0f:02.0[A] -> GSI 32 (level, low) -> IRQ 74 megaraid: fw version:[352B] bios version:[1.10] megaraid: cluster firmware, initiator ID: 6 scsi0 : LSI Logic MegaRAID driver scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices usb 4-3: new high speed USB device using ehci_hcd and address 2 usb 4-3: configuration #1 chosen from 1 choice hub 4-3:1.0: USB hub found hub 4-3:1.0: 2 ports detected usb 3-1: new low speed USB device using uhci_hcd and address 2 usb 3-1: configuration #1 chosen from 1 choice input: ATEN ATEN Composite as /class/input/input0 input: USB HID v1.10 Keyboard [ATEN ATEN Composite] on usb-0000:00:1d.2-1 input: ATEN ATEN Composite as /class/input/input1 input: USB HID v1.10 Mouse [ATEN ATEN Composite] on usb-0000:00:1d.2-1 scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices Vendor: DELL Model: PV22XS Rev: E.19 Type: Processor ANSI SCSI revision: 03 scsi[0]: scanning scsi channel 2 [virtual] for logical drives megaraid: probe new device 0x1028:0x0013:0x1028:0x0170: bus 20:slot 14:func 0 ACPI: PCI Interrupt 0000:14:0e.0[A] -> GSI 110 (level, low) -> IRQ 82 megaraid: fw version:[522A] bios version:[H430] scsi1 : LSI Logic MegaRAID driver scsi[1]: scanning scsi channel 0 [Phy 0] for non-raid devices Vendor: PE/PV Model: 1x5 SCSI BP Rev: 1.0 Type: Processor ANSI SCSI revision: 02 scsi[1]: scanning scsi channel 1 [Phy 1] for non-raid devices scsi[1]: scanning scsi channel 2 [virtual] for logical drives Vendor: MegaRAID Model: LD 0 RAID0 139G Rev: 522A Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 286515200 512-byte hdwr sectors (146696 MB) sda: Write Protect is off sda: Mode Sense: 00 00 00 00 sda: asking for cache data failed sda: assuming drive cache: write through SCSI device sda: 286515200 512-byte hdwr sectors (146696 MB) sda: Write Protect is off sda: Mode Sense: 00 00 00 00 sda: asking for cache data failed sda: assuming drive cache: write through sda: sda1 sda2 sda3 sd 1:2:0:0: Attached scsi disk sda ACPI: PCI Interrupt 0000:15:07.0[A] -> GSI 134 (level, low) -> IRQ 90 scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ACPI: PCI Interrupt 0000:15:07.1[B] -> GSI 135 (level, low) -> IRQ 98 scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel at redhat.com EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: dm-0: orphan cleanup on readonly fs ext3_orphan_cleanup: deleting unreferenced inode 1405630 EXT3-fs: dm-0: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1163414831.743:2): selinux=0 auid=4294967295 hda: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 tg3.c:v3.65 (August 07, 2006) ACPI: PCI Interrupt 0000:12:02.0[A] -> GSI 64 (level, low) -> IRQ 106 Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. eth0: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:22:74:2e:4f eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] Split[0] WireSpeed[1] TSOcap[0] eth0: dma_rwctrl[769f4000] dma_mask[64-bit] ACPI: PCI Interrupt 0000:15:06.0[A] -> GSI 132 (level, low) -> IRQ 114 ACPI: PCI Interrupt 0000:12:02.1[B] -> GSI 65 (level, low) -> IRQ 122 Intel 82802 RNG detected eth1: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:22:74:2e:50 eth1: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth1: dma_rwctrl[769f4000] dma_mask[64-bit] e1000: 0000:15:06.0: e1000_probe: (PCI:66MHz:64-bit) 00:0e:0c:85:c9:35 e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection scsi 0:1:15:0: Attached scsi generic sg0 type 3 scsi 1:0:6:0: Attached scsi generic sg1 type 3 sd 1:2:0:0: Attached scsi generic sg2 type 0 input: PC Speaker as /class/input/input2 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 lp: driver loaded but no devices found ACPI: Power Button (FF) [PWRF] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.4 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 2097144k swap on /dev/VG_xen/LV_swap. Priority:-1 extents:1 across:2097144k NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead. ADDRCONF(NETDEV_UP): eth0: link is not ready e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready PM: Writing back config space on device 0000:12:02.1 at offset b (was 164814e4, writing 1701028) PM: Writing back config space on device 0000:12:02.1 at offset 3 (was 804000, writing 804010) PM: Writing back config space on device 0000:12:02.1 at offset 2 (was 2000000, writing 2000010) PM: Writing back config space on device 0000:12:02.1 at offset 1 (was 2b00000, writing 2b00106) ADDRCONF(NETDEV_UP): eth3: link is not ready tg3: eth3: Link is up at 100 Mbps, full duplex. tg3: eth3: Flow control is on for TX and on for RX. ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready eth0: no IPv6 routers present Bluetooth: Core ver 2.10 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.8 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: HIDP (Human Interface Emulation) ver 1.1 eth3: no IPv6 routers present [drm] Initialized drm 1.0.1 20051102 ACPI: PCI Interrupt 0000:16:00.0[A] -> GSI 16 (level, low) -> IRQ 169 [drm] Initialized radeon 1.25.0 20060524 on minor 0 mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining [drm] Setting GART location based on new memory map [drm] writeback test succeeded in 2 usecs -------------- next part -------------- Linux version 2.6.18-1.2798.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 15:11:19 EDT 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000f553f000 (usable) 3197MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active On node 0 totalpages: 1004863 DMA zone: 186366 pages, LIFO batch:31 HighMem zone: 818497 pages, LIFO batch:31 found SMP MP-table at 000fe710 DMI 2.3 present. ACPI: RSDP (v000 DELL ) @ 0x000fcd80 ACPI: RSDT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fcd94 ACPI: FADT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fce14 ACPI: MADT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fce88 ACPI: SPCR (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fcfe4 ACPI: HPET (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd034 ACPI: MCFG (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd06c ACPI: SRAT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000a) @ 0x000fd0a8 ACPI: DSDT (v001 DELL PE68x0 0x00000001 MSFT 0x0100000e) @ 0x00000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x08] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x0e] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x09] enabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x0f] enabled) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0c] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x0a] disabled) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x06] disabled) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0d] disabled) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x05] disabled) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0b] disabled) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x03] disabled) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x07] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x01] address[0xfec85000] gsi_base[32]) IOAPIC[1]: apic_id 1, version 32, address 0xfec85000, GSI 32-55 ACPI: IOAPIC (id[0x02] address[0xfec85800] gsi_base[64]) IOAPIC[2]: apic_id 2, version 32, address 0xfec85800, GSI 64-87 ACPI: IOAPIC (id[0x03] address[0xfec86000] gsi_base[96]) IOAPIC[3]: apic_id 3, version 32, address 0xfec86000, GSI 96-119 ACPI: IOAPIC (id[0x04] address[0xfec86800] gsi_base[128]) IOAPIC[4]: apic_id 4, version 32, address 0xfec86800, GSI 128-151 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 5 I/O APICs Using ACPI (MADT) for SMP configuration information Built 1 zonelists. Total pages: 1004863 Kernel command line: ro root=/dev/VG_xen/LV_dom0 rhgb quiet Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c078a000 soft=c076a000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3158.954 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB enabled: Aperture: 64 megabytes Kernel range: 0x00000000c33f2000 - 0x00000000c73f2000 vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000 Memory: 3896848k/4019452k available (2097k kernel code, 113308k reserved, 840k data, 180k init, 3273988k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 7900.77 BogoMIPS (lpj=15801547) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebd3f1 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: After vendor identify, caps: bfebd3f1 20100000 00000000 00000000 0000659d 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: After all inits, caps: bfebd3f1 20100000 00000000 00000180 0000659d 00000000 00000000 Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code ACPI: Core revision 20060707 CPU 1 irqstacks, hard=c078b000 soft=c076b000 CPU 2 irqstacks, hard=c078c000 soft=c076c000 CPU 3 irqstacks, hard=c078d000 soft=c076d000 ENABLING IO-APIC IRQs SMP alternatives: switching to SMP code Initializing CPU#1 Initializing CPU#2 Brought up 4 CPUs sizeof(vma)=88 bytes sizeof(page)=32 bytes Initializing CPU#3 sizeof(inode)=424 bytes sizeof(dentry)=148 bytes sizeof(ext3inode)=600 bytes sizeof(buffer_head)=52 bytes sizeof(skbuff)=172 bytes sizeof(task_struct)=1392 bytes migration_cost=721 checking if image is initramfs... it is Freeing initrd memory: 5227k freed Grant table initialized NET: Registered protocol family 16 ACPI: bus type pci registered PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. PCI: Using configuration type 1 Setting up standard PCI resources Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: Device [M4] status [0000000c]: functional but not present; setting present ACPI: Device [M2] status [0000000c]: functional but not present; setting present ACPI: Device [M5] status [0000000c]: functional but not present; setting present ACPI: Device [M3] status [0000000c]: functional but not present; setting present ACPI: Device [M1] status [0000000c]: functional but not present; setting present ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0880-08bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 PCI: PXH quirk detected, disabling MSI for SHPC device PCI: PXH quirk detected, disabling MSI for SHPC device Boot video device is 0000:16:00.0 PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI.DOBA._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PAHI.DOBB._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.PXA0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.PXA2._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCHI._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PDLO._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PICH._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 12 devices xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: 00:07: ioport range 0x800-0x87f could not be reserved pnp: 00:07: ioport range 0x880-0x8bf has been reserved pnp: 00:07: ioport range 0x8c0-0x8df has been reserved pnp: 00:07: ioport range 0xc00-0xc1f has been reserved pnp: 00:07: ioport range 0xc10-0xc1f has been reserved pnp: 00:07: ioport range 0xca0-0xca7 has been reserved pnp: 00:07: ioport range 0xca9-0xcab has been reserved pnp: 00:07: ioport range 0xcad-0xcaf has been reserved PCI: Bridge: 0000:00:01.0 IO window: e000-efff MEM window: dfe00000-dfefffff PREFETCH window: db000000-dbffffff PCI: Bridge: 0000:00:02.0 IO window: d000-dfff MEM window: dfd00000-dfdfffff PREFETCH window: da000000-daffffff PCI: Bridge: 0000:00:03.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:04.0 IO window: c000-cfff MEM window: dfc00000-dfcfffff PREFETCH window: d9000000-d9ffffff PCI: Bridge: 0000:00:05.0 IO window: b000-bfff MEM window: dfb00000-dfbfffff PREFETCH window: d8000000-d8ffffff PCI: Bridge: 0000:0e:00.0 IO window: disabled. MEM window: dfa00000-dfafffff PREFETCH window: dc100000-dc1fffff PCI: Bridge: 0000:0e:00.2 IO window: a000-afff MEM window: df800000-df9fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:06.0 IO window: 9000-afff MEM window: df600000-dfafffff PREFETCH window: dc100000-dc1fffff PCI: Bridge: 0000:13:00.0 IO window: disabled. MEM window: df400000-df5fffff PREFETCH window: dc000000-dc0fffff PCI: Bridge: 0000:13:00.2 IO window: 8000-8fff MEM window: df200000-df3fffff PREFETCH window: df100000-df1fffff PCI: Bridge: 0000:00:07.0 IO window: 8000-8fff MEM window: df100000-df5fffff PREFETCH window: dc000000-dc0fffff PCI: Bridge: 0000:00:1e.0 IO window: 7000-7fff MEM window: def00000-df0fffff PREFETCH window: d0000000-d7ffffff PCI: Setting latency timer of device 0000:00:01.0 to 64 PCI: Setting latency timer of device 0000:00:02.0 to 64 PCI: Setting latency timer of device 0000:00:03.0 to 64 PCI: Setting latency timer of device 0000:00:04.0 to 64 PCI: Setting latency timer of device 0000:00:05.0 to 64 PCI: Setting latency timer of device 0000:00:06.0 to 64 ACPI: PCI Interrupt 0000:0e:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:0e:00.0 to 64 PCI: Setting latency timer of device 0000:0e:00.2 to 64 PCI: Setting latency timer of device 0000:00:07.0 to 64 PCI: Setting latency timer of device 0000:13:00.0 to 64 PCI: Setting latency timer of device 0000:13:00.2 to 64 PCI: Setting latency timer of device 0000:00:1e.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 9, 2621440 bytes) TCP bind hash table entries: 65536 (order: 8, 1310720 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1163415423.476:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 8BDC589434DBC709 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) PCI: Setting latency timer of device 0000:00:01.0 to 64 pcie_portdrv_probe->Dev[2601:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:01.0:pcie00] Allocate Port Service[0000:00:01.0:pcie02] PCI: Setting latency timer of device 0000:00:02.0 to 64 pcie_portdrv_probe->Dev[2608:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:02.0:pcie00] Allocate Port Service[0000:00:02.0:pcie02] PCI: Setting latency timer of device 0000:00:03.0 to 64 pcie_portdrv_probe->Dev[2603:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:03.0:pcie00] PCI: Setting latency timer of device 0000:00:04.0 to 64 pcie_portdrv_probe->Dev[2604:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:04.0:pcie00] Allocate Port Service[0000:00:04.0:pcie02] PCI: Setting latency timer of device 0000:00:05.0 to 64 pcie_portdrv_probe->Dev[2605:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:05.0:pcie00] Allocate Port Service[0000:00:05.0:pcie02] PCI: Setting latency timer of device 0000:00:06.0 to 64 pcie_portdrv_probe->Dev[2606:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:06.0:pcie00] PCI: Setting latency timer of device 0000:00:07.0 to 64 pcie_portdrv_probe->Dev[2607:8086] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:07.0:pcie00] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x1 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x2 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x3 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x4 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x5 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x6 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x7 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x8 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x9 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xa ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xb ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xc ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xd ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xe ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0xf ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x10 Real Time Clock Driver v1.12ac hpet_acpi_add: no address or irqs in _CRS Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as ttyS0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH5: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: Unable to derive IRQ for device 0000:00:1f.1 ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI ICH5: chipset revision 2 ICH5: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: TEAC CD-ROM CD-224E, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... Probing IDE interface ide1... ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 356k USB Universal Host Controller Interface driver v3.0 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 16, io base 0x00006ce0 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 17, io base 0x00006cc0 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 18, io base 0x00006ca0 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:1d.7: debug port 1 PCI: cache line size of 128 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: irq 19, io mem 0xdff00000 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) SCSI subsystem initialized megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006) megaraid: probe new device 0x1000:0x1960:0x1028:0x0518: bus 15:slot 2:func 0 ACPI: PCI Interrupt 0000:0f:02.0[A] -> GSI 32 (level, low) -> IRQ 20 megaraid: fw version:[352B] bios version:[1.10] megaraid: cluster firmware, initiator ID: 6 scsi0 : LSI Logic MegaRAID driver scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices usb 4-3: new high speed USB device using ehci_hcd and address 2 usb 4-3: configuration #1 chosen from 1 choice hub 4-3:1.0: USB hub found hub 4-3:1.0: 2 ports detected usb 3-1: new low speed USB device using uhci_hcd and address 2 usb 3-1: configuration #1 chosen from 1 choice input: ATEN ATEN Composite as /class/input/input0 input: USB HID v1.10 Keyboard [ATEN ATEN Composite] on usb-0000:00:1d.2-1 input: ATEN ATEN Composite as /class/input/input1 input: USB HID v1.10 Mouse [ATEN ATEN Composite] on usb-0000:00:1d.2-1 scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices Vendor: DELL Model: PV22XS Rev: E.19 Type: Processor ANSI SCSI revision: 03 scsi[0]: scanning scsi channel 2 [virtual] for logical drives megaraid: probe new device 0x1028:0x0013:0x1028:0x0170: bus 20:slot 14:func 0 ACPI: PCI Interrupt 0000:14:0e.0[A] -> GSI 110 (level, low) -> IRQ 21 megaraid: fw version:[522A] bios version:[H430] scsi1 : LSI Logic MegaRAID driver scsi[1]: scanning scsi channel 0 [Phy 0] for non-raid devices Vendor: PE/PV Model: 1x5 SCSI BP Rev: 1.0 Type: Processor ANSI SCSI revision: 02 scsi[1]: scanning scsi channel 1 [Phy 1] for non-raid devices scsi[1]: scanning scsi channel 2 [virtual] for logical drives Vendor: MegaRAID Model: LD 0 RAID0 139G Rev: 522A Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 286515200 512-byte hdwr sectors (146696 MB) sda: Write Protect is off sda: Mode Sense: 00 00 00 00 sda: asking for cache data failed sda: assuming drive cache: write through SCSI device sda: 286515200 512-byte hdwr sectors (146696 MB) sda: Write Protect is off sda: Mode Sense: 00 00 00 00 sda: asking for cache data failed sda: assuming drive cache: write through sda: sda1 sda2 sda3 sd 1:2:0:0: Attached scsi disk sda ACPI: PCI Interrupt 0000:15:07.0[A] -> GSI 134 (level, low) -> IRQ 22 scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ACPI: PCI Interrupt 0000:15:07.1[B] -> GSI 135 (level, low) -> IRQ 23 scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel at redhat.com kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1163415477.255:2): selinux=0 auid=4294967295 hda: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. ACPI: PCI Interrupt 0000:15:06.0[A] -> GSI 132 (level, low) -> IRQ 24 e1000: 0000:15:06.0: e1000_probe: (PCI:66MHz:64-bit) 00:0e:0c:85:c9:35 tg3.c:v3.65 (August 07, 2006) ACPI: PCI Interrupt 0000:12:02.0[A] -> GSI 64 (level, low) -> IRQ 25 eth0: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:22:74:2e:4f eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] Split[0] WireSpeed[1] TSOcap[0] eth0: dma_rwctrl[769f4000] dma_mask[64-bit] ACPI: PCI Interrupt 0000:12:02.1[B] -> GSI 65 (level, low) -> IRQ 26 e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection Intel 82802 RNG detected eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:22:74:2e:50 eth2: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth2: dma_rwctrl[769f4000] dma_mask[64-bit] input: PC Speaker as /class/input/input2 scsi 0:1:15:0: Attached scsi generic sg0 type 3 scsi 1:0:6:0: Attached scsi generic sg1 type 3 sd 1:2:0:0: Attached scsi generic sg2 type 0 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 lp: driver loaded but no devices found ACPI: Power Button (FF) [PWRF] ibm_acpi: ec object not found md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.4 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 2097144k swap on /dev/VG_xen/LV_swap. Priority:-1 extents:1 across:2097144k NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead. ADDRCONF(NETDEV_UP): eth0: link is not ready e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready PM: Writing back config space on device 0000:12:02.1 at offset b (was 164814e4, writing 1701028) PM: Writing back config space on device 0000:12:02.1 at offset 3 (was 804000, writing 804010) PM: Writing back config space on device 0000:12:02.1 at offset 2 (was 2000000, writing 2000010) PM: Writing back config space on device 0000:12:02.1 at offset 1 (was 2b00000, writing 2b00106) ADDRCONF(NETDEV_UP): eth3: link is not ready tg3: eth3: Link is up at 100 Mbps, full duplex. tg3: eth3: Flow control is on for TX and on for RX. ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready eth0: no IPv6 routers present Bluetooth: Core ver 2.10 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.8 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: HIDP (Human Interface Emulation) ver 1.1 eth3: no IPv6 routers present Bridge firewalling registered PM: Writing back config space on device 0000:12:02.1 at offset b (was 164814e4, writing 1701028) PM: Writing back config space on device 0000:12:02.1 at offset 3 (was 804000, writing 804010) PM: Writing back config space on device 0000:12:02.1 at offset 2 (was 2000000, writing 2000010) PM: Writing back config space on device 0000:12:02.1 at offset 1 (was 2b00000, writing 2b00106) device vif0.3 entered promiscuous mode audit(1163415514.347:3): dev=vif0.3 prom=256 old_prom=0 auid=4294967295 xenbr3: port 1(vif0.3) entering learning state xenbr3: topology change detected, propagating xenbr3: port 1(vif0.3) entering forwarding state PM: Writing back config space on device 0000:12:02.1 at offset b (was 164814e4, writing 1701028) PM: Writing back config space on device 0000:12:02.1 at offset 3 (was 804000, writing 804010) PM: Writing back config space on device 0000:12:02.1 at offset 2 (was 2000000, writing 2000010) PM: Writing back config space on device 0000:12:02.1 at offset 1 (was 2b00000, writing 2b00106) ADDRCONF(NETDEV_UP): peth3: link is not ready tg3: peth3: Link is up at 100 Mbps, full duplex. tg3: peth3: Flow control is on for TX and on for RX. ADDRCONF(NETDEV_CHANGE): peth3: link becomes ready device peth3 entered promiscuous mode audit(1163415516.507:4): dev=peth3 prom=256 old_prom=0 auid=4294967295 xenbr3: port 2(peth3) entering learning state xenbr3: topology change detected, propagating xenbr3: port 2(peth3) entering forwarding state eth3: no IPv6 routers present [drm] Initialized drm 1.0.1 20051102 ACPI: PCI Interrupt 0000:16:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [drm] Initialized radeon 1.25.0 20060524 on minor 0 [drm] Setting GART location based on new memory map [drm] writeback test failed From parsley at linuxjedi.org Mon Nov 13 11:58:09 2006 From: parsley at linuxjedi.org (David Parsley) Date: Mon, 13 Nov 2006 06:58:09 -0500 Subject: [Fedora-xen] Win Xp 32 bit as guest in In-Reply-To: <4557654D.80206@gmail.com> References: <4557654D.80206@gmail.com> Message-ID: <6b4bb8650611130358q5bb670a1h633ec40d6f4f5d03@mail.gmail.com> Hi Denis, On 11/12/06, Denis Forveille wrote: > Q: > - is it possible to run an instance of Win XP SP2 32bits as a guest on a > x86_64 FC6 fully updated dom0? (CPU = AMD x2 4600 with pacifica...) > > I successfully installed Win XP in an lvm logical volume. Everything > worked fine and at the end, I got the request from XP asking to remove > the CD and reboot... > Then, when I try to start the guest (after changing the line from boot=d > to boot=c in the config file), the only thing I see is a black screen. > (the windows resize itself and then a black screen...) > "xm top" shows that the guest consumes 0% CPU... > I think I've tried almost every combination of parameters in the config > files (pae, acpi,sdl...) during installation and after... > Also, I've seen that others have post similar problems in this forum, > but none of them have answers/workarounds to my problem. > > Does anyone succeeded in running such a combination (ie XP SP2 32 bits > in a 64bit FC6)? > Or maybe the problems comes from the fcat that I installed windows in an > lvm instead of in a file? > Thx in advance I had this problem, too - the solution was re-installing WinXP, and, when the installer asks you to press 'F6' for addtional drivers, press 'F5' instead. Then select 'Standard PC ...' My XP VM runs in either FC6 32 or FC6 64, pretty well. Hopefully future versions of Xen won't require this workaround. Regards, David -- David L. Parsley Linux Systems Engineer, James Madison University "If I have seen further, it is by standing on ye shoulders of giants" - Isaac Newton From jean-marc.pouchoulon at ac-montpellier.fr Mon Nov 13 12:19:45 2006 From: jean-marc.pouchoulon at ac-montpellier.fr (jean-marc pouchoulon) Date: Mon, 13 Nov 2006 13:19:45 +0100 Subject: [Fedora-xen] How to install Redhat Entreprise V3 guest on fedora core 6 ? Message-ID: <455862E1.8050605@ac-montpellier.fr> Hi , I want to install Redhat Entreprise V3 as a guest in a fedora core 6. What is the best way to do that ? I suppose xenguest-install won't work.... thanks for any links , howto.... Jmp From berrange at redhat.com Mon Nov 13 13:55:26 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 13 Nov 2006 13:55:26 +0000 Subject: [Fedora-xen] How to install Redhat Entreprise V3 guest on fedora core 6 ? In-Reply-To: <455862E1.8050605@ac-montpellier.fr> References: <455862E1.8050605@ac-montpellier.fr> Message-ID: <20061113135526.GA26148@redhat.com> On Mon, Nov 13, 2006 at 01:19:45PM +0100, jean-marc pouchoulon wrote: > Hi , > I want to install Redhat Entreprise V3 as a guest in a fedora core 6. > What is the best way to do that ? > > I suppose xenguest-install won't work.... > > thanks for any links , howto.... You'll have to have a CPU with virtualization extensions, eg Intel VT, or AMD-V cpus. You then ought to be able to run RHEL-3 in fully-virt mode. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From kzak at redhat.com Mon Nov 13 14:02:43 2006 From: kzak at redhat.com (Karel Zak) Date: Mon, 13 Nov 2006 15:02:43 +0100 Subject: [Fedora-xen] announce: gnome-applet-vm 0.1.2 Message-ID: <20061113140243.GQ4324@petra.dvoda.cz> I have just pushed out a new 0.1.2 version of the VM Applet. The changes/features are: - removed dependence on dbus libs - improved collaboration with virt-manager (you have use the latest version of virt-manager) - fixed few minor bugs Web page: http://people.redhat.com/kzak/gnome-applet-vm/ TODO for next release(s): - finalize support for more hypervisors (the applet should be able to monitor cluster of VM machines on more hosts in same time) - alarm on important changes (domain create, destrory, ...) - keep track of important changes I welcome your feedback! Send me your comments, ideas for enhancements or bug reports. Karel -- Karel Zak From rodger at thompsonprint.com Mon Nov 13 15:33:06 2006 From: rodger at thompsonprint.com (Rodger Haynes) Date: Mon, 13 Nov 2006 10:33:06 -0500 Subject: [Fedora-xen] No samba login to guest Message-ID: <45589032.8020103@thompsonprint.com> I'm a newbie trying to set up Xen. I have a guest domain running fine, and can connect from the guest domain via samba to dom0 and all the other network hosts external to the xen machine. I can connect from the network to dom0. I can 'see' the guest in windows networking, but can't connect to it. I can ping it fine. It would seem to be a rights issue. The guest setup is the same as on dom0. I've double checked the samba setup and can't find anything wrong, but I'm obviously missing something, probably very basic. Any help would be greatly appreciated. -- Rodger Haynes Thompson Printing & Lithographing Paris, ON N3L 3K4 519-442-7804 x210 From shobha.ranganathan at intel.com Mon Nov 13 23:28:14 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Mon, 13 Nov 2006 15:28:14 -0800 Subject: [Fedora-xen] RE: No mouse and KB activity in FC5 guest OS in FC6 xen host setup Message-ID: I appreciate if somebody has any ideas/tips on this... Here is the configuration of unmodified guest FC5 in FC6 Xen host. I have a iMac running FC6 Xen in x86 mode and FC5 as unmodified guest I get a graphics for unmodified guest which allows me login. But then no mouse and keyboard is active after logging me into FC5 unmodified guest. What is wrong ? I also tried adding nographic=1 options and usb=1 and sdl=1. I always created it again. But absolutely no mouse/KB activity. Any tip/trick is greatly appreciated as I am not making forward progress.. # Automatically generated xen config file name = "xenbox_G1FC5" builder = "hvm" memory = "256" uuid = "e56c658f-a4f2-3c10-3bb1-93a1e519bd69" disk = [ 'file:/root/xenguest4,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:42:1c:1f' ] 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 apic=1 acpi=1 pae=1 nographic = 0 # don't use graphics serial='pty' # enable serial console Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha.ranganathan at intel.com Tue Nov 14 01:08:48 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Mon, 13 Nov 2006 17:08:48 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: I am trying to install unmodified guest FC5 in host Os FC6. I am using virt-manager and upon gathering all information, when I click finish, the GUI shows me "The console is currently unavailable". What is wrong ? xm list shows the guest as blocked. I see error messages in xend-debug.log and xend.log Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Nov 14 01:23:49 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 14 Nov 2006 01:23:49 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: References: Message-ID: <20061114012349.GA12336@redhat.com> On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > I am trying to install unmodified guest FC5 in host Os FC6. > > I am using virt-manager and upon gathering all information, when I click > finish, the GUI shows me "The console is currently unavailable". This basically means that virt-manager was unable to successfully connect to the VNC server which exports the guest framebuffer / console. Since you say this is with fully virt, it probably means that the qemu-dm process failed to startup correctly - since VNC itself rarely fails I imagine some other bit of the guest config broke - network / disk setup being most likely > > What is wrong ? xm list shows the guest as blocked. I see error messages > in xend-debug.log and xend.log What are the errors you see - they may well help diagnose the problem you are encountering ? Also check for /var/log/xen/qemu-dm*.log for info about the fully-virt device model startup Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Tue Nov 14 01:44:55 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Mon, 13 Nov 2006 17:44:55 -0800 Subject: [Fedora-xen] "KBD: unsupported int 16h function 03" -- is the keyboard in Intel Mac system not supported in FC6 Xen ? Message-ID: I am trying to install FC5 guest in FC6 host in x86 mode. I am using virt-manager to install fully virt guest. I get in "xm dmesg", that "KBD: unsupported int 16h function 03". Does this mean that my keyboard is not getting recognized properly ? Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha.ranganathan at intel.com Tue Nov 14 02:03:17 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Mon, 13 Nov 2006 18:03:17 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: I had a typo in my previous message. I see no errors in xend.log and xend-debug.log. But I do have qemu*log messages. For my last problem, I only see the following Domid: 2 Shared page at pfn:ffff, mfn:34cd5 Buffered io page at pfn:fffd, mfn:34cd7 Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Monday, November 13, 2006 5:24 PM To: Ranganathan, Shobha Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > I am trying to install unmodified guest FC5 in host Os FC6. > > I am using virt-manager and upon gathering all information, when I click > finish, the GUI shows me "The console is currently unavailable". This basically means that virt-manager was unable to successfully connect to the VNC server which exports the guest framebuffer / console. Since you say this is with fully virt, it probably means that the qemu-dm process failed to startup correctly - since VNC itself rarely fails I imagine some other bit of the guest config broke - network / disk setup being most likely > > What is wrong ? xm list shows the guest as blocked. I see error messages > in xend-debug.log and xend.log What are the errors you see - they may well help diagnose the problem you are encountering ? Also check for /var/log/xen/qemu-dm*.log for info about the fully-virt device model startup Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From denis.forveille at gmail.com Tue Nov 14 03:24:26 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Mon, 13 Nov 2006 22:24:26 -0500 Subject: [Fedora-xen] Win Xp 32 bit as guest in In-Reply-To: <6b4bb8650611130358q5bb670a1h633ec40d6f4f5d03@mail.gmail.com> References: <4557654D.80206@gmail.com> <6b4bb8650611130358q5bb670a1h633ec40d6f4f5d03@mail.gmail.com> Message-ID: <455936EA.6020007@gmail.com> Thanks for your answer, When I pressed F5, i saw the display you're talking about (choose between different hardware infrastructure). But as someone already mentioned in another post, I was unable to use the keyboard to make a selection. So I installed the qemu package (yum install qemu.x86_64) an then install XP SP2 with qemu with the following command (for documentation): qemu -cdrom /dev/dvd -m 512 -boot d -hda /dev/vg_domU/lv_windows There, I was able to use my keyboard to choose an architecture (after having pressed F5...). Ichoose "Standard PC" as you suggest. Whence windows has been installed (took a looong time), I can now start my guest with xen... I count 2 (minor?) bugs there: the bad architecture detection, and the incapacity to use the keyboard after pressing F5 on the "..preess F6.." screen Thanks very much for your help I now have to find a way to make my DVD Writer available to this win guest, but i read elsewhere that this is not possible, even with a full virtualized guest...it it? David Parsley wrote: > Hi Denis, > > On 11/12/06, Denis Forveille wrote: >> Q: >> - is it possible to run an instance of Win XP SP2 32bits as a guest on a >> x86_64 FC6 fully updated dom0? (CPU = AMD x2 4600 with pacifica...) >> >> I successfully installed Win XP in an lvm logical volume. Everything >> worked fine and at the end, I got the request from XP asking to remove >> the CD and reboot... >> Then, when I try to start the guest (after changing the line from boot=d >> to boot=c in the config file), the only thing I see is a black screen. >> (the windows resize itself and then a black screen...) >> "xm top" shows that the guest consumes 0% CPU... >> I think I've tried almost every combination of parameters in the config >> files (pae, acpi,sdl...) during installation and after... >> Also, I've seen that others have post similar problems in this forum, >> but none of them have answers/workarounds to my problem. >> >> Does anyone succeeded in running such a combination (ie XP SP2 32 bits >> in a 64bit FC6)? >> Or maybe the problems comes from the fcat that I installed windows in an >> lvm instead of in a file? >> Thx in advance > > I had this problem, too - the solution was re-installing WinXP, and, > when the installer asks you to press 'F6' for addtional drivers, press > 'F5' instead. Then select 'Standard PC ...' > > My XP VM runs in either FC6 32 or FC6 64, pretty well. Hopefully > future versions of Xen won't require this workaround. > > Regards, > David From berrange at redhat.com Tue Nov 14 04:03:45 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 14 Nov 2006 04:03:45 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: References: Message-ID: <20061114040345.GA23171@redhat.com> On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote: > I had a typo in my previous message. > > I see no errors in xend.log and xend-debug.log. Ok, that's good - can you see if there is a qemu-dm process running, eg ps -auxfww | grep qemu-dm > But I do have qemu*log messages. For my last problem, I only see the > following > Domid: 2 > Shared page at pfn:ffff, mfn:34cd5 > Buffered io page at pfn:fffd, mfn:34cd7 Looks reasonable. Can you see if there is a '' block in the XML when you run 'virsh dumpxml ' For the domain that you failed to get a console on. Also make sure that in the /etc/xen/ there is a 'vnc=1' config option. Finally, take a look at /root/.virt-manager/virt-manager.log to see if there's any errors reported. > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com] > Sent: Monday, November 13, 2006 5:24 PM > To: Ranganathan, Shobha > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > unavailable" in FC6 > > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > > I am trying to install unmodified guest FC5 in host Os FC6. > > > > I am using virt-manager and upon gathering all information, when I > click > > finish, the GUI shows me "The console is currently unavailable". > > This basically means that virt-manager was unable to successfully > connect > to the VNC server which exports the guest framebuffer / console. Since > you say this is with fully virt, it probably means that the qemu-dm > process > failed to startup correctly - since VNC itself rarely fails I imagine > some > other bit of the guest config broke - network / disk setup being most > likely > > > > > What is wrong ? xm list shows the guest as blocked. I see error > messages > > in xend-debug.log and xend.log > > What are the errors you see - they may well help diagnose the problem > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for > info about the fully-virt device model startup Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Tue Nov 14 18:53:59 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 10:53:59 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: Yes there is qemu-dm process running. I see a line in "virsh dumpxml xen_FC5G1" >From the log file of virt-manager I have DEBUG Graphics vnc://localhost:5902 ERROR Unable to activate console socket.error(111,'Connection refused') In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Monday, November 13, 2006 8:04 PM To: Ranganathan, Shobha Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote: > I had a typo in my previous message. > > I see no errors in xend.log and xend-debug.log. Ok, that's good - can you see if there is a qemu-dm process running, eg ps -auxfww | grep qemu-dm > But I do have qemu*log messages. For my last problem, I only see the > following > Domid: 2 > Shared page at pfn:ffff, mfn:34cd5 > Buffered io page at pfn:fffd, mfn:34cd7 Looks reasonable. Can you see if there is a '' block in the XML when you run 'virsh dumpxml ' For the domain that you failed to get a console on. Also make sure that in the /etc/xen/ there is a 'vnc=1' config option. Finally, take a look at /root/.virt-manager/virt-manager.log to see if there's any errors reported. > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com] > Sent: Monday, November 13, 2006 5:24 PM > To: Ranganathan, Shobha > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > unavailable" in FC6 > > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > > I am trying to install unmodified guest FC5 in host Os FC6. > > > > I am using virt-manager and upon gathering all information, when I > click > > finish, the GUI shows me "The console is currently unavailable". > > This basically means that virt-manager was unable to successfully > connect > to the VNC server which exports the guest framebuffer / console. Since > you say this is with fully virt, it probably means that the qemu-dm > process > failed to startup correctly - since VNC itself rarely fails I imagine > some > other bit of the guest config broke - network / disk setup being most > likely > > > > > What is wrong ? xm list shows the guest as blocked. I see error > messages > > in xend-debug.log and xend.log > > What are the errors you see - they may well help diagnose the problem > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for > info about the fully-virt device model startup Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From laurent.mylists at gmail.com Tue Nov 14 19:49:21 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Tue, 14 Nov 2006 20:49:21 +0100 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <20061114040345.GA23171@redhat.com> References: <20061114040345.GA23171@redhat.com> Message-ID: Hello, Actually, I have exactly the same problem with FC6 for some days now. Concerning Daniel's questions (for me) : - qemu process : ok - virsh dump : ok but why port=-1 ? - virt-manager log : Unable to activate console socket.gaierror (-2, 'Nom ou service inconnu') (detail is given below). What strange is, it is that everything worked well at beginning. I have not made system modifications or so. It's the third time that I have to install FC6. It would be really great if you have an idea about what is happening. Thanks for your help 2006/11/14, Daniel P. Berrange : > > On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote: > > I had a typo in my previous message. > > > > I see no errors in xend.log and xend-debug.log. > > Ok, that's good - can you see if there is a qemu-dm process running, > eg > > ps -auxfww | grep qemu-dm > > > But I do have qemu*log messages. For my last problem, I only see the > > following > > Domid: 2 > > Shared page at pfn:ffff, mfn:34cd5 > > Buffered io page at pfn:fffd, mfn:34cd7 > > Looks reasonable. Can you see if there is a '' block > in the XML when you run > > 'virsh dumpxml ' > > For the domain that you failed to get a console on. Also make sure that > in the /etc/xen/ there is a 'vnc=1' config option. Finally, > take a look at /root/.virt-manager/virt- manager.log to see if there's > any errors reported. > > > -----Original Message----- > > From: Daniel P. Berrange [mailto:berrange at redhat.com] > > Sent: Monday, November 13, 2006 5:24 PM > > To: Ranganathan, Shobha > > Cc: fedora-xen at redhat.com > > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > > unavailable" in FC6 > > > > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > > > I am trying to install unmodified guest FC5 in host Os FC6. > > > > > > I am using virt-manager and upon gathering all information, when I > > click > > > finish, the GUI shows me "The console is currently unavailable". > > > > This basically means that virt-manager was unable to successfully > > connect > > to the VNC server which exports the guest framebuffer / console. Since > > you say this is with fully virt, it probably means that the qemu-dm > > process > > failed to startup correctly - since VNC itself rarely fails I imagine > > some > > other bit of the guest config broke - network / disk setup being most > > likely > > > > > > > > What is wrong ? xm list shows the guest as blocked. I see error > > messages > > > in xend-debug.log and xend.log > > > > What are the errors you see - they may well help diagnose the problem > > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for > > info about the fully-virt device model startup > > Regards, > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=| > > -- > 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 laurent.mylists at gmail.com Tue Nov 14 20:44:45 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Tue, 14 Nov 2006 21:44:45 +0100 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: References: Message-ID: Hi, After a new check, it looks like I have exactly the same problem than your with the same logs. I found no solution for the moment as making a new FC6 installation. Best Regards 2006/11/14, Ranganathan, Shobha : > > Yes there is qemu-dm process running. > > I see a line in "virsh dumpxml xen_FC5G1" > > > >From the log file of virt-manager I have > > DEBUG Graphics vnc://localhost:5902 > ERROR Unable to activate console socket.error(111,'Connection refused') > > In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1. > > Regards > Shobha Ranganathan > "The significant challenges we face cannot be resolved at the same level > of thinking we were at when we created them." Albert Einstein > > > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com] > Sent: Monday, November 13, 2006 8:04 PM > To: Ranganathan, Shobha > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > unavailable" in FC6 > > On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote: > > I had a typo in my previous message. > > > > I see no errors in xend.log and xend-debug.log. > > Ok, that's good - can you see if there is a qemu-dm process running, > eg > > ps -auxfww | grep qemu-dm > > > But I do have qemu*log messages. For my last problem, I only see the > > following > > Domid: 2 > > Shared page at pfn:ffff, mfn:34cd5 > > Buffered io page at pfn:fffd, mfn:34cd7 > > Looks reasonable. Can you see if there is a '' block > in the XML when you run > > 'virsh dumpxml ' > > For the domain that you failed to get a console on. Also make sure that > in the /etc/xen/ there is a 'vnc=1' config option. Finally, > take a look at /root/.virt-manager/virt-manager.log to see if there's > any errors reported. > > > -----Original Message----- > > From: Daniel P. Berrange [mailto:berrange at redhat.com] > > Sent: Monday, November 13, 2006 5:24 PM > > To: Ranganathan, Shobha > > Cc: fedora-xen at redhat.com > > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > > unavailable" in FC6 > > > > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > > > I am trying to install unmodified guest FC5 in host Os FC6. > > > > > > I am using virt-manager and upon gathering all information, when I > > click > > > finish, the GUI shows me "The console is currently unavailable". > > > > This basically means that virt-manager was unable to successfully > > connect > > to the VNC server which exports the guest framebuffer / console. Since > > you say this is with fully virt, it probably means that the qemu-dm > > process > > failed to startup correctly - since VNC itself rarely fails I imagine > > some > > other bit of the guest config broke - network / disk setup being most > > likely > > > > > > > > What is wrong ? xm list shows the guest as blocked. I see error > > messages > > > in xend-debug.log and xend.log > > > > What are the errors you see - they may well help diagnose the problem > > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for > > info about the fully-virt device model startup > > Regards, > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 > 2496 -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > -=| > > -- > 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 shobha.ranganathan at intel.com Tue Nov 14 21:45:53 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 13:45:53 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: This means that this is FC6 specific. I have had successful installations on FC6 Test2 . Any suggestions/workarounds possible to install unmodified guest ? I am in dire need for a solution. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Laurent Flesch Sent: Tuesday, November 14, 2006 12:45 PM To: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 Hi, After a new check, it looks like I have exactly the same problem than your with the same logs. I found no solution for the moment as making a new FC6 installation. Best Regards 2006/11/14, Ranganathan, Shobha : Yes there is qemu-dm process running. I see a line in "virsh dumpxml xen_FC5G1" >From the log file of virt-manager I have DEBUG Graphics vnc://localhost:5902 ERROR Unable to activate console socket.error(111,'Connection refused') In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Monday, November 13, 2006 8:04 PM To: Ranganathan, Shobha Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote: > I had a typo in my previous message. > > I see no errors in xend.log and xend-debug.log. Ok, that's good - can you see if there is a qemu-dm process running, eg ps -auxfww | grep qemu-dm > But I do have qemu*log messages. For my last problem, I only see the > following > Domid: 2 > Shared page at pfn:ffff, mfn:34cd5 > Buffered io page at pfn:fffd, mfn:34cd7 Looks reasonable. Can you see if there is a '' block in the XML when you run 'virsh dumpxml ' For the domain that you failed to get a console on. Also make sure that in the /etc/xen/ there is a 'vnc=1' config option. Finally, take a look at /root/.virt-manager/virt-manager.log to see if there's any errors reported. > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com ] > Sent: Monday, November 13, 2006 5:24 PM > To: Ranganathan, Shobha > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] virt-manager gives "The console is currently > unavailable" in FC6 > > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote: > > I am trying to install unmodified guest FC5 in host Os FC6. > > > > I am using virt-manager and upon gathering all information, when I > click > > finish, the GUI shows me "The console is currently unavailable". > > This basically means that virt-manager was unable to successfully > connect > to the VNC server which exports the guest framebuffer / console. Since > you say this is with fully virt, it probably means that the qemu-dm > process > failed to startup correctly - since VNC itself rarely fails I imagine > some > other bit of the guest config broke - network / disk setup being most > likely > > > > > What is wrong ? xm list shows the guest as blocked. I see error > messages > > in xend-debug.log and xend.log > > What are the errors you see - they may well help diagnose the problem > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for > info about the fully-virt device model startup Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- 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 berrange at redhat.com Tue Nov 14 23:57:01 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 14 Nov 2006 23:57:01 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: References: Message-ID: <20061114235701.GC21142@redhat.com> On Tue, Nov 14, 2006 at 10:53:59AM -0800, Ranganathan, Shobha wrote: > Yes there is qemu-dm process running. Great. > I see a line in "virsh dumpxml xen_FC5G1" > > > From the log file of virt-manager I have > > DEBUG Graphics vnc://localhost:5902 > ERROR Unable to activate console socket.error(111,'Connection refused') Ok, that's a very odd situation - virsh is saying port 5900 is where the VNC server is (which sounds plausible), but virt-manager is trying to connect to 5902 (which sounds like old, hardcoded port behaviour). Could you tell me what version of kernel-xen, xen, libvirt & virt-manager RPMs you have installed in the host. If you close the console window & re-open it, I assume it still fails to connect again, with same error message in the logs ? > In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1. Ok, that's good - so port 5900 is definitely the desired port. Oh, are you running 'virsh' and 'virt-manager' as root, or a normal user ? Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Wed Nov 15 00:01:40 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 15 Nov 2006 00:01:40 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: References: <20061114040345.GA23171@redhat.com> Message-ID: <20061115000140.GD21142@redhat.com> On Tue, Nov 14, 2006 at 08:49:21PM +0100, Laurent Flesch wrote: > Hello, > > Actually, I have exactly the same problem with FC6 for some days now. > Concerning Daniel's questions (for me) : > > - qemu process : ok > - virsh dump : ok but why port=-1 ? > Hmm, that's very bad - that should never happen ! I'll have to investigate just what scenario could cause that to happen. > - virt-manager log : > Unable to activate console socket.gaierror (-2, 'Nom ou service inconnu') > (detail is given below). > > What strange is, it is that everything worked well at beginning. > I have not made system modifications or so. It's the third time that I have > to install FC6. Could you also let me know what kernel-xen, virt-manager, libvirt and xen RPM version you have. And whether its 32 or 64 bit ? Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From eswar.m.eduri at intel.com Wed Nov 15 00:06:58 2006 From: eswar.m.eduri at intel.com (Eduri, Eswar M) Date: Tue, 14 Nov 2006 16:06:58 -0800 Subject: [Fedora-xen] Building and booting Dom0 in FC6 Message-ID: <5461330FA59EDB46BE9AB8AAF2C431AD023915AA@scsmsx412.amr.corp.intel.com> Hello there, I am trying to build Xen0 image based on FC6 release. I have copied kernel-2.6.18-i686-xen.config into a local directory and was able to build Linux kernel with this configuration file. This gave me vmlinuz file ready for Xen0 execution. Now, I believe I would need an initrd to go with this image so that Xen0 boots up. What should I do? I don't want to run 'make install module_install' and overwrite my existing configuration. This seems like basic stuff - is there some obvious documentation I am missing I should refer to? Thanks a lot for your help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha.ranganathan at intel.com Wed Nov 15 00:30:51 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 16:30:51 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: I built Xen the way the README specifies. So although FC6 is 2.6.18, I get it built against 2.6.16.29 So uname -a yields 2.6.16.29-xen. I have kernel-xen version as this My xen version is xen-3.0.3-rc3 src rpm that comes with FC6. I installed libvirt-0.1.7-2.i386.rpm (again this comes with FC6). Virt-manager version is 0.2.3 from the About button of the GUI. I always login as root in these machines. When I tried it again this time , I still get same results. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Tuesday, November 14, 2006 3:57 PM To: Ranganathan, Shobha Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 On Tue, Nov 14, 2006 at 10:53:59AM -0800, Ranganathan, Shobha wrote: > Yes there is qemu-dm process running. Great. > I see a line in "virsh dumpxml xen_FC5G1" > > > From the log file of virt-manager I have > > DEBUG Graphics vnc://localhost:5902 > ERROR Unable to activate console socket.error(111,'Connection refused') Ok, that's a very odd situation - virsh is saying port 5900 is where the VNC server is (which sounds plausible), but virt-manager is trying to connect to 5902 (which sounds like old, hardcoded port behaviour). Could you tell me what version of kernel-xen, xen, libvirt & virt-manager RPMs you have installed in the host. If you close the console window & re-open it, I assume it still fails to connect again, with same error message in the logs ? > In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1. Ok, that's good - so port 5900 is definitely the desired port. Oh, are you running 'virsh' and 'virt-manager' as root, or a normal user ? Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at xelerance.com Wed Nov 15 00:38:00 2006 From: paul at xelerance.com (Paul Wouters) Date: Wed, 15 Nov 2006 01:38:00 +0100 (CET) Subject: [Fedora-xen] Building and booting Dom0 in FC6 In-Reply-To: <5461330FA59EDB46BE9AB8AAF2C431AD023915AA@scsmsx412.amr.corp.intel.com> References: <5461330FA59EDB46BE9AB8AAF2C431AD023915AA@scsmsx412.amr.corp.intel.com> Message-ID: On Tue, 14 Nov 2006, Eduri, Eswar M wrote: > I am trying to build Xen0 image based on FC6 release. I have copied > kernel-2.6.18-i686-xen.config into a local directory and was able to > build Linux kernel with this configuration file. This gave me vmlinuz > file ready for Xen0 execution. > > Now, I believe I would need an initrd to go with this image so that Xen0 > boots up. What should I do? I don't want to run 'make install > module_install' and overwrite my existing configuration. mkinitrd /boot/initrd-2.6.18-i686-xen.img 2.6.18-i686-xen Use whatever your linux/Makefile gives as version eg 2.6.18-1.2198 Somewhere on the redhat wiki probably. Paul From junk at remcc.org Wed Nov 15 01:23:20 2006 From: junk at remcc.org (Robert Thiem) Date: Wed, 15 Nov 2006 11:23:20 +1000 (EST) Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <20061114214608.A6F8E7304B@hormel.redhat.com> References: <20061114214608.A6F8E7304B@hormel.redhat.com> Message-ID: <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> When first setting up FC6 I had an issue where I could start an FC6 Xen guest install but couldn't connect with VNC. I don't know if it's the same (I can't remember the exact messages I was getting), but it ended up being that "localhost" wouldn't resolve to an IPv4 address. This was due to a nasty combination of anaconda putting IPv4 and v6 entries in /etc/hosts and system-config-network trimming the "extra" v4 entry when run. Anyway I'd suggest: - Check that you can ping localhost - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 (and not with ::1) - Run "netstat -antp" to see what ports programs are listening on Regards, Robert Thiem From berrange at redhat.com Wed Nov 15 01:27:49 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 15 Nov 2006 01:27:49 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> References: <20061114214608.A6F8E7304B@hormel.redhat.com> <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> Message-ID: <20061115012749.GF21142@redhat.com> On Wed, Nov 15, 2006 at 11:23:20AM +1000, Robert Thiem wrote: > When first setting up FC6 I had an issue where I could start an FC6 Xen > guest install but couldn't connect with VNC. > > I don't know if it's the same (I can't remember the exact messages I was > getting), but it ended up being that "localhost" wouldn't resolve to an > IPv4 address. This was due to a nasty combination of anaconda putting IPv4 > and v6 entries in /etc/hosts and system-config-network trimming the > "extra" v4 entry when run. > > Anyway I'd suggest: > - Check that you can ping localhost > - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 > (and not with ::1) > - Run "netstat -antp" to see what ports programs are listening on Ahhh, that would certainly make sense - virt-manager explicitly connects to 'localhost' when opening the VNC connection. Since the VNC server doesn't support IPv6, I think it'd be fairly safe for me to switch virt-manager to explicitly use '127.0.0.1' which would eliminate this particularly /etc/hosts issue. Thanks for the info about the issue. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Wed Nov 15 01:45:17 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 17:45:17 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 Message-ID: Anyway I'd suggest: - Check that you can ping localhost I could ping the localhost - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 (and not with ::1) I have two entries one with 127.0.0.1 and ::1. I went ahead and commented out ::1 entry - Run "netstat -antp" to see what ports programs are listening on I see various services on IP address of the local host 172.xx.xx.xx and 127.0.0.1 and ::22 and ::1 and 0.0.0.0 I see sshd, cupsd and hpiod running with local address as ::22, ::1 and 0.0.0.0. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Daniel P. Berrange Sent: Tuesday, November 14, 2006 5:28 PM To: Robert Thiem Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 On Wed, Nov 15, 2006 at 11:23:20AM +1000, Robert Thiem wrote: > When first setting up FC6 I had an issue where I could start an FC6 Xen > guest install but couldn't connect with VNC. > > I don't know if it's the same (I can't remember the exact messages I was > getting), but it ended up being that "localhost" wouldn't resolve to an > IPv4 address. This was due to a nasty combination of anaconda putting IPv4 > and v6 entries in /etc/hosts and system-config-network trimming the > "extra" v4 entry when run. > > Anyway I'd suggest: > - Check that you can ping localhost > - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 > (and not with ::1) > - Run "netstat -antp" to see what ports programs are listening on Ahhh, that would certainly make sense - virt-manager explicitly connects to 'localhost' when opening the VNC connection. Since the VNC server doesn't support IPv6, I think it'd be fairly safe for me to switch virt-manager to explicitly use '127.0.0.1' which would eliminate this particularly /etc/hosts issue. Thanks for the info about the issue. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From berrange at redhat.com Wed Nov 15 01:51:25 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 15 Nov 2006 01:51:25 +0000 Subject: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 In-Reply-To: References: Message-ID: <20061115015125.GG21142@redhat.com> On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote: > Anyway I'd suggest: > - Check that you can ping localhost > I could ping the localhost > > - Check there's a localhost entry in /etc/hosts associated with > 127.0.0.1 > (and not with ::1) > I have two entries one with 127.0.0.1 and ::1. I went ahead and > commented out ::1 entry > - Run "netstat -antp" to see what ports programs are listening on > I see various services on IP address of the local host 172.xx.xx.xx and > 127.0.0.1 and ::22 and ::1 and 0.0.0.0 > > I see sshd, cupsd and hpiod running with local address as ::22, ::1 and > 0.0.0.0. For fully-virt / HVM guests you should see a 'qemu-dm' process listening on the port associated with VNC (something around 5900+). If you don't then this is the primary problem to address - the qemu-dm*log file may be useful. Also grabbing the command line for qemu-dm active process should indicate what port it tried to start on. In my case: # virsh dumpxml rhel4i386 | grep graphics # ps -axuww | grep qemu root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00 /usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4 -acpi -domain-name rhel4i386 -net nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4005/qemu-dm # virsh dumpxml rhel4i386 | grep graphics Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Wed Nov 15 02:08:14 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 18:08:14 -0800 Subject: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 Message-ID: # virsh dumpxml xenbox_G1FC5 | grep graphics # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4517/qemu-dm # ps -axuww | grep qemu root 4517 0.3 0.4 32452 3324 ? Sl 17:53 0:01 /usr/lib64/xen/bin/qemu-dm -d 1 -m 256 -boot d -acpi -domain-name xenbox_G1FC5 -net nic,vlan=1,macaddr=00:16:3e:4a:0d:50,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 I did try commenting the ::1 entry in /etc/hosts file. I still see this issue. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Tuesday, November 14, 2006 5:51 PM To: Ranganathan, Shobha Cc: Robert Thiem; fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote: > Anyway I'd suggest: > - Check that you can ping localhost > I could ping the localhost > > - Check there's a localhost entry in /etc/hosts associated with > 127.0.0.1 > (and not with ::1) > I have two entries one with 127.0.0.1 and ::1. I went ahead and > commented out ::1 entry > - Run "netstat -antp" to see what ports programs are listening on > I see various services on IP address of the local host 172.xx.xx.xx and > 127.0.0.1 and ::22 and ::1 and 0.0.0.0 > > I see sshd, cupsd and hpiod running with local address as ::22, ::1 and > 0.0.0.0. For fully-virt / HVM guests you should see a 'qemu-dm' process listening on the port associated with VNC (something around 5900+). If you don't then this is the primary problem to address - the qemu-dm*log file may be useful. Also grabbing the command line for qemu-dm active process should indicate what port it tried to start on. In my case: # virsh dumpxml rhel4i386 | grep graphics # ps -axuww | grep qemu root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00 /usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4 -acpi -domain-name rhel4i386 -net nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4005/qemu-dm # virsh dumpxml rhel4i386 | grep graphics Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Wed Nov 15 02:13:45 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Tue, 14 Nov 2006 18:13:45 -0800 Subject: [Fedora-xen] virt-manager gives "The console iscurrentlyunavailable" in FC6 Message-ID: Also the qemu*log files do not any errors for my latest run. One of the previous runs I had "False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 Thanks Dan for all your help.. I pretty much have a valid configuration as you have down here though... -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ranganathan, Shobha Sent: Tuesday, November 14, 2006 6:08 PM To: Daniel P. Berrange Cc: fedora-xen at redhat.com Subject: RE: [Fedora-xen] virt-manager gives "The console iscurrentlyunavailable" in FC6 # virsh dumpxml xenbox_G1FC5 | grep graphics # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4517/qemu-dm # ps -axuww | grep qemu root 4517 0.3 0.4 32452 3324 ? Sl 17:53 0:01 /usr/lib64/xen/bin/qemu-dm -d 1 -m 256 -boot d -acpi -domain-name xenbox_G1FC5 -net nic,vlan=1,macaddr=00:16:3e:4a:0d:50,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 I did try commenting the ::1 entry in /etc/hosts file. I still see this issue. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Tuesday, November 14, 2006 5:51 PM To: Ranganathan, Shobha Cc: Robert Thiem; fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote: > Anyway I'd suggest: > - Check that you can ping localhost > I could ping the localhost > > - Check there's a localhost entry in /etc/hosts associated with > 127.0.0.1 > (and not with ::1) > I have two entries one with 127.0.0.1 and ::1. I went ahead and > commented out ::1 entry > - Run "netstat -antp" to see what ports programs are listening on > I see various services on IP address of the local host 172.xx.xx.xx and > 127.0.0.1 and ::22 and ::1 and 0.0.0.0 > > I see sshd, cupsd and hpiod running with local address as ::22, ::1 and > 0.0.0.0. For fully-virt / HVM guests you should see a 'qemu-dm' process listening on the port associated with VNC (something around 5900+). If you don't then this is the primary problem to address - the qemu-dm*log file may be useful. Also grabbing the command line for qemu-dm active process should indicate what port it tried to start on. In my case: # virsh dumpxml rhel4i386 | grep graphics # ps -axuww | grep qemu root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00 /usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4 -acpi -domain-name rhel4i386 -net nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4005/qemu-dm # virsh dumpxml rhel4i386 | grep graphics Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From laurent.mylists at gmail.com Wed Nov 15 07:47:11 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Wed, 15 Nov 2006 08:47:11 +0100 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> References: <20061114214608.A6F8E7304B@hormel.redhat.com> <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> Message-ID: YES. You are right. Each time I had the intuition it was a problem with VNC connection. Effectively, after initialising localhost in /etc/hosts everrything works right again. The good question is now why it comes in this situation ? I never modified this localhost. Is this an issue with system-config-network or another installation I made ? In any case, really THANKS for your help ! 2006/11/15, Robert Thiem : > > When first setting up FC6 I had an issue where I could start an FC6 Xen > guest install but couldn't connect with VNC. > > I don't know if it's the same (I can't remember the exact messages I was > getting), but it ended up being that "localhost" wouldn't resolve to an > IPv4 address. This was due to a nasty combination of anaconda putting IPv4 > and v6 entries in /etc/hosts and system-config-network trimming the > "extra" v4 entry when run. > > Anyway I'd suggest: > - Check that you can ping localhost > - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 > (and not with ::1) > - Run "netstat -antp" to see what ports programs are listening on > > Regards, > Robert Thiem > > -- > 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 laurent.mylists at gmail.com Wed Nov 15 07:47:11 2006 From: laurent.mylists at gmail.com (Laurent Flesch) Date: Wed, 15 Nov 2006 08:47:11 +0100 Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> References: <20061114214608.A6F8E7304B@hormel.redhat.com> <48919.203.25.1.208.1163553800.squirrel@gw.remcc.org> Message-ID: YES. You are right. Each time I had the intuition it was a problem with VNC connection. Effectively, after initialising localhost in /etc/hosts everrything works right again. The good question is now why it comes in this situation ? I never modified this localhost. Is this an issue with system-config-network or another installation I made ? In any case, really THANKS for your help ! 2006/11/15, Robert Thiem : > > When first setting up FC6 I had an issue where I could start an FC6 Xen > guest install but couldn't connect with VNC. > > I don't know if it's the same (I can't remember the exact messages I was > getting), but it ended up being that "localhost" wouldn't resolve to an > IPv4 address. This was due to a nasty combination of anaconda putting IPv4 > and v6 entries in /etc/hosts and system-config-network trimming the > "extra" v4 entry when run. > > Anyway I'd suggest: > - Check that you can ping localhost > - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1 > (and not with ::1) > - Run "netstat -antp" to see what ports programs are listening on > > Regards, > Robert Thiem > > -- > 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 Rob at REMCC.org Wed Nov 15 15:49:56 2006 From: Rob at REMCC.org (Robert Thiem) Date: Thu, 16 Nov 2006 01:49:56 +1000 (EST) Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 Message-ID: <54330.192.168.1.13.1163605796.squirrel@beatrix> Laurent Flesch wrote: > The good question is now why it comes in this situation? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211800 Anaconda and system-config-network behaviour that slipped into FC6. Supposed to be fixed now, but that doesn't update your install DVD :p Robert From junk at remcc.org Wed Nov 15 15:55:55 2006 From: junk at remcc.org (Robert Thiem) Date: Thu, 16 Nov 2006 01:55:55 +1000 (EST) Subject: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6 In-Reply-To: <54330.192.168.1.13.1163605796.squirrel@beatrix> References: <54330.192.168.1.13.1163605796.squirrel@beatrix> Message-ID: <44860.192.168.1.13.1163606155.squirrel@beatrix> Laurent Flesch wrote: > The good question is now why it comes in this situation? ... https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211800 Anaconda and system-config-network behaviour that slipped into FC6. Robert From bloch at verdurin.com Wed Nov 15 17:31:28 2006 From: bloch at verdurin.com (bloch at verdurin.com) Date: Wed, 15 Nov 2006 17:31:28 +0000 Subject: [Fedora-xen] X startup failure with Xen kernel Message-ID: <20061115173128.GL16083@bloch> On a system upgraded from FC5 to FC6, I find that the whole system hangs at X startup if I boot with the Xen kernel. Even Alt-SysRq has no effect. X starts without any problems on a non-Xen kernel. It's a Dell OptiPlex GX270. lspci output: 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) 01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) I see a few other people have vaguely similar problems. Any ideas? Adam From berrange at redhat.com Wed Nov 15 18:26:59 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 15 Nov 2006 18:26:59 +0000 Subject: [Fedora-xen] X startup failure with Xen kernel In-Reply-To: <20061115173128.GL16083@bloch> References: <20061115173128.GL16083@bloch> Message-ID: <20061115182659.GM17466@redhat.com> On Wed, Nov 15, 2006 at 05:31:28PM +0000, bloch at verdurin.com wrote: > On a system upgraded from FC5 to FC6, I find that the whole system hangs > at X startup if I boot with the Xen kernel. Even Alt-SysRq has no > effect. > > X starts without any problems on a non-Xen kernel. > > It's a Dell OptiPlex GX270. > > lspci output: > > 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated > Graphics Controller (rev 02) There's an issue with encountered with Xen and a number of Intel graphics cards when testing for RHEL-5. The core problem is that the real-mode emulation in Xen is broken, so its not handling the switches between 16&32bit mode correctly. We tried to fix Xen but the VMX assist code is just tooo hairly to resolve correctly - a fix for one graphics card would break a different one. So instead, our Xorg wizards have patched the X server to use its own built in realmode emulation instead of relying on Xen. The updated 'xorg-x11-server' RPMs are being prepared for a Fedora Core 6 update in the very near future, so keep an eye on the updates-testing YUM repository for the fix.... Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From stan at freedomics.com Wed Nov 15 19:04:30 2006 From: stan at freedomics.com (Stan Larson) Date: Wed, 15 Nov 2006 14:04:30 -0500 Subject: [Fedora-xen] 3 vif NIC Limit? Message-ID: <455B64BE.9060209@freedomics.com> First and foremost, great job with Xen in Fedora. Now, on to my question. Are there any plans to extend the amount of vif interfaces beyond the current limit of three in DomUs? I realize I can use pciback to get around the current limitation. I'm interested in a solution that doesn't require pciback. Thanks, -- Stan Larson I/S Manager Freedom Sales & Marketing P: (727) 835-1150 F: (727) 835-1151 stan at freedomics.com www.freedomics.com From shobha.ranganathan at intel.com Wed Nov 15 20:16:23 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Wed, 15 Nov 2006 12:16:23 -0800 Subject: [Fedora-xen] I got it work ---- virt-manager gives "The console is currentlyunavailable" in FC6 Message-ID: Thanks Dan for all the debug . and Thanks Robert for sharing and providing the tip. I did cleanup the host file and some more clean up in rc.d directories. I did get the unmodified guest up in running. It has always been helpful to ask Qs in this mailing list... Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: Daniel P. Berrange [mailto:berrange at redhat.com] Sent: Tuesday, November 14, 2006 5:51 PM To: Ranganathan, Shobha Cc: Robert Thiem; fedora-xen at redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6 On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote: > Anyway I'd suggest: > - Check that you can ping localhost > I could ping the localhost > > - Check there's a localhost entry in /etc/hosts associated with > 127.0.0.1 > (and not with ::1) > I have two entries one with 127.0.0.1 and ::1. I went ahead and > commented out ::1 entry > - Run "netstat -antp" to see what ports programs are listening on > I see various services on IP address of the local host 172.xx.xx.xx and > 127.0.0.1 and ::22 and ::1 and 0.0.0.0 > > I see sshd, cupsd and hpiod running with local address as ::22, ::1 and > 0.0.0.0. For fully-virt / HVM guests you should see a 'qemu-dm' process listening on the port associated with VNC (something around 5900+). If you don't then this is the primary problem to address - the qemu-dm*log file may be useful. Also grabbing the command line for qemu-dm active process should indicate what port it tried to start on. In my case: # virsh dumpxml rhel4i386 | grep graphics # ps -axuww | grep qemu root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00 /usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4 -acpi -domain-name rhel4i386 -net nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1 # netstat -t -a -n -p | grep qemu tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4005/qemu-dm # virsh dumpxml rhel4i386 | grep graphics Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Wed Nov 15 20:22:13 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Wed, 15 Nov 2006 12:22:13 -0800 Subject: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage Message-ID: I am trying to get scp to work. It gets stuck displaying "stalled" message. I did "iptables stop". But does not help. This happens in the Xen that I built with xen-3.0.3-rc3 which builds it with 2.6.16.29 kernel in Fedora Core 6. I boot into Fedora provided FC6 Xen host and tried scp and it works. What settings did I miss in configuration ? Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at xelerance.com Wed Nov 15 21:24:55 2006 From: paul at xelerance.com (Paul Wouters) Date: Wed, 15 Nov 2006 22:24:55 +0100 (CET) Subject: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage In-Reply-To: References: Message-ID: On Wed, 15 Nov 2006, Ranganathan, Shobha wrote: > I am trying to get scp to work. It gets stuck displaying "stalled" > message. > This happens in the Xen that I built with xen-3.0.3-rc3 which builds it > with 2.6.16.29 kernel in Fedora Core 6. > I boot into Fedora provided FC6 Xen host and tried scp and it works. Looks more like an MTU isuse. Try using clamping: iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu Otherwise, try pinging with different size packets until it fails, and then use the last successful packet size (eg 1440) to: iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1440 Paul From berrange at redhat.com Wed Nov 15 22:20:11 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 15 Nov 2006 22:20:11 +0000 Subject: [Fedora-xen] Intel graphics problems: [ajackson@redhat.com: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6] Message-ID: <20061115222011.GO17466@redhat.com> For anyone with an Intel graphics card who is experiancing hangs upon boot / starting X under the Xen kernel, then I recommend testing this updated X server RPm from updates-testing. It makes X use its own x86 realmode emulator instead of relying on Xens. Send feedback to the fedora-test-list at redhat.com if you have issues with this update. Regards, Dan. ----- Forwarded message from Adam Jackson ----- > Date: Wed, 15 Nov 2006 16:27:14 -0500 > From: "Adam Jackson" > To: fedora-test-list at redhat.com > Subject: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6 > > --------------------------------------------------------------------- > Fedora Test Update Notification > FEDORA-2006-1237 > 2006-11-15 > --------------------------------------------------------------------- > > Product : Fedora Core 6 > Name : xorg-x11-server > Version : 1.1.1 > Release : 47.1.fc6 > Summary : X.Org X11 X server > Description : > X.Org X11 X server > > --------------------------------------------------------------------- > > * Wed Nov 15 2006 Adam Jackson - 1.1.1-47.1.fc6 > - xorg-x11-server-1.1.1-int10-muxing.patch: Build both the vm86 and x86emu > backends for BIOS calls on x86; prefer x86emu when running under Xen dom0 > since Xen's vm86 handling is flaky. [snip changelogs] > > --------------------------------------------------------------------- > This update can be downloaded from: > http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/ > > a5fc3ad6348f22bf0ac1379c2a58fc3bcb4155a9 SRPMS/xorg-x11-server-1.1.1-47.1.fc6.src.rpm > a5fc3ad6348f22bf0ac1379c2a58fc3bcb4155a9 noarch/xorg-x11-server-1.1.1-47.1.fc6.src.rpm > eafd7064ca6bbdd9e1fc1b0eae41878ef15defed ppc/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.ppc.rpm > 58df8ab98a74cebbb1ed54886bf5c53431abf6ee ppc/xorg-x11-server-Xorg-1.1.1-47.1.fc6.ppc.rpm > 8ae4230c83cfe5c7a1770e7b317e788ecf7a0d1b ppc/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.ppc.rpm > 4b70dcf48e75c657e3fbf8dd77ace737d3a2a663 ppc/xorg-x11-server-sdk-1.1.1-47.1.fc6.ppc.rpm > 360640e2ecb7055a059e8b73de4a865ddfd69dba ppc/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.ppc.rpm > e1fcc733f9a9a0f84783e06054a876ae2e3120d1 ppc/xorg-x11-server-Xnest-1.1.1-47.1.fc6.ppc.rpm > 584ad2bbf57c36e6aaedd9b7b68744cf88051dec ppc/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.ppc.rpm > 729588c5283e9276c3342cbe11a22649204ba378 x86_64/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.x86_64.rpm > 2e3e7a06ef8991469192ae4ce79df18e3b90375b x86_64/xorg-x11-server-Xorg-1.1.1-47.1.fc6.x86_64.rpm > 0f4c5d1ec62a327bc1ece26b9661fa961b94d197 x86_64/xorg-x11-server-sdk-1.1.1-47.1.fc6.x86_64.rpm > 3a5896dbb22523a8d51318197e7a842c4cce620c x86_64/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.x86_64.rpm > 18f3afc3274e9cca963207e5d8476b9129bcef9d x86_64/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.x86_64.rpm > 5366c9326e7fe40cf90a67d5b7953484a43d0e23 x86_64/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.x86_64.rpm > b6125b5a79d48dd6dcc08e1821f55cab13b944ce x86_64/xorg-x11-server-Xnest-1.1.1-47.1.fc6.x86_64.rpm > ab77099f59a79dc35ec6261344dc3498810ad750 i386/xorg-x11-server-Xorg-1.1.1-47.1.fc6.i386.rpm > c4650da3cf8455bd68a81325d8b20236b9c93020 i386/xorg-x11-server-Xnest-1.1.1-47.1.fc6.i386.rpm > 194a3c89736942f35b5ae4fdab7c670c986b37ba i386/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.i386.rpm > 7ed8bf3d750c6dcc1f819dc80a91d79d7d73af27 i386/xorg-x11-server-sdk-1.1.1-47.1.fc6.i386.rpm > e3b589d56b2bb641a6cb17774b4e296cc2b4b7cb i386/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.i386.rpm > f6e45c51bdbf4bd633095d1808f0e5b3b7ce2007 i386/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.i386.rpm > 5213b46a432e69dda9af2a178658c60b64b5dca9 i386/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.i386.rpm > > This update can be installed with the 'yum' update program. Use 'yum update > package-name' at the command line. For more information, refer to 'Managing > Software with yum,' available at http://fedora.redhat.com/docs/yum/. > --------------------------------------------------------------------- > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > ----- End forwarded message ----- -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha.ranganathan at intel.com Thu Nov 16 00:26:20 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Wed, 15 Nov 2006 16:26:20 -0800 Subject: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage Message-ID: Yes . That did it. I am able to copy files using scp. Why does an MTU issue come up in this scenario ? Thanks Shobha -----Original Message----- From: Paul Wouters [mailto:paul at xelerance.com] Sent: Wednesday, November 15, 2006 1:25 PM To: Ranganathan, Shobha Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage On Wed, 15 Nov 2006, Ranganathan, Shobha wrote: > I am trying to get scp to work. It gets stuck displaying "stalled" > message. > This happens in the Xen that I built with xen-3.0.3-rc3 which builds it > with 2.6.16.29 kernel in Fedora Core 6. > I boot into Fedora provided FC6 Xen host and tried scp and it works. Looks more like an MTU isuse. Try using clamping: iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu Otherwise, try pinging with different size packets until it fails, and then use the last successful packet size (eg 1440) to: iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1440 Paul From paul at xelerance.com Thu Nov 16 00:49:10 2006 From: paul at xelerance.com (Paul Wouters) Date: Thu, 16 Nov 2006 01:49:10 +0100 (CET) Subject: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage In-Reply-To: References: Message-ID: On Wed, 15 Nov 2006, Ranganathan, Shobha wrote: > Yes . That did it. I am able to copy files using scp. Excellent. > Why does an MTU issue come up in this scenario ? I have no idea. I encounter this problem mostly in my support job for Openswan, and then the case is usually an overzealous firewall administrator blocking all icmp packets or overly horrid and cheap DSL/cable network design. There have also been issues in the past with path MTU and IPsec (on both KLIPS and NETKEY). This fix tends to work, at least for tcp. Perhaps this is related to the bridging setup of Xen? Or VLAN tagging? I have no idea. Paul > -----Original Message----- > From: Paul Wouters [mailto:paul at xelerance.com] > Sent: Wednesday, November 15, 2006 1:25 PM > To: Ranganathan, Shobha > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage > > On Wed, 15 Nov 2006, Ranganathan, Shobha wrote: > > > I am trying to get scp to work. It gets stuck displaying "stalled" > > message. > > > This happens in the Xen that I built with xen-3.0.3-rc3 which builds > it > > with 2.6.16.29 kernel in Fedora Core 6. > > > I boot into Fedora provided FC6 Xen host and tried scp and it works. > > Looks more like an MTU isuse. Try using clamping: > > iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS > --clamp-mss-to-pmtu > > Otherwise, try pinging with different size packets until it fails, and > then use > the last successful packet size (eg 1440) to: > > iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss > 1440 > > Paul > -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From naoki at valuecommerce.com Thu Nov 16 01:15:10 2006 From: naoki at valuecommerce.com (Naoki) Date: Thu, 16 Nov 2006 10:15:10 +0900 Subject: [Fedora-xen] X startup failure with Xen kernel In-Reply-To: <20061115173128.GL16083@bloch> References: <20061115173128.GL16083@bloch> Message-ID: <1163639710.2944.179.camel@dragon.valuecommerce.ne.jp> Exactly the same problem on my Dell GX620. I've got major problems with Xen and have had them throughout the entire testing cycle of FC6. The two bugs I have opened and am working on are : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215464 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207432 What X driver are you using? $ /sbin/lspci 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1e.2 Multimedia audio controller: Intel Corporation 82801G (ICH7 Family) AC'97 Audio Controller (rev 01) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) On Wed, 2006-11-15 at 17:31 +0000, bloch at verdurin.com wrote: > On a system upgraded from FC5 to FC6, I find that the whole system hangs > at X startup if I boot with the Xen kernel. Even Alt-SysRq has no > effect. > > X starts without any problems on a non-Xen kernel. > > It's a Dell OptiPlex GX270. > > lspci output: > > 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM > Controller/Host-Hub Interface (rev 02) > 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated > Graphics Controller (rev 02) > 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB > UHCI Controller #1 (rev 02) > 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB > UHCI Controller #2 (rev 02) > 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB > UHCI Controller #3 (rev 02) > 00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB > UHCI Controller #4 (rev 02) > 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 > EHCI Controller (rev 02) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) > 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC > Interface Bridge (rev 02) > 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE > Controller (rev 02) > 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller > (rev 02) > 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus > Controller (rev 02) > 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER > (ICH5/ICH5R) AC'97 Audio Controller (rev 02) > 01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 02) > > I see a few other people have vaguely similar problems. Any ideas? > > > Adam > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From e1geo at yahoo.com Thu Nov 16 02:46:22 2006 From: e1geo at yahoo.com (George Hill) Date: Wed, 15 Nov 2006 18:46:22 -0800 (PST) Subject: [Fedora-xen] xenguest-install & vncviewer Message-ID: <20061116024622.42775.qmail@web53614.mail.yahoo.com> It would be nice if the vncserver that xenguest-install starts ran vncviewer (perhaps with the --nowin option so the little window does not get in the way). That way it would be easy to copy error messages, which can get quite lengthy, to a file and include them in bug reports. Or perhaps someone knows another way of copying these messages? From filipe.miranda at gmail.com Thu Nov 16 10:33:17 2006 From: filipe.miranda at gmail.com (Filipe Miranda) Date: Thu, 16 Nov 2006 08:33:17 -0200 Subject: [Fedora-xen] Cannot execute a PAE-enabled kernel on a PAE-less CPU Message-ID: Hello, I have a Thinkpad T41 notebook and I recently installed FC6. One of the cool features of FC6 is the virtualization through Xen, but the xen-kernel that comes with FC6 ( 2.6.18-1.2849) causes kernel panic. Here is the exact message: KERNEL PANIC: Cannot execute a PAE-enabled kernel on a PAE-less CPU! I already tried to use the swiotlb=force parameter during system boots (Grub) but no success. Someone on the xen channel of the Freenode told me that I would need a FC6 xen-non-PAE-kernel but I searched o the FC6 repositories and did not find it. Any suggestions besides compiling it from source? Regards, --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From jurgen at botz.org Thu Nov 16 16:34:04 2006 From: jurgen at botz.org (Juergen Botz) Date: Thu, 16 Nov 2006 13:34:04 -0300 Subject: [Fedora-xen] Virtual hosting provider..? Message-ID: Can anyone recommend any good virtual hosting providers that use Xen and Fedora? :j From e1geo at yahoo.com Thu Nov 16 21:35:42 2006 From: e1geo at yahoo.com (George Hill) Date: Thu, 16 Nov 2006 13:35:42 -0800 (PST) Subject: [Fedora-xen] help installing ubuntu server guest Message-ID: <20061116213543.10183.qmail@web53608.mail.yahoo.com> When I install ubuntu server as a fully-virtualized guest the install always hangs at exactly the same place. After it installs a bunch of packages, it hangs when it tries to install zliblg... I am running Xen/FC6 on a AMD chip. I have tried the following, but it always hangs at the same place I have tried both the 32-bit and 64-bit iso files I have run md5sum on both files I have had the installer check the iso files I have increased the alloted disk space (10GB) and RAM (1.2GB) When I try to do a non-graphical install with xenguest-install I get this message: Domain installation does not appear to have been successful. If it was, you can restart your domain by running 'xm create -c ub.serv1'; otherwise, please restart your installation. As an aside, I have no problem installing fully-virtualized ubuntu desktop and FC6. Any thoughts or suggestions would be appreciated. From bst at mobilethink.dk Fri Nov 17 09:45:43 2006 From: bst at mobilethink.dk (Bertho Stultiens) Date: Fri, 17 Nov 2006 10:45:43 +0100 Subject: [Fedora-xen] Block device sharing Message-ID: <455D84C7.4000203@mobilethink.dk> Hi, I am trying to share a GFS2 partition across multiple xen boxes to share f.x. the /home dir (using FC6). According to the Xen 3.0 documentation at chapter 6.1, I should be using either NFS or a clusterFS. I do not want to use a networkFS, so GFS seems to be the sane choice. The setup: SAN -> /dev/sdX -> [c]LVM -> vgxen -> lvbox{00-99} -> lvswap{00-99} -> lvhome Each VM has mounted a unique rootfs from lvboxX and swap from lvswapX partition and share lvhome using GFS. The SAN has a multipath FC connection to 8 blades and the VMs run distributed over the blades. The problem, however, is that xen does not allow me to export blockdevices that are in use. I've tried to export the PV (/dev/sdX) and the LV (/dev/vgxen/lvhome), but both cases fail with an error (Device /dev/sdX is mounted in a guest domain, and so cannot be mounted now.) Any VM started after the first fails. Is there a way to force xen to export the same blockdevice (either the PV or preferably the LV)? -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From bst at mobilethink.dk Fri Nov 17 12:20:44 2006 From: bst at mobilethink.dk (Bertho Stultiens) Date: Fri, 17 Nov 2006 13:20:44 +0100 Subject: [Fedora-xen] VLANs on DomU domains Message-ID: <455DA91C.7020905@mobilethink.dk> > I am setting up a box with FC6 + xen with FC6 for the DomU guests. > I have a server with 4 gigabit ports and I want to use 802.1Q vlans on > one of the gig ports. > I have the VLANs configured in Dom0 without any addresses attached to > them. > How do I make the VLANs available to the guests? I want to make 4 > VLANs available to each guest. I have thought of a few alternatives > but I cannot get any to work. The easy way; I have installed FC6 with 802.1Q and 4 guests. It works very nicely. For each guest do: 1 - You need to enable vlans /etc/sysconfig/network. NETWORKING=yes VLAN=yes NETWORKING_IPV6=no HOSTNAME=xenbox2.example.com GATEWAY=192.168.42.1 2 - create a subinterface by file editting /etc/sysconfig/network-scripts/ifcfg-eth0.42: DEVICE=eth0.42 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.42.102 NETMASK=255.255.255.0 TYPE=Ethernet 3 - depending on whether you want untagged packets on the same interface, you need to edit the /etc/.../ifcfg-eth0 file too. (note: the parent interface must be up for the tagged interface to work.) The lines commented out will assign an IP address to the untagged interface: DEVICE=eth0 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet # BOOTPROTO=static # IPADDR=172.16.42.102 # NETMASK=255.255.255.0 4 - make sure that your /etc/hosts setup is correct. If you have DNS available 24/7, then only define localhost[.localdomain} as 127.0.0.1 and not the hostname itself. When you restart the network in the guest, then your guest will default to use the tagged interface vlan 42 (above example). If you want the untagged interface as default, then you can change the gateway and assign an IP address to it. On the host, you need to do a similar thing. Create a subinterface eth0.42 and assign an IP address to it. Once that is done, you can talk to your guests via dot1Q from your host. Beware of iptables! If you have a firewall setup, then you need to make sure that it is done right. Doing it right, though, is a though job with dot1Q in place. I have the firewall completely disabled on the host and guests. My firewall is placed physically separated on another box. > 1. Bridge the tagged 802.1Q stream from the Gig port through to the > guests and configure eth0.x. on the guests This would be above scenario. > 2. Create a bridge on Dom0 for each VLAN so that they appear as > eth0...eth3 on the guests. The xenbrX interfaces on the host already transport all packets because they are L2 bridges (see brctl). The bridge does not care whether the packets are .1Q tagged or not. The only thing you need is to instruct the kernel to look for/act on specifics by creating (sub-)interfaces. Now, if you want the guests not to know that they are connected to a VLAN, then you need a brigde-interface to do (un-)tagging for you. That means that you need to create a dot1Q subinterface on the host's physical peth[0-3] and add the subinterface to a new bridge. Normal scenario: peth0 -> xenbr0 -> vif0.0(host eth0) vif1.0(guest1 eth0) Dot1Q scenario: peth0.42 -> xenbr42 -> vif1.0(guest1 eth0) i.e.: # brctl addbr xenbr42 # ip link set xenbr42 up # vconfig add peth0 42 # ip link set peth0.42 up # brctl addif xenbr42 peth0.42 In the VM config you have now something like: vif = [ 'mac=00:16:3e:11:22:33, bridge=xenbr42', ] The VM's eth0 interface is created as part of bridge that will fowrard to a subinterface. The kernel will now do the tagging/untagging (note: slow) and the VM cannot see that it is attached to a VLAN. Theoretically it should work, but I was not able to make this scenario work as expected though. I suspect that the hosts peth0 -> eth0 bridge is interfering (which has a tagged interface too in my setup). Or maybe my fingers were too fast at typing and I forgot a simple thing... > The xen documentation is minimal for configuring VLANs. Is there a > (FC6) supported way of configuring them? Vlans is a no-issue for xen. It is layered in the network and xen only passes the packets. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From paul at xelerance.com Fri Nov 17 16:19:07 2006 From: paul at xelerance.com (Paul Wouters) Date: Fri, 17 Nov 2006 17:19:07 +0100 (CET) Subject: [Fedora-xen] Block device sharing In-Reply-To: <455D84C7.4000203@mobilethink.dk> References: <455D84C7.4000203@mobilethink.dk> Message-ID: On Fri, 17 Nov 2006, Bertho Stultiens wrote: > The problem, however, is that xen does not allow me to export > blockdevices that are in use. I've tried to export the PV (/dev/sdX) and > the LV (/dev/vgxen/lvhome), but both cases fail with an error (Device > /dev/sdX is mounted in a guest domain, and so cannot be mounted now.) > Any VM started after the first fails. > > Is there a way to force xen to export the same blockdevice (either the > PV or preferably the LV)? Isn't the typical setup to have GNDB as SAN and have that exported to the xen's? Paul From thomas.vonsteiger at bluewin.ch Sat Nov 18 09:10:03 2006 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Sat, 18 Nov 2006 10:10:03 +0100 Subject: AW: [Fedora-xen] Block device sharing In-Reply-To: <455D84C7.4000203@mobilethink.dk> Message-ID: <01ac01c70af1$55a6f670$3201a8c0@athlon> Hi Bertho, My setup for gfs inside guest's looks like this. For export 1 os lv and 2 shared lv's I use this: disk = ['phy:/dev/xenvg/xenRHEL4_3,ioemu:hda,w', 'phy:/dev/xenvg/xenCLU1fs1,ioemu:hdb,w!', 'phy:/dev/xenvg/xenCLU1fs2,ioemu:hdc,w!' ] For sharing a blockdevice you need "w!". On top xenCLU1fs1 and xenCLU1fs2 i have running gfs with clvm inside the guests. Thomas -----Urspr?ngliche Nachricht----- Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Bertho Stultiens Gesendet: Freitag, 17. November 2006 10:46 An: fedora-xen at redhat.com Betreff: [Fedora-xen] Block device sharing Hi, I am trying to share a GFS2 partition across multiple xen boxes to share f.x. the /home dir (using FC6). According to the Xen 3.0 documentation at chapter 6.1, I should be using either NFS or a clusterFS. I do not want to use a networkFS, so GFS seems to be the sane choice. The setup: SAN -> /dev/sdX -> [c]LVM -> vgxen -> lvbox{00-99} -> lvswap{00-99} -> lvhome Each VM has mounted a unique rootfs from lvboxX and swap from lvswapX partition and share lvhome using GFS. The SAN has a multipath FC connection to 8 blades and the VMs run distributed over the blades. The problem, however, is that xen does not allow me to export blockdevices that are in use. I've tried to export the PV (/dev/sdX) and the LV (/dev/vgxen/lvhome), but both cases fail with an error (Device /dev/sdX is mounted in a guest domain, and so cannot be mounted now.) Any VM started after the first fails. Is there a way to force xen to export the same blockdevice (either the PV or preferably the LV)? -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.6/536 - Release Date: 16.11.2006 From pspuhler at ball.com Sat Nov 18 22:04:08 2006 From: pspuhler at ball.com (Peter Spuhler) Date: Sat, 18 Nov 2006 15:04:08 -0700 Subject: [Fedora-xen] keyboard/mouse problems during win2k3 installation Message-ID: <455F8358.1080103@ball.com> I am able to install windows 2003 64-bit on FC6 64-bit Dell Precision 490 until the win2k3 installer gets to asking about name/org and product id, then the keyboard and mouse stops working alltogether in the virtual machine. I've tried virt-install, virt-manger and modified example.hvm file. I've also played with using vnc or sdl and turning on/off usb without success. Has anyone else encountered this problem and found a workaround? # -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses 'hvm'. builder='hvm' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 512 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. shadow_memory = 32 # A name for your domain. All domains must have different names. name = "win2k3" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to 'xm create'. uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # the number of cpus guest platform has, default=1 vcpus=1 # enable/disable HVM guest PAE, default=0 (disabled) pae=1 # enable/disable HVM guest ACPI, default=0 (disabled) acpi=1 # enable/disable HVM guest APIC, default=0 (disabled) apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] # type=ioemu specify the NIC is an ioemu device not netfront #vif = [ 'type=ioemu, bridge=xenbr0' ] #---------------------------------------------------------------------------- # 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:/dev/sda3,ioemu:hda,w','file:/root/WINDOWS_2003.iso,hdc:cdrom,r' ] #disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',hdc:cdrom,r' ] #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'destroy' # # restart = 'always' means on_poweroff = 'restart' # on_reboot = 'restart' # on_crash = 'restart' # # restart = 'never' means on_poweroff = 'destroy' # on_reboot = 'destroy' # on_crash = 'destroy' on_poweroff = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' #============================================================================ # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' #----------------------------------------------------------------------------- # Disk image for cdrom = '/root/WINDOWS_2003.iso' #cdrom = '/dev/cdrom' #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot='c' #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=0 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 vnc=1 vncviewer=1 #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #---------------------------------------------------------------------------- # set VNC display number, default = domid #vncdisplay=1 #---------------------------------------------------------------------------- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #---------------------------------------------------------------------------- # enable spawning vncviewer for domain's console # (only valid when vnc=1), default = 0 #vncconsole=0 #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=1 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial='pty' #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw='sb16' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) usb=0 # Enable USB mouse support (only enable one of the following, `mouse' for # PS/2 protocol relative mouse, `tablet' for # absolute mouse) #usbdevice='mouse' #usbdevice='tablet' #----------------------------------------------------------------------------- # enable ne2000, default = 0 (use pcnet) ne2000=1 From bst at mobilethink.dk Sun Nov 19 10:49:38 2006 From: bst at mobilethink.dk (Bertho Stultiens) Date: Sun, 19 Nov 2006 11:49:38 +0100 Subject: AW: [Fedora-xen] Block device sharing In-Reply-To: <01ac01c70af1$55a6f670$3201a8c0@athlon> References: <01ac01c70af1$55a6f670$3201a8c0@athlon> Message-ID: <456036C2.9010900@mobilethink.dk> Thomas von Steiger wrote: > My setup for gfs inside guest's looks like this. > For export 1 os lv and 2 shared lv's I use this: > disk = ['phy:/dev/xenvg/xenRHEL4_3,ioemu:hda,w', > 'phy:/dev/xenvg/xenCLU1fs1,ioemu:hdb,w!', > 'phy:/dev/xenvg/xenCLU1fs2,ioemu:hdc,w!' ] > For sharing a blockdevice you need "w!". On top xenCLU1fs1 and xenCLU1fs2 i > have running gfs with clvm inside the guests. Thank you very much. The w! does the trick. You also have the "ioemu" flag specified. Is this required? I could not find any documentation about that. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From ianbrn at gmail.com Sun Nov 19 16:24:49 2006 From: ianbrn at gmail.com (Ian Brown) Date: Sun, 19 Nov 2006 18:24:49 +0200 Subject: [Fedora-xen] Probems installiing windows under xen in FC6 Message-ID: Hello, I am trying desperately to install windows under xen in FC6 on x86_64; my processor has virtulaization extensions (as can be seen from flags of /proc/cpuinfo). The kernel I have is the one from the FC6 DVD, 2.6.18-1.2798.fc6xen. I had prepared a configuration file , windows.hvm, which is given fully in the end of this message. When I ran : xm create windows.hvm , there is some window on the screen for a second then it is closed. On the console I see xm create windows.hvm Using config file "/etc/xen/windows.hvm". Started domain ExampleHVMDomain and that's it. I am not sure about this line : disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ] I am not sure about something: I do indeed have a sata disk; which is sda; but when using qemu, should it also be sda? I see in the kernel log the following: rh kernel: device tap0 entered promiscuous mode rh kernel: audit(1163952063.221:41): dev=tap0 prom=256 old_prom=0 auid=4294967295 rh kernel: xenbr0: port 3(tap0) entering learning state rh kernel: xenbr0: topology change detected, propagating rh kernel: xenbr0: port 3(tap0) entering forwarding state rh kernel: device vif10.0 entered promiscuous mode rh kernel: audit(1163952063.589:42): dev=vif10.0 prom=256 old_prom=0 auid=4294967295 rh kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready rh kernel: xenbr0: port 4(vif10.0) entering disabled state rh kernel: device vif10.0 left promiscuous mode rh kernel: audit(1163952064.309:43): dev=vif10.0 prom=0 old_prom=256 auid=4294967295 rh kernel: xenbr0: port 4(vif10.0) entering disabled state rh kernel: xenbr0: port 3(tap0) entering disabled state rh kernel: device tap0 left promiscuous mode rh kernel: audit(1163952064.469:44): dev=tap0 prom=0 old_prom=256 auid=4294967295 rh kernel: xenbr0: port 3(tap0) entering disabled state and this is windows.hvm: # -*- mode: python; -*- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses 'hvm'. builder='hvm' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. #memory = 128 memory = 384 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. shadow_memory = 8 # A name for your domain. All domains must have different names. name = "ExampleHVMDomain" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to 'xm create'. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # the number of cpus guest platform has, default=1 #vcpus=1 vcpus=1 # enable/disable HVM guest PAE, default=0 (disabled) #pae=0 # enable/disable HVM guest ACPI, default=0 (disabled) #acpi=0 # enable/disable HVM guest APIC, default=0 (disabled) #apic=0 vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ] #---------------------------------------------------------------------------- # 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 = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ] cdrom='/dev/hdb' on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' #on_reboot = 'destroy' #on_crash = 'destroy' ne2000=0 #============================================================================ # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy #boot from cdrom boot="d" sdl=1 vnc=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect #serial='pty' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) usb=1 # Enable USB mouse support (only enable one of the following, `mouse' for # PS/2 protocol relative mouse, `tablet' for # absolute mouse) usbdevice='mouse' any ideas what can cause the problem? Regards, Ian From berrange at redhat.com Sun Nov 19 16:53:32 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 19 Nov 2006 16:53:32 +0000 Subject: AW: [Fedora-xen] Block device sharing In-Reply-To: <456036C2.9010900@mobilethink.dk> References: <01ac01c70af1$55a6f670$3201a8c0@athlon> <456036C2.9010900@mobilethink.dk> Message-ID: <20061119165332.GA2393@redhat.com> On Sun, Nov 19, 2006 at 11:49:38AM +0100, Bertho Stultiens wrote: > Thomas von Steiger wrote: > > My setup for gfs inside guest's looks like this. > > For export 1 os lv and 2 shared lv's I use this: > > disk = ['phy:/dev/xenvg/xenRHEL4_3,ioemu:hda,w', > > 'phy:/dev/xenvg/xenCLU1fs1,ioemu:hdb,w!', > > 'phy:/dev/xenvg/xenCLU1fs2,ioemu:hdc,w!' ] > > For sharing a blockdevice you need "w!". On top xenCLU1fs1 and xenCLU1fs2 i > > have running gfs with clvm inside the guests. > > Thank you very much. The w! does the trick. > > You also have the "ioemu" flag specified. Is this required? I could not > find any documentation about that. ioemu: is obsolete as of Xen 3.0.3 release. It prior releases it was needed whenever setting up a disk for fullyvirt/HVM guests. In current releases it is silently ignored. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From robin-lists at robinbowes.com Sun Nov 19 18:53:33 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Sun, 19 Nov 2006 18:53:33 +0000 Subject: [Fedora-xen] Using large disk in DomU Message-ID: Hi, I'm running Xen 3.0.3 on FC6 with FC6 DomU guests. On the Dom0 machine, I have 8 x 500GB disks running as a RAID6 array with lvm on top of that. There is one partition available: /dev/vg_media/lv_media which has an ext3 FS on it. I want to make this available to a DomU guest, so I put this in the xen config file: disk = [ 'phy:/dev/vg_host/lv_slim,xvda,w', 'phy:/dev/vg_media/lv_media,sda1,w', ] The disk appears in the DomU guest, but if I fsck it, this is what I see: # fsck /dev/sda1 fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) The filesystem size (according to the superblock) is 732575744 blocks The physical size of the device is 195704832 blocks Either the superblock or the partition table is likely to be corrupt! Abort? yes Any idea what's going on here? Am I doing something wrong? R. From robin-lists at robinbowes.com Sun Nov 19 19:07:55 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Sun, 19 Nov 2006 19:07:55 +0000 Subject: [Fedora-xen] Re: DomU network doesn't start automatically In-Reply-To: References: Message-ID: Robin Bowes wrote: > Hi, > > I'm running 2.6.17-1.2187_FC5xen0 as my host and 2.6.18-1.2200.fc5xenU > in the guest. > > I'm finding that the network doesn't start when I start the guest. > > If I login (through the console) and manually start it, it works fine. e.g.: > > service network start > > Any idea what might cause this and how to fix it? I figured out what this is. I've installed runit from an RPM with a script that installs it to inittab automatically. Unfortunately, it's broken! It adds these lines: RV:2345:respawn:/usr/bin/runsvdir-start /var/service RX:S016:wait:/usr/bin/runsvdir-stopall /var/service But manages to delete the following lines: l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 I've added them back and all is well. R. From junk at remcc.org Mon Nov 20 00:39:56 2006 From: junk at remcc.org (Robert Thiem) Date: Mon, 20 Nov 2006 10:39:56 +1000 (EST) Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: <20061119170007.3C7AE734BC@hormel.redhat.com> References: <20061119170007.3C7AE734BC@hormel.redhat.com> Message-ID: <37595.192.168.1.13.1163983196.squirrel@beatrix> Ian Brown wrote: > I am trying desperately to install windows under xen in FC6 on x86_64; ... > When I ran : > xm create windows.hvm , there is some window on the screen for a second > then it is closed. > > On the console I see > xm create windows.hvm > Using config file "/etc/xen/windows.hvm". > Started domain ExampleHVMDomain > and that's it. I'm just starting to look at getting a HVM running myself (that's an "I'm not an expert disclaimer" :> ) I didn't think that "xm create" would say anything beyond that. If you do a "xm list" does it show up the HVM domain? Maybe it's just sitting around running in the background waiting for a VNC connection or somesuch. Regards, Robert From junk at remcc.org Mon Nov 20 01:00:44 2006 From: junk at remcc.org (Robert Thiem) Date: Mon, 20 Nov 2006 11:00:44 +1000 (EST) Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: <37595.192.168.1.13.1163983196.squirrel@beatrix> References: <20061119170007.3C7AE734BC@hormel.redhat.com> <37595.192.168.1.13.1163983196.squirrel@beatrix> Message-ID: <43499.192.168.1.13.1163984444.squirrel@beatrix> > Ian Brown wrote: >> I am trying desperately to install windows under xen in FC6 on x86_64; > ... >> When I ran : >> xm create windows.hvm , there is some window on the screen for a second >> then it is closed. > > I didn't think that "xm create" would say anything beyond that. > > If you do a "xm list" does it show up the HVM domain? Maybe it's just > sitting around running in the background waiting for a VNC connection or > somesuch. Seeing as I was after one anyway I gave your config a go. It does *indeed* pop up a window briefly - whatchaknow :) >From "xm dmesg" it looks as though (on my box) it can't see the CDROM to boot from and shuts down. There does seem to be something about a CDROM in the window that pops up, but I don't read quite *that* quickly. If I get it going I'll post back here. Robert From junk at remcc.org Mon Nov 20 02:07:30 2006 From: junk at remcc.org (Robert Thiem) Date: Mon, 20 Nov 2006 12:07:30 +1000 (EST) Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: <43499.192.168.1.13.1163984444.squirrel@beatrix> References: <20061119170007.3C7AE734BC@hormel.redhat.com> <37595.192.168.1.13.1163983196.squirrel@beatrix> <43499.192.168.1.13.1163984444.squirrel@beatrix> Message-ID: <35136.192.168.1.13.1163988450.squirrel@beatrix> The xen cdrom config seems to have changed, or at least it's pickier than I'd like. Here are the non-comment bits from my config that seems to be working. import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 128 shadow_memory = 8 name = "winxp" vif = [ 'type=ioemu, bridge=xenbr0' ] disk = [ 'file:/extra/xen/hvm.img,hda,w', 'file:/extra/xen/hvm-cdrom.iso,hdc:cdrom,r' ] device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' sdl=1 vnc=0 stdvga=0 serial='pty' From ianbrn at gmail.com Mon Nov 20 06:58:26 2006 From: ianbrn at gmail.com (Ian Brown) Date: Mon, 20 Nov 2006 08:58:26 +0200 Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: <35136.192.168.1.13.1163988450.squirrel@beatrix> References: <20061119170007.3C7AE734BC@hormel.redhat.com> <37595.192.168.1.13.1163983196.squirrel@beatrix> <43499.192.168.1.13.1163984444.squirrel@beatrix> <35136.192.168.1.13.1163988450.squirrel@beatrix> Message-ID: Hello, I will give it a try in a couple of hours as I am right now not close to that machine with the processors with VT support. May I ask - is your disk is a SATA disk on non-SATA? (this is for the disk = [ 'file:/extra/xen/hvm.img,hda,w', line, which in my case is disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]). And : Did you succeed in installing windows with this config file ? Did you succeed in running windows under Xen ? I am quite surprised that there is not (yet) an HowTo on this , which seems to be a popular task theses days under FC6. Regards, Ian On 11/20/06, Robert Thiem wrote: > The xen cdrom config seems to have changed, or at least it's pickier than > I'd like. > > Here are the non-comment bits from my config that seems to be working. > > import os, re > arch = os.uname()[4] > if re.search('64', arch): > arch_libdir = 'lib64' > else: > arch_libdir = 'lib' > kernel = "/usr/lib/xen/boot/hvmloader" > builder='hvm' > memory = 128 > shadow_memory = 8 > name = "winxp" > vif = [ 'type=ioemu, bridge=xenbr0' ] > disk = [ 'file:/extra/xen/hvm.img,hda,w', > 'file:/extra/xen/hvm-cdrom.iso,hdc:cdrom,r' ] > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' > sdl=1 > vnc=0 > stdvga=0 > serial='pty' > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From junk at remcc.org Mon Nov 20 08:29:24 2006 From: junk at remcc.org (Robert Thiem) Date: Mon, 20 Nov 2006 18:29:24 +1000 (EST) Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: References: <20061119170007.3C7AE734BC@hormel.redhat.com> <37595.192.168.1.13.1163983196.squirrel@beatrix> <43499.192.168.1.13.1163984444.squirrel@beatrix> <35136.192.168.1.13.1163988450.squirrel@beatrix> Message-ID: <41008.192.168.1.13.1164011364.squirrel@beatrix> > May I ask - is your disk is a SATA disk on non-SATA? (this is for the > disk = [ 'file:/extra/xen/hvm.img,hda,w', line, which in my case is > disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]). My disk is a SATA, but I don't think that matters much as I'm just using a file based disk device. I think that second tag tells the HW emulation layer what to present the device as to the guest operating system, so you should be able to present the disk image file as SDA if you like but it would only affect what sort of drivers windows uses to talk to the emulation layer. They may have to match if you're presenting the guest with real partitions (which gives better performance), not sure. If you're wanting to point it at a real CD-ROM you put in something like 'phy:/dev/cdrom,hdc:cdrom,r' instead of the iso. > And : > Did you succeed in installing windows with this config file ? > Did you succeed in running windows under Xen ? Yes, seems to work fine. Good luck, Robert From junk at remcc.org Mon Nov 20 09:22:54 2006 From: junk at remcc.org (Robert Thiem) Date: Mon, 20 Nov 2006 19:22:54 +1000 (EST) Subject: [Fedora-xen] SELinux HVM unfriendly? Message-ID: <34576.192.168.1.13.1164014574.squirrel@beatrix> When getting hardware virtualisation running on my machine I noticed that xen couldn't find my file backed disk unless I put selinux back to permissive. In /var/log/messages qemu-dm, ifconfig and python (running in the context of xend_t) are triggering a lot of denies. Is this usual, or have I messed up my SELinux policy somehow? Paravirt seems happy enough, and I could just add a "setenforce permissive" to the startup for whatever infrequently used full virt systems I build. It's just a bit strange as selinux had been surprisingly quiet so far on FC6. Robert From robin-lists at robinbowes.com Mon Nov 20 11:16:14 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Mon, 20 Nov 2006 11:16:14 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: Message-ID: Robin Bowes wrote: > Hi, > > I'm running Xen 3.0.3 on FC6 with FC6 DomU guests. > > On the Dom0 machine, I have 8 x 500GB disks running as a RAID6 array > with lvm on top of that. There is one partition available: > /dev/vg_media/lv_media which has an ext3 FS on it. > > I want to make this available to a DomU guest, so I put this in the xen > config file: > > disk = [ 'phy:/dev/vg_host/lv_slim,xvda,w', > 'phy:/dev/vg_media/lv_media,sda1,w', ] > > > > The disk appears in the DomU guest, but if I fsck it, this is what I see: > > # fsck /dev/sda1 > fsck 1.39 (29-May-2006) > e2fsck 1.39 (29-May-2006) > The filesystem size (according to the superblock) is 732575744 blocks > The physical size of the device is 195704832 blocks > Either the superblock or the partition table is likely to be corrupt! > Abort? yes > > Any idea what's going on here? Am I doing something wrong? Robin Bowes wrote: > Hi, > > I'm running Xen 3.0.3 on FC6 with FC6 DomU guests. > > On the Dom0 machine, I have 8 x 500GB disks running as a RAID6 array > with lvm on top of that. There is one partition available: > /dev/vg_media/lv_media which has an ext3 FS on it. > > I want to make this available to a DomU guest, so I put this in the xen > config file: > > disk = [ 'phy:/dev/vg_host/lv_slim,xvda,w', > 'phy:/dev/vg_media/lv_media,sda1,w', ] > > > > The disk appears in the DomU guest, but if I fsck it, this is what I see: > > # fsck /dev/sda1 > fsck 1.39 (29-May-2006) > e2fsck 1.39 (29-May-2006) > The filesystem size (according to the superblock) is 732575744 blocks > The physical size of the device is 195704832 blocks > Either the superblock or the partition table is likely to be corrupt! > Abort? yes > > Any idea what's going on here? Am I doing something wrong? I tried a different approach to this. I made /dev/md2 visible in the guest as xvdb1: disk = [ 'phy:vg_host/lv_slim,xvda,w', 'phy:md2,xvdb1,w', ] Now, the VG is being detected when the guest boots up: Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "vg_media" using metadata type lvm2 Found volume group "vg_slim" using metadata type lvm2 And, from a root shell, both the VG and the LV are visible: # vgs VG #PV #LV #SN Attr VSize VFree vg_media 1 1 0 wz--n- 2.73T 0 vg_slim 1 6 0 wz--n- 9.88G 32.00M # lvdisplay vg_media/lv_media --- Logical volume --- LV Name /dev/vg_media/lv_media VG Name vg_media LV UUID KK4J0k-OgoI-441I-lYa2-OF1k-C4FW-g4qi7o LV Write Access read/write LV Status available # open 0 LV Size 2.73 TB Current LE 715406 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:6 /dev/mapper/vg_media-lv_media is present but there's no device file in /dev, i.e. /dev/vg_media/lv_media does not exists. I did notice an error if I try to activate all VGs: # vgchange -ay device-mapper: reload ioctl failed: Invalid argument 1 logical volume(s) in volume group "vg_media" now active 6 logical volume(s) in volume group "vg_slim" now active So, any idea what's going on here? How can I make this filesystem available to my guest? Thanks, R. From tomas at jikos.cz Mon Nov 20 11:30:05 2006 From: tomas at jikos.cz (Tomas Kouba) Date: Mon, 20 Nov 2006 12:30:05 +0100 Subject: [Fedora-xen] xenguest-install and vif-nat Message-ID: <456191BD.4000600@jikos.cz> Hi, is it possible to use xenguest-install script to build up a guest if I use NAT-ed configuration for guests? I don't see any option like this and the network is always bridged. -- Tomas Kouba From berrange at redhat.com Mon Nov 20 11:58:19 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 20 Nov 2006 11:58:19 +0000 Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: References: <20061119170007.3C7AE734BC@hormel.redhat.com> <37595.192.168.1.13.1163983196.squirrel@beatrix> <43499.192.168.1.13.1163984444.squirrel@beatrix> <35136.192.168.1.13.1163988450.squirrel@beatrix> Message-ID: <20061120115819.GA16922@redhat.com> On Mon, Nov 20, 2006 at 08:58:26AM +0200, Ian Brown wrote: > Hello, > I will give it a try in a couple of hours as I am right now not close to > that > machine with the processors with VT support. > > May I ask - is your disk is a SATA disk on non-SATA? (this is for the > disk = [ 'file:/extra/xen/hvm.img,hda,w', line, which in my case is > disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]). > > > And : > Did you succeed in installing windows with this config file ? > Did you succeed in running windows under Xen ? > > I am quite surprised that there is not (yet) an HowTo on this , which > seems to be a popular task theses days under FC6. If anyone wants to write one - feel free to add it in the Fedora Project wiki - there is a general Xen + FC6 guide you can either add to directly, or link to a new page from http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Mon Nov 20 13:28:34 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 20 Nov 2006 13:28:34 +0000 Subject: [Fedora-xen] SELinux HVM unfriendly? In-Reply-To: <34576.192.168.1.13.1164014574.squirrel@beatrix> References: <34576.192.168.1.13.1164014574.squirrel@beatrix> Message-ID: <20061120132834.GA15703@redhat.com> On Mon, Nov 20, 2006 at 07:22:54PM +1000, Robert Thiem wrote: > When getting hardware virtualisation running on my machine I noticed that > xen couldn't find my file backed disk unless I put selinux back to > permissive. In FC6 GA you had to make sure the file for the disk was under /xen to be labelled correctly. In rawhide (and I think latest FC6 policy) we're moving to /var/lib/xen/images. To see what the required dir is run semanage context -l | grep xen_image_t You can also define new locations any time you like using semanage, eg semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From junk at remcc.org Mon Nov 20 14:38:42 2006 From: junk at remcc.org (Robert Thiem) Date: Tue, 21 Nov 2006 00:38:42 +1000 (EST) Subject: [Fedora-xen] SELinux HVM unfriendly? In-Reply-To: <20061120132834.GA15703@redhat.com> References: <34576.192.168.1.13.1164014574.squirrel@beatrix> <20061120132834.GA15703@redhat.com> Message-ID: <58773.192.168.1.13.1164033522.squirrel@beatrix> > In FC6 GA you had to make sure the file for the disk was under /xen > to be labelled correctly. In rawhide (and I think latest FC6 policy) > we're moving to /var/lib/xen/images. To see what the required dir is > run > semanage context -l | grep xen_image_t > You can also define new locations any time you like using semanage, > eg > semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' I had a look at that when I first came across the problem and found it mentioned on the list archives. AFAIK that's fine. All the images come up with the system_u:object_r:xen_image_t context when I do an ls -Z. "semanage fcontext -l | grep xen_image_t" yields the expected /extra/xen(/.*)?all files system_u:object_r:xen_image_t:s0 along with "/xen(/.*)?" and the new "/var/lib/xen/images(/.*)?" What when SELinux is enforcing all I get is: avc: denied { search } for pid=3662 comm="python" name="/" dev=sda8 ino=2 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:default_t:s0 tclass=dir [sda8 is my /extra partition] When it's permissive then I see: "ifconfig" being denied write to the cdrom devices qemu-dm denied access to dsp If I have it set in SDL I also getqemu-dm denies on various things that seem to be related to bringing up the display window (.xauth* files, xdm temp folders, ".X11-unix" and "tmp" dirs, "X0" socket, ".xauthBLAHBLAH"). From junk at remcc.org Mon Nov 20 14:50:05 2006 From: junk at remcc.org (Robert Thiem) Date: Tue, 21 Nov 2006 00:50:05 +1000 (EST) Subject: [Fedora-xen] SELinux HVM unfriendly? In-Reply-To: <58773.192.168.1.13.1164033522.squirrel@beatrix> References: <34576.192.168.1.13.1164014574.squirrel@beatrix> <20061120132834.GA15703@redhat.com> <58773.192.168.1.13.1164033522.squirrel@beatrix> Message-ID: <46592.192.168.1.13.1164034205.squirrel@beatrix> ... (Continued - apparently trying to add tabs and spaces to a web based e-mail window can lead to premature mailing :> ) None of these turn up with the paravirtualisation. My HVM config is straight from the xmexample.hvm except for the disk line and activating SDL and sound. I don't remember destroying my SELinux settings except to set contexts on /extra/xen (selinux policies scare me), but I do run the closed source NVidia drivers (Of Doom!) which do do something to SELinux, so who knows. Anyway - I lived without SELinux for FC1-5. I imagine I can live with the occasional permissive mode until FC7. Robert From shobha.ranganathan at intel.com Mon Nov 20 17:46:44 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Mon, 20 Nov 2006 09:46:44 -0800 Subject: [Fedora-xen] keyboard/mouse problems during win2k3 installation Message-ID: I have had keyboard/mouse problems after the install in the FC5 guest install in x86 mode for both host/guest. It was an Apple Intel machine and I could not find a workaround. I then installed it with no graphics on boot up. But I had several other problems like VNC issues plaguing me... I do not have a workaround. I only share the same set of problems at a different time. Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Peter Spuhler Sent: Saturday, November 18, 2006 2:04 PM To: fedora-xen at redhat.com Subject: [Fedora-xen] keyboard/mouse problems during win2k3 installation I am able to install windows 2003 64-bit on FC6 64-bit Dell Precision 490 until the win2k3 installer gets to asking about name/org and product id, then the keyboard and mouse stops working alltogether in the virtual machine. I've tried virt-install, virt-manger and modified example.hvm file. I've also played with using vnc or sdl and turning on/off usb without success. Has anyone else encountered this problem and found a workaround? # -*- mode: python; -*- #======================================================================= ===== # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #======================================================================= ===== import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' #----------------------------------------------------------------------- ----- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses 'hvm'. builder='hvm' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 512 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. shadow_memory = 32 # A name for your domain. All domains must have different names. name = "win2k3" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to 'xm create'. uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------- ------ # the number of cpus guest platform has, default=1 vcpus=1 # enable/disable HVM guest PAE, default=0 (disabled) pae=1 # enable/disable HVM guest ACPI, default=0 (disabled) acpi=1 # enable/disable HVM guest APIC, default=0 (disabled) apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] # type=ioemu specify the NIC is an ioemu device not netfront #vif = [ 'type=ioemu, bridge=xenbr0' ] #----------------------------------------------------------------------- ----- # 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:/dev/sda3,ioemu:hda,w','file:/root/WINDOWS_2003.iso,hdc:cdrom,r' ] #disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',hdc:cdrom,r' ] #----------------------------------------------------------------------- ----- # Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'destroy' # # restart = 'always' means on_poweroff = 'restart' # on_reboot = 'restart' # on_crash = 'restart' # # restart = 'never' means on_poweroff = 'destroy' # on_reboot = 'destroy' # on_crash = 'destroy' on_poweroff = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' #======================================================================= ===== # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' #----------------------------------------------------------------------- ------ # Disk image for cdrom = '/root/WINDOWS_2003.iso' #cdrom = '/dev/cdrom' #----------------------------------------------------------------------- ------ # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot='c' #----------------------------------------------------------------------- ------ # write to temporary files instead of disk image files #snapshot=1 #----------------------------------------------------------------------- ----- # enable SDL library for graphics, default = 0 sdl=0 #----------------------------------------------------------------------- ----- # enable VNC library for graphics, default = 1 vnc=1 vncviewer=1 #----------------------------------------------------------------------- ----- # address that should be listened on for the VNC server if vnc is set. # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #----------------------------------------------------------------------- ----- # set VNC display number, default = domid #vncdisplay=1 #----------------------------------------------------------------------- ----- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #----------------------------------------------------------------------- ----- # enable spawning vncviewer for domain's console # (only valid when vnc=1), default = 0 #vncconsole=0 #----------------------------------------------------------------------- ----- # no graphics, use serial port #nographic=0 #----------------------------------------------------------------------- ----- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=1 #----------------------------------------------------------------------- ------ # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial='pty' #----------------------------------------------------------------------- ------ # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw='sb16' #----------------------------------------------------------------------- ------ # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------- ------ # start in full screen #full-screen=1 #----------------------------------------------------------------------- ------ # Enable USB support (specific devices specified at runtime through the # monitor window) usb=0 # Enable USB mouse support (only enable one of the following, `mouse' for # PS/2 protocol relative mouse, `tablet' for # absolute mouse) #usbdevice='mouse' #usbdevice='tablet' #----------------------------------------------------------------------- ------ # enable ne2000, default = 0 (use pcnet) ne2000=1 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From paul at xelerance.com Mon Nov 20 18:34:06 2006 From: paul at xelerance.com (Paul Wouters) Date: Mon, 20 Nov 2006 19:34:06 +0100 (CET) Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge Message-ID: I again have the problem that the installer hangs while installing a xenu. The symptoms are that the last you see is the "Starting install process. This may take several minutes..." I can still send a shutdown over the xm command. "xm top" shows no CPU usage whatsoever. I gave it a GB of ram and it reports only using 25%. It's a stock install, with all options unselected, "customize" picked, and all options again unselected, using the default partition scheme on a 4GB diskfile. With selinux disabled on the dom0. The hardware is a Dell poweredge (I believe an 850), with a single P4, 4GB of ram and SATA disks. The dom0 is a i386 image install of FC6 with all updates. Paul From berrange at redhat.com Mon Nov 20 18:34:42 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 20 Nov 2006 18:34:42 +0000 Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: References: Message-ID: <20061120183442.GD15703@redhat.com> On Mon, Nov 20, 2006 at 07:34:06PM +0100, Paul Wouters wrote: > > I again have the problem that the installer hangs while installing a > xenu. The symptoms are that the last you see is the > > "Starting install process. This may take several minutes..." > > I can still send a shutdown over the xm command. "xm top" shows no CPU > usage whatsoever. I gave it a GB of ram and it reports only using 25%. > > It's a stock install, with all options unselected, "customize" picked, > and all options again unselected, using the default partition scheme on a > 4GB diskfile. With selinux disabled on the dom0. Is it a FC6 guest you're installing, or something else ? > The hardware is a Dell poweredge (I believe an 850), with a single P4, > 4GB of ram and SATA disks. > > The dom0 is a i386 image install of FC6 with all updates. Are you sure ? Because there is no xenguest-install.py in FC6. It got renamed first to xenguest-install, and then to virt-install just before release. FC5 should be the only place where xenguest-install.py is still distributed. What 'xen' RPM version have you got ? Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at xelerance.com Mon Nov 20 18:42:14 2006 From: paul at xelerance.com (Paul Wouters) Date: Mon, 20 Nov 2006 19:42:14 +0100 (CET) Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: <20061120183442.GD15703@redhat.com> References: <20061120183442.GD15703@redhat.com> Message-ID: On Mon, 20 Nov 2006, Daniel P. Berrange wrote: > Is it a FC6 guest you're installing, or something else ? Yes. > > The hardware is a Dell poweredge (I believe an 850), with a single P4, > > 4GB of ram and SATA disks. > > > > The dom0 is a i386 image install of FC6 with all updates. > > Are you sure ? Because there is no xenguest-install.py in FC6. It got > renamed first to xenguest-install, and then to virt-install just before > release. FC5 should be the only place where xenguest-install.py is > still distributed. What 'xen' RPM version have you got ? Uhm yeah. long live tab completion. I didnt even notice. The commandline used was: xenguest-install -n ftp.xtdnet.nl -f /children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi noapic" -r 1024 (the noapic noacpi was a test in the hope tht it would fix my issue). Also, I can still do xm shutdown and then I see the system halting. Paul > Regards, > Dan. > -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From paul at xelerance.com Mon Nov 20 19:36:28 2006 From: paul at xelerance.com (Paul Wouters) Date: Mon, 20 Nov 2006 20:36:28 +0100 (CET) Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: References: <20061120183442.GD15703@redhat.com> Message-ID: On Mon, 20 Nov 2006, Paul Wouters wrote: > xenguest-install -n ftp.xtdnet.nl -f /children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi noapic" -r 1024 > > > (the noapic noacpi was a test in the hope tht it would fix my issue). > > Also, I can still do xm shutdown and then I see the system halting. Using kpartx and losetup, I checked the filesystems. They hasn't been any writing apart from formatting done to the disk. So no logfiles of the anaconda installer to see what went wrong either : Paul From denis.forveille at gmail.com Tue Nov 21 01:14:14 2006 From: denis.forveille at gmail.com (Denis Forveille) Date: Mon, 20 Nov 2006 20:14:14 -0500 Subject: [Fedora-xen] Probems installiing windows under xen in FC6 In-Reply-To: References: Message-ID: <456252E6.1090306@gmail.com> Ian, Did you check the thread called "Win Xp 32 bit as guest in..."? (I missed the ..in x86_64 FC6 dom0) I had (and others too, it seems...) some problems to install Win XP fp2 on my FC6 x86_64 dom0... I finally installed it with qemu...and now I run it directly with xen Maybe the answer is in this thread... (BTW thanks to David Parsley for his help...) Denis Ian Brown wrote: > Hello, > I am trying desperately to install windows under xen in FC6 on x86_64; > my processor has virtulaization extensions (as can be seen from flags of > /proc/cpuinfo). > The kernel I have is the one from the FC6 DVD, 2.6.18-1.2798.fc6xen. > > > I had prepared a configuration file , windows.hvm, which is > given fully in the end of this message. > When I ran : > xm create windows.hvm , there is some window on the screen for a > second then > it is closed. > > On the console I see > xm create windows.hvm > Using config file "/etc/xen/windows.hvm". > Started domain ExampleHVMDomain > and that's it. > > > I am not sure about this line : > disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ] > > I am not sure about something: I do indeed have a sata disk; which is > sda; > but when using qemu, should it also be sda? > > I see in the kernel log the following: > > rh kernel: device tap0 entered promiscuous mode > rh kernel: audit(1163952063.221:41): dev=tap0 prom=256 old_prom=0 > auid=4294967295 > rh kernel: xenbr0: port 3(tap0) entering learning state > rh kernel: xenbr0: topology change detected, propagating > rh kernel: xenbr0: port 3(tap0) entering forwarding state > rh kernel: device vif10.0 entered promiscuous mode > rh kernel: audit(1163952063.589:42): dev=vif10.0 prom=256 old_prom=0 > auid=4294967295 > rh kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready > rh kernel: xenbr0: port 4(vif10.0) entering disabled state > rh kernel: device vif10.0 left promiscuous mode > rh kernel: audit(1163952064.309:43): dev=vif10.0 prom=0 old_prom=256 > auid=4294967295 > rh kernel: xenbr0: port 4(vif10.0) entering disabled state > rh kernel: xenbr0: port 3(tap0) entering disabled state > rh kernel: device tap0 left promiscuous mode > rh kernel: audit(1163952064.469:44): dev=tap0 prom=0 old_prom=256 > auid=4294967295 > rh kernel: xenbr0: port 3(tap0) entering disabled state > > and this is windows.hvm: > > # -*- mode: python; -*- > > import os, re > arch = os.uname()[4] > if re.search('64', arch): > arch_libdir = 'lib64' > else: > arch_libdir = 'lib' > > #---------------------------------------------------------------------------- > > # Kernel image file. > kernel = "/usr/lib/xen/boot/hvmloader" > > # The domain build function. HVM domain uses 'hvm'. > builder='hvm' > > # Initial memory allocation (in megabytes) for the new domain. > # > # WARNING: Creating a domain with insufficient memory may cause out of > # memory errors. The domain needs enough memory to boot kernel > # and modules. Allocating less than 32MBs is not recommended. > #memory = 128 > memory = 384 > > # Shadow pagetable memory for the domain, in MB. > # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. > shadow_memory = 8 > > # A name for your domain. All domains must have different names. > name = "ExampleHVMDomain" > > # 128-bit UUID for the domain. The default behavior is to generate a > new UUID > # on each call to 'xm create'. > #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" > > #----------------------------------------------------------------------------- > > # the number of cpus guest platform has, default=1 > #vcpus=1 > vcpus=1 > # enable/disable HVM guest PAE, default=0 (disabled) > #pae=0 > > # enable/disable HVM guest ACPI, default=0 (disabled) > #acpi=0 > > # enable/disable HVM guest APIC, default=0 (disabled) > #apic=0 > > vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ] > > #---------------------------------------------------------------------------- > > # 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 = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ] > cdrom='/dev/hdb' > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'restart' > #on_reboot = 'destroy' > #on_crash = 'destroy' > ne2000=0 > > #============================================================================ > > > # New stuff > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' > > #----------------------------------------------------------------------------- > > # boot on floppy (a), hard disk (c) or CD-ROM (d) > # default: hard disk, cd-rom, floppy > #boot from cdrom > boot="d" > sdl=1 > vnc=0 > > #---------------------------------------------------------------------------- > > # enable stdvga, default = 0 (use cirrus logic device model) > stdvga=0 > > #----------------------------------------------------------------------------- > > # serial port re-direct to pty deivce, /dev/pts/n > # then xm console or minicom can connect > #serial='pty' > > > #----------------------------------------------------------------------------- > > # set the real time clock to local time [default=0 i.e. set to utc] > #localtime=1 > > > #----------------------------------------------------------------------------- > > # start in full screen > #full-screen=1 > > > #----------------------------------------------------------------------------- > > # Enable USB support (specific devices specified at runtime through the > # monitor window) > usb=1 > > # Enable USB mouse support (only enable one of the following, > `mouse' for > # PS/2 protocol relative mouse, `tablet' for > # absolute mouse) > usbdevice='mouse' > > > any ideas what can cause the problem? > Regards, > Ian > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From robin-lists at robinbowes.com Tue Nov 21 12:02:32 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Tue, 21 Nov 2006 12:02:32 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: Message-ID: Logged as a bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216555 Also see this thread on xen-devel: http://thread.gmane.org/gmane.comp.emulators.xen.devel/32640/focus=32640 This changeset has been applied to fix it: http://xenbits.xensource.com/xen-unstable.hg?cs=0c0ef61de06b R. From berrange at redhat.com Tue Nov 21 12:46:48 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 21 Nov 2006 12:46:48 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: Message-ID: <20061121124648.GC1951@redhat.com> On Tue, Nov 21, 2006 at 12:02:32PM +0000, Robin Bowes wrote: > Logged as a bug: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216555 > > Also see this thread on xen-devel: > > http://thread.gmane.org/gmane.comp.emulators.xen.devel/32640/focus=32640 > > This changeset has been applied to fix it: > > http://xenbits.xensource.com/xen-unstable.hg?cs=0c0ef61de06b If you want to build a new kernel RPM for testing this patch something along the lines of the following should work. 1. Extract the patch file from mercurial hg clone http://xenbits.xensource.com/xen-unstable.hg cd xen-unstable.hg hg log --patch -r 0c0ef61de06b > ~/rpm/SOURCES/large-disks.patch 2. Grab the latest kernel src.rpm file & install it locally rpm -ivh kernel-XXXXXX.src.rpm cd ~/rpm/SPECS 3. Edit the kenrel.spec file, incrementing release tag, Release: %{release}.1xen2tbtest Add Patch30000: large-disks.patch And in the %setup section %patch30000 -p1 4. Rebuild the Xen kernel for i686 rpmbuild --target i686 --define 'buildup 0' --define 'buildsmp 0' --define 'buildkdump 0' -ba kernel-2.6.spec ..wait 30 minutes or so... You should now have a shiny new kernel-xen RPM ready for install in Dom0/DomU Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From heckeler at web.de Tue Nov 21 16:12:07 2006 From: heckeler at web.de (Patrick Heckeler) Date: Tue, 21 Nov 2006 17:12:07 +0100 Subject: [Fedora-xen] Xen and pciback.hide Message-ID: <45632557.70404@web.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, I tried to passthrough a pci-device (network-interface) to my virtual machine. Since the Grub-parameter doesn't work, i used this tutorial for solving the problem: http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module?highlight=%28pciback%29 (the second method) But now it is not possible to passthrough a second and a third interface... (don't know why)... All 4 network-interfaces in my machine (sun fire x4100) are the same (intel 82546EB Gigabit Ethernet Controler). Does anybody know how to passthrough more than 1 pci-device to different vms? Thanks a lot - -- Viele Gr??e Patrick Heckeler Teckstr. 6 72074 T?bingen Germany Mobil: +49172 / 719 23 24 Homezone: +497071 / 28 47 33 email: heckeler [at] web [dot] de skype: p_heckeler ICQ: 200910972 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFYyVX23tKQtXqwP4RAlV/AJ0acKcCuJCy6y/UWozLoLuGYEDOsQCfc2BM +fihDEotKHPa3orLxDqzf/4= =K2t2 -----END PGP SIGNATURE----- From e1geo at yahoo.com Tue Nov 21 18:23:19 2006 From: e1geo at yahoo.com (George Hill) Date: Tue, 21 Nov 2006 10:23:19 -0800 (PST) Subject: [Fedora-xen] anyone running Xen on an AMD chip? Message-ID: <20061121182319.61135.qmail@web53608.mail.yahoo.com> I am running fully virtualized (linux) guests on an Athlon 64 X2 4000+ Socket AM2 (Windsor) chip. When I run a non-Xen kernel the system is stable. When I run Xen with a guest it crashes within 8-10 hours. Is anyone else running on an AMD chip? Any problems? Thanks. From bench at silentmedia.com Tue Nov 21 18:35:52 2006 From: bench at silentmedia.com (Ben) Date: Tue, 21 Nov 2006 10:35:52 -0800 (PST) Subject: [Fedora-xen] anyone running Xen on an AMD chip? In-Reply-To: <20061121182319.61135.qmail@web53608.mail.yahoo.com> References: <20061121182319.61135.qmail@web53608.mail.yahoo.com> Message-ID: It's running just fine on my opterons, but those aren't fully virtualized.... On Tue, 21 Nov 2006, George Hill wrote: > I am running fully virtualized (linux) guests on an Athlon 64 X2 4000+ Socket AM2 (Windsor) chip. When I run a non-Xen kernel the system is stable. When I run Xen with a guest it crashes within 8-10 hours. Is anyone else running on an AMD chip? Any problems? Thanks. > > > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From rstory-l at 2006.revelstone.com Tue Nov 21 18:58:19 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 21 Nov 2006 13:58:19 -0500 Subject: [Fedora-xen] anyone running Xen on an AMD chip? In-Reply-To: <20061121182319.61135.qmail@web53608.mail.yahoo.com> References: <20061121182319.61135.qmail@web53608.mail.yahoo.com> Message-ID: <20061121135819.459f5c15@king.vb.futz.org> On Tue, 21 Nov 2006 10:23:19 -0800 (PST) George wrote: GH> I am running fully virtualized (linux) guests on an Athlon 64 X2 4000+ Socket AM2 (Windsor) chip. When I run a non-Xen kernel the system is stable. When I run Xen with a guest it crashes within 8-10 hours. Is anyone else running on an AMD chip? Any problems? Thanks. Works fine on my old Athalon... From davidsen at tmr.com Fri Nov 17 22:51:24 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Fri, 17 Nov 2006 17:51:24 -0500 Subject: [Fedora-xen] virDomainCreateLinux() failed Message-ID: <455E3CEC.1010806@tmr.com> FC6, xen installed, latest updates as of five minutes ago. ASUS P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. PAE on, virtualization on. xend running, "xm list" works, shows one domain. Install of any fully virtualized o/s fails. Sample output: Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. yes How much RAM should be allocated (in megabytes)? 256 Would you like to enable graphics support? (yes or no) no Starting install... libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: Disk image does not exist: /home/davidsen/Virtual_Machines/OpenBSD-4.0a') Failed to create domain OpenBSD-4.0 Traceback (most recent call last): File "/usr/sbin/xenguest-install", line 396, in ? main() File "/usr/sbin/xenguest-install", line 360, in main dom = guest.start_install(conscb) File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line 355, in start_install self.domain = self.conn.createLinux(cxml, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed') libvirt.libvirtError: virDomainCreateLinux() failed Tried from CD, same error. Tried from xenguest-install and virt-manager, same error. VMware under Windows installs everything, but that's not where I need it installed. Any thoughts? From nig at rhoen.de Tue Nov 21 19:20:24 2006 From: nig at rhoen.de (nig at rhoen.de) Date: Tue, 21 Nov 2006 20:20:24 +0100 Subject: [Fedora-xen] xen fedora 6 on thinkpad t41 Message-ID: <1164136824.4563517866349@bigmama.rhoen.de> Hi, i tried to run fedora 6 and xen on a thinkpad t41, as already stated in http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 this will not work on a t41 because it does not have a PAE enabled cpu. My questions are: 1. Would i be able to run xen on a non-pae cpu when i compile xen myself or is pae cpu a requirement for xen3.0.3 2. If a pae cpu is not requrired by xen 3.0.3, itself, why was the decision taken to not support non-pae cpu under fedora 6 with xen. Thanks Frank From robin-lists at robinbowes.com Tue Nov 21 20:35:38 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Tue, 21 Nov 2006 20:35:38 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: <20061121124648.GC1951@redhat.com> References: <20061121124648.GC1951@redhat.com> Message-ID: Daniel P. Berrange wrote: > If you want to build a new kernel RPM for testing this patch something along > the lines of the following should work. > > 1. Extract the patch file from mercurial > > hg clone http://xenbits.xensource.com/xen-unstable.hg > cd xen-unstable.hg > hg log --patch -r 0c0ef61de06b > ~/rpm/SOURCES/large-disks.patch > > 2. Grab the latest kernel src.rpm file & install it locally > > rpm -ivh kernel-XXXXXX.src.rpm > cd ~/rpm/SPECS > > 3. Edit the kenrel.spec file, incrementing release tag, > > Release: %{release}.1xen2tbtest > > Add > > Patch30000: large-disks.patch > > And in the %setup section > > %patch30000 -p1 > > 4. Rebuild the Xen kernel for i686 > > rpmbuild --target i686 --define 'buildup 0' --define 'buildsmp 0' > --define 'buildkdump 0' -ba kernel-2.6.spec I did this, but the patch failed: Patch #30000 (large-disks.patch): + patch -p1 -s The text leading up to this was: -------------------------- |changeset: 12496:0c0ef61de06b |user: kfraser at localhost.localdomain |date: Tue Nov 21 10:16:58 2006 +0000 |summary: [BLK] Handle block devices with more than 2^32 sectors. | |diff -r 82ba3c086e6c -r 0c0ef61de06b linux-2.6-xen-sparse/drivers/xen/blkback/common.h |--- a/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov 21 09:26:43 2006 +0000 |+++ b/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov 21 10:16:58 2006 +0000 -------------------------- File to patch: To be honest, it was creating the patch that I would struggle with - I'm OK on modifying spec files,etc. Any idea what's wrong? R. From berrange at redhat.com Tue Nov 21 20:50:23 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 21 Nov 2006 20:50:23 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: <20061121124648.GC1951@redhat.com> Message-ID: <20061121205023.GA3438@redhat.com> On Tue, Nov 21, 2006 at 08:35:38PM +0000, Robin Bowes wrote: > Daniel P. Berrange wrote: > > If you want to build a new kernel RPM for testing this patch something along > > the lines of the following should work. > > > > 1. Extract the patch file from mercurial > > > > hg clone http://xenbits.xensource.com/xen-unstable.hg > > cd xen-unstable.hg > > hg log --patch -r 0c0ef61de06b > ~/rpm/SOURCES/large-disks.patch > > > > 2. Grab the latest kernel src.rpm file & install it locally > > > > rpm -ivh kernel-XXXXXX.src.rpm > > cd ~/rpm/SPECS > > > > 3. Edit the kenrel.spec file, incrementing release tag, > > > > Release: %{release}.1xen2tbtest > > > > Add > > > > Patch30000: large-disks.patch > > > > And in the %setup section > > > > %patch30000 -p1 > > > > 4. Rebuild the Xen kernel for i686 > > > > rpmbuild --target i686 --define 'buildup 0' --define 'buildsmp 0' > > --define 'buildkdump 0' -ba kernel-2.6.spec > > I did this, but the patch failed: > > Patch #30000 (large-disks.patch): > + patch -p1 -s > The text leading up to this was: > -------------------------- > |changeset: 12496:0c0ef61de06b > |user: kfraser at localhost.localdomain > |date: Tue Nov 21 10:16:58 2006 +0000 > |summary: [BLK] Handle block devices with more than 2^32 sectors. > | > |diff -r 82ba3c086e6c -r 0c0ef61de06b > linux-2.6-xen-sparse/drivers/xen/blkback/common.h > |--- a/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov > 21 09:26:43 2006 +0000 > |+++ b/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov > 21 10:16:58 2006 +0000 > -------------------------- > File to patch: > > To be honest, it was creating the patch that I would struggle with - I'm > OK on modifying spec files,etc. > > Any idea what's wrong? Wrong patch stripping I think - it should actually be '-p2' instead of '-p1'. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From robin-lists at robinbowes.com Tue Nov 21 21:08:05 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Tue, 21 Nov 2006 21:08:05 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: <20061121205023.GA3438@redhat.com> References: <20061121124648.GC1951@redhat.com> <20061121205023.GA3438@redhat.com> Message-ID: Daniel P. Berrange wrote: > On Tue, Nov 21, 2006 at 08:35:38PM +0000, Robin Bowes wrote: >> I did this, but the patch failed: >> >> Patch #30000 (large-disks.patch): >> + patch -p1 -s >> The text leading up to this was: >> -------------------------- >> |changeset: 12496:0c0ef61de06b >> |user: kfraser at localhost.localdomain >> |date: Tue Nov 21 10:16:58 2006 +0000 >> |summary: [BLK] Handle block devices with more than 2^32 sectors. >> | >> |diff -r 82ba3c086e6c -r 0c0ef61de06b >> linux-2.6-xen-sparse/drivers/xen/blkback/common.h >> |--- a/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov >> 21 09:26:43 2006 +0000 >> |+++ b/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov >> 21 10:16:58 2006 +0000 >> -------------------------- >> File to patch: >> >> To be honest, it was creating the patch that I would struggle with - I'm >> OK on modifying spec files,etc. >> >> Any idea what's wrong? > > Wrong patch stripping I think - it should actually be '-p2' instead > of '-p1'. I tried -p2 - same problem. R. From ed.jimison at intel.com Tue Nov 21 23:06:11 2006 From: ed.jimison at intel.com (Jimison, Ed) Date: Tue, 21 Nov 2006 15:06:11 -0800 Subject: [Fedora-xen] error when trying to connect with virt-manager Message-ID: <395DB1DBC1F0E4499EA739E0919759D3BBB8C5@fmsmsx412.amr.corp.intel.com> I am doing a new install of Fedora Core 6, trying to use the virt-manager app to create fully virtualized guests on an Intel VT-enabled system. I have read the Fedora Xen Quickstart guide and have verified that the Xen kernel is running (via uname -r) and that Xen is started (via xm list). After starting virt-manager, clicking "Local Xen host" in the Open connection box, and clicking Connect I get the following error: Unable to open a connection to the Xen hypervisor/daemon Verify that: - A Xen host kernel was booted - The Xen service has been started Has anyone else seen this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin-lists at robinbowes.com Tue Nov 21 23:07:03 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Tue, 21 Nov 2006 23:07:03 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: <20061121124648.GC1951@redhat.com> <20061121205023.GA3438@redhat.com> Message-ID: Robin Bowes wrote: > Daniel P. Berrange wrote: >> On Tue, Nov 21, 2006 at 08:35:38PM +0000, Robin Bowes wrote: >>> Any idea what's wrong? >> Wrong patch stripping I think - it should actually be '-p2' instead >> of '-p1'. > > I tried -p2 - same problem. Daniel, I'm really struggling here - I can't seem to get the original patch to apply, even manually. I tried this: Created ~/rpmbuild/SOURCES/xen-large-disk.patch using the content here: http://xenbits.xensource.com/xen-unstable.hg?cs=0c0ef61de06b Installed kernel-2.6.18-1.2849.fc6.src.rpm. Ran "rpmbuild -bp ~/rpmbuild/SPECS/kernel-xen.spec" Switched to ~/rpmbuild/BUILD/kernel-2.6.18 Ran patch -p2 < ../../SOURCES/xen-large-disks.patch Result: can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov 21 09:26:43 2006 +0000 |+++ b/linux-2.6-xen-sparse/drivers/xen/blkback/common.h Tue Nov 21 10:16:58 2006 +0000 -------------------------- File to patch: Any idea what I'm doing wrong here? R. From berrange at redhat.com Tue Nov 21 23:51:07 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 21 Nov 2006 23:51:07 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: <20061121124648.GC1951@redhat.com> <20061121205023.GA3438@redhat.com> Message-ID: <20061121235107.GD3438@redhat.com> On Tue, Nov 21, 2006 at 11:07:03PM +0000, Robin Bowes wrote: > Robin Bowes wrote: > > Daniel P. Berrange wrote: > >> On Tue, Nov 21, 2006 at 08:35:38PM +0000, Robin Bowes wrote: > >>> Any idea what's wrong? > >> Wrong patch stripping I think - it should actually be '-p2' instead > >> of '-p1'. > > > > I tried -p2 - same problem. > > Daniel, > > I'm really struggling here - I can't seem to get the original patch to > apply, even manually. I've created a src.rpm from latest FC6 kernel including the neccessary patch & uploaded it here: http://people.redhat.com/berrange/kernel-2.6.18-1.2849.1dan2tb.src.rpm You can just grab it and run rpmbuild --rebuild --target i686 kernel-2.6.18-1.2849.1dan2tb.src.rpm Due to disk space limitations I'll be removing it from this URL after a day or two... Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From robin-lists at robinbowes.com Wed Nov 22 01:29:12 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 22 Nov 2006 01:29:12 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: <20061121235107.GD3438@redhat.com> References: <20061121124648.GC1951@redhat.com> <20061121205023.GA3438@redhat.com> <20061121235107.GD3438@redhat.com> Message-ID: Daniel P. Berrange wrote: > > I've created a src.rpm from latest FC6 kernel including the neccessary > patch & uploaded it here: > > http://people.redhat.com/berrange/kernel-2.6.18-1.2849.1dan2tb.src.rpm > > You can just grab it and run > > rpmbuild --rebuild --target i686 kernel-2.6.18-1.2849.1dan2tb.src.rpm > > Due to disk space limitations I'll be removing it from this URL after a > day or two... Dan, Thanks for this. I've grabbed it anyway, even though I've managed to get this to work. It was just a matter of getting into the right directory: cd ../linux-%{kversion}.%{_target_cpu} %patch30000 -p2 The kernel rebuild is chugging away as I type. Thanks again. R. From tancs at comp.nus.edu.sg Wed Nov 22 01:51:08 2006 From: tancs at comp.nus.edu.sg (Tan Chee Sin) Date: Wed, 22 Nov 2006 09:51:08 +0800 Subject: [Fedora-xen] Cannot create files or dirs even as root on FC6 xen system Message-ID: <4563AD0C.10309@comp.nus.edu.sg> Hi, I've installed a FC6 xen guest system and there is a /misc folder which I want to create files and directories. I get a permission denied when I try to do so even when I am root. # pwd /misc # mkdir test mkdir: cannot create directory `test': Permission denied When I do a directoy listing on /, misc is 0 bytes. drwxr-xr-x 2 root root 0 Nov 21 13:24 misc I have listed the disk space usage and the fstab below. # df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda1 11904588 1830176 9459928 17% / tmpfs 768000 0 768000 0% /dev/shm /dev/xvda3 5431008 171288 4979388 4% /var # cat /etc/fstab LABEL=/1 / ext3 defaults 1 1 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 LABEL=/var /var ext3 defaults 1 2 LABEL=SWAP-xvda2 swap swap defaults 0 0 I'm not sure if this issue happens only on FC6 xen but I am able to create files and directories on a FC5 xen system. cheesin From craig at trader.name Wed Nov 22 03:47:16 2006 From: craig at trader.name (W Craig Trader) Date: Tue, 21 Nov 2006 22:47:16 -0500 Subject: [Fedora-xen] Cannot create files or dirs even as root on FC6 xen system In-Reply-To: <4563AD0C.10309@comp.nus.edu.sg> References: <4563AD0C.10309@comp.nus.edu.sg> Message-ID: <4563C844.5070808@trader.name> Cheesin ... Do you have the autofs daemon running, and does your /etc/auto.master file reference mounting devices on /misc, using the definitions in /etc/auto.misc? Once upon a time, RedHat Linux used autofs to dynamically mount the CDROM on /misc/cdrom; if you've got an older system that's been upgraded, you might still have a remnant of that style of configuration. If you run "ps aux | grep automount", it will show you which mappings are active; if you see something like "/usr/sbin/automount --timeout=60 /misc program /etc/auto.misc" you've found the culprit. - Craig - Tan Chee Sin wrote: > Hi, > > I've installed a FC6 xen guest system and there is a /misc folder > which I want to create files and directories. I get a permission > denied when I try to do so even when I am root. > > # pwd > /misc > # mkdir test > > mkdir: cannot create directory `test': Permission denied > > When I do a directoy listing on /, misc is 0 bytes. > > drwxr-xr-x 2 root root 0 Nov 21 13:24 misc > > I have listed the disk space usage and the fstab below. > # df -k > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/xvda1 11904588 1830176 9459928 17% / > tmpfs 768000 0 768000 0% /dev/shm > /dev/xvda3 5431008 171288 4979388 4% /var > > # cat /etc/fstab > LABEL=/1 / ext3 > defaults 1 1 > devpts /dev/pts devpts > gid=5,mode=620 0 0 > tmpfs /dev/shm tmpfs > defaults 0 0 > proc /proc proc > defaults 0 0 > sysfs /sys sysfs > defaults 0 0 > LABEL=/var /var ext3 > defaults 1 2 > LABEL=SWAP-xvda2 swap swap > defaults 0 0 > > I'm not sure if this issue happens only on FC6 xen but I am able to > create files and directories on a FC5 xen system. > > cheesin > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From anna.fischer at hp.com Wed Nov 22 07:37:59 2006 From: anna.fischer at hp.com (Fischer, Anna) Date: Wed, 22 Nov 2006 07:37:59 -0000 Subject: [Fedora-xen] error when trying to connect with virt-manager In-Reply-To: <395DB1DBC1F0E4499EA739E0919759D3BBB8C5@fmsmsx412.amr.corp.intel.com> Message-ID: <86FE9B2B91ADD04095335314BE6906E897FB90@sdcexc04.emea.cpqcorp.net> I have the same problem, with xend + Xen kernel running and the xend-config.sxp configured accordingly by setting either (xend-http-server yes) or (xend-unix-server yes). But still I can't get virt-manager to run. I hope someone can help here... ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Jimison, Ed Sent: 21 November 2006 23:06 To: fedora-xen at redhat.com Subject: [Fedora-xen] error when trying to connect with virt-manager I am doing a new install of Fedora Core 6, trying to use the virt-manager app to create fully virtualized guests on an Intel VT-enabled system. I have read the Fedora Xen Quickstart guide and have verified that the Xen kernel is running (via uname -r) and that Xen is started (via xm list). After starting virt-manager, clicking "Local Xen host" in the Open connection box, and clicking Connect I get the following error: Unable to open a connection to the Xen hypervisor/daemon Verify that: - A Xen host kernel was booted - The Xen service has been started Has anyone else seen this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bhkwan at thoughtworks.com Wed Nov 22 07:40:57 2006 From: bhkwan at thoughtworks.com (Barrow H Kwan) Date: Tue, 21 Nov 2006 23:40:57 -0800 Subject: [Fedora-xen] Can't allocate memory (12) Message-ID: This happen when I tried to create a Windows Guest. After few days of struggling, I just found out Domain-0 has been assigned 99% of the physical memory "BY DEFAUT". I am wondering 1. Why does Fedora assign 99% to all phsical memory to Domain-0 ? 2. Why does this memory allocation error happen with the Windows Guest? Barrow From robin-lists at robinbowes.com Wed Nov 22 10:43:01 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Wed, 22 Nov 2006 10:43:01 +0000 Subject: [Fedora-xen] Re: Using large disk in DomU In-Reply-To: References: <20061121124648.GC1951@redhat.com> <20061121205023.GA3438@redhat.com> <20061121235107.GD3438@redhat.com> Message-ID: I installed the patched kernel and xen RPMS this morning and can confirm that this fixed my problem. I can now see my 2.7TB partition correctly in the DomU guest. Thanks to all for the quick fix, and to Dan for help with building the modified kernel RPM. R. From berrange at redhat.com Wed Nov 22 12:07:29 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Nov 2006 12:07:29 +0000 Subject: [Fedora-xen] error when trying to connect with virt-manager In-Reply-To: <86FE9B2B91ADD04095335314BE6906E897FB90@sdcexc04.emea.cpqcorp.net> References: <395DB1DBC1F0E4499EA739E0919759D3BBB8C5@fmsmsx412.amr.corp.intel.com> <86FE9B2B91ADD04095335314BE6906E897FB90@sdcexc04.emea.cpqcorp.net> Message-ID: <20061122120729.GB13945@redhat.com> On Wed, Nov 22, 2006 at 07:37:59AM -0000, Fischer, Anna wrote: > I have the same problem, with xend + Xen kernel running and the > xend-config.sxp configured accordingly by setting either > > (xend-http-server yes) or Don't turn this on - it is a (remotely exploitable) security hole because it makes XenD open a TCP port with no authentication checks made upon connection :-( > (xend-unix-server yes). This is the required parameter for virt-manager. > But still I can't get virt-manager to run. I hope someone can help > here... Check in /root/.virt-manager/virt-manager.log for any errors being reported. Also just try running 'virsh list' which is a simple sanity test for libvirt operating correctly. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Wed Nov 22 12:12:27 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Nov 2006 12:12:27 +0000 Subject: [Fedora-xen] Can't allocate memory (12) In-Reply-To: References: Message-ID: <20061122121227.GC13945@redhat.com> On Tue, Nov 21, 2006 at 11:40:57PM -0800, Barrow H Kwan wrote: > > This happen when I tried to create a Windows Guest. After few days of > struggling, I just found out Domain-0 has been assigned 99% of the physical > memory "BY DEFAUT". I am wondering > > 1. Why does Fedora assign 99% to all phsical memory to Domain-0 ? Dom0 gets essentially 100% of all memory at boot time. XenD will use the balloon driver to take memory away from Dom0 when it is needed to launch a new guest. Of course this relies on you not actively using that memory in Dom0 but in general it just works. If balooning were failing though you would see a different error - one saying it was unable to balloon down the dom0. The 'cannot allocate memory' error suggests a more fundamental problem. > 2. Why does this memory allocation error happen with the Windows Guest? Running 'xm dmesg' shortly after creating the guest may be helpful in tracking down actual errors. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Wed Nov 22 12:18:52 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Nov 2006 12:18:52 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <456434FB.6050005@sun.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> Message-ID: <20061122121852.GE13945@redhat.com> On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote: > Hi Daniel, > > Here I have another question on virt-manager, as you write "an embedded > VNC client viewer provides console access to each of the guest domains", > my concern is where is the vnc server, who provide it, and start it? > Need we setup vnc? I looked through the process used to create guest, > seems there is no any step for vnc... The VNC server depends on what type of domain is being run. For HVM guests the VNC server is provided by the qemu-dm process assoicated with that guest. For paravirt guests, VNC is only available if you have the paravirt framebuffer patches applied to your xen tree - these are not in xen-unstable yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC server. So in both case all you need to do is set 'vnc=1' in the guest config file & XenD will ensure the VNC servers are started as required. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From anna.fischer at hp.com Wed Nov 22 12:27:01 2006 From: anna.fischer at hp.com (Fischer, Anna) Date: Wed, 22 Nov 2006 12:27:01 -0000 Subject: [Fedora-xen] error when trying to connect with virt-manager In-Reply-To: <20061122120729.GB13945@redhat.com> Message-ID: <86FE9B2B91ADD04095335314BE6906E897FC4A@sdcexc04.emea.cpqcorp.net> The log says: Wed, 22 Nov 2006 12:17:44 ERROR Unable to open connection to hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not known') "virsh list" runs perfect on my system. Furthermore, a strange thing is that while this error message window is shown when virt-manager starts up, I can see in the background (virt-manager GUI is actually loaded while showing the error message) that virt-manager shows Dom0 and its CPU usage etc. correctly. So why do I get this error message then and virt-manager shuts down? > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com] > Sent: 22 November 2006 12:07 > To: Fischer, Anna > Cc: Jimison, Ed; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] error when trying to connect with > virt-manager > > On Wed, Nov 22, 2006 at 07:37:59AM -0000, Fischer, Anna wrote: > > I have the same problem, with xend + Xen kernel running and the > > xend-config.sxp configured accordingly by setting either > > > > (xend-http-server yes) or > > Don't turn this on - it is a (remotely exploitable) security > hole because it makes XenD open a TCP port with no > authentication checks made upon connection :-( > > > (xend-unix-server yes). > > This is the required parameter for virt-manager. > > > But still I can't get virt-manager to run. I hope someone can help > > here... > > Check in /root/.virt-manager/virt-manager.log for any errors > being reported. Also just try running 'virsh list' which is a > simple sanity test for libvirt operating correctly. > > Regards, > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 > 978 392 2496 -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF > F742 7D3B 9505 -=| > From xmlsec at gmail.com Wed Nov 22 12:46:57 2006 From: xmlsec at gmail.com (Kenneth Jensen) Date: Wed, 22 Nov 2006 13:46:57 +0100 Subject: [Fedora-xen] xen fedora 6 on thinkpad t41 In-Reply-To: <1164136824.4563517866349@bigmama.rhoen.de> References: <1164136824.4563517866349@bigmama.rhoen.de> Message-ID: I 'm not qualified to comment on 1) as I haven't tried, but... Wrt. 2, I believe that the Fedora team decided to drop non-PAE support because of the extra work required in maintaining two branches of kernel patches (xen and xen0/xenU kernels). One argument I read, was that since most of the latest generation CPUs are PAE capable there wouldn't be much harm done.... At least that how I understood it, after sifting through a bunch of mailinglists, releasefiles and changelogs. Btw. I found out about this only after I had upgraded my T42p to FC6. :-) It kind of sucks that a 2 year old top-of-the-line laptop is now "outdated"... Cheers, Kenneth On 11/21/06, nig at rhoen.de wrote: > Hi, > > i tried to run fedora 6 and xen on a thinkpad t41, > as already stated in http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 > this will not work on a t41 because it does not have a PAE enabled cpu. > > My questions are: > > 1. Would i be able to run xen on a non-pae cpu when i compile xen myself or > is > pae cpu a requirement for xen3.0.3 > > 2. If a pae cpu is not requrired by xen 3.0.3, itself, why was the decision > taken to not support non-pae cpu under fedora 6 with xen. > > Thanks > > Frank > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- --- Cheers, Kenneth From adrian at creative.net.au Wed Nov 22 13:24:44 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Wed, 22 Nov 2006 21:24:44 +0800 Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? Message-ID: <20061122132444.GI14185@skywalker.creative.net.au> Hiya, I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development and regression testing on. Has anyone done this? Any pointers to what I should be looking at doing? Bootstrapping Debian under Debian wasn't too hard - just debootstrap into a new filesystem, then start domU up to finish configuration. I've had absolutely no luck with the FC5 and FC6 supplied xenguest-install python stuff to bootstrap PVM guests. Thanks, Adrian From berrange at redhat.com Wed Nov 22 13:32:53 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Nov 2006 13:32:53 +0000 Subject: [Fedora-xen] error when trying to connect with virt-manager In-Reply-To: <86FE9B2B91ADD04095335314BE6906E897FC4A@sdcexc04.emea.cpqcorp.net> References: <20061122120729.GB13945@redhat.com> <86FE9B2B91ADD04095335314BE6906E897FC4A@sdcexc04.emea.cpqcorp.net> Message-ID: <20061122133253.GA11685@redhat.com> On Wed, Nov 22, 2006 at 12:27:01PM -0000, Fischer, Anna wrote: > The log says: > > Wed, 22 Nov 2006 12:17:44 ERROR Unable to open connection to > hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not known') Hmm, sounds like you have a messed up /etc/hosts file - check that the line for '127.0.0.1' has a name 'localhost' associated with it, eg $ cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost ::1 localhost.localdomain localhost > > "virsh list" runs perfect on my system. Furthermore, a strange thing is > that while this error message window is shown when virt-manager starts > up, I can see in the background (virt-manager GUI is actually loaded > while showing the error message) that virt-manager shows Dom0 and its > CPU usage etc. correctly. So why do I get this error message then and > virt-manager shuts down? Its it failing to lookup 'localhost' when opening the console for the guest I think. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From anna.fischer at hp.com Wed Nov 22 14:37:46 2006 From: anna.fischer at hp.com (Fischer, Anna) Date: Wed, 22 Nov 2006 14:37:46 -0000 Subject: [Fedora-xen] error when trying to connect with virt-manager In-Reply-To: <20061122133253.GA11685@redhat.com> Message-ID: <86FE9B2B91ADD04095335314BE6906E897FC8F@sdcexc04.emea.cpqcorp.net> Yes, you were right. It was in fact a name resolution problem. Now it works fine. Thanks!! > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange at redhat.com] > Sent: 22 November 2006 13:33 > To: Fischer, Anna > Cc: Jimison, Ed; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] error when trying to connect with > virt-manager > > On Wed, Nov 22, 2006 at 12:27:01PM -0000, Fischer, Anna wrote: > > The log says: > > > > Wed, 22 Nov 2006 12:17:44 ERROR Unable to open connection to > > hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not > > known') > > Hmm, sounds like you have a messed up /etc/hosts file - check > that the line for '127.0.0.1' has a name 'localhost' > associated with it, eg > > $ cat /etc/hosts > # Do not remove the following line, or various programs # > that require network functionality will fail. > 127.0.0.1 localhost.localdomain localhost > ::1 localhost.localdomain localhost > > > > > > "virsh list" runs perfect on my system. Furthermore, a > strange thing > > is that while this error message window is shown when virt-manager > > starts up, I can see in the background (virt-manager GUI is > actually > > loaded while showing the error message) that virt-manager > shows Dom0 > > and its CPU usage etc. correctly. So why do I get this > error message > > then and virt-manager shuts down? > > Its it failing to lookup 'localhost' when opening the console > for the guest I think. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 > 978 392 2496 -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF > F742 7D3B 9505 -=| > From emailme at monolive.org Wed Nov 22 16:06:56 2006 From: emailme at monolive.org (Monolive) Date: Wed, 22 Nov 2006 17:06:56 +0100 Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? In-Reply-To: <20061122132444.GI14185@skywalker.creative.net.au> References: <20061122132444.GI14185@skywalker.creative.net.au> Message-ID: <456475A0.3010100@monolive.org> Adrian Chadd wrote: > Hiya, > > I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development > and regression testing on. Has anyone done this? Any pointers to what I should be > looking at doing? > > Bootstrapping Debian under Debian wasn't too hard - just debootstrap into a new > filesystem, then start domU up to finish configuration. I've had absolutely no luck > with the FC5 and FC6 supplied xenguest-install python stuff to bootstrap PVM guests. > > Thanks, > > > > Adrian > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > You will find some good documentation @ http://people.redhat.com/~riel/RHEL4-Xen-HOWTO If you do not have a processor with the VT extension, you can always use qemu to install RHEL4 in FV. As written in the doc, you will need to use the kernel from http://people.redhat.com/~jbaron/rhel4/RPMS.kernel/ Have fun, Mono From davidsen at tmr.com Tue Nov 21 22:05:30 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Tue, 21 Nov 2006 17:05:30 -0500 Subject: [Fedora-xen] Re: virDomainCreateLinux() failed In-Reply-To: <455E3CEC.1010806@tmr.com> References: <455E3CEC.1010806@tmr.com> Message-ID: <4563782A.8010804@tmr.com> Bill Davidsen wrote: > FC6, xen installed, latest updates as of five minutes ago. ASUS > P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. > PAE on, virtualization on. xend running, "xm list" works, shows one domain. > > > Install of any fully virtualized o/s fails. Sample output: > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes > How much RAM should be allocated (in megabytes)? 256 > Would you like to enable graphics support? (yes or no) no > > > Starting install... > libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 > libvir: Xen Daemon error : POST operation failed: (xend.err 'Error > creating domain: Disk image does not exist: > /home/davidsen/Virtual_Machines/OpenBSD-4.0a') NOTE: yes it does... > Failed to create domain OpenBSD-4.0 > Traceback (most recent call last): > File "/usr/sbin/xenguest-install", line 396, in ? > main() > File "/usr/sbin/xenguest-install", line 360, in main > dom = guest.start_install(conscb) > File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line 355, > in start_install > self.domain = self.conn.createLinux(cxml, 0) > File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed') > libvirt.libvirtError: virDomainCreateLinux() failed > > Tried from CD, same error. Tried from xenguest-install and virt-manager, > same error. > VMware under Windows installs everything, but that's not where I need it > installed. > > Any thoughts? > Seems to work with qemu, for what that's worth. -- Bill Davidsen Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion. From davidsen at tmr.com Tue Nov 21 22:07:29 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Tue, 21 Nov 2006 17:07:29 -0500 Subject: [Fedora-xen] Re: xen fedora 6 on thinkpad t41 In-Reply-To: <1164136824.4563517866349@bigmama.rhoen.de> References: <1164136824.4563517866349@bigmama.rhoen.de> Message-ID: <456378A1.1040107@tmr.com> nig at rhoen.de wrote: > Hi, > > i tried to run fedora 6 and xen on a thinkpad t41, > as already stated in http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 > this will not work on a t41 because it does not have a PAE enabled cpu. > > My questions are: > > 1. Would i be able to run xen on a non-pae cpu when i compile xen myself or is > pae cpu a requirement for xen3.0.3 > > 2. If a pae cpu is not requrired by xen 3.0.3, itself, why was the decision > taken to not support non-pae cpu under fedora 6 with xen. > > Thanks > > Frank > I read that the old FC5 0 and U kernels work. Haven't tried. -- Bill Davidsen Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion. From davidsen at tmr.com Wed Nov 22 00:01:40 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Tue, 21 Nov 2006 19:01:40 -0500 Subject: [Fedora-xen] virDomainCreateLinux() failed In-Reply-To: References: <455E3CEC.1010806@tmr.com> Message-ID: <45639364.2080703@tmr.com> Paul Wouters wrote: > On Fri, 17 Nov 2006, Bill Davidsen wrote: > > >> FC6, xen installed, latest updates as of five minutes ago. ASUS P5LD2-R2.0 >> board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >> PAE on, virtualization on. xend running, "xm list" works, shows one domain. >> > > does not mention "selinux disabled" > If that's needed it somewhat conflicts with the idea for running things in virtual machines for added security :-( I thought that was a non-issue with 2.6.18, but I may be wrong. > >> libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating >> domain: Disk image does not exist: >> /home/davidsen/Virtual_Machines/OpenBSD-4.0a') >> > > And that's not in /xen/ > Hopefully doesn't have to be. Having all projects in a single place just begs for name clash and visibility exposure issues. The browse didn't have any trouble finding the file, at minimum probably a bug if it allows me to select a file I can't use. > I think that used to be an issue with selinux. not sure if it still is. > Thanks for the ideas, I was hoping to use xen instead of VMware, but when I did a project a few years ago I don't recall it being particularly inflexible. I'll try just moving the disk image file and running with that. Again, many thanks. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From Hua.Zhang at Sun.COM Wed Nov 22 11:31:07 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Wed, 22 Nov 2006 19:31:07 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061106044542.GA28547@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> Message-ID: <456434FB.6050005@sun.com> Hi Daniel, Here I have another question on virt-manager, as you write "an embedded VNC client viewer provides console access to each of the guest domains", my concern is where is the vnc server, who provide it, and start it? Need we setup vnc? I looked through the process used to create guest, seems there is no any step for vnc... Thanks, Henry Daniel P. Berrange ??: > On Mon, Nov 06, 2006 at 10:51:21AM +0800, Henry Zhang wrote: > >> Thanks, Dan. >> >> so for "pygtk2 >= 1.99.12-6", it means 1.99.12 - 1.6? >> And I can say if we want virt-manager to run, pygtk2 1.99.12 can be OK, >> right? >> > > These version numbers refer to the RPM versions - so 1.99.12-6 refers > to pygtk2 1.99.12, with RPM release number 6. So for non-RPM builds > just look at the first component - 1.99.12 > > >> BTW, I found these 2 requirements are different, for example, I can't >> find Matplotlib in download.html. So could you mind giving me a total >> list, including Pre-requisites and its earlist version, on what we need >> to build and run virt-manager? >> > > Again, the 'download.html' page is the most accurate - it does > not list matplotlib since we no longer have that as a requirement, > the faq.html page is outdated in this respect. The version numbers > documented are the earliest that I have personally tested & verified > against. It may well run fine against even earlier versions - I just > haven't had opportunity to verify - if you find it does work against > earlier versions of particular software let me know & i'll update > the docs. > > >> Daniel P. Berrange ??????: >> >>> On Mon, Nov 06, 2006 at 01:22:58AM +0800, Henry Zhang wrote: >>> >>>> I am a little confused on the Pre-requisites for virt-manager, because I >>>> am finding two: >>>> >>>> 1. at http://virt-manager.et.redhat.com/faq.html, under "What other >>>> libraries are needed prior to installing "Virtual Machine Manager"?" >>>> >>>> 2. and find another one under "Pre-requisites" at >>>> http://virt-manager.et.redhat.com/download.html >>>> >>>> I am thinking 2 is a general one for all version of virt-manager, and 1 >>>> is exactly indicating the requirement before running latest virt-manger. >>>> is it correct? >>>> >>>> >>> The list on the download.html page is more up2date / accurate - I'll fix >>> the list under the faq.html to match this. >>> > > Regards, > Dan. > From berrange at redhat.com Wed Nov 22 16:35:59 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 22 Nov 2006 16:35:59 +0000 Subject: [Fedora-xen] virDomainCreateLinux() failed In-Reply-To: <455E3CEC.1010806@tmr.com> References: <455E3CEC.1010806@tmr.com> Message-ID: <20061122163559.GF11685@redhat.com> On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote: > FC6, xen installed, latest updates as of five minutes ago. ASUS > P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. > PAE on, virtualization on. xend running, "xm list" works, shows one domain. > > > Install of any fully virtualized o/s fails. Sample output: > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes > How much RAM should be allocated (in megabytes)? 256 > Would you like to enable graphics support? (yes or no) no > > > Starting install... > libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 > libvir: Xen Daemon error : POST operation failed: (xend.err 'Error > creating domain: Disk image does not exist: > /home/davidsen/Virtual_Machines/OpenBSD-4.0a') In FC6 GA you have to make sure the file for the disk was under /xen to be labelled correctly. In rawhide (and the latest FC6 policy) we're moving to /var/lib/xen/images. This is consistent with the directory used on Suse, and what the next version of XenD will enforce. To double check what directory is setup for the SELinux policy you can run semanage fcontext -l | grep xen_image_t If you don't have space under /var/lib/xen/images, then either mount a new volume there, or bind that dir to a location which has extra space, eg mount --bind /some/dir/with/big/disk /var/lib/xen/images If you really really don't want to use /var/lib/xen/images at all, then you can define a new location in the SELinux policy using: semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From bhkwan at thoughtworks.com Wed Nov 22 16:42:10 2006 From: bhkwan at thoughtworks.com (Barrow H Kwan) Date: Wed, 22 Nov 2006 08:42:10 -0800 Subject: [Fedora-xen] Can't allocate memory (12) In-Reply-To: <20061122121227.GC13945@redhat.com> Message-ID: here are more information about the issue When all memories are allocated to Dom0, I can add Paravirtualized Guest OS but this limited to Linux OS ( I mean I don't know if it is possible to run Windows as a Paravirtualized VM ). If I tried to add a FULLY Virtualized Guest OS, I will get this error. To fix this, I have to change the memory for Dom0 ( under Grub ). I have a 16G box and when I assigned 14G to the Dom0, then I can add a Fully Virtuallized Windows Guest OS with 1.5G memory. When I tried to add another Windows Guest OS with 1G memory, I got the same memory error again. My guess is the number of fully virtualized Windows Guest OS I can run will depend on the "phyical" memory that I have. for example, if I have a 16G box, if I allocate 4G memory for a Windows Guest OS, I can only run 4 of them ( ie 4 x 4G = 16G ). Unless this is a problem with the FC6's Xen. "Daniel P. Berrange" Barrow H Kwan 11/22/2006 04:12 cc AM fedora-xen at redhat.com Subject Re: [Fedora-xen] Can't allocate Please respond to memory (12) "Daniel P. Berrange" On Tue, Nov 21, 2006 at 11:40:57PM -0800, Barrow H Kwan wrote: > > This happen when I tried to create a Windows Guest. After few days of > struggling, I just found out Domain-0 has been assigned 99% of the physical > memory "BY DEFAUT". I am wondering > > 1. Why does Fedora assign 99% to all phsical memory to Domain-0 ? Dom0 gets essentially 100% of all memory at boot time. XenD will use the balloon driver to take memory away from Dom0 when it is needed to launch a new guest. Of course this relies on you not actively using that memory in Dom0 but in general it just works. If balooning were failing though you would see a different error - one saying it was unable to balloon down the dom0. The 'cannot allocate memory' error suggests a more fundamental problem. > 2. Why does this memory allocation error happen with the Windows Guest? Running 'xm dmesg' shortly after creating the guest may be helpful in tracking down actual errors. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From bhkwan at thoughtworks.com Wed Nov 22 17:06:53 2006 From: bhkwan at thoughtworks.com (Barrow H Kwan) Date: Wed, 22 Nov 2006 09:06:53 -0800 Subject: [Fedora-xen] Can't allocate memory (12) In-Reply-To: Message-ID: I need to make a clarification. This is not only applied to Windows Guest OS. If all the "Physical" memory has assigned to Dom0, I can't add any Fully virtualized Guest OS. I got "virDomainCreateLinux() failed' from virt-manager or Can't allocated memory error from shell ( xm create -c win2k3 ) Paravirtualized Guest OS is fine but like I said I can't find a way to create a Windows Paravirtualized Guest OS. Barrow H Kwan To Sent by: "Daniel P. Berrange" fedora-xen-bounce s at redhat.com cc fedora-xen at redhat.com Subject 11/22/2006 08:42 Re: [Fedora-xen] Can't allocate AM memory (12) here are more information about the issue When all memories are allocated to Dom0, I can add Paravirtualized Guest OS but this limited to Linux OS ( I mean I don't know if it is possible to run Windows as a Paravirtualized VM ). If I tried to add a FULLY Virtualized Guest OS, I will get this error. To fix this, I have to change the memory for Dom0 ( under Grub ). I have a 16G box and when I assigned 14G to the Dom0, then I can add a Fully Virtuallized Windows Guest OS with 1.5G memory. When I tried to add another Windows Guest OS with 1G memory, I got the same memory error again. My guess is the number of fully virtualized Windows Guest OS I can run will depend on the "phyical" memory that I have. for example, if I have a 16G box, if I allocate 4G memory for a Windows Guest OS, I can only run 4 of them ( ie 4 x 4G = 16G ). Unless this is a problem with the FC6's Xen. "Daniel P. Berrange" Barrow H Kwan 11/22/2006 04:12 cc AM fedora-xen at redhat.com Subject Re: [Fedora-xen] Can't allocate Please respond to memory (12) "Daniel P. Berrange" On Tue, Nov 21, 2006 at 11:40:57PM -0800, Barrow H Kwan wrote: > > This happen when I tried to create a Windows Guest. After few days of > struggling, I just found out Domain-0 has been assigned 99% of the physical > memory "BY DEFAUT". I am wondering > > 1. Why does Fedora assign 99% to all phsical memory to Domain-0 ? Dom0 gets essentially 100% of all memory at boot time. XenD will use the balloon driver to take memory away from Dom0 when it is needed to launch a new guest. Of course this relies on you not actively using that memory in Dom0 but in general it just works. If balooning were failing though you would see a different error - one saying it was unable to balloon down the dom0. The 'cannot allocate memory' error suggests a more fundamental problem. > 2. Why does this memory allocation error happen with the Windows Guest? Running 'xm dmesg' shortly after creating the guest may be helpful in tracking down actual errors. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From ian.patton at gmail.com Wed Nov 22 21:06:48 2006 From: ian.patton at gmail.com (Ian Patton) Date: Wed, 22 Nov 2006 16:06:48 -0500 Subject: [Fedora-xen] Running Windows Vista RC1 in Xen on FC6 Message-ID: <1579d8590611221306vbca89ecoe99a2dbcd1c159a8@mail.gmail.com> Hello All, I am trying to get Windows Vista RC1 to run in Xen. I had it working fine when I first tried it. I installed an update to Xen when it came out an now my virt-manager says: Unable to open a connection to the Xen hypervisor/daemon. Verify that: - A Xen host kernel was booted - The Xen service has been started Of course I verified those and I have Intel VT turned on in the BIOS. What is funny is that I can see Dom0 running in virt-manager behind the error. As soon as I close the error, virt-manager closes. I can provide any additional info as needed. Any ideas? Following similar threads, I ran 'virsh list' and it shows Dom0 running fine. 'xm top' shows it running fine as well. Looking at /root/.virt-manager/virt-manager.log, I see this error: Unable to open connection to hypervisor URI 'xen': socket.gaierror (-3, 'Temporary failure in name resolution') I did rename my system after creating it... What's the fix? Thanks in advance! Ian -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From turner at ftn.net Wed Nov 22 22:05:32 2006 From: turner at ftn.net (turner at ftn.net) Date: Wed, 22 Nov 2006 17:05:32 -0500 (EST) Subject: [Fedora-xen] Xen + LVM + OS image Message-ID: Hello all, I have a setup that I have been testing to create a FC6 guest image on a lvm logical volume (lv) and then use that to deploy new a new guest. I wanted to get feedback about anything that I might have overlooked. In a nutshell, each xen guest install has it's own lv for a root partition and swap partition provided by the host. The guest installs are not using lvm, they use the whole 'disk' as they see it, which is of course managed by the host lvm. To deploy a new FC6 guest, lvcreate new swap and data partitions and dd the image lv to the new guest partition. Then a copy of the /etc/xen/image is made, the mac address, uuid and name are updated. Furthermore, in the new guest os the mac address and networking settings must be updated. An external USB2.0 drive that is managed by lvm is used for backups. Use pvcreate and vgcreate to create a backup volume group (first time only) and create logical volumes, shutdown the guests and dd the guest lv to the backup volume group. Then use vgchange and vgexport to remove the backup volume (pvscan and vgimport are used to re-attach the volume in the future). The following is a edited version of my more detailed notes. I would really like to hear any suggestions or any major problems with this, Thanks! Gordon Turner. 1. Host setup ------------- - Install FC6 and xen on the host, using LVM and leaving space for the guest logical volumes. - Create logical volumes for xen hosts and create swap space: lvcreate -L 1G -n ImageSwap00 VolGroup00 lvcreate -L 3G -n ImageData00 VolGroup00 2. Create image domain ---------------------- - Run installer: [root at xen ~]# /usr/sbin/xenguest-install What is the name of your virtual machine? image How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /dev/VolGroup00/ImageData00 Would you like to enable graphics support? (yes or no) no What is the install location? http://192.168.1.199/fc6/ - During the guest install, remove default lvm partitioning and create one filesystem that completely fills the available 'drive'. Ignore the swap warning, it will be added later. - After the first boot of the guest image, update fstab in the image to include the swap space: vi /etc/fstab /dev/xvdb swap swap defaults 0 0 - Then halt the guest os: halt - In the host xen system, edit the /etc/xen/image file to shrink the ram(optional) and add the swap: vi /etc/xen/image ... memory = "64" disk = [ 'phy:/dev/VolGroup00/ImageData00,xvda,w', 'phy:/dev/VolGroup00/ImageSwap00,xvdb,w' ] - Create the swap space: mkswap /dev/VolGroup00/ImageSwap00 - Boot and test guest image, halt when done. 3. Create a new guest from image -------------------------------- - Create lvm partitions: lvcreate -L 1G -n ExampleSwap00 VolGroup00 lvcreate -L 3G -n ExampleData00 VolGroup00 - Map the ImageData00 partition: kpartx -av /dev/VolGroup00/ImageData00 - Use dd to copy to the new partition: dd if=/dev/mapper/ImageData00p1 of=/dev/VolGroup00/ExampleData00 - Create swap space: mkswap /dev/VolGroup00/ExampleSwap00 - Unmap the ImageData00 partition: kpartx -dv /dev/VolGroup00/ImageData00 - Mount the new data partition: mount /dev/VolGroup00/ExampleData00 /mnt/Data - In new host, edit the following files and change 'image' to new name: vi /mnt/Data/etc/hosts vi /mnt/Data/etc/sysconfig/network - Also on new host, set the correct ip address and MAC address: vi /mnt/Data/etc/sysconfig/network-scripts/ifcfg-eth0 - Unmount the new data partition: umount /mnt/Data - Copy the 'image' xen configuration file and edit it: cp /etc/xen/image /etc/xen/example vi /etc/xen/example 4. Create new Backup Volume Group --------------------------------- - One time deal: pvcreate /dev/sda vgcreate VolBackup00 /dev/sda vgchange -a n VolBackup00 vgexport VolBackup00 5. Backup Logical Volume ------------------------ - Plugin USB2.0 drive, wait for initialization(check dmesg) and import the Volume Group: pvscan vgimport VolBackup00 - To create and backup to new logical volume: lvcreate -L3G -n YYYYMMDD_NAME VolBackup00 dd if=/dev/VolGroup00/ImageData00 of=/dev/VolBackup00/YYYYMMDD_NAME - To export the Volume Group and disconnect the drive: vgchange -a n VolBackup00 vgexport VolBackup00 6. Notes and questions ---------------------- - My understanding is that using dd to copy lv around is safe as long as the physical extents are the same, ie lvcreate should create volumes of exactly the same size. - Not sure the exact process of increasing a guest lv from the host, but it should be possible. - When a new copy of an image is copied, the ssh keys should be recreated so that they are unique. Haven't looked at how to do that yet. From ian.patton at gmail.com Wed Nov 22 22:58:22 2006 From: ian.patton at gmail.com (Ian Patton) Date: Wed, 22 Nov 2006 17:58:22 -0500 Subject: [Fedora-xen] Windows Vista RC1 on Xen 3.0.3 FC6 Message-ID: <1579d8590611221458h2d128c7pb0135449737b492b@mail.gmail.com> Hello, I now have Windows Vista RC1 attempting to boot using the following hvm file: # Automatically generated xen config file name = "WindowsVistaRC1" builder = "hvm" memory = "784" disk = [ 'phy:/dev/hdc1,hda,w', 'file:/tmp/WINDOWS_VISTA.iso,hdc:cdrom,r' ] vif = [ 'type=ioemu, mac=00:16:3e:0f:a7:08, bridge=xenbr0', ] uuid = "7232d84d-f579-a4f1-d190-b31ebb66faf9" device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 #sdl=1 apic=1 acpi=1 pae=1 boot="d" vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'destroy' I can see it boot from the DVD image and start to load the installer. It gets to the point where the black screen progress bar is at 100% and then I see the DomU processor drop to 0% and it does nothing. xend.log shows nothing useful the qemu-dm.*.log shows: domid: 28 qemu: the number of cpus is 1 shared page at pfn:30fff, mfn: 3a0af buffered io page at pfn:30ffd, mfn: 3a0b1 char device redirected to /dev/pts/1 False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 and the xend-debug.log shows this: Nothing to flush. Nothing to flush. File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 77, in op_create dominfo = self.xd.domain_create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 228, in domain_create dominfo = XendDomainInfo.create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1335, in initDomain balloon.free(memory + shadow) File "/usr/lib/python2.4/site-packages/xen/xend/balloon.py", line 166, in free raise VmError( VmError: I need 1070492 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 773804 KiB free. I have tried chaning the APIC, ACPI and PAE settings to every possible combo and it only made it worse. I did create a partition for this install... Actually I gave it it's own whole disk drive. The partition is /dev/hdc1 but it is not formatted. I assumed Windows would format it as needed. Does anyone know if it should be formatted as ext3 for it to work? -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbond at nrggos.com.au Thu Nov 23 00:10:54 2006 From: dbond at nrggos.com.au (Darryl Bond) Date: Thu, 23 Nov 2006 10:10:54 +1000 Subject: [Fedora-xen] VLANs on DomU domains In-Reply-To: <455DA91C.7020905@mobilethink.dk> References: <455DA91C.7020905@mobilethink.dk> Message-ID: <4564E70E.9050407@nrggos.com.au> Thanks Bertho, I managed to get it to work something along the lines of your first method before I read your email. I was also unsuccessful using your second method. I wanted a Dom0 host to be accessable only on an administration network with the guests accessing their relevant VLANs I used one Gig (eth0) real interface as an 802.1Q trunk with the Dom0 having no interfaces mapped to it. The Dom0 was connected (without VLANS) to the administration network via eth1. I had to modify /etc/xen/xend-config.sxp to bridge eth0 otherwise it would bridge the active device (eth1) eth0 --> xenbr0 -> Dom1 --> VLAN1 |-> VLAN2 |->... eth1-->Dom0 (network-script 'network-bridge netdev=eth0') The guests were then set up as normal hosts connected to an 802.1Q trunk network as you detailed. I found that if I used VLANs on the Dom0 on eth0 then the trunk would not pass through to the guests, Hence why Dom0 is not using VLANs on eth0. I did not do much research to discover why except that the instant I removed the VLANs from Dom0 eth0 the VLAN networks started working on the guest. My initial email came about because I was expecting to have to plumb the individual VLANs through to the guests as you also failed to do. This is much like VMWare ESX works. Regards Darryl Bertho Stultiens wrote: >> I am setting up a box with FC6 + xen with FC6 for the DomU guests. >> I have a server with 4 gigabit ports and I want to use 802.1Q vlans on >> one of the gig ports. >> I have the VLANs configured in Dom0 without any addresses attached to >> them. >> How do I make the VLANs available to the guests? I want to make 4 >> VLANs available to each guest. I have thought of a few alternatives >> but I cannot get any to work. >> > > The easy way; I have installed FC6 with 802.1Q and 4 guests. It works > very nicely. For each guest do: > 1 - You need to enable vlans /etc/sysconfig/network. > NETWORKING=yes > VLAN=yes > NETWORKING_IPV6=no > HOSTNAME=xenbox2.example.com > GATEWAY=192.168.42.1 > > 2 - create a subinterface by file editting > /etc/sysconfig/network-scripts/ifcfg-eth0.42: > DEVICE=eth0.42 > BOOTPROTO=static > ONBOOT=yes > IPADDR=192.168.42.102 > NETMASK=255.255.255.0 > TYPE=Ethernet > > 3 - depending on whether you want untagged packets on the same > interface, you need to edit the /etc/.../ifcfg-eth0 file too. (note: the > parent interface must be up for the tagged interface to work.) The lines > commented out will assign an IP address to the untagged interface: > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > TYPE=Ethernet > # BOOTPROTO=static > # IPADDR=172.16.42.102 > # NETMASK=255.255.255.0 > > 4 - make sure that your /etc/hosts setup is correct. If you have DNS > available 24/7, then only define localhost[.localdomain} as 127.0.0.1 > and not the hostname itself. > > When you restart the network in the guest, then your guest will default > to use the tagged interface vlan 42 (above example). If you want the > untagged interface as default, then you can change the gateway and > assign an IP address to it. > > On the host, you need to do a similar thing. Create a subinterface > eth0.42 and assign an IP address to it. Once that is done, you can talk > to your guests via dot1Q from your host. > > Beware of iptables! If you have a firewall setup, then you need to make > sure that it is done right. Doing it right, though, is a though job with > dot1Q in place. I have the firewall completely disabled on the host and > guests. My firewall is placed physically separated on another box. > > > >> 1. Bridge the tagged 802.1Q stream from the Gig port through to the >> guests and configure eth0.x. on the guests >> > > This would be above scenario. > > > >> 2. Create a bridge on Dom0 for each VLAN so that they appear as >> eth0...eth3 on the guests. >> > > The xenbrX interfaces on the host already transport all packets because > they are L2 bridges (see brctl). The bridge does not care whether the > packets are .1Q tagged or not. The only thing you need is to instruct > the kernel to look for/act on specifics by creating (sub-)interfaces. > > Now, if you want the guests not to know that they are connected to a > VLAN, then you need a brigde-interface to do (un-)tagging for you. That > means that you need to create a dot1Q subinterface on the host's > physical peth[0-3] and add the subinterface to a new bridge. > > Normal scenario: > peth0 -> xenbr0 -> vif0.0(host eth0) > vif1.0(guest1 eth0) > > Dot1Q scenario: > peth0.42 -> xenbr42 -> vif1.0(guest1 eth0) > > i.e.: > # brctl addbr xenbr42 > # ip link set xenbr42 up > # vconfig add peth0 42 > # ip link set peth0.42 up > # brctl addif xenbr42 peth0.42 > > In the VM config you have now something like: > vif = [ 'mac=00:16:3e:11:22:33, bridge=xenbr42', ] > > The VM's eth0 interface is created as part of bridge that will fowrard > to a subinterface. The kernel will now do the tagging/untagging (note: > slow) and the VM cannot see that it is attached to a VLAN. > > Theoretically it should work, but I was not able to make this scenario > work as expected though. I suspect that the hosts peth0 -> eth0 bridge > is interfering (which has a tagged interface too in my setup). Or maybe > my fingers were too fast at typing and I forgot a simple thing... > > > > >> The xen documentation is minimal for configuring VLANs. Is there a >> (FC6) supported way of configuring them? >> > > Vlans is a no-issue for xen. It is layered in the network and xen only > passes the packets. > > > __________________________________________________________________________________ DISCLAIMER The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company. From berrange at redhat.com Thu Nov 23 00:46:55 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 23 Nov 2006 00:46:55 +0000 Subject: [Fedora-xen] Windows Vista RC1 on Xen 3.0.3 FC6 In-Reply-To: <1579d8590611221458h2d128c7pb0135449737b492b@mail.gmail.com> References: <1579d8590611221458h2d128c7pb0135449737b492b@mail.gmail.com> Message-ID: <20061123004655.GC24782@redhat.com> On Wed, Nov 22, 2006 at 05:58:22PM -0500, Ian Patton wrote: > Hello, > > I now have Windows Vista RC1 attempting to boot using the following hvm > file: > > # Automatically generated xen config file > name = "WindowsVistaRC1" > builder = "hvm" > memory = "784" [snip] > raise VmError( > VmError: I need 1070492 KiB, but dom0_min_mem is 262144 and shrinking to > 262144 KiB would leave only 773804 KiB free. You asked for 784 MB of ram for the guest, but it was only able to free up 773804 KiB from Dom0. Either reduce the amount of RAM you give to the guest, or make more free memory in Dom0. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Nov 23 01:01:16 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 23 Nov 2006 01:01:16 +0000 Subject: [Fedora-xen] Windows Vista RC1 on Xen 3.0.3 FC6 In-Reply-To: <20061123004655.GC24782@redhat.com> References: <1579d8590611221458h2d128c7pb0135449737b492b@mail.gmail.com> <20061123004655.GC24782@redhat.com> Message-ID: <20061123010116.GB32283@redhat.com> On Thu, Nov 23, 2006 at 12:46:55AM +0000, Daniel P. Berrange wrote: > On Wed, Nov 22, 2006 at 05:58:22PM -0500, Ian Patton wrote: > > Hello, > > > > I now have Windows Vista RC1 attempting to boot using the following hvm > > file: > > > > # Automatically generated xen config file > > name = "WindowsVistaRC1" > > builder = "hvm" > > memory = "784" > > [snip] > > > raise VmError( > > VmError: I need 1070492 KiB, but dom0_min_mem is 262144 and shrinking to > > 262144 KiB would leave only 773804 KiB free. > > You asked for 784 MB of ram for the guest, but it was only able to free > up 773804 KiB from Dom0. Either reduce the amount of RAM you give to > the guest, or make more free memory in Dom0. I should also mention that the HV will always require a few MB more than you actually request, to maintain the shadow pagetables & other bookeeping data structs. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From tancs at comp.nus.edu.sg Thu Nov 23 02:31:16 2006 From: tancs at comp.nus.edu.sg (Tan Chee Sin) Date: Thu, 23 Nov 2006 10:31:16 +0800 Subject: [Fedora-xen] Cannot create files or dirs even as root on FC6 xen system In-Reply-To: <4563C844.5070808@trader.name> References: <4563AD0C.10309@comp.nus.edu.sg> <4563C844.5070808@trader.name> Message-ID: <456507F4.6070605@comp.nus.edu.sg> Hi Craig, Thanks for the info. Yes, autofs is indeed configured to dynamically mount the CDROM on /misc/cdrom. This is fresh install on a new system but it still have this style of config. Hmm... I have commented out the culprit line and restarted autofs. I'm able to write to /misc now. =) cheesin W Craig Trader wrote: > Cheesin ... > > Do you have the autofs daemon running, and does your /etc/auto.master > file reference mounting devices on /misc, using the definitions in > /etc/auto.misc? Once upon a time, RedHat Linux used autofs to > dynamically mount the CDROM on /misc/cdrom; if you've got an older > system that's been upgraded, you might still have a remnant of that > style of configuration. If you run "ps aux | grep automount", it will > show you which mappings are active; if you see something like > "/usr/sbin/automount --timeout=60 /misc program /etc/auto.misc" you've > found the culprit. > > - Craig - > > Tan Chee Sin wrote: > >> Hi, >> >> I've installed a FC6 xen guest system and there is a /misc folder >> which I want to create files and directories. I get a permission >> denied when I try to do so even when I am root. >> >> # pwd >> /misc >> # mkdir test >> >> mkdir: cannot create directory `test': Permission denied >> >> When I do a directoy listing on /, misc is 0 bytes. >> >> drwxr-xr-x 2 root root 0 Nov 21 13:24 misc >> >> I have listed the disk space usage and the fstab below. >> # df -k >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/xvda1 11904588 1830176 9459928 17% / >> tmpfs 768000 0 768000 0% /dev/shm >> /dev/xvda3 5431008 171288 4979388 4% /var >> >> # cat /etc/fstab >> LABEL=/1 / ext3 >> defaults 1 1 >> devpts /dev/pts devpts >> gid=5,mode=620 0 0 >> tmpfs /dev/shm tmpfs >> defaults 0 0 >> proc /proc proc >> defaults 0 0 >> sysfs /sys sysfs >> defaults 0 0 >> LABEL=/var /var ext3 >> defaults 1 2 >> LABEL=SWAP-xvda2 swap swap >> defaults 0 0 >> >> I'm not sure if this issue happens only on FC6 xen but I am able to >> create files and directories on a FC5 xen system. >> >> cheesin >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen From paul at xelerance.com Thu Nov 23 05:23:45 2006 From: paul at xelerance.com (Paul Wouters) Date: Thu, 23 Nov 2006 06:23:45 +0100 (CET) Subject: [Fedora-xen] 2.6.18-1.2798.fc6xen and Realtek Message-ID: When upgrading to 2.6.18-1.2798.fc6xen on my dom0, I ended up with a broken ethernet setup because the 8139cp module failed to drive the card. modprobe.conf contained: alias dev1804289383 8139too alias eth1 e1000 I dont remember if I put that in a long long long time ago, or wether it magically got put in there on install. But I had an eth0 and an eth1, of which eth1 was not in use. Changing dev1804289383 to eth0 did not help. I did not really care, so I just switched the cable to the other ethernet port. My dom0 had connectivity, but all connectivity on my xenu's was broken. I think this has to do with the bridge setup. Rebooting did not help either. So I think that apart from the kernel bug in the 8139cp driver, the fedora bridge setup for xen might assume eth0 exists, or won't look further if eth0 is not found? I did not pursue this bug further to actually find out what happens exactly, since I don't have time for that now. I did want to report it, in case someone else runs into the same issue. At least google will find this entry then. Paul From davej at redhat.com Thu Nov 23 06:20:32 2006 From: davej at redhat.com (Dave Jones) Date: Thu, 23 Nov 2006 01:20:32 -0500 Subject: [Fedora-xen] 2.6.18-1.2798.fc6xen and Realtek In-Reply-To: References: Message-ID: <20061123062032.GB31020@redhat.com> On Thu, Nov 23, 2006 at 06:23:45AM +0100, Paul Wouters wrote: > > When upgrading to 2.6.18-1.2798.fc6xen on my dom0, I ended up with a > broken ethernet setup because the 8139cp module failed to drive the > card. > > modprobe.conf contained: > > alias dev1804289383 8139too > alias eth1 e1000 Sounds like your /etc/sysconfig/network-scripts/ifcfg-eth0 lacks an HWADDR= entry for some reason. Put your MAC address there, and it should work, and 'bind' eth0 to that NIC every boot. Dave -- http://www.codemonkey.org.uk From bhkwan at thoughtworks.com Thu Nov 23 07:48:37 2006 From: bhkwan at thoughtworks.com (Barrow H Kwan) Date: Wed, 22 Nov 2006 23:48:37 -0800 Subject: [Fedora-xen] Error: (12, 'Cannot allocate memory') Message-ID: This is a second post regrading running Windows Guest OS. Does anyone has Windows Guest OS running successfully with the Dom0 has all the physical memory allocated? If I don't lower the memory assign to Dom0 through grub, I will not be able to run a Windows Guest OS. This what I got Using config file "/etc/xen/Win2k3R2-01". Error: (12, 'Cannot allocate memory') and here is the xm dmesg [root at sfxen01 ~]# xm dmesg __ __ _____ ___ _____ ____ __ __ \ \/ /___ _ __ |___ / / _ \ |___ / _ __ ___| ___| / _| ___ / /_ \ // _ \ '_ \ |_ \| | | | |_ \ __| '__/ __|___ \ | |_ / __| '_ \ / \ __/ | | | ___) | |_| | ___) |__| | | (__ ___) || _| (__| (_) | /_/\_\___|_| |_| |____(_)___(_)____/ |_| \___|____(_)_| \___|\___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0.3-rc5-1.2849.fc6 (brewbuilder at build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) Fri Nov 10 12:36:50 EST 2006 Latest ChangeSet: unavailable (XEN) Command line: /xen.gz-2.6.18-1.2849.fc6 (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed (XEN) by Xen in 32-bit mode. Truncating the memory map... (XEN) Physical RAM map: (XEN) 0000000000000000 - 00000000000a0000 (usable) (XEN) 0000000000100000 - 00000000cffa8000 (usable) (XEN) 00000000cffa8000 - 00000000cffb7c00 (ACPI data) (XEN) 00000000cffb7c00 - 00000000d0000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fe000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000400000000 (usable) (XEN) System RAM: 15615MB (15990048kB) (XEN) Xen heap: 9MB (9864kB) (XEN) PAE enabled, limit: 16 GB (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.4 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v002 DELL ) @ 0x000f2a00 (XEN) ACPI: XSDT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2a80 (XEN) ACPI: FADT (v003 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2b88 (XEN) ACPI: MADT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2c7c (XEN) ACPI: SPCR (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2d5d (XEN) ACPI: HPET (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2dad (XEN) ACPI: MCFG (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x000f2de5 (XEN) ACPI: DSDT (v001 DELL PE_SC3 0x00000001 MSFT 0x0100000e) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) (XEN) Processor #7 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x14] disabled) (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x15] disabled) (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] disabled) (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x17] disabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x09] address[0xfec81000] gsi_base[64]) (XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec81000, GSI 64-87 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2992.570 MHz processor. (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06 (XEN) Booting processor 1/6 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU: Processor Core ID: 0 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06 (XEN) Booting processor 2/1 eip 90000 (XEN) Initializing CPU#2 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#2. (XEN) CPU2: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06 (XEN) Booting processor 3/7 eip 90000 (XEN) Initializing CPU#3 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU: Processor Core ID: 1 (XEN) VMXON is done (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#3. (XEN) CPU3: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 4 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.: 000000000e000000->0000000010000000 (3924903 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0400000->c0807808 (XEN) Init. ramdisk: c0808000->c0cf9e00 (XEN) Phys-Mach map: c0cfa000->c1bfae9c (XEN) Start info: c1bfb000->c1bfb46c (XEN) Page tables: c1bfc000->c1c11000 (XEN) Boot stack: c1c11000->c1c12000 (XEN) TOTAL: c0000000->c2000000 (XEN) ENTRY ADDRESS: c0400000 (XEN) Dom0 has maximum 4 VCPUs (XEN) Initrd len 0x4f1e00, start at 0xc0808000 (XEN) Scrubbing Free RAM: ....................................................................................................................................................................done. (XEN) Xen trace buffers: disabled (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen). (XEN) (file=platform_hypercall.c, line=129) Domain 0 says that IO-APIC REGSEL is good (XEN) mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining (XEN) mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining (XEN) DOM2: (file=mm.c, line=586) Non-privileged (2) attempt to map I/O space 000000f8 (XEN) DOM2: (file=mm.c, line=586) Non-privileged (2) attempt to map I/O space 000000f8 xend.log : [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:190) XendDo mainInfo.create(['vm', ['name', 'Win2k3R2-01'], ['memory', '768'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['uuid', '5a59e56b-3b2f-8030 -db16-5e028cef4d0e'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader' ], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boo t', 'c'], ['serial', 'pty'], ['acpi', 1], ['apic', 1], ['vnc', 1], ['vncunused', 1], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]], ['dev ice', ['vbd', ['uname', 'phy:/dev/VolGroup00/LogVol09'], ['dev', 'hda'], ['mode' , 'w']]], ['device', ['vbd', ['uname', 'file:/tmp/win2k3cd1.iso'], ['dev', 'hdc: cdrom'], ['mode', 'r']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:1 6:3e:65:9b:22'], ['type', 'ioemu']]]]) [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:296) parseC onfig: config is ['vm', ['name', 'Win2k3R2-01'], ['memory', '768'], ['on_reboot' , 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['uuid', '5a59e56b-3b2f-803 0-db16-5e028cef4d0e'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader '], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['bo ot', 'c'], ['serial', 'pty'], ['acpi', 1], ['apic', 1], ['vnc', 1], ['vncunused' , 1], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]], ['de vice', ['vbd', ['uname', 'phy:/dev/VolGroup00/LogVol09'], ['dev', 'hda'], ['mode ', 'w']]], ['device', ['vbd', ['uname', 'file:/tmp/win2k3cd1.iso'], ['dev', 'hdc :cdrom'], ['mode', 'r']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00: 16:3e:65:9b:22'], ['type', 'ioemu']]]] [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:395) parseC onfig: result is {'shadow_memory': None, 'uuid': '5a59e56b-3b2f-8030-db16-5e028c ef4d0e', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'imag e': ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/li b/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['serial', 'pty'], ['acpi', 1], ['apic', 1], ['vnc', 1], ['vncunused', 1], ['display', 'localhost: 10.0'], ['xauthority', '/root/.Xauthority']], 'on_poweroff': None, 'bootloader_a rgs': None, 'cpus': None, 'name': 'Win2k3R2-01', 'backend': [], 'vcpus': 1, 'cpu _weight': None, 'features': None, 'vcpu_avail': None, 'memory': 768, 'device': [ ('vbd', ['vbd', ['uname', 'phy:/dev/VolGroup00/LogVol09'], ['dev', 'hda'], ['mod e', 'w']]), ('vbd', ['vbd', ['uname', 'file:/tmp/win2k3cd1.iso'], ['dev', 'hdc:c drom'], ['mode', 'r']]), ('vif', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e :65:9b:22'], ['type', 'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': No ne} [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:1253) XendD omainInfo.construct: None [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:1285) XendD omainInfo.initDomain: 4 1.0 [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: boot, val: c [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: fda, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: fdb, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: soundhw, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: localtime, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: serial, val: pty [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: std-vga, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: isa, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: vcpus, val: 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: acpi, val: 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: usb, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (image:379) args: usbdevice, val: None [2006-11-22 23:42:34 xend 3162] DEBUG (balloon:127) Balloon: 806556 KiB free; ne ed 805684; done. [2006-11-22 23:42:34 xend 3162] INFO (image:138) buildDomain os=hvm dom=4 vcpus= 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:338) dom = 4 [2006-11-22 23:42:34 xend 3162] DEBUG (image:339) image = /usr/lib/xen/ boot/hvmloader [2006-11-22 23:42:34 xend 3162] DEBUG (image:340) store_evtchn = 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:341) memsize = 768 [2006-11-22 23:42:34 xend 3162] DEBUG (image:342) vcpus = 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:343) pae = 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:344) acpi = 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:345) apic = 1 [2006-11-22 23:42:34 xend 3162] DEBUG (image:467) hvm shutdown watch registered [2006-11-22 23:42:34 xend.XendDomainInfo 3162] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363, in initDomain raise VmError(str(exn)) VmError: (12, 'Cannot allocate memory') [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:1449) XendD omainInfo.destroy: domid=4 [2006-11-22 23:42:34 xend.XendDomainInfo 3162] DEBUG (XendDomainInfo:1457) XendD omainInfo.destroyDomain(4) [2006-11-22 23:42:34 xend 3162] DEBUG (image:479) hvm shutdown watch unregistere d [2006-11-22 23:42:34 xend 3162] ERROR (xswatch:70) read_watch failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xswatch.py", line 66, in watchMain res = watch.fn(we[0], *watch.args, **watch.kwargs) File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 489, in hvm_sh utdown reason = vm.readDom('control/shutdown') AttributeError: 'NoneType' object has no attribute 'readDom' From bst at mobilethink.dk Thu Nov 23 08:45:20 2006 From: bst at mobilethink.dk (Bertho Stultiens) Date: Thu, 23 Nov 2006 09:45:20 +0100 Subject: [Fedora-xen] VLANs on DomU domains In-Reply-To: <4564E70E.9050407@nrggos.com.au> References: <455DA91C.7020905@mobilethink.dk> <4564E70E.9050407@nrggos.com.au> Message-ID: <45655FA0.1060002@mobilethink.dk> Darryl Bond wrote: > I managed to get it to work something along the lines of your first > method before I read your email. I was also unsuccessful using your > second method. It still eludes me why the second method does not work, but the first seems to be ok too. Users cannot change set setup, so there is no real risk involved. [snip] > I found that if I used VLANs on the Dom0 on eth0 then the trunk would > not pass through to the guests, Hence why Dom0 is not using VLANs on eth0. > I did not do much research to discover why except that the instant I > removed the VLANs from Dom0 eth0 the VLAN networks started working on > the guest. You have to take care here because in Dom0 you have ethX and pethX. Vlans on ethX(dom0) will work whereas those on peth0 apparently do not as expected. My current setup is like this: peth0 -> xenbr0 -> vif0.0 -> eth0(Dom0)+IP-> eth0.42+IP -> vif1.0 -> eth0(Guest1) -> eth0.42+IP -> vif2.0 -> eth0(Guest2) -> eth0.42+IP -> ... Dom0 is part of vlan 42 and my management (no routing between them enabled though). The uplink peth0 is a trunk with management untagged and vlan 42 tagged. My guess why the other setup has problems lies in several parts. Firstly, the management MAC address (default fe:ff:ff:ff:ff:ff) of the second bridge must be different. I forgot to change that and have had problems with that before with STP enabled (bridge can otherwise not be uniquely identified). And secondly, juggling with peth0.X can only be done after xen has remapped the interfaces. The remapping occurs after the original network is brought up. I need to go through the xen scripts to get that right, I guess. I'll have to do some more experimenting to get this pinned down because it actually is interesting to have bridges that can swap/map/juggle vlan tags. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From Hua.Zhang at Sun.COM Thu Nov 23 06:25:09 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Thu, 23 Nov 2006 14:25:09 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061122121852.GE13945@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> Message-ID: <45653EC5.5030800@sun.com> Excellent explanation, I see... you are expert. :) Thanks, Henry Daniel P. Berrange ??: > On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote: > >> Hi Daniel, >> >> Here I have another question on virt-manager, as you write "an embedded >> VNC client viewer provides console access to each of the guest domains", >> my concern is where is the vnc server, who provide it, and start it? >> Need we setup vnc? I looked through the process used to create guest, >> seems there is no any step for vnc... >> > > The VNC server depends on what type of domain is being run. For HVM guests > the VNC server is provided by the qemu-dm process assoicated with that > guest. For paravirt guests, VNC is only available if you have the paravirt > framebuffer patches applied to your xen tree - these are not in xen-unstable > yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC > server. So in both case all you need to do is set 'vnc=1' in the guest > config file & XenD will ensure the VNC servers are started as required. > > Dan. > From Hua.Zhang at Sun.COM Thu Nov 23 11:54:24 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Thu, 23 Nov 2006 19:54:24 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061122121852.GE13945@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> Message-ID: <45658BF0.60505@sun.com> hi Daniel, From the webpage, I can see that dbus and gnome-python-desktop are optional, but when our release engineer try to build, seems they are not, so could you confirm me if we can build/run virt-manager correctly without Dbus? I carefully read the content in "Dbus Services", My understanding is that Dbus in virt-manager is used to make other external application call some core function, so that they can get display the window/dialog . When Dbus is used? "The remote control module provides the DBus service allowing various UI functions to be controlled remotely.": My understanding for "remotely" is to run virt-manager remotely, is it correct? so will dbus only used when remotely? if some application in local machine, it may also use Dbus to run some function? Thanks, Henry Daniel P. Berrange ??: > On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote: > >> Hi Daniel, >> >> Here I have another question on virt-manager, as you write "an embedded >> VNC client viewer provides console access to each of the guest domains", >> my concern is where is the vnc server, who provide it, and start it? >> Need we setup vnc? I looked through the process used to create guest, >> seems there is no any step for vnc... >> > > The VNC server depends on what type of domain is being run. For HVM guests > the VNC server is provided by the qemu-dm process assoicated with that > guest. For paravirt guests, VNC is only available if you have the paravirt > framebuffer patches applied to your xen tree - these are not in xen-unstable > yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC > server. So in both case all you need to do is set 'vnc=1' in the guest > config file & XenD will ensure the VNC servers are started as required. > > Dan. > From davidsen at tmr.com Thu Nov 23 04:53:43 2006 From: davidsen at tmr.com (Bill Davidsen) Date: Wed, 22 Nov 2006 23:53:43 -0500 Subject: [Fedora-xen] Re: virDomainCreateLinux() failed In-Reply-To: <20061122163559.GF11685@redhat.com> References: <455E3CEC.1010806@tmr.com> <20061122163559.GF11685@redhat.com> Message-ID: <45652957.9070706@tmr.com> Daniel P. Berrange wrote: > On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote: >> FC6, xen installed, latest updates as of five minutes ago. ASUS >> P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >> PAE on, virtualization on. xend running, "xm list" works, shows one domain. >> >> >> Install of any fully virtualized o/s fails. Sample output: >> Would you like a fully virtualized guest (yes or no)? This will allow >> you to run unmodified operating systems. yes >> How much RAM should be allocated (in megabytes)? 256 >> Would you like to enable graphics support? (yes or no) no >> >> >> Starting install... >> libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 >> libvir: Xen Daemon error : POST operation failed: (xend.err 'Error >> creating domain: Disk image does not exist: >> /home/davidsen/Virtual_Machines/OpenBSD-4.0a') > > In FC6 GA you have to make sure the file for the disk was under /xen > to be labelled correctly. In rawhide (and the latest FC6 policy) > we're moving to /var/lib/xen/images. This is consistent with the > directory used on Suse, and what the next version of XenD will > enforce. To double check what directory is setup for the SELinux > policy you can run > > semanage fcontext -l | grep xen_image_t > > If you don't have space under /var/lib/xen/images, then either > mount a new volume there, or bind that dir to a location which > has extra space, eg > > mount --bind /some/dir/with/big/disk /var/lib/xen/images > > If you really really don't want to use /var/lib/xen/images at all, > then you can define a new location in the SELinux policy using: > > semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' > This sounds like the missing piece, I can check where the current install wants it, and then get it there in one way or another. I'll try it some time over the long weekend and report back. Thanks much, I suspect this was the hint I needed. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From berrange at redhat.com Thu Nov 23 14:51:52 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 23 Nov 2006 14:51:52 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <45658BF0.60505@sun.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> Message-ID: <20061123145152.GA30705@redhat.com> On Thu, Nov 23, 2006 at 07:54:24PM +0800, Henry Zhang wrote: > hi Daniel, > > From the webpage, I can see that dbus and gnome-python-desktop are > optional, but when our release engineer try to build, seems they are > not, so could you confirm me if we can build/run virt-manager correctly > without Dbus? Ah, I should perhaps clarify that a little. The DBus python libraries are required to be present, but you don't have to have DBus running. If it fails to connect to the DBus daemon, the app will log a warning and continue. The GNome Python Desktop stuff is competely optional - if you don't have the python bindings installed it will simply disable the VNC password saving altogether. > I carefully read the content in "Dbus Services", My understanding is > that Dbus in virt-manager is used to make other external application > call some core function, so that they can get display the window/dialog . > > When Dbus is used? > > "The remote control module provides the DBus service > allowing various UI > functions to be controlled remotely.": My understanding for "remotely" > is to run virt-manager remotely, is it correct? so will dbus only used > when remotely? if some application in local machine, it may also use > Dbus to run some function? Not quite - the intent with the DBus stuff is that if you run two copies of virt-manager on the same machine, the second one will use DBus to find the first one & just make RPC calls to it. It also allows other applications within the local X desktop to control various bits of its UI. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From paul at xelerance.com Thu Nov 23 15:17:13 2006 From: paul at xelerance.com (Paul Wouters) Date: Thu, 23 Nov 2006 16:17:13 +0100 (CET) Subject: [Fedora-xen] 2.6.18-1.2798.fc6xen and Realtek In-Reply-To: <20061123062032.GB31020@redhat.com> References: <20061123062032.GB31020@redhat.com> Message-ID: On Thu, 23 Nov 2006, Dave Jones wrote: > > alias dev1804289383 8139too > > alias eth1 e1000 > > Sounds like your /etc/sysconfig/network-scripts/ifcfg-eth0 lacks > an HWADDR= entry for some reason. Put your MAC address there, > and it should work, and 'bind' eth0 to that NIC every boot. I'll try that on the next kernel if it recognises my hardware again. My question was more why does the xen networking fail in this case on the guests (while it works on the host). Paul From rstory-l at 2006.revelstone.com Thu Nov 23 16:10:34 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Thu, 23 Nov 2006 11:10:34 -0500 Subject: [Fedora-xen] Xen + LVM + OS image In-Reply-To: References: Message-ID: <20061123111034.75fc1d4f@king.vb.futz.org> On Wed, 22 Nov 2006 17:05:32 -0500 (EST) turner at ftn.net wrote: TN> - When a new copy of an image is copied, the ssh keys should be recreated TN> so that they are unique. Haven't looked at how to do that yet. Just delete them, and sshd will recreate them the next time it starts.. From paul at xelerance.com Thu Nov 23 16:45:39 2006 From: paul at xelerance.com (Paul Wouters) Date: Thu, 23 Nov 2006 17:45:39 +0100 (CET) Subject: [Fedora-xen] Xen + LVM + OS image In-Reply-To: <20061123111034.75fc1d4f@king.vb.futz.org> References: <20061123111034.75fc1d4f@king.vb.futz.org> Message-ID: On Thu, 23 Nov 2006, Robert Story wrote: > On Wed, 22 Nov 2006 17:05:32 -0500 (EST) turner at ftn.net wrote: > TN> - When a new copy of an image is copied, the ssh keys should be recreated > TN> so that they are unique. Haven't looked at how to do that yet. > > Just delete them, and sshd will recreate them the next time it starts.. Provided your xenu actually has random, which it likely doesn't have that much :( The same applies to the Openswan hostkey. Worse, due to bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209395 running 'yum install openswan' will cause yum to hang indefinately. Worse if you select the package in the anaconda installer..... Paul From turner at ftn.net Thu Nov 23 17:49:37 2006 From: turner at ftn.net (turner at ftn.net) Date: Thu, 23 Nov 2006 12:49:37 -0500 (EST) Subject: [Fedora-xen] Xen + LVM + OS image In-Reply-To: References: <20061123111034.75fc1d4f@king.vb.futz.org> Message-ID: On Thu, 23 Nov 2006, Paul Wouters wrote: > On Thu, 23 Nov 2006, Robert Story wrote: > >> On Wed, 22 Nov 2006 17:05:32 -0500 (EST) turner at ftn.net wrote: >> TN> - When a new copy of an image is copied, the ssh keys should be recreated >> TN> so that they are unique. Haven't looked at how to do that yet. >> >> Just delete them, and sshd will recreate them the next time it starts.. > > Provided your xenu actually has random, which it likely doesn't have > that much :( > > The same applies to the Openswan hostkey. Worse, due to bug > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209395 > > running 'yum install openswan' will cause yum to hang indefinately. Worse > if you select the package in the anaconda installer..... > > Paul > Thanks for the tip, will have to check things out, see if things hang. GT. From rstory-l at 2006.revelstone.com Thu Nov 23 21:56:44 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Thu, 23 Nov 2006 16:56:44 -0500 Subject: [Fedora-xen] renaming vg for lvm backed domU Message-ID: <20061123165644.088aec59@king.vb.futz.org> Hi, I've got a FC5 dom0 where I've created a lvm backed domU I want to use as a template. The domU works fine. If I create a new lv in the dom0 and dd the orginal lv over to the new one, copy the xen conf file, update the path and mac addr, the domU clone boots fine too. However, I want the domU vg name to be different in the new domU. So, I used kpartx to get to the new vg, and used vgrename to rename it. This works great in the dom0, and I can get to all the lv's. However, when I try to reboot the domU (after updating it's grub.conf and fstab, deleting it's /etc/lvm/cache, and renaming the files and vg name in /etc/lvm/(backup|archive)/*), something is still looking for the old vg name. On boot, I see: ... Kernel command line: ro root=/dev/new/root s ... Loading dm-mod.ko module device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel at redhat.com Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "new" using metadata type lvm2 Activating logical volumes Unable to find volume group "old" Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! In dom0: # kpartx -a /dev/vm/new # pvscan PV /dev/dm-15 VG new lvm2 [9.88 GB / 1.94 GB free] # lvscan inactive '/dev/new/root' [1.00 GB] inherit inactive '/dev/new/usr' [5.94 GB] inherit inactive '/dev/new/swap' [1.00 GB] inherit I mounted /dev/new/root and did a find 'etc -type f|xargs grep old', and couldn't find any files that still referenced the 'old' vg. Anyone have any idea what I'm missing? From naoki at valuecommerce.com Fri Nov 24 01:32:36 2006 From: naoki at valuecommerce.com (Naoki) Date: Fri, 24 Nov 2006 10:32:36 +0900 Subject: [Fedora-xen] Updated 'xorg-x11-server' + kernel-xen = system reboot. Message-ID: <1164331956.2932.19.camel@dragon.valuecommerce.ne.jp> Howdy, I was pleased to hear Dan B's announcement of a Xorg fix that would stop the high frequency random crashing under certain intel chipsets but here are my results on my Dell GX620. Booting up is fine, all the way to GDM. At this point, without logging in, I can SSH to the machine and check no application failures, and "xm list" shows my dom0 as expected. However immediately upon successful login the system reboots. I tried three times and have now fallen back to the non-xen kernel. I was trying with "selinux=0" if that's of use. There is nothing in the messages file to indicate what the problem might be, the messages file simply contains the next kernel boot message. >From the sounds of things debugging the intel / xorg issue was a nightmare, hopefully this gremlin will be easier to tame. But is anybody else finding this issue, or just my lucky self? From tancs at comp.nus.edu.sg Fri Nov 24 03:48:37 2006 From: tancs at comp.nus.edu.sg (Tan Chee Sin) Date: Fri, 24 Nov 2006 11:48:37 +0800 Subject: [Fedora-xen] Bringing up second physical interface in Dom0 Message-ID: <45666B95.1040608@comp.nus.edu.sg> Hi, I have two physical network interfaces on my machine and I'm trying to do VLAN on a DomU via eth1 instead of eth0. On Dom0, I see peth0 but not peth1, how do I bring up peth1? cheesin From Hua.Zhang at Sun.COM Fri Nov 24 03:30:54 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Fri, 24 Nov 2006 11:30:54 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061122121852.GE13945@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> Message-ID: <4566676E.1040706@sun.com> hi Dan, I think it over, and seems more concern, see below, Daniel P. Berrange ??: > On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote: > >> Hi Daniel, >> >> Here I have another question on virt-manager, as you write "an embedded >> VNC client viewer provides console access to each of the guest domains", >> my concern is where is the vnc server, who provide it, and start it? >> Need we setup vnc? I looked through the process used to create guest, >> seems there is no any step for vnc... >> > > The VNC server depends on what type of domain is being run. For HVM guests > the VNC server is provided by the qemu-dm process assoicated with that > guest. For paravirt guests, VNC is only available if you have the paravirt > framebuffer patches applied to your xen tree - these are not in xen-unstable > yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC > server. due to vnc connection is required by vnc-viewer, vnc-viewer can present the graphical console, because there is no paravirt framebuffer patches applied to xen-unstable, so virt-manager can't work with xen-unstable for paravirt guests, because we can't get the graphical console run. is it right? xen-unstable should be the latest version of Xen, if it has no paravirt framebuffer patches, maybe xen-stable should have no either? and if so, we may say virt-manager not support paravirt at the moment? > So in both case all you need to do is set 'vnc=1' in the guest > config file & XenD will ensure the VNC servers are started as required. > > Dan. > From berrange at redhat.com Fri Nov 24 03:59:12 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 24 Nov 2006 03:59:12 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <4566676E.1040706@sun.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <4566676E.1040706@sun.com> Message-ID: <20061124035912.GA1197@redhat.com> On Fri, Nov 24, 2006 at 11:30:54AM +0800, Henry Zhang wrote: > hi Dan, I think it over, and seems more concern, see below, > > Daniel P. Berrange ??????: > >On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote: > > > >>Hi Daniel, > >> > >>Here I have another question on virt-manager, as you write "an embedded > >>VNC client viewer provides console access to each of the guest domains", > >>my concern is where is the vnc server, who provide it, and start it? > >>Need we setup vnc? I looked through the process used to create guest, > >>seems there is no any step for vnc... > >> > > > >The VNC server depends on what type of domain is being run. For HVM guests > >the VNC server is provided by the qemu-dm process assoicated with that > >guest. For paravirt guests, VNC is only available if you have the paravirt > >framebuffer patches applied to your xen tree - these are not in > >xen-unstable > >yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC > >server. > due to vnc connection is required by vnc-viewer, vnc-viewer can present > the graphical console, > because there is no paravirt framebuffer patches applied to > xen-unstable, so virt-manager can't work > with xen-unstable for paravirt guests, because we can't get the > graphical console run. is it right? That is correct - the paravirt framebuffer patches are no yet in the xen-unstable tree. In Fedora kernels we apply them as a patch ourselves since it was important to have graphical console available for both PV and FV guests in the same way. So any FC5, FC6 or RHEL-5 guest has the PV framebuffer patches available already, even though they're not upstream > xen-unstable should be the latest version of Xen, if it has no paravirt > framebuffer patches, maybe xen-stable > should have no either? and if so, we may say virt-manager not support > paravirt at the moment? The PV framebuffer patches have been submitted several times & it looks like they are very close to being merged upstream. Perhaps next couple of weeks if all goes well. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Nov 24 04:05:14 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 24 Nov 2006 04:05:14 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <45665E5D.3050405@sun.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> Message-ID: <20061124040514.GB1197@redhat.com> On Fri, Nov 24, 2006 at 10:52:13AM +0800, Henry Zhang wrote: > > Thanks Dan, please see comments below.. :) > > Daniel P. Berrange ??????: > >On Thu, Nov 23, 2006 at 07:54:24PM +0800, Henry Zhang wrote: > > > >>hi Daniel, > >> > >>From the webpage, I can see that dbus and gnome-python-desktop are > >>optional, but when our release engineer try to build, seems they are > >>not, so could you confirm me if we can build/run virt-manager correctly > >>without Dbus? > >> > > > >Ah, I should perhaps clarify that a little. The DBus python libraries > >are required to be present, but you don't have to have DBus running. > So can I say: Dbus is necessary one for building virt-manager, while not > when running it? The DBus python libraries *are* needed at runtime. If the DBus daemon isn't present though, we catch the connection failure and disable that piece of the virtmanager functionality on the fly. > > If it fails to connect to the DBus daemon, the app will log a warning and > >continue. The GNome Python Desktop stuff is competely optional - if you > >don't have the python bindings installed it will simply disable the VNC > >password saving altogether. > > > > > >>I carefully read the content in "Dbus Services", My understanding is > >>that Dbus in virt-manager is used to make other external application > >>call some core function, so that they can get display the window/dialog . > >>When Dbus is used? > >> > >>"The remote control module provides the DBus service > >> allowing various UI > >>functions to be controlled remotely.": My understanding for "remotely" > >>is to run virt-manager remotely, is it correct? so will dbus only used > >>when remotely? if some application in local machine, it may also use > >>Dbus to run some function? > >> > > > >Not quite - the intent with the DBus stuff is that if you run two copies > >of virt-manager on the same machine, > For "two copies of virt-manager": my understanding is: > Case 1: when I login, and run %/usr/binvirt-manager, then when I run > %/usr/bin/virt-manager in the same machine again, > the second one is the copy of first one, and just use DBus/RPC to call. Yes, the first copy you run of 'virt-manager' pops up the window directly. The second concurrent copy will send a DBus message to the first, asking it to popup a particular window, and then the second copy exits - since the first copy is dealing with it now. > Case2: When I login machine A, run %/usr/binvirt-manager, then remotely > access machine A through machine B, > and run %/usr/bin/virt-manager again, so in this case, the second one is > the copy of the first one, and use Dbus/RPC. In most cases the DBus daemon is only available if you are logged into a local X / GNOME desktop session. If you are ssh'ing into a machine remotely it typically won't have DBus session available. So, when DBus isn't available, many copies of virt-manager will be launched and have no way to detect that another copy is already running. When the DBus folks get the DBus connection automatically forwarding over SSH, in the same way that X11 is forwarded, then the remote case will work in same way as local case. I've no idea when that'll be made to work though. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From roger at gwch.net Fri Nov 24 07:08:26 2006 From: roger at gwch.net (Roger Grosswiler) Date: Fri, 24 Nov 2006 08:08:26 +0100 (CET) Subject: [Fedora-xen] Installation says to less space on disk Message-ID: <12401.193.223.193.103.1164352106.squirrel@www.gwch.net> Hi, I try to install XEN on FC6 on a machine having 512 mb of ram and enough diskspace. i created a DOMU, having 2.5GB of Diskspace (Image-File), 256 MB Ram with 64 at start and ballooned Dom0 to 200 MB Ram. Everything goes well, until the installation starts to get its packages. When the download should start, i get the error message, that / just has 284 MB's of Disk available. I then tried to change the partition-scheme not to use LVM and wanted to create the scheme manually. This was mission impossible, as i had no / to indicate the mountpoints. How could i handle this? It was also strange, that i could not use the GUI-installer. btw. i tried to install via virt-manager. Thanks, Roger From Hua.Zhang at Sun.COM Fri Nov 24 12:28:24 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Fri, 24 Nov 2006 20:28:24 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061124040514.GB1197@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> <20061124040514.GB1197@redhat.com> Message-ID: <4566E568.40609@sun.com> Dan, that's great, see comments below... Daniel P. Berrange ??: > On Fri, Nov 24, 2006 at 10:52:13AM +0800, Henry Zhang wrote: > >> Thanks Dan, please see comments below.. :) >> >> Daniel P. Berrange ??????: >> >>> On Thu, Nov 23, 2006 at 07:54:24PM +0800, Henry Zhang wrote: >>> >>> >>>> hi Daniel, >>>> >>>> >>> >From the webpage, I can see that dbus and gnome-python-desktop are >>> >>>> optional, but when our release engineer try to build, seems they are >>>> not, so could you confirm me if we can build/run virt-manager correctly >>>> without Dbus? >>>> >>>> >>> Ah, I should perhaps clarify that a little. The DBus python libraries >>> are required to be present, but you don't have to have DBus running. >>> >> So can I say: Dbus is necessary one for building virt-manager, while not >> when running it? >> > > The DBus python libraries *are* needed at runtime. If the DBus daemon isn't > present though, we catch the connection failure and disable that piece of > the virtmanager functionality on the fly. > thanks, I know what you mean, now for us, the problem is we don't want to port Dbus/HAL, it means when we build virt-manager there is no Dbus/HAL in our system, if we want to succeed in building, I am thinking to delete all codes relative to Dbus, I find they are almost in remote.py, and some code in makefile, create.py and virt-manager.py.in, do you think it's ok? > >>> If it fails to connect to the DBus daemon, the app will log a warning and >>> continue. The GNome Python Desktop stuff is competely optional - if you >>> don't have the python bindings installed it will simply disable the VNC >>> password saving altogether. >>> >>> >>> >>>> I carefully read the content in "Dbus Services", My understanding is >>>> that Dbus in virt-manager is used to make other external application >>>> call some core function, so that they can get display the window/dialog . >>>> When Dbus is used? >>>> >>>> "The remote control module provides the DBus service >>>> allowing various UI >>>> functions to be controlled remotely.": My understanding for "remotely" >>>> is to run virt-manager remotely, is it correct? so will dbus only used >>>> when remotely? if some application in local machine, it may also use >>>> Dbus to run some function? >>>> >>>> >>> Not quite - the intent with the DBus stuff is that if you run two copies >>> of virt-manager on the same machine, >>> >> For "two copies of virt-manager": my understanding is: >> Case 1: when I login, and run %/usr/binvirt-manager, then when I run >> %/usr/bin/virt-manager in the same machine again, >> the second one is the copy of first one, and just use DBus/RPC to call. >> > > Yes, the first copy you run of 'virt-manager' pops up the window directly. > The second concurrent copy will send a DBus message to the first, asking > it to popup a particular window, and then the second copy exits - since the > first copy is dealing with it now. > So it seems only when in one machine, Dbus is used, so why named remote control and in remote.py? My understanding is when second copy is running, if there is first one is running, send Dbus message, and in the end exit, so there is only one virt-manager running there, but when I try in Fedaro 6, seems I can run several virt-manager after I login. a little weird.. :) > >> Case2: When I login machine A, run %/usr/binvirt-manager, then remotely >> access machine A through machine B, >> and run %/usr/bin/virt-manager again, so in this case, the second one is >> the copy of the first one, and use Dbus/RPC. >> > > In most cases the DBus daemon is only available if you are logged into > a local X / GNOME desktop session. If you are ssh'ing into a machine > remotely it typically won't have DBus session available. So, when DBus > isn't available, many copies of virt-manager will be launched and have > no way to detect that another copy is already running. > > When the DBus folks get the DBus connection automatically forwarding > over SSH, in the same way that X11 is forwarded, then the remote case > will work in same way as local case. I've no idea when that'll be > made to work though. > > Regards, > Dan. > From ian.patton at gmail.com Fri Nov 24 14:38:38 2006 From: ian.patton at gmail.com (Ian Patton) Date: Fri, 24 Nov 2006 09:38:38 -0500 Subject: [Fedora-xen] Windows Vista RC1 on Xen 3.0.3 FC6 In-Reply-To: <20061123010116.GB32283@redhat.com> References: <1579d8590611221458h2d128c7pb0135449737b492b@mail.gmail.com> <20061123004655.GC24782@redhat.com> <20061123010116.GB32283@redhat.com> Message-ID: <1579d8590611240638p12078c3v406bdb8482f00c2d@mail.gmail.com> I got the memory warning message to go away... Does anyone know what this means? False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 My DomU runs for about 5 seconds and then drops to 0% CPU and just shows a black screen Thanks, Ian On 11/22/06, Daniel P. Berrange wrote: > > On Thu, Nov 23, 2006 at 12:46:55AM +0000, Daniel P. Berrange wrote: > > On Wed, Nov 22, 2006 at 05:58:22PM -0500, Ian Patton wrote: > > > Hello, > > > > > > I now have Windows Vista RC1 attempting to boot using the following > hvm > > > file: > > > > > > # Automatically generated xen config file > > > name = "WindowsVistaRC1" > > > builder = "hvm" > > > memory = "784" > > > > [snip] > > > > > raise VmError( > > > VmError: I need 1070492 KiB, but dom0_min_mem is 262144 and shrinking > to > > > 262144 KiB would leave only 773804 KiB free. > > > > You asked for 784 MB of ram for the guest, but it was only able to free > > up 773804 KiB from Dom0. Either reduce the amount of RAM you give to > > the guest, or make more free memory in Dom0. > > I should also mention that the HV will always require a few MB more than > you actually request, to maintain the shadow pagetables & other bookeeping > data structs. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=| > -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Nov 24 15:40:10 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 24 Nov 2006 15:40:10 +0000 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <4566E568.40609@sun.com> References: <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> <20061124040514.GB1197@redhat.com> <4566E568.40609@sun.com> Message-ID: <20061124154010.GA29762@redhat.com> On Fri, Nov 24, 2006 at 08:28:24PM +0800, Henry Zhang wrote: > Dan, > > that's great, see comments below... > > Daniel P. Berrange ??????: > >On Fri, Nov 24, 2006 at 10:52:13AM +0800, Henry Zhang wrote: > > > >>Thanks Dan, please see comments below.. :) > >> > >>Daniel P. Berrange ??????: > >> > >>>On Thu, Nov 23, 2006 at 07:54:24PM +0800, Henry Zhang wrote: > >>> > >>> > >>>>hi Daniel, > >>>> > >>>> > >>>>From the webpage, I can see that dbus and gnome-python-desktop are > >>> > >>>>optional, but when our release engineer try to build, seems they are > >>>>not, so could you confirm me if we can build/run virt-manager correctly > >>>>without Dbus? > >>>> > >>>> > >>>Ah, I should perhaps clarify that a little. The DBus python libraries > >>>are required to be present, but you don't have to have DBus running. > >>> > >>So can I say: Dbus is necessary one for building virt-manager, while not > >>when running it? > >> > > > >The DBus python libraries *are* needed at runtime. If the DBus daemon isn't > >present though, we catch the connection failure and disable that piece of > >the virtmanager functionality on the fly. > > > thanks, I know what you mean, > now for us, the problem is we don't want to port Dbus/HAL, it means when > we build virt-manager there is no Dbus/HAL in our system, if we want to > succeed in building, I am thinking to delete all codes relative to Dbus, > I find they are almost in remote.py, and some code in makefile, > create.py and virt-manager.py.in, do you think it's ok? Yes, it should be pretty straightforward for you to remove the DBus bits completely - just remove the src/virtManager/remote.py file, and any referneces to DBus in srv/virt-manager.py.in FYI, though I assume (from your email address) you're trying to get this working on Solaris ? DBus should work on Solaris already, and I'm told that there is also already a port of HAL to Solaris. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From ianbrn at gmail.com Sat Nov 25 20:00:57 2006 From: ianbrn at gmail.com (Ian Brown) Date: Sat, 25 Nov 2006 22:00:57 +0200 Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 Message-ID: Hello, I have fc6 which runs on AMD x86_64. I have SVM support in this processor; still I want to create x86_64 fully virtualized guest OS , based on FC6. So I ran virt-mananger (I have virt-manager-0.2.3-2.fc6 rpm , which came with the installation). After I enter parameters and click "finish" it starts doing something, but after about a minute or two it stops giving the following error: "Guest install error" ERROR: VirDomainCreateLinux() failed I had tried this 3 times, each time getting the same error. The parameters I had chosen are: MachineName: guestFC6 Virtulaization Method: Paravirtualized installation source: http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ Disk Image: /work/xenGuest/guest Disk Size: 2000MB Maximum memory: 500 MB Initial memory: 500 MB Virtual CPUs: 1 Am I doing something wrong ? is there some log where the errors are more detailed ? Regards, IB From paul at xelerance.com Sat Nov 25 22:52:55 2006 From: paul at xelerance.com (Paul Wouters) Date: Sat, 25 Nov 2006 23:52:55 +0100 (CET) Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 In-Reply-To: References: Message-ID: On Sat, 25 Nov 2006, Ian Brown wrote: > After I enter parameters and click "finish" it starts doing something, > but after about a minute or two it stops giving the following error: > "Guest install error" > ERROR: VirDomainCreateLinux() failed > > I had tried this 3 times, each time getting the same error. > > The parameters I had chosen are: > MachineName: guestFC6 > Virtulaization Method: Paravirtualized > installation source: > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ Did you try a different url? Perhaps the web/ftp server was full? Try another, eg: ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/x86_64/os/ ? Paul From Hua.Zhang at Sun.COM Sun Nov 26 03:53:25 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Sun, 26 Nov 2006 11:53:25 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061124154010.GA29762@redhat.com> References: <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> <20061124040514.GB1197@redhat.com> <4566E568.40609@sun.com> <20061124154010.GA29762@redhat.com> Message-ID: <45690FB5.8060806@sun.com> >> thanks, I know what you mean, >> now for us, the problem is we don't want to port Dbus/HAL, it means when >> we build virt-manager there is no Dbus/HAL in our system, if we want to >> succeed in building, I am thinking to delete all codes relative to Dbus, >> I find they are almost in remote.py, and some code in makefile, >> create.py and virt-manager.py.in, do you think it's ok? >> > > Yes, it should be pretty straightforward for you to remove the DBus bits > completely - just remove the src/virtManager/remote.py file, and any referneces > to DBus in srv/virt-manager.py.in > > FYI, though I assume (from your email address) you're trying to get this > working on Solaris ? DBus should work on Solaris already, and I'm told > that there is also already a port of HAL to Solaris. > yeah, HAL/DBus have been in Solaris, but at some version, the porting work have not done.. > Regards, > Dan. > From ianbrn at gmail.com Sun Nov 26 13:44:00 2006 From: ianbrn at gmail.com (Ian Brown) Date: Sun, 26 Nov 2006 15:44:00 +0200 Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 In-Reply-To: References: Message-ID: Hello, 1) Ok, I did succeed with an alternate web site; and the process was finished ok. Then I close the virt-manager; xm list shows now only domain 0. How can I now restart that guest domain ? Resatring the virt-manager does not restart it , as xm list shows. (let's assume that the file where the guest domain was created is /home/ian/xenGuest) 2) Regarding Ian Patton remark - I meant para virtualized and not fully virtualized guest; it was a miskate from me to talk about fully virtualized guest,sorry. Regards, Ian On 11/26/06, Paul Wouters wrote: > On Sat, 25 Nov 2006, Ian Brown wrote: > > > After I enter parameters and click "finish" it starts doing something, > > but after about a minute or two it stops giving the following error: > > "Guest install error" > > ERROR: VirDomainCreateLinux() failed > > > > I had tried this 3 times, each time getting the same error. > > > > The parameters I had chosen are: > > MachineName: guestFC6 > > Virtulaization Method: Paravirtualized > > installation source: > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ > > Did you try a different url? Perhaps the web/ftp server was full? Try > another, eg: ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/x86_64/os/ ? > > Paul > From ian.patton at gmail.com Sun Nov 26 14:21:26 2006 From: ian.patton at gmail.com (Ian Patton) Date: Sun, 26 Nov 2006 09:21:26 -0500 Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 In-Reply-To: References: Message-ID: <1579d8590611260621sc9f3f70q168154bbfd28b1f@mail.gmail.com> if you have created the domain with virt-manager, look in /etc/xen/ to see what the name of the config file is. if you called it "guestFC6" for instance, To restart that domain in the future, you can just type 'xm create guestFC6' To make it start automatically on system reboot, move that file into /etc/xen/auto/ Ian Patton On 11/26/06, Ian Brown wrote: > > Hello, > 1) Ok, I did succeed with an alternate web site; and the process was > finished ok. > Then I close the virt-manager; > xm list shows now only domain 0. > > How can I now restart that guest domain ? > Resatring the virt-manager does not restart it , as xm list shows. > (let's assume that the file where the guest > domain was created is /home/ian/xenGuest) > > 2) Regarding Ian Patton remark - I meant para virtualized and not > fully virtualized guest; it was a miskate from me to talk about fully > virtualized guest,sorry. > > Regards, > Ian > > > On 11/26/06, Paul Wouters wrote: > > On Sat, 25 Nov 2006, Ian Brown wrote: > > > > > After I enter parameters and click "finish" it starts doing something, > > > but after about a minute or two it stops giving the following error: > > > "Guest install error" > > > ERROR: VirDomainCreateLinux() failed > > > > > > I had tried this 3 times, each time getting the same error. > > > > > > The parameters I had chosen are: > > > MachineName: guestFC6 > > > Virtulaization Method: Paravirtualized > > > installation source: > > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ > > > > Did you try a different url? Perhaps the web/ftp server was full? Try > > another, eg: ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/x86_64/os/ ? > > > > Paul > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas.Sjolshagen at hp.com Sun Nov 26 14:26:38 2006 From: Thomas.Sjolshagen at hp.com (Sjolshagen, Thomas) Date: Sun, 26 Nov 2006 09:26:38 -0500 Subject: [Fedora-xen] : "Guest Install Error" while creating a paravirtualized guest with virt manager on FC6 In-Reply-To: <1579d8590611260621sc9f3f70q168154bbfd28b1f@mail.gmail.com> Message-ID: <0E766B4D32E1BC4A877197B95A04A25AA733D3@tayexc14.americas.cpqcorp.net> As a suggestion, don't move the file but rather link it (# ln -s /etc/xen/fc6guest /etc/xen/auto/fc6guest ) IIRC, the default path for xm to be looking for the config file of a guest is in /etc/xen and by moving the file to ./auto you'll have to specify the path whenever manually starting the domU (i.e. # xm create /etc/xen/auto/fc6guest in stead of # xm create fc6guest). Naturally, the problem w/having two copies of the file speaks for itself... // Thoma ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ian Patton Sent: Sunday, November 26, 2006 9:21 AM To: Ian Brown; fedora-xen at redhat.com Subject: Re: [Fedora-xen] : "Guest Install Error" while creating a paravirtualized guest with virt manager on FC6 if you have created the domain with virt-manager, look in /etc/xen/ to see what the name of the config file is. if you called it "guestFC6" for instance, To restart that domain in the future, you can just type 'xm create guestFC6' To make it start automatically on system reboot, move that file into /etc/xen/auto/ Ian Patton On 11/26/06, Ian Brown < ianbrn at gmail.com > wrote: Hello, 1) Ok, I did succeed with an alternate web site; and the process was finished ok. Then I close the virt-manager; xm list shows now only domain 0. How can I now restart that guest domain ? Resatring the virt-manager does not restart it , as xm list shows. (let's assume that the file where the guest domain was created is /home/ian/xenGuest) 2) Regarding Ian Patton remark - I meant para virtualized and not fully virtualized guest; it was a miskate from me to talk about fully virtualized guest,sorry. Regards, Ian On 11/26/06, Paul Wouters wrote: > On Sat, 25 Nov 2006, Ian Brown wrote: > > > After I enter parameters and click "finish" it starts doing something, > > but after about a minute or two it stops giving the following error: > > "Guest install error" > > ERROR: VirDomainCreateLinux() failed > > > > I had tried this 3 times, each time getting the same error. > > > > The parameters I had chosen are: > > MachineName: guestFC6 > > Virtulaization Method: Paravirtualized > > installation source: > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ > > Did you try a different url? Perhaps the web/ftp server was full? Try > another, eg: ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/x86_64/os/ ? > > Paul > -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at xelerance.com Sun Nov 26 17:36:31 2006 From: paul at xelerance.com (Paul Wouters) Date: Sun, 26 Nov 2006 18:36:31 +0100 (CET) Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 In-Reply-To: References: Message-ID: On Sun, 26 Nov 2006, Ian Brown wrote: > Hello, > 1) Ok, I did succeed with an alternate web site; and the process was > finished ok. > Then I close the virt-manager; > xm list shows now only domain 0. godo. > How can I now restart that guest domain ? xm create -c /etc/xen/yourconfigname Paul From sailer at us.ibm.com Mon Nov 27 03:13:58 2006 From: sailer at us.ibm.com (Reiner Sailer) Date: Sun, 26 Nov 2006 22:13:58 -0500 Subject: [Fedora-xen] Howto enable sHype/ACM security for Xen with FC6 Xen sources and FC6 kernels Message-ID: I have been approached for help in enabling sHype/ACM for Xen on an FC6 system using Fedora sources only. Since sHype/ACM is still disabled by default in Xen, you need to recompile and re-install Xen to enable it. I have attached a short howto, since this procedure might not be straight-forward for the general user. sHype/ACM is part of the core Xen distribution and includes mandatory access control in the Xen hypervisor. sHype controls sharing between user domains (controls which domains can communicate with each other and which domains can access which resources) and enforces anti-collocation rules (controls which domains can run simultaneously on the same platform) with simple formal security policies. Please refer to the Xen user guide section about sHype/ACM for more details and for usage/test examples and current limitations. You do not need to follow this howto if you choose to install the original Xensource.com Xen version and the 2.6.16.29 Xen kernel. In this case, the Xen user guide for sHype/ACM includes all information needed for configuration, installation, and usage examples. Feedback / corrections / improvements are welcome (I am not an FC6 specialist!). Regards Reiner =======================================HOWTO BUILD AND INSTALL SHYPE/ACM XEN FROM FEDORA CORE 6 SOURCES *********************************************************** Foreword: You can use the official Xen source install from Xensource.com and configure ACM (see Xen user guide). However, Xen comes with a 2.6.16.29 kernel by default. If you depend on a FC6 2.6.18 kernel running on Xen and you want the sHype ACM security extension, then the following document describes how to get there from a clean non-virtualized FC6 install. The following step-wise description shows how to get sources, configure them, and install them so that sHype/ACM security is enabled in Xen on FC6 for the latest FC6 kernel. Once you run sHype/ACM Xen, you can refer to the Xen user guide manual chapter (found in: ) 10 to walk through usage examples. A) Get source Xen/Kernel for FC6 (from any FC6 mirror) ====================================================== ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/updates/6/SRPMS download: kernel-2.6.18-1.2849.fc6.src.rpm ftp://ftp.linux.ncsu.edu/pub/fedora/linux/core/6/source/SRPMS download: xen-3.0.3-0.1.rc3.src.rpm B) Unpack source rpm ==================== rpm -ihv kernel-2.6.18-1.2849.fc6.src.rpm rpm -ihv xen-3.0.3-0.1.rc3.src.rpm C) Create sources and configure sHype Access Control Module for Xen =================================================================== (this step creates the sources into /usr/src/redhat/BUILD) cd /usr/src/redhat/SPECS rpmbuild -bp xen.spec rpmbuild -bp kernel-2.6.spec D) Build/Install Xen ==================== Note: it appears that most problems in this stage stem from inconsistent PAE settings in Xen and Kernel (must be the same). i) Configure + install security enabled Xen and tools: cd /usr/src/redhat/BUILD/xen-3.0.3-rc3 edit Config.mk and set following variables for PAE/no PAE: i.a) if you DON'T want PAE support (<4GB on x386): XEN_TARGET_X86_PAE ?= n ACM_SECURITY ?= y i.b) if you DO want PAE support: XEN_TARGET_X86_PAE ?= y ACM_SECURITY ?= y ii) Now save Config.mk and exit editor. iii) in the current xen-3.0.3-rc3 directory: root# (cd LibVNCServer-0.8.2; make install) root# make xen tools Note: do not just 'make' because it will take a long time to build the kernel and you are not going to use it (see below) iv) root# make install-xen; make install-tools v) Install wxPython for ez-Security Policy tool root# yum install wxPython Test: /usr/sbin/xensec_ezpolicy should bring up a GUI (close it) E) BUILD/INSTALL FC6 Kernel for Xen =================================== We only use the 2.6.18.i386 kernel from this install. Not xen. i) Configure + install FC6 Kernel for Xen: root# cd /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386 root# cp configs/kernel-2.6.18.i686-xen.config .config use 'make menuconfig' or 'make gconfig' to configure the following variables for PAE/no PAE: i.a) if you DON'T want PAE support (<4GB on x386): In submenu: Processor_type_and_features->High_Memory_Support set HIMEM to 4GB i.b) if you DO want PAE support: In submenu: Processor_type_and_features->High_Memory_Support set HIMEM to 64GB ii) Compile + Install kernel (currently, the kernel is not ACM specific) Note: If you already have a proprietary kernel installed, you might want to name the kernel by setting the LOCALVERSION config parameter. root# make all root# make modules_install root# make install F) CREATE BOOT ENTRY ==================== Mine looks as follows (using xen/kernel that were built/installed above): title XEN sHype/ACM (2.6.18-1.2849-xen) root (hd0,0) kernel /xen-3.0.3-rc3.gz module /vmlinuz-2.6.18-prep ro root=/dev/hda3 rhgb module /initrd-2.6.18-prep.img Make sure you have the initrd and that you have the proper file prefix for the files. This example assumes that you mount /boot. You might need to build the initrd manually if it does not show up in the /boot directory after the kernel make install: root #cd /boot root #mkinitrd initrd-2.6.18-prep.img 2.6.18-prep G) WHERE DO I GO FROM HERE ========================== If you boot into sHype/ACM XEN, then you need to label resources and domains. For this, you need a policy. Without it, you can start domain 0 but no other domains. Please refer to the Xen User Guide (currently chapter 10) for further information. =======================================END __________________________________________________________ Reiner Sailer, Research Staff Member, Secure Systems Department IBM T J Watson Research Ctr, 19 Skyline Drive, Hawthorne NY 10532 Phone: 914 784 6280 (t/l 863) Fax: 914 784 6205, sailer at us.ibm.com http://www.research.ibm.com/people/s/sailer/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianbrn at gmail.com Mon Nov 27 10:43:31 2006 From: ianbrn at gmail.com (Ian Brown) Date: Mon, 27 Nov 2006 12:43:31 +0200 Subject: [Fedora-xen] : "Guest Install Error" while creating a para virtualized guest with virt manager on FC6 In-Reply-To: <1579d8590611260621sc9f3f70q168154bbfd28b1f@mail.gmail.com> References: <1579d8590611260621sc9f3f70q168154bbfd28b1f@mail.gmail.com> Message-ID: Hello all, I wonder if there is a possibility to create a guest OS under FC6 with virt-manager , where as the created guest OS is from other distros , like debian/unubtu/mandriva Did anybody tried this ? Regards, IB On 11/26/06, Ian Patton wrote: > if you have created the domain with virt-manager, look in /etc/xen/ to see > what the name of the config file is. if you called it "guestFC6" for > instance, To restart that domain in the future, you can just type 'xm create > guestFC6' > > To make it start automatically on system reboot, move that file into > /etc/xen/auto/ > > Ian Patton > > > On 11/26/06, Ian Brown < ianbrn at gmail.com> wrote: > > > > Hello, > > 1) Ok, I did succeed with an alternate web site; and the process was > > finished ok. > > Then I close the virt-manager; > > xm list shows now only domain 0. > > > > How can I now restart that guest domain ? > > Resatring the virt-manager does not restart it , as xm list shows. > > (let's assume that the file where the guest > > domain was created is /home/ian/xenGuest) > > > > 2) Regarding Ian Patton remark - I meant para virtualized and not > > fully virtualized guest; it was a miskate from me to talk about fully > > virtualized guest,sorry. > > > > Regards, > > Ian > > > > > > On 11/26/06, Paul Wouters wrote: > > > On Sat, 25 Nov 2006, Ian Brown wrote: > > > > > > > After I enter parameters and click "finish" it starts doing something, > > > > but after about a minute or two it stops giving the following error: > > > > "Guest install error" > > > > ERROR: VirDomainCreateLinux() failed > > > > > > > > I had tried this 3 times, each time getting the same error. > > > > > > > > The parameters I had chosen are: > > > > MachineName: guestFC6 > > > > Virtulaization Method: Paravirtualized > > > > installation source: > > > > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ > > > > > > Did you try a different url? Perhaps the web/ftp server was full? Try > > > another, eg: > ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/x86_64/os/ ? > > > > > > Paul > > > > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > -- > Ian Patton From porjo38 at hotmail.com Mon Nov 27 12:08:54 2006 From: porjo38 at hotmail.com (. .) Date: Mon, 27 Nov 2006 22:08:54 +1000 Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge Message-ID: On Mon, 20 Nov 2006, Paul Wouters wrote: >>xenguest-install -n ftp.xtdnet.nl -f >>/children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l >> >ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi noapic" >>-r 1024 >> >> >>(the noapic noacpi was a test in the hope tht it would fix my issue). >> >>Also, I can still do xm shutdown and then I see the system halting. >Using kpartx and losetup, I checked the filesystems. They hasn't been >any writing apart from formatting done to the disk. So no logfiles of >the anaconda installer to see what went wrong either : >Paul Hi, I'm having exactly the same issue trying to load a new Xen guest system. My setup is: AMD64, 1Gig RAM, SATA Hard disk Fedora Core 6 x86_64 - Dom0 I'm using FC6 for the guest system also, installing to a partition of the hard disk - /dev/sda15 The installation source is an NFS mount of the FC6 DVD media (in the local DVD drive). It gets to the "Starting install process. This may take several minutes..." and just sits there. Every couple of minutes, the DVD drives spins up and reads but nothing else happens - like it's stuck in a loop of some kind. The log files in /var/log/xen don't give any clues. Ian. _________________________________________________________________ Advertisement: House hunt online now! http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Erealestate%2Ecom%2Eau%2Fcgi%2Dbin%2Frsearch%3Fa%3Dbhp%26t%3Dres%26cu%3DMSN&_t=758874163&_r=HM_EndText_Nov06&_m=EXT From Hua.Zhang at Sun.COM Fri Nov 24 02:52:13 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Fri, 24 Nov 2006 10:52:13 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061123145152.GA30705@redhat.com> References: <454E1DF2.90703@sun.com> <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> Message-ID: <45665E5D.3050405@sun.com> Thanks Dan, please see comments below.. :) Daniel P. Berrange ??: > On Thu, Nov 23, 2006 at 07:54:24PM +0800, Henry Zhang wrote: > >> hi Daniel, >> >> From the webpage, I can see that dbus and gnome-python-desktop are >> optional, but when our release engineer try to build, seems they are >> not, so could you confirm me if we can build/run virt-manager correctly >> without Dbus? >> > > Ah, I should perhaps clarify that a little. The DBus python libraries > are required to be present, but you don't have to have DBus running. So can I say: Dbus is necessary one for building virt-manager, while not when running it? > If it fails to connect to the DBus daemon, the app will log a warning and > continue. The GNome Python Desktop stuff is competely optional - if you > don't have the python bindings installed it will simply disable the VNC > password saving altogether. > > >> I carefully read the content in "Dbus Services", My understanding is >> that Dbus in virt-manager is used to make other external application >> call some core function, so that they can get display the window/dialog . >> >> When Dbus is used? >> >> "The remote control module provides the DBus service >> allowing various UI >> functions to be controlled remotely.": My understanding for "remotely" >> is to run virt-manager remotely, is it correct? so will dbus only used >> when remotely? if some application in local machine, it may also use >> Dbus to run some function? >> > > Not quite - the intent with the DBus stuff is that if you run two copies > of virt-manager on the same machine, For "two copies of virt-manager": my understanding is: Case 1: when I login, and run %/usr/binvirt-manager, then when I run %/usr/bin/virt-manager in the same machine again, the second one is the copy of first one, and just use DBus/RPC to call. Case2: When I login machine A, run %/usr/binvirt-manager, then remotely access machine A through machine B, and run %/usr/bin/virt-manager again, so in this case, the second one is the copy of the first one, and use Dbus/RPC. I have to understand all of these, because we have to decide if we need to support these feature, and if we need integrate Dbus. it's important to us.... > the second one will use DBus to find > the first one & just make RPC calls to it. It also allows other applications > within the local X desktop to control various bits of its UI. > > Regards, > Dan. > From paul at xelerance.com Mon Nov 27 15:50:52 2006 From: paul at xelerance.com (Paul Wouters) Date: Mon, 27 Nov 2006 16:50:52 +0100 (CET) Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: References: Message-ID: On Mon, 27 Nov 2006, . . wrote: > On Mon, 20 Nov 2006, Paul Wouters wrote: > > > >xenguest-install -n ftp.xtdnet.nl -f > > >/children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l > > > >ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi noapic" > > >-r 1024 > > > > > > > > >(the noapic noacpi was a test in the hope tht it would fix my issue). > > > > > >Also, I can still do xm shutdown and then I see the system halting. > > >Using kpartx and losetup, I checked the filesystems. They hasn't been > >any writing apart from formatting done to the disk. So no logfiles of > >the anaconda installer to see what went wrong either : > > >Paul > > Hi, > > I'm having exactly the same issue trying to load a new Xen guest system. My > setup is: > > AMD64, 1Gig RAM, SATA Hard disk > Fedora Core 6 x86_64 - Dom0 > > I'm using FC6 for the guest system also, installing to a partition of the hard > disk - /dev/sda15 > The installation source is an NFS mount of the FC6 DVD media (in the local DVD > drive). > > It gets to the "Starting install process. This may take several minutes..." > and just sits there. Every couple of minutes, the DVD drives spins up and > reads but nothing else happens - like it's stuck in a loop of some kind. The > log files in /var/log/xen don't give any clues. I did not get past this yet. I ended up doing a manual yum install with yum: yum -c yum-xen.conf --installroot=/mnt -y groupinstall Base Though perhaps next time I'll use a qemu install using the ISO DVD. Paul From porjo38 at hotmail.com Mon Nov 27 20:44:40 2006 From: porjo38 at hotmail.com (. .) Date: Tue, 28 Nov 2006 06:44:40 +1000 Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: <20061127170010.EB27873AC6@hormel.redhat.com> Message-ID: >From: fedora-xen-request at redhat.com >Reply-To: fedora-xen at redhat.com >To: fedora-xen at redhat.com >Subject: Fedora-xen Digest, Vol 12, Issue 52 >Date: Mon, 27 Nov 2006 12:00:10 -0500 (EST) > >Message: 1 >Date: Mon, 27 Nov 2006 16:50:52 +0100 (CET) >From: Paul Wouters >Subject: Re: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on > Dell poweredge >To: ". ." >Cc: fedora-xen at redhat.com >Message-ID: >Content-Type: TEXT/PLAIN; charset=US-ASCII > >On Mon, 27 Nov 2006, . . wrote: > > > On Mon, 20 Nov 2006, Paul Wouters wrote: > > > > > >xenguest-install -n ftp.xtdnet.nl -f > > > >/children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l > > > > >ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi >noapic" > > > >-r 1024 > > > > > > > > > > > >(the noapic noacpi was a test in the hope tht it would fix my issue). > > > > > > > >Also, I can still do xm shutdown and then I see the system halting. > > > > >Using kpartx and losetup, I checked the filesystems. They hasn't been > > >any writing apart from formatting done to the disk. So no logfiles of > > >the anaconda installer to see what went wrong either : > > > > >Paul > > > > Hi, > > > > I'm having exactly the same issue trying to load a new Xen guest system. >My > > setup is: > > > > AMD64, 1Gig RAM, SATA Hard disk > > Fedora Core 6 x86_64 - Dom0 > > > > I'm using FC6 for the guest system also, installing to a partition of >the hard > > disk - /dev/sda15 > > The installation source is an NFS mount of the FC6 DVD media (in the >local DVD > > drive). > > > > It gets to the "Starting install process. This may take several >minutes..." > > and just sits there. Every couple of minutes, the DVD drives spins up >and > > reads but nothing else happens - like it's stuck in a loop of some kind. >The > > log files in /var/log/xen don't give any clues. > >I did not get past this yet. I ended up doing a manual yum install with >yum: > >yum -c yum-xen.conf --installroot=/mnt -y groupinstall Base > >Though perhaps next time I'll use a qemu install using the ISO DVD. > >Paul > > > >------------------------------ > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen > > >End of Fedora-xen Digest, Vol 12, Issue 52 >****************************************** Hi Paul, That's a good idea. I'm only somewhat familiar with this method - I understand that you are mounting the Guest filesystem to /mnt then using yum to install packages onto it. Do you have a good 'howto' you can recommend that describes this procedure. Also, could you cat your yum-xen.conf file for me? I'm not sure what you mean by a 'qemu install' - can you elaborate on that? Thanks, Ian. _________________________________________________________________ Advertisement: Looking to expand your DVD collection? Go to www.tradingpost.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fwww%2Etradingpost%2Ecom%2Eau%2Fbrowse%2FEntertainment%2DElectronics%2FDVDs%2DCDs%2DVideos%2DRecords%2DTapes%2Floc%5FlocRZSQregtAVSCdistRZSQAVSCstateRZSQ9AVSCregRZSQ%5Fns%5FTrue%5Foff%5F0%5Fsqt%5F1%5Fstpg%5F0%5F%3Freferrer%3Dplace1&_t=758874129&_r=emailtagline_nov&_m=EXT From jerutley at gmail.com Mon Nov 27 20:54:20 2006 From: jerutley at gmail.com (Jeremy Utley) Date: Mon, 27 Nov 2006 12:54:20 -0800 Subject: [Fedora-xen] Need some setup pointers for using Xen in a HA system Message-ID: Hello to everyone on the list. We're looking at making our datacenter monitoring system (traffic graphs, nagios, etc) run under Xen so a machine failure doesn't kill off our entire monitoring system. Right now, all our monitoring runs on a single machine, so if that fails, we're dead in the water, which is why we want to do this. Here's what we've thought of so far. 2 identical machines running Xen-enabled All monitoring services running within domU Shared filesystem provided by GFS (Sun T3 array connected to both machines with a brocade switch) domU root filesystem is a loopback-style EXT3 on the GFS filesystem The sticky point is getting set up so that we can move the domU from one machine to the other in a live migration scenario, or activate on the other machine in the case of a crash. In the second case (crash), we'd like to automate the process so it will automatically come up properly. The distro in use for both dom0 and domU is planned to be FC6. Can any of you who have done this type of thing in a real-life scenario think of anything I've missed, or any issues with what we're thinking? Especially suggestions for automating in the case of a crash would be welcome! Thanks for any input any of you can give! Jeremy From paul at xelerance.com Mon Nov 27 20:59:45 2006 From: paul at xelerance.com (Paul Wouters) Date: Mon, 27 Nov 2006 21:59:45 +0100 (CET) Subject: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge In-Reply-To: References: Message-ID: On Tue, 28 Nov 2006, . . wrote: > That's a good idea. I'm only somewhat familiar with this method - I understand > that you are mounting the Guest filesystem to /mnt then using yum to install > packages onto it. Do you have a good 'howto' you can recommend that describes > this procedure. Also, could you cat your yum-xen.conf file for me? I'm not > sure what you mean by a 'qemu install' - can you elaborate on that? dd if=/dev/zero of=fc6-i386.img bs=1M count=1 seek=4096 /sbin/mke2fs -F -j fc6-i386.img mount -o loop fc6-i386.img /mnt mkdir /mnt/dev mkdir /mnt/proc mkdir /mnt/etc for i in console null zero ; do /sbin/MAKEDEV -d /mnt/dev -x $i ; done create /mnt/etc/fstab with: /dev/hda1 / ext3 defaults 1 1 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 mount -t proc none /mnt/proc create yum-xen.conf with: [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log exclude=*-debuginfo gpgcheck=0 obsoletes=1 reposdir=/dev/null [base] name=Fedora Core 6 - i386 - Base mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-6 enabled=1 [updates-released] name=Fedora Core 6 - i386 - Released Updates mirrorlist=http://fedora.redhat.com/download/mirrors/updates-released-fc6 enabled=1 run: yum -c yum-xen.conf --installroot=/mnt -y groupinstall Base find /mnt/var/cache/yum -name \*.rpm | xargs rm mv /mnt/lib/tls /mnt/lib/tls-disabled [edit /mnt/etc/sysconfig/selinux if you want to disabled it] sync umount /mnt create the xen config, using root=/dev/hda1 and the diskimage pointing to "hda1". Using qemu you simply do: dd if=/dev/zero of=fc6-i386.img bs=1M count=1 seek=4096 qemu -hda fc6-i386.img -cdrom fc6-dvd.iso -boot d -nographics after it is done, create the xen config using pygrub and xvda as diskimage. (like the current installer creates for you) Paul From bloch at verdurin.com Mon Nov 27 22:05:09 2006 From: bloch at verdurin.com (bloch at verdurin.com) Date: Mon, 27 Nov 2006 22:05:09 +0000 Subject: [Fedora-xen] Intel graphics problems: [ajackson@redhat.com: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6] In-Reply-To: <20061115222011.GO17466@redhat.com> References: <20061115222011.GO17466@redhat.com> Message-ID: <20061127220509.GG28540@bloch.config> On Wed, 15 Nov 2006, Daniel P. Berrange wrote: > > For anyone with an Intel graphics card who is experiancing hangs upon > boot / starting X under the Xen kernel, then I recommend testing this > updated X server RPm from updates-testing. It makes X use its own > x86 realmode emulator instead of relying on Xens. Send feedback to > the fedora-test-list at redhat.com if you have issues with this update. > Just to point out that the update made no substantial difference in my case. The system doesn't crash but X still fails to start. From ian.patton at gmail.com Tue Nov 28 00:40:23 2006 From: ian.patton at gmail.com (Ian Patton) Date: Mon, 27 Nov 2006 19:40:23 -0500 Subject: [Fedora-xen] xen partitioning for Vista Message-ID: <1579d8590611271640x5179f43o2a6cd541e1a02e03@mail.gmail.com> I added a new drive to use with a fully virtualized Xen domain. I intend to run Vista on it. Should the partition be formatted? If so, should it be formatted using ext3 or ntfs? Should the Windows installer do the partitioning? I asked this as part of a multi-part question previously an only got a partial answer excluding this.... On my system, the partition is /dev/hdc1 On my first attempt at getting Vista to work, I used a file instead of a partition and it worked. It worked for a very short period of time. Vista would boot and I could see the desktop. The only thing that did not work was the network, which I was sure would be an easy fix. I installed a few patches and some other software via Yum and at some point Vista stopped booting. I decided to add a new 120G disk for it to use and start over, but ever since I have not been able to get it to run. None of the logs show anything helpful. It runs for about 5 seconds, and I can see it boot from the ISO that I made, but after it loads the progress bar to 100% it tries to change the screen resolution or something and the processor drops to 0% and nothing else happens. Meanwhile, i have learned a bit about using Xen and tried to help others on the list, but still have gotten nowhere with my own problems. I will be posting a nice howto once i get all the steps and facts straight. Thanks in advance, Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From acathrow at redhat.com Tue Nov 28 01:12:52 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 27 Nov 2006 20:12:52 -0500 Subject: [Fedora-xen] xen partitioning for Vista In-Reply-To: <1579d8590611271640x5179f43o2a6cd541e1a02e03@mail.gmail.com> References: <1579d8590611271640x5179f43o2a6cd541e1a02e03@mail.gmail.com> Message-ID: <1164676372.18527.35.camel@amd.cathrow.org> See what happens if you give it a file instead of a physical partition. Aic On Mon, 2006-11-27 at 19:40 -0500, Ian Patton wrote: > I added a new drive to use with a fully virtualized Xen domain. I > intend to run Vista on it. Should the partition be formatted? If so, > should it be formatted using ext3 or ntfs? Should the Windows > installer do the partitioning? I asked this as part of a multi-part > question previously an only got a partial answer excluding this.... > On my system, the partition is /dev/hdc1 > > On my first attempt at getting Vista to work, I used a file instead of > a partition and it worked. It worked for a very short period of time. > Vista would boot and I could see the desktop. The only thing that did > not work was the network, which I was sure would be an easy fix. I > installed a few patches and some other software via Yum and at some > point Vista stopped booting. I decided to add a new 120G disk for it > to use and start over, but ever since I have not been able to get it > to run. None of the logs show anything helpful. It runs for about 5 > seconds, and I can see it boot from the ISO that I made, but after it > loads the progress bar to 100% it tries to change the screen > resolution or something and the processor drops to 0% and nothing else > happens. > > Meanwhile, i have learned a bit about using Xen and tried to help > others on the list, but still have gotten nowhere with my own > problems. I will be posting a nice howto once i get all the steps and > facts straight. > > Thanks in advance, > > Ian Patton > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437 6178 - Home Office acathrow at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tancs at comp.nus.edu.sg Tue Nov 28 06:18:32 2006 From: tancs at comp.nus.edu.sg (Tan Chee Sin) Date: Tue, 28 Nov 2006 14:18:32 +0800 (GMT-8) Subject: [Fedora-xen] tcpdump on DomU's eth1 Message-ID: Hi, I have a machine with 2 physical network interfaces: eth0 and eth1. I'm using FC6Xen on both Dom0 and DomU. I want to do network sniffing on DomU's eth1. When I do a tcpdump on DomU's eth1, I see nothing. But when I do it on Dom0's eth1, I can see the traffic. I have enabled promiscuous mode on Dom0's and DomU's eth1. What could possible went wrong? When I do a "ifconfig", I see peth0 but not peth1. Why is this so? The list of bridges are shown below: # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif2.0 peth0 vif0.0 xenbr1 8000.feffffffffff no vif2.1 Hope someone can help. Chee Sin From shuo.li at intel.com Tue Nov 28 07:37:02 2006 From: shuo.li at intel.com (Li, Shuo) Date: Mon, 27 Nov 2006 23:37:02 -0800 Subject: [Fedora-xen] Guest OS Reboot Message-ID: <07DDDFCFB8BE0A43BCA52E743373DBDC024FEF83@orsmsx416.amr.corp.intel.com> Hi, I installed FC5 as a guest OS on FC6 host system. I used the GUI version of virt-manager. The installation finished OK. As I tried to boot guest OS using xm create -c GuestFC5, the guest OS came up. But before for it allowed me to login, it rebooted itself. It continued to reboot itself. (most likely when it was trying to automount, but I am not certain about this) Could someone point me to where the problem is? Best Shuo Li From oehmes at de.ibm.com Tue Nov 28 08:02:21 2006 From: oehmes at de.ibm.com (Sven Oehme) Date: Tue, 28 Nov 2006 09:02:21 +0100 Subject: [Fedora-xen] Intel graphics problems: [ajackson@redhat.com: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6] In-Reply-To: <20061127220509.GG28540@bloch.config> Message-ID: with this package my system with a ATI X700 card is no longer able to start X at all , i had to boot in runlevel 3 after upgrade, if i boot in 5 the system freezes immediately. on my Laptop with a ATI V5200 Card X crashes every 2-3 time i start a AVI playback. With a Intel Card in a 3 system it works fine for me . Sven bloch at verdurin.com Sent by: fedora-xen-bounces at redhat.com 11/27/06 11:05 PM To "Daniel P. Berrange" cc fedora-xen at redhat.com Subject Re: [Fedora-xen] Intel graphics problems: [ajackson at redhat.com: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6] On Wed, 15 Nov 2006, Daniel P. Berrange wrote: > > For anyone with an Intel graphics card who is experiancing hangs upon > boot / starting X under the Xen kernel, then I recommend testing this > updated X server RPm from updates-testing. It makes X use its own > x86 realmode emulator instead of relying on Xens. Send feedback to > the fedora-test-list at redhat.com if you have issues with this update. > Just to point out that the update made no substantial difference in my case. The system doesn't crash but X still fails to start. -- 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 tscherf at redhat.com Tue Nov 28 07:41:13 2006 From: tscherf at redhat.com (Thorsten Scherf) Date: Tue, 28 Nov 2006 08:41:13 +0100 Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? In-Reply-To: <456475A0.3010100@monolive.org> References: <20061122132444.GI14185@skywalker.creative.net.au> <456475A0.3010100@monolive.org> Message-ID: <1164699673.1176.6.camel@tiffy.tuxgeek.de> Am Mittwoch, den 22.11.2006, 17:06 +0100 schrieb Monolive: > Adrian Chadd wrote: > > Hiya, > > > > I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development > > and regression testing on. Has anyone done this? Any pointers to what I should be > > looking at doing? [...] > You will find some good documentation @ > http://people.redhat.com/~riel/RHEL4-Xen-HOWTO > > If you do not have a processor with the VT extension, you can always use > qemu to install RHEL4 in FV. AFAIK, it's no longer possible to use a FV RHEL4 image which has been created with the latest version of QEMU. Reason is, that QEMU now uses Copy-on-Write disk images. -- Thorsten Scherf Red Hat GmbH -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From paul at xelerance.com Tue Nov 28 15:21:59 2006 From: paul at xelerance.com (Paul Wouters) Date: Tue, 28 Nov 2006 16:21:59 +0100 (CET) Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? In-Reply-To: <1164699673.1176.6.camel@tiffy.tuxgeek.de> References: <20061122132444.GI14185@skywalker.creative.net.au> <456475A0.3010100@monolive.org> <1164699673.1176.6.camel@tiffy.tuxgeek.de> Message-ID: On Tue, 28 Nov 2006, Thorsten Scherf wrote: > > If you do not have a processor with the VT extension, you can always use > > qemu to install RHEL4 in FV. > > AFAIK, it's no longer possible to use a FV RHEL4 image which has been > created with the latest version of QEMU. Reason is, that QEMU now uses > Copy-on-Write disk images. eh? Even if that was an issue (I am running qemu fine without COW files), then you can just boot the image with qemu, nfs mount your new image file from the xen server, copy the files onto the image, unmount, and throw away the qemu image. Paul -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From paul at xelerance.com Tue Nov 28 15:26:48 2006 From: paul at xelerance.com (Paul Wouters) Date: Tue, 28 Nov 2006 16:26:48 +0100 (CET) Subject: [Fedora-xen] tcpdump on DomU's eth1 In-Reply-To: References: Message-ID: On Tue, 28 Nov 2006, Tan Chee Sin wrote: > I have a machine with 2 physical network interfaces: eth0 and eth1. > I'm using FC6Xen on both Dom0 and DomU. I want to do network sniffing on > DomU's eth1. > > When I do a tcpdump on DomU's eth1, I see nothing. But when I do it on Dom0's > eth1, I can see the traffic. I have enabled promiscuous mode on Dom0's and > DomU's eth1. What could possible went wrong? I guess your being switched? It's probably easier to just have one xenu route through another xenu and then sniff on the "router"? Paul From berrange at redhat.com Tue Nov 28 15:31:06 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 28 Nov 2006 15:31:06 +0000 Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? In-Reply-To: <1164699673.1176.6.camel@tiffy.tuxgeek.de> References: <20061122132444.GI14185@skywalker.creative.net.au> <456475A0.3010100@monolive.org> <1164699673.1176.6.camel@tiffy.tuxgeek.de> Message-ID: <20061128153106.GD24746@redhat.com> On Tue, Nov 28, 2006 at 08:41:13AM +0100, Thorsten Scherf wrote: > Am Mittwoch, den 22.11.2006, 17:06 +0100 schrieb Monolive: > > Adrian Chadd wrote: > > > Hiya, > > > > > > I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development > > > and regression testing on. Has anyone done this? Any pointers to what I should be > > > looking at doing? > > [...] > > > You will find some good documentation @ > > http://people.redhat.com/~riel/RHEL4-Xen-HOWTO > > > > If you do not have a processor with the VT extension, you can always use > > qemu to install RHEL4 in FV. > > AFAIK, it's no longer possible to use a FV RHEL4 image which has been > created with the latest version of QEMU. Reason is, that QEMU now uses > Copy-on-Write disk images. Well, QEMU doesn't use any particular type of image by default - that's entirely up to whomever creates the disk image. QEMU has about 6 different kinds of images it is able to use. You can trivially convert between disk image formats using QEMU's own tool set, eg qemu-img convert -f qcow source.img -O raw dest.img will convert from 'qcow' format to 'raw' - the latter being the format Xen wants. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From ian.patton at gmail.com Tue Nov 28 16:21:14 2006 From: ian.patton at gmail.com (Ian Patton) Date: Tue, 28 Nov 2006 11:21:14 -0500 Subject: [Fedora-xen] xen partitioning for Vista In-Reply-To: <1164676372.18527.35.camel@amd.cathrow.org> References: <1579d8590611271640x5179f43o2a6cd541e1a02e03@mail.gmail.com> <1164676372.18527.35.camel@amd.cathrow.org> Message-ID: <1579d8590611280821x2c20acy7377f7a22872fbbf@mail.gmail.com> Using a file works. What is wrong with using a partition? Can someone please tell me how a partition needs to be created in order to work? The partition is currently unformatted. Thanks, Ian Patton On 11/27/06, Andrew Cathrow wrote: > > See what happens if you give it a file instead of a physical partition. > > Aic > > On Mon, 2006-11-27 at 19:40 -0500, Ian Patton wrote: > > I added a new drive to use with a fully virtualized Xen domain. I intend > to run Vista on it. Should the partition be formatted? If so, should it be > formatted using ext3 or ntfs? Should the Windows installer do the > partitioning? I asked this as part of a multi-part question previously an > only got a partial answer excluding this.... On my system, the partition is > /dev/hdc1 > > On my first attempt at getting Vista to work, I used a file instead of a > partition and it worked. It worked for a very short period of time. Vista > would boot and I could see the desktop. The only thing that did not work > was the network, which I was sure would be an easy fix. I installed a few > patches and some other software via Yum and at some point Vista stopped > booting. I decided to add a new 120G disk for it to use and start over, but > ever since I have not been able to get it to run. None of the logs show > anything helpful. It runs for about 5 seconds, and I can see it boot from > the ISO that I made, but after it loads the progress bar to 100% it tries to > change the screen resolution or something and the processor drops to 0% and > nothing else happens. > > Meanwhile, i have learned a bit about using Xen and tried to help others > on the list, but still have gotten nowhere with my own problems. I will be > posting a nice howto once i get all the steps and facts straight. > > Thanks in advance, > > Ian Patton > > --Fedora-xen mailing listFedora-xen at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-xen > > -- > > Andrew Cathrow > Red Hat, Inc. > > (678) 733 0452 - Mobile > (404) 437 6178 - Home Office > > acathrow at redhat.com > > -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.patton at gmail.com Tue Nov 28 16:31:48 2006 From: ian.patton at gmail.com (Ian Patton) Date: Tue, 28 Nov 2006 11:31:48 -0500 Subject: [Fedora-xen] xen partitioning for Vista In-Reply-To: <1164676372.18527.35.camel@amd.cathrow.org> References: <1579d8590611271640x5179f43o2a6cd541e1a02e03@mail.gmail.com> <1164676372.18527.35.camel@amd.cathrow.org> Message-ID: <1579d8590611280831i59408129t1c76b2aaf5300b9e@mail.gmail.com> Andrew, I just noticed something significant. It is not the partition or the file causing the problem. In my assumption I based it on the fact I used the file when using the old xen kernel 2798, and used the partition on the new xen kernel 2849 I just tested it using a file on both kernels, and it turns out that it works using a file only under the old kernel. Using the exact same config file on the new kernel does not work. I did not test using a partition on the old kernel, but I bet it would work. At last I can finally continue working on this! But, it looks like a problem that needs to be documented in the short term and fixed in the next kernel in the long term. I hope anyone else trying this finds this! Thanks for your assistance, Ian Patton On 11/27/06, Andrew Cathrow wrote: > > See what happens if you give it a file instead of a physical partition. > > Aic > > On Mon, 2006-11-27 at 19:40 -0500, Ian Patton wrote: > > I added a new drive to use with a fully virtualized Xen domain. I intend > to run Vista on it. Should the partition be formatted? If so, should it be > formatted using ext3 or ntfs? Should the Windows installer do the > partitioning? I asked this as part of a multi-part question previously an > only got a partial answer excluding this.... On my system, the partition is > /dev/hdc1 > > On my first attempt at getting Vista to work, I used a file instead of a > partition and it worked. It worked for a very short period of time. Vista > would boot and I could see the desktop. The only thing that did not work > was the network, which I was sure would be an easy fix. I installed a few > patches and some other software via Yum and at some point Vista stopped > booting. I decided to add a new 120G disk for it to use and start over, but > ever since I have not been able to get it to run. None of the logs show > anything helpful. It runs for about 5 seconds, and I can see it boot from > the ISO that I made, but after it loads the progress bar to 100% it tries to > change the screen resolution or something and the processor drops to 0% and > nothing else happens. > > Meanwhile, i have learned a bit about using Xen and tried to help others > on the list, but still have gotten nowhere with my own problems. I will be > posting a nice howto once i get all the steps and facts straight. > > Thanks in advance, > > Ian Patton > > --Fedora-xen mailing listFedora-xen at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-xen > > -- > > Andrew Cathrow > Red Hat, Inc. > > (678) 733 0452 - Mobile > (404) 437 6178 - Home Office > > acathrow at redhat.com > > -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: From e1geo at yahoo.com Wed Nov 29 03:18:36 2006 From: e1geo at yahoo.com (George Hill) Date: Tue, 28 Nov 2006 19:18:36 -0800 (PST) Subject: [Fedora-xen] Error: (12, 'Cannot allocate memory') Message-ID: <20061129031836.92168.qmail@web53615.mail.yahoo.com> Sometimes I get a cannot allocate memory error when I try to create a guest. I have plenty of memory. When I reboot the host, I no longer get the error. Any ideas on how to fix this problem? Thanks for your help. # xm create /etc/xen/FC6.virt3 Using config file "/etc/xen/FC6.virt3". Error: (12, 'Cannot allocate memory') The end of the log shows the following: [2006-11-28 19:11:00 xend 2851] DEBUG (image:467) hvm shutdown watch registered [2006-11-28 19:11:00 xend.XendDomainInfo 2851] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363, in initDomain raise VmError(str(exn)) VmError: (12, \047Cannot allocate memory\047) [2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=3 [2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(3) [2006-11-28 19:11:00 xend 2851] DEBUG (image:479) hvm shutdown watch unregistered [2006-11-28 19:11:00 xend 2851] ERROR (xswatch:70) read_watch failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xswatch.py", line 66, in watchMain res = watch.fn(we[0], *watch.args, **watch.kwargs) File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 489, in hvm_shutdown reason = vm.readDom(\047control/shutdown\047) AttributeError: \047NoneType\047 object has no attribute \047readDom\047 ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com From e1geo at yahoo.com Wed Nov 29 04:48:24 2006 From: e1geo at yahoo.com (George Hill) Date: Tue, 28 Nov 2006 20:48:24 -0800 (PST) Subject: [Fedora-xen] memory allocation issue Message-ID: <20061129044824.69232.qmail@web53605.mail.yahoo.com> Sorry for the repost, but this got burried as a possible follow-up to an old post. Was Error: (12, 'Cannot allocate memory') Sometimes I get a cannot allocate memory error when I try to create a guest. I have plenty of memory. When I reboot the host, I no longer get the error. Any ideas on how to fix this problem? Thanks for your help. # xm create /etc/xen/FC6.virt3 Using config file "/etc/xen/FC6.virt3". Error: (12, 'Cannot allocate memory') The end of the log shows the following: [2006-11-28 19:11:00 xend 2851] DEBUG (image:467) hvm shutdown watch registered [2006-11-28 19:11:00 xend.XendDomainInfo 2851] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363, in initDomain raise VmError(str(exn)) VmError: (12, \047Cannot allocate memory\047) [2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=3 [2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(3) [2006-11-28 19:11:00 xend 2851] DEBUG (image:479) hvm shutdown watch unregistered [2006-11-28 19:11:00 xend 2851] ERROR (xswatch:70) read_watch failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xswatch.py", line 66, in watchMain res = watch.fn(we[0], *watch.args, **watch.kwargs) File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 489, in hvm_shutdown reason = vm.readDom(\047control/shutdown\047) AttributeError: \047NoneType\047 object has no attribute \047readDom\047 ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com From Hua.Zhang at Sun.COM Wed Nov 29 08:43:49 2006 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Wed, 29 Nov 2006 16:43:49 +0800 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <20061124154010.GA29762@redhat.com> References: <20061105205201.GC27599@redhat.com> <454EA329.9020705@sun.com> <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> <20061124040514.GB1197@redhat.com> <4566E568.40609@sun.com> <20061124154010.GA29762@redhat.com> Message-ID: <456D4845.7050207@sun.com> Dan, > Yes, it should be pretty straightforward for you to remove the DBus bits > completely - just remove the src/virtManager/remote.py file, and any referneces > to DBus in srv/virt-manager.py.in > I checked the codes in create.py, seems if we delete DBus/HAL, we will can't list cdrom volumes when user selects "New Virtual Machine...". I think it's a big issue if not support CD install for guest Domain, And seems there is an applet named gnome-nv-applet, but I didn't find any infor from our virt-manager website, should we list it in this webpage? and seems this applet is also using DBus to access virt-manager, so if I delete DBus/HAL, seems this applet can't work eigher. I know you are expert for this tool.Could you give any good idea for that? especially for CD install.... Thanks, Henry From davidsen1 at verizon.net Wed Nov 29 02:00:29 2006 From: davidsen1 at verizon.net (Bill Davidsen) Date: Tue, 28 Nov 2006 21:00:29 -0500 Subject: [Fedora-xen] Re: virDomainCreateLinux() failed In-Reply-To: <45652957.9070706@tmr.com> References: <455E3CEC.1010806@tmr.com> <20061122163559.GF11685@redhat.com> <45652957.9070706@tmr.com> Message-ID: <456CE9BD.5090301@verizon.net> Bill Davidsen wrote: > Daniel P. Berrange wrote: >> On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote: >>> FC6, xen installed, latest updates as of five minutes ago. ASUS >>> P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >>> PAE on, virtualization on. xend running, "xm list" works, shows one >>> domain. >>> >>> >>> Install of any fully virtualized o/s fails. Sample output: >>> Would you like a fully virtualized guest (yes or no)? This will >>> allow you to run unmodified operating systems. yes >>> How much RAM should be allocated (in megabytes)? 256 >>> Would you like to enable graphics support? (yes or no) no >>> >>> >>> Starting install... >>> libvir: Xen Daemon error : GET operation failed: No such domain >>> OpenBSD-4.0 >>> libvir: Xen Daemon error : POST operation failed: (xend.err 'Error >>> creating domain: Disk image does not exist: >>> /home/davidsen/Virtual_Machines/OpenBSD-4.0a') >> >> In FC6 GA you have to make sure the file for the disk was under /xen >> to be labelled correctly. In rawhide (and the latest FC6 policy) >> we're moving to /var/lib/xen/images. This is consistent with the >> directory used on Suse, and what the next version of XenD will >> enforce. To double check what directory is setup for the SELinux >> policy you can run >> >> semanage fcontext -l | grep xen_image_t >> >> If you don't have space under /var/lib/xen/images, then either >> mount a new volume there, or bind that dir to a location which >> has extra space, eg >> >> mount --bind /some/dir/with/big/disk /var/lib/xen/images >> >> If you really really don't want to use /var/lib/xen/images at all, >> then you can define a new location in the SELinux policy using: >> >> semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' >> > This sounds like the missing piece, I can check where the current > install wants it, and then get it there in one way or another. I'll try > it some time over the long weekend and report back. > > Thanks much, I suspect this was the hint I needed. > Wasn't, unfortunately. I still get told both the ISO and the file don't exist, even though they clearly do. And after attempting a create the system eats the root filesystem so I have to reinstall. Makes for slow testing. - works with Windows and VMware, I think that lets hardware out - runs memtest86+ for hours (and fails every time I do an install). - checked with semanage, /xen and /var/lib/xen/images are listed. Can I safely resize the Dom0 down to get room to do an install? Is it related to running LVM (don't usually). I have a ton of captured logs and such, didn't want to post or load for www unless someone wants to see them. Same error as subject, log shows "file does not exist" even though the install process created the image file. -- Bill Davidsen He was a full-time professional cat, not some moonlighting ferret or weasel. He knew about these things. From tscherf at redhat.com Wed Nov 29 06:39:37 2006 From: tscherf at redhat.com (Thorsten Scherf) Date: Wed, 29 Nov 2006 07:39:37 +0100 Subject: [Fedora-xen] RHEL4 inside FC5/FC6 Dom0? In-Reply-To: <20061128153106.GD24746@redhat.com> References: <20061122132444.GI14185@skywalker.creative.net.au> <456475A0.3010100@monolive.org> <1164699673.1176.6.camel@tiffy.tuxgeek.de> <20061128153106.GD24746@redhat.com> Message-ID: <1164782377.4154.7.camel@tiffy.tuxgeek.de> Am Dienstag, den 28.11.2006, 15:31 +0000 schrieb Daniel P. Berrange: > On Tue, Nov 28, 2006 at 08:41:13AM +0100, Thorsten Scherf wrote: > > Am Mittwoch, den 22.11.2006, 17:06 +0100 schrieb Monolive: > > > Adrian Chadd wrote: > > > > Hiya, > > > > > > > > I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development > > > > and regression testing on. Has anyone done this? Any pointers to what I should be > > > > looking at doing? > > > > [...] > > > > > You will find some good documentation @ > > > http://people.redhat.com/~riel/RHEL4-Xen-HOWTO > > > > > > If you do not have a processor with the VT extension, you can always use > > > qemu to install RHEL4 in FV. > > > > AFAIK, it's no longer possible to use a FV RHEL4 image which has been > > created with the latest version of QEMU. Reason is, that QEMU now uses > > Copy-on-Write disk images. > > Well, QEMU doesn't use any particular type of image by default - that's > entirely up to whomever creates the disk image. QEMU has about 6 different > kinds of images it is able to use. > > You can trivially convert between disk image formats using QEMU's own tool > set, eg > > qemu-img convert -f qcow source.img -O raw dest.img > > will convert from 'qcow' format to 'raw' - the latter being the format Xen > wants. Ah. That's the trick. :) Thanks, Thorsten -- Thorsten Scherf, RHCE, RHCA, RHCSS Office : ++49 2064 485 321 Red Hat GLS EMEA Fax : ++49 2064 470 564 GPG KEY-ID: 3B9280BB Mobile : ++49 172 61 32 548 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From tscherf at redhat.com Wed Nov 29 07:13:36 2006 From: tscherf at redhat.com (Thorsten Scherf) Date: Wed, 29 Nov 2006 08:13:36 +0100 Subject: [Fedora-xen] SELinux HVM unfriendly? In-Reply-To: <58773.192.168.1.13.1164033522.squirrel@beatrix> References: <34576.192.168.1.13.1164014574.squirrel@beatrix> <20061120132834.GA15703@redhat.com> <58773.192.168.1.13.1164033522.squirrel@beatrix> Message-ID: <1164784416.4154.22.camel@tiffy.tuxgeek.de> Am Dienstag, den 21.11.2006, 00:38 +1000 schrieb Robert Thiem: > > In FC6 GA you had to make sure the file for the disk was under /xen > > to be labelled correctly. In rawhide (and I think latest FC6 policy) > > we're moving to /var/lib/xen/images. To see what the required dir is > > run > > semanage context -l | grep xen_image_t > > You can also define new locations any time you like using semanage, > > eg > > semanage fcontext -a -f "" -t xen_image_t '/some/directory(/.*)?' > > I had a look at that when I first came across the problem and found it > mentioned on the list archives. > > AFAIK that's fine. All the images come up with the > system_u:object_r:xen_image_t context when I do an ls -Z. > > "semanage fcontext -l | grep xen_image_t" yields the expected > /extra/xen(/.*)?all files system_u:object_r:xen_image_t:s0 > along with "/xen(/.*)?" and the new "/var/lib/xen/images(/.*)?" relabeling doesn't fix the problem? Happy Day. Thorsten -- Thorsten Scherf, RHCE, RHCA, RHCSS Office : ++49 2064 485 321 Red Hat GLS EMEA Fax : ++49 2064 470 564 GPG KEY-ID: 3B9280BB Mobile : ++49 172 61 32 548 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From kzak at redhat.com Wed Nov 29 10:16:08 2006 From: kzak at redhat.com (Karel Zak) Date: Wed, 29 Nov 2006 11:16:08 +0100 Subject: [Fedora-xen] What's the Pre-requisites for virt-manager In-Reply-To: <456D4845.7050207@sun.com> References: <20061106044542.GA28547@redhat.com> <456434FB.6050005@sun.com> <20061122121852.GE13945@redhat.com> <45658BF0.60505@sun.com> <20061123145152.GA30705@redhat.com> <45665E5D.3050405@sun.com> <20061124040514.GB1197@redhat.com> <4566E568.40609@sun.com> <20061124154010.GA29762@redhat.com> <456D4845.7050207@sun.com> Message-ID: <20061129101608.GT2671@petra.dvoda.cz> On Wed, Nov 29, 2006 at 04:43:49PM +0800, Henry Zhang wrote: > Dan, > >Yes, it should be pretty straightforward for you to remove the DBus bits > >completely - just remove the src/virtManager/remote.py file, and any > >referneces > >to DBus in srv/virt-manager.py.in > > > I checked the codes in create.py, seems if we delete DBus/HAL, we will > can't list cdrom volumes when user > selects "New Virtual Machine...". I think it's a big issue if not > support CD install for guest Domain, > > And seems there is an applet named gnome-nv-applet, but I didn't find > any infor from our virt-manager website, http://people.redhat.com/kzak/gnome-applet-vm/ Hehe, you're right -- Dan forgot add the link to his web site :-) > should we list it in this webpage? and seems this applet is also using > DBus to access virt-manager, so if I delete > DBus/HAL, seems this applet can't work eigher. The latest versions of the applet and virt-manager are able to collaborate without DBUS. Karel -- Karel Zak From filipe.miranda at gmail.com Wed Nov 29 13:14:19 2006 From: filipe.miranda at gmail.com (Filipe Miranda) Date: Wed, 29 Nov 2006 11:14:19 -0200 Subject: [Fedora-xen] Xen-kernel with no PAE support Message-ID: Hello, Since I have a thinkpad T41 with a non PAE CPU, unfortunately the xen-kernel that comes with the FC6 does not work. I know that the upstreams of the xen-kernel for FC6 will only work on CPUs with PAE support, but what would be the best way to have a xen-kernel what would have no-PAE support? I downloaded the src xen-kernel file from the FC6 repositories and tried to disable the PAE support. No success, it seems that the xen itself is PAE aware. Is there any *smart* suggestion on how to compile or get a xen-kernel that would work on a non-PAE CPU? Regards, -- --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Wed Nov 29 16:55:41 2006 From: clalance at redhat.com (Chris Lalancette) Date: Wed, 29 Nov 2006 11:55:41 -0500 Subject: [Fedora-xen] Xen-kernel with no PAE support In-Reply-To: References: Message-ID: <456DBB8D.70304@redhat.com> Filipe Miranda wrote: > Hello, > > Since I have a thinkpad T41 with a non PAE CPU, unfortunately the > xen-kernel that comes with the FC6 does not work. > I know that the upstreams of the xen-kernel for FC6 will only work on > CPUs with PAE support, but what would be the best way to have a > xen-kernel what would have no-PAE support? > > I downloaded the src xen-kernel file from the FC6 repositories and tried > to disable the PAE support. No success, it seems that the xen itself is > PAE aware. > > Is there any *smart* suggestion on how to compile or get a xen-kernel > that would work on a non-PAE CPU? > > Regards, > > -- > --- > Filipe T Miranda > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Filipe, You have two options: 1) Use an FC5 -xen0 kernel; those didn't have PAE enabled. However, that also means that your guests have to use the FC5 -xenU kernels, which also don't have PAE enabled. 2) Recompile both the hypervisor and the -xen kernel on FC6 to remove PAE support. The problem with this approach is that all of the FC6 guest kernels have PAE enabled, so you won't be able to use any of the normal tools (virt-install, virt-manager, etc) to install the guests without some effort. If you want to do 2), you basically have to: a) install FC6 kernel src RPM. b) rpmbuild -bp kernel-2.6.spec c) cd BUILD/kernel-2.6.18/xen d) make verbose=y crash_debug=y e) cp xen.gz /boot f) cd BUILD/kernel-2.6.18/linux-2.6.18 g) make menuconfig -> set to NOHIGHMEM h) make i) make modules_install j) make install And then setup your grub.conf to point to the right hypervisor/kernel. Note that all of the above is from memory and not tested; it's just approximately what you have to do. No, it's not pretty. Chris Lalancette From thiago.morais at caprioli.com.br Thu Nov 30 15:07:16 2006 From: thiago.morais at caprioli.com.br (Thiago Morais) Date: Thu, 30 Nov 2006 13:07:16 -0200 Subject: [Fedora-xen] Error Xen Message-ID: <007501c71491$3d1b4800$0b1e10ac@caprioli.com.br> Hello, I'm trying start one guest OS, Fedora 5, on Xen 3 in Fedora Core 6, but during the booting process I get this error: 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) My configuration file: kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" memory = 64 name = "vm1" disk = [ 'phy:/dev/volgrp/vmdisk1,sda1,w','phy:/dev/volgrp/swdisk1,sda2,w' ] root = "/dev/sda1 ro" extra = "4" What can I do? Thanks! Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From filipe.miranda at gmail.com Thu Nov 30 19:52:29 2006 From: filipe.miranda at gmail.com (Filipe Miranda) Date: Thu, 30 Nov 2006 17:52:29 -0200 Subject: [Fedora-xen] Mouse out of sync on guest machines Message-ID: Hello, After installing FC6 and the virtualization pack, I managed to install a FC6 as guest OS. No problem at all (just the fact that I had to set xm mem-set 0 256, and them xm mem-max 0 256 for the the virtual manager to let me create the guest machines *my machine has 512RAM) Anyway, everything worked just fine, but I noticed the the my mouse pointer is totally out of sync in either text mode or graphic mode. Is anyone having the same issue? Or is it a bug? or a misconfiguration? Regards, -- --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From pspuhler at ball.com Thu Nov 30 20:43:02 2006 From: pspuhler at ball.com (Spuhler, Peter) Date: Thu, 30 Nov 2006 13:43:02 -0700 Subject: [Fedora-xen] Mouse out of sync on guest machines Message-ID: <7575324F915A05448800386F6CEAF3670454C7C8@AEROMSG2.AERO.BALL.COM> Yes I've been experiencing the same mouse problem although less noticeably when using SDL and have also had the keyboard lock up. Sofar I haven't seen a solution to this problem. My setup in a 2cpu dual-core machine running FC6-64. I've had this problem with both FC6 and windows as an unmodified guest OS. ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Filipe Miranda Sent: Thursday, November 30, 2006 12:52 PM To: fedora xen Subject: [Fedora-xen] Mouse out of sync on guest machines Hello, After installing FC6 and the virtualization pack, I managed to install a FC6 as guest OS. No problem at all (just the fact that I had to set xm mem-set 0 256, and them xm mem-max 0 256 for the the virtual manager to let me create the guest machines *my machine has 512RAM) Anyway, everything worked just fine, but I noticed the the my mouse pointer is totally out of sync in either text mode or graphic mode. Is anyone having the same issue? Or is it a bug? or a misconfiguration? Regards, -- --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From armbru at redhat.com Thu Nov 30 20:45:42 2006 From: armbru at redhat.com (Markus Armbruster) Date: Thu, 30 Nov 2006 21:45:42 +0100 Subject: [Fedora-xen] Mouse out of sync on guest machines In-Reply-To: (Filipe Miranda's message of "Thu, 30 Nov 2006 17:52:29 -0200") References: Message-ID: <87mz68y87d.fsf@pike.pond.sub.org> "Filipe Miranda" writes: > Hello, > > After installing FC6 and the virtualization pack, I managed to install a FC6 as > guest OS. No problem at all (just the fact that I had to set xm mem-set 0 256, > and them xm mem-max 0 256 for the the virtual manager to let me create the > guest machines *my machine has 512RAM) > > Anyway, everything worked just fine, but I noticed the the my mouse pointer is > totally out of sync in either text mode or graphic mode. > Is anyone having the same issue? Or is it a bug? or a misconfiguration? > > Regards, PV or FV? FV is a known issue, and it is being worked on. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201220 From ian.patton at gmail.com Thu Nov 30 22:22:18 2006 From: ian.patton at gmail.com (Ian Patton) Date: Thu, 30 Nov 2006 17:22:18 -0500 Subject: [Fedora-xen] Networking inside DomU Message-ID: <1579d8590611301422t3f0d60f3jd73a703adcb2fa82@mail.gmail.com> Does anyone know what is required to get networking working inside of a DomU? I have only one running, and it is using the default network-bridge setup from virt-manager I am running Vista in the domain and it sees the virtual NIC, but gives it one of those auto-config IP addresses from the 169.254.x.x range Thanks in advance -- Ian Patton -------------- next part -------------- An HTML attachment was scrubbed... URL: