From haircut at gmail.com Thu Feb 1 01:35:54 2007 From: haircut at gmail.com (Adam Monsen) Date: Wed, 31 Jan 2007 17:35:54 -0800 Subject: [Fedora-xen] switching virtual terminals when viewing serial console Message-ID: <9ebd65110701311735k5b23bff4m8bf2c0e27192a3ca@mail.gmail.com> Is it possible to switch virtual terminals when viewing a Xen console? For instance, I'm using virt-manager to install a guest OS of Fedora rawhide. During the install, it would be helpful if I could see the other virtual terminals, like when I press ALT-F2 during a bare-metal text-based install (or CTRL-ALT-F2 during a graphical install). -- Adam Monsen -------------- next part -------------- An HTML attachment was scrubbed... URL: From master at bradleyland.com Thu Feb 1 04:15:23 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Wed, 31 Jan 2007 20:15:23 -0800 (PST) Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131191928.GA24206@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> Message-ID: <4781.192.168.2.92.1170303323.squirrel@www.bradleyland.com> The problem comes about when you update the kernel with yum. In my experience (like all good lessons, learned the hard way), the initrd is created on the fly and does not include xenblk. You cannot just take the initrd that ends up in the /boot directory and use it for your guest. Doesn't work. Now I know this, it's an easy matter to create a fresh initrd and include the xenblk module. Maybe there's a smarter way to do this. If so, it escapes me. From jtower at gmail.com Thu Feb 1 06:18:49 2007 From: jtower at gmail.com (Jason Tower) Date: Thu, 1 Feb 2007 01:18:49 -0500 Subject: [Fedora-xen] migration from fc5 to fc6 fails Message-ID: i have several fc5 dom0 servers booting ubuntu-based domUs with stock fc5 domU kernel and initrd, works beautifully. however, those same exact domUs fail to boot under fc6 (kernel panic, can't find /). it's even the same hardware (dell 2650 server) - a given domU filesystem/kernel/initrd combo works great under fc5, but fails under fc6. any thoughts? From berrange at redhat.com Thu Feb 1 12:37:38 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 1 Feb 2007 12:37:38 +0000 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <4781.192.168.2.92.1170303323.squirrel@www.bradleyland.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> <4781.192.168.2.92.1170303323.squirrel@www.bradleyland.com> Message-ID: <20070201123738.GB1430@redhat.com> On Wed, Jan 31, 2007 at 08:15:23PM -0800, master at bradleyland.com wrote: > The problem comes about when you update the kernel with yum. In my > experience (like all good lessons, learned the hard way), the initrd is > created on the fly and does not include xenblk. You cannot just take the > initrd that ends up in the /boot directory and use it for your guest. > Doesn't work. > > Now I know this, it's an easy matter to create a fresh initrd and include > the xenblk module. Maybe there's a smarter way to do this. If so, it > escapes me. The smarter way is to keep the kernel & initrd / RPM installed inside the guest OS itself. So doing yum update in the host doesn't have any risk of breaking your guests, and doing yum update inside the guest will ensure that the automatically created initrd is correct wrt to that guest's virtual hardware setup. The reason the default initrd for kernel-xen in the host is not working for the guest is that the initrd generated to be suitable for booting the host OS which has real hardware. If you're keeping initrds for the guest in the host filesystem, then you're always going to have to manually create yourself a new initrd whenever kernel-xen in the host is upgraded. 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 Thu Feb 1 12:41:00 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 1 Feb 2007 12:41:00 +0000 Subject: [Fedora-xen] switching virtual terminals when viewing serial console In-Reply-To: <9ebd65110701311735k5b23bff4m8bf2c0e27192a3ca@mail.gmail.com> References: <9ebd65110701311735k5b23bff4m8bf2c0e27192a3ca@mail.gmail.com> Message-ID: <20070201124100.GC1430@redhat.com> On Wed, Jan 31, 2007 at 05:35:54PM -0800, Adam Monsen wrote: > Is it possible to switch virtual terminals when viewing a Xen console? > > For instance, I'm using virt-manager to install a guest OS of Fedora > rawhide. During the install, it would be helpful if I could see the other > virtual terminals, like when I press ALT-F2 during a bare-metal text-based > install (or CTRL-ALT-F2 during a graphical install). You can use the (undocumented :-) sticky keys feature of virt-manager. If you press the same modifier key 3 times in a row, it wil stay active until the next non-modifier is pressed. eg Ctrl Ctrl Ctrl Alt+F2 will send Ctlr+Alt+F2 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 frommetoyou at comxnet.dk Thu Feb 1 20:56:33 2007 From: frommetoyou at comxnet.dk (Karsten Rasmussen) Date: Thu, 1 Feb 2007 21:56:33 +0100 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem Message-ID: <000c01c74643$75b41dc0$65ca4857@xcomp> Hi I am trying to install Windows XP Pro on Fedora Core 6 with Xen. Iam using the graphically interface to create a new session. The windows install DVD is a OEM Rescue DVD. The installation starts fine. The installation passes the point where it is posible to press F6 to install driver The installation writes Please Wait" and the CPU load drops to 0 and does not continue. Any Ideas? Regards K Rasmussen System: I am running FC6 with SElinux in permissive mode: I have trie to upgrade to kernel-xen 2.6.19-1.2895 with no luck - I only got problems shutting down the system with "hda lost interrupt" mesages so I returned the the default installed version. Varius Logs appended: xend.log xend-debug.log xen-hotplug.log qemu-dm.3829.log message audit.log ************ xend.log ***************** [2007-02-01 21:08:52 xend 3394] INFO (SrvDaemon:283) Xend Daemon started [2007-02-01 21:08:52 xend 3394] INFO (SrvDaemon:287) Xend changeset: unavailable . [2007-02-01 21:08:52 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:212) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 186093836980L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 1915320, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [2007-02-01 21:08:52 xend.XendDomainInfo 3394] INFO (XendDomainInfo:224) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2007-02-01 21:08:52 xend.XendDomainInfo 3394] WARNING (XendDomainInfo:246) No vm path in store for existing domain 0 [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '1871', 'on_crash': 'restart', 'maxmem': '1871'} [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:750) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '1915904', 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2007-02-01 21:08:53 xend 3394] DEBUG (XendDomain:153) number of vcpus to use is 0 [2007-02-01 21:08:53 xend 3394] INFO (SrvServer:116) unix path=/var/lib/xend/xend-socket [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'win'], ['memory', '500'], ['maxmem', '500'], ['vcpus', '1'], ['uuid', 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c'], ['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/lib/xen/images/win'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:67:4a:87'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']]]]) [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'win'], ['memory', '500'], ['maxmem', '500'], ['vcpus', '1'], ['uuid', 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c'], ['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/lib/xen/images/win'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:67:4a:87'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']]]] [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', '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': 'win', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 500, 'device': [('vbd', ['vbd', ['dev', 'hda:disk'], ['uname', 'file:/var/lib/xen/images/win'], ['mode', 'w']]), ('vbd', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], ['mode', 'r']]), ('vif', ['vif', ['mac', '00:16:3e:67:4a:87'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': 500} [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 1 1.0 [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: boot, val: d [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: fda, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: fdb, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: soundhw, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: localtime, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: serial, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: std-vga, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: isa, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: vcpus, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: acpi, val: 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: usb, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: usbdevice, val: None [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:133) Balloon: 129052 KiB free; 0 to scrub; need 528560; retries: 20. [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:148) Balloon: setting dom0 target to 1480 MiB. [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:1021) Setting memory target of domain Domain-0 (0) to 1480 MiB. [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:127) Balloon: 528852 KiB free; need 528560; done. [2007-02-01 21:10:43 xend 3394] INFO (image:138) buildDomain os=hvm dom=1 vcpus=1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:364) dom = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:365) image = /usr/lib/xen/boot/hvmloader [2007-02-01 21:10:43 xend 3394] DEBUG (image:366) store_evtchn = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:367) memsize = 500 [2007-02-01 21:10:43 xend 3394] DEBUG (image:368) vcpus = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:369) pae = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:370) acpi = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:371) apic = 1 [2007-02-01 21:10:43 xend 3394] DEBUG (image:513) hvm shutdown watch registered [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) DevController: writing {'domain': 'win', 'frontend': '/local/domain/1/device/vbd/768', 'dev': 'hda', 'state': '1', 'params': '/var/lib/xen/images/win', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/768. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/5632'} to /local/domain/1/device/vbd/5632. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) DevController: writing {'domain': 'win', 'frontend': '/local/domain/1/device/vbd/5632', 'dev': 'hdc', 'state': '1', 'params': '/var/lib/xen/images/win.iso', 'mode': 'r', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/5632. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'win', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:67:4a:87', 'online': '1', 'frontend-id': '1', 'type': 'ioemu'} to /local/domain/0/backend/vif/1/0. [2007-02-01 21:10:44 xend 3394] INFO (image:497) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '1', '-m', '500', '-boot', 'd', '-acpi', '-domain-name', 'win', '-net', 'nic,vlan=1,macaddr=00:16:3e:67:4a:87,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vncunused', '-k', 'en-us', '-vnclisten', '127.0.0.1'] [2007-02-01 21:10:44 xend 3394] INFO (image:499) device model pid: 3829 [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '3', 'uuid': 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', 'on_reboot': 'destroy', 'start_time': '1170360644.22', 'on_poweroff': 'destroy', 'name': 'win', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '500', '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))', 'maxmem': '500'} [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:750) Storing domain details: {'console/port': '2', 'name': 'win', 'console/limit': '1048576', 'vm': '/vm/cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '512000', 'store/ring-ref': '200054', 'store/port': '1'} [2007-02-01 21:10:44 xend 3394] DEBUG (image:536) hvm_shutdown fired, shutdown reason=None [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:143) Waiting for devices vif. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:149) Waiting for 0. [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:143) Waiting for devices usb. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:143) Waiting for devices vbd. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:149) Waiting for 768. [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:149) Waiting for 5632. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for devices irq. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for devices pci. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for devices ioports. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for devices tap. [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for devices vtpm. [2007-02-01 21:10:46 xend 3394] INFO (XendDomain:370) Domain win (1) unpaused. *********** xend-debug.log *************************** Nothing to flush. Nothing to flush. ********** xen-hotplug.log **************** Nothing to flush. ********* audit.log ****************************** type=AVC msg=audit(1170360644.595:30): avc: denied { read write } for pid=3890 comm="ifconfig" name="win" dev=dm-0 ino=32571956 scontext=root:system_r:ifconfig_t:s0 tcontext=root:object_r:xend_var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1170360644.595:30): arch=40000003 syscall=11 success=yes exit=0 a0=9d46a18 a1=9d46ee8 a2=9d46e28 a3=9d46cf0 items=0 ppid=3877 pid=3890 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="ifconfig" exe="/sbin/ifconfig" subj=root:system_r:ifconfig_t:s0 key=(null) type=AVC_PATH msg=audit(1170360644.595:30): path="/var/lib/xen/images/win" type=ANOM_PROMISCUOUS msg=audit(1170360644.611:31): dev=tap0 prom=256 old_prom=0 auid=0 type=SYSCALL msg=audit(1170360644.611:31): arch=40000003 syscall=54 success=yes exit=0 a0=5 a1=89a2 a2=bfbee170 a3=1 items=0 ppid=3877 pid=3896 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="brctl" exe="/usr/sbin/brctl" subj=root:system_r:xend_t:s0 key=(null) type=ANOM_PROMISCUOUS msg=audit(1170360645.127:32): dev=vif1.0 prom=256 old_prom=0 auid=4294967295 type=SYSCALL msg=audit(1170360645.127:32): arch=40000003 syscall=54 success=yes exit=0 a0=3 a1=89a2 a2=bfe82ac0 a3=1 items=0 ppid=3865 pid=3952 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) comm="brctl" exe="/usr/sbin/brctl" subj=system_u:system_r:udev_t:s0-s0:c0.c1023 key=(null) *********** messages ********************* Feb 1 21:10:44 webserver1 kernel: tun: Universal TUN/TAP device driver, 1.6 Feb 1 21:10:44 webserver1 kernel: tun: (C) 1999-2004 Max Krasnyansky Feb 1 21:10:44 webserver1 kernel: device tap0 entered promiscuous mode Feb 1 21:10:44 webserver1 kernel: xenbr0: port 3(tap0) entering learning state Feb 1 21:10:44 webserver1 kernel: xenbr0: topology change detected, propagating Feb 1 21:10:44 webserver1 kernel: xenbr0: port 3(tap0) entering forwarding state Feb 1 21:10:45 webserver1 kernel: device vif1.0 entered promiscuous mode Feb 1 21:10:45 webserver1 kernel: ADDRCONF(NETDEV_UP): vif1.0: link is not ready Feb 1 21:10:45 webserver1 kernel: loop: loaded (max 8 devices) Feb 1 21:11:19 webserver1 ntpd[2283]: synchronized to LOCAL(0), stratum 10 Feb 1 21:11:19 webserver1 ntpd[2283]: kernel time sync enabled 0001 -------------- next part -------------- An HTML attachment was scrubbed... URL: From frommetoyou at comxnet.dk Thu Feb 1 21:00:36 2007 From: frommetoyou at comxnet.dk (Karsten Rasmussen) Date: Thu, 1 Feb 2007 22:00:36 +0100 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem References: <000c01c74643$75b41dc0$65ca4857@xcomp> Message-ID: <003a01c74644$068d6a40$65ca4857@xcomp> Sorry - forgot the qemu-dm.*.log Regard K Rasmussen ************** qemu-dm.*.log *********************** domid: 1 shared page at pfn:1f3ff, mfn: 30d75 buffered io page at pfn:1f3fd, mfn: 30d77 xs_read(): vncpasswd get error. /vm/cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c/vncpasswd. False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ligesh at lxlabs.com Thu Feb 1 21:26:38 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 02:56:38 +0530 Subject: [Fedora-xen] Centos Hangs before login prompt, and udev fails. Message-ID: <20070201212638.GA18920@lxlabs.com> Hi, I finally got xen to work properly by creating initrd by hand, so thanks to all the people who helped me out last time. Now I have another issue. The centos guest is hanging just before the login prompt comes up, and I also notice that udev is failing initially itself. I am using the images from jailtime.org. I created the mkinitrd by using the command below. Is there anything I should add? mkinitrd -f --with=xennet --builtin=aic7xxx --builtin=serverworks --preload=xenblk --omit-raid-modules --omit-lvm-modules --fstab=myfstab /boot/lxxen-initrd.img 2.6.19-1.2895.fc6xen" Thanks. From mike at mommabears.com Thu Feb 1 21:36:19 2007 From: mike at mommabears.com (MJang) Date: Thu, 01 Feb 2007 13:36:19 -0800 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem In-Reply-To: <000c01c74643$75b41dc0$65ca4857@xcomp> References: <000c01c74643$75b41dc0$65ca4857@xcomp> Message-ID: <1170365779.5821.27.camel@localhost> On Thu, 2007-02-01 at 21:56 +0100, Karsten Rasmussen wrote: > Hi > > I am trying to install Windows XP Pro on Fedora Core 6 with Xen. Iam > using the graphically interface to create a new session. The windows > install DVD is a OEM Rescue DVD. > The installation starts fine. > The installation passes the point where it is posible to press F6 to > install driver > The installation writes Please Wait" and the CPU load drops to 0 and > does not continue. > > Any Ideas? Just an idea - this seems like the thing that the workaround in Red Hat's Xen install doc is supposed to address https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf I think one related bug - from RHEL 5 beta 2 - is 223444. Thanks, Mike From ligesh at lxlabs.com Thu Feb 1 22:12:44 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 03:42:44 +0530 Subject: [Fedora-xen] Re: Centos Hangs before login prompt, and udev fails. In-Reply-To: <20070201212638.GA18920@lxlabs.com> References: <20070201212638.GA18920@lxlabs.com> Message-ID: <20070201221244.GA20831@lxlabs.com> Update on this: I was able to login to the domU using sshd, and found that it was the nash-hotplugd that's using 99% of the cpu, and I think this is what's interfering with the udevd and also making the mingetty not appear on the console. So how do I turn off nash-hotplugd in the initrd? thanks. From chris at tylers.info Thu Feb 1 22:23:53 2007 From: chris at tylers.info (Chris Tyler) Date: Thu, 01 Feb 2007 17:23:53 -0500 Subject: [Fedora-xen] FC6 Xen Guest Installation on Core 2 Duo Message-ID: <1170368633.31821.44.camel@concord2.proximity.on.ca> Greetings! I'm teaching in the Linux Administration program at Seneca College, Toronto -- this is a graduate certificate program in Linux system administration (http://isa.senecac.on.ca). This semester I'm adding a special emphasis on virtualization using Xen (and possibly KVM) on top of FC6. Seneca has generously provided a fantastic cluster for us to experiment on; each node is a Core 2 Duo with 4 GB of RAM, the nodes are connected with gig-E, and a fibre channel SAN will be added in a few weeks. Initially, we only have ssh character-mode access to the cluster; ssh tunneling is being set up. My hope is that the student's work on this cluster will result in several meaningful contributions back to the Xen community (and Fedora Xen community in particular) in areas such as rapid provisioning tools, detailed configuration benchmarks, and migration-control tools. Unfortunately, we're having a rough time getting FC6 guests installed via virt-install/xenguest-install. When attempting to install the x86_64 version, I get this: ======================= Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (22, 'Invalid argument')") Failed to create domain ct001 ======================= And when I try i386 I get: ======================= ...Installation proceeds, minstage2 starts, Welcome message appears, and then... Searching for Fedora Core installations... ------------[ cut here ]------------ kernel BUG at arch/i386/mm/hypervisor.c:197! invalid opcode: 0000 [#1] SMP last sysfs file: /block/ram0/dev ======================= Any recommendations/pointers/suggestions appreciated! -- Chris Tyler School of Computer Studies, Seneca at York From ligesh at lxlabs.com Thu Feb 1 23:28:39 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 04:58:39 +0530 Subject: [Fedora-xen] Re: Centos Hangs before login prompt, and udev fails. In-Reply-To: <20070201221244.GA20831@lxlabs.com> References: <20070201212638.GA18920@lxlabs.com> <20070201221244.GA20831@lxlabs.com> Message-ID: <20070201232839.GA23370@lxlabs.com> Hello: It seems ------------------ - scrub another possible error message from dmraid output * Mon Feb 13 2006 Bill Nottingham 8.28-1 - kill nash-hotplug before starting udev () ------------------ It appears you need to kill nash-hotplug before you start udev, but I think the kill is failing and the something is screwing up nash-hotplug to consume a lot of cpu. So how do I kill nash-hotplug before starting udev? Thanks. From ligesh at lxlabs.com Thu Feb 1 23:52:12 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 05:22:12 +0530 Subject: [Fedora-xen] Re: Centos Hangs before login prompt, and udev fails. In-Reply-To: <20070201232839.GA23370@lxlabs.com> References: <20070201212638.GA18920@lxlabs.com> <20070201221244.GA20831@lxlabs.com> <20070201232839.GA23370@lxlabs.com> Message-ID: <20070201235212.GA23922@lxlabs.com> Allright, I think I got the issue. I am trying to boot a centos 4.1 on a fc6. Now fc6 initrd, even the custom created one, has nash-hotplugd, which has to be killed before starting udev, but this logic is not there in the initscripts of centos-4.1. So I have to basically hand craft an initrd that will kill off this nash-hotplug in the initrd itself, if it has to work with all the older distros. This is too much work, to tell the truth. I will test with fc6 guest on fc6 and report back. From ligesh at lxlabs.com Thu Feb 1 23:53:50 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 05:23:50 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070201123738.GB1430@redhat.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> <4781.192.168.2.92.1170303323.squirrel@www.bradleyland.com> <20070201123738.GB1430@redhat.com> Message-ID: <20070201235350.GB23922@lxlabs.com> On Thu, Feb 01, 2007 at 12:37:38PM +0000, Daniel P. Berrange wrote: > On Wed, Jan 31, 2007 at 08:15:23PM -0800, master at bradleyland.com wrote: > > The problem comes about when you update the kernel with yum. In my > > experience (like all good lessons, learned the hard way), the initrd is > > created on the fly and does not include xenblk. You cannot just take the > > initrd that ends up in the /boot directory and use it for your guest. > > Doesn't work. > > > > Now I know this, it's an easy matter to create a fresh initrd and include > > the xenblk module. Maybe there's a smarter way to do this. If so, it > > escapes me. > > The smarter way is to keep the kernel & initrd / RPM installed inside the > guest OS itself. This is not acceptable, since the guests are basically tar files that are unaware of the existance of xen. They are pre-created ostemplates from jailtime.org and it is the duty of the host to provide transparent virtualization. Also just think of the scale. It is always better to get ONE host working properly rather than to makes sure that 200 guest ostemplates are all kept in sync. thanks. From paul at xelerance.com Fri Feb 2 01:10:24 2007 From: paul at xelerance.com (Paul Wouters) Date: Fri, 2 Feb 2007 02:10:24 +0100 (CET) Subject: [Fedora-xen] Re: Centos Hangs before login prompt, and udev fails. In-Reply-To: <20070201235212.GA23922@lxlabs.com> References: <20070201212638.GA18920@lxlabs.com> <20070201221244.GA20831@lxlabs.com> <20070201232839.GA23370@lxlabs.com> <20070201235212.GA23922@lxlabs.com> Message-ID: On Fri, 2 Feb 2007, K T Ligesh wrote: > Allright, I think I got the issue. I am trying to boot a centos 4.1 on a fc6. Now fc6 initrd, even the custom created one, has nash-hotplugd, which has to be killed before starting udev, but this logic is not there in the initscripts of centos-4.1. So I have to basically hand craft an initrd that will kill off this nash-hotplug in the initrd itself, if it has to work with all the older distros. I don't think that is the reason for not getting a login prompt. The nash-hotplug can be annoying. I've had to kill it in the past too. I infact disable hotplay/udev on those older images, and just use a MAKEDEV and create the devices I need, To fix your login problem do this: mount -o loop centosfs dir cd dir (or login via ssh to the running centos box) cd dev ; /dev/MAKEDEV null zero random urandom console tty pty hda xvd loop (this uses the MAKEDEV script in the /dev/ of dom0 to create nodes in the /dev of the guest image) mknod dev/xvc0 c 25 187 (cause there is some confusion about which major/minor to use) edit inittab and change the mingetty for tty2 to xvc0, eg: 2:2345:respawn:/sbin/mingetty xvc0 (change tty2 not tty1 because in a normal "working" situation, tty1 will be mapped to the xen virtual console already, you do not want to break that) And do: echo "xvc0" >> etc/securetty (to allow root logins) I also made a xenU ramdisk for my images, on dom0: mkinitrd /boot/initrd-2.6.18-1.2849.fc6xenU.img --with=xennet --preload=xenblk (again note to redhat: PLEASE include xennet/xenblk in the xen ramdisk, even if the dom0 strictly does not need it. It will allow everyone to re-use the same initrd when not using pygrub with disk images, but kernel=/ramdisk= statements with a rootfs) Paul From ligesh at lxlabs.com Fri Feb 2 06:53:34 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 2 Feb 2007 12:23:34 +0530 Subject: [Fedora-xen] Re: Centos Hangs before login prompt, and udev fails. In-Reply-To: References: <20070201212638.GA18920@lxlabs.com> <20070201221244.GA20831@lxlabs.com> <20070201232839.GA23370@lxlabs.com> <20070201235212.GA23922@lxlabs.com> Message-ID: <20070202065334.GA29097@lxlabs.com> On Fri, Feb 02, 2007 at 02:10:24AM +0100, Paul Wouters wrote: > On Fri, 2 Feb 2007, K T Ligesh wrote: > > > Allright, I think I got the issue. I am trying to boot a centos 4.1 on a fc6. Now fc6 initrd, even the custom created one, has nash-hotplugd, which has to be killed before starting udev, but this logic is not there in the initscripts of centos-4.1. So I have to basically hand craft an initrd that will kill off this nash-hotplug in the initrd itself, if it has to work with all the older distros. > (or login via ssh to the running centos box) > > cd dev ; /dev/MAKEDEV null zero random urandom console tty pty hda xvd loop > (this uses the MAKEDEV script in the /dev/ of dom0 to create nodes in the > /dev of the guest image) > > mknod dev/xvc0 c 25 187 > (cause there is some confusion about which major/minor to use) > > edit inittab and change the mingetty for tty2 to xvc0, eg: > > 2:2345:respawn:/sbin/mingetty xvc0 > > (change tty2 not tty1 because in a normal "working" situation, tty1 will be mapped > to the xen virtual console already, you do not want to break that) > > And do: > > echo "xvc0" >> etc/securetty > (to allow root logins) > > I also made a xenU ramdisk for my images, on dom0: > > mkinitrd /boot/initrd-2.6.18-1.2849.fc6xenU.img --with=xennet --preload=xenblk > > (again note to redhat: PLEASE include xennet/xenblk in the xen ramdisk, even if > the dom0 strictly does not need it. It will allow everyone to re-use the same > initrd when not using pygrub with disk images, but kernel=/ramdisk= statements > with a rootfs) > Yeah, I did that. So now xen uses xvc0 and not the ttyS0? That's actually good news, since that means that the tty is now freed up? Thanks. From xenguy at gmail.com Fri Feb 2 06:59:51 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Fri, 02 Feb 2007 12:29:51 +0530 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem In-Reply-To: <000c01c74643$75b41dc0$65ca4857@xcomp> References: <000c01c74643$75b41dc0$65ca4857@xcomp> Message-ID: <45C2E167.9020603@gmail.com> Karsten Rasmussen wrote: > Hi > > I am trying to install Windows XP Pro on Fedora Core 6 with Xen. Iam > using the graphically interface to create a new session. The windows > install DVD is a OEM Rescue DVD. > The installation starts fine. > The installation passes the point where it is posible to press F6 to > install driver > The installation writes Please Wait" and the CPU load drops to 0 and > does not continue. When the system says to press F6, Press F5 and select "standard PC" and continue. Regards, Sadique > > Any Ideas? > > Regards > K Rasmussen > > System: > I am running FC6 with SElinux in permissive mode: > I have trie to upgrade to kernel-xen 2.6.19-1.2895 with no luck - I > only got problems shutting down the system with "hda lost interrupt" > mesages so I returned the the default installed version. > > Varius Logs appended: > xend.log > xend-debug.log > xen-hotplug.log > qemu-dm.3829.log > message > audit.log > > ************ xend.log ***************** > [2007-02-01 21:08:52 xend 3394] INFO (SrvDaemon:283) Xend Daemon started > [2007-02-01 21:08:52 xend 3394] INFO (SrvDaemon:287) Xend changeset: > unavailable . > [2007-02-01 21:08:52 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:212) XendDomainInfo.recreate({'paused': 0, 'cpu_time': > 186093836980L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, > 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, > 'mem_kb': 1915320, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, > 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) > [2007-02-01 21:08:52 xend.XendDomainInfo 3394] INFO > (XendDomainInfo:224) Recreating domain 0, UUID > 00000000-0000-0000-0000-000000000000. > [2007-02-01 21:08:52 xend.XendDomainInfo 3394] WARNING > (XendDomainInfo:246) No vm path in store for existing domain 0 > [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:715) Storing VM details: {'shadow_memory': '0', > 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': > 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', > 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': > '1871', 'on_crash': 'restart', 'maxmem': '1871'} > [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:750) Storing domain details: {'cpu/0/availability': > 'online', 'memory/target': '1915904', 'cpu/1/availability': 'online', > 'name': 'Domain-0', 'console/limit': '1048576', 'vm': > '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} > [2007-02-01 21:08:53 xend 3394] DEBUG (XendDomain:153) number of vcpus > to use is 0 > [2007-02-01 21:08:53 xend 3394] INFO (SrvServer:116) unix > path=/var/lib/xend/xend-socket > [2007-02-01 21:08:53 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'win'], > ['memory', '500'], ['maxmem', '500'], ['vcpus', '1'], ['uuid', > 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c'], ['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/lib/xen/images/win'], ['mode', 'w']]], ['device', ['vbd', > ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], > ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:67:4a:87'], > ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], > ['type', 'ioemu']]]]) > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'win'], > ['memory', '500'], ['maxmem', '500'], ['vcpus', '1'], ['uuid', > 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c'], ['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/lib/xen/images/win'], ['mode', 'w']]], ['device', ['vbd', > ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], > ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:67:4a:87'], > ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], > ['type', 'ioemu']]]] > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, > 'start_time': None, 'uuid': 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', > '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': 'win', 'backend': [], 'vcpus': 1, 'cpu_weight': None, > 'features': None, 'vcpu_avail': None, 'memory': 500, 'device': > [('vbd', ['vbd', ['dev', 'hda:disk'], ['uname', > 'file:/var/lib/xen/images/win'], ['mode', 'w']]), ('vbd', ['vbd', > ['dev', 'hdc:cdrom'], ['uname', 'file:/var/lib/xen/images/win.iso'], > ['mode', 'r']]), ('vif', ['vif', ['mac', '00:16:3e:67:4a:87'], > ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], > ['type', 'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': 500} > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:1264) XendDomainInfo.construct: None > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:1296) XendDomainInfo.initDomain: 1 1.0 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: boot, val: d > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: fda, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: fdb, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: soundhw, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: localtime, > val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: serial, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: std-vga, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: isa, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: vcpus, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: acpi, val: 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: usb, val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (image:410) args: usbdevice, > val: None > [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:133) Balloon: 129052 > KiB free; 0 to scrub; need 528560; retries: 20. > [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:148) Balloon: setting > dom0 target to 1480 MiB. > [2007-02-01 21:10:43 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:1021) Setting memory target of domain Domain-0 (0) to > 1480 MiB. > [2007-02-01 21:10:43 xend 3394] DEBUG (balloon:127) Balloon: 528852 > KiB free; need 528560; done. > [2007-02-01 21:10:43 xend 3394] INFO (image:138) buildDomain os=hvm > dom=1 vcpus=1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:364) dom = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:365) image = > /usr/lib/xen/boot/hvmloader > [2007-02-01 21:10:43 xend 3394] DEBUG (image:366) store_evtchn = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:367) memsize = 500 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:368) vcpus = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:369) pae = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:370) acpi = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:371) apic = 1 > [2007-02-01 21:10:43 xend 3394] DEBUG (image:513) hvm shutdown watch > registered > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) > DevController: writing {'backend-id': '0', 'virtual-device': '768', > 'device-type': 'disk', 'state': '1', 'backend': > '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) > DevController: writing {'domain': 'win', 'frontend': > '/local/domain/1/device/vbd/768', 'dev': 'hda', 'state': '1', > 'params': '/var/lib/xen/images/win', 'mode': 'w', 'online': '1', > 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/768. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) > DevController: writing {'backend-id': '0', 'virtual-device': '5632', > 'device-type': 'cdrom', 'state': '1', 'backend': > '/local/domain/0/backend/vbd/1/5632'} to /local/domain/1/device/vbd/5632. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) > DevController: writing {'domain': 'win', 'frontend': > '/local/domain/1/device/vbd/5632', 'dev': 'hdc', 'state': '1', > 'params': '/var/lib/xen/images/win.iso', 'mode': 'r', 'online': '1', > 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/5632. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:110) > DevController: writing {'state': '1', 'backend-id': '0', 'backend': > '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:112) > DevController: writing {'bridge': 'xenbr0', 'domain': 'win', 'handle': > '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', > 'frontend': '/local/domain/1/device/vif/0', 'mac': > '00:16:3e:67:4a:87', 'online': '1', 'frontend-id': '1', 'type': > 'ioemu'} to /local/domain/0/backend/vif/1/0. > [2007-02-01 21:10:44 xend 3394] INFO (image:497) spawning device > models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', > '1', '-m', '500', '-boot', 'd', '-acpi', '-domain-name', 'win', > '-net', 'nic,vlan=1,macaddr=00:16:3e:67:4a:87,model=rtl8139', '-net', > 'tap,vlan=1,bridge=xenbr0', '-vncunused', '-k', 'en-us', '-vnclisten', > '127.0.0.1'] > [2007-02-01 21:10:44 xend 3394] INFO (image:499) device model pid: 3829 > [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:715) Storing VM details: {'shadow_memory': '3', > 'uuid': 'cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', 'on_reboot': > 'destroy', 'start_time': '1170360644.22', 'on_poweroff': 'destroy', > 'name': 'win', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': > '1', 'memory': '500', '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))', 'maxmem': > '500'} > [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:750) Storing domain details: {'console/port': '2', > 'name': 'win', 'console/limit': '1048576', 'vm': > '/vm/cc98adea-d1b5-2d63-22ae-be2b6b4d0c9c', 'domid': '1', > 'cpu/0/availability': 'online', 'memory/target': '512000', > 'store/ring-ref': '200054', 'store/port': '1'} > [2007-02-01 21:10:44 xend 3394] DEBUG (image:536) hvm_shutdown fired, > shutdown reason=None > [2007-02-01 21:10:44 xend.XendDomainInfo 3394] DEBUG > (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:143) Waiting for > devices vif. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:149) Waiting for 0. > [2007-02-01 21:10:44 xend 3394] DEBUG (DevController:471) > hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:471) > hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:485) > hotplugStatusCallback 1. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:143) Waiting for > devices usb. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:143) Waiting for > devices vbd. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:149) Waiting for 768. > [2007-02-01 21:10:45 xend 3394] DEBUG (DevController:471) > hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:471) > hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:485) > hotplugStatusCallback 1. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:149) Waiting for > 5632. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:471) > hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:485) > hotplugStatusCallback 1. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for > devices irq. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for > devices pci. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for > devices ioports. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for > devices tap. > [2007-02-01 21:10:46 xend 3394] DEBUG (DevController:143) Waiting for > devices vtpm. > [2007-02-01 21:10:46 xend 3394] INFO (XendDomain:370) Domain win (1) > unpaused. > > > > > *********** xend-debug.log *************************** > Nothing to flush. > Nothing to flush. > > > > ********** xen-hotplug.log **************** > Nothing to flush. > > > ********* audit.log ****************************** > type=AVC msg=audit(1170360644.595:30): avc: denied { read write } > for pid=3890 comm="ifconfig" name="win" dev=dm-0 ino=32571956 > scontext=root:system_r:ifconfig_t:s0 > tcontext=root:object_r:xend_var_lib_t:s0 tclass=file > type=SYSCALL msg=audit(1170360644.595:30): arch=40000003 syscall=11 > success=yes exit=0 a0=9d46a18 a1=9d46ee8 a2=9d46e28 a3=9d46cf0 items=0 > ppid=3877 pid=3890 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 > sgid=0 fsgid=0 tty=(none) comm="ifconfig" exe="/sbin/ifconfig" > subj=root:system_r:ifconfig_t:s0 key=(null) > type=AVC_PATH msg=audit(1170360644.595:30): > path="/var/lib/xen/images/win" > type=ANOM_PROMISCUOUS msg=audit(1170360644.611:31): dev=tap0 prom=256 > old_prom=0 auid=0 > type=SYSCALL msg=audit(1170360644.611:31): arch=40000003 syscall=54 > success=yes exit=0 a0=5 a1=89a2 a2=bfbee170 a3=1 items=0 ppid=3877 > pid=3896 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 > fsgid=0 tty=(none) comm="brctl" exe="/usr/sbin/brctl" > subj=root:system_r:xend_t:s0 key=(null) > type=ANOM_PROMISCUOUS msg=audit(1170360645.127:32): dev=vif1.0 > prom=256 old_prom=0 auid=4294967295 > type=SYSCALL msg=audit(1170360645.127:32): arch=40000003 syscall=54 > success=yes exit=0 a0=3 a1=89a2 a2=bfe82ac0 a3=1 items=0 ppid=3865 > pid=3952 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 > sgid=0 fsgid=0 tty=(none) comm="brctl" exe="/usr/sbin/brctl" > subj=system_u:system_r:udev_t:s0-s0:c0.c1023 key=(null) > > > > *********** messages ********************* > Feb 1 21:10:44 webserver1 kernel: tun: Universal TUN/TAP device > driver, 1.6 > Feb 1 21:10:44 webserver1 kernel: tun: (C) 1999-2004 Max Krasnyansky > > > Feb 1 21:10:44 webserver1 kernel: device tap0 entered promiscuous mode > Feb 1 21:10:44 webserver1 kernel: xenbr0: port 3(tap0) entering > learning state > Feb 1 21:10:44 webserver1 kernel: xenbr0: topology change detected, > propagating > Feb 1 21:10:44 webserver1 kernel: xenbr0: port 3(tap0) entering > forwarding state > Feb 1 21:10:45 webserver1 kernel: device vif1.0 entered promiscuous mode > Feb 1 21:10:45 webserver1 kernel: ADDRCONF(NETDEV_UP): vif1.0: link > is not ready > Feb 1 21:10:45 webserver1 kernel: loop: loaded (max 8 devices) > Feb 1 21:11:19 webserver1 ntpd[2283]: synchronized to LOCAL(0), > stratum 10 > Feb 1 21:11:19 webserver1 ntpd[2283]: kernel time sync enabled 0001 > > > > > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From xenguy at gmail.com Fri Feb 2 07:36:20 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Fri, 02 Feb 2007 13:06:20 +0530 Subject: [Fedora-xen] FC6 Xen Guest Installation on Core 2 Duo In-Reply-To: <1170368633.31821.44.camel@concord2.proximity.on.ca> References: <1170368633.31821.44.camel@concord2.proximity.on.ca> Message-ID: <45C2E9F4.4070004@gmail.com> Chris Tyler wrote: > Greetings! > > I'm teaching in the Linux Administration program at Seneca College, > Toronto -- this is a graduate certificate program in Linux system > administration (http://isa.senecac.on.ca). This semester I'm adding a > special emphasis on virtualization using Xen (and possibly KVM) on top > of FC6. > > Seneca has generously provided a fantastic cluster for us to experiment > on; each node is a Core 2 Duo with 4 GB of RAM, the nodes are connected > with gig-E, and a fibre channel SAN will be added in a few weeks. > Initially, we only have ssh character-mode access to the cluster; ssh > tunneling is being set up. > > My hope is that the student's work on this cluster will result in > several meaningful contributions back to the Xen community (and Fedora > Xen community in particular) in areas such as rapid provisioning tools, > detailed configuration benchmarks, and migration-control tools. > > Unfortunately, we're having a rough time getting FC6 guests installed > via virt-install/xenguest-install. When attempting to install the x86_64 > version, I get this: > > ======================= > Starting install... > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > creating domain: (22, 'Invalid argument')") > Failed to create domain ct001 > ======================= > You can only install 32bit paravirtualised guest operating systems on top of a 32 bit hypervisor. You can install only 64bit prara virtualised guest operating systems on top of a 64 bit hypervisor. > > And when I try i386 I get: > > ======================= > ...Installation proceeds, minstage2 starts, Welcome message appears, and > then... > > Searching for Fedora Core installations... > ------------[ cut here ]------------ > kernel BUG at arch/i386/mm/hypervisor.c:197! > invalid opcode: 0000 [#1] > SMP > last sysfs file: /block/ram0/dev > ======================= > > > Any recommendations/pointers/suggestions appreciated! > > -- > Chris Tyler > School of Computer Studies, Seneca at York > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From maillist at hittafel.net Fri Feb 2 09:52:05 2007 From: maillist at hittafel.net (Jonas Bystr?m) Date: Fri, 02 Feb 2007 10:52:05 +0100 Subject: [Fedora-xen] Xen installation Fedora6 Message-ID: Hi. I have make a installation on my Fedora 6 box. (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6) Now is the problem that i cant connect to my box through Windows GUI (XenSource XServer). Its just saying "Not a XenServer Host". How can i solve that problem? Thanks. From mk at crc.dk Fri Feb 2 12:43:53 2007 From: mk at crc.dk (Mogens Kjaer) Date: Fri, 02 Feb 2007 13:43:53 +0100 Subject: [Fedora-xen] Some newbie xen questions Message-ID: <45C33209.5010702@crc.dk> I'm learning xen on a machine with fc6.i386. The CPU can do pae and vmx. I have some problems: 1. virt-manager doesn't start when I'm logged in as root: # virt-manager Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 56, in ? import gtk ImportError: No module named gtk It works if I start /usr/bin/virt-manager instead of /usr/sbin/virt-manager. 2. xm doesn't start: # xm Traceback (most recent call last): File "/usr/sbin/xm", line 8, in ? from xen.xm import main ImportError: No module named xen.xm 3. If I create a guest and start an installation (I've tried FC6 and W2K), the guest doesn't come up again after the "reboot". For W2K I can fix this problem by creating a new machine on the same partition and boot from the w2k CD. When it says "press any key to boot from CD", I don't. Installing&updating W2K requires some reboots, this leaves quite some ghost virtual machines :-) 3. The two mouse cursors in the virtual console don't follow each other, this is quite annoying. # rpm -qa|fgrep xen kernel-xen-2.6.18-1.2869.fc6 xen-devel-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 xen-3.0.3-3.fc6 # rpm -qa|fgrep virt python-virtinst-0.98.0-1.fc6 virt-manager-0.2.6-3.fc6 libvirt-0.1.10-1.fc6 libvirt-python-0.1.10-1.fc6 Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk From frommetoyou at comxnet.dk Fri Feb 2 12:58:43 2007 From: frommetoyou at comxnet.dk (Karsten Rasmussen) Date: Fri, 2 Feb 2007 13:58:43 +0100 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem References: <000c01c74643$75b41dc0$65ca4857@xcomp> <1170365779.5821.27.camel@localhost> Message-ID: <000b01c746c9$df3dd250$65ca4857@xcomp> > this seems like the thing that the workaround in Red > Hat's Xen install doc is supposed to address > https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf > > I think one related bug - from RHEL 5 beta 2 - is 223444. PDF document states to format C drive with FAT file system ... But how? There is no prompt for this. Some parts of the windows installation passes the screen in a few seconds - any messages to press XXX is displayed to fast to be read. Regards K Rasmussen From xenguy at gmail.com Fri Feb 2 13:06:41 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Fri, 02 Feb 2007 18:36:41 +0530 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem In-Reply-To: <000b01c746c9$df3dd250$65ca4857@xcomp> References: <000c01c74643$75b41dc0$65ca4857@xcomp> <1170365779.5821.27.camel@localhost> <000b01c746c9$df3dd250$65ca4857@xcomp> Message-ID: <45C33761.9070200@gmail.com> Karsten Rasmussen wrote: >> this seems like the thing that the workaround in Red >> Hat's Xen install doc is supposed to address >> https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf >> >> >> I think one related bug - from RHEL 5 beta 2 - is 223444. > > PDF document states to format C drive with FAT file system ... But > how? There is no prompt for this. Some parts of the windows > installation passes the screen in a few seconds - any messages to > press XXX is displayed to fast to be read. As I said earlier, When the system says to press F6, Press F5, select "standard PC" and continue. This would give you the prompt to format the drive using fat. > > Regards > K Rasmussen > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From frommetoyou at comxnet.dk Fri Feb 2 13:07:23 2007 From: frommetoyou at comxnet.dk (Karsten Rasmussen) Date: Fri, 2 Feb 2007 14:07:23 +0100 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem References: <000c01c74643$75b41dc0$65ca4857@xcomp> <45C2E167.9020603@gmail.com> Message-ID: <000f01c746cb$1568bec0$65ca4857@xcomp> > When the system says to press F6, Press F5 and select "standard PC" and > continue. This helped for a while. BTW: There is no indication on the screen that it is posible to press F5. I had to press F5 directly after F6 not waiting until screen image changes. If I waited to press F5 until the screen image had change F5 had no effect . The installation continued and the process also continued after the first reboot. The installaion was copying files but the second reboot did not succeded. The second reboot started displayed disk size and booting from disk followed by a black screen. The qeme log file only writes redirect to /tty/25 Regards K Rasmussen From xenguy at gmail.com Fri Feb 2 13:09:46 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Fri, 02 Feb 2007 18:39:46 +0530 Subject: [Fedora-xen] Some newbie xen questions In-Reply-To: <45C33209.5010702@crc.dk> References: <45C33209.5010702@crc.dk> Message-ID: <45C3381A.1070600@gmail.com> Mogens Kjaer wrote: > I'm learning xen on a machine with fc6.i386. > > The CPU can do pae and vmx. > > I have some problems: > > 1. virt-manager doesn't start when I'm logged in as > root: > > # virt-manager > Traceback (most recent call last): > File "/usr/share/virt-manager/virt-manager.py", line 56, in ? > import gtk > ImportError: No module named gtk > > It works if I start /usr/bin/virt-manager instead of > /usr/sbin/virt-manager. > > 2. xm doesn't start: > > # xm > Traceback (most recent call last): > File "/usr/sbin/xm", line 8, in ? > from xen.xm import main > ImportError: No module named xen.xm > > 3. If I create a guest and start an installation > (I've tried FC6 and W2K), the guest doesn't come > up again after the "reboot". > > For W2K I can fix this problem by creating a new > machine on the same partition and boot from the w2k > CD. When it says "press any key to boot from CD", > I don't. Installing&updating W2K requires some > reboots, this leaves quite some ghost virtual > machines :-) As of now virt-manager doesn't have the ability to manage inactive domains. You need to boot the guest from the backend using "xm create " > > 3. The two mouse cursors in the virtual console > don't follow each other, this is quite annoying. > > # rpm -qa|fgrep xen > kernel-xen-2.6.18-1.2869.fc6 > xen-devel-3.0.3-3.fc6 > xen-libs-3.0.3-3.fc6 > xen-3.0.3-3.fc6 > > # rpm -qa|fgrep virt > python-virtinst-0.98.0-1.fc6 > virt-manager-0.2.6-3.fc6 > libvirt-0.1.10-1.fc6 > libvirt-python-0.1.10-1.fc6 > > Mogens > From mk at crc.dk Fri Feb 2 13:27:11 2007 From: mk at crc.dk (Mogens Kjaer) Date: Fri, 02 Feb 2007 14:27:11 +0100 Subject: [Fedora-xen] Some newbie xen questions In-Reply-To: <45C3381A.1070600@gmail.com> References: <45C33209.5010702@crc.dk> <45C3381A.1070600@gmail.com> Message-ID: <45C33C2F.90006@crc.dk> Sadique Puthen wrote: > Mogens Kjaer wrote: ... >> 2. xm doesn't start: >> >> # xm >> Traceback (most recent call last): >> File "/usr/sbin/xm", line 8, in ? >> from xen.xm import main >> ImportError: No module named xen.xm ... > As of now virt-manager doesn't have the ability to manage inactive > domains. You need to boot the guest from the backend using "xm create > " Why can't I run xm? Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk From frommetoyou at comxnet.dk Fri Feb 2 13:39:52 2007 From: frommetoyou at comxnet.dk (Karsten Rasmussen) Date: Fri, 2 Feb 2007 14:39:52 +0100 Subject: [Fedora-xen] Xen, Fc6, Windows XP Pro SP2, Install Problem References: <000c01c74643$75b41dc0$65ca4857@xcomp> <1170365779.5821.27.camel@localhost> <000b01c746c9$df3dd250$65ca4857@xcomp> <45C33761.9070200@gmail.com> Message-ID: <000b01c746cf$9f135f50$65ca4857@xcomp> > As I said earlier, When the system says to press F6, Press F5, select > "standard PC" and continue. This would give you the prompt to format the > drive using fat. > Sorry for my bad reading. I should had read: ... When the system says to press F6, Press F5 INSTEAD of F6? I am able to select Standard PC and continue but there is no prompt for formating disk to FAT. Baybe my OEM XP Pro SP2 has removed this option? Thanks for the help Regards K Rasmussen From andreground at gmail.com Fri Feb 2 16:36:45 2007 From: andreground at gmail.com (AndreGround) Date: Fri, 2 Feb 2007 17:36:45 +0100 Subject: [Fedora-xen] Building a PAE-disabled kernel & HV Message-ID: Hi everybody, I'm looking to find a way in order to build a PAE-disabled kernel & HV. I'm starting from the Fedora's official SRPMS for both the kernel and xen. While I can find some flags related to PAE in the .spec file for the kernel, I can't find any flag inside the xen.spec file. @ the moment, also building a custom PAE disabled kernel, I always get a PAE mismatch error when booting (xen=no dom0=yes). Please let me have your considerations. Thanks in advance, Andrea From paul at xelerance.com Fri Feb 2 17:44:10 2007 From: paul at xelerance.com (Paul Wouters) Date: Fri, 2 Feb 2007 18:44:10 +0100 (CET) Subject: [Fedora-xen] Xen installation Fedora6 Message-ID: > I have make a installation on my Fedora 6 box. > (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6) > > Now is the problem that i cant connect to my box through Windows GUI > (XenSource XServer). > Its just saying "Not a XenServer Host". How can i solve that problem? Xensource XServer (actually "Xensource Server") only supports Windows guests. You will need Xensource Enterprise to run Windows and unix guests Paul From annefacq at crpp-bordeaux.cnrs.fr Sun Feb 4 08:29:44 2007 From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq) Date: Sun, 04 Feb 2007 09:29:44 +0100 Subject: [Fedora-xen] DomU boot on Fedora 6 fails with 'VFS: Cannot open root device' Message-ID: <45C59978.4050509@crpp-bordeaux.cnrs.fr> Hello I have got a problem booting a DomU on Linux Fedora Core 6 (kernel 2.6.19-1.2895.fc6xen) I did the following operations : 1) dd if=/dev/zero of=/home/xen/vm1 bs=1k seek=6144k count=1 2) mkfs.ext3 /home/xen/vm1 3) mount -o loop /home/xen/vm1 /mnt 4) cp -ax /{root,dev,var,etc,usr,bin,sbin,lib,boot} /mnt 5) mkdir -m 755 /mnt/{proc,sys,home,tmp,mnt} 6) DomU fstab : /dev/sdb1 / 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 7) cat > /etc/xen/vm1 kernel = "/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory = 512 name = 'vm1' vif = [ '' ] disk = [ 'file:/home/xen/vm1,sdb1,w' ] root = '/dev/sdb1 ro' extra = 'ro selinux=0 3' 8) When I launch : xm create -c vm1 I get the following error message : ---- VFS: Cannot open root device "sdb1" 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 tried several devices but I got the same message Any advice ? Thanks in advance. Anne Facq From billzingler at gmail.com Thu Feb 1 20:38:33 2007 From: billzingler at gmail.com (Bill Zingler) Date: Thu, 1 Feb 2007 15:38:33 -0500 Subject: [Fedora-xen] Unable to get working guest on FC6 Message-ID: The following command yeilds the error below. Anyone have any ideas what could be the problem. Am I encountering a problem due to using the x86_64 version of FC6? Thanks, Bill virt-install --name=fc6g3 --ram=512 --vcpus=1 --file=/home/admin/fc6g3.img --file-size=5 --paravirt --location= http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os --vnc Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err 'destroyDevice() takes exactly 3 arguments (2 given)') Failed to get devices for domain fc6g3 Traceback (most recent call last): File "/usr/sbin/virt-install", line 447, in ? main() File "/usr/sbin/virt-install", line 411, in main dom = guest.start_install(conscb) File "/usr/lib/python2.4/site-packages/virtinst/ParaVirtGuest.py", line 202, in start_install return XenGuest.XenGuest.start_install(self, consolecb) File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line 366, in start_install self.domain = self.conn.createLinux(cxml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 329, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: ( xend.err 'destroyDevice() takes exactly 3 arguments (2 given)') [root at fc6-test admin]# -- Bill Zingler Zingler & Associates, Inc. (443) 822-4857 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Sun Feb 4 16:01:53 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 4 Feb 2007 16:01:53 +0000 Subject: [Fedora-xen] Unable to get working guest on FC6 In-Reply-To: References: Message-ID: <20070204160153.GA19290@redhat.com> On Thu, Feb 01, 2007 at 03:38:33PM -0500, Bill Zingler wrote: > The following command yeilds the error below. Anyone have any ideas what > could be the problem. Am I encountering a problem due to using the x86_64 > version of FC6? > > Thanks, > > Bill > > virt-install --name=fc6g3 --ram=512 --vcpus=1 --file=/home/admin/fc6g3.img > --file-size=5 --paravirt --location= > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os --vnc If you have SELinux enabled, then this will fail because the disk image is under in a permitted directory. SELinux policy requires disk images to be in either /xen (for legacy compat), or /var/lib/xen/images (current preferred). If you really really want to keep disk images elsewhere, then you need to add the extra directory to the policy & make sure its labelled, eg To add to policy: semanage fcontext --add -t xen_image_t '/home/admin/xen(/.*)?' And then to label the dir: restorecon /home/admin/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 mk at crc.dk Mon Feb 5 07:37:39 2007 From: mk at crc.dk (Mogens Kjaer) Date: Mon, 05 Feb 2007 08:37:39 +0100 Subject: [Fedora-xen] Some newbie xen questions In-Reply-To: <45C33C2F.90006@crc.dk> References: <45C33209.5010702@crc.dk> <45C3381A.1070600@gmail.com> <45C33C2F.90006@crc.dk> Message-ID: <45C6DEC3.8010508@crc.dk> Mogens Kjaer wrote: ... > Why can't I run xm? It was a stupid mistake by me; I had a python in /usr/local/bin as well. Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk From Eric.Doutreleau at int-evry.fr Mon Feb 5 08:21:49 2007 From: Eric.Doutreleau at int-evry.fr (Eric Doutreleau) Date: Mon, 05 Feb 2007 09:21:49 +0100 Subject: [Fedora-xen] problem with xenguest-install@redhat.com Message-ID: <45C6E91D.3060702@int-evry.fr> hi i m trying to build a new guest on my fc5 enabled machine the kernel is 2.6.18-1.2257.fc5xen0 xen version is xen-3.0.3-3.fc5 when i run /usr/sbin/xenguest-install.py I got What is the name of your virtual machine? ntp1 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /var/xen/ntp1.img How large would you like the disk to be (in gigabytes)? 10 What is the install location? http://yum.int-evry.fr/core/fc5 Traceback (most recent call last): File "/usr/sbin/xenguest-install.py", line 460, in ? main() File "/usr/sbin/xenguest-install.py", line 451, in main start_paravirt_install(name, ram, disk, mac, uuid, src, options.extra) File "/usr/sbin/xenguest-install.py", line 324, in start_paravirt_install conn = libvirt.open(None) File "/usr/lib/python2.4/site-packages/libvirt.py", line 39, in open if ret is None:raise libvirtError('virConnectOpen() failed') libvirt.libvirtError: virConnectOpen() failed i have read on the list some had the same problems month ago but i didn't see any answer on the list. Thanks in advance for any help From billzingler at gmail.com Mon Feb 5 13:25:11 2007 From: billzingler at gmail.com (Bill Zingler) Date: Mon, 5 Feb 2007 08:25:11 -0500 Subject: [Fedora-xen] Unable to get working guest on FC6 In-Reply-To: <20070204160153.GA19290@redhat.com> References: <20070204160153.GA19290@redhat.com> Message-ID: Dan, Thanks for the response. I changed my command to: virt-install --name=fc6g3 --ram=512 --vcpus=1 --file=/var/lib/xen/images/fc6g3.img --file-size=5 --paravirt --location= http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os --vnc But, I get the same error. I then disabled SELinux and still got the same error. Do you know of any working tutorials on this? I have looked at: https://virt.108.redhat.com/articles/2007/01/15/xen-chapter-from-fedora-core-6-unleashed.html http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 They both are short on details. Thanks, Bill On 2/4/07, Daniel P. Berrange wrote: > > On Thu, Feb 01, 2007 at 03:38:33PM -0500, Bill Zingler wrote: > > The following command yeilds the error below. Anyone have any ideas > what > > could be the problem. Am I encountering a problem due to using the > x86_64 > > version of FC6? > > > > Thanks, > > > > Bill > > > > virt-install --name=fc6g3 --ram=512 --vcpus=1 > --file=/home/admin/fc6g3.img > > --file-size=5 --paravirt --location= > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os--vnc > > If you have SELinux enabled, then this will fail because the disk image is > under in a permitted directory. SELinux policy requires disk images to be > in either /xen (for legacy compat), or /var/lib/xen/images (current > preferred). > > If you really really want to keep disk images elsewhere, then you need to > add the extra directory to the policy & make sure its labelled, eg > > To add to policy: > > semanage fcontext --add -t xen_image_t '/home/admin/xen(/.*)?' > > And then to label the dir: > > restorecon /home/admin/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 -=| > -- Bill Zingler Zingler & Associates, Inc. (443) 822-4857 -------------- next part -------------- An HTML attachment was scrubbed... URL: From filipe.miranda at gmail.com Mon Feb 5 14:45:26 2007 From: filipe.miranda at gmail.com (Filipe Miranda) Date: Mon, 5 Feb 2007 12:45:26 -0200 Subject: [Fedora-xen] Win2k3 guest full-virtualization guest - problems Message-ID: Hi there, I'm running FC6 kernel 2.6.19-1.2895.fc6xen xen-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 I'm using a Intel VT processor (Intel Core Duo 2) and using the option Full Virtualization. The first part of the install begins without much struggle, it detects the hardware, finds the disk, and after the disk format the virtual console crashes. Is there any hints on how to proceed with this guest installation? Any help is appreciated. Here is the information about the guest OS: The configuration file for the guest machine /etc/xen/win2k3: # Automatically generated xen config file name = "win2k3" builder = "hvm" memory = "500" disk = [ 'file:/backup/xen/win2k3,hda,w', ] vif = [ 'type=ioemu, mac=00:16:3e:65:70:5d, bridge=xenbr0', ] uuid = "9e685a11-8abf-bd86-2db5-8c36cd0b84b3" device_model = "/usr/lib/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 the /var/log/xen : xend.log [2007-02-05 12:37:14 xend.XendDomainInfo 19124] WARNING (XendDomainInfo:882) Domain has crashed: name=win2k3 id=25. [2007-02-05 12:37:14 xend.XendDomainInfo 19124] DEBUG (XendDomainInfo:1460) XendDomainInfo.destroy: domid=25 [2007-02-05 12:37:14 xend.XendDomainInfo 19124] DEBUG (XendDomainInfo:1468) XendDomainInfo.destroyDomain(25) [2007-02-05 12:37:14 xend 19124] DEBUG (image:525) hvm shutdown watch unregistered qemu-dm.22827.log domid: 25 shared page at pfn:1f3ff, mfn: 3d50f buffered io page at pfn:1f3fd, mfn: 3d511 xs_read(): vncpasswd get error. /vm/9e685a11-8abf-bd86-2db5-8c36cd0b84b3/vncpasswd. False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 -- --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From vladimir.giszpenc at gmail.com Sun Feb 4 17:57:30 2007 From: vladimir.giszpenc at gmail.com (Vladimir Giszpenc) Date: Sun, 4 Feb 2007 12:57:30 -0500 Subject: [Fedora-xen] Compatibility with others Message-ID: <8ed5cbac0702040957w7bccfd00jda28e986fbc051f1@mail.gmail.com> Hi, I was really amazed with the ease of adding FC6 DomUs. However, when I tried other distributions (gentoo, debian, suse) it was pretty much impossible as I am a newbie and the howtos overwhelmed me. Is there any plan to have a standard DomU format (such as the wonderful one FC6 uses) to be used for all DomUs? Right now, it is easy to add FC6 on top of a FC6 Dom0 but if I want NetBSD as a Dom0 and RHEL5 as DomUs I would like a standard DomU adding tool to make that possible. I understand that you cannot make others follow your direction, but maybe you can help me anyway. In short I like the ease of use of adding DomUs in FC6, but I wish FC6 played well with others as a Dom0. And I wish that way of playing well with others was a standard so I could ask the same of other Dom0 making distros and/or ask DomU making distros to package their OSes in a friendly way. Thanks for your time, Vlad From billzingler at gmail.com Mon Feb 5 19:22:01 2007 From: billzingler at gmail.com (Bill Zingler) Date: Mon, 5 Feb 2007 14:22:01 -0500 Subject: [Fedora-xen] Unable to get working guest on FC6 In-Reply-To: References: <20070204160153.GA19290@redhat.com> Message-ID: I have made a another attempt with the following command: virt-install --name=fc6g3 --ram=512 --vcpus=1 --file=/var/lib/xen/images/fc6g3.img --file-size=5 --paravirt --location= http://10.1.10.2/Zod-dvd-x86_64/ --vnc This time, the location agrument is getting install files from a local server, but I still get the same results. I have included the xend.logwhich shows the following error: [2007-02-05 13:45:39 xend 3391] ERROR (SrvBase:88) Request wait_for_devices failed. Not sure what devices this is referring to. Any one have some suggestions? Thanks, Bill The xend.log contains the following info: [2007-02-05 13:43:52 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:1460) XendDomainInfo.destroy: domid=18 [2007-02-05 13:43:52 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:1468) XendDomainInfo.destroyDomain(18) [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/10/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/12/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/14/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/15/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/17/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/10/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/12/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/14/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/15/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/17/0/hotplug-status. [2007-02-05 13:43:53 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/18/0/hotplug-status. [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'fc6g3'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid', '4dd02285-72d1-1c50-04e9-6ec2408966fe'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/vmlinuz.BF-1d7'], ['ramdisk', '/var/lib/xen/initrd.img.QDw2yy'], ['args', ' method= http://10.1.10.2/Zod-dvd-x86_64/ '], ['vnc', '1'], ['vncunused', '1']]], ['device', ['tap', ['dev', 'xvda'], ['uname', 'tap:aio:/var/lib/xen/images/fc6g3.img'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:16:3e:71:78:08'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']]]]) [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'fc6g3'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid', '4dd02285-72d1-1c50-04e9-6ec2408966fe'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/vmlinuz.BF-1d7'], ['ramdisk', '/var/lib/xen/initrd.img.QDw2yy'], ['args', ' method= http://10.1.10.2/Zod-dvd-x86_64/ '], ['vnc', '1'], ['vncunused', '1']]], ['device', ['tap', ['dev', 'xvda'], ['uname', 'tap:aio:/var/lib/xen/images/fc6g3.img'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:16:3e:71:78:08'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']]]] [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': '4dd02285-72d1-1c50-04e9-6ec2408966fe', 'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None, 'image': ['linux', ['kernel', '/var/lib/xen/vmlinuz.BF-1d7'], ['ramdisk', '/var/lib/xen/initrd.img.QDw2yy'], ['args', ' method= http://10.1.10.2/Zod-dvd-x86_64/ '], ['vnc', '1'], ['vncunused', '1']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'fc6g3', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 512, 'device': [('tap', ['tap', ['dev', 'xvda'], ['uname', 'tap:aio:/var/lib/xen/images/fc6g3.img'], ['mode', 'w']]), ('vif', ['vif', ['mac', '00:16:3e:71:78:08'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']])], 'bootloader': None, 'cpu': None, 'maxmem': 512} [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 19 1.0 [2007-02-05 13:43:59 xend 3391] INFO (image:222) configuring linux guest [2007-02-05 13:43:59 xend 3391] INFO (image:245) setting use_graphics [2007-02-05 13:43:59 xend 3391] DEBUG (balloon:127) Balloon: 1523556 KiB free; need 524288; done. [2007-02-05 13:43:59 xend 3391] INFO (image:138) buildDomain os=linux dom=19 vcpus=1 [2007-02-05 13:43:59 xend 3391] WARNING (image:598) Unable to set e820 map. Probably an old HyperVisor. (38, 'Function not implemented') [2007-02-05 13:43:59 xend 3391] DEBUG (image:201) dom = 19 [2007-02-05 13:43:59 xend 3391] DEBUG (image:202) image = /var/lib/xen/vmlinuz.BF-1d7 [2007-02-05 13:43:59 xend 3391] DEBUG (image:203) store_evtchn = 1 [2007-02-05 13:43:59 xend 3391] DEBUG (image:204) console_evtchn = 2 [2007-02-05 13:43:59 xend 3391] DEBUG (image:205) cmdline = method= http://10.1.10.2/Zod-dvd-x86_64/ [2007-02-05 13:43:59 xend 3391] DEBUG (image:206) ramdisk = /var/lib/xen/initrd.img.QDw2yy [2007-02-05 13:43:59 xend 3391] DEBUG (image:207) vcpus = 1 [2007-02-05 13:43:59 xend 3391] DEBUG (image:208) features = [2007-02-05 13:43:59 xend 3391] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '51712', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/tap/19/51712'} to /local/domain/19/device/vbd/51712. [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:112) DevController: writing {'domain': 'fc6g3', 'frontend': '/local/domain/19/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/fc6g3.img', 'mode': 'w', 'online': '1', 'frontend-id': '19', 'type': 'tap'} to /local/domain/0/backend/tap/19/51712. [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:71:78:08', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/19/0'} to /local/domain/19/device/vif/0. [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'fc6g3', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/19/device/vif/0', 'mac': '00:16:3e:71:78:08', 'online': '1', 'frontend-id': '19'} to /local/domain/0/backend/vif/19/0. [2007-02-05 13:43:59 xend 3391] INFO (image:287) spawning video: ['/usr/lib64/xen/bin/xen-vncfb', '--unused', '--listen', '127.0.0.1', '--domid', '19', '--title', 'fc6g3'] [2007-02-05 13:43:59 xend 3391] INFO (image:289) device model pid: 7643 [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '0', 'uuid': '4dd02285-72d1-1c50-04e9-6ec2408966fe', 'on_reboot': 'destroy', 'start_time': '1170701039.71', 'on_poweroff': 'destroy', 'name': 'fc6g3', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 'destroy', 'image': "(linux (kernel /var/lib/xen/vmlinuz.BF-1d7) (ramdisk /var/lib/xen/initrd.img.QDw2yy) (args ' method= http://10.1.10.2/Zod-dvd-x86_64/ ') (vnc 1) (vncunused 1))", 'maxmem': '512'} [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:750) Storing domain details: {'console/ring-ref': '629607', 'console/port': '2', 'name': 'fc6g3', 'console/limit': '1048576', 'vm': '/vm/4dd02285-72d1-1c50-04e9-6ec2408966fe', 'domid': '19', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '629608', 'store/port': '1'} [2007-02-05 13:43:59 xend.XendDomainInfo 3391] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:143) Waiting for devices vif. [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:149) Waiting for 0. [2007-02-05 13:43:59 xend 3391] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/19/0/hotplug-status. [2007-02-05 13:45:39 xend 3391] ERROR (SrvBase:88) Request wait_for_devices failed. Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 72, in op_wait_for_devices return self.dom.waitForDevices() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1607, in waitForDevices self.waitForDevices_(c) File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1101, in waitForDevices_ return self.getDeviceController(deviceClass).waitForDevices() File "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py", line 145, in waitForDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py", line 154, in waitForDevice self.destroyDevice(devid) TypeError: destroyDevice() takes exactly 3 arguments (2 given) On 2/5/07, Bill Zingler wrote: > > Dan, > > Thanks for the response. I changed my command to: > > virt-install --name=fc6g3 --ram=512 --vcpus=1 > --file=/var/lib/xen/images/fc6g3.img --file-size=5 --paravirt --location=http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os--vnc > > But, I get the same error. I then disabled SELinux and still got the same > error. > > Do you know of any working tutorials on this? I have looked at: > > https://virt.108.redhat.com/articles/2007/01/15/xen-chapter-from-fedora-core-6-unleashed.html > http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 > They both are short on details. > > Thanks, > > Bill > > > On 2/4/07, Daniel P. Berrange wrote: > > > > On Thu, Feb 01, 2007 at 03:38:33PM -0500, Bill Zingler wrote: > > > The following command yeilds the error below. Anyone have any ideas > > what > > > could be the problem. Am I encountering a problem due to using the > > x86_64 > > > version of FC6? > > > > > > Thanks, > > > > > > Bill > > > > > > virt-install --name=fc6g3 --ram=512 --vcpus=1 > > --file=/home/admin/fc6g3.img > > > --file-size=5 --paravirt --location= > > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os--vnc > > > > If you have SELinux enabled, then this will fail because the disk image > > is > > under in a permitted directory. SELinux policy requires disk images to > > be > > in either /xen (for legacy compat), or /var/lib/xen/images (current > > preferred). > > > > If you really really want to keep disk images elsewhere, then you need > > to > > add the extra directory to the policy & make sure its labelled, eg > > > > To add to policy: > > > > semanage fcontext --add -t xen_image_t '/home/admin/xen(/.*)?' > > > > And then to label the dir: > > > > restorecon /home/admin/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 -=| > > > > > > -- > Bill Zingler > Zingler & Associates, Inc. > (443) 822-4857 > -- Bill Zingler Zingler & Associates, Inc. (443) 822-4857 -------------- next part -------------- An HTML attachment was scrubbed... URL: From list+fcxen at riverside-machines.co.uk Mon Feb 5 19:33:03 2007 From: list+fcxen at riverside-machines.co.uk (Evan Lavelle) Date: Mon, 05 Feb 2007 19:33:03 +0000 Subject: [Fedora-xen] fc6-xen install issues Message-ID: <45C7866F.5020400@riverside-machines.co.uk> Just done an out-of-the-box installation of FC6, with 'virtualization' selected. However, I was surprised to find that I've only got the Xen kernel in /boot, and only the Xen option in grub.conf. Is this expected? Surely there should also be an unmodified kernel? I'm tempted to re-install without virtualization, and to do a manual Xen install, to make sure that I have a fall-back kernel. I've also got very slow performance on my networked X terminal (this box is headless; I use WinAxe on a PC). In fact, it's so slow that WinAxe is pretty much unusable. Any ideas what's going on here? Is anyone getting reasonable performance on Exceed/WinAxe/VNC/whatever? Thanks - Evan From berrange at redhat.com Mon Feb 5 20:16:20 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 5 Feb 2007 20:16:20 +0000 Subject: [Fedora-xen] fc6-xen install issues In-Reply-To: <45C7866F.5020400@riverside-machines.co.uk> References: <45C7866F.5020400@riverside-machines.co.uk> Message-ID: <20070205201620.GA5478@redhat.com> On Mon, Feb 05, 2007 at 07:33:03PM +0000, Evan Lavelle wrote: > Just done an out-of-the-box installation of FC6, with 'virtualization' > selected. However, I was surprised to find that I've only got the Xen > kernel in /boot, and only the Xen option in grub.conf. > > Is this expected? Surely there should also be an unmodified kernel? I'm > tempted to re-install without virtualization, and to do a manual Xen > install, to make sure that I have a fall-back kernel. Yes, when you select 'virtualization' you'll only get the xen-ified kernel, no bare metal. You can easily just do 'yum install kernel' after your initial install if you want a bare-metal fallback kernel. 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 henning_sprang at gmx.de Tue Feb 6 12:51:42 2007 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 6 Feb 2007 13:51:42 +0100 Subject: [Fedora-xen] Compatibility with others In-Reply-To: <8ed5cbac0702040957w7bccfd00jda28e986fbc051f1@mail.gmail.com> References: <8ed5cbac0702040957w7bccfd00jda28e986fbc051f1@mail.gmail.com> Message-ID: <5bb00b3f0702060451s403f362bx9982ee846f5d93b6@mail.gmail.com> On 2/4/07, Vladimir Giszpenc wrote: > Is there > any plan to have a standard DomU format (such as the wonderful one FC6 > uses) to be used for all DomUs? What do you mean with "standard domU format"? I think the different implementations on different distributions all have their pros and cons - I tested them on Fedora, SuSE, Ubuntu and Debian. Too long to name all differences and pros and cons, but they all have theirs. > Right now, it is easy to add FC6 on > top of a FC6 Dom0 but if I want NetBSD as a Dom0 and RHEL5 as DomUs I > would like a standard DomU adding tool to make that possible. The problem with NetBSD is that the current available NetBSD Kernels have a different PAE setting than the Fedora xen packages. One would need to get a PAE-enabled NETBSD DomU Kernel - don't know if this is just a simple compile switch and recompile, or if it's harder to get. I've not found the time to ask the netbsd developers for a solution. Apart from that, there is not much of "following Fedoras path" required for the others - basically virt-manager would only be required to use the (when available as PAE) NetBSD Install kernel instead of the Linux Kernel, and after installation switch to the NetBSD runtime kernel. That should be doable. Henning From guy at neocleus.com Tue Feb 6 10:12:09 2007 From: guy at neocleus.com (Guy Zana) Date: Tue, 6 Feb 2007 05:12:09 -0500 Subject: [Fedora-xen] FC6 Dom0 Xen Kernel Sources Message-ID: <9392A06CB0FDC847B3A530B3DC174E7B01E9E664@mse10be1.mse10.exchange.ms> Hi, 1. Where can I find the *release* version of the dom0 xen kernel source for FC6? Have I encountered the development tree? http://hg.et.redhat.com/kernel/ 2. What are the "development" phases that redhat do in order to port xen to fedora? Thanks, Guy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From m3freak at rogers.com Tue Feb 6 18:00:00 2007 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Tue, 06 Feb 2007 13:00:00 -0500 Subject: [Fedora-xen] problem with xenguest-install@redhat.com In-Reply-To: <45C6E91D.3060702@int-evry.fr> References: <45C6E91D.3060702@int-evry.fr> Message-ID: <1170784801.11067.15.camel@krs> On Mon, 2007-02-05 at 09:21 +0100, Eric Doutreleau wrote: > What is the name of your virtual machine? ntp1 > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /var/xen/ntp1.img > How large would you like the disk to be (in gigabytes)? 10 > What is the install location? http://yum.int-evry.fr/core/fc5 > > Traceback (most recent call last): > File "/usr/sbin/xenguest-install.py", line 460, in ? > main() > File "/usr/sbin/xenguest-install.py", line 451, in main > start_paravirt_install(name, ram, disk, mac, uuid, src, options.extra) > File "/usr/sbin/xenguest-install.py", line 324, in start_paravirt_install > conn = libvirt.open(None) > File "/usr/lib/python2.4/site-packages/libvirt.py", line 39, in open > if ret is None:raise libvirtError('virConnectOpen() failed') > libvirt.libvirtError: virConnectOpen() failed When I try to install a CentOS 4 domU with virt-install (xenguest-install is a symlink to the virt-install tool), I get this error: ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Content-Length: 345 Date: Tue, 06 Feb 2007 17:30:34 GMT Accept-Ranges: bytes Content-Type: text/html Server: lighttpd/1.3.16 Here's the command I used: virt-install -n aserisk -r 128 -f /dev/vg00/asterisk -s 1.2 -b xenbr0 -p -l http://mirror.linux.duke.edu/pub/centos/4.4/os/i386/CentOS/RPMS/ I've tried a number of different locations, but everything fails. I have yet to find an example "path/to/tree" example that would help me understand what I'm doing wrong. Having said that, I do have running domUs, but I didn't set them up the "fedora" way. That's what I'm attempting to do now. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.19-1.2895.fc6 i686 GNU/Linux 12:56:42 up 6 days, 17:58, 2 users, load average: 0.18, 0.45, 0.50 From m3freak at rogers.com Tue Feb 6 18:09:20 2007 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Tue, 06 Feb 2007 13:09:20 -0500 Subject: [Fedora-xen] problem with xenguest-install@redhat.com In-Reply-To: <1170784801.11067.15.camel@krs> References: <45C6E91D.3060702@int-evry.fr> <1170784801.11067.15.camel@krs> Message-ID: <1170785360.11067.19.camel@krs> On Tue, 2007-02-06 at 13:00 -0500, Kanwar Ranbir Sandhu wrote: > I've tried a number of different locations, but everything fails. I > have yet to find an example "path/to/tree" example that would help me > understand what I'm doing wrong. Never fails...I think I found the answer in this thread (to my problem anyway - not sure if it applies to the thread starter): http://www.redhat.com/archives/fedora-xen/2007-January/msg00088.html That explains what's going on. Guess I'll have to wait until CentOS 4.5 is out before I can try out the virt-install tool. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.19-1.2895.fc6 i686 GNU/Linux 13:07:13 up 6 days, 18:09, 2 users, load average: 0.25, 0.28, 0.37 From berrange at redhat.com Tue Feb 6 18:10:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 6 Feb 2007 18:10:15 +0000 Subject: [Fedora-xen] problem with xenguest-install@redhat.com In-Reply-To: <1170784801.11067.15.camel@krs> References: <45C6E91D.3060702@int-evry.fr> <1170784801.11067.15.camel@krs> Message-ID: <20070206181015.GE16463@redhat.com> On Tue, Feb 06, 2007 at 01:00:00PM -0500, Kanwar Ranbir Sandhu wrote: > On Mon, 2007-02-05 at 09:21 +0100, Eric Doutreleau wrote: > > What is the name of your virtual machine? ntp1 > > How much RAM should be allocated (in megabytes)? 256 > > What would you like to use as the disk (path)? /var/xen/ntp1.img > > How large would you like the disk to be (in gigabytes)? 10 > > What is the install location? http://yum.int-evry.fr/core/fc5 > > > > Traceback (most recent call last): > > File "/usr/sbin/xenguest-install.py", line 460, in ? > > main() > > File "/usr/sbin/xenguest-install.py", line 451, in main > > start_paravirt_install(name, ram, disk, mac, uuid, src, options.extra) > > File "/usr/sbin/xenguest-install.py", line 324, in start_paravirt_install > > conn = libvirt.open(None) > > File "/usr/lib/python2.4/site-packages/libvirt.py", line 39, in open > > if ret is None:raise libvirtError('virConnectOpen() failed') > > libvirt.libvirtError: virConnectOpen() failed > > When I try to install a CentOS 4 domU with virt-install > (xenguest-install is a symlink to the virt-install tool), I get this > error: > > ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: > Content-Length: 345 > Date: Tue, 06 Feb 2007 17:30:34 GMT > Accept-Ranges: bytes > Content-Type: text/html > Server: lighttpd/1.3.16 > > Here's the command I used: > > virt-install -n aserisk -r 128 -f /dev/vg00/asterisk -s 1.2 -b xenbr0 -p > -l http://mirror.linux.duke.edu/pub/centos/4.4/os/i386/CentOS/RPMS/ > > I've tried a number of different locations, but everything fails. I > have yet to find an example "path/to/tree" example that would help me > understand what I'm doing wrong. The CentOS 4 distro does not suppport paravirtualization. You will have to do full virtualizated installs, which require local ISO image / CDROM. 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 Tue Feb 6 21:42:38 2007 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Tue, 06 Feb 2007 16:42:38 -0500 Subject: [Fedora-xen] problem with xenguest-install@redhat.com In-Reply-To: <20070206181015.GE16463@redhat.com> References: <45C6E91D.3060702@int-evry.fr> <1170784801.11067.15.camel@krs> <20070206181015.GE16463@redhat.com> Message-ID: <1170798158.11067.28.camel@krs> On Tue, 2007-02-06 at 18:10 +0000, Daniel P. Berrange wrote: > The CentOS 4 distro does not suppport paravirtualization. You will have to > do full virtualizated installs, which require local ISO image / CDROM. I'm running two CentOS 4.4 domU on a FC6 dom0 right now, though they weren't created with the virt-install tool. I want to setup two more CentOS 4.4 domU, but this time with virt-install - that's when I had problems. I suspect there are some problems though because udev fails to start when the domU boot. Also, I have to manually kill nash-hotplugd because it eats 99% of the CPU. I didn't have this problem at all when dom0 was FC5. When CentOS 5 is out, I'm going to use it as dom0. That should run paravirtualized CentOS 4 domU well (as far as I know). I want to get a new server so I can have full virtualized domUs. But, it's not in the budget - maybe in a couple of years. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.19-1.2895.fc6 i686 GNU/Linux 16:35:01 up 6 days, 21:37, 2 users, load average: 0.74, 0.81, 0.61 From EyalRi at clal-ins.co.il Wed Feb 7 07:28:53 2007 From: EyalRi at clal-ins.co.il (EyalRi at clal-ins.co.il) Date: Wed, 7 Feb 2007 09:28:53 +0200 Subject: [Fedora-xen] Trouble installing VM under Xen Server Message-ID: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> Hi, I am trying to install Xen VM (redhat) under Xen Redhat 5.0 beta. Using virt-install I have entered the following: What is the name of your virtual machine? xen01 How much RAM should be allocated (in megabytes)? 2000 What would you like to use as the disk (path)? /xen_vm/xen01.img How large would you like the disk to be (in gigabytes)? 10 Would you like to enable graphics support? (yes or no) yes What is the install location? nfs:abc:/abc/Unix_Install Starting install... ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.sOAI67/images/xen/vmlinuz' The "abc:/abc/Unix_Install" is pointing to nfs mount point with Redhat ISO`s (.iso) Tried using ftp,http,nfs - with no success Any idea what could be the problem ? Regards, Eyal ----------------------------------------------------------------------------------------- This message was sent by Clal Insurance Ltd Mail Systems Visit us at http://www.clalbit.co.il ----------------------------------------------------------------------------------------- The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. If you are not an intended recipient, please delete the message and any attachments and notify the sender of misdelivery: any use or disclosure of the contents of either is unauthorized and may be unlawful. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at base2technology.com Wed Feb 7 18:10:01 2007 From: chris at base2technology.com (Chris Hirsch) Date: Wed, 07 Feb 2007 11:10:01 -0700 Subject: [Fedora-xen] Raid-1 over iscsi vs DRBD? Message-ID: <45CA15F9.4080307@base2technology.com> Hey all...I'm looking to set up a high availably xen "cluster" so that if my iSCSI storage goes down, my domU's will remain up. I've been looking around on the net and it appears this is a pretty common thing to do but I have one question that I haven't seen an answer to. It looks like I can accomplish the high availably in one of two ways. I can use DRBD on my two boxes as shown here http://www.gridvm.org/drbd-lvm-gnbd-and-xen-for-free-and-reliable-san.html and I should be able to take down a storage box and my iSCSI domU's will never know any difference. An alternate approach (as I see it) is that instead of DRBD I should be able to carve out two iSCSI targets (one on each storage machine) and then in my domU make those two targets (say sda1 and sdb1) a raid-1 and accomplish the same thing as DRBD but use the Linux md stuff instead? Is there a reason that this isn't done? From my lack of findings I'd say yes but I haven't actually tried this in a real setting yet. I was just hoping somebody could steer me in the right direction (and away from this approach if it's just silly). My *guess* is that DRBD was written to do a network raid-1 and thus has optimizations to do just that vs a Linux "disk" raid-1 using md. Thanks for any pointers or insights to this. I'd really appreciate any websites or writeups that would compare the two or just some cook book examples. Thanks, Chris From rstevens at vitalstream.com Wed Feb 7 18:33:45 2007 From: rstevens at vitalstream.com (Rick Stevens) Date: Wed, 07 Feb 2007 10:33:45 -0800 Subject: [Fedora-xen] Having issues with Windows 2003 as a guest Message-ID: <1170873225.5284.87.camel@prophead.corp.publichost.com> System configuration: Opteron 1210, 2GB RAM, Abit motherboard with nVidia chipset, but running "vesa" video driver. I'm trying to get Windows 2003 Server SP2 up and running on Xen as a guest. The installation gets stuck at the blue "Starting Windows" screen. I read somewhere that early in the boot process, at the "Press F6 to install SCSI drivers", I should press F5 instead, then select the HAL version for "Standard PC". All well and good. The problem is that when I use VNC as the console, the system ignores keyboard input, and when I try to switch to SDL, I get no console at all. Needless to say, this is bloody frustrating. Here's my config file: -------------------------------- CUT HERE ---------------------------- # -*- 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 = 8 # 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=0 pae=1 # enable/disable HVM guest ACPI, default=0 (disabled) #acpi=0 # enable/disable HVM guest APIC, default=0 (disabled) #apic=0 # 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 = [ 'file:/var/lib/xen/images/win2k3.img,hda,w', 'phy:/dev/cdrom,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 = 'restart' #on_crash = 'restart' #============================================================================ # 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="cda" boot="dc" #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 # Crikey, VNC's not working, let's try SDL. #sdl=0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 # For now, we're trying SDL #vnc=1 vnc=0 #---------------------------------------------------------------------------- # 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 #---------------------------------------------------------------------------- # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=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' #----------------------------------------------------------------------------- # 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=1 # 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' -------------------------------- CUT HERE ---------------------------- Any help will be GREATLY appreciated and you'll win major good karma points! ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com - - VitalStream, Inc. http://www.vitalstream.com - - - - BASIC is the Computer Science version of `Scientific Creationism' - ---------------------------------------------------------------------- From mkearey at redhat.com Wed Feb 7 23:58:59 2007 From: mkearey at redhat.com (Mike Kearey) Date: Thu, 08 Feb 2007 09:58:59 +1000 Subject: [Fedora-xen] Trouble installing VM under Xen Server In-Reply-To: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> References: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> Message-ID: <45CA67C3.2090705@redhat.com> EyalRi at clal-ins.co.il wrote: > Hi, > > I am trying to install Xen VM (redhat) under Xen Redhat 5.0 beta. > Using virt-install I have entered the following: > > What is the name of your virtual machine? xen01 > How much RAM should be allocated (in megabytes)? 2000 > What would you like to use as the disk (path)? /xen_vm/xen01.img > How large would you like the disk to be (in gigabytes)? 10 > Would you like to enable graphics support? (yes or no) yes > What is the install location? nfs:abc:/abc/Unix_Install > > > Starting install... > ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.sOAI67/images/xen/vmlinuz' > > > The "abc:/abc/Unix_Install" is pointing to nfs mount point with Redhat ISO`s (.iso) > > Tried using ftp,http,nfs - with no success > > Any idea what could be the problem ? > > Regards, > Eyal In my experience it must be an install _tree_ and not a set of ISO images. Yes I am aware that we can do NFS installs by pointing at ISO's. But I have not seen it work with a virt install.. > > ----------------------------------------------------------------------------------------- > This message was sent by Clal Insurance Ltd Mail Systems > > Visit us at http://www.clalbit.co.il > ----------------------------------------------------------------------------------------- > The information in this e-mail and any attachments is confidential and may be > legally privileged. It is intended solely for the addressee or addressees. If > you are not an intended recipient, please delete the message and any attachments > and notify the sender of misdelivery: any use or disclosure of the contents of > either is unauthorized and may be unlawful. You are posting to a public mailing list. We cannot comply with this message :) Cheers, Michael From berrange at redhat.com Thu Feb 8 03:16:56 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 8 Feb 2007 03:16:56 +0000 Subject: [Fedora-xen] Trouble installing VM under Xen Server In-Reply-To: <45CA67C3.2090705@redhat.com> References: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> <45CA67C3.2090705@redhat.com> Message-ID: <20070208031656.GA13701@redhat.com> On Thu, Feb 08, 2007 at 09:58:59AM +1000, Mike Kearey wrote: > EyalRi at clal-ins.co.il wrote: > > Hi, > > > > I am trying to install Xen VM (redhat) under Xen Redhat 5.0 beta. > > Using virt-install I have entered the following: > > > > What is the name of your virtual machine? xen01 > > How much RAM should be allocated (in megabytes)? 2000 > > What would you like to use as the disk (path)? /xen_vm/xen01.img > > How large would you like the disk to be (in gigabytes)? 10 > > Would you like to enable graphics support? (yes or no) yes > > What is the install location? nfs:abc:/abc/Unix_Install > > > > > > Starting install... > > ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.sOAI67/images/xen/vmlinuz' > > > > > > The "abc:/abc/Unix_Install" is pointing to nfs mount point with Redhat ISO`s (.iso) > > > > Tried using ftp,http,nfs - with no success > > > > Any idea what could be the problem ? > > > > Regards, > > Eyal > > In my experience it must be an install _tree_ and not a set of ISO > images. Yes I am aware that we can do NFS installs by pointing at ISO's. > But I have not seen it work with a virt install.. Indeed - the whatever URL you give for the install location must be a fully exploded tree. The virt-install program tries to fetch $URL/images/xen/vmlinuz and $URL/images/xen/initrd.img. So pointing at an ISO image won't 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 takebe_akio at jp.fujitsu.com Thu Feb 8 10:36:58 2007 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 08 Feb 2007 19:36:58 +0900 Subject: [Fedora-xen] FC6 Dom0 Xen Kernel Sources In-Reply-To: <9392A06CB0FDC847B3A530B3DC174E7B01E9E664@mse10be1.mse10.exchange.ms> References: <9392A06CB0FDC847B3A530B3DC174E7B01E9E664@mse10be1.mse10.exchange.ms> Message-ID: <68C74B6D0FA53Btakebe_akio@jp.fujitsu.com> Hi, Guy >1. Where can I find the *release* version of the dom0 xen kernel source >for FC6? >Have I encountered the development tree? >http://hg.et.redhat.com/kernel/ > You can get it from http://download.fedora.redhat.com/pub/fedora/linux/core/6/source/SRPMS/. dom0 kernel is built from kernel source with kernel-2.6.--xen.config. Best Regards, Akio Takebe From colin at agernet.org.uk Thu Feb 8 12:02:00 2007 From: colin at agernet.org.uk (Colin Ager) Date: Thu, 08 Feb 2007 12:02:00 +0000 Subject: [Fedora-xen] Nvidia drivers for xen kernel Message-ID: <45CB1138.8040409@agernet.org.uk> Hi I am a newbie to xen and I am wondering if anyone has got the latest Nvidia graphics driver (9746) working with the xen version of FC6 (2798). Nvidia reports that xen is unsupported but I have seen reports of people applying patches to make some Nvidia drivers work with xen. Is this possible? Colin Ager Norfolk UK From guy at neocleus.com Thu Feb 8 12:42:41 2007 From: guy at neocleus.com (Guy Zana) Date: Thu, 8 Feb 2007 07:42:41 -0500 Subject: [Fedora-xen] FC6 Dom0 Xen Kernel Sources In-Reply-To: <68C74B6D0FA53Btakebe_akio@jp.fujitsu.com> Message-ID: <9392A06CB0FDC847B3A530B3DC174E7B01EEA7A4@mse10be1.mse10.exchange.ms> Thanks! > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] > Sent: Thursday, February 08, 2007 12:37 PM > To: Guy Zana; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] FC6 Dom0 Xen Kernel Sources > > Hi, Guy > > >1. Where can I find the *release* version of the dom0 xen > kernel source > >for FC6? > >Have I encountered the development tree? > >http://hg.et.redhat.com/kernel/ > > > You can get it from > http://download.fedora.redhat.com/pub/fedora/linux/core/6/sour > ce/SRPMS/. > > dom0 kernel is built from kernel source > with kernel-2.6.--xen.config. > > Best Regards, > > Akio Takebe > > From davidsonpaulo at gmail.com Thu Feb 8 16:06:28 2007 From: davidsonpaulo at gmail.com (Davidson Rodrigues Paulo) Date: Thu, 8 Feb 2007 14:06:28 -0200 Subject: [Fedora-xen] All the ways go to Error: (22, 'Invalid argument') Message-ID: Good afternoon, I've installed Xen on a Fedora 6. The xend process are running, all ok, but no matter what or how I try to create a new domain, I got the useless error message "Error: (22, 'Invalid argument')". On my last try, I've populated the directory /vm/fc5.base with a base installation of Fedora Core 5. So, I exported that directory on NFS, inserting the following line on /etc/exports /vm/fc5.base *(rw,no_root_squash) and running exportfs -afr to update NFS server. Afer, I created a config file on /etc/xen/fc5base with the following content: # General kernel = "/vm/fc5.base/boot/vmlinuz-2.6.18-1.2257.fc5xenU" ramdisk = "/vm/fc5.base/boot/initrd-2.6.18-1.2257.fc5xenU.img" memory = 128 root = "/dev/nfs" nfs_server = "127.0.0.1" nfs_root = "/vm/fc5.base" # Network netmask = "255.255.255.0" gateway = "10.1.0.1" hostname = "doutorx.niteroi.unimed" At last, running the following command # xm create fc5base vmid=100 I got that message error: Error: (22, 'Invalid argument') I have tried other ways to create a new domain from scratch, following instrunctions on the xm man page, but, I repeat, every try result in that error message. Some idea? Thanks, Davidson Paulo From jklein at saugus.k12.ca.us Thu Feb 8 17:08:47 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Thu, 8 Feb 2007 09:08:47 -0800 Subject: [Fedora-xen] HVM Performance and PV drivers Message-ID: Anyone been able to get the PV drivers from Xensource to work on an FC6 created HVM. Performance is rather sluggish, even on 64bit, without these, yet they don't seem to want to work here. Or, alternatively, is Red Hat working on their own? The HVM IO is really a bit too slow for most production use without them. -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" -------------- next part -------------- An HTML attachment was scrubbed... URL: From master at bradleyland.com Thu Feb 8 17:36:35 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Thu, 8 Feb 2007 09:36:35 -0800 (PST) Subject: [Fedora-xen] All the ways go to Error: (22, 'Invalid argument') In-Reply-To: References: Message-ID: <2540.192.168.2.92.1170956195.squirrel@www.bradleyland.com> > Good afternoon, > > I've installed Xen on a Fedora 6. The xend process are running, all > ok, but no matter what or how I try to create a new domain, I got the > useless error message "Error: (22, 'Invalid argument')". > > On my last try, I've populated the directory /vm/fc5.base with a base > installation of Fedora Core 5. So, I exported that directory on NFS, > inserting the following line on /etc/exports > > /vm/fc5.base *(rw,no_root_squash) > > and running exportfs -afr to update NFS server. > > Afer, I created a config file on /etc/xen/fc5base with the following > content: > > # General > kernel = "/vm/fc5.base/boot/vmlinuz-2.6.18-1.2257.fc5xenU" > ramdisk = "/vm/fc5.base/boot/initrd-2.6.18-1.2257.fc5xenU.img" > memory = 128 > root = "/dev/nfs" > nfs_server = "127.0.0.1" > nfs_root = "/vm/fc5.base" > > # Network > netmask = "255.255.255.0" > gateway = "10.1.0.1" > hostname = "doutorx.niteroi.unimed" > > At last, running the following command > > # xm create fc5base vmid=100 > > I got that message error: > > Error: (22, 'Invalid argument') > > I have tried other ways to create a new domain from scratch, following > instrunctions on the xm man page, but, I repeat, every try result in > that error message. > > Some idea? > > Thanks, > > Davidson Paulo > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > I believe that error indicates the dom0 and domU kernels are mismatched PAE vs. non-PAE. All of the FC6 kernels I thought were PAE enabled now. An FC5 kernel is probably non-PAE in any case. Just use the dom0 kernel as the domU kernel. From jerutley at gmail.com Thu Feb 8 18:19:35 2007 From: jerutley at gmail.com (Jeremy Utley) Date: Thu, 8 Feb 2007 10:19:35 -0800 Subject: [Fedora-xen] Nvidia drivers for xen kernel In-Reply-To: <45CB1138.8040409@agernet.org.uk> References: <45CB1138.8040409@agernet.org.uk> Message-ID: On 2/8/07, Colin Ager wrote: > Hi > I am a newbie to xen and I am wondering if anyone has got the latest > Nvidia graphics driver (9746) working with the xen version of FC6 (2798). > > Nvidia reports that xen is unsupported but I have seen reports of people > applying patches to make some Nvidia drivers work with xen. > > Is this possible? Hey Colin! From my FC6 machine here: [jeremy at vulcan ~]$ rpm -qa | grep nvidia kmod-nvidia-xen-1.0.9746-1.2.6.19_1.2895.fc6 xorg-x11-drv-nvidia-1.0.9746-7.lvn6 Courtesy of the Livna RPM Repository :) Hope this helps! Jeremy From lamont at gurulabs.com Thu Feb 8 18:26:16 2007 From: lamont at gurulabs.com (Lamont Peterson) Date: Thu, 8 Feb 2007 11:26:16 -0700 Subject: [Fedora-xen] HVM Performance and PV drivers In-Reply-To: References: Message-ID: <200702081126.22167.lamont@gurulabs.com> On Thursday 08 February 2007 10:08am, Jim Klein wrote: > Anyone been able to get the PV drivers from Xensource to work on an > FC6 created HVM. Performance is rather sluggish, even on 64bit, > without these, yet they don't seem to want to work here. Or, > alternatively, is Red Hat working on their own? The HVM IO is really > a bit too slow for most production use without them. I don't believe that you can do this. But, I'm wondering what OS you're trying to run on the HVM DomU. If it's Linux, use a paravirtualized DomU. You'll get much better performance (especially on things like I/O). HVM adds some emulation overhead and, thus, is slower than PV. HVM is only necessary to run an OS for which no paravirtualized kernel is available. -- Lamont Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From junk at remcc.org Thu Feb 8 21:56:45 2007 From: junk at remcc.org (Robert Thiem) Date: Fri, 9 Feb 2007 07:56:45 +1000 (EST) Subject: [Fedora-xen] Nvidia drivers for xen kernel In-Reply-To: <20070208160639.7562173392@hormel.redhat.com> References: <20070208160639.7562173392@hormel.redhat.com> Message-ID: <49895.192.168.1.13.1170971805.squirrel@beatrix> > I am a newbie to xen and I am wondering if anyone has got the latest > Nvidia graphics driver (9746) working with the xen version of FC6 (2798). > ... > Colin Ager Norfolk UK I'm using a (evil) closed source nVidia driver, with FC6 xen 2.6.19-1.2895 (32 bit). It does *seem* to work, but I haven't used the Xen kernel much since so I can't comment on long term stability. I post as Penguinfan on nvnews.net http://www.nvnews.net/vbulletin/showthread.php?t=77597 From haircut at gmail.com Fri Feb 9 03:02:53 2007 From: haircut at gmail.com (Adam Monsen) Date: Thu, 8 Feb 2007 19:02:53 -0800 Subject: [Fedora-xen] cannot move Fedora Core 6 OS from one guest into another Message-ID: <9ebd65110702081902n272c70d7hd6061a2a6cbd581b@mail.gmail.com> I'm having trouble moving an entire Fedora Core 6 OS from one guest (let's call it "OLD") into a new guest ("NEW"). I want to do this because the old guest (which appears to be working just fine, thank you) uses LVM, and I'd like to discontinue using LVM. In case it saves you an hour or so of reading the rest of this email, here's the error message: -------------------8<------------------- host# xm create -c /xen/new/conf Using config file "./conf". Going to boot Fedora Core (2.6.19-1.2895.fc6xen) kernel: /boot/vmlinuz-2.6.19-1.2895.fc6xen initrd: /boot/initrd-2.6.19-1.2895.fc6xen.img Started domain manual3 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 ... XENBUS: Device with no driver: device/vbd/51712 Freeing unused kernel memory: 184k freed Write protecting the kernel read-only data: 387k Red Hat nash version 5.1.19.0.2 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 xenblk.ko module Registering block device major 202 xvda: xvda1 Loading dm-mod.ko module device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) 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... No volume groups found Activating logical volumes Volume group "VolGroup00" not found 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! ------------------->8------------------- I see nothing useful in /var/log/xend.log or /var/log/xend-debug.log, just that the domain crashed and was destroyed. Ok, now here's the whole story from the beginning... OLD is a paravirtualized guest, NEW will also be. The host for both OLD and NEW is an up-to-date FC6 system. The goal is to migrate OLD into NEW, a created-from-scratch guest that doesn't use LVM to slice up its file-backed VBD. To try to make it easy on myself, I used qemu to boot a Fedora Core 6 rescue CD .iso image (hmm, might've be a FC5 rescue CD, but this hopefully shouldn't matter based on what I did in rescue mode), as follows: -------------------8<------------------- host# qemu -hda old.img -hdb new.img -cdrom FC-6-i386-rescuecd.iso -boot d ------------------->8------------------- old.img is the file-backed VBD for OLD, and was created using a GUI-guided network/anaconda/whatever install via the "Virtual Machine Manager". The first partition is /boot, the second is an LVM volume group with two logical volumes, LogVol00 being a 1.9G partition that is mounted as the root partition, and LogVol01 is used for swap space. -------------------8<------------------- host# ls -lh old.img -rw-r--r-- 1 root root 3.0G Feb 8 17:07 old.img host# du -hs old.img 934M old.img host# fdisk -l old.img last_lba(): I don't know how to handle files with mode 81a4 You must set cylinders. You can do this from the extra functions menu. Disk old.img: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System old.img1 * 1 13 104391 83 Linux old.img2 14 382 2963992+ 8e Linux LVM ------------------->8------------------- new.img was just a large sparse file, waiting to become a file-backed VBD. -------------------8<------------------- host# dd if=/dev/zero bs=1 count=1 seek=3G of=new.img ------------------->8------------------- And qemu worked fine. In rescue mode, I was able to mount both file-backed VBDs, partition/format hdb, copy over OLD to create NEW. Seemed peachy. -------------------8<------------------- qemu# fdisk -l /dev/hdb Disk /dev/hdb: 3221 MB, 3221225472 bytes 255 heads, 63 sectors/track, 391 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 391 3140676 83 Linux qemu# mkfs.ext3 /dev/hdb1 ...worked fine... qemu# mkdir /mnt/old qemu# lvm vgchange -ay 2 logical volume(s) in volume group "VolGroup00" now active qemu# mount /dev/VolGroup00/LogVol00 /mnt/old qemu# mount /dev/hda1 /mnt/old/boot qemu# mkdir /mnt/new qemu# mount /dev/hdb1 /mnt/new qemu# cp -a /mnt/old/* /mnt/new ------------------->8------------------- grub install onto hdb seemed to work fine, too: -------------------8<------------------- qemu# grub grub> device (hd0) /dev/hdb grub> root (hd0,0) grub> setup (hd0) ...worked fine... grub> quit ------------------->8------------------- I then got out of rescue mode and quit qemu. I proceeded to modify NEW slightly. First I mounted it): -------------------8<------------------- host# mkdir /mnt/new host# bytes_sec=512 sect_track=63 host# mount -o loop,offset=$((bytes_sec * sect_track)) hd.img /mnt/new ------------------->8------------------- I got that calculation for the offset from the Xen user manual. I was somehow using this python script to derive the number of cylinders: -------------------8<------------------- host# cat disk_geom.py size_GiB = 2.0 size_bytes = size_GiB * 1024 * 1024 * 1024 bytes_sec = 512 sec_track = 63 heads = 255 print "Cylinders: %d" % (size_bytes / (heads * sec_track * bytes_sec)) ------------------->8------------------- And yeah, I'm saying 2.0 GB instead of 3.0 GB in the script, and I'm probably mixing up GiB and GB, and ...ugh. ANYWAY, the mount command actually worked, so I guess 32256 (512 * 63) was correct. Or something. At any rate, I was able to modify files in the NEW's file-backed VBD. /etc/grub.conf (a symlink to ../boot/grub/grub.conf) became: -------------------8<------------------- default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.19-1.2895.fc6xen) root (hd0,0) kernel /boot/vmlinuz-2.6.19-1.2895.fc6xen ro root=/ initrd /boot/initrd-2.6.19-1.2895.fc6xen.img ------------------->8------------------- The Xen guest config for NEW looks like: -------------------8<------------------- name = 'new' memory = '256' disk = [ 'tap:aio:/var/xen/vm/new/hd.img,xvda,w' ] vif = [ '' ] vnc = 1 bootloader = '/usr/bin/pygrub' on_reboot = 'restart' on_crash = 'destroy' ------------------->8------------------- NEW's /etc/fstab looks like: -------------------8<------------------- /dev/xvda1 / 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 ------------------->8------------------- (nope, no swap, hope I don't need that). I also changed NEW's /boot/grub/device.map, just in case: -------------------8<------------------- (hd0) /dev/xvda ------------------->8------------------- I then unmounted the file-backed VBD, started up NEW, and saw the error I pasted at the top of this email. Hints on how I could possibly make this any harder on myself would also be appreciated. Thanks! -- Adam Monsen From jklein at saugus.k12.ca.us Fri Feb 9 05:40:50 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Thu, 8 Feb 2007 21:40:50 -0800 (PST) Subject: [Fedora-xen] HVM Performance and PV drivers In-Reply-To: <8204975.950451170998633660.JavaMail.root@do8> Message-ID: <7299753.950531170999650887.JavaMail.root@do8> On Thursday 08 February 2007 10:08am, Jim Klein wrote: > Anyone been able to get the PV drivers from Xensource to work on an > FC6 created HVM. Performance is rather sluggish, even on 64bit, > without these, yet they don't seem to want to work here. Or, > alternatively, is Red Hat working on their own? The HVM IO is really > a bit too slow for most production use without them. On Thu, 8 Feb 2007 11:26am, Lamont Peterson wrote: > I don't believe that you can do this. > >But, I'm wondering what OS you're trying to run on the HVM DomU. If it's >Linux, use a paravirtualized DomU. You'll get much better performance >(especially on things like I/O). > >HVM adds some emulation overhead and, thus, is slower than PV. HVM is only >necessary to run an OS for which no paravirtualized kernel is available. >-- >Lamont Peterson >Senior Instructor >Guru Labs, L.C. [ http://www.GuruLabs.com/ ] All my Linux guests are PV (been running Xen in production for 7 months - far longer in testing.) I'm talking about Windows guests, which is why I would need PV drivers to work. Am running 64bit Dom0 to alleviate some of the pain, but I/O is still too slow for anything but lightweight applications. We're a RHEL shop, so would prefer to use RHEL as a base over XenSource Commercial, but it looks like I may have to go that route if noone else is working on PV drivers for Windows guests. -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" -------------- next part -------------- An HTML attachment was scrubbed... URL: From ligesh at lxlabs.com Fri Feb 9 10:37:26 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Fri, 9 Feb 2007 16:07:26 +0530 Subject: [Fedora-xen] Xen, Security and Selinux: An analysis Message-ID: <20070209103726.GA3831@lxlabs.com> There was discussion recently about the need for security on xen dom0, and quite frankly I am a bit confused. For me, the entire idea of virtualization is to enhance the security, as in, on our main website, we have a single virtual machine (on openvz) running inside the host, which has all the services. The host has absolutely no services other than ssh. Even the ssh can be turned off, so that the only access is through the serial console, but I found it not really worth it, especially considering how cumbersome and unreliable the provider's serial console access was. The idea is that the dom0 will contain nothing other than xen virtual machines, and every other service is run inside the domUs, which is the right way, considering the really low overheads of virtualization. So whatever service you are planning to run on dom0, create a new domU specifically for it, and run it there. Xen has the problem that they have a xend service running, which frankly is a very bad design. Even for migration, the better way would be use more reliable channels like ssh, but other than that, do we actually need selinux on dom0? The only exception to this is if you have the backup of the domUs on the dom0, and you want them to be protected in the case of xend getting compromised. Thanks. From pasik at iki.fi Fri Feb 9 17:25:20 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 9 Feb 2007 19:25:20 +0200 Subject: [Fedora-xen] HVM Performance and PV drivers In-Reply-To: <7299753.950531170999650887.JavaMail.root@do8> References: <8204975.950451170998633660.JavaMail.root@do8> <7299753.950531170999650887.JavaMail.root@do8> Message-ID: <20070209172520.GP7120@edu.joroinen.fi> On Thu, Feb 08, 2007 at 09:40:50PM -0800, Jim Klein wrote: > > On Thursday 08 February 2007 10:08am, Jim Klein wrote: > > Anyone been able to get the PV drivers from Xensource to work on an > > FC6 created HVM. Performance is rather sluggish, even on 64bit, > > without these, yet they don't seem to want to work here. Or, > > alternatively, is Red Hat working on their own? The HVM IO is really > > a bit too slow for most production use without them. > > > On Thu, 8 Feb 2007 11:26am, Lamont Peterson wrote: > > I don't believe that you can do this. > > > >But, I'm wondering what OS you're trying to run on the HVM DomU. If it's > >Linux, use a paravirtualized DomU. You'll get much better performance > >(especially on things like I/O). > > > >HVM adds some emulation overhead and, thus, is slower than PV. HVM is only > >necessary to run an OS for which no paravirtualized kernel is available. > >-- > >Lamont Peterson > >Senior Instructor > >Guru Labs, L.C. [ http://www.GuruLabs.com/ ] > > All my Linux guests are PV (been running Xen in production for 7 months - far longer > in testing.) I'm talking about Windows guests, which is why I would need PV drivers to work. > Am running 64bit Dom0 to alleviate some of the pain, but I/O is still too slow for anything > but lightweight applications. We're a RHEL shop, so would prefer to use RHEL as a base over > XenSource Commercial, but it looks like I may have to go that route if noone else is working > on PV drivers for Windows guests. > Interesting point is the fact that Novell will ship Windows PV drivers in SLES 10 SP1 when it's released in May 2007.. -- Pasi From rstevens at vitalstream.com Fri Feb 9 18:58:16 2007 From: rstevens at vitalstream.com (Rick Stevens) Date: Fri, 09 Feb 2007 10:58:16 -0800 Subject: [Fedora-xen] Re: Having issues with Windows 2003 as a guest Message-ID: <1171047496.5284.233.camel@prophead.corp.publichost.com> I'll try again. Can anyone tell me why VNC consoles for Win 2003 fully virtualized guests won't accept keystrokes and why SDL-based stuff never even opens a console window? I have GOT to get this crap running! I've been doing Linux for as long as it's been around so I'm not a complete idiot. Can someone offer some help? Please? I'm getting desperate! ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com - - VitalStream, Inc. http://www.vitalstream.com - - - - I haven't lost my mind. It's backed up on tape somewhere, but - - probably not recoverable. - ---------------------------------------------------------------------- From jklein at saugus.k12.ca.us Sat Feb 10 17:45:07 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Sat, 10 Feb 2007 09:45:07 -0800 Subject: [Fedora-xen] HVM Performance and PV drivers Message-ID: <22DEE552-2012-49CA-ADE7-877D4D9DC3F9@saugus.k12.ca.us> >> >> On Thursday 08 February 2007 10:08am, Jim Klein wrote: >> >>> Anyone been able to get the PV drivers from Xensource to work on an >>> FC6 created HVM. Performance is rather sluggish, even on 64bit, >>> without these, yet they don't seem to want to work here. Or, >>> alternatively, is Red Hat working on their own? The HVM IO is really >>> a bit too slow for most production use without them. >>> >> >> >> On Thu, 8 Feb 2007 11:26am, Lamont Peterson wrote: >> >>> I don't believe that you can do this. >>> >>> But, I'm wondering what OS you're trying to run on the HVM DomU. >>> If it's >>> Linux, use a paravirtualized DomU. You'll get much better >>> performance >>> (especially on things like I/O). >>> >>> HVM adds some emulation overhead and, thus, is slower than PV. >>> HVM is only >>> necessary to run an OS for which no paravirtualized kernel is >>> available. >>> -- >>> Lamont Peterson >>> Senior Instructor >>> Guru Labs, L.C. [ http://www.GuruLabs.com/ ] >>> >> >> All my Linux guests are PV (been running Xen in production for 7 >> months - far longer >> in testing.) I'm talking about Windows guests, which is why I >> would need PV drivers to work. >> Am running 64bit Dom0 to alleviate some of the pain, but I/O is >> still too slow for anything >> but lightweight applications. We're a RHEL shop, so would prefer >> to use RHEL as a base over >> XenSource Commercial, but it looks like I may have to go that >> route if noone else is working >> on PV drivers for Windows guests. >> >> > > Interesting point is the fact that Novell will ship Windows PV > drivers in > SLES 10 SP1 when it's released in May 2007.. > > -- Pasi > If only SLES didn't suck - and Novell actually kept their promises. But I could be wrong, maybe they'll be better now that they have reliable partners like Microsoft... -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidsen at tmr.com Sat Feb 10 20:44:39 2007 From: davidsen at tmr.com (Bill Davidsen) Date: Sat, 10 Feb 2007 15:44:39 -0500 Subject: [Fedora-xen] Trouble installing VM under Xen Server In-Reply-To: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> References: <4DF43A38097C5149A792F1EEBE2F5CDF08DE0218@CETAVMAIL01.clal-ins> Message-ID: <45CE2EB7.9010707@tmr.com> EyalRi at clal-ins.co.il wrote: > > Hi, > > I am trying to install Xen VM (redhat) under Xen Redhat 5.0 beta. > > Using virt-install I have entered the following: > > What is the name of your virtual machine? xen01 > > How much RAM should be allocated (in megabytes)? 2000 > > What would you like to use as the disk (path)? /xen_vm/xen01.img > > How large would you like the disk to be (in gigabytes)? 10 > > Would you like to enable graphics support? (yes or no) yes > > What is the install location? nfs:abc:/abc/Unix_Install > > > Starting install... > > ERROR: Invalid NFS location given: [Errno 2] No such file or > directory: '/var/lib/xen/xennfs.sOAI67/images/xen/vmlinuz' > > > The "abc:/abc/Unix_Install" is pointing to nfs mount point with Redhat > ISO`s (.iso) > > Tried using ftp,http,nfs - with no success > > Any idea what could be the problem ? > > Regards, > > Eyal > You need to mount and export the ISO tree. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From jandrejkovic at gmail.com Mon Feb 12 02:51:36 2007 From: jandrejkovic at gmail.com (Jan Andrejkovic) Date: Mon, 12 Feb 2007 02:51:36 +0000 Subject: [Fedora-xen] Fwd: FreeNX session - mouse and keyboard frozen under XEN Dom0 kernel In-Reply-To: References: Message-ID: Hello FC XEN list, I already sent this e-mail to main Fedora mailing list but now I realised it will be better to send it to XEN dist list: I have FC6 installed with latests patches (I use GNOME and XEN kernel 2.6.19-1.2895.fc6xen) with all current updates. I installed FreeNX from fedora extras and I tried to connect to this Dom0 kernel from Win XP client ( 2.1.0-16). The connection was successful but after a few seconds I lost the control using mouse and keyboard. I saw the screen, Gnome was just not responding. Even when I tried to resume abandoned session I saw the dektop again but I was not able to re-gain the control. Then I removed freenx downloaded from extras and I installed newest rpms from nomachine web-site: nxclient-2.1.0-11.i386.rpm nxnode-2.1.0-15.i386.rpm nxserver-2.1.0-18.i386.rpm and for compatibility I had to add: compat-libstdc++-296-2.96-138.i386.rpm (downloaded from rpmfind) However the result was the same - sesssion gets frozen after a couple of seconds. Then I tried to use older kernel - 2.6.18-1.2798.fc6xen with the same result - once I just moved the mouse over gnome main menu the session was frozen. (I did not make so much observations yet but I think it is somehow related to mouse because when the session is waiting for the text input it will not get frozen so easily. In final I tried non-XEN kernel 2.6.19-1.2895.fc6 and it seems to be working fine. Does anybody notice the same behaviour? I would like to try GUI manager to setup some domains but I can't... (Well, VNC is probaby the option...) Thank you, Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: From John.Sanabria at ece.uprm.edu Mon Feb 12 14:51:13 2007 From: John.Sanabria at ece.uprm.edu (John.Sanabria at ece.uprm.edu) Date: Mon, 12 Feb 2007 10:51:13 -0400 (AST) Subject: [Fedora-xen] virt-install question... Message-ID: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> Hi, i'm using virt-install and it runs successfully with that command: virt-install -n xengrid2 --vcpus=1 -r 256 -s 4 -f /media/disk/iso/xengrid/xengrid2 -l ftp://mirrors.hpcf.upr.edu/pub/Mirrors/redhat/download.fedora.redhat.com/6/i386/os -p --nographics now, i have a question. What's the kernel image and initrd file used for virt-install in order to carry out the installation process? I need that information because i want use the cobbler/koan tools in order to provision virtual machines remotely, but when i submit the command koan --virt --server=136.145.116.114 --profile="xentemplate-profile" i got that: XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 184k freed Write protecting the kernel read-only data: 387k Red Hat nash version 5.1.19.0.2 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 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 appears the installation has crashed i'm using the kernel used by domain0 in my machine. thanks a lot for your comments. regards. (`'`'`'`'`) | | | | | | -----.. (()---- | | || (_ | | || | | | || | | | || /\ ..-- '--------'' /\ ||-'' \ / \ \ \// ,, \---. .---------. \./ |~| /__\ \ | ___|_________|__|""-.___ / || | | | | .-----' || | | | |CC.-----. | | | | '-----' | |-ABG | | From mdehaan at redhat.com Mon Feb 12 14:58:03 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 12 Feb 2007 09:58:03 -0500 Subject: [Fedora-xen] Re: [et-mgmt-tools] virt-install question... In-Reply-To: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> References: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> Message-ID: <45D0807B.7060207@redhat.com> John.Sanabria at ece.uprm.edu wrote: > Hi, > > i'm using virt-install and it runs successfully with that command: > > virt-install -n xengrid2 --vcpus=1 -r 256 -s 4 -f > /media/disk/iso/xengrid/xengrid2 -l > ftp://mirrors.hpcf.upr.edu/pub/Mirrors/redhat/download.fedora.redhat.com/6/i386/os > -p --nographics > > now, i have a question. What's the kernel image and initrd file used for > virt-install in order to carry out the installation process? I need that > information because i want use the cobbler/koan tools in order to > provision virtual machines remotely, but when i submit the command > > koan --virt --server=136.145.116.114 --profile="xentemplate-profile" > The kernel and initrd can be found in ftp://mirrors.hpcf.upr.edu/pub/Mirrors/redhat/download.fedora.redhat.com/6/i386/os/images/xen/ From berrange at redhat.com Mon Feb 12 14:59:58 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 12 Feb 2007 14:59:58 +0000 Subject: [Fedora-xen] Re: [et-mgmt-tools] virt-install question... In-Reply-To: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> References: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> Message-ID: <20070212145958.GD21671@redhat.com> On Mon, Feb 12, 2007 at 10:51:13AM -0400, John.Sanabria at ece.uprm.edu wrote: > Hi, > > i'm using virt-install and it runs successfully with that command: > > virt-install -n xengrid2 --vcpus=1 -r 256 -s 4 -f > /media/disk/iso/xengrid/xengrid2 -l > ftp://mirrors.hpcf.upr.edu/pub/Mirrors/redhat/download.fedora.redhat.com/6/i386/os > -p --nographics > > now, i have a question. What's the kernel image and initrd file used for > virt-install in order to carry out the installation process? When you supply a NFS/HTTP/FTP url to virt-install, it will take that URL and try to fetch the 2 files $URL/images/xen/vmlinuz and $URL/images/xen/initrd.img for the remote site. It saves those two files to /var/lib/xen/images and then boots the VM - the files are removed once the VM has started. > I need that > information because i want use the cobbler/koan tools in order to > provision virtual machines remotely, but when i submit the command You'll want to grab the vmlinuz & initrd.img files out of $URL/images/xen and give them to cobbler when setting up the profile. 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 John.Sanabria at ece.uprm.edu Mon Feb 12 15:46:53 2007 From: John.Sanabria at ece.uprm.edu (John.Sanabria at ece.uprm.edu) Date: Mon, 12 Feb 2007 11:46:53 -0400 (AST) Subject: [Fedora-xen] Re: [et-mgmt-tools] virt-install question... In-Reply-To: <20070212145958.GD21671@redhat.com> References: <36596.136.145.116.114.1171291873.squirrel@ece.uprm.edu> <20070212145958.GD21671@redhat.com> Message-ID: <33595.136.145.116.114.1171295213.squirrel@ece.uprm.edu> Thanks a lot, now it works! regards. > On Mon, Feb 12, 2007 at 10:51:13AM -0400, John.Sanabria at ece.uprm.edu > wrote: >> Hi, >> >> i'm using virt-install and it runs successfully with that command: >> >> virt-install -n xengrid2 --vcpus=1 -r 256 -s 4 -f >> /media/disk/iso/xengrid/xengrid2 -l >> ftp://mirrors.hpcf.upr.edu/pub/Mirrors/redhat/download.fedora.redhat.com/6/i386/os >> -p --nographics >> >> now, i have a question. What's the kernel image and initrd file used for >> virt-install in order to carry out the installation process? > > When you supply a NFS/HTTP/FTP url to virt-install, it will take that URL > and try to fetch the 2 files $URL/images/xen/vmlinuz and > $URL/images/xen/initrd.img > for the remote site. It saves those two files to /var/lib/xen/images and > then > boots the VM - the files are removed once the VM has started. > >> I need that >> information because i want use the cobbler/koan tools in order to >> provision virtual machines remotely, but when i submit the command > > You'll want to grab the vmlinuz & initrd.img files out of $URL/images/xen > and give them to cobbler when setting up the profile. > > 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 > -=| > > _______________________________________________ > et-mgmt-tools mailing list > et-mgmt-tools at redhat.com > https://www.redhat.com/mailman/listinfo/et-mgmt-tools > (`'`'`'`'`) | | | | | | -----.. (()---- | | || (_ | | || | | | || | | | || /\ ..-- '--------'' /\ ||-'' \ / \ \ \// ,, \---. .---------. \./ |~| /__\ \ | ___|_________|__|""-.___ / || | | | | .-----' || | | | |CC.-----. | | | | '-----' | |-ABG | | From pasik at iki.fi Mon Feb 12 17:12:23 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 12 Feb 2007 19:12:23 +0200 Subject: [Fedora-xen] HVM Performance and PV drivers In-Reply-To: <22DEE552-2012-49CA-ADE7-877D4D9DC3F9@saugus.k12.ca.us> References: <22DEE552-2012-49CA-ADE7-877D4D9DC3F9@saugus.k12.ca.us> Message-ID: <20070212171222.GR7120@edu.joroinen.fi> On Sat, Feb 10, 2007 at 09:45:07AM -0800, Jim Klein wrote: > >> > >>On Thursday 08 February 2007 10:08am, Jim Klein wrote: > >> > >>>Anyone been able to get the PV drivers from Xensource to work on an > >>>FC6 created HVM. Performance is rather sluggish, even on 64bit, > >>>without these, yet they don't seem to want to work here. Or, > >>>alternatively, is Red Hat working on their own? The HVM IO is really > >>>a bit too slow for most production use without them. > >>> > >> > >> > >>On Thu, 8 Feb 2007 11:26am, Lamont Peterson wrote: > >> > >>>I don't believe that you can do this. > >>> > >>>But, I'm wondering what OS you're trying to run on the HVM DomU. > >>>If it's > >>>Linux, use a paravirtualized DomU. You'll get much better > >>>performance > >>>(especially on things like I/O). > >>> > >>>HVM adds some emulation overhead and, thus, is slower than PV. > >>>HVM is only > >>>necessary to run an OS for which no paravirtualized kernel is > >>>available. > >>>-- > >>>Lamont Peterson > >>>Senior Instructor > >>>Guru Labs, L.C. [ http://www.GuruLabs.com/ ] > >>> > >> > >>All my Linux guests are PV (been running Xen in production for 7 > >>months - far longer > >>in testing.) I'm talking about Windows guests, which is why I > >>would need PV drivers to work. > >>Am running 64bit Dom0 to alleviate some of the pain, but I/O is > >>still too slow for anything > >>but lightweight applications. We're a RHEL shop, so would prefer > >>to use RHEL as a base over > >>XenSource Commercial, but it looks like I may have to go that > >>route if noone else is working > >>on PV drivers for Windows guests. > >> > >> > > > >Interesting point is the fact that Novell will ship Windows PV > >drivers in > >SLES 10 SP1 when it's released in May 2007.. > > > >-- Pasi > > > > If only SLES didn't suck - and Novell actually kept their promises. > But I could be wrong, maybe they'll be better now that they have > reliable partners like Microsoft... > "Novell and Intel plan to announce Monday software that improves the performance of Windows running atop the Xen virtualization software." http://news.com.com/Novell+offers+faster+virtualized+Windows/2100-1012_3-6158196.html I guess that means PV drivers for windows.. -- Pasi From jklein at saugus.k12.ca.us Mon Feb 12 17:57:36 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Mon, 12 Feb 2007 09:57:36 -0800 Subject: [Fedora-xen] HVM Performance and PV drivers In-Reply-To: <20070212171222.GR7120@edu.joroinen.fi> References: <22DEE552-2012-49CA-ADE7-877D4D9DC3F9@saugus.k12.ca.us> <20070212171222.GR7120@edu.joroinen.fi> Message-ID: <8EB55AA1-CC9D-48D6-A299-B1937D9E15EB@saugus.k12.ca.us> On Feb 12, 2007, at 9:12 AM, Pasi K?rkk?inen wrote: > On Sat, Feb 10, 2007 at 09:45:07AM -0800, Jim Klein wrote: >>>> >>>> On Thursday 08 February 2007 10:08am, Jim Klein wrote: >>>> >>>>> Anyone been able to get the PV drivers from Xensource to work >>>>> on an >>>>> FC6 created HVM. Performance is rather sluggish, even on 64bit, >>>>> without these, yet they don't seem to want to work here. Or, >>>>> alternatively, is Red Hat working on their own? The HVM IO is >>>>> really >>>>> a bit too slow for most production use without them. >>>>> >>>> >>>> >>>> On Thu, 8 Feb 2007 11:26am, Lamont Peterson wrote: >>>> >>>>> I don't believe that you can do this. >>>>> >>>>> But, I'm wondering what OS you're trying to run on the HVM DomU. >>>>> If it's >>>>> Linux, use a paravirtualized DomU. You'll get much better >>>>> performance >>>>> (especially on things like I/O). >>>>> >>>>> HVM adds some emulation overhead and, thus, is slower than PV. >>>>> HVM is only >>>>> necessary to run an OS for which no paravirtualized kernel is >>>>> available. >>>>> -- >>>>> Lamont Peterson >>>>> Senior Instructor >>>>> Guru Labs, L.C. [ http://www.GuruLabs.com/ ] >>>>> >>>> >>>> All my Linux guests are PV (been running Xen in production for 7 >>>> months - far longer >>>> in testing.) I'm talking about Windows guests, which is why I >>>> would need PV drivers to work. >>>> Am running 64bit Dom0 to alleviate some of the pain, but I/O is >>>> still too slow for anything >>>> but lightweight applications. We're a RHEL shop, so would prefer >>>> to use RHEL as a base over >>>> XenSource Commercial, but it looks like I may have to go that >>>> route if noone else is working >>>> on PV drivers for Windows guests. >>>> >>>> >>> >>> Interesting point is the fact that Novell will ship Windows PV >>> drivers in >>> SLES 10 SP1 when it's released in May 2007.. >>> >>> -- Pasi >>> >> >> If only SLES didn't suck - and Novell actually kept their promises. >> But I could be wrong, maybe they'll be better now that they have >> reliable partners like Microsoft... >> > > "Novell and Intel plan to announce Monday software that improves the > performance of Windows running atop the Xen virtualization software." > > http://news.com.com/Novell+offers+faster+virtualized+Windows/ > 2100-1012_3-6158196.html > > I guess that means PV drivers for windows.. > > -- Pasi Impressive prediction - hopefully, they will open source them so that all may benefit. -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdehaan at redhat.com Mon Feb 12 20:44:38 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 12 Feb 2007 15:44:38 -0500 Subject: [Fedora-xen] Strange video problem with Xen kernel and undocked laptop Message-ID: <45D0D1B6.3090600@redhat.com> Computer: IBM T43 kernel: 2.6.19-1.2895.fc6xen When docked, the laptop seems very happy, and I can use X/Gnome/etc fine ... undocked, the entire screen goes black right after logging in via gdm and I can't even switch to a tty. Booting a non-Xen kernel allows full use of graphics, and I can find no relevant enteries in /var/log/xen/* that indicate what might be going on. Any ideas or has anyone else experienced similar? --Michael From mdehaan at redhat.com Mon Feb 12 20:46:46 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 12 Feb 2007 15:46:46 -0500 Subject: [Fedora-xen] Re: Strange video problem with Xen kernel and undocked laptop In-Reply-To: <45D0D1B6.3090600@redhat.com> References: <45D0D1B6.3090600@redhat.com> Message-ID: <45D0D236.8090308@redhat.com> Michael DeHaan wrote: > Computer: IBM T43 > kernel: 2.6.19-1.2895.fc6xen > > When docked, the laptop seems very happy, and I can use X/Gnome/etc > fine ... undocked, the entire screen goes black right after logging in > via gdm and I can't even switch to a tty. Booting a non-Xen kernel > allows full use of graphics, and I can find no relevant enteries in > /var/log/xen/* that indicate what might be going on. > > Any ideas or has anyone else experienced similar? > > --Michael > > Graphics card, if it helps... [root at mdehaan service]# /sbin/lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300] From jandrejkovic at gmail.com Wed Feb 14 02:00:19 2007 From: jandrejkovic at gmail.com (Jan Andrejkovic) Date: Wed, 14 Feb 2007 02:00:19 +0000 Subject: [Fedora-xen] VNC and FreeNX disrupted is lost under XEN Dom0 kernel (mouse and keyboard are frozen) Message-ID: Hello, I thought there is a pobrlem between FreeNX and FC6 XEN Dom0 kerenel but now I discovered that there is also the same problem between VNC server and XEN enabled kernel (vnc-server-4.1.2-9.fc6 and 2.6.19-1.2895.fc6xen). Does anybody have the same problem? Do you know any workaround? Thank you, Jan 2007/2/12, Jan Andrejkovic : > > Hello FC XEN list, > > I already sent this e-mail to main Fedora mailing list but now I realised > it will be better to send it to XEN dist list: > > I have FC6 installed with latests patches (I use GNOME and XEN kernel > 2.6.19-1.2895.fc6xen) with all current updates. I installed FreeNX from > fedora extras and I tried to connect to this Dom0 kernel from Win XP client > ( 2.1.0-16). The connection was successful but after a few seconds I lost > the control using mouse and keyboard. I saw the screen, Gnome was just not > responding. Even when I tried to resume abandoned session I saw the dektop > again but I was not able to re-gain the control. > > Then I removed freenx downloaded from extras and I installed newest rpms > from nomachine web-site: > nxclient-2.1.0-11.i386.rpm > nxnode-2.1.0-15.i386.rpm > nxserver-2.1.0-18.i386.rpm > and for compatibility I had to add: > compat-libstdc++-296-2.96-138.i386.rpm (downloaded from rpmfind) > > However the result was the same - sesssion gets frozen after a couple of > seconds. > Then I tried to use older kernel - 2.6.18-1.2798.fc6xen with the same > result - once I just moved the mouse over gnome main menu the session was > frozen. > > (I did not make so much observations yet but I think it is somehow related > to mouse because when the session is waiting for the text input it will not > get frozen so easily. > > In final I tried non-XEN kernel 2.6.19-1.2895.fc6 and it seems to be > working fine. > > Does anybody notice the same behaviour? I would like to try GUI manager to > setup some domains but I can't... (Well, VNC is probaby the option...) > > Thank you, > > Jan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jandrejkovic at gmail.com Wed Feb 14 02:02:35 2007 From: jandrejkovic at gmail.com (Jan Andrejkovic) Date: Wed, 14 Feb 2007 02:02:35 +0000 Subject: [Fedora-xen] Re: VNC and FreeNX session disrupted under XEN Dom0 kernel (mouse and keyboard are frozen) Message-ID: Sorry for typo in the subject. Now it is ok... 2007/2/14, Jan Andrejkovic : > > Hello, > > I thought there is a pobrlem between FreeNX and FC6 XEN Dom0 kerenel but > now I discovered that there is also the same problem between VNC server and > XEN enabled kernel (vnc-server-4.1.2-9.fc6 and 2.6.19-1.2895.fc6xen ). > Does anybody have the same problem? > > Do you know any workaround? > > Thank you, > > Jan > > 2007/2/12, Jan Andrejkovic : > > > > Hello FC XEN list, > > > > I already sent this e-mail to main Fedora mailing list but now I > > realised it will be better to send it to XEN dist list: > > > > I have FC6 installed with latests patches (I use GNOME and XEN kernel > > 2.6.19-1.2895.fc6xen) with all current updates. I installed FreeNX from > > fedora extras and I tried to connect to this Dom0 kernel from Win XP client > > ( 2.1.0-16). The connection was successful but after a few seconds I > > lost the control using mouse and keyboard. I saw the screen, Gnome was just > > not responding. Even when I tried to resume abandoned session I saw the > > dektop again but I was not able to re-gain the control. > > > > Then I removed freenx downloaded from extras and I installed newest rpms > > from nomachine web-site: > > nxclient-2.1.0-11.i386.rpm > > nxnode-2.1.0-15.i386.rpm > > nxserver-2.1.0-18.i386.rpm > > and for compatibility I had to add: > > compat-libstdc++-296-2.96-138.i386.rpm (downloaded from rpmfind) > > > > However the result was the same - sesssion gets frozen after a couple of > > seconds. > > Then I tried to use older kernel - 2.6.18-1.2798.fc6xen with the same > > result - once I just moved the mouse over gnome main menu the session was > > frozen. > > > > (I did not make so much observations yet but I think it is somehow > > related to mouse because when the session is waiting for the text input it > > will not get frozen so easily. > > > > In final I tried non-XEN kernel 2.6.19-1.2895.fc6 and it seems to be > > working fine. > > > > Does anybody notice the same behaviour? I would like to try GUI manager > > to setup some domains but I can't... (Well, VNC is probaby the option...) > > > > Thank you, > > > > Jan > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From royalties1 at bol.com.br Wed Feb 14 18:59:27 2007 From: royalties1 at bol.com.br (royalties1) Date: Wed, 14 Feb 2007 16:59:27 -0200 Subject: [Fedora-xen] Error Install Win2003 XEN Opensource 3.0 Message-ID: Good Afternoon, I'm Alex Nogueira and have a problem with xen 3.0. When I go to install appears the message: xm create /etc/xen/win2003.hvm Using config file "/etc/xen/win2003.hvm". Error: HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS? It follows below the data of xen [root at localhost /]# xm info host : localhost.localdomain release : 2.6.19-1.2895.fc6xen version : #1 SMP Wed Jan 10 19:47:12 EST 2007 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:00000000:00000000:00000180:0000441d total_memory : 2046 free_memory : 127 xen_major : 3 xen_minor : 0 xen_extra : .3-0-1.2895.fc6 xen_caps : xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-51) cc_compile_by : brewbuilder cc_compile_domain : redhat.com cc_compile_date : Wed Jan 10 18:29:56 EST 2007 xend_config_format : 2 Thanks , From itamar at ispbrasil.com.br Wed Feb 14 19:26:55 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 14 Feb 2007 17:26:55 -0200 Subject: [Fedora-xen] Error Install Win2003 XEN Opensource 3.0 References: Message-ID: <003401c7506e$1959f920$fe0fa8c0@ispbrasil> para rodar o windows no xen voce precisa ter um processador que suporte isto. cat /proc/cpuinfo|grep vmx -------------------- 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: "royalties1" To: "fedora-xen" Sent: Wednesday, February 14, 2007 4:59 PM Subject: [Fedora-xen] Error Install Win2003 XEN Opensource 3.0 > Good Afternoon, > > I'm Alex Nogueira and have a problem with xen 3.0. > > When I go to install appears the message: > > xm create /etc/xen/win2003.hvm > Using config file "/etc/xen/win2003.hvm". > Error: HVM guest support is unavailable: is VT/AMD-V supported by your CPU > and enabled in your BIOS? > > > It follows below the data of xen > [root at localhost /]# xm info > host : localhost.localdomain > release : 2.6.19-1.2895.fc6xen > version : #1 SMP Wed Jan 10 19:47:12 EST 2007 > machine : i686 > nr_cpus : 2 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2992 > hw_caps : bfebfbff:00000000:00000000:00000180:0000441d > total_memory : 2046 > free_memory : 127 > xen_major : 3 > xen_minor : 0 > xen_extra : .3-0-1.2895.fc6 > xen_caps : xen-3.0-x86_32p > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-51) > cc_compile_by : brewbuilder > cc_compile_domain : redhat.com > cc_compile_date : Wed Jan 10 18:29:56 EST 2007 > xend_config_format : 2 > > Thanks , > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From acathrow at redhat.com Wed Feb 14 20:20:56 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Wed, 14 Feb 2007 15:20:56 -0500 Subject: [Fedora-xen] Error Install Win2003 XEN Opensource 3.0 In-Reply-To: <003401c7506e$1959f920$fe0fa8c0@ispbrasil> References: <003401c7506e$1959f920$fe0fa8c0@ispbrasil> Message-ID: <1171484456.3689.54.camel@aic-laptop-5.cathrow.org> Also look for "svm" which indicates the AMD virtualization extensions are available. On Wed, 2007-02-14 at 17:26 -0200, Itamar Reis Peixoto wrote: > para rodar o windows no xen voce precisa ter um processador que suporte > isto. > > cat /proc/cpuinfo|grep vmx > > -------------------- > > 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: "royalties1" > To: "fedora-xen" > Sent: Wednesday, February 14, 2007 4:59 PM > Subject: [Fedora-xen] Error Install Win2003 XEN Opensource 3.0 > > > > Good Afternoon, > > > > I'm Alex Nogueira and have a problem with xen 3.0. > > > > When I go to install appears the message: > > > > xm create /etc/xen/win2003.hvm > > Using config file "/etc/xen/win2003.hvm". > > Error: HVM guest support is unavailable: is VT/AMD-V supported by your CPU > > and enabled in your BIOS? > > > > > > It follows below the data of xen > > [root at localhost /]# xm info > > host : localhost.localdomain > > release : 2.6.19-1.2895.fc6xen > > version : #1 SMP Wed Jan 10 19:47:12 EST 2007 > > machine : i686 > > nr_cpus : 2 > > nr_nodes : 1 > > sockets_per_node : 1 > > cores_per_socket : 1 > > threads_per_core : 2 > > cpu_mhz : 2992 > > hw_caps : bfebfbff:00000000:00000000:00000180:0000441d > > total_memory : 2046 > > free_memory : 127 > > xen_major : 3 > > xen_minor : 0 > > xen_extra : .3-0-1.2895.fc6 > > xen_caps : xen-3.0-x86_32p > > xen_pagesize : 4096 > > platform_params : virt_start=0xf5800000 > > xen_changeset : unavailable > > cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-51) > > cc_compile_by : brewbuilder > > cc_compile_domain : redhat.com > > cc_compile_date : Wed Jan 10 18:29:56 EST 2007 > > xend_config_format : 2 > > > > Thanks , > > > > > > -- > > 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 -- 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 tleasure at gmail.com Thu Feb 15 04:22:13 2007 From: tleasure at gmail.com (Tom Leasure) Date: Wed, 14 Feb 2007 23:22:13 -0500 Subject: [Fedora-xen] Xen networking Message-ID: <81844dda0702142022n496e8988qbe88fb1e9239677d@mail.gmail.com> Hello all - I have a guest domain running that I want to run a web server on (Both are FC5). The guest has its own IP and I can ssh into from anywhere. It is able to download anything from the network/Internet However, I can't get to it via port 80 from the browser. The network firewall has port 80 open for that IP. I have apache setup and configured properly. Do I need to configure something with domain0 in order for web traffic over to port 80 to reach the guest domain? I suppose port 22 for SSH was configured by default? Any help would be appreciated. Thanks T -------------- next part -------------- An HTML attachment was scrubbed... URL: From jprats at cesca.es Thu Feb 15 09:19:34 2007 From: jprats at cesca.es (Jordi Prats) Date: Thu, 15 Feb 2007 10:19:34 +0100 Subject: [Fedora-xen] destroydevice In-Reply-To: <20070130220539.GP18642@redhat.com> References: <45BFB880.1060409@cesca.es> <20070130213652.GN18642@redhat.com> <45BFC0FD.3060503@cesca.es> <20070130220539.GP18642@redhat.com> Message-ID: <45D425A6.9010102@cesca.es> Hi again, It seems to me that really are a problem here. I've created a new virtual machine, but after shuting down it I can't create it again. The error reported is: [root at inf16 ssh]# xm create /etc/xen/granit.cfg -c Using config file "/etc/xen/granit.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) Thanks, Jordi Daniel P. Berrange wrote: > On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote: > >> Ok, thank you! >> >> How long will take for the next release? >> > > Probably a few days before it goes to updates-testing, so don't > expect it to go to updates for at least a week > > >> On the other hand, I can't ignore that error because I can't create any >> virtual machine, so Xen does nothing. On redhat 5 b2 it happens the >> same. I've changed my servers to FC6 because of this. >> > > Urm - read my explanation below again.... > > The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem > is *NOT* what is causing your guest to fail. It is merely obscuring the > underlying failure - an updated RPM will remove up the 'destroyDevice' > misleading message, but it won't magically make your guest work again. > > The fundamental problem is a configuration issue with your guest's virtual > disk or networking. Once you fix the config problem, the guest will work > just fine, with or without an updated RPM for the 'destroyDevice' issue > > >> Daniel P. Berrange wrote: >> >>> On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote: >>> >>>> Hi, >>>> It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm >>>> tool: creating a new VM it aborts showing this error: >>>> >>>> [root at inf16 ~]# xm create /etc/xen/rata.cfg >>>> Using config file "/etc/xen/rata.cfg". >>>> Error: destroyDevice() takes exactly 3 arguments (2 given) >>>> [root at inf16 ~]# >>>> >>>> Anyone knows what is causing this? On the xen-users list there's some >>>> other messages related to this isue (one mine). Mats Petersson say that >>>> this may be causes by a backport. >>>> >>> Its a bug in one of the other patches we applied to the Xen RPM. I'll fix >>> it in the next release. >>> >>> >>>> There's something broken on the package? There's any easy workarround? >>>> >>> The error above isn't actually the root cause of your problems. What's >>> happened is that the hotplug scripts for your domain failed to complete >>> for some reason. Then when XenD is cleaning up from that failure, we >>> hit the bug above. So wrt to debugging your actual problems, ignore the >>> error message above. Instead look for a mis-configuration in either your >>> virtual network card or virtual disk config params. >>> > > > Dan. > -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From John.Sanabria at ece.uprm.edu Thu Feb 15 13:55:02 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Thu, 15 Feb 2007 09:55:02 -0400 (AST) Subject: [Fedora-xen] strange behavior. Message-ID: <45954.136.145.116.114.1171547702.squirrel@ece.uprm.edu> Hi, i'm compiling gt4 (Globus Toolkit 4.0.3) inside a virtual machine. That is the commands that i had executed: # make >& installer.log ^Z # bg # tail -f installer.log time later, the make stop to do its job. # jobs [1]+ Stopped make >&installer.log then, manually i have to re-run the command, with "fg". The question is: Why programs (all or some of them) stop suddenly with no apparent reason? thanks a lot, http://ece.uprm.edu/~s047267 From jklein at saugus.k12.ca.us Fri Feb 16 00:22:53 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Thu, 15 Feb 2007 16:22:53 -0800 (PST) Subject: [Fedora-xen] Virt-manager and Migration Message-ID: <9975676.1466171171585373917.JavaMail.root@do8> When I migrate a PV from one box to another, I lose access to the virtual console in virt-manager, even if i migrate it back to the original box. DomU is working fine, just no vfb console access (although xm console still works.) Any ideas out there for a fix? -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" -------------- next part -------------- An HTML attachment was scrubbed... URL: From xenguy at gmail.com Fri Feb 16 07:19:50 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Fri, 16 Feb 2007 12:49:50 +0530 Subject: [Fedora-xen] Virt-manager and Migration In-Reply-To: <9975676.1466171171585373917.JavaMail.root@do8> References: <9975676.1466171171585373917.JavaMail.root@do8> Message-ID: <45D55B16.7010206@gmail.com> Better you report it at https://bugzilla.redhat.com. Jim Klein wrote: > When I migrate a PV from one box to another, I lose access to the > virtual console in virt-manager, even if i migrate it back to the > original box. DomU is working fine, just no vfb console access > (although xm console still works.) Any ideas out there for a fix? > > -- > Jim Klein > Director Information Services & Technology > LPIC1, CNA/CNE 4-6, RHCT/RHCE > Saugus Union School District > http://www.saugus.k12.ca.us > > "Finis Origine Pendet" > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From kadafax at gmail.com Fri Feb 16 11:23:50 2007 From: kadafax at gmail.com (kadafax) Date: Fri, 16 Feb 2007 12:23:50 +0100 Subject: [Fedora-xen] memory strangeness Message-ID: <45D59446.40805@gmail.com> Hi list, I am a happy user of xen'ed fedora 6. It is working really well (fc6 domU on fc6 dom0). I have recently added memory to the server (Dell Power Edge 2850, latest bios A06) from 2GB to 4GB. And there is something strange with the total memory report from the OS: [root at host ~]# uname -a Linux host 2.6.19-1.2911.fc6xen #1 SMP Sat Feb 10 15:34:39 EST 2007 x86_64 x86_64 x86_64 GNU/Linux [root at host ~]# cat /proc/meminfo | grep MemTotal MemTotal: 3584000 kB [root at krypton ~]# xm top ... Mem: 4193664k total, 4184456k used, 9208k free CPUs: 4 @ 2992MHz ... Why does it return different value with 'cat /proc/meminfo' and 'xm top'. Should I worry about this? Thanks, Kfx. From bloch at verdurin.com Sun Feb 18 15:53:24 2007 From: bloch at verdurin.com (bloch at verdurin.com) Date: Sun, 18 Feb 2007 15:53:24 +0000 Subject: [Fedora-xen] Unable to boot properly with Xen kernel Message-ID: <20070218155324.GB19449@bloch.config> I'm still unable to boot successfully with the latest Xen kernel on a laptop with a T7200 CPU and the following hardware: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) 07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 15) 09:04.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 09:04.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 09:04.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) The relevant bug report is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220134 The kernel does boot but the system becomes unusable as services are started. From edamaral at nortel.com Mon Feb 19 00:14:10 2007 From: edamaral at nortel.com (Eduardo Amaral) Date: Sun, 18 Feb 2007 19:14:10 -0500 Subject: [Fedora-xen] Problems with starting xen guest (DomU) Message-ID: <54A70491E004F44CA31355B49244588C03209C1F@zrtphxm2.corp.nortel.com> Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo Started domain fedora.fc6 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx -------------- next part -------------- An HTML attachment was scrubbed... URL: From itamar at ispbrasil.com.br Mon Feb 19 00:28:46 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sun, 18 Feb 2007 22:28:46 -0200 Subject: [Fedora-xen] Problems with starting xen guest (DomU) References: <54A70491E004F44CA31355B49244588C03209C1F@zrtphxm2.corp.nortel.com> Message-ID: <001d01c753bc$ee02b3a0$fe0fa8c0@ispbrasil> Problems with starting xen guest (DomU)where are your domU config ? have you created a initrd form domU with xenblk module ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo Started domain fedora.fc6 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ------------------------------------------------------------------------------ -- 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 edamaral at nortel.com Mon Feb 19 00:46:21 2007 From: edamaral at nortel.com (Eduardo Amaral) Date: Sun, 18 Feb 2007 19:46:21 -0500 Subject: [Fedora-xen] Problems with starting xen guest (DomU) In-Reply-To: <001d01c753bc$ee02b3a0$fe0fa8c0@ispbrasil> Message-ID: <54A70491E004F44CA31355B49244588C03209C2C@zrtphxm2.corp.nortel.com> ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo Started domain fedora.fc6 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ________________________________ -- 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 daniel at velotype.nl Mon Feb 19 00:51:07 2007 From: daniel at velotype.nl (Daniel Tuijnman) Date: Mon, 19 Feb 2007 01:51:07 +0100 Subject: [Fedora-xen] Problem renaming Logical Volumes Message-ID: <20070219005107.GA6898@velotype.nl> Hi all, Sorry if this is not really a Xen problem, but it is something which you wouldn't want to do if you were not playing with virtual machines... I had one small VM set up to use as a base for other (paravirtualized) VM's. (both dom0 and the domU's in question are Fedora Core 6 installs). I gave it a LV, say /dev/VG_domU/base, as its (only) disk /dev/xvda, and partitioned it during install as follows: /dev/xvda1 /boot filesystem /dev/xvda2 PV for VG VG_base, with LV's swap for swap root as / filesystem which is the way I usually partition my Linux installs (except that I usually create LV's for /usr, /var, /tmp, /home etc.) Then in dom0, I created another LV /dev/VG_domU/derived, did a dd from /dev/VG_domU/base to /dev/VG_domU/derived, et voila, I have another VM. But this other VM has on its disk a VG with the same name, so I wanted to rename the VG: you never know if you want to access both VG's at the same time. So I used kpartx to make it visible: # kpartx -a /dev/VG_domU/derived # vgscan # vgrename /dev/VG_base /VG_derived Then, of course, the name of the VG are mentioned a number of times: - in /boot/grub/grub.conf the name of the root partition - in /etc/fstab - and in /init on /boot/initrd...img But after that, the cloned VM with the renamed VG wouldn't boot - kernel panic. Does someone has an idea what I'm missing here? Greetings, Daniel -- Dani?l Tuijnman phone: +31-24-377.7329 De Voorstenkamp 19-59 mobile: +31-6-4611.4589 NL-6545 GR Nijmegen fax: +31-24-373.3632 ======================================================================== The tree of liberty must be refreshed from time to time with the blood of patriots & tyrants. Thomas Jefferson ======================================================================== From itamar at ispbrasil.com.br Mon Feb 19 04:11:22 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Mon, 19 Feb 2007 02:11:22 -0200 Subject: [Fedora-xen] Problems with starting xen guest (DomU) References: <54A70491E004F44CA31355B49244588C03209C2C@zrtphxm2.corp.nortel.com> Message-ID: <001c01c753dc$067fd560$fe0fa8c0@ispbrasil> Problems with starting xen guest (DomU)mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ------------------------------------------------------------------------------ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo Started domain fedora.fc6 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ---------------------------------------------------------------------------- -- 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 adrian.revill at shazamteam.net Mon Feb 19 11:19:42 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Mon, 19 Feb 2007 11:19:42 +0000 Subject: [Fedora-xen] Guest install very slow Message-ID: <45D987CE.7090103@shazamteam.net> Hi, I have just done a clean install of FC6 with visualization on a single cpu box (AMD 1.7+XP 1.5G ram) The performance of the box running FC6 is fine, all the windows and menus open quickly and smoothly. I followed the FedoraXenQuickstartFC6 and all seems to work perfectly except the guest seems to run very slowly. The Virtual machine manager shows about 0.1% cpu use for the new guest and Domain-0 stays about 4% I have extracted the FC6 isos onto the same box and created a nfs mount point for the source. I am using /var/lib/xen/images/testOne as the directory for the disk path with a 3G limit I set 512Mb ram and 1CPU The boot seems quite quick, and anaconda starts, all the selection of the language and keyboard seems ok too. Then it sits for about 15mins with Running Anaconda at the bottom of the screen, then starts the x window. It takes about 1/2 hr for a X cursor to appear, that will follow mouse movement, but takes a couple of seconds to catch up. I never have seen anything more. Just a black window, even after leaving it all weekend. when i run virsh list it always says the testOne domain is blocked. I have looked in all the log files and the console, but there are no errors. Anyone got any ideas? as i guess its not meant to be this slow. From asraikhn at gmail.com Mon Feb 19 11:52:31 2007 From: asraikhn at gmail.com (Asrai khn) Date: Mon, 19 Feb 2007 16:52:31 +0500 Subject: [Fedora-xen] Particular domU boots before anyother domU on the same host Message-ID: <5f0f8dba0702190352y3cc93aa9w50b097ca62bbcd4e@mail.gmail.com> Hi, I am wondering how to make sure that a particular domU boots before anyother domU on the same host. For example this particular domU providing some samba shares to other domU. Apparently if the dom0 reboots we have to 'mount' the shares on some domU(s) which boots before domU which providing these shares. Any help in this regards will be highly appreciated. Thanks. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Mon Feb 19 14:04:41 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 19 Feb 2007 14:04:41 +0000 Subject: [Fedora-xen] Particular domU boots before anyother domU on the same host In-Reply-To: <5f0f8dba0702190352y3cc93aa9w50b097ca62bbcd4e@mail.gmail.com> References: <5f0f8dba0702190352y3cc93aa9w50b097ca62bbcd4e@mail.gmail.com> Message-ID: <20070219140441.GJ31525@redhat.com> On Mon, Feb 19, 2007 at 04:52:31PM +0500, Asrai khn wrote: > Hi, > > I am wondering how to make sure that a particular domU boots before anyother > domU on the same host. For example this particular domU providing some samba > shares to other domU. Apparently if the dom0 reboots we have to 'mount' the > shares on some domU(s) which boots before domU which providing these > shares. The xendomains init script which is responsible for starting domains at boot time is pretty simplisitic. It simply does a wildcard on the files in /etc/xen/auto/* or saved VMs in /var/lib/xen/save/* so domains will get started in alphabetical order based on their name. You shouldn't rely on this behaviour though, because the way domains are autostarted has changed in Xen 3.0.4 which will be in Fedora 7 and I can't guarentee the startup ordering will be the same So if you want to ensure domains start ina particular order, I'd not use the xendomains script at all. Instead just put a bunch of 'xm create' statements in /etc/rc.d/rc.local to follow your desired ordering exactly. 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 asraikhn at gmail.com Mon Feb 19 14:31:08 2007 From: asraikhn at gmail.com (Asrai khn) Date: Mon, 19 Feb 2007 19:31:08 +0500 Subject: [Fedora-xen] Particular domU boots before anyother domU on the same host In-Reply-To: <20070219140441.GJ31525@redhat.com> References: <5f0f8dba0702190352y3cc93aa9w50b097ca62bbcd4e@mail.gmail.com> <20070219140441.GJ31525@redhat.com> Message-ID: <5f0f8dba0702190631g2f1062afi8f587aab2a2ddd8@mail.gmail.com> Hi Dan On 2/19/07, Daniel P. Berrange wrote: > > > The xendomains init script which is responsible for starting domains at > boot time is pretty simplisitic. It simply does a wildcard on the files in > /etc/xen/auto/* or saved VMs in /var/lib/xen/save/* so domains will get > started in alphabetical order based on their name. You shouldn't rely on > this behaviour though, because the way domains are autostarted has > changed > in Xen 3.0.4 which will be in Fedora 7 and I can't guarentee the startup > ordering will be the same > > So if you want to ensure domains start ina particular order, I'd not use > the xendomains script at all. Instead just put a bunch of 'xm create' > statements in /etc/rc.d/rc.local to follow your desired ordering exactly. Alright then we must go for /etc/rc.d/rc.local approach, however I wonders why xen uses the alphabetic approach when starts domains its kinda weird :) Thanks. Askar 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 -=| > -------------- next part -------------- An HTML attachment was scrubbed... URL: From asraikhn at gmail.com Mon Feb 19 15:35:23 2007 From: asraikhn at gmail.com (Asrai khn) Date: Mon, 19 Feb 2007 20:35:23 +0500 Subject: [Fedora-xen] Particular domU boots before anyother domU on the same host In-Reply-To: <20070219140441.GJ31525@redhat.com> References: <5f0f8dba0702190352y3cc93aa9w50b097ca62bbcd4e@mail.gmail.com> <20070219140441.GJ31525@redhat.com> Message-ID: <5f0f8dba0702190735j2d27c63cy9e1dcc7d5c926889@mail.gmail.com> On 2/19/07, Daniel P. Berrange wrote: > > > So if you want to ensure domains start ina particular order, I'd not use > the xendomains script at all. Instead just put a bunch of 'xm create' > statements in /etc/rc.d/rc.local to follow your desired ordering exactly. By this you mean to stop 'xendomains' service to run when system (dom0) boots, and putting 'xm create blah.cfg' in rc.local right? Thanks. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From edamaral at nortel.com Tue Feb 20 01:08:56 2007 From: edamaral at nortel.com (Eduardo Amaral) Date: Mon, 19 Feb 2007 20:08:56 -0500 Subject: [Fedora-xen] Problems with starting xen guest (DomU) Message-ID: <54A70491E004F44CA31355B49244588C032423CC@zrtphxm2.corp.nortel.com> Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstory-l at 2006.revelstone.com Tue Feb 20 20:17:17 2007 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 20 Feb 2007 15:17:17 -0500 Subject: [Fedora-xen] Problem renaming Logical Volumes In-Reply-To: <20070219005107.GA6898@velotype.nl> References: <20070219005107.GA6898@velotype.nl> Message-ID: <200702202102.l1KL2Hcq016937@mx1.redhat.com> On Mon, 19 Feb 2007 01:51:07 +0100 Daniel wrote: DT> Then in dom0, I created another LV /dev/VG_domU/derived, did a dd from DT> /dev/VG_domU/base to /dev/VG_domU/derived, et voila, I have another VM. DT> But this other VM has on its disk a VG with the same name, so I wanted to DT> rename the VG: you never know if you want to access both VG's at the same DT> time. I asked this same question back in November, and never got a response. If you figure it out, please come back and share what you find! From itamar at ispbrasil.com.br Wed Feb 21 15:13:52 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 21 Feb 2007 13:13:52 -0200 Subject: [Fedora-xen] Problems with starting xen guest (DomU) References: <54A70491E004F44CA31355B49244588C032423CC@zrtphxm2.corp.nortel.com> Message-ID: <032d01c755ca$e7105330$fe0fa8c0@ispbrasil> Problems with starting xen guest (DomU)Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" hda2 seems to be a swap, your domU never boot. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Monday, February 19, 2007 11:08 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! ------------------------------------------------------------------------------ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ---------------------------------------------------------------------------- From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From polytropolis at gmail.com Wed Feb 21 22:31:04 2007 From: polytropolis at gmail.com (Claus Reheis) Date: Wed, 21 Feb 2007 23:31:04 +0100 Subject: [Fedora-xen] XEN Problem with root device Message-ID: <1172097064.4079.19.camel@workstation> Hi all! At first I have to admit that I am very inexperienced in using XEN! What I try to do is get OpenSuse 10.2 working on my FC6 Station. To do that I did the following steps: 1)Installed the XEN Kernel: 2.6.19-1.2911.fc6xen 2)Installed OpenSuse 10.2 on my girlfriends Laptop 3)made a complete image of the installation and put it in my home: /home/user/opensuse102xen.img 4)created an suse.xen.cfg: kernel = "/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory = 512 name = "opensuse102" vif = [''] #nics = 1 #dhcp = "dhcp" disk = disk = ['file:/home/rehcla/opensuse102xen.img,xvda,w'] root = "/dev/xvda ro" 5)did edit the /etc/fstab in the Image: /dev/xvda / ext3 acl,user_xattr 1 1 #/dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 #/dev/hda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 When I try to start Xen with: "xm create opensuse102 -c suse.xen.cfg" I get this: Using config file "./suse.xen.cfg". Started domain opensuse102 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2166k kernel code, 11200k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8489.82 BogoMIPS (lpj=16979653) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172096781.555:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2166k kernel code, 11200k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8489.82 BogoMIPS (lpj=16979653) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172096781.555:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda" 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) Can some help me? Thanks! Claus Reheis -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From xenguy at gmail.com Thu Feb 22 07:24:16 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Thu, 22 Feb 2007 12:54:16 +0530 Subject: [Fedora-xen] XEN Problem with root device In-Reply-To: <1172097064.4079.19.camel@workstation> References: <1172097064.4079.19.camel@workstation> Message-ID: <45DD4520.1050601@gmail.com> You need to create an initrd image with --with=xennet --preload=xenblk options and specify that using "ramdisk = " in the configuration file for guest. Claus Reheis wrote: > Hi all! > > At first I have to admit that I am very inexperienced in using XEN! > What I try to do is get OpenSuse 10.2 working on my FC6 Station. > To do that I did the following steps: > > 1)Installed the XEN Kernel: 2.6.19-1.2911.fc6xen > > 2)Installed OpenSuse 10.2 on my girlfriends Laptop > > 3)made a complete image of the installation and put it in my home: > > /home/user/opensuse102xen.img > > 4)created an suse.xen.cfg: > > kernel = "/boot/vmlinuz-2.6.19-1.2895.fc6xen" > memory = 512 > name = "opensuse102" > vif = [''] > #nics = 1 > #dhcp = "dhcp" > disk = disk = ['file:/home/rehcla/opensuse102xen.img,xvda,w'] > root = "/dev/xvda ro" > > 5)did edit the /etc/fstab in the Image: > > > /dev/xvda / ext3 acl,user_xattr > 1 1 > #/dev/hda1 /windows/C ntfs > ro,users,gid=users,umask=0002,nls=utf8 0 0 > #/dev/hda2 swap swap defaults > 0 0 > proc /proc proc defaults > 0 0 > sysfs /sys sysfs noauto > 0 0 > debugfs /sys/kernel/debug debugfs noauto > 0 0 > usbfs /proc/bus/usb usbfs noauto > 0 0 > devpts /dev/pts devpts mode=0620,gid=5 > 0 0 > > > When I try to start Xen with: > > "xm create opensuse102 -c suse.xen.cfg" > > I get this: > > > Using config file "./suse.xen.cfg". > Started domain opensuse102 > Linux version 2.6.19-1.2895.fc6xen > (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 > (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000020800000 (usable) > 0MB HIGHMEM available. > 520MB LOWMEM available. > NX (Execute Disable) protection: active > Zone PFN ranges: > DMA 0 -> 133120 > Normal 133120 -> 133120 > HighMem 133120 -> 133120 > early_node_map[1] active PFN ranges > 0: 0 -> 133120 > ACPI in unprivileged domain disabled > Built 1 zonelists. Total pages: 132080 > Kernel command line: root=/dev/xvda ro > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 > PID hash table entries: 4096 (order: 12, 16384 bytes) > Xen reported: 3391.494 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 > Memory: 512768k/532480k available (2166k kernel code, 11200k reserved, > 1100k data, 184k init, 0k highmem) > virtual kernel memory layout: > fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) > pkmap : 0xf5000000 - 0xf5200000 (2048 kB) > vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) > lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) > .init : 0xc078e000 - 0xc07bc000 ( 184 kB) > .data : 0xc061da2c - 0xc0730bf4 (1100 kB) > .text : 0xc0400000 - 0xc061da2c (2166 kB) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 8489.82 BogoMIPS > (lpj=16979653) > 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: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 2048K > 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 > PCI: Fatal: No config space access function found > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 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(1172096781.555:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > ksign: Installing public key data > Loading keyring > - Added public key A803A00FB8A89D68 > - User ID: Red Hat, Inc. (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Linux version 2.6.19-1.2895.fc6xen > (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 > (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000020800000 (usable) > 0MB HIGHMEM available. > 520MB LOWMEM available. > NX (Execute Disable) protection: active > Zone PFN ranges: > DMA 0 -> 133120 > Normal 133120 -> 133120 > HighMem 133120 -> 133120 > early_node_map[1] active PFN ranges > 0: 0 -> 133120 > ACPI in unprivileged domain disabled > Built 1 zonelists. Total pages: 132080 > Kernel command line: root=/dev/xvda ro > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 > PID hash table entries: 4096 (order: 12, 16384 bytes) > Xen reported: 3391.494 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 > Memory: 512768k/532480k available (2166k kernel code, 11200k reserved, > 1100k data, 184k init, 0k highmem) > virtual kernel memory layout: > fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) > pkmap : 0xf5000000 - 0xf5200000 (2048 kB) > vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) > lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) > .init : 0xc078e000 - 0xc07bc000 ( 184 kB) > .data : 0xc061da2c - 0xc0730bf4 (1100 kB) > .text : 0xc0400000 - 0xc061da2c (2166 kB) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 8489.82 BogoMIPS > (lpj=16979653) > 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: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 2048K > 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 > PCI: Fatal: No config space access function found > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 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(1172096781.555:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > ksign: Installing public key data > Loading keyring > - Added public key A803A00FB8A89D68 > - User ID: Red Hat, Inc. (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new interface driver libusual > usbcore: registered new interface driver hiddev > usbcore: registered new interface driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > TCP bic registered > Initializing XFRM netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "xvda" 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) > > > Can some help me? > > Thanks! > > Claus Reheis > > > > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From thrall.mail.list at gmail.com Thu Feb 22 12:30:26 2007 From: thrall.mail.list at gmail.com (Nadeem Shahbaz) Date: Thu, 22 Feb 2007 17:30:26 +0500 Subject: [Fedora-xen] xen time sync problem Message-ID: Hi, I am facing problem in sync time within DomU with Dom0. After gone through mailing lists, I have set /proc/sys/xen/independent_wallclock to 0. But still DomU are not syncing their time :-S Machine using kernel-xen-2.6.19-1.2911.fc6 xen-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 Please advice to solve this weird problem, Thanks From polytropolis at gmail.com Thu Feb 22 18:06:36 2007 From: polytropolis at gmail.com (Claus Reheis) Date: Thu, 22 Feb 2007 19:06:36 +0100 Subject: [Fedora-xen] XEN Kernel Panic [update] Message-ID: <1172167596.5243.5.camel@workstation> Hi all! At first I have to admit that I am very inexperienced in using XEN! What I try to do is get OpenSuse 10.2 working on my FC6 Station. To do that I did the following steps: 1)Installed the XEN Kernel: 2.6.19-1.2911.fc6xen 2)Installed OpenSuse 10.2 on my girlfriends Laptop 3)made a complete image of the installation and put it in my home: /home/user/opensuse102xen.img 4)created an suse.xen.cfg: kernel = "/boot/vmlinuz-2.6.19-1.2911.fc6xen" ramdisk= "/boot/initrd-2.6.19-1.2911.fc6xen.img" memory = 512 name = "opensuse102" vif = [''] #nics = 1 #dhcp = "dhcp" disk = ['file:/home/rehcla/opensuse102xen.img,xvda,w'] root = "/dev/xvda ro" 5)did edit the /etc/fstab in the Image: /dev/xvda / ext3 acl,user_xattr 1 1 #/dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 #/dev/hda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 ~ When I try to start Xen with: "xm create opensuse102 -c suse.xen.cfg" I get this: Using config file "./suse.xen.cfg". Started domain opensuse102 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.492 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 507648k/532480k available (2168k kernel code, 16360k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8488.39 BogoMIPS (lpj=16976791) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 5155k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172157593.055:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.492 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 507648k/532480k available (2168k kernel code, 16360k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8488.39 BogoMIPS (lpj=16976791) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 5155k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172157593.055:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 387k Red Hat nash version 5.1.19.0.2 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 ata_piix.ko module Loading dm-mod.ko module device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) 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... No volume groups found Activating logical volumes Volume group "VolGroup00" not found 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! Can some help me? Thanks! Claus Reheis -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From master at bradleyland.com Thu Feb 22 22:30:00 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Thu, 22 Feb 2007 14:30:00 -0800 (PST) Subject: [Fedora-xen] XEN Kernel Panic [update] In-Reply-To: <1172167596.5243.5.camel@workstation> References: <1172167596.5243.5.camel@workstation> Message-ID: <3207.192.168.2.92.1172183400.squirrel@www.bradleyland.com> Hi Claus -- Almost certainly (believe me, based on hard-won experience) your problem is with the initrd.img defined in your VM config file: ramdisk= "/boot/initrd-2.6.19-1.2911.fc6xen.img" The root cause is probably the img file missing the xenblk.ko driver. Just rebuild the initrd using the "--with" switch to include it. If that doesn't work, you will need to look into the initrd image and possibly modify the init script; it may be trying to mount a nonexistent root device. But, my guess is xenblk.ko is missing. Search through the mailing list here or on xensource.com and it has been discussed recently. Good luck, Dave From jandrejkovic at gmail.com Fri Feb 23 00:21:43 2007 From: jandrejkovic at gmail.com (Jan Andrejkovic) Date: Fri, 23 Feb 2007 00:21:43 +0000 Subject: [Fedora-xen] Re: VNC and FreeNX disrupted is lost under XEN Dom0 kernel (mouse and keyboard are frozen) - resolved Message-ID: Hello, I resolved the problem by installing 3rd party graphic driver. My motherboard is Via J7F2WE2G and in the xorg.conf I had defafult Vesa driver. This driver caused below problem under FC6XEN kernel (also under 2.6.19-1.2911.fc6xen). I also noticed that under FC6XEN my xorg log had this error at the end: Fatal server error: Caught signal 11. Server aborting As I explained the server was working but because of this error it was not working properly. The problem was resolved by installing Via OpenChrome drivers from http://washington.kelkoo.net/epia/ and also I updated Xorg.conf using 'X -configure' Regards, Jan 2007/2/14, Jan Andrejkovic : > > Hello, > > I thought there is a pobrlem between FreeNX and FC6 XEN Dom0 kerenel but > now I discovered that there is also the same problem between VNC server and > XEN enabled kernel (vnc-server-4.1.2-9.fc6 and 2.6.19-1.2895.fc6xen ). > Does anybody have the same problem? > > Do you know any workaround? > > Thank you, > > Jan > > 2007/2/12, Jan Andrejkovic : > > > > Hello FC XEN list, > > > > I already sent this e-mail to main Fedora mailing list but now I > > realised it will be better to send it to XEN dist list: > > > > I have FC6 installed with latests patches (I use GNOME and XEN kernel > > 2.6.19-1.2895.fc6xen) with all current updates. I installed FreeNX from > > fedora extras and I tried to connect to this Dom0 kernel from Win XP client > > ( 2.1.0-16). The connection was successful but after a few seconds I > > lost the control using mouse and keyboard. I saw the screen, Gnome was just > > not responding. Even when I tried to resume abandoned session I saw the > > dektop again but I was not able to re-gain the control. > > > > Then I removed freenx downloaded from extras and I installed newest rpms > > from nomachine web-site: > > nxclient-2.1.0-11.i386.rpm > > nxnode-2.1.0-15.i386.rpm > > nxserver-2.1.0-18.i386.rpm > > and for compatibility I had to add: > > compat-libstdc++-296-2.96-138.i386.rpm (downloaded from rpmfind) > > > > However the result was the same - sesssion gets frozen after a couple of > > seconds. > > Then I tried to use older kernel - 2.6.18-1.2798.fc6xen with the same > > result - once I just moved the mouse over gnome main menu the session was > > frozen. > > > > (I did not make so much observations yet but I think it is somehow > > related to mouse because when the session is waiting for the text input it > > will not get frozen so easily. > > > > In final I tried non-XEN kernel 2.6.19-1.2895.fc6 and it seems to be > > working fine. > > > > Does anybody notice the same behaviour? I would like to try GUI manager > > to setup some domains but I can't... (Well, VNC is probaby the option...) > > > > Thank you, > > > > Jan > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at xelerance.com Fri Feb 23 03:47:01 2007 From: paul at xelerance.com (Paul Wouters) Date: Fri, 23 Feb 2007 04:47:01 +0100 (CET) Subject: [Fedora-xen] XEN Kernel Panic [update] In-Reply-To: <3207.192.168.2.92.1172183400.squirrel@www.bradleyland.com> References: <1172167596.5243.5.camel@workstation> <3207.192.168.2.92.1172183400.squirrel@www.bradleyland.com> Message-ID: On Thu, 22 Feb 2007, master at bradleyland.com wrote: > > Almost certainly (believe me, based on hard-won experience) your problem > is with the initrd.img defined in your VM config file: > > ramdisk= "/boot/initrd-2.6.19-1.2911.fc6xen.img" > > The root cause is probably the img file missing the xenblk.ko driver. Just > rebuild the initrd using the "--with" switch to include it. That's not enough, since you need to preload it. What I do to create initrd's for the guests (xenU's) on the dom0 is: mkinitrd /boot/initrd-2.6.19-1.2911.fc6xenU.img --preload=xenblk --with=xennet 2.6.19-1.2911.fc6xen I've said it before and I'll say it again. Life would be much simpler if all the "xen" kernel tree images include xenblk and xennet in the initrd. The "space" won has been completely not worth the time people lost over this issue. Paul -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From annefacq at crpp-bordeaux.cnrs.fr Fri Feb 23 06:51:06 2007 From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq) Date: Fri, 23 Feb 2007 07:51:06 +0100 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'VFS: Cannot open root device' In-Reply-To: <45C59978.4050509@crpp-bordeaux.cnrs.fr> References: <45C59978.4050509@crpp-bordeaux.cnrs.fr> Message-ID: <45DE8EDA.7030001@crpp-bordeaux.cnrs.fr> Hi Thanks to Sadique Puthen, here is the solution to my problem : - create an initrd image with --with=xennet --preload=xenblk options - specify that using "ramdisk = " in the configuration file for guest. Anne Facq wrote: > Hello > > I have got a problem booting a DomU on Linux Fedora Core 6 (kernel > 2.6.19-1.2895.fc6xen) > > I did the following operations : > > 1) dd if=/dev/zero of=/home/xen/vm1 bs=1k seek=6144k count=1 > > 2) mkfs.ext3 /home/xen/vm1 > > 3) mount -o loop /home/xen/vm1 /mnt > > 4) cp -ax /{root,dev,var,etc,usr,bin,sbin,lib,boot} /mnt > 5) mkdir -m 755 /mnt/{proc,sys,home,tmp,mnt} > > 6) DomU fstab : > /dev/sdb1 / 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 > > > 7) cat > /etc/xen/vm1 > kernel = "/boot/vmlinuz-2.6.19-1.2895.fc6xen" > memory = 512 > name = 'vm1' > vif = [ '' ] > disk = [ 'file:/home/xen/vm1,sdb1,w' ] > root = '/dev/sdb1 ro' > extra = 'ro selinux=0 3' > > 8) When I launch : > xm create -c vm1 > > I get the following error message : > ---- > VFS: Cannot open root device "sdb1" 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 tried several devices but I got the same message > > Any advice ? > > Thanks in advance. > > Anne Facq > From ashokthapliyal at gmail.com Fri Feb 23 07:23:31 2007 From: ashokthapliyal at gmail.com (Ashok Thapliyal) Date: Fri, 23 Feb 2007 12:53:31 +0530 Subject: [Fedora-xen] Problem creating VM image. Message-ID: hi, i have fedora core 6 installed with xen support. im trying to create a VM guest image using virt-manager what is the url that i can give in the install location as it is asking for a http,ftp,nfs location. i don't know what url to give ,,, or how can i set up an installation tree on the host OS ?? i have no clue as to how i can make this image file. can anyone please tell me??? thanks in advance Warm regards Ashok thapliyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From g+fedora at pkg.fr Fri Feb 23 09:36:04 2007 From: g+fedora at pkg.fr (Guillaume Bougard) Date: Fri, 23 Feb 2007 10:36:04 +0100 Subject: [Fedora-xen] destroydevice In-Reply-To: <20070130220539.GP18642@redhat.com> References: <45BFB880.1060409@cesca.es> <20070130213652.GN18642@redhat.com> <45BFC0FD.3060503@cesca.es> <20070130220539.GP18642@redhat.com> Message-ID: <1172223364.31929.8.camel@psyborg64.pkg.fr> Hi, I just got the same problem after an update to the last xen & kernel on FC5 system. I had 4 of my 5 virtual machines up but the 5th did not start and gave me this 'destroyDevice()' error. I searched a little to understand I mounted manually the volume disk I use for this machine and that was the problem... Just unmounting it and retry solved my problem. So if you have mounted manually the disk image of your virtual machine, try to unmount it before starting your virtual machine. Regards, Guillaume Bougard. Le mardi 30 janvier 2007 ? 22:05 +0000, Daniel P. Berrange a ?crit : > On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote: > > Ok, thank you! > > > > How long will take for the next release? > > Probably a few days before it goes to updates-testing, so don't > expect it to go to updates for at least a week > > > On the other hand, I can't ignore that error because I can't create any > > virtual machine, so Xen does nothing. On redhat 5 b2 it happens the > > same. I've changed my servers to FC6 because of this. > > Urm - read my explanation below again.... > > The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem > is *NOT* what is causing your guest to fail. It is merely obscuring the > underlying failure - an updated RPM will remove up the 'destroyDevice' > misleading message, but it won't magically make your guest work again. > > The fundamental problem is a configuration issue with your guest's virtual > disk or networking. Once you fix the config problem, the guest will work > just fine, with or without an updated RPM for the 'destroyDevice' issue > > > Daniel P. Berrange wrote: > > > On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote: > > >> Hi, > > >> It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm > > >> tool: creating a new VM it aborts showing this error: > > >> > > >> [root at inf16 ~]# xm create /etc/xen/rata.cfg > > >> Using config file "/etc/xen/rata.cfg". > > >> Error: destroyDevice() takes exactly 3 arguments (2 given) > > >> [root at inf16 ~]# > > >> > > >> Anyone knows what is causing this? On the xen-users list there's some > > >> other messages related to this isue (one mine). Mats Petersson say that > > >> this may be causes by a backport. > > > > > > Its a bug in one of the other patches we applied to the Xen RPM. I'll fix > > > it in the next release. > > > > > >> There's something broken on the package? There's any easy workarround? > > > > > > The error above isn't actually the root cause of your problems. What's > > > happened is that the hotplug scripts for your domain failed to complete > > > for some reason. Then when XenD is cleaning up from that failure, we > > > hit the bug above. So wrt to debugging your actual problems, ignore the > > > error message above. Instead look for a mis-configuration in either your > > > virtual network card or virtual disk config params. > > > Dan. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message num?riquement sign?e URL: From berrange at redhat.com Fri Feb 23 12:18:06 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 23 Feb 2007 12:18:06 +0000 Subject: [Fedora-xen] destroydevice In-Reply-To: <1172223364.31929.8.camel@psyborg64.pkg.fr> References: <45BFB880.1060409@cesca.es> <20070130213652.GN18642@redhat.com> <45BFC0FD.3060503@cesca.es> <20070130220539.GP18642@redhat.com> <1172223364.31929.8.camel@psyborg64.pkg.fr> Message-ID: <20070223121806.GE14993@redhat.com> On Fri, Feb 23, 2007 at 10:36:04AM +0100, Guillaume Bougard wrote: > Hi, > > I just got the same problem after an update to the last xen & kernel on > FC5 system. I had 4 of my 5 virtual machines up but the 5th did not > start and gave me this 'destroyDevice()' error. I searched a little to > understand I mounted manually the volume disk I use for this machine and > that was the problem... Just unmounting it and retry solved my problem. For anyone on Fedora Core 6 seeing this destroyDevice() issue, an update is available in updates-testing which addresses it, so you can see the root cause error. The package is xen-3.0.3-6.fc6 I'll look at doing an update for FC5 too. 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 ChipMotley at comcast.net Thu Feb 15 14:21:24 2007 From: ChipMotley at comcast.net (Chip Motley) Date: Thu, 15 Feb 2007 09:21:24 -0500 Subject: [Fedora-xen] Problems installing Xen Message-ID: <009901c7510c$92a12440$0201a8c0@homepc> Hello, I set up my first dual boot with Fedora 6 and WinXp. The partitions were setup as shown below. My problem occurred after the installation of Xen. When I went to /boot/grub and looked at grub.conf there was no reference to Xen. I ran "Xend start" and received the following message: ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 21, in ? import relocate File "/usr/lib/python2.4/site-packages/xen/xend/server/relocate.py", line 26, in ? from xen.xend import XendDomain File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 33, in ? import XendDomainInfo File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 39, in ? import image File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 36, in ? xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (2, 'No such file or directory') I looked in the Yum.log and found the following: Feb 15 01:42:04 Installed: xen-libs.i386 3.0.3-3.fc6 Feb 15 01:42:05 Installed: bridge-utils.i386 1.1-2 Feb 15 01:42:05 Installed: gnome-python2-gnomekeyring.i386 2.16.0-1.fc6 Feb 15 01:42:06 Installed: libvirt-python.i386 0.1.11-1.fc6 Feb 15 01:42:06 Installed: python-virtinst.noarch 0.98.0-1.fc6 Feb 15 01:42:12 Installed: libvirt.i386 0.1.11-1.fc6 Feb 15 01:42:14 Installed: virt-manager.i386 0.2.6-3.fc6 Feb 15 01:42:17 Installed: xen.i386 3.0.3-3.fc6 How do I install Xen correctly? PS I am new to Linux Thanks Chip Motley -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook.jpg Type: image/jpeg Size: 38723 bytes Desc: not available URL: From ChipMotley at comcast.net Fri Feb 16 01:34:28 2007 From: ChipMotley at comcast.net (Chip Motley) Date: Thu, 15 Feb 2007 20:34:28 -0500 Subject: [Fedora-xen] FW: Problems installing Xen Message-ID: <000101c7516a$99fbd5b0$0201a8c0@homepc> Hello, I set up my first dual boot with Fedora 6 and WinXp. The partitions were setup as shown below. My problem occurred after the installation of Xen. When I went to /boot/grub and looked at grub.conf there was no reference to Xen. I ran "Xend start" and received the following message: ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 49, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 21, in ? import relocate File "/usr/lib/python2.4/site-packages/xen/xend/server/relocate.py", line 26, in ? from xen.xend import XendDomain File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 33, in ? import XendDomainInfo File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 39, in ? import image File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 36, in ? xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (2, 'No such file or directory') I looked in the Yum.log and found the following: Feb 15 01:42:04 Installed: xen-libs.i386 3.0.3-3.fc6 Feb 15 01:42:05 Installed: bridge-utils.i386 1.1-2 Feb 15 01:42:05 Installed: gnome-python2-gnomekeyring.i386 2.16.0-1.fc6 Feb 15 01:42:06 Installed: libvirt-python.i386 0.1.11-1.fc6 Feb 15 01:42:06 Installed: python-virtinst.noarch 0.98.0-1.fc6 Feb 15 01:42:12 Installed: libvirt.i386 0.1.11-1.fc6 Feb 15 01:42:14 Installed: virt-manager.i386 0.2.6-3.fc6 Feb 15 01:42:17 Installed: xen.i386 3.0.3-3.fc6 How do I install Xen correctly? PS I am new to Linux Thanks Chip Motley -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook.jpg Type: image/jpeg Size: 38723 bytes Desc: not available URL: From ChipMotley at comcast.net Fri Feb 16 04:09:44 2007 From: ChipMotley at comcast.net (Chip Motley) Date: Thu, 15 Feb 2007 23:09:44 -0500 Subject: [Fedora-xen] xen windows already installed Message-ID: <000001c75180$4a5a15b0$0201a8c0@homepc> Hello, Is it possible to: Setup a dual boot using WinXp and Fedora 6 ---- then boot into Fedora using the xen kernel, start the virtual manager and boot the windows operating system that is already installed??? This would most likely require setting up a separate hardware profile within windows. I came across such an article (PDF) sometime ago, but now I can not find/Google it. Thanks Cmotley -------------- next part -------------- An HTML attachment was scrubbed... URL: From edoamaral at ig.com.br Sun Feb 18 01:56:22 2007 From: edoamaral at ig.com.br (edoamaral) Date: Sat, 17 Feb 2007 23:56:22 -0200 Subject: [Fedora-xen] Problems with starting xen guest Message-ID: <20070218_015622_024270.edoamaral@ig.com.br> Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo Started domain fedora.fc6 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2895.fc6xen (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:47:12 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/hda2 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e0000 soft=c07c0000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 1808.801 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 124568k/139264k available (2166k kernel code, 6360k reserved, 1100k data, 184k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc078e000 - 0xc07bc000 ( 184 kB) .data : 0xc061da2c - 0xc0730bf4 (1100 kB) .text : 0xc0400000 - 0xc061da2c (2166 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4528.74 BogoMIPS (lpj=9057489) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 128K (64 bytes/line) 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 5, 163840 bytes) TCP bind hash table entries: 4096 (order: 4, 81920 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1171762557.754:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx From pilger.david at gmail.com Mon Feb 19 17:19:09 2007 From: pilger.david at gmail.com (David Pilger) Date: Mon, 19 Feb 2007 19:19:09 +0200 Subject: [Fedora-xen] Preparing a Dom0 Kernel Message-ID: <280848580702190919n487278c0u760f2f30ec8a8d28@mail.gmail.com> Hi, What is the procedure to build one of the kernels from these repositories (http://hg.et.redhat.com/kernel/) to function as domain0? I built kernel 2.6.19.2 and tried to boot it with Xen. The function elf_xen_note_check prints the following error: "ERROR: Not a Xen-ELF image: No ELF notes or '__xen_guest' section found. Thanks in advance for your help, David. From ciaran.byrne at barefruit.co.uk Wed Feb 21 11:31:40 2007 From: ciaran.byrne at barefruit.co.uk (Ciaran Byrne) Date: Wed, 21 Feb 2007 11:31:40 +0000 Subject: [Fedora-xen] Console is unavailable Message-ID: <45DC2D9C.6020303@barefruit.co.uk> Hi, I hope you don't mind me contacting you like this, but I got your emails from an inconclusive discussion about the following subject. I am experimenting with virtualization in RHEL 5 Beta 2, and everything appears to go well until I try to connect to the console of the new virtual machine. The error includes the message "connection refused". There is no qemu-dm process running and /var/log/xen/qemu-dm.3598.log contains the following line: xc_get_pfn_list returned error 22 I have attached xend.log for today in case it helps. Incidentally, I seem to have found that there is no way to recover the new virtual machine after I have installed Fedora unless I save it just before the final reboot. I then do virsh restore xen-machine1.saved. I am hoping this is the right thing to do. Many thanks, Ciaran Byrne -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xend.log URL: From berrange at redhat.com Fri Feb 23 13:08:41 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 23 Feb 2007 13:08:41 +0000 Subject: [Fedora-xen] Problems installing Xen In-Reply-To: <009901c7510c$92a12440$0201a8c0@homepc> References: <009901c7510c$92a12440$0201a8c0@homepc> Message-ID: <20070223130841.GL14993@redhat.com> On Thu, Feb 15, 2007 at 09:21:24AM -0500, Chip Motley wrote: > Hello, > > I set up my first dual boot with Fedora 6 and WinXp. The partitions were > setup as shown below. My problem occurred after the installation of Xen. > When I went to /boot/grub and looked at grub.conf there was no reference to > Xen. I ran "Xend start" and received the following message: > > ERROR: Could not obtain handle on privileged command interface (2 = No such > file or directory) > ERROR: Could not obtain handle on privileged command interface (2 = No such > file or directory) Traceback (most recent call last): > File "/usr/sbin/xend", line 49, in ? > from xen.xend.server import SrvDaemon > File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line > 21, in ? > import relocate > File "/usr/lib/python2.4/site-packages/xen/xend/server/relocate.py", line > 26, in ? > from xen.xend import XendDomain > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 33, in > ? > import XendDomainInfo > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 39, > in ? > import image > File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 36, in ? > xc = xen.lowlevel.xc.xc() > xen.lowlevel.xc.Error: (2, 'No such file or directory') That error sugggests you're not running the Xen kernel - make sure you have 'kernel-xen' installed in your host & that it was selected in grub. > I looked in the Yum.log and found the following: > Feb 15 01:42:04 Installed: xen-libs.i386 3.0.3-3.fc6 > Feb 15 01:42:05 Installed: bridge-utils.i386 1.1-2 > Feb 15 01:42:05 Installed: gnome-python2-gnomekeyring.i386 2.16.0-1.fc6 > Feb 15 01:42:06 Installed: libvirt-python.i386 0.1.11-1.fc6 > Feb 15 01:42:06 Installed: python-virtinst.noarch 0.98.0-1.fc6 > Feb 15 01:42:12 Installed: libvirt.i386 0.1.11-1.fc6 > Feb 15 01:42:14 Installed: virt-manager.i386 0.2.6-3.fc6 > Feb 15 01:42:17 Installed: xen.i386 3.0.3-3.fc6 > > How do I install Xen correctly? PS I am new to Linux 'yum install kernel-xen' is needed to get the kernel too. 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 polytropolis at gmail.com Fri Feb 23 13:22:55 2007 From: polytropolis at gmail.com (Claus Reheis) Date: Fri, 23 Feb 2007 14:22:55 +0100 Subject: [Fedora-xen] XEN Kernel Panic [update] In-Reply-To: References: <1172167596.5243.5.camel@workstation> <3207.192.168.2.92.1172183400.squirrel@www.bradleyland.com> Message-ID: <1172236975.10909.0.camel@workstation> Hi Paul, hi Dave! I did a: mkinitrd -f --with=ext3 --preload=ext3 --with=xennet --builtin=aic7xxx --builtin=serverworks --preload=xenblk --omit-raid-modules --omit-lvm-modules --fstab=/home/user/disk/etc/fstab /boot/xen-initrd.img 2.6.19-1.2911.fc6xen created a new xen-initrd.img and tried again with this suse.xen.conf: kernel = "/boot/vmlinuz-2.6.19-1.2911.fc6xen" initrd= "/boot/xen-initrd.img" memory = 512 name = "opensuse102" vif = [''] #nics = 1 #dhcp = "dhcp" disk = ['file:/home/rehcla/opensuse102xen.img,xvda,w'] root = "/dev/xvda ro" and got again a Kernel Panic: Using config file "./suse.xen.cfg". Started domain opensuse102 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.492 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2168k kernel code, 11204k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8487.78 BogoMIPS (lpj=16975578) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172231052.798:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.492 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2168k kernel code, 11204k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8487.78 BogoMIPS (lpj=16975578) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172231052.798:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda" 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 also downloaded an debian 3.1 image from http://jailtime.org/ what gave me with the old initrd.img the same error as the opensuse102xen.img. I tried it with the new xen-initrd.img and the result gives me hope:) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2168k kernel code, 11204k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8494.77 BogoMIPS (lpj=16989547) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172213430.748:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: root=/dev/xvda ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 512768k/532480k available (2168k kernel code, 11204k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8494.77 BogoMIPS (lpj=16989547) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K 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 PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172213430.748:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda" 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) [root at workstation rehcla]# xm create -c /home/rehcla/debian/debian.3-1.xen3.cfg Using config file "/home/rehcla/debian/debian.3-1.xen3.cfg". Started domain debian.3-1 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 507520k/532480k available (2168k kernel code, 16420k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8495.53 BogoMIPS (lpj=16991062) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 5216k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172216475.645:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.19-1.2911.fc6xen (brewbuilder at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Feb 10 16:09:50 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 133120 Normal 133120 -> 133120 HighMem 133120 -> 133120 early_node_map[1] active PFN ranges 0: 0 -> 133120 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 132080 Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07e1000 soft=c07c1000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 3391.494 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 507520k/532480k available (2168k kernel code, 16420k reserved, 1106k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB) lowmem : 0xc0000000 - 0xe0800000 ( 520 MB) .init : 0xc0790000 - 0xc07bd000 ( 180 kB) .data : 0xc061e2e4 - 0xc0732bf4 (1106 kB) .text : 0xc0400000 - 0xc061e2e4 (2168 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 8495.53 BogoMIPS (lpj=16991062) 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: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 5216k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 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(1172216475.645:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks ksign: Installing public key data Loading keyring - Added public key BE1C9570C411C444 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 387k Red Hat nash version 5.1.19.0.2 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module Registering block device major 8 Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module register_blkdev: cannot get major 8 for sd Loading libata.ko module Loading ata_piix.ko module Loading dm-mod.ko module device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel at redhat.com Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading xennet.ko module netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys INIT: version 2.86 booting Activating swap. Adding 65528k swap on /dev/sda2. Priority:-1 extents:1 across:65528k Checking root file system... fsck 1.37 (21-Mar-2005) /dev/sda1: clean, 8493/131072 files, 48009/262144 blocks EXT3 FS on sda1, internal journal System time was Fri Feb 23 07:41:31 UTC 2007. Setting the System Clock using the Hardware Clock as reference... System Clock set. System local time is now Fri Feb 23 07:41:40 UTC 2007. Cleaning up ifupdown...done. Creating device-mapper devices...done. Checking all file systems... fsck 1.37 (21-Mar-2005) Setting kernel variables ... ... done. Mounting local filesystems... Cleaning /tmp /var/run /var/lock. Setting up networking...done. Setting up IP spoofing protection: rp_filter. Configuring network interfaces...Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html Listening on LPF/eth0/00:16:3e:7f:4d:fa Sending on LPF/eth0/00:16:3e:7f:4d:fa Sending on Socket/fallback/fallback-net DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPOFFER from 192.168.0.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.104 -- renewal in 21600 seconds. done. Loading the saved-state of the serial devices... Not setting System Clock INIT: Entering runlevel: 3 Starting system log daemon: syslogd. Starting kernel log daemon: klogd. Starting OpenBSD Secure Shell server: sshdPRNG is not seeded Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. At this step the progess stops and does not move on! No error message, nothing! xm list gives me: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1508 2 r----- 405.2 debian.3-1 3 511 1 r----- 1189.0 Login from another terminal with: xm console 3 was also not possible! Here is the /var/log/xen/xend.log: 2007-02-23 09:05:15 xend 3120] DEBUG (image:205) cmdline = ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro [2007-02-23 09:05:15 xend 3120] DEBUG (image:206) ramdisk = /boot/xen-initrd.img [2007-02-23 09:05:15 xend 3120] DEBUG (image:207) vcpus = 1 [2007-02-23 09:05:15 xend 3120] DEBUG (image:208) features = [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '2049', 'device-type': 'disk', 'state': '1', 'backend': '/ local/domain/0/backend/vbd/3/2049'} to /local/domain/3/device/vbd/2049. [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:112) DevController: writing {'domain': 'debian.3-1', 'frontend': '/local/domain/3/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params': '/home/rehcla/debian/debian.3-1.img', 'mode': 'w', 'online': '1', 'frontend-id': '3', 'type': 'file'} to /local/domain/0/backend/vbd/3/2049. [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '2050', 'device-type': 'disk', 'state': '1', 'backend': '/ local/domain/0/backend/vbd/3/2050'} to /local/domain/3/device/vbd/2050. [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:112) DevController: writing {'domain': 'debian.3-1', 'frontend': '/local/domain/3/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params': '/home/rehcla/debian/debian.swap', 'mode': 'w', 'online': '1', 'frontend-id': '3', 'type': 'file'} to /local/domain/0/backend/vbd/3/2050. [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:78:3f:1e', 'handle': '0', 'state': '1', 'backend': '/local/ domain/0/backend/vif/3/0'} to /local/domain/3/device/vif/0. [2007-02-23 09:05:15 xend 3120] DEBUG (DevController:112) DevController: writing {'domain': 'debian.3-1', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', ' frontend': '/local/domain/3/device/vif/0', 'mac': '00:16:3e:78:3f:1e', 'online': '1', 'frontend-id': '3'} to /local/domain/0/backend/vif/3/0. [2007-02-23 09:05:15 xend.XendDomainInfo 3120] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '0', 'uuid': '3d361011-5da9-5c8a-40a9-5f2b3daedd72', 'on_reboot': 'restart', 'start_time': '1172217915.99', 'on_poweroff': 'destroy', 'name': 'debian.3-1', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash ': 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6.19-1.2911.fc6xen) (ramdisk /boot/xen-initrd.img) (ip :1.2.3.4::::eth0:dhcp) (root '/dev/sda1 ro') (vncunused 1) (display :0.0) (xauthority /root/.xauthKyCkI4))", 'maxmem': '512'} [2007-02-23 09:05:16 xend.XendDomainInfo 3120] DEBUG (XendDomainInfo:750) Storing domain details: {'console/ring-ref': '180218', 'console/port': '2', 'name': 'debian.3-1', 'cons ole/limit': '1048576', 'vm': '/vm/3d361011-5da9-5c8a-40a9-5f2b3daedd72', 'domid': '3', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '180219', 'st ore/port': '1'} [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices vif. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:149) Waiting for 0. [2007-02-23 09:05:16 xend.XendDomainInfo 3120] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices usb. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices vbd. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:149) Waiting for 2049. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:149) Waiting for 2050. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/3/2050/hotplug-status. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices irq. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices pci. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices ioports. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices tap. [2007-02-23 09:05:16 xend 3120] DEBUG (DevController:143) Waiting for devices vtpm. [2007-02-23 09:05:16 xend 3120] INFO (XendDomain:370) Domain debian.3-1 (3) unpaused. Any Idea? Thanks for your answers, Claus Reheis On Fri, 2007-02-23 at 04:47 +0100, Paul Wouters wrote: > On Thu, 22 Feb 2007, master at bradleyland.com wrote: > > > > > Almost certainly (believe me, based on hard-won experience) your problem > > is with the initrd.img defined in your VM config file: > > > > ramdisk= "/boot/initrd-2.6.19-1.2911.fc6xen.img" > > > > The root cause is probably the img file missing the xenblk.ko driver. Just > > rebuild the initrd using the "--with" switch to include it. > > That's not enough, since you need to preload it. What I do to create > initrd's for the guests (xenU's) on the dom0 is: > > mkinitrd /boot/initrd-2.6.19-1.2911.fc6xenU.img --preload=xenblk --with=xennet 2.6.19-1.2911.fc6xen > > I've said it before and I'll say it again. Life would be much simpler if > all the "xen" kernel tree images include xenblk and xennet in the initrd. > The "space" won has been completely not worth the time people lost over > this issue. > > Paul -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From daryld at norco.com Fri Feb 23 19:25:16 2007 From: daryld at norco.com (Daryl Daly) Date: Fri, 23 Feb 2007 11:25:16 -0800 (PST) Subject: [Fedora-xen] gui console unavailable after upgrade Message-ID: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> I am just learning how to use xen. I installed a fc6 virtual machine and everything went okay. After the install I was able to start the virtual machine and use the gui console to log in. Then I did a 'yum update' on the virtual machine and rebooted it. Since doing that I have been unable to use the gui console. It just says "The console is currently unavailable". I am able to use the serial console. I don't see any new entries in the xend-debug.log I have also updated my host fc6. Any ideas as to the cause? Thanks, Daryl. -- Daryl Daly, B.Sc. Chief Programmer/Business Analyst daryld at norco.com Norco Products Ltd. Really Cool Bikes!!! Norco __O Tel: 604-552-2930 ext 205 Performance =\ \ Fax: 604-552-2948 Bikes (=)/(=) www.norco.com 1465 Kebet Way, Port Coquitlam, British Columbia, V3C 6L3 From armbru at redhat.com Fri Feb 23 21:47:37 2007 From: armbru at redhat.com (Markus Armbruster) Date: Fri, 23 Feb 2007 22:47:37 +0100 Subject: [Fedora-xen] gui console unavailable after upgrade In-Reply-To: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> (Daryl Daly's message of "Fri, 23 Feb 2007 11:25:16 -0800 (PST)") References: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> Message-ID: <87wt2835s6.fsf@pike.pond.sub.org> "Daryl Daly" writes: > I am just learning how to use xen. > I installed a fc6 virtual machine and everything went okay. After the > install I was able to start the virtual machine and use the gui console to > log in. > > Then I did a 'yum update' on the virtual machine and rebooted it. Since > doing that I have been unable to use the gui console. It just says "The > console is currently unavailable". I am able to use the serial console. > > I don't see any new entries in the xend-debug.log > > I have also updated my host fc6. > > Any ideas as to the cause? Fully virtual or paravirtual? Did you upgrade dom0 as well? From daryld at norco.com Fri Feb 23 21:58:24 2007 From: daryld at norco.com (Daryl Daly) Date: Fri, 23 Feb 2007 13:58:24 -0800 (PST) Subject: [Fedora-xen] gui console unavailable after upgrade In-Reply-To: <87wt2835s6.fsf@pike.pond.sub.org> References: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> <87wt2835s6.fsf@pike.pond.sub.org> Message-ID: <41209.192.168.45.20.1172267904.squirrel@email.norco.com> On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote: > Fully virtual or paravirtual? paravirtual > > Did you upgrade dom0 as well? > Hmmm... I am not sure of the terminology here. I assume that dom0 is the host OS (the host that the virtual machine was created and is running on). If that assumption is correct then yes it was updated as well. From huor.carnesir at arcor.de Fri Feb 23 21:52:46 2007 From: huor.carnesir at arcor.de (Christian Schuermann) Date: Fri, 23 Feb 2007 22:52:46 +0100 Subject: [Fedora-xen] Failed to obtain physical IRQ Message-ID: <45DF622E.1060800@arcor.de> Hi, I tried to boot a FC6 domU with kernel 2.6.19-1.2911.fc6xen. When I try to activate the network device (physical NIC, hidden from dom0) ifconfig eth0 up I get this error msg: Failed to obtain physical IRQ 10 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 ifconfig says, the device is up but pinging another host doesn't work. I tried to change the pci-slots, the NICs and used different drivers, the error message remains (just the IRQ changes). It seems that this is not a hardware problem. Googling the error message didn't help much. What can do to narrow down the problem? Thanks, Chris From edamaral at nortel.com Sat Feb 24 02:13:24 2007 From: edamaral at nortel.com (Eduardo Amaral) Date: Fri, 23 Feb 2007 21:13:24 -0500 Subject: [Fedora-xen] Problems with starting xen guest (DomU) In-Reply-To: <032d01c755ca$e7105330$fe0fa8c0@ispbrasil> Message-ID: <54A70491E004F44CA31355B49244588C032CB6E4@zrtphxm2.corp.nortel.com> I put img file on hda2 and swap on hda1. Now DomU started booting but it did not move one after starting sshd. Any idea what is going on ? Thanks Eduardo Creating root device. Mounting root filesystem. 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: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1172281317.492:2): selinux=0 auid=4294967295 INIT: version 2.86 booting Welcome to Fedora Core Press 'I' to enter interactive startup. Setting clock : Fri Feb 23 20:41:59 EST 2007 [ OK ] Setting hostname fc6_pristine: [ OK ] Checking filesystems Checking all file systems. [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Wednesday, February 21, 2007 1:14 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" hda2 seems to be a swap, your domU never boot. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Monday, February 19, 2007 11:08 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From junk at remcc.org Sat Feb 24 05:20:28 2007 From: junk at remcc.org (Robert Thiem) Date: Sat, 24 Feb 2007 15:20:28 +1000 (EST) Subject: [Fedora-xen] Re: gui console unavailable after upgrade In-Reply-To: <20070224021400.EFA9072F45@hormel.redhat.com> References: <20070224021400.EFA9072F45@hormel.redhat.com> Message-ID: <50712.192.168.1.3.1172294428.squirrel@virgil.remcc.org> > I am just learning how to use xen. > I installed a fc6 virtual machine and everything went okay. After the > install I was able to start the virtual machine and use the gui console to > log in. ... > I don't see any new entries in the xend-debug.log I had a similar problem that's mysteriously rectified itself today. Anyway, when you have a guest running you should see (on the host, Dom0): [root at lair6 ~]# netstat -antp | grep xen tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4350/xen-vncfb tcp 0 0 127.0.0.1:5900 127.0.0.1:36614 ESTABLISHED 4350/xen-vncfb [root at lair6 ~]# netstat -antp | grep python tcp 0 0 127.0.0.1:36614 127.0.0.1:5900 ESTABLISHED 4555/python This is (I believe) the xen virtual framebuffer serving on port 5900 and the client python console connecting to it (if a console is running). Checking that this xen-vncfb is running on the host is a good start. I'm pretty sure that it wasn't when my console wasn't working, but you might not be having the same issue. In case my checking today actually did something here's what I can remember doing since it wasn't working. yum update Reboot with SELinux in permissive mode (which didn't show up anything obviously wrong audit wise, but the console was working) Reboot with SELinux in enforcing mode (console still working) Robert Thiem From armbru at redhat.com Sat Feb 24 08:11:05 2007 From: armbru at redhat.com (Markus Armbruster) Date: Sat, 24 Feb 2007 09:11:05 +0100 Subject: [Fedora-xen] Re: gui console unavailable after upgrade In-Reply-To: <50712.192.168.1.3.1172294428.squirrel@virgil.remcc.org> (Robert Thiem's message of "Sat, 24 Feb 2007 15:20:28 +1000 (EST)") References: <20070224021400.EFA9072F45@hormel.redhat.com> <50712.192.168.1.3.1172294428.squirrel@virgil.remcc.org> Message-ID: <87zm740ycm.fsf@pike.pond.sub.org> "Robert Thiem" writes: >> I am just learning how to use xen. >> I installed a fc6 virtual machine and everything went okay. After the >> install I was able to start the virtual machine and use the gui console to >> log in. > ... >> I don't see any new entries in the xend-debug.log > > I had a similar problem that's mysteriously rectified itself today. > > Anyway, when you have a guest running you should see (on the host, Dom0): > > [root at lair6 ~]# netstat -antp | grep xen > tcp 0 0 127.0.0.1:5900 0.0.0.0:* > LISTEN 4350/xen-vncfb > tcp 0 0 127.0.0.1:5900 127.0.0.1:36614 > ESTABLISHED 4350/xen-vncfb > [root at lair6 ~]# netstat -antp | grep python > tcp 0 0 127.0.0.1:36614 127.0.0.1:5900 > ESTABLISHED 4555/python > > This is (I believe) the xen virtual framebuffer serving on port 5900 and > the client python console connecting to it (if a console is running). Correct. > Checking that this xen-vncfb is running on the host is a good start. I'm > pretty sure that it wasn't when my console wasn't working, but you might > not be having the same issue. > > In case my checking today actually did something here's what I can > remember doing since it wasn't working. > > yum update > Reboot with SELinux in permissive mode (which didn't show up anything > obviously wrong audit wise, but the console was working) > Reboot with SELinux in enforcing mode (console still working) > > Robert Thiem I figure restarting xend did the trick. From armbru at redhat.com Sat Feb 24 08:31:53 2007 From: armbru at redhat.com (Markus Armbruster) Date: Sat, 24 Feb 2007 09:31:53 +0100 Subject: [Fedora-xen] gui console unavailable after upgrade In-Reply-To: <41209.192.168.45.20.1172267904.squirrel@email.norco.com> (Daryl Daly's message of "Fri, 23 Feb 2007 13:58:24 -0800 (PST)") References: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> <87wt2835s6.fsf@pike.pond.sub.org> <41209.192.168.45.20.1172267904.squirrel@email.norco.com> Message-ID: <87y7mo0xdy.fsf@pike.pond.sub.org> "Daryl Daly" writes: > On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote: > >> Fully virtual or paravirtual? > > paravirtual > >> >> Did you upgrade dom0 as well? >> > > Hmmm... I am not sure of the terminology here. I assume that dom0 is the > host OS (the host that the virtual machine was created and is running on). > If that assumption is correct then yes it was updated as well. Good. The virtual framebuffer protocol recently changed from a preliminary version to the final version. The new backend (running in dom0, what you call host) is backward compatible: it can cope with new and old domU (what you may call guest). Old backend with new frontend doesn't work, though. Your update of dom0 should have gotten you the new backend. Weird. Does restarting xend help? If not, what's new in /var/log/xen/* ? From itamar at ispbrasil.com.br Sat Feb 24 22:10:03 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 24 Feb 2007 20:10:03 -0200 Subject: [Fedora-xen] Problems with starting xen guest (DomU) References: <54A70491E004F44CA31355B49244588C032CB6E4@zrtphxm2.corp.nortel.com> Message-ID: <017d01c75860$89efb040$fe0fa8c0@ispbrasil> Problems with starting xen guest (DomU)seems to be a networking problem add this line to your /etc/modprobe.conf in your domU alias eth0 xennet and try to boot your domU again. Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Saturday, February 24, 2007 12:13 AM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) I put img file on hda2 and swap on hda1. Now DomU started booting but it did not move one after starting sshd. Any idea what is going on ? Thanks Eduardo Creating root device. Mounting root filesystem. 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: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1172281317.492:2): selinux=0 auid=4294967295 INIT: version 2.86 booting Welcome to Fedora Core Press 'I' to enter interactive startup. Setting clock : Fri Feb 23 20:41:59 EST 2007 [ OK ] Setting hostname fc6_pristine: [ OK ] Checking filesystems Checking all file systems. [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] ------------------------------------------------------------------------------ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Wednesday, February 21, 2007 1:14 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" hda2 seems to be a swap, your domU never boot. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Monday, February 19, 2007 11:08 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! ---------------------------------------------------------------------------- From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) -------------------------------------------------------------------------- From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From edamaral at nortel.com Sat Feb 24 22:58:28 2007 From: edamaral at nortel.com (Eduardo Amaral) Date: Sat, 24 Feb 2007 17:58:28 -0500 Subject: [Fedora-xen] Problems with starting xen guest (DomU) In-Reply-To: <017d01c75860$89efb040$fe0fa8c0@ispbrasil> Message-ID: <54A70491E004F44CA31355B49244588C032CB7AB@zrtphxm2.corp.nortel.com> I added it but the i got the same problem ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Saturday, February 24, 2007 8:10 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) seems to be a networking problem add this line to your /etc/modprobe.conf in your domU alias eth0 xennet and try to boot your domU again. Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Saturday, February 24, 2007 12:13 AM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) I put img file on hda2 and swap on hda1. Now DomU started booting but it did not move one after starting sshd. Any idea what is going on ? Thanks Eduardo Creating root device. Mounting root filesystem. 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: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1172281317.492:2): selinux=0 auid=4294967295 INIT: version 2.86 booting Welcome to Fedora Core Press 'I' to enter interactive startup. Setting clock : Fri Feb 23 20:41:59 EST 2007 [ OK ] Setting hostname fc6_pristine: [ OK ] Checking filesystems Checking all file systems. [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Wednesday, February 21, 2007 1:14 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" hda2 seems to be a swap, your domU never boot. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Monday, February 19, 2007 11:08 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ________________________________ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From itamar at ispbrasil.com.br Sat Feb 24 23:28:23 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 24 Feb 2007 21:28:23 -0200 Subject: [Fedora-xen] Problems with starting xen guest (DomU) References: <54A70491E004F44CA31355B49244588C032CB7AB@zrtphxm2.corp.nortel.com> Message-ID: <001301c7586b$7f788be0$fe0fa8c0@ispbrasil> Problems with starting xen guest (DomU)have you configured network on domU ? /etc/sysconfig/networking (NETWORKING= yes) /etc/sysconfig/network-scripts/ifcfg-eth0 ? -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Saturday, February 24, 2007 8:58 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) I added it but the i got the same problem ------------------------------------------------------------------------------ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Saturday, February 24, 2007 8:10 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) seems to be a networking problem add this line to your /etc/modprobe.conf in your domU alias eth0 xennet and try to boot your domU again. Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Saturday, February 24, 2007 12:13 AM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) I put img file on hda2 and swap on hda1. Now DomU started booting but it did not move one after starting sshd. Any idea what is going on ? Thanks Eduardo Creating root device. Mounting root filesystem. 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: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1172281317.492:2): selinux=0 auid=4294967295 INIT: version 2.86 booting Welcome to Fedora Core Press 'I' to enter interactive startup. Setting clock : Fri Feb 23 20:41:59 EST 2007 [ OK ] Setting hostname fc6_pristine: [ OK ] Checking filesystems Checking all file systems. [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] ---------------------------------------------------------------------------- From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Wednesday, February 21, 2007 1:14 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" hda2 seems to be a swap, your domU never boot. -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Monday, February 19, 2007 11:08 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) Thanks Itamar . I ceated initrd file and started the guest DomU but i am still having problems... See below the last lines SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading xenblk.ko module Registering block device major 3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev hda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument 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! -------------------------------------------------------------------------- From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Monday, February 19, 2007 2:11 AM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) mkinitrd -v -f --with=ext3 --with=xenblk /boot/initrd-2.6.19-1.2895.fc6xen-ext3.img 2.6.19-1.2895.fc6xen add a ramdisk line on your domU config ramdisk ="/boot/initrd-2.6.19-1.2895.fc6xen-ext3.img" -------------------- 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: Eduardo Amaral To: Itamar Reis Peixoto ; fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:46 PM Subject: RE: [Fedora-xen] Problems with starting xen guest (DomU) ------------------------------------------------------------------------ From: Itamar Reis Peixoto [mailto:itamar at ispbrasil.com.br] Sent: Sunday, February 18, 2007 10:29 PM To: Amaral, Eduardo (UNID:2637); fedora-xen at redhat.com Subject: Re: [Fedora-xen] Problems with starting xen guest (DomU) where are your domU config ? /etc/xen See my DomU config Kernel ="/boot/vmlinuz-2.6.19-1.2895.fc6xen" memory= 128 name="fedora.fc6" vif=[' '] disk=['file:/root/Desktop/m_virtual/fedora.fc6.img,hda1,w' , ' file:/root/Desktop/m_virtual/fedora.swap,hda2,w?] root="/dev/hda2 ro" have you created a initrd form domU with xenblk module ? No. How is it created ? Could you give me the commands ? -------------------- 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: Eduardo Amaral To: fedora-xen at redhat.com Sent: Sunday, February 18, 2007 10:14 PM Subject: [Fedora-xen] Problems with starting xen guest (DomU) Hello All, My XEN guest was not starting. It stopped after " ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx "... Do you know what is going on ? Thanks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From samfw at redhat.com Sun Feb 25 15:01:15 2007 From: samfw at redhat.com (Sam Folk-Williams) Date: Sun, 25 Feb 2007 10:01:15 -0500 Subject: [Fedora-xen] Vanishing Harddisk In-Reply-To: <1168730997.45a96b75b68c9@webmail.purdue.edu> References: <1168730997.45a96b75b68c9@webmail.purdue.edu> Message-ID: <20070225150114.GH4543@unplugged.rdu.redhat.com> On 01/13/07 18:29 -0500 sjafri at purdue.edu wrote: > > > Hello All, I hope some one can help me. I have xen running on Fedora Core 6, now > when I try to add a guest os using virt-manager there are no hard disks > detected. the whole process goes fine until I have to pick a partition for > installation. I tried using both a file as avirtual disk and also a partition, > in both cases I come to stop because no hard disks or partitions are selected. In case you are still having this problem - this is most likely due to selinux. Selinux will only allow (by default) disk images to be in /var/lib/xen. You can either move your disk images there, adjust selinux, or disable selinux... -Sam > > > Ali > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Sam Folk-Williams, RHCE Red Hat Global Support Services Phone: 919/754-4558 GPG ID: 1B0D46BA From pasik at iki.fi Sun Feb 25 19:16:58 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 25 Feb 2007 21:16:58 +0200 Subject: [Fedora-xen] VLANs on DomU domains In-Reply-To: <45655FA0.1060002@mobilethink.dk> References: <455DA91C.7020905@mobilethink.dk> <4564E70E.9050407@nrggos.com.au> <45655FA0.1060002@mobilethink.dk> Message-ID: <20070225191658.GZ7120@edu.joroinen.fi> On Thu, Nov 23, 2006 at 09:45:20AM +0100, Bertho Stultiens wrote: > 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. > Hi! Did you figure out the correct way to do this? (set up bridge per vlan interface in dom0, and export/bridge only untagged frames to domU's). -- Pasi From ashokthapliyal at gmail.com Mon Feb 26 07:03:52 2007 From: ashokthapliyal at gmail.com (Ashok Thapliyal) Date: Mon, 26 Feb 2007 12:33:52 +0530 Subject: [Fedora-xen] Problem creating VM image using virt-manager in FC6 Message-ID: i have fedora core 6 installed with xen support. im trying to create a VM guest image using virt-manager what is the url that i can give in the install location as it is asking for a http,ftp,nfs location. i don't know what url to give ,,, if i use nfs option then, how can i set up an installation tree on the host OS ?? i have no clue as to how i can make this image file. What all steps are needed to create a VM image ,can anyone please tell me? Warm regards Ashok thapliyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From bst at mobilethink.dk Mon Feb 26 08:11:09 2007 From: bst at mobilethink.dk (Bertho Stultiens) Date: Mon, 26 Feb 2007 09:11:09 +0100 Subject: [Fedora-xen] VLANs on DomU domains In-Reply-To: <20070225191658.GZ7120@edu.joroinen.fi> References: <455DA91C.7020905@mobilethink.dk> <4564E70E.9050407@nrggos.com.au> <45655FA0.1060002@mobilethink.dk> <20070225191658.GZ7120@edu.joroinen.fi> Message-ID: <45E2961D.9020805@mobilethink.dk> Pasi K?rkk?inen wrote: > Did you figure out the correct way to do this? (set up bridge per vlan interface in > dom0, and export/bridge only untagged frames to domU's). Actually, I never did go further investigating. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From pasik at iki.fi Mon Feb 26 08:22:15 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 26 Feb 2007 10:22:15 +0200 Subject: [Fedora-xen] VLANs on DomU domains In-Reply-To: <45E2961D.9020805@mobilethink.dk> References: <455DA91C.7020905@mobilethink.dk> <4564E70E.9050407@nrggos.com.au> <45655FA0.1060002@mobilethink.dk> <20070225191658.GZ7120@edu.joroinen.fi> <45E2961D.9020805@mobilethink.dk> Message-ID: <20070226082215.GA7120@edu.joroinen.fi> On Mon, Feb 26, 2007 at 09:11:09AM +0100, Bertho Stultiens wrote: > Pasi K?rkk?inen wrote: > > Did you figure out the correct way to do this? (set up bridge per vlan interface in > > dom0, and export/bridge only untagged frames to domU's). > > Actually, I never did go further investigating. > > OK, thanks for the reply. I'll see what I can figure out.. -- Pasi From adrian.revill at shazamteam.net Mon Feb 26 08:32:18 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Mon, 26 Feb 2007 08:32:18 +0000 Subject: [Fedora-xen] Running Xen on low spec single CPU Message-ID: <45E29B12.5050503@shazamteam.net> I know a lot of people just see Xen as a method to use over spec'd boxes more efficiently, but im interested in using its virtulisation capabilities on low spec systems. Has any one had any luck with getting a DomU running on a single CPU. I seem to get stuck during the install, as far as i can see it seems that the DomU is not being allocated CPU time. Using Fedora 6, i can get through the anaconda stage in about 1/2 hr but when the X window starts the CPU use drops to near 0% and i never get past a black screen with the X cursor. From adrian at creative.net.au Mon Feb 26 08:47:33 2007 From: adrian at creative.net.au (Adrian Chadd) Date: Mon, 26 Feb 2007 16:47:33 +0800 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <45E29B12.5050503@shazamteam.net> References: <45E29B12.5050503@shazamteam.net> Message-ID: <20070226084733.GU19830@skywalker.creative.net.au> On Mon, Feb 26, 2007, Adrian Revill wrote: > I know a lot of people just see Xen as a method to use over spec'd boxes > more efficiently, but im interested in using its virtulisation > capabilities on low spec systems. > Has any one had any luck with getting a DomU running on a single CPU. > > I seem to get stuck during the install, as far as i can see it seems > that the DomU is not being allocated CPU time. > > Using Fedora 6, i can get through the anaconda stage in about 1/2 hr but > when the X window starts the CPU use drops to near 0% and i never get > past a black screen with the X cursor. I have no trouble with Xen on single CPU athlon machines running >10 DomU's. I don't run X or a framebuffer console. And my IO load is light. Adrian From adrian.revill at shazamteam.net Mon Feb 26 09:45:17 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Mon, 26 Feb 2007 09:45:17 +0000 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <20070226084733.GU19830@skywalker.creative.net.au> References: <45E29B12.5050503@shazamteam.net> <20070226084733.GU19830@skywalker.creative.net.au> Message-ID: <45E2AC2D.6080908@shazamteam.net> Hi Adrian, Thx for the reply, gives me hope. As you can guess im new to Xen. So how do you install the os into the DomU? If i was installing from cd i could use linux text expert, but i cant see how to give the option to the Dom install. regards Adrian Adrian Chadd wrote: > On Mon, Feb 26, 2007, Adrian Revill wrote: > >> I know a lot of people just see Xen as a method to use over spec'd boxes >> more efficiently, but im interested in using its virtulisation >> capabilities on low spec systems. >> Has any one had any luck with getting a DomU running on a single CPU. >> >> I seem to get stuck during the install, as far as i can see it seems >> that the DomU is not being allocated CPU time. >> >> Using Fedora 6, i can get through the anaconda stage in about 1/2 hr but >> when the X window starts the CPU use drops to near 0% and i never get >> past a black screen with the X cursor. >> > > I have no trouble with Xen on single CPU athlon machines running >10 DomU's. > I don't run X or a framebuffer console. And my IO load is light. > > > > Adrian > > From adrian at creative.net.au Mon Feb 26 10:05:29 2007 From: adrian at creative.net.au (Adrian Chadd) Date: Mon, 26 Feb 2007 18:05:29 +0800 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <45E2AC2D.6080908@shazamteam.net> References: <45E29B12.5050503@shazamteam.net> <20070226084733.GU19830@skywalker.creative.net.au> <45E2AC2D.6080908@shazamteam.net> Message-ID: <20070226100529.GY19830@skywalker.creative.net.au> On Mon, Feb 26, 2007, Adrian Revill wrote: > Hi Adrian, > > Thx for the reply, gives me hope. As you can guess im new to Xen. > > So how do you install the os into the DomU? > If i was installing from cd i could use linux text expert, but i cant > see how to give the option to the Dom install. I bootstrap Debian/ubuntu in a fresh jail using debootstrap inside the install root. I dump that into a freshly made LVM partition and boot the DomU up, then finish configuring it that way. Its not that simple. :) I'm pretty sure there's a much nicer way to bootstrap Fedora DomU's and hopefully one of the Fedora-Savvy people 'ere will point it out. Adrian From armbru at redhat.com Mon Feb 26 10:19:23 2007 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 26 Feb 2007 11:19:23 +0100 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <45E29B12.5050503@shazamteam.net> (Adrian Revill's message of "Mon, 26 Feb 2007 08:32:18 +0000") References: <45E29B12.5050503@shazamteam.net> Message-ID: <87649p1as4.fsf@pike.pond.sub.org> Adrian Revill writes: > I know a lot of people just see Xen as a method to use over spec'd > boxes more efficiently, but im interested in using its virtulisation > capabilities on low spec systems. > Has any one had any luck with getting a DomU running on a single CPU. > > I seem to get stuck during the install, as far as i can see it seems > that the DomU is not being allocated CPU time. > > Using Fedora 6, i can get through the anaconda stage in about 1/2 hr > but when the X window starts the CPU use drops to near 0% and i never > get past a black screen with the X cursor. Shot from the hip: how much physical RAM? How much memory allocated to the domU? From pasik at iki.fi Mon Feb 26 13:40:25 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 26 Feb 2007 15:40:25 +0200 Subject: [Fedora-xen] Xen network bridge questions (using network configuration tools provided by distribution) Message-ID: <20070226134025.GD7120@edu.joroinen.fi> Hi list! I'm trying to figure out a way to use network configuration scripts provided by the distribution to manage network/bridge configuration with xen.. This means I dont't want use xen "network-bridge" (or any other) script at all, because they are a bit limited in functionality. I want to setup VLAN interfaces with the scripts/tools provided by the distribution, and bridge each VLAN separately, so I can flexibly assign (and manage) specific VLAN's to domU's. This does not work with the default xen network-bridge script (the black magic it does seems to fail with VLAN interfaces). Example configuration: peth0.X == xenbrX peth0.Y == xenbrY peth1.Z == xenbrZ peth1.W == xenbrW Default Xen network-bridge script does the following (in addition to other things): 1. Changes the MAC-address of peth0 to FE:FF:FF:FF:FF:FF. If I have another physical interface, peth1, can it have the same MAC address, or does it have to be different? 2. Sets peth0 to NOARP (disables ARP). Why is this? Is it a requirement? 3. Sets xenbr0 to NOARP. Same question goes for this. I have working setup with FC6 network scripts/tools, but I'd like to make sure I do the correct things. Thanks! -- Pasi From berrange at redhat.com Mon Feb 26 13:45:50 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 26 Feb 2007 13:45:50 +0000 Subject: [Fedora-xen] Problem creating VM image using virt-manager in FC6 In-Reply-To: References: Message-ID: <20070226134550.GA23075@redhat.com> On Mon, Feb 26, 2007 at 12:33:52PM +0530, Ashok Thapliyal wrote: > i have fedora core 6 installed with xen support. > > im trying to create a VM guest image using virt-manager > > what is the url that i can give in the install location as it is asking for > a http,ftp,nfs location. i don't know what url to give ,,, The URL wanted is the same as the URL you would give to Anaconda if doing an install off a network media source. eg, it should be a URL pointing to the top level installation tree. http://download.fedora.devel.redhat.com/pub/fedora/linux/core/6/x86_64/os/ > if i use nfs option then, how can i set up an installation tree on the host > OS ?? To setup an NFS tree, copy the contents of all 5 ISO images into a directory and then point to the top level directory - eg you basically want to get a directory containing a copy of all the content at the URL i list above. 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 Feb 26 13:49:23 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 26 Feb 2007 13:49:23 +0000 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <45E29B12.5050503@shazamteam.net> References: <45E29B12.5050503@shazamteam.net> Message-ID: <20070226134923.GC23075@redhat.com> On Mon, Feb 26, 2007 at 08:32:18AM +0000, Adrian Revill wrote: > I know a lot of people just see Xen as a method to use over spec'd boxes > more efficiently, but im interested in using its virtulisation > capabilities on low spec systems. > Has any one had any luck with getting a DomU running on a single CPU. > > I seem to get stuck during the install, as far as i can see it seems > that the DomU is not being allocated CPU time. > > Using Fedora 6, i can get through the anaconda stage in about 1/2 hr but > when the X window starts the CPU use drops to near 0% and i never get > past a black screen with the X cursor. How much RAM did you give the guest install VM - RAM is much more important than CPU speed - I've seen hangs like the one you describe when I didn't give enough RAM for install. 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 bst at mobilethink.dk Mon Feb 26 14:13:04 2007 From: bst at mobilethink.dk (Bertho Stultiens) Date: Mon, 26 Feb 2007 15:13:04 +0100 Subject: [Fedora-xen] Xen network bridge questions (using network configuration tools provided by distribution) In-Reply-To: <20070226134025.GD7120@edu.joroinen.fi> References: <20070226134025.GD7120@edu.joroinen.fi> Message-ID: <45E2EAF0.9070208@mobilethink.dk> Pasi K?rkk?inen wrote: [snip] > 1. Changes the MAC-address of peth0 to FE:FF:FF:FF:FF:FF. If I have another > physical interface, peth1, can it have the same MAC address, or does it have > to be different? In principle, all unicast MACs in a broadcast domain have to be unique. Each vlan is a broadcast domain, so that is fine. However, the kernel has a slightly different view of the interfaces and I an not sure that it can keep everything properly isolated. The FE:FF..FF addresses are fake anyway and should be local only. There is then the STP problems you can run into depending on whether you have all isolated STP instances for each vlan/interface. To make a long story short :), use unique MACs to avoid problems. You can use them f.ex. from the 00:01:01, 10:00:00, ac:de:48... (and there are more private MAC pools defined; see http://standards.ieee.org/regauth/oui/oui.txt and look for PRIVATE). [do not use MAC addresses with an odd numbered high octet; these are reserved for multicast/broadcast] > 2. Sets peth0 to NOARP (disables ARP). Why is this? Is it a requirement? > 3. Sets xenbr0 to NOARP. Same question goes for this. The NOARP is because you do not want the interfaces to answer to arp requests. Neither interface has an IP address assigned, so they are to be local only and their MAC should not propagate. It is a requirement so far as to have them shut up... > I have working setup with FC6 network scripts/tools, but I'd like to make > sure I do the correct things. If you also could post your resulting scripts or make a micro-howto, that would be great too. Polishing can be done on the list I guess. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S From adrian.revill at shazamteam.net Mon Feb 26 14:16:37 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Mon, 26 Feb 2007 14:16:37 +0000 Subject: [Fedora-xen] Problem creating VM image using virt-manager in Message-ID: <45E2EBC5.7030307@shazamteam.net> Hi, I too found that part of the guides a bit light on information. I used the NFS option via a mount from the Dom0 box. I created a dir /fc6 and extracted all of the first cd to it, then for all the other CDs all you have to do is extract the Fedora dir into /fc6/Fedora. You need to edit /etc/exports and add the line /fc6 *(ro,no_root_squash) then restart nfs via /etc/init.d/nfs restart No need to worry about the long path normally given unless you like typing or are planning on using it for a mirror service. In virt-manager you the specify the source as nfs:'hostbox':/fc6 Also i found a comment saying that the file backed storage should be under /var/lib/xen/images so tha.t the SElinux doesnt block it, not sure if this is still valid for the latest release of FC regards Adrian From chris at tylers.info Mon Feb 26 14:21:03 2007 From: chris at tylers.info (Chris Tyler) Date: Mon, 26 Feb 2007 09:21:03 -0500 Subject: [Fedora-xen] Re: Problem creating VM image using virt-manager in FC6 In-Reply-To: <20070226134555.62CE57312D@hormel.redhat.com> References: <20070226134555.62CE57312D@hormel.redhat.com> Message-ID: <1172499663.5211.29.camel@concord2.proximity.on.ca> On Mon, 2007-02-26 at 08:45 -0500, Daniel P. Berrange wrote: > On Mon, Feb 26, 2007 at 12:33:52PM +0530, Ashok Thapliyal wrote: > > what is the url that i can give in the install location as it is > asking for > > a http,ftp,nfs location. i don't know what url to give ,,, > > The URL wanted is the same as the URL you would give to Anaconda if > doing an install off a network media source. eg, it should be a URL > pointing to the top level installation tree. > > http://download.fedora.devel.redhat.com/pub/fedora/linux/core/6/x86_64/os/ That will fetch all the files over the Internet, which may be slow (especially if you are experimenting and trying several installations). As an alternative, you can use a DVD as a local installation medium by serving it through Apache: # yum install -y httpd # setenforce 0 # temporary to enable httpd DVD access # ln -s /media/dvd /var/www/html/fedora # service httpd start Change /media/dvd to wherever your DVD is mounted (or you can use a DVD image mounted with the loopback option), then use http://dom0_ip_address/fedora/ as the install location (do not use 127.0.0.1 as the dom0_ip_address, because it will refer the guest domain to itself). -- Chris Tyler Author - Professor - Consultant From adrian.revill at shazamteam.net Mon Feb 26 14:21:25 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Mon, 26 Feb 2007 14:21:25 +0000 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <20070226134923.GC23075@redhat.com> References: <45E29B12.5050503@shazamteam.net> <20070226134923.GC23075@redhat.com> Message-ID: <45E2ECE5.5060702@shazamteam.net> Hi Dan I have a 1.7+ XP athlon and 1.5G ram in the box an have given it 512Mb for the DomU The same settings work a treat on a quad core Opto > How much RAM did you give the guest install VM - RAM is much more important > than CPU speed - I've seen hangs like the one you describe when I didn't > give enough RAM for install. > > Dan. > From frank at rosendahl.dyndns.org Mon Feb 26 14:57:10 2007 From: frank at rosendahl.dyndns.org (Frank Rosendahl) Date: Mon, 26 Feb 2007 15:57:10 +0100 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <45E2ECE5.5060702@shazamteam.net> References: <45E29B12.5050503@shazamteam.net> <20070226134923.GC23075@redhat.com> <45E2ECE5.5060702@shazamteam.net> Message-ID: <200702261557.19104.frank@rosendahl.dyndns.org> Am Montag Februar 26 2007 schrieb Adrian Revill: > Hi Dan > > I have a 1.7+ XP athlon and 1.5G ram in the box an have given it 512Mb > for the DomU > > The same settings work a treat on a quad core Opto > > > How much RAM did you give the guest install VM - RAM is much more > > important than CPU speed - I've seen hangs like the one you describe when > > I didn't give enough RAM for install. > > > > Dan. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen I use a Double Pentium III 650 MHz with 1GB RAM with 3 DomU's running. It's really good running! -- Gru? Frank Rosendahl Fingerprint: 7506 6D0F 2C79 09A6 A8CF E51D BEF0 0279 A989 8450 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gaurav at cpsc.ucalgary.ca Mon Feb 26 17:30:05 2007 From: gaurav at cpsc.ucalgary.ca (Abhishek Gaurav) Date: Mon, 26 Feb 2007 10:30:05 -0700 Subject: [Fedora-xen] NFS Booting - Kernel modification Message-ID: <45E3191D.201@cpsc.ucalgary.ca> Hi, I have been trying to boot a VM over NFS with the default xen-kernel that came with FC6. However, I ran into the problems like: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) After some search, it looks like that the CONFIG_IP_PNP and CONFIG_ROOT_NFS parameters need to be enabled in the kernel. Can anyone please let me know how to go about it in the default fc6-xen system. It also looks like that I do not have the source for the xen-enabled kernel. Thanks, Abhishek. From paul at xelerance.com Mon Feb 26 17:40:25 2007 From: paul at xelerance.com (Paul Wouters) Date: Mon, 26 Feb 2007 18:40:25 +0100 (CET) Subject: [Fedora-xen] NFS Booting - Kernel modification In-Reply-To: <45E3191D.201@cpsc.ucalgary.ca> References: <45E3191D.201@cpsc.ucalgary.ca> Message-ID: On Mon, 26 Feb 2007, Abhishek Gaurav wrote: > I have been trying to boot a VM over NFS with the default xen-kernel that came > with FC6. However, I ran into the problems like: > VFS: Cannot open root device "nfs" or unknown-block(0,255) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,255) You are missing drivers from the initrd. I am not sure if you can grab the ramdisk (initrd) over the network, obviously you need some network drivers first. > After some search, it looks like that the CONFIG_IP_PNP and CONFIG_ROOT_NFS > parameters need to be enabled in the kernel. Can anyone please let me know how > to go about it in the default fc6-xen system. It also looks like that I do not > have the source for the xen-enabled kernel. install the kernel-xen-devel package. Then either change the config-* files or, which is easier, you can run rpmbuild -bp which sets up the build/linux-* directory and patch everything, and then you can run make config and make bzImage yourself. Paul From daryld at norco.com Mon Feb 26 19:10:46 2007 From: daryld at norco.com (Daryl Daly) Date: Mon, 26 Feb 2007 11:10:46 -0800 (PST) Subject: [Fedora-xen] gui console unavailable after upgrade In-Reply-To: <87y7mo0xdy.fsf@pike.pond.sub.org> References: <58886.192.168.45.20.1172258716.squirrel@email.norco.com> <87wt2835s6.fsf@pike.pond.sub.org> <41209.192.168.45.20.1172267904.squirrel@email.norco.com> <87y7mo0xdy.fsf@pike.pond.sub.org> Message-ID: <33196.192.168.45.20.1172517046.squirrel@email.norco.com> On Sat, February 24, 2007 12:31 am, Markus Armbruster wrote: > "Daryl Daly" writes: > >> On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote: >> >>> Fully virtual or paravirtual? >> >> paravirtual >> >>> >>> Did you upgrade dom0 as well? >>> >> >> Hmmm... I am not sure of the terminology here. I assume that dom0 is the >> host OS (the host that the virtual machine was created and is running >> on). >> If that assumption is correct then yes it was updated as well. > > Good. > > The virtual framebuffer protocol recently changed from a preliminary > version to the final version. The new backend (running in dom0, what > you call host) is backward compatible: it can cope with new and old > domU (what you may call guest). Old backend with new frontend doesn't > work, though. > > Your update of dom0 should have gotten you the new backend. Weird. > Does restarting xend help? If not, what's new in /var/log/xen/* ? > After rebooting this morning the problem seems to be resolved. I had rebooted Friday morning but that hadn't fixed the problem. It turns out that there were some updates to the dom0 for xen that came in after the Friday morning reboot. Those updates must have fixed the problem. Thanks for your help. From paul at xelerance.com Mon Feb 26 22:13:06 2007 From: paul at xelerance.com (Paul Wouters) Date: Mon, 26 Feb 2007 23:13:06 +0100 (CET) Subject: [Fedora-xen] NFS Booting - Kernel modification In-Reply-To: <45E33EA2.7010903@cpsc.ucalgary.ca> References: <45E3191D.201@cpsc.ucalgary.ca> <45E33EA2.7010903@cpsc.ucalgary.ca> Message-ID: On Mon, 26 Feb 2007, Abhishek Gaurav wrote: > If I use a ramdisk, the error log changes (its attached to this mail). Not > sure if I am in the right direction. Yes you are! Your logs show: > Bootdata ok (command line is ip=136.159.8.59:136.159.8.14:136.159.8.14:255.255.255.0::eth0:off root=/dev/nfs nfsroot=136.159.8.14:/home/xen-images/fc4 ) > > Linux version 2.6.18-1.2798.fc6xen (brewbuilder at hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 > > SELinux: Initializing. > > checking if image is initramfs... it is > > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize it loads the ramdisk > Xen virtual console successfully installed as xvc0 > > XENBUS: Device with no driver: device/vif/0 Looks like a missing xenblk or xennet driver... > Write protecting the kernel read-only data: 440k > > 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 cciss.ko module > HP CISS Driver (v 3.6.10) > > 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 > 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! I am confused that I don't see xenblk being loaded, yet you are able to get mount the rootfs. Might be a NFS thing. Try creating a special ramdisk/initrd for this machine on the dom0 using: mkinitrd /boot/initrd-2.6.18-1.2798.fc6xenU.img --preload=xenblk --with=xennet 2.6.18-1.2798.fc6xen and change your config to use the ramdisk /boot/initrd-2.6.18-1.2798.fc6xenU.img instead. Please let me know if this works. Paul From debian at herakles.homelinux.org Mon Feb 26 23:02:44 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 27 Feb 2007 08:02:44 +0900 Subject: [Fedora-xen] Running Xen on low spec single CPU In-Reply-To: <20070226100529.GY19830@skywalker.creative.net.au> References: <45E29B12.5050503@shazamteam.net> <20070226084733.GU19830@skywalker.creative.net.au> <45E2AC2D.6080908@shazamteam.net> <20070226100529.GY19830@skywalker.creative.net.au> Message-ID: <45E36714.9070400@herakles.homelinux.org> Adrian Chadd wrote: > On Mon, Feb 26, 2007, Adrian Revill wrote: >> Hi Adrian, >> >> Thx for the reply, gives me hope. As you can guess im new to Xen. >> >> So how do you install the os into the DomU? >> If i was installing from cd i could use linux text expert, but i cant >> see how to give the option to the Dom install. > > I bootstrap Debian/ubuntu in a fresh jail using debootstrap inside the > install root. I dump that into a freshly made LVM partition and boot > the DomU up, then finish configuring it that way. > > Its not that simple. :) I'm pretty sure there's a much nicer way > to bootstrap Fedora DomU's and hopefully one of the Fedora-Savvy people > 'ere will point it out. Debian/Ubuntu has some nice scripts for creating VMs (a little buggy at present though). It writes the xen config file, and (according to its docs) can create Ubuntu, Debian and Fedora guests, is extensible. It has the option of running debootstrap (for Debian/ubuntu), rpmstrap (for RPM-based systems), creating the system from an exising directory tree, from a tarball. With the right incantation, you can go from raw materials to a running guest in one command. SUSE's Yast cam also create guests; I have a SLES guest on my laptop (openSUSE 10.2 host) created with Yast. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From debian at herakles.homelinux.org Mon Feb 26 23:05:07 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 27 Feb 2007 08:05:07 +0900 Subject: [Fedora-xen] Problem creating VM image using virt-manager in FC6 In-Reply-To: References: Message-ID: <45E367A3.2000403@herakles.homelinux.org> Ashok Thapliyal wrote: > i have fedora core 6 installed with xen support. > > im trying to create a VM guest image using virt-manager > > what is the url that i can give in the install location as it is asking for > a http,ftp,nfs location. i don't know what url to give ,,, > > > if i use nfs option then, how can i set up an installation tree on the host > OS ?? > > i have no clue as to how i can make this image file. > > What all steps are needed to create a VM image ,can anyone please tell me? > > Warm regards > Ashok thapliyal Really, you need to read your instructions for installing FC6. This information has been on the CDs for years, updated for each release at least as far back as RHL 7.x. The README tells how to create the install tree. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From gaurav at cpsc.ucalgary.ca Mon Feb 26 22:53:43 2007 From: gaurav at cpsc.ucalgary.ca (Abhishek Gaurav) Date: Mon, 26 Feb 2007 15:53:43 -0700 Subject: [Fedora-xen] NFS Booting - Kernel modification In-Reply-To: References: <45E3191D.201@cpsc.ucalgary.ca> <45E33EA2.7010903@cpsc.ucalgary.ca> Message-ID: <45E364F7.2000209@cpsc.ucalgary.ca> Paul Wouters wrote: > On Mon, 26 Feb 2007, Abhishek Gaurav wrote: > > >> If I use a ramdisk, the error log changes (its attached to this mail). Not >> sure if I am in the right direction. >> > > Yes you are! > > Your logs show: > > >> Bootdata ok (command line is ip=136.159.8.59:136.159.8.14:136.159.8.14:255.255.255.0::eth0:off root=/dev/nfs nfsroot=136.159.8.14:/home/xen-images/fc4 ) >> >> Linux version 2.6.18-1.2798.fc6xen (brewbuilder at hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 >> >> SELinux: Initializing. >> >> checking if image is initramfs... it is >> >> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >> > > it loads the ramdisk > > >> Xen virtual console successfully installed as xvc0 >> >> XENBUS: Device with no driver: device/vif/0 >> > > Looks like a missing xenblk or xennet driver... > > >> Write protecting the kernel read-only data: 440k >> >> 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 cciss.ko module >> HP CISS Driver (v 3.6.10) >> >> 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 >> 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! >> > > I am confused that I don't see xenblk being loaded, yet you are > able to get mount the rootfs. Might be a NFS thing. > > Try creating a special ramdisk/initrd for this machine on the > dom0 using: > > mkinitrd /boot/initrd-2.6.18-1.2798.fc6xenU.img --preload=xenblk --with=xennet 2.6.18-1.2798.fc6xen > > and change your config to use the ramdisk /boot/initrd-2.6.18-1.2798.fc6xenU.img instead. > > Please let me know if this works. > > Paul > Hi Paul, It ends up in the same error with the following diff in the boot sequence. I have also attached the complete boot sequence. 15,16c15,16 Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k data, 172k init) Calibrating delay using timer specific routine.. 6002.08 BogoMIPS (lpj=12004172) --- Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k data, 172k init) Calibrating delay using timer specific routine.. 6001.96 BogoMIPS (lpj=12003922) 26c26 CPU: Processor Core ID: 1 --- CPU: Processor Core ID: 0 54c54 audit(1172530246.553:1): initialized --- audit(1172530185.634:1): initialized 87,88c87,88 Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k data, 172k init) Calibrating delay using timer specific routine.. 6002.08 BogoMIPS (lpj=12004172) --- Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k data, 172k init) Calibrating delay using timer specific routine.. 6001.96 BogoMIPS (lpj=12003922) 98c98 CPU: Processor Core ID: 1 --- CPU: Processor Core ID: 0 126c126 audit(1172530246.553:1): initialized --- audit(1172530185.634:1): initialized 170a171 > Loading xenblk.ko module 187c188,191 < Creating root device. --- > Loading xennet.ko module > netfront: Initialising virtual ethernet driver. netfront: Created netdev eth0 with flipping receive path. Creating root device. Also, for your reference, the config file for the VM is: kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xenU.img" name = "grc59" memory = "1024" vif = [ 'mac=00:16:3e:0e:81:59' ] root = '/dev/nfs' nfs_server = '136.159.8.14' nfs_root = '/home/xen-images/fc4' Thanks for the help, Abhishek. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: error_log URL: From paul at xelerance.com Tue Feb 27 01:31:08 2007 From: paul at xelerance.com (Paul Wouters) Date: Tue, 27 Feb 2007 02:31:08 +0100 (CET) Subject: [Fedora-xen] NFS Booting - Kernel modification In-Reply-To: <45E364F7.2000209@cpsc.ucalgary.ca> References: <45E3191D.201@cpsc.ucalgary.ca> <45E33EA2.7010903@cpsc.ucalgary.ca> <45E364F7.2000209@cpsc.ucalgary.ca> Message-ID: On Mon, 26 Feb 2007, Abhishek Gaurav wrote: The loading of those two drivers look good, but I don't know why it still does not work. I haven't tried booting xenu's over NFS myself. Paul > Paul Wouters wrote: > > On Mon, 26 Feb 2007, Abhishek Gaurav wrote: > > > > > > > If I use a ramdisk, the error log changes (its attached to this mail). Not > > > sure if I am in the right direction. > > > > > > > Yes you are! > > > > Your logs show: > > > > > > > Bootdata ok (command line is > > > ip=136.159.8.59:136.159.8.14:136.159.8.14:255.255.255.0::eth0:off > > > root=/dev/nfs nfsroot=136.159.8.14:/home/xen-images/fc4 ) > > > > > > Linux version 2.6.18-1.2798.fc6xen > > > (brewbuilder at hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red > > > Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 > > > > > > SELinux: Initializing. > > > > > > checking if image is initramfs... it is > > > > > > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > > > > > > > it loads the ramdisk > > > > > > > Xen virtual console successfully installed as xvc0 > > > > > > XENBUS: Device with no driver: device/vif/0 > > > > > > > Looks like a missing xenblk or xennet driver... > > > > > > > Write protecting the kernel read-only data: 440k > > > > > > 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 cciss.ko module > > > HP CISS Driver (v 3.6.10) > > > > > > 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 > > > 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! > > > > > > > I am confused that I don't see xenblk being loaded, yet you are > > able to get mount the rootfs. Might be a NFS thing. > > > > Try creating a special ramdisk/initrd for this machine on the > > dom0 using: > > > > mkinitrd /boot/initrd-2.6.18-1.2798.fc6xenU.img --preload=xenblk > > --with=xennet 2.6.18-1.2798.fc6xen > > > > and change your config to use the ramdisk > > /boot/initrd-2.6.18-1.2798.fc6xenU.img instead. > > > > Please let me know if this works. > > > > Paul > > > Hi Paul, > It ends up in the same error with the following diff in the boot sequence. I > have also attached the complete boot sequence. > > 15,16c15,16 > Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k > data, 172k init) > Calibrating delay using timer specific routine.. 6002.08 BogoMIPS > (lpj=12004172) > --- > Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k > data, 172k init) > Calibrating delay using timer specific routine.. 6001.96 BogoMIPS > (lpj=12003922) > 26c26 > CPU: Processor Core ID: 1 > --- > CPU: Processor Core ID: 0 > 54c54 > audit(1172530246.553:1): initialized > --- > audit(1172530185.634:1): initialized > 87,88c87,88 > Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k > data, 172k init) > Calibrating delay using timer specific routine.. 6002.08 BogoMIPS > (lpj=12004172) > --- > Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k > data, 172k init) > Calibrating delay using timer specific routine.. 6001.96 BogoMIPS > (lpj=12003922) > 98c98 > CPU: Processor Core ID: 1 > --- > CPU: Processor Core ID: 0 > 126c126 > audit(1172530246.553:1): initialized > --- > audit(1172530185.634:1): initialized > 170a171 > > Loading xenblk.ko module > 187c188,191 > < Creating root device. > --- > > Loading xennet.ko module > > netfront: Initialising virtual ethernet driver. > netfront: Created netdev eth0 with flipping receive path. > Creating root device. > > > Also, for your reference, the config file for the VM is: > > kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" > ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xenU.img" > name = "grc59" > memory = "1024" > vif = [ 'mac=00:16:3e:0e:81:59' ] > root = '/dev/nfs' > nfs_server = '136.159.8.14' > nfs_root = '/home/xen-images/fc4' > > > Thanks for the help, > Abhishek. > > -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From abrination at googlemail.com Tue Feb 27 15:02:59 2007 From: abrination at googlemail.com (Abri Nation) Date: Tue, 27 Feb 2007 16:02:59 +0100 Subject: [Fedora-xen] Windows on FC6 - Installation freeze Message-ID: <387e65040702270702m41c5a771n92b0f68e76548aa2@mail.gmail.com> Hi @all, i have problems with installing a virtual Windows 2003 on my FC6 with XEN. the installation freeze during the windows setup in the section of device installation . i selected (F5) APCI-Multi-Processor cause i want to use 2 cpus in the Windows VM. i think thats one of the problems, cause if install Widnows as a "Standard PC" there is no problem during the installation - but there it is not possible to use 2 cpus. The system i use: 2 Quadcore Xeon and FC6 Do anyone got the same problems? What can i do for using Windows 2003 Server with more than 1 cpu? Thank you very much for help! Greets, Abri -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Feb 27 15:12:21 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 27 Feb 2007 15:12:21 +0000 Subject: [Fedora-xen] Windows on FC6 - Installation freeze In-Reply-To: <387e65040702270702m41c5a771n92b0f68e76548aa2@mail.gmail.com> References: <387e65040702270702m41c5a771n92b0f68e76548aa2@mail.gmail.com> Message-ID: <20070227151221.GH17206@redhat.com> On Tue, Feb 27, 2007 at 04:02:59PM +0100, Abri Nation wrote: > Hi @all, > > i have problems with installing a virtual Windows 2003 on my FC6 with XEN. > the installation freeze during the windows setup in the section of device > installation . > i selected (F5) APCI-Multi-Processor cause i want to use 2 cpus in the > Windows VM. > i think thats one of the problems, cause if install Widnows as a "Standard > PC" there is no problem > during the installation - but there it is not possible to use 2 cpus. > > The system i use: 2 Quadcore Xeon and FC6 > > Do anyone got the same problems? What can i do for using Windows 2003 Server > with more than 1 cpu? The support for SMP in fullvirtualized guests in Xen 3.0.3 is flaky at best, downright broken at worst. So don't expect >1 VCPU to work at all reliably, if at all. Xen 3.0.4 (which is in Fedora 7) has improved SMP for HVM guests a great deal so your really best sticking with a single VCPU in Windows 2k3 until you can update to Fedora 7. 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 pasik at iki.fi Tue Feb 27 18:17:42 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 27 Feb 2007 20:17:42 +0200 Subject: [Fedora-xen] Xen network bridge questions (using network configuration tools provided by distribution) In-Reply-To: <45E2EAF0.9070208@mobilethink.dk> References: <20070226134025.GD7120@edu.joroinen.fi> <45E2EAF0.9070208@mobilethink.dk> Message-ID: <20070227181742.GG7120@edu.joroinen.fi> On Mon, Feb 26, 2007 at 03:13:04PM +0100, Bertho Stultiens wrote: > Pasi K?rkk?inen wrote: > [snip] > > 1. Changes the MAC-address of peth0 to FE:FF:FF:FF:FF:FF. If I have another > > physical interface, peth1, can it have the same MAC address, or does it have > > to be different? > > In principle, all unicast MACs in a broadcast domain have to be unique. > Each vlan is a broadcast domain, so that is fine. However, the kernel > has a slightly different view of the interfaces and I an not sure that > it can keep everything properly isolated. The FE:FF..FF addresses are > fake anyway and should be local only. There is then the STP problems you > can run into depending on whether you have all isolated STP instances > for each vlan/interface. > > To make a long story short :), use unique MACs to avoid problems. You > can use them f.ex. from the 00:01:01, 10:00:00, ac:de:48... (and there > are more private MAC pools defined; see > http://standards.ieee.org/regauth/oui/oui.txt and look for PRIVATE). > > [do not use MAC addresses with an odd numbered high octet; these are > reserved for multicast/broadcast] > OK. Thanks. Because peth* and xenbr* have NOARP, it should be ok to use fake MAC-addresses.. for example: peth0 FE:FF:FF:FF:FF:00 peth1 FE:FF:FF:FF:FF:01 etc. Or should I use some of the PRIVATE address ranges from that doc? > > > 2. Sets peth0 to NOARP (disables ARP). Why is this? Is it a requirement? > > 3. Sets xenbr0 to NOARP. Same question goes for this. > > The NOARP is because you do not want the interfaces to answer to arp > requests. Neither interface has an IP address assigned, so they are to > be local only and their MAC should not propagate. It is a requirement so > far as to have them shut up... > OK. > > > I have working setup with FC6 network scripts/tools, but I'd like to make > > sure I do the correct things. > > If you also could post your resulting scripts or make a micro-howto, > that would be great too. Polishing can be done on the list I guess. > I'll do it after I've tested them properly :) -- Pasi From altenah at hccnet.nl Tue Feb 27 18:13:04 2007 From: altenah at hccnet.nl (Henk Altena) Date: Tue, 27 Feb 2007 19:13:04 +0100 Subject: [Fedora-xen] xen and fc6 Message-ID: <45E474B0.3050904@hccnet.nl> Hello everybody, I have two problems with xen and fc6 on a x86_64 AMD. The first problem: When I install on a new HD fc6 x86_64 WITH the program group VM then my pc is refusing to boot. The boot process stops with the message: udev and then hangs. After the above procedure I installed FC6 x86-64 WITHOUT xen. The machine boots normal. Now I install all the xen packages. At boot time I can choose now between the xen kernel and the 'normal' kernel. BUT when I make the xen kernel the default boot option the machine hangs again. So I make the 'normal' kernel the default which it was by default. Now I can boot both kernels without problems. So when the xen kernel is the default boot option or the only boot option the machine refuses to boot. Why ? My second problem is how to create a VM image: In this list I used the advice from Chris Tyler on booting from a network source in this case http. My URL is: http://192.168.0.1/FC_5, which is the ip adres of my FC_6-xen installation. The startup works ok untill the following error: "error: failed to retrieve FC_5/Fedora/base/stage2.img" I disabled SElinux. I can browse the dvd with Firefox. When I use nfs as a source as Adrian Revill pointed out I end up with the error: "That directory could not be mounted from the server" While the setup starts fine it seems to me the nfs setup is correct so there must be another problem ? What am I doing wrong ? Thanks in advance ! Henk From altenah at hccnet.nl Tue Feb 27 18:18:01 2007 From: altenah at hccnet.nl (Henk Altena) Date: Tue, 27 Feb 2007 19:18:01 +0100 Subject: [Fedora-xen] xen and fc6 x86_64 Message-ID: <45E475D9.4060104@hccnet.nl> Hello everybody, I have two problems with xen and fc6 on a x86_64 AMD. The first problem: When I install on a new HD fc6 x86_64 WITH the program group VM then my pc is refusing to boot. The boot process stops with the message: udev and then hangs. After the above procedure I installed FC6 x86-64 WITHOUT xen. The machine boots normal. Now I install all the xen packages. At boot time I can choose now between the xen kernel and the 'normal' kernel. BUT when I make the xen kernel the default boot option the machine hangs again. So I make the 'normal' kernel the default which it was by default. Now I can boot both kernels without problems. So when the xen kernel is the default boot option or the only boot option the machine refuses to boot. Why ? My second problem is how to create a VM image: In this list I used the advice from Chris Tyler on booting from a network source in this case http. My URL is: http://192.168.0.1/FC_5, which is the ip adres of my FC_6-xen installation. The startup works ok untill the following error: "error: failed to retrieve FC_5/Fedora/base/stage2.img" I disabled SElinux. I can browse the dvd with Firefox. When I use nfs as a source as Adrian Revill pointed out I end up with the error: "That directory could not be mounted from the server" While the setup starts fine it seems to me the nfs setup is correct so there must be another problem ? What am I doing wrong ? Thanks in advance ! Henk From gaurav at cpsc.ucalgary.ca Tue Feb 27 20:24:23 2007 From: gaurav at cpsc.ucalgary.ca (Abhishek Gaurav) Date: Tue, 27 Feb 2007 13:24:23 -0700 Subject: [Fedora-xen] Kernel compile Message-ID: <45E49377.5080202@cpsc.ucalgary.ca> Hi, I have the kernel-xen-devel 2.6.19-1.2895.fc6-xen-i686 package that I am trying to compile after inserting couple of parameters, CONFIG_IP_PNP and CONFIG_ROOT_NFS in the .config file. After 'make oldconfig', make fails like following: make[1]: *** No rule to make target `init/main.o', needed by `init/built-in.o'. Stop. make: *** [init] Error 2 Also, if I do, [root at ict720ac 2.6.19-1.2895.fc6-xen-i686]# ls init/ Kconfig Makefile Can anybody please let me know how to correct this. Thanks, Abhishek. From taoj2 at cs.rpi.edu Wed Feb 28 03:31:43 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Tue, 27 Feb 2007 22:31:43 -0500 (EST) Subject: [Fedora-xen] This is a test! Message-ID: <3329.128.213.51.15.1172633503.squirrel@webmail.cs.rpi.edu> From abrination at googlemail.com Wed Feb 28 13:25:43 2007 From: abrination at googlemail.com (Abri Nation) Date: Wed, 28 Feb 2007 14:25:43 +0100 Subject: [Fedora-xen] XEN, FC6 - two networkbridges, problems with ssh Message-ID: <387e65040702280525p3f3c4aa0hea2dab91f48ca1a6@mail.gmail.com> Hi @all, i got two networkdevices (eth0, eth1), and i want to use the eth1 for DMZ and eth0 for "normal" internetaccess, so i have to build to bridges. on default FC6 created this bridge and "brctl show" shows the following conifgured bridge: ----------------------------------------------------------------------------------------------- bridge name bridge id STP enabled interfaces xenbr1 8000.024103917534 no vif49.0 tap0 vif45.0 tap1 peth1 vif0.1 ----------------------------------------------------------------------------------------------- that bridge (xenbr1) i want to use know for DMZ. and the interface eth0 i want to create an new bridge for "normal" internetaccess, and my other VM. But if i will configure this, it will not longer be possible to connect to the XEN server with ssh (cause now, i could only connect the xen server on the eth0 interface with ssh. eth1 is not reachabel per ssh, cause of the bridging). My Questions are: 1. How could i build two bridges, one for DMZ and one for "normal" internetaccess, having acces per ssh? 2. Is this default that the bridge interface is not longer available for ssh? i thought in bridging interfaces, the IP is copied from the interface to an virtual interface (e.g. peth1), so it is possible to conntact the physical interface also? 3. using FC6 with virt-manager - where can i change the bridge or build a new one? only on the command line? (with the network.bridge script oder with "brctl"?) Could anyone tell me my failure, or the mistake on my part? Thank you very much for help! kind regards, Abri -------------- next part -------------- An HTML attachment was scrubbed... URL: From skipper at zinix.nl Tue Feb 27 17:56:52 2007 From: skipper at zinix.nl (Henk Altena) Date: Tue, 27 Feb 2007 18:56:52 +0100 Subject: [Fedora-xen] xen in fc6 Message-ID: <45E470E4.90804@zinix.nl> Hello everybody, I have two problems with xen and fc6 on a x86_64 AMD. The first problem: When I install on a new HD fc6 x86_64 WITH the program group VM then my pc is refusing to boot. The boot process stops with the message: udev and then hangs. After the above procedure I installed FC6 x86-64 WITHOUT xen. The machine boots normal. Now I install all the xen packages. At boot time I can choose now between the xen kernel and the 'normal' kernel. BUT when I make the xen kernel the default boot option the machine hangs again. So I make the 'normal' kernel the default which it was by default. Now I can boot both kernels without problems. So when the xen kernel is the default boot option or the only boot option the machine refuses to boot. Why ? My second problem is how to create a VM image: In this list I used the advice from Chris Tyler on booting from a network source in this case http. My URL is: http://192.168.0.1/FC_5, which is the ip adres of my FC_6-xen installation. The startup works ok untill the following error: "error: failed to retrieve FC_5/Fedora/base/stage2.img" I disabled SElinux. I can browse the dvd with Firefox. When I use nfs as a source as Adrian Revill pointed out I end up with the error: "That directory could not be mounted from the server" While the setup starts fine it seems to me the nfs setup is correct so there must be another problem ? What am I doing wrong ? Thanks in advance ! Henk From taoj2 at cs.rpi.edu Wed Feb 28 04:19:31 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Tue, 27 Feb 2007 23:19:31 -0500 (EST) Subject: [Fedora-xen] Problem about installing guesting OS with virt-manger of Fedora Core 6 Message-ID: <33516.128.213.11.196.1172636371.squirrel@webmail.cs.rpi.edu> Hi, I installed the Fedora Core 6 on my computer. Now I was trying to install the Fedora Core 6 guesting OS in my computer. I use the Virtual Machine Manager to do this. First, I create an empty file, box1, like this: cat > box1 I didn't type anthing into the file. SO the file is empty. (Is this a correct approach to create a file for the guesting OS storage space ?) Then I set the /home/jane/xen/box1 as the storage space to install my guesting OS. I chose Fedora COre 6 again as my guest os. The problem is: When the installation comes to selecting disk partition part, there is no available drive there. I print the screen and attached the picture. I get stucked there and can't continue the guest os installation. COuld you please give me some hint? THank you very much. Regards, Angel -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 132825 bytes Desc: not available URL: From berrange at redhat.com Wed Feb 28 14:22:08 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 28 Feb 2007 14:22:08 +0000 Subject: [Fedora-xen] Problem about installing guesting OS with virt-manger of Fedora Core 6 In-Reply-To: <33516.128.213.11.196.1172636371.squirrel@webmail.cs.rpi.edu> References: <33516.128.213.11.196.1172636371.squirrel@webmail.cs.rpi.edu> Message-ID: <20070228142208.GA9555@redhat.com> On Tue, Feb 27, 2007 at 11:19:31PM -0500, taoj2 at cs.rpi.edu wrote: > Hi, > > I installed the Fedora Core 6 on my computer. > > Now I was trying to install the Fedora Core 6 guesting OS in my computer. > I use the Virtual Machine Manager to do this. > > First, I create an empty file, box1, like this: > > cat > box1 I think you'll need more than 0 bytes in which to install the guest OS packages :-) > I didn't type anthing into the file. SO the file is empty. (Is this a > correct approach to create a file for the guesting OS storage space ?) Don't create the file manually - let virt-manager do it for you - it will give you option to specify the desired size & location > Then I set the /home/jane/xen/box1 as the storage space to install my > guesting OS. I chose Fedora COre 6 again as my guest os. The problem is: > When the installation comes to selecting disk partition part, there is no > available drive there. I print the screen and attached the picture. There is no drive because you created a zero byte file. Let virt-manager create it, in addition it needs to be under /var/lib/xen/images rather than /home. 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.revill at shazamteam.net Wed Feb 28 14:52:33 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Wed, 28 Feb 2007 14:52:33 +0000 Subject: [Fedora-xen] Problem about installing guesting OS with, virt-manger of Fedora Core 6 Message-ID: <45E59731.9060701@shazamteam.net> Hi Angel If i understand you, you are trying to use file backed storage in /home/jane/xen/box1 Try deleting the file /home/jane/xen/box1 and if it exists the file /etc/xen/box1 Then in the virt_manager enter the file name /home/jane/xen/box1 The file will be created and correctly formatted etc. regards Adrian From adrian.revill at shazamteam.net Wed Feb 28 15:04:24 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Wed, 28 Feb 2007 15:04:24 +0000 Subject: [Fedora-xen] xen in fc6 Message-ID: <45E599F8.1050904@shazamteam.net> Hi Henk, For the NFS problem, have you tried testing the nfs mount by mounting it back on Dom0 When i first set mine up i logged in as root on Dom0, created a dir called testmnt then mounted the nfs on it. In your case #mount 192.168.0.1:/fc_5 testmnt You should then see all of the install tree under testmnt The other thing, is look in /var/log/messages on Dom0, you should see the mount attempt from your DomU I also run with no firewall, is yours on? is it blocking the mounts? You other problem The startup works ok until the following error: "error: failed to retrieve FC_5/Fedora/base/stage2.img" I guess the file is actually there? try extracting it from CD again, maybe its corrupt. regards Adrian From adrian.revill at shazamteam.net Wed Feb 28 15:09:18 2007 From: adrian.revill at shazamteam.net (Adrian Revill) Date: Wed, 28 Feb 2007 15:09:18 +0000 Subject: [Fedora-xen] iSCSI root Message-ID: <45E59B1E.2000908@shazamteam.net> Hi Has anyone had any luck using iSCSI as the root device for a DomU. Is it possible to specify the target address in the virt-manager directly? as i have seen comments on google that it has to be mounted on Dom0 first. Which kinda defeats the object of virtual storage for virtual machines. If i was doing a straight FC6 install i could select an iSCSI target as the target drive. regards Adrian From berrange at redhat.com Wed Feb 28 15:17:37 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 28 Feb 2007 15:17:37 +0000 Subject: [Fedora-xen] iSCSI root In-Reply-To: <45E59B1E.2000908@shazamteam.net> References: <45E59B1E.2000908@shazamteam.net> Message-ID: <20070228151737.GC9555@redhat.com> On Wed, Feb 28, 2007 at 03:09:18PM +0000, Adrian Revill wrote: > Hi > Has anyone had any luck using iSCSI as the root device for a DomU. > > Is it possible to specify the target address in the virt-manager > directly? as i have seen comments on google that it has to be mounted on > Dom0 first. Which kinda defeats the object of virtual storage for > virtual machines. No you can't specify anything wrt to iSCSI in virt-manager. We only support creating guests which boot from a locally attached storage device - since pygrub has to access the disk in dom0 to etract the boot kernel & initrd. If you want to use iSCSI, then you'll need to create a diskless guest, and keep its kernel/initrd in dom0 rather than using pygrub. None of the tools are able to help with such a setup though, so its a mnual process. > If i was doing a straight FC6 install i could select an iSCSI target as > the target drive. Basically create yourself a guest config in /etc/xen, and have it explicitly boot the kernel/init you pull from $INSTALL_URL/images/xen to get started. Then after install copy the newer kernel / initrd back to 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 katzj at redhat.com Wed Feb 28 15:31:44 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 28 Feb 2007 10:31:44 -0500 Subject: [Fedora-xen] iSCSI root In-Reply-To: <45E59B1E.2000908@shazamteam.net> References: <45E59B1E.2000908@shazamteam.net> Message-ID: <1172676704.19660.15.camel@aglarond.local> On Wed, 2007-02-28 at 15:09 +0000, Adrian Revill wrote: > Has anyone had any luck using iSCSI as the root device for a DomU. Yes -- you just keep a small local[1] to dom0 disk image to use for /boot and then everything else can be over iSCSI. This is analagous to the (usual) need to set up PXE or similar for a physical machine to boot from when using a software iSCSI initiator. Jeremy [1] It can be a file on an nfs mount for the cheap answer to making moving the VM easy From taoj2 at cs.rpi.edu Wed Feb 28 18:06:24 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Wed, 28 Feb 2007 13:06:24 -0500 (EST) Subject: [Fedora-xen] Problem about installing guesting OS with virt-manger of Fedora Core 6 Message-ID: <1572.128.213.28.108.1172685984.squirrel@webmail.cs.rpi.edu> Hi, Thank you guys a lot. This time I didn't create the file manually. Just Let the virt-manager to do this. First, I try to use /home/jane/xen/box1, but it failed. So according to Dan's suggestion, I use /var/lib/xen/images/box1 as the storage location of guest OS. But why this file has to be under /var/lib/xen/images rather than /home? I didn't realize this problem when I was intalling the guesting OS before. Only /var/lib/xen/images is a valid directoy? Is there any other valid directory? And I found another problem even if I use /var/lib/xen/images/box1 : "The partition table on device xvda was unreachable. To create new partitions it must be initialized, causing the loss of All Data on this drive. This opeartion will override any previous installation choices about which drives to ignore. Would you like to initialize this drive, erasing ALL DATA? " So this means each time I want to install an guest OS, I have to create new partition? It seems not good. :( And I don't know how to solve this problem. This is the first time I use Fedora Core and XEN. I want to do some experiments about the VM migration with XEN. Do you guys have any idea of above problem? Thanks a lot. Regads, Angel From berrange at redhat.com Wed Feb 28 18:09:51 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 28 Feb 2007 18:09:51 +0000 Subject: [Fedora-xen] Re: Problem about installing guesting OS with virt-manger of Fedora Core 6 In-Reply-To: <1572.128.213.28.108.1172685984.squirrel@webmail.cs.rpi.edu> References: <1572.128.213.28.108.1172685984.squirrel@webmail.cs.rpi.edu> Message-ID: <20070228180951.GN9555@redhat.com> On Wed, Feb 28, 2007 at 01:06:24PM -0500, taoj2 at cs.rpi.edu wrote: > Hi, > > Thank you guys a lot. > > This time I didn't create the file manually. Just Let the virt-manager to > do this. First, I try to use /home/jane/xen/box1, but it failed. > > So according to Dan's suggestion, I use /var/lib/xen/images/box1 as the > storage location of guest OS. > > But why this file has to be under /var/lib/xen/images rather than /home? I > didn't realize this problem when I was intalling the guesting OS before. > Only /var/lib/xen/images is a valid directoy? Is there any other valid > directory? Yes, it has to be in that directoy to comply with the SELinux security policy - we don't want to let XenD write all over the disk. > And I found another problem even if I use /var/lib/xen/images/box1 : > > "The partition table on device xvda was unreachable. To create new > partitions it must be initialized, causing the loss of All Data on this > drive. This opeartion will override any previous installation choices > about which drives to ignore. Would you like to initialize this drive, > erasing ALL DATA? > " > > So this means each time I want to install an guest OS, I have to create > new partition? It seems not good. :( This is completely expected & normal behaviour. The '/var/lib/xen/image/box1' file in the host, is exposed to the guest as a *disk*. So anaconda sees this disk and wants to partition it - this is same thing you'd see if running anaconda on a bare-metal machine with a brandnew harddisk which hadn't been partitioned before. Simply say 'yes', and it'll create the neccessary bits. 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 taoj2 at cs.rpi.edu Wed Feb 28 18:58:20 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Wed, 28 Feb 2007 13:58:20 -0500 (EST) Subject: [Fedora-xen] Live Virtual Machine Migration with XEN in Fedora Core 6 Message-ID: <1726.128.213.28.108.1172689100.squirrel@webmail.cs.rpi.edu> Hi, I wanna do some experiments of Live VM Migration with XEN in Fedora Core 6. Is there anybody know whether the XEN in Fedora Core support live migration or not? Thanks. Regards, Angel From jklein at saugus.k12.ca.us Wed Feb 28 20:01:05 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Wed, 28 Feb 2007 12:01:05 -0800 (PST) Subject: [Fedora-xen] NAT Problem Message-ID: <5438853.439271172692865596.JavaMail.root@do8> This may not be specifically a xen problem, but I am having an issue with running a xen vm as a NAT gateway. Basically, the situation is this: Dom0 is set up with 2 bridged ports, xenbr0 and xenbr1. xenbr0 is on the public network and xenbr1 is on the private (10.x.x.x). DomU #1 is setup as a router using both interfaces, eth0 public (xenbr0) and eth1 private (xenbr1) with NAT via iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE. Now, if I bring up another DomU (#2) on the same box with only 1 interface (eth0) on xenbr0, it is completely inaccessible by machines routing through DomU #1. However, ssh into DomU#1, then ssh into DomU#2 from the DomU#1 console works. Further, if I migrate DomU#2 to another box, it is suddenly accessible to machined routing through DomU#1. Thanks in advance for any help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gaurav at cpsc.ucalgary.ca Wed Feb 28 22:46:11 2007 From: gaurav at cpsc.ucalgary.ca (Abhishek Gaurav) Date: Wed, 28 Feb 2007 15:46:11 -0700 Subject: [Fedora-xen] Win Xp 64 bit install Message-ID: <45E60633.40705@cpsc.ucalgary.ca> Hi, I am trying to install windows xp 64 bit (trial version) using virt-install on a fc6 system. The installation seems to stall when the message in the vnc console says "Setup is starting windows". The xm dmesg shows: (XEN) (GUEST: 13) Booting from CD-Rom... (XEN) (GUEST: 13) unsupported PCI BIOS function 0x0E (XEN) (GUEST: 13) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) (GUEST: 13) *** int 15h function AX=E980, BX=00F2 not yet supported! (XEN) (GUEST: 13) *** int 15h function AX=EC00, BX=0002 not yet supported! (XEN) Trying to set reserved bit in EFER: 4d01 The last message "Trying to set ... " actually comes up just before it stalls. What might be causing this ? I have also tried to install an older Win Xp home sp1, which actually goes past the above messages (without "trying to set ...") but ends up in the famous black screen upon first reboot. It'll be great to know what might be causing the above problems. Thanks, Abhishek.