Hi, I am trying to boot a freshly installed DomU (using xen-tools and rinse) of CentOS 5 64bit. It starts booting the operating system but it freezes every time after starting SSH:> INIT: version 2.86 booting > Welcome to CentOS release 5.2 (Final) > Press ''I'' to enter interactive startup. > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access > method. > Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ] > Starting udev: [ OK ] > Setting hostname test4: [ OK ] > Checking filesystems > Checking all file systems. > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2 > /dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > Mounting local filesystems: [ OK ] > Enabling /etc/fstab swaps: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Mounting other filesystems: [ OK ] > Starting sshd: [ OK ]Nothing comes up, it just stops there. I have tried mounting the HDD image of the domU on my host to access the log files but there does not appear to be anything of use. This is the dmesg log file on the domU:> Bootdata ok (command line is root=/dev/sda2 ro ) > Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org) > (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16 > 12:26:32 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000020800000 (usable) > On node 0 totalpages: 133120 > DMA zone: 133120 pages, LIFO batch:31 > No mptable found. > Built 1 zonelists. Total pages: 133120 > Kernel command line: root=/dev/sda2 ro > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 32768 bytes) > Xen reported: 2833.530 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) > Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) > Software IO TLB disabled > Memory: 500992k/532480k available (2418k kernel code, 22768k reserved, > 1353k data, 176k init) > Calibrating delay using timer specific routine.. 7087.48 BogoMIPS > (lpj=14174967) > 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: 256 > , L1 D cache: 32K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 0 > (SMP-)alternatives turned off > Brought up 1 CPUs > sizeof(vma)=168 bytes > sizeof(page)=56 bytes > sizeof(inode)=560 bytes > sizeof(dentry)=216 bytes > sizeof(ext3inode)=760 bytes > sizeof(buffer_head)=96 bytes > sizeof(skbuff)=240 bytes > checking if image is initramfs... it is > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could > not acquire Mutex [2] [20060707] > No dock devices found. > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could > not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: Fatal: No PCI 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 driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > TCP established hash table entries: 131072 (order: 9, 2097152 bytes) > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1238443140.218:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key 6D65AF37871D9CBE > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > Probing IDE interface ide0... > Probing IDE interface ide1... > Probing IDE interface ide2... > Probing IDE interface ide3... > Probing IDE interface ide4... > Probing IDE interface ide5... > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/console/0 > Write protecting the kernel read-only data: 461k > Registering block device major 8 > ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver (PCI) > USB Universal Host Controller Interface driver v3.0 > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > Fusion MPT base driver 3.04.05 > Copyright (c) 1999-2007 LSI Corporation > Fusion MPT SAS Host driver 3.04.05 > libata version 3.00 loaded. > netfront: Initialising virtual ethernet driver. > netfront: device eth0 has flipping receive path. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > input: PC Speaker as /class/input/input0 > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 > (usb?) > Failed to obtain physical IRQ 6 > floppy0: no floppy controllers found > lp: driver loaded but no devices found > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: > dm-devel@redhat.com > EXT3 FS on sda2, internal journal > Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064kI can''t recognise any serious errors in there. Could someone please help me? Cheers, Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Xen virtual console successfully installed as xvc0Try to boot with extre=''xencons=tty'' in config file or xencons=tty in kernel line when using pygrub. BR, Carsten. ----- Originalnachricht ----- Von: Andrew Kilham <andrew@estyles.com.au> Gesendet: Mon, 30.3.2009 14:03 An: xen-users@lists.xensource.com Betreff: [Xen-users] DomU freezes during boot Hi, I am trying to boot a freshly installed DomU (using xen-tools and rinse) of CentOS 5 64bit. It starts booting the operating system but it freezes every time after starting SSH:> INIT: version 2.86 booting > Welcome to CentOS release 5.2 (Final) > Press ''I'' to enter interactive startup. > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access > method. > Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ] > Starting udev: [ OK ] > Setting hostname test4: [ OK ] > Checking filesystems > Checking all file systems. > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2 > /dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > Mounting local filesystems: [ OK ] > Enabling /etc/fstab swaps: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Mounting other filesystems: [ OK ] > Starting sshd: [ OK ]Nothing comes up, it just stops there. I have tried mounting the HDD image of the domU on my host to access the log files but there does not appear to be anything of use. This is the dmesg log file on the domU:> Bootdata ok (command line is root=/dev/sda2 ro ) > Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org) > (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16 > 12:26:32 EST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000020800000 (usable) > On node 0 totalpages: 133120 > DMA zone: 133120 pages, LIFO batch:31 > No mptable found. > Built 1 zonelists. Total pages: 133120 > Kernel command line: root=/dev/sda2 ro > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 32768 bytes) > Xen reported: 2833.530 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) > Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) > Software IO TLB disabled > Memory: 500992k/532480k available (2418k kernel code, 22768k reserved, > 1353k data, 176k init) > Calibrating delay using timer specific routine.. 7087.48 BogoMIPS > (lpj=14174967) > 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: 256 > , L1 D cache: 32K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 0 > (SMP-)alternatives turned off > Brought up 1 CPUs > sizeof(vma)=168 bytes > sizeof(page)=56 bytes > sizeof(inode)=560 bytes > sizeof(dentry)=216 bytes > sizeof(ext3inode)=760 bytes > sizeof(buffer_head)=96 bytes > sizeof(skbuff)=240 bytes > checking if image is initramfs... it is > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could > not acquire Mutex [2] [20060707] > No dock devices found. > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could > not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: Fatal: No PCI 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 driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > TCP established hash table entries: 131072 (order: 9, 2097152 bytes) > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > audit: initializing netlink socket (disabled) > audit(1238443140.218:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key 6D65AF37871D9CBE > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > Probing IDE interface ide0... > Probing IDE interface ide1... > Probing IDE interface ide2... > Probing IDE interface ide3... > Probing IDE interface ide4... > Probing IDE interface ide5... > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/console/0 > Write protecting the kernel read-only data: 461k > Registering block device major 8 > ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver (PCI) > USB Universal Host Controller Interface driver v3.0 > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > Fusion MPT base driver 3.04.05 > Copyright (c) 1999-2007 LSI Corporation > Fusion MPT SAS Host driver 3.04.05 > libata version 3.00 loaded. > netfront: Initialising virtual ethernet driver. > netfront: device eth0 has flipping receive path. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > input: PC Speaker as /class/input/input0 > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 > (usb?) > Failed to obtain physical IRQ 6 > floppy0: no floppy controllers found > lp: driver loaded but no devices found > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: > dm-devel@redhat.com > EXT3 FS on sda2, internal journal > Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064kI can''t recognise any serious errors in there. Could someone please help me? Cheers, Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I have put that line in to the config file but now it freezes even before it starts to boot the OS. Here is the complete output after running xm create with "extra = ''xencons=tty''" in my config file:> [root@localhost vm]# xm create -c test4.cfg > Using config file "/etc/xen/test4.cfg". > Started domain test4 > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/console/0 > Write protecting the kernel read-only data: 461k > Registering block device major 8 > USB Universal Host Controller Interface driver v3.0 > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > Fusion MPT base driver 3.04.05 > Copyright (c) 1999-2007 LSI Corporation > Fusion MPT SAS Host driver 3.04.05 > netfront: Initialising virtual ethernet driver. > netfront: device eth0 has flipping receive path. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode.However, an update: I just tried booting it in to different run-levels using the ''extra'' command in the config file, and it will boot in to run-level 1 but nothing higher. Still nothing in the log files or anything though. Cheers, Andrew Carsten Schiers wrote:> Hi, > > >> Xen virtual console successfully installed as xvc0 >> > > Try to boot with extre=''xencons=tty'' in config file or xencons=tty in > kernel line when using pygrub. > > BR, > Carsten. > > ----- Originalnachricht ----- > Von: Andrew Kilham <andrew@estyles.com.au> > Gesendet: Mon, 30.3.2009 14:03 > An: xen-users@lists.xensource.com > Betreff: [Xen-users] DomU freezes during boot > > Hi, > > I am trying to boot a freshly installed DomU (using xen-tools and rinse) > of CentOS 5 64bit. It starts booting the operating system but it freezes > every time after starting SSH: > > >> INIT: version 2.86 booting >> Welcome to CentOS release 5.2 (Final) >> Press ''I'' to enter interactive startup. >> Cannot access the Hardware Clock via any known method. >> Use the --debug option to see the details of our search for an access >> method. >> Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ] >> Starting udev: [ OK ] >> Setting hostname test4: [ OK ] >> Checking filesystems >> Checking all file systems. >> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2 >> /dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks >> [ OK ] >> Remounting root filesystem in read-write mode: [ OK ] >> Mounting local filesystems: [ OK ] >> Enabling /etc/fstab swaps: [ OK ] >> INIT: Entering runlevel: 3 >> Entering non-interactive startup >> Bringing up loopback interface: [ OK ] >> Bringing up interface eth0: [ OK ] >> Mounting other filesystems: [ OK ] >> Starting sshd: [ OK ] >> > Nothing comes up, it just stops there. I have tried mounting the HDD > image of the domU on my host to access the log files but there does not > appear to be anything of use. This is the dmesg log file on the domU: > > >> Bootdata ok (command line is root=/dev/sda2 ro ) >> Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org) >> (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16 >> 12:26:32 EST 2008 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000020800000 (usable) >> On node 0 totalpages: 133120 >> DMA zone: 133120 pages, LIFO batch:31 >> No mptable found. >> Built 1 zonelists. Total pages: 133120 >> Kernel command line: root=/dev/sda2 ro >> Initializing CPU#0 >> PID hash table entries: 4096 (order: 12, 32768 bytes) >> Xen reported: 2833.530 MHz processor. >> Console: colour dummy device 80x25 >> Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) >> Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) >> Software IO TLB disabled >> Memory: 500992k/532480k available (2418k kernel code, 22768k reserved, >> 1353k data, 176k init) >> Calibrating delay using timer specific routine.. 7087.48 BogoMIPS >> (lpj=14174967) >> 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: 256 >> , L1 D cache: 32K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 0 >> (SMP-)alternatives turned off >> Brought up 1 CPUs >> sizeof(vma)=168 bytes >> sizeof(page)=56 bytes >> sizeof(inode)=560 bytes >> sizeof(dentry)=216 bytes >> sizeof(ext3inode)=760 bytes >> sizeof(buffer_head)=96 bytes >> sizeof(skbuff)=240 bytes >> checking if image is initramfs... it is >> Grant table initialized >> NET: Registered protocol family 16 >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could >> not acquire Mutex [2] [20060707] >> No dock devices found. >> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could >> not acquire Mutex [2] [20060707] >> Brought up 1 CPUs >> PCI: Fatal: No PCI 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 driver usbfs >> usbcore: registered new driver hub >> PCI: System does not support PCI >> PCI: System does not support PCI >> NetLabel: Initializing >> NetLabel: domain hash size = 128 >> NetLabel: protocols = UNLABELED CIPSOv4 >> NetLabel: unlabeled traffic allowed by default >> NET: Registered protocol family 2 >> IP route cache hash table entries: 32768 (order: 6, 262144 bytes) >> TCP established hash table entries: 131072 (order: 9, 2097152 bytes) >> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) >> TCP: Hash tables configured (established 131072 bind 65536) >> TCP reno registered >> audit: initializing netlink socket (disabled) >> audit(1238443140.218:1): initialized >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> SELinux: Registering netfilter hooks >> Initializing Cryptographic API >> ksign: Installing public key data >> Loading keyring >> - Added public key 6D65AF37871D9CBE >> - User ID: CentOS (Kernel Module GPG key) >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >> rtc: IRQ 8 is not free. >> Non-volatile memory driver v1.2 >> Linux agpgart interface v0.101 (c) Dave Jones >> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >> Xen virtual console successfully installed as xvc0 >> Event-channel device installed. >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with >> idebus=xx >> Probing IDE interface ide0... >> Probing IDE interface ide1... >> Probing IDE interface ide2... >> Probing IDE interface ide3... >> Probing IDE interface ide4... >> Probing IDE interface ide5... >> ide-floppy driver 0.99.newide >> usbcore: registered new driver hiddev >> usbcore: registered new driver usbhid >> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> md: bitmap version 4.39 >> TCP bic registered >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vbd/2050 >> XENBUS: Device with no driver: device/vbd/2049 >> XENBUS: Device with no driver: device/vif/0 >> XENBUS: Device with no driver: device/console/0 >> Write protecting the kernel read-only data: 461k >> Registering block device major 8 >> ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver (PCI) >> USB Universal Host Controller Interface driver v3.0 >> SCSI subsystem initialized >> register_blkdev: cannot get major 8 for sd >> Fusion MPT base driver 3.04.05 >> Copyright (c) 1999-2007 LSI Corporation >> Fusion MPT SAS Host driver 3.04.05 >> libata version 3.00 loaded. >> netfront: Initialising virtual ethernet driver. >> netfront: device eth0 has flipping receive path. >> kjournald starting. Commit interval 5 seconds >> EXT3-fs: mounted filesystem with ordered data mode. >> input: PC Speaker as /class/input/input0 >> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 >> (usb?) >> Failed to obtain physical IRQ 6 >> floppy0: no floppy controllers found >> lp: driver loaded but no devices found >> device-mapper: uevent: version 1.0.3 >> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: >> dm-devel@redhat.com >> EXT3 FS on sda2, internal journal >> Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064k >> > I can''t recognise any serious errors in there. Could someone please help me? > > Cheers, > > Andrew > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09 16:56:00 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2009/3/30 Andrew Kilham <andrew@estyles.com.au>:> Fusion MPT base driver 3.04.05 > Copyright (c) 1999-2007 LSI Corporation > Fusion MPT SAS Host driver 3.04.05This is odd. Why would a domU need MPT driver?> However, an update: I just tried booting it in to different run-levels using > the ''extra'' command in the config file, and it will boot in to run-level 1 > but nothing higher. Still nothing in the log files or anything though.Can you post the lines of domU''s /etc/inittab which has "tty" on it? You need to have something like this co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here is my complete /etc/inittab file on domU:> sh-3.2# cat inittab > # > # inittab This file describes how the INIT process should set up > # the system in a certain run-level. > # > # Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org> > # Modified for RHS Linux by Marc Ewing and Donnie Barnes > # > > # Default runlevel. The runlevels used by RHS are: > # 0 - halt (Do NOT set initdefault to this) > # 1 - Single user mode > # 2 - Multiuser, without NFS (The same as 3, if you do not have > networking) > # 3 - Full multiuser mode > # 4 - unused > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > id:3:initdefault: > > # System initialization. > si::sysinit:/etc/rc.d/rc.sysinit > > l0:0:wait:/etc/rc.d/rc 0 > l1:1:wait:/etc/rc.d/rc 1 > l2:2:wait:/etc/rc.d/rc 2 > l3:3:wait:/etc/rc.d/rc 3 > l4:4:wait:/etc/rc.d/rc 4 > l5:5:wait:/etc/rc.d/rc 5 > l6:6:wait:/etc/rc.d/rc 6 > > # Trap CTRL-ALT-DELETE > ca::ctrlaltdel:/sbin/shutdown -t3 -r now > > # When our UPS tells us power has failed, assume we have a few minutes > # of power left. Schedule a shutdown for 2 minutes from now. > # This does, of course, assume you have powerd installed and your > # UPS connected and working correctly. > pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting > Down" > > # If power was restored before the shutdown kicked in, cancel it. > pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown > Cancelled" > > > # Run gettys in standard runlevels > 1:2345:respawn:/sbin/mingetty tty1 > #2:2345:respawn:/sbin/mingetty tty2 > #3:2345:respawn:/sbin/mingetty tty3 > #4:2345:respawn:/sbin/mingetty tty4 > #5:2345:respawn:/sbin/mingetty tty5 > #6:2345:respawn:/sbin/mingetty tty6 > > # Run xdm in runlevel 5 > x:5:respawn:/etc/X11/prefdm -nodaemonNothing like the line you said. Should I add it in exactly as you typed it? Cheers, Andrew Fajar A. Nugraha wrote:> 2009/3/30 Andrew Kilham <andrew@estyles.com.au>: > >> Fusion MPT base driver 3.04.05 >> Copyright (c) 1999-2007 LSI Corporation >> Fusion MPT SAS Host driver 3.04.05 >> > > This is odd. Why would a domU need MPT driver? > > >> However, an update: I just tried booting it in to different run-levels using >> the ''extra'' command in the config file, and it will boot in to run-level 1 >> but nothing higher. Still nothing in the log files or anything though. >> > > Can you post the lines of domU''s /etc/inittab which has "tty" on it? > You need to have something like this > > co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav > > Regards, > > Fajar > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09 16:56:00 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Could you post
1. test4.cfg
2. xm info (at Dom0)
--- On Mon, 3/30/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Carsten Schiers" <carsten@schiers.de>
Cc: xen-users@lists.xensource.com
Date: Monday, March 30, 2009, 8:30 AM
Hi,
I have put that line in to the config file but now it freezes even
before it starts to boot the OS. Here is the complete output after
running xm create with "extra = ''xencons=tty''" in my
config file:
[root@localhost vm]# xm create -c test4.cfg
Using config file "/etc/xen/test4.cfg".
Started domain test4
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
However, an update: I just tried booting it in to different run-levels
using the ''extra'' command in the config file, and it will boot
in to
run-level 1 but nothing higher. Still nothing in the log files or
anything though.
Cheers,
Andrew
Carsten Schiers wrote:
Hi,
Xen virtual console successfully installed as xvc0
Try to boot with extre=''xencons=tty'' in config file or
xencons=tty in
kernel line when using pygrub.
BR,
Carsten.
----- Originalnachricht -----
Von: Andrew Kilham <andrew@estyles.com.au>
Gesendet: Mon, 30.3.2009 14:03
An: xen-users@lists.xensource.com
Betreff: [Xen-users] DomU freezes during boot
Hi,
I am trying to boot a freshly installed DomU (using xen-tools and rinse)
of CentOS 5 64bit. It starts booting the operating system but it freezes
every time after starting SSH:
INIT: version 2.86 booting
Welcome to CentOS release 5.2 (Final)
Press ''I'' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ]
Starting udev: [ OK ]
Setting hostname test4: [ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2
/dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Mounting other filesystems: [ OK ]
Starting sshd: [ OK ]
Nothing comes up, it just stops there. I have tried mounting the HDD
image of the domU on my host to access the log files but there does not
appear to be anything of use. This is the dmesg log file on the domU:
Bootdata ok (command line is root=/dev/sda2 ro )
Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org)
(gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16
12:26:32 EST 2008
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020800000 (usable)
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
No mptable found.
Built 1 zonelists. Total pages: 133120
Kernel command line: root=/dev/sda2 ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2833.530 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Software IO TLB disabled
Memory: 500992k/532480k available (2418k kernel code, 22768k reserved,
1353k data, 176k init)
Calibrating delay using timer specific routine.. 7087.48 BogoMIPS
(lpj=14174967)
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: 256
, L1 D cache: 32K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
(SMP-)alternatives turned off
Brought up 1 CPUs
sizeof(vma)=168 bytes
sizeof(page)=56 bytes
sizeof(inode)=560 bytes
sizeof(dentry)=216 bytes
sizeof(ext3inode)=760 bytes
sizeof(buffer_head)=96 bytes
sizeof(skbuff)=240 bytes
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: Fatal: No PCI 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 driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1238443140.218:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 6D65AF37871D9CBE
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI)
Driver (PCI)
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
libata version 3.00 loaded.
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input0
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers found
lp: driver loaded but no devices found
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
EXT3 FS on sda2, internal journal
Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064k
I can''t recognise any serious errors in there. Could someone please
help me?
Cheers,
Andrew
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09
16:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Looks like you install RHEL PV DomU at RHEL Dom0.
If this is a case it''s possible to survive without xen-tools &
rinse :)
supposed to help at Debian Dom0s :-
Insert your CentOS 5 DVD in the drive. Run "df -h" to find out what
mount point is. Suppose, it is /dev/hde
# dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso
# dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000
# mkdir -p /mnt/tmp
# mount -o loop,ro /etc/xen/disks/CentOS5.iso /mnt/tmp
Edit /etc/exports and add the line:-
/mnt/tmp
Restart Service "nfsd"
# virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img \
-l nfs:IP-Dom0:/mnt/tmp
or
1.To install your CentOS 5 DomU , at the command prompt type: virt-install.
2.When asked to install a fully virtualized guest, type: no.
3.Type CentOS5pv for your virtual machine name.
4.Type 1000 for your RAM allocation.
5.Type /etc/xen/images/CentOS5.img for your disk (guest image).
6.Type 12000 for the size of your disk (guest image).
7.Type yes to enable graphics support.
8.Type nfs:<IP address of Dom0>:/mnt/tmp for your install location.
The installation begins. Proceed as normal with the installation
--- On Mon, 3/30/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Carsten Schiers" <carsten@schiers.de>, "Andrew
Kilham" <andrew@estyles.com.au>
Cc: xen-users@lists.xensource.com
Date: Monday, March 30, 2009, 11:24 AM
Could you post
1. test4.cfg
2. xm info (at Dom0)
--- On Mon, 3/30/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Carsten Schiers" <carsten@schiers.de>
Cc: xen-users@lists.xensource.com
Date: Monday, March 30, 2009, 8:30 AM
Hi,
I have put that line in to the config file but now it freezes even
before it starts to boot the OS. Here is the complete output after
running xm create with "extra = ''xencons=tty''" in my
config file:
[root@localhost vm]# xm create -c test4.cfg
Using config file "/etc/xen/test4.cfg".
Started domain test4
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
However, an update: I just tried booting it in to different run-levels
using the ''extra'' command in the config file, and it will boot
in to
run-level 1 but nothing higher. Still nothing in the log files or
anything though.
Cheers,
Andrew
Carsten Schiers wrote:
Hi,
Xen virtual console successfully installed as xvc0
Try to boot with extre=''xencons=tty'' in config file or
xencons=tty in
kernel line when using pygrub.
BR,
Carsten.
----- Originalnachricht -----
Von: Andrew Kilham <andrew@estyles.com.au>
Gesendet: Mon, 30.3.2009 14:03
An: xen-users@lists.xensource.com
Betreff: [Xen-users] DomU freezes during boot
Hi,
I am trying to boot a freshly installed DomU (using xen-tools and rinse)
of CentOS 5 64bit. It starts booting the operating system but it freezes
every time after starting SSH:
INIT: version 2.86 booting
Welcome to CentOS release 5.2 (Final)
Press ''I'' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ]
Starting udev: [ OK ]
Setting hostname test4: [ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2
/dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Mounting other filesystems: [ OK ]
Starting sshd: [ OK ]
Nothing comes up, it just stops there. I have tried mounting the HDD
image of the domU on my host to access the log files but there does not
appear to be anything of use. This is the dmesg log file on the domU:
Bootdata ok (command line is root=/dev/sda2 ro )
Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org)
(gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16
12:26:32 EST 2008
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020800000 (usable)
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
No mptable found.
Built 1 zonelists. Total pages: 133120
Kernel command line: root=/dev/sda2 ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2833.530 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Software IO TLB disabled
Memory: 500992k/532480k available
(2418k kernel code, 22768k reserved,
1353k data, 176k init)
Calibrating delay using timer specific routine.. 7087.48 BogoMIPS
(lpj=14174967)
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: 256
, L1 D cache: 32K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
(SMP-)alternatives turned off
Brought up 1 CPUs
sizeof(vma)=168 bytes
sizeof(page)=56 bytes
sizeof(inode)=560 bytes
sizeof(dentry)=216 bytes
sizeof(ext3inode)=760 bytes
sizeof(buffer_head)=96 bytes
sizeof(skbuff)=240 bytes
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2]
[20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: Fatal: No PCI 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 driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576
bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1238443140.218:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 6D65AF37871D9CBE
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device
installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver:
device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI)
Driver (PCI)
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
libata version 3.00 loaded.
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input0
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers
found
lp: driver loaded but no devices found
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
EXT3 FS on sda2, internal journal
Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064k
I can''t recognise any serious errors in there. Could someone please
help me?
Cheers,
Andrew
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09
16:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi, Here is ''xm info'':> [root@localhost ~]# xm info > host : localhost.localdomain > release : 2.6.18-92.1.22.el5xen > version : #1 SMP Tue Dec 16 12:26:32 EST 2008 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2833 > hw_caps : > bfebfbff:20100800:00000000:00000140:0408e3fd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 8190 > free_memory : 128 > node_to_cpu : node0:0-3 > node_to_memory : node0:128 > xen_major : 3 > xen_minor : 3 > xen_extra : .0 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42) > cc_compile_by : root > cc_compile_domain : labor.lan > cc_compile_date : Tue Sep 9 20:18:14 CEST 2008 > xend_config_format : 4And here is test4.cfg:> [root@localhost ~]# cat /etc/xen/test4.cfg > # > # Configuration file for the Xen instance test4, created > # by xen-tools 4.1 on Tue Mar 31 02:30:20 2009. > # > > # > # Kernel + memory size > # > kernel = ''/boot/vmlinuz-2.6.18-92.1.22.el5xen'' > #ramdisk = ''/boot/initrd.img-2.6.18-92.1.22.el5xen'' > ramdisk = ''/boot/initrd-2.6.18-92.1.22.el5xen-xenblk.img'' > > memory = ''512'' > > # > # Disk device(s). > # > root = ''/dev/sda2 ro'' > disk = [ > ''file:/vm/domains/test4/disk.img,sda2,w'', > ''file:/vm/domains/test4/swap.img,sda1,w'', > ] > > > > > > extra = ''1'' > #extra = ''xencons=tty'' > > # > # Physical volumes > # > > > > # > # Hostname > # > name = ''test4'' > > # > # Networking > # > vif = [ ''ip=10.0.0.84,mac=00:16:3E:98:19:66'' ] > > # > # Behaviour > # > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart''Cheers, Andrew Boris Derzhavets wrote:> Could you post > 1. test4.cfg > 2. xm info (at Dom0) > > --- On *Mon, 3/30/09, Andrew Kilham /<andrew@estyles.com.au>/* wrote: > > From: Andrew Kilham <andrew@estyles.com.au> > Subject: Re: AW: [Xen-users] DomU freezes during boot > To: "Carsten Schiers" <carsten@schiers.de> > Cc: xen-users@lists.xensource.com > Date: Monday, March 30, 2009, 8:30 AM > > Hi, > > I have put that line in to the config file but now it freezes even > before it starts to boot the OS. Here is the complete output after > running xm create with "extra = ''xencons=tty''" in my config file: > >> [root@localhost vm]# xm create -c test4.cfg >> Using config file "/etc/xen/test4.cfg". >> Started domain test4 >> ide-floppy driver 0.99.newide >> usbcore: registered new driver hiddev >> usbcore: registered new driver usbhid >> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> md: bitmap version 4.39 >> TCP bic registered >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vbd/2050 >> XENBUS: Device with no driver: device/vbd/2049 >> XENBUS: Device with no driver: device/vif/0 >> XENBUS: Device with no driver: device/console/0 >> Write protecting the kernel read-only data: 461k >> Registering block device major 8 >> USB Universal Host Controller Interface driver v3.0 >> SCSI subsystem initialized >> register_blkdev: cannot get major 8 for sd >> Fusion MPT base driver 3.04.05 >> Copyright (c) 1999-2007 LSI Corporation >> Fusion MPT SAS Host driver 3.04.05 >> netfront: Initialising virtual ethernet driver. >> netfront: device eth0 has flipping receive path. >> kjournald starting. Commit interval 5 seconds >> EXT3-fs: mounted filesystem with ordered data mode. > However, an update: I just tried booting it in to different > run-levels using the ''extra'' command in the config file, and it > will boot in to run-level 1 but nothing higher. Still nothing in > the log files or anything though. > > Cheers, > > Andrew > > > Carsten Schiers wrote: >> Hi, >> >> >>> Xen virtual console successfully installed as xvc0 >>> >> Try to boot with extre=''xencons=tty'' in config file or xencons=tty in >> kernel line when using pygrub. >> >> BR, >> Carsten. >> >> ----- Originalnachricht ----- >> Von: Andrew Kilham <andrew@estyles.com.au> >> Gesendet: Mon, 30.3.2009 14:03 >> An: xen-users@lists.xensource.com >> Betreff: [Xen-users] DomU freezes during boot >> >> Hi, >> >> I am trying to boot a freshly installed DomU (using xen-tools and rinse) >> of CentOS 5 64bit. It starts booting the operating system but it freezes >> every time after starting SSH: >> >> >>> INIT: version 2.86 booting >>> Welcome to CentOS release 5.2 (Final) >>> Press ''I'' to enter interactive startup. >>> Cannot access the Hardware Clock via any known method. >>> Use the --debug option to see the details of our search for an access >>> method. >>> Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ] >>> Starting udev: [ OK ] >>> Setting hostname test4: [ OK ] >>> Checking filesystems >>> Checking all file systems. >>> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2 >>> /dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks >>> [ OK ] >>> Remounting root filesystem in read-write mode: [ OK ] >>> Mounting local filesystems: [ OK ] >>> Enabling /etc/fstab swaps: [ OK ] >>> INIT: Entering runlevel: 3 >>> Entering non-interactive startup >>> Bringing up loopback interface: [ OK ] >>> Bringing up interface eth0: [ OK ] >>> Mounting other filesystems: [ OK ] >>> Starting sshd: [ OK ] >>> >>> >> Nothing comes up, it just stops there. I have tried mounting the HDD >> image of the domU on my host to access the log files but there does not >> appear to be anything of use. This is the dmesg log file on the domU: >> >> >>> Bootdata ok (command line is root=/dev/sda2 ro ) >>> Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org) >>> (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16 >>> 12:26:32 EST 2008 >>> BIOS-provided physical RAM map: >>> Xen: 0000000000000000 - 0000000020800000 (usable) >>> On node 0 totalpages: 133120 >>> DMA zone: 133120 pages, LIFO batch:31 >>> No mptable found. >>> Built 1 zonelists. Total pages: 133120 >>> Kernel command line: root=/dev/sda2 ro >>> Initializing CPU#0 >>> PID hash table entries: 4096 (order: 12, 32768 bytes) >>> Xen reported: 2833.530 MHz processor. >>> Console: colour dummy device 80x25 >>> Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) >>> Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) >>> Software IO TLB disabled >>> Memory: 500992k/532480k available >>> (2418k kernel code, 22768k reserved, >>> 1353k data, 176k init) >>> Calibrating delay using timer specific routine.. 7087.48 BogoMIPS >>> (lpj=14174967) >>> 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: 256 >>> , L1 D cache: 32K >>> CPU: Physical Processor ID: 0 >>> CPU: Processor Core ID: 0 >>> (SMP-)alternatives turned off >>> Brought up 1 CPUs >>> sizeof(vma)=168 bytes >>> sizeof(page)=56 bytes >>> sizeof(inode)=560 bytes >>> sizeof(dentry)=216 bytes >>> sizeof(ext3inode)=760 bytes >>> sizeof(buffer_head)=96 bytes >>> sizeof(skbuff)=240 bytes >>> checking if image is initramfs... it is >>> Grant table initialized >>> NET: Registered protocol family 16 >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could >>> not acquire Mutex [2] >>> [20060707] >>> No dock devices found. >>> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could >>> not acquire Mutex [2] [20060707] >>> Brought up 1 CPUs >>> PCI: Fatal: No PCI 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 driver usbfs >>> usbcore: registered new driver hub >>> PCI: System does not support PCI >>> PCI: System does not support PCI >>> NetLabel: Initializing >>> NetLabel: domain hash size = 128 >>> NetLabel: protocols = UNLABELED CIPSOv4 >>> NetLabel: unlabeled traffic allowed by default >>> NET: Registered protocol family 2 >>> IP route cache hash table entries: 32768 (order: 6, 262144 bytes) >>> TCP established hash table entries: 131072 (order: 9, 2097152 bytes) >>> TCP bind hash table entries: 65536 (order: 8, 1048576 >>> bytes) >>> TCP: Hash tables configured (established 131072 bind 65536) >>> TCP reno registered >>> audit: initializing netlink socket (disabled) >>> audit(1238443140.218:1): initialized >>> VFS: Disk quotas dquot_6.5.1 >>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>> SELinux: Registering netfilter hooks >>> Initializing Cryptographic API >>> ksign: Installing public key data >>> Loading keyring >>> - Added public key 6D65AF37871D9CBE >>> - User ID: CentOS (Kernel Module GPG key) >>> io scheduler noop registered >>> io scheduler anticipatory registered >>> io scheduler deadline registered >>> io scheduler cfq registered (default) >>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >>> rtc: IRQ 8 is not free. >>> Non-volatile memory driver v1.2 >>> Linux agpgart interface v0.101 (c) Dave Jones >>> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize >>> Xen virtual console successfully installed as xvc0 >>> Event-channel device >>> installed. >>> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >>> ide: Assuming 50MHz system bus speed for PIO modes; override with >>> idebus=xx >>> Probing IDE interface ide0... >>> Probing IDE interface ide1... >>> Probing IDE interface ide2... >>> Probing IDE interface ide3... >>> Probing IDE interface ide4... >>> Probing IDE interface ide5... >>> ide-floppy driver 0.99.newide >>> usbcore: registered new driver hiddev >>> usbcore: registered new driver usbhid >>> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >>> PNP: No PS/2 controller found. Probing ports directly. >>> i8042.c: No controller found. >>> mice: PS/2 mouse device common for all mice >>> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >>> md: bitmap version 4.39 >>> TCP bic registered >>> Initializing IPsec netlink socket >>> NET: Registered protocol family 1 >>> NET: Registered protocol family 17 >>> XENBUS: Device with no driver: device/vbd/2050 >>> XENBUS: Device with no driver: >>> device/vbd/2049 >>> XENBUS: Device with no driver: device/vif/0 >>> XENBUS: Device with no driver: device/console/0 >>> Write protecting the kernel read-only data: 461k >>> Registering block device major 8 >>> ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver (PCI) >>> USB Universal Host Controller Interface driver v3.0 >>> SCSI subsystem initialized >>> register_blkdev: cannot get major 8 for sd >>> Fusion MPT base driver 3.04.05 >>> Copyright (c) 1999-2007 LSI Corporation >>> Fusion MPT SAS Host driver 3.04.05 >>> libata version 3.00 loaded. >>> netfront: Initialising virtual ethernet driver. >>> netfront: device eth0 has flipping receive path. >>> kjournald starting. Commit interval 5 seconds >>> EXT3-fs: mounted filesystem with ordered data mode. >>> input: PC Speaker as /class/input/input0 >>> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 >>> (usb?) >>> Failed to obtain physical IRQ 6 >>> floppy0: no floppy controllers >>> found >>> lp: driver loaded but no devices found >>> device-mapper: uevent: version 1.0.3 >>> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: >>> dm-devel@redhat.com >>> EXT3 FS on sda2, internal journal >>> Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064k >>> >> I can''t recognise any serious errors in there. Could someone please help me? >> >> Cheers, >> >> Andrew >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09 16:56:00 >> >> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09 16:56:00 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
List works pretty slow.
Actually , you try to install CentOS 5.2 PV DomU at CentOS 5.2 Dom0.
I would guess you upgraded Hypervisor via http://gitco.de prepared rpms.
It''s due to :-
# xm info
. . . . .
cc_compile_domain : labor.lan
. . . . .
Sasha''s Gunter domain for xen builds
Hence, you should have virt-install handy and missing virt-manger
without gitco''s support.
I suspect, that xen-tools & rinse install has not created proper image.
Following bellow is RH''s approved standard installation procedure :-
Insert your CentOS 5 DVD in the drive. Run "df -h" to find out what
mount point is. Suppose, it is /dev/hde
# dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso
# dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000
# mkdir -p /mnt/tmp
# mount -o loop,ro /etc/xen/disks/CentOS5.iso /mnt/tmp
Edit /etc/exports and add the line:-
/mnt/tmp
Restart Service "nfsd"
# virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img \
-l nfs:IP-Dom0:/mnt/tmp
or
1.To install your CentOS 5 DomU , at the command prompt type: virt-install.
2.When asked to install a fully virtualized guest, type: no.
3.Type CentOS5PV for your virtual machine name.
4.Type 1000 for your RAM allocation.
5.Type /etc/xen/images/CentOS5.img for your disk (guest image).
6.Type 12000 for the size of your disk (guest image).
7.Type yes to enable graphics support.
8.Type nfs:<IP address of Dom0>:/mnt/tmp for your install location.
The installation begins. Proceed as normal with the installation
Instead of image file , you can use " -f /dev/sda(X)" or
5.Type /dev/sda(X) for your disk (guest image).
When virt-install completed.
# xm list
Domain-0 8000 . . . . .
CentO5PV 1024 . . . . .
# xm start CentOS5PV
Check
# netstat -a | grep 590
In case of grapical install (by default)
# vncviewer localhost:0
will connect you to DomU, otherwise
# xm console CentOS5PV
will provide text console
Information above has been moderated at LXER about 1.5 years ago.
View:-
http://lxer.com/module/newswire/view/95262/index.html
Personally , i performed 20-25 such kind of virt-installs ( after
gitco''s
Hypervisor upgrade) with no problems.
Should you have any problems with virt-install, please , let me know.
Boris.
--- On Mon, 3/30/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: bderzhavets@yahoo.com
Cc: "Carsten Schiers" <carsten@schiers.de>,
xen-users@lists.xensource.com
Date: Monday, March 30, 2009, 7:46 PM
Hi,
Here is ''xm info'':
[root@localhost ~]# xm info
host : localhost.localdomain
release : 2.6.18-92.1.22.el5xen
version : #1 SMP Tue Dec 16 12:26:32 EST 2008
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2833
hw_caps :
bfebfbff:20100800:00000000:00000140:0408e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8190
free_memory : 128
node_to_cpu : node0:0-3
node_to_memory : node0:128
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
cc_compile_by : root
cc_compile_domain : labor.lan
cc_compile_date : Tue Sep 9 20:18:14 CEST 2008
xend_config_format : 4
And here is test4.cfg:
[root@localhost ~]# cat /etc/xen/test4.cfg
#
# Configuration file for the Xen instance test4, created
# by xen-tools 4.1 on Tue Mar 31 02:30:20 2009.
#
#
# Kernel + memory size
#
kernel = ''/boot/vmlinuz-2.6.18-92.1.22.el5xen''
#ramdisk = ''/boot/initrd.img-2.6.18-92.1.22.el5xen''
ramdisk = ''/boot/initrd-2.6.18-92.1.22.el5xen-xenblk.img''
memory = ''512''
#
# Disk device(s).
#
root = ''/dev/sda2 ro''
disk = [
''file:/vm/domains/test4/disk.img,sda2,w'',
''file:/vm/domains/test4/swap.img,sda1,w'',
]
extra = ''1''
#extra = ''xencons=tty''
#
# Physical volumes
#
#
# Hostname
#
name = ''test4''
#
# Networking
#
vif = [ ''ip=10.0.0.84,mac=00:16:3E:98:19:66'' ]
#
# Behaviour
#
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
Cheers,
Andrew
Boris Derzhavets wrote:
Could you post
1. test4.cfg
2. xm info (at Dom0)
--- On Mon, 3/30/09, Andrew Kilham <andrew@estyles.com.au>
wrote:
From:
Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Carsten Schiers" <carsten@schiers.de>
Cc: xen-users@lists.xensource.com
Date: Monday, March 30, 2009, 8:30 AM
Hi,
I have put that line in to the config file but now it freezes even
before it starts to boot the OS. Here is the complete output after
running xm create with "extra = ''xencons=tty''" in my
config file:
[root@localhost vm]# xm create -c
test4.cfg
Using config file "/etc/xen/test4.cfg".
Started domain test4
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
However, an update: I just tried booting it in to different run-levels
using the ''extra'' command in the config file, and it will boot
in to
run-level 1 but nothing higher. Still nothing in the log files or
anything though.
Cheers,
Andrew
Carsten Schiers wrote:
Hi,
Xen virtual console successfully installed as xvc0
Try to boot with extre=''xencons=tty'' in config
file or xencons=tty in
kernel line when using pygrub.
BR,
Carsten.
----- Originalnachricht -----
Von: Andrew Kilham <andrew@estyles.com.au>
Gesendet: Mon, 30.3.2009 14:03
An: xen-users@lists.xensource.com
Betreff: [Xen-users] DomU freezes during boot
Hi,
I am trying to boot a freshly installed DomU (using xen-tools and rinse)
of CentOS 5 64bit. It starts booting the operating system but it freezes
every time after starting SSH:
INIT: version 2.86 booting
Welcome to CentOS release 5.2 (Final)
Press ''I'' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Setting clock : Mon Mar 30 15:59:11 EDT 2009 [ OK ]
Starting udev: [ OK ]
Setting hostname test4: [ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2
/dev/sda2: clean, 17060/655360 files, 174903/1310720 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Mounting other filesystems: [ OK ]
Starting sshd: [ OK ]
Nothing comes up, it just stops there. I have tried mounting the HDD
image of the domU on my host to access the log files but there does not
appear to be anything of use. This is the dmesg log file on the domU:
Bootdata ok (command line is root=/dev/sda2 ro )
Linux version 2.6.18-92.1.22.el5xen (mockbuild@builder10.centos.org)
(gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16
12:26:32 EST 2008
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020800000 (usable)
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
No mptable found.
Built 1 zonelists. Total pages: 133120
Kernel command line: root=/dev/sda2 ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2833.530 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Software IO TLB disabled
Memory: 500992k/532480k available
(2418k kernel code, 22768k reserved,
1353k data, 176k init)
Calibrating delay using timer specific routine.. 7087.48 BogoMIPS
(lpj=14174967)
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: 256
, L1 D cache: 32K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
(SMP-)alternatives turned off
Brought up 1 CPUs
sizeof(vma)=168 bytes
sizeof(page)=56 bytes
sizeof(inode)=560 bytes
sizeof(dentry)=216 bytes
sizeof(ext3inode)=760 bytes
sizeof(buffer_head)=96 bytes
sizeof(skbuff)=240 bytes
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2]
[20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 127A0 could
not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: Fatal: No PCI 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 driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576
bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1238443140.218:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 6D65AF37871D9CBE
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device
installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver:
device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
Registering block device major 8
ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI)
Driver (PCI)
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.05
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.05
libata version 3.00 loaded.
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input0
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers
found
lp: driver loaded but no devices found
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
EXT3 FS on sda2, internal journal
Adding 131064k swap on /dev/sda1. Priority:-1 extents:1 across:131064k
I can''t recognise any serious errors in there. Could
someone please help me?
Cheers,
Andrew
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09
16:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.31/2029 - Release Date: 03/29/09
16:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham <andrew@estyles.com.au> wrote:> Here is my complete /etc/inittab file on domU:> # Run gettys in standard runlevels > 1:2345:respawn:/sbin/mingetty tty1> Nothing like the line you said. Should I add it in exactly as you typed it?Yup. Put it before the line "1:2345:respawn:" ... I think what happens is your domU boots succesfully, but it does not display any login prompt on console (which is xvc0). Oh and you should also add "xvc0" to /etc/securetty. Regards, Fajar. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sure, getting this rinse bug fixed you''ll get login to DomU. I just cannot understand why old fashioned style of PV DomUs setup ( with all kind of debootstrap''s fun) seems so attractive on the system having virt-install ready to go. Please, advise. Where i am wrong ? Boris. --- On Tue, 3/31/09, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: AW: [Xen-users] DomU freezes during boot To: "Andrew Kilham" <andrew@estyles.com.au> Cc: "Carsten Schiers" <carsten@schiers.de>, xen-users@lists.xensource.com Date: Tuesday, March 31, 2009, 3:00 AM On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham <andrew@estyles.com.au> wrote:> Here is my complete /etc/inittab file on domU:> # Run gettys in standard runlevels > 1:2345:respawn:/sbin/mingetty tty1> Nothing like the line you said. Should I add it in exactly as you typedit? Yup. Put it before the line "1:2345:respawn:" ... I think what happens is your domU boots succesfully, but it does not display any login prompt on console (which is xvc0). Oh and you should also add "xvc0" to /etc/securetty. Regards, Fajar. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Mar 31, 2009 at 2:15 PM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Sure, getting this rinse bug fixed you''ll get login to DomU. > I just cannot understand why old fashioned style of PV DomUs > setup ( with all kind of debootstrap''s fun) seems so attractive on the > system having virt-install ready to go. > Please, advise. Where i am wrong ?I don''t know about Andrew''s reasons for using rinse or xen-tools (which I never use), but personally I prefer manual-way instead of virt-install because I''m using a template (tar.gz) for domU deployment so I can create a new domU in 5 minutes or less. Plus text-based console (via "xm console") requires less bandwitdh compared to vnc console, which is important when you''re accessing domU via ssh from a slow network :) Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks , Fajar. --- On Tue, 3/31/09, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: AW: [Xen-users] DomU freezes during boot To: bderzhavets@yahoo.com Cc: xen-users@lists.xensource.com Date: Tuesday, March 31, 2009, 3:36 AM On Tue, Mar 31, 2009 at 2:15 PM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Sure, getting this rinse bug fixed you''ll get login to DomU. > I just cannot understand why old fashioned style of PV DomUs > setup ( with all kind of debootstrap''s fun) seems so attractive on the > system having virt-install ready to go. > Please, advise. Where i am wrong ?I don''t know about Andrew''s reasons for using rinse or xen-tools (which I never use), but personally I prefer manual-way instead of virt-install because I''m using a template (tar.gz) for domU deployment so I can create a new domU in 5 minutes or less. ******** Got it ! ******** Plus text-based console (via "xm console") requires less bandwitdh compared to vnc console, which is important when you''re accessing domU via ssh from a slow network :) Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi everybody, in Xen users manual they say that to perform a live migration the command is # xm migrate --live mydomain destination.ournetwork.com but it isn''t so clear to me what destination.ournetwork.com is supposed to be. I would like to do a live migration to a partition of another server in the same subnet, on which there''s already a dom0 and another domU. What am I supposed to do? Thanks in advance, paola _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Paola, This might make more sense to you: Xm migrate --live nameofvmtotransfer destinationdom0ip You might also need to specify the port to use with "--port=xx" Regards, Ro -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Paola Salviato Sent: 31 March 2009 10:18 To: xen-users@lists.xensource.com Cc: psalviato@gmail.com Subject: [Xen-users] Live migration Hi everybody, in Xen users manual they say that to perform a live migration the command is # xm migrate --live mydomain destination.ournetwork.com but it isn''t so clear to me what destination.ournetwork.com is supposed to be. I would like to do a live migration to a partition of another server in the same subnet, on which there''s already a dom0 and another domU. What am I supposed to do? Thanks in advance, paola _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users The SAQ Group Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ SAQ is the trading name of SEMTEC Limited. Registered in England & Wales Company Number: 06481952 http://www.saqnet.co.uk AS29219 SAQ Group Delivers high quality, honestly priced communication and I.T. services to UK Business. Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : Backups : Managed Networks : Remote Support. ISPA Member Find us in http://www.thebestof.co.uk/petersfield _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you very much, Robert. Cheers, paola Robert Dunkley wrote:> Hi Paola, > > This might make more sense to you: > Xm migrate --live nameofvmtotransfer destinationdom0ip > > You might also need to specify the port to use with "--port=xx" > > > Regards, > > Ro > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Paola > Salviato > Sent: 31 March 2009 10:18 > To: xen-users@lists.xensource.com > Cc: psalviato@gmail.com > Subject: [Xen-users] Live migration > > Hi everybody, > > in Xen users manual they say that to perform a live migration the > command is > > # xm migrate --live mydomain destination.ournetwork.com > > but it isn''t so clear to me what destination.ournetwork.com is supposed > to be. I would like to do a live migration to a partition of another > server in the same subnet, on which there''s already a dom0 and another > domU. What am I supposed to do? > > Thanks in advance, > paola > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > The SAQ Group > > Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ > SAQ is the trading name of SEMTEC Limited. Registered in England & Wales > Company Number: 06481952 > > http://www.saqnet.co.uk AS29219 > > SAQ Group Delivers high quality, honestly priced communication and I.T. services to UK Business. > > Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : Backups : Managed Networks : Remote Support. > > ISPA Member > > Find us in http://www.thebestof.co.uk/petersfield > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hmm, someone told me the other day that I should be using xen-tools and rinse, and NOT virt-install (see http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html). So which one should I use and why? And if I should be using virt-install, can someone please take a look at my initial problem that I still haven''t fixed in the above thread? :p Cheers, Andrew Boris Derzhavets wrote:> Sure, getting this rinse bug fixed you''ll get login to DomU. > I just cannot understand why old fashioned style of PV DomUs > setup ( with all kind of debootstrap''s fun) seems so attractive on the > system having virt-install ready to go. > Please, advise. Where i am wrong ? > > Boris. > > --- On *Tue, 3/31/09, Fajar A. Nugraha /<fajar@fajar.net>/* wrote: > > From: Fajar A. Nugraha <fajar@fajar.net> > Subject: Re: AW: [Xen-users] DomU freezes during boot > To: "Andrew Kilham" <andrew@estyles.com.au> > Cc: "Carsten Schiers" <carsten@schiers.de>, > xen-users@lists.xensource.com > Date: Tuesday, March 31, 2009, 3:00 AM > > On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham > <andrew@estyles.com.au> > wrote: > > Here is my complete /etc/inittab file on domU: > > > # Run gettys in standard runlevels > > 1:2345:respawn:/sbin/mingetty tty1 > > > Nothing like the line you said. Should I add it in exactly as you typed > it? > > Yup. Put it before the line "1:2345:respawn:" ... > I think what happens is your domU boots succesfully, but it does not > display any login prompt on console (which is xvc0). > > Oh and you should also add "xvc0" to /etc/securetty. > > Regards, > > Fajar. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: 03/30/09 17:56:00 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Mar 31, 2009 at 6:34 PM, Andrew Kilham <andrew@estyles.com.au> wrote:> Hmm, someone told me the other day that I should be using xen-tools and > rinse, and NOT virt-install (see > http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html). > > So which one should I use and why?It''s a matter of preference and support, really. Redhat support would probably tell you to use virt-install because they created and support it. I don''t use either.> And if I should be using virt-install, > can someone please take a look at my initial problem that I still haven''t > fixed in the above thread? :p >Did read my reply ? http://lists.xensource.com/archives/html/xen-users/2009-03/msg00746.html Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew,
As i have noticed two times your mistake when creating PV DomU via
virt-install is well known:-
************************************************************************************
--location <-l> should point to NFS shared directory with loop mounted
ISO image of
CentOS 5. 2 , NOT to path to ISO image itself.
************************************************************************************
That is what Red Hat Inc. and Sun Inc. taught customers to do for several years
already.
I''ve also twice wrote to you how to do that. You can also view it third
time:-
Insert your CentOS 5 DVD in the drive. Run "df -h" to find out what
mount point is. Suppose, it is /dev/hde
# dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso
# dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000
# mkdir -p /mnt/tmp
# mount -o loop,ro /etc/xen/disks/CentOS5.iso /mnt/tmp
Edit /etc/exports and add the line:-
/mnt/tmp
Restart Service "nfsd"
In other words make /mnt/tmp NFS shared directory at your local machine.
Run :-
# ifconfig
to find out your IP address (IP-Dom0) and run
# virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img \
-l nfs:IP-Dom0:/mnt/tmp
However with Xen Hypervisor 3.3 you might have reissue
# vncviewer localhost:0
several times during installation procedure, to get reconnected
Be sure it''s there on display 0 ( port 5900 ) .
Virt-install option <--nographics> will allow you to get text mode
install.
When graphical install gets done:-
# xm start CentOS5PV
# vncviewer localhost:0
When text mode install gets done :-
# xm start -c CentOS5PV
Personally, i have never suggested you to run rinse & xen-tools on system
with virt-install ready to go.
The other person did. Keep track of your threads
Regards.
B.
--- On Tue, 3/31/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: bderzhavets@yahoo.com
Cc: "Fajar A. Nugraha" <fajar@fajar.net>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 7:34 AM
Hmm, someone told me the other day that I should be using xen-tools and
rinse, and NOT virt-install (see
http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html).
So which one should I use and why? And if I should be using
virt-install, can someone please take a look at my initial problem that
I still haven''t fixed in the above thread? :p
Cheers,
Andrew
Boris Derzhavets wrote:
Sure, getting this rinse bug fixed you''ll get login to
DomU.
I just cannot understand why old fashioned style of PV DomUs
setup ( with all kind of debootstrap''s fun) seems so attractive on the
system having virt-install ready to go.
Please, advise. Where i am wrong ?
Boris.
--- On Tue, 3/31/09, Fajar A. Nugraha <fajar@fajar.net>
wrote:
From:
Fajar A. Nugraha <fajar@fajar.net>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Andrew Kilham" <andrew@estyles.com.au>
Cc: "Carsten Schiers" <carsten@schiers.de>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 3:00 AM
On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham
<andrew@estyles.com.au>
wrote:> Here is my complete /etc/inittab file on domU:
> # Run gettys in standard runlevels
> 1:2345:respawn:/sbin/mingetty tty1
> Nothing like the line you said. Should I add it in exactly as you typed
it?
Yup. Put it before the line "1:2345:respawn:" ...
I think what happens is your domU boots succesfully, but it does not
display any login prompt on console (which is xvc0).
Oh and you should also add "xvc0" to /etc/securetty.
Regards,
Fajar.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: 03/30/09
17:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boris Derzhavets
2009-Mar-31 15:40 UTC
[Xen-users] Virt-install and creating PV DomUs via local HTTP mirror at CentOS 5.2 Dom0
Different option of quick virt-install PV DomU (with xen-ified kernel on ISO
image) via local HTTP mirror :-
# dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso
# dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000
# chkconfig httpd on
# reboot
# mkdir -p /var/www/html/rhel
# mount -o loop /etc/xen/disks/CentOS5.iso /var/www/html/rhel
In other words , create local HTTP mirror via local Apache Server
Run :-
# ifconfig
to find out your IP address (IP-Dom0) and run
# virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img \
-l http://IP-Dom0/rhel
Virt-install provide you to options for location (on CentOS 5.X and Fedora 8)
1. NFS shared directory ( --location nfs:IP:/dir1)
2. Local or remote HTTP mirror ( --location http://IP/dir1)
B.
--- On Tue, 3/31/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: bderzhavets@yahoo.com
Cc: "Fajar A. Nugraha" <fajar@fajar.net>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 7:34 AM
Hmm, someone told me the other day that I should be using xen-tools and
rinse, and NOT virt-install (see
http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html).
So which one should I use and why? And if I should be using
virt-install, can someone please take a look at my initial problem that
I still haven''t fixed in the above thread? :p
Cheers,
Andrew
Boris Derzhavets wrote:
Sure, getting this rinse bug fixed you''ll get login to
DomU.
I just cannot understand why old fashioned style of PV DomUs
setup ( with all kind of debootstrap''s fun) seems so attractive on the
system having virt-install ready to go.
Please, advise. Where i am wrong ?
Boris.
--- On Tue, 3/31/09, Fajar A. Nugraha <fajar@fajar.net>
wrote:
From:
Fajar A. Nugraha <fajar@fajar.net>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Andrew Kilham" <andrew@estyles.com.au>
Cc: "Carsten Schiers" <carsten@schiers.de>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 3:00 AM
On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham
<andrew@estyles.com.au>
wrote:> Here is my complete /etc/inittab file on domU:
> # Run gettys in standard runlevels
> 1:2345:respawn:/sbin/mingetty tty1
> Nothing like the line you said. Should I add it in exactly as you typed
it?
Yup. Put it before the line "1:2345:respawn:" ...
I think what happens is your domU boots succesfully, but it does not
display any login prompt on console (which is xvc0).
Oh and you should also add "xvc0" to /etc/securetty.
Regards,
Fajar.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: 03/30/09
17:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha wrote:> On Tue, Mar 31, 2009 at 6:34 PM, Andrew Kilham <andrew@estyles.com.au> wrote: >> Hmm, someone told me the other day that I should be using xen-tools and >> rinse, and NOT virt-install (see >> http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html). >> >> So which one should I use and why? > > It''s a matter of preference and support, really. Redhat support would > probably tell you to use virt-install because they created and support > it. I don''t use either.Correct, it''s just a mater of preferences. I can tell you as well not to use the above 2 and use dtc-xen, because I wrote it! :) Thomas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Boris, I apologise for ignoring your previous comments! I attempted your instructions and ran virt-install like this:> virt-install -n test5 -r 1024 -p -f /vm/images/CentOS5-2.img -l > nfs:localhost:/test1 --nographicsI received no errors or anything until the CentOS installer was running (right after I configured my IP address etc), I got this error:> +-----------+ Error +------------+ > | | > | That directory could not be | > | mounted from the server. | > | | > | +----+ | > | | OK | | > | +----+ | > | | > | | > +--------------------------------+I hit OK and it just confirms my details (I tried /mnt/tmp, same problem, and I also tried localhost, same problem):> +----------------------+ NFS Setup +----------------------+ > | | > | Please enter the following information: | > | | > | o the name or IP number of your NFS server | > | o the directory on that server containing | > | CentOS for your architecture | > | | > | NFS server name: 10.0.0.81_______________ | > | CentOS directory: /test1__________________ | > | | > | +----+ +------+ | > | | OK | | Back | | > | +----+ +------+ | > | | > | | > +---------------------------------------------------------+Cheers, Andrew Boris Derzhavets wrote:> Andrew, > > As i have noticed two times your mistake when creating PV DomU via > virt-install is well known:- > > ************************************************************************************ > --location <-l> should point to NFS shared directory with loop > mounted ISO image of > CentOS 5. 2 , NOT to path to ISO image itself. > ************************************************************************************ > > That is what Red Hat Inc. and Sun Inc. taught customers to do for > several years already. > > I''ve also twice wrote to you how to do that. You can also view it > third time:- > > Insert your CentOS 5 DVD in the drive. Run "df -h" to find out what > mount point is. Suppose, it is /dev/hde > > # dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso > # dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000 > # mkdir -p /mnt/tmp > # mount -o loop,ro /etc/xen/disks/CentOS5.iso /mnt/tmp > > Edit /etc/exports and add the line:- > /mnt/tmp > Restart Service "nfsd" > > In other words make /mnt/tmp NFS shared directory at your local machine. > Run :- > # ifconfig > to find out your IP address (IP-Dom0) and run > > # virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img \ > -l nfs:IP-Dom0:/mnt/tmp > > However with Xen Hypervisor 3.3 you might have reissue > # vncviewer localhost:0 > several times during installation procedure, to get reconnected > Be sure it''s there on display 0 ( port 5900 ) . > > Virt-install option <--nographics> will allow you to get text mode > install. > > When graphical install gets done:- > # xm start CentOS5PV > # vncviewer localhost:0 > > When text mode install gets done :- > # xm start -c CentOS5PV > > Personally, i have never suggested you to run rinse & xen-tools on > system > with virt-install ready to go. > The other person did. Keep track of your threads > > Regards. > B. > > --- On *Tue, 3/31/09, Andrew Kilham /<andrew@estyles.com.au>/* wrote: > > From: Andrew Kilham <andrew@estyles.com.au> > Subject: Re: AW: [Xen-users] DomU freezes during boot > To: bderzhavets@yahoo.com > Cc: "Fajar A. Nugraha" <fajar@fajar.net>, > xen-users@lists.xensource.com > Date: Tuesday, March 31, 2009, 7:34 AM > > Hmm, someone told me the other day that I should be using > xen-tools and rinse, and NOT virt-install (see > http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html). > > So which one should I use and why? And if I should be using > virt-install, can someone please take a look at my initial problem > that I still haven''t fixed in the above thread? :p > > Cheers, > > Andrew > > > Boris Derzhavets wrote: >> Sure, getting this rinse bug fixed you''ll get login to DomU. >> I just cannot understand why old fashioned style of PV DomUs >> setup ( with all kind of debootstrap''s fun) seems so attractive >> on the system having virt-install ready to go. >> Please, advise. Where i am wrong ? >> >> Boris. >> >> --- On *Tue, 3/31/09, Fajar A. Nugraha /<fajar@fajar.net>/* wrote: >> >> From: Fajar A. Nugraha <fajar@fajar.net> >> Subject: Re: AW: [Xen-users] DomU freezes during boot >> To: "Andrew Kilham" <andrew@estyles.com.au> >> Cc: "Carsten Schiers" <carsten@schiers.de>, >> xen-users@lists.xensource.com >> Date: Tuesday, March 31, 2009, 3:00 AM >> >> On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham >> <andrew@estyles.com.au> >> wrote: >> > Here is my complete /etc/inittab file on domU: >> >> > # Run gettys in standard runlevels >> > 1:2345:respawn:/sbin/mingetty tty1 >> >> > Nothing like the line you said. Should I add it in exactly as you typed >> it? >> >> Yup. Put it before the line "1:2345:respawn:" ... >> I think what happens is your domU boots succesfully, but it does not >> display any login prompt on console (which is xvc0). >> >> Oh and you should also add "xvc0" to /etc/securetty. >> >> Regards, >> >> Fajar. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: 03/30/09 17:56:00 >> >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.35/2033 - Release Date: 03/31/09 13:05:00 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew ,
Please , configure IP of your Dom0 and post "ifconfig" report.
1. Goto Services start "nfsd" and make sure your "libvirtd"
daemon"
is up and runnning.
2. Add entry to /etc/exports:-
/mnt/tmp
Goto Services and restart "nfsd".
3. Try mount and umount IP:/mnt/tmp from remote host to
make sure you''ve done a remote share.
4. # mount -o loop,ro /etc/xen/isos/centos.iso /mnt/tmp
and run
# df -h
make sure it''s mounted
5. During virt-install run you must submit exactly IP address of your box
and "/mnt/tmp" ( i mean directory, which you did NFS share, and
nothing
else). At this time issue "ifconfig" in other terminal session to
doublecheck
your IP is in place). Please, post this snaphot as well.
You might experience network problem ussually connected with presence of WI-FI
adapter catching up IP on the fly and making up mess ( my experience)
*****************************
SECOND WAY TO INSTALL.
*****************************
If you see that your IP is good all the time and NFS fails to work.
1. Goto Services and start "httpd" daemon
2. mkdir -p /var/www/html/centos
3. mount -o loop centos.iso /var/www/html/centos
Launch browser to http://IP/centos and make sure you see a DVD ISO as web page
4. Then try :-
--location http://IP/centos
and select HTTP setup for virt-install
5. Submit your IP and URL - /centos
At the same time verify ifconfig in other terminal session , verify that browser
may launched to http://IP/centos.
You may take a look at :-
http://lxer.com/module/newswire/view/110642/index.html
Actually, there is no any difference between Xen 3.2 Ubuntu Dom0 and
Xen 3.3 CentOS 5.2 Dom0 in regards of procedure desribed above.
***********************
Worst case scenario:-
***********************
During Gitco''s upgrade something went wrong and "libvirt"
gets broken
I had some trouble doing Gitco''s Hypervisor Upgrades. It works , but
might require some background to complete things properly
You may try reinstall CentOS 5.2 with native Xen 3.1.X. Make sure
"libvirt ","dnsmask" services have been picked up during
install.
Then you can run in Xen environment :-
# yum update
# yum upgrade
to install the most recent RH patches (500 MB download).
Then try native virt-install or virt-manager. They should work both.
Boris.
-- On Tue, 3/31/09, Andrew Kilham <andrew@estyles.com.au> wrote:
From: Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: bderzhavets@yahoo.com
Cc: "Fajar A. Nugraha" <fajar@fajar.net>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 11:53 PM
Hi Boris,
I apologise for ignoring your previous comments!
I attempted your instructions and ran virt-install like this:
virt-install -n test5 -r 1024 -p -f
/vm/images/CentOS5-2.img -l nfs:localhost:/test1 --nographics
I received no errors or anything until the CentOS installer was running
(right after I configured my IP address etc), I got this error:
+-----------+ Error +------------+
| |
| That directory could not be |
| mounted from the server. |
| |
| +----+ |
| | OK | |
| +----+ |
| |
| |
+--------------------------------+
I hit OK and it just confirms my details (I tried /mnt/tmp, same
problem, and I also tried localhost, same problem):
+----------------------+ NFS Setup
+----------------------+
| |
| Please enter the following information: |
| |
| o the name or IP number of your NFS server |
| o the directory on that server containing |
| CentOS for your architecture |
| |
| NFS server name: 10.0.0.81_______________ |
| CentOS directory: /test1__________________ |
| |
| +----+ +------+ |
| | OK | | Back | |
| +----+ +------+ |
| |
| |
+---------------------------------------------------------+
Cheers,
Andrew
Boris Derzhavets wrote:
Andrew,
As i have noticed two times your mistake when creating PV DomU via
virt-install is well known:-
************************************************************************************
--location <-l> should point to NFS shared directory with loop
mounted ISO image of
CentOS 5. 2 , NOT to path to ISO image itself.
************************************************************************************
That is what Red Hat Inc. and Sun Inc. taught customers to do for
several years already.
I''ve also twice wrote to you how to do that. You can also view it third
time:-
Insert your CentOS 5 DVD in the drive. Run "df -h" to find out what
mount point is. Suppose, it is /dev/hde
# dd if=/dev/hde of=/etc/xen/disks/CentOS5.iso
# dd if=/dev/zero of=/etc/xen/images/CentOS5.img bs=1024k count=12000
# mkdir -p /mnt/tmp
# mount -o loop,ro /etc/xen/disks/CentOS5.iso /mnt/tmp
Edit /etc/exports and add the line:-
/mnt/tmp
Restart Service "nfsd"
In other words make /mnt/tmp NFS shared directory at your local machine.
Run :-
# ifconfig
to find out your IP address (IP-Dom0) and run
# virt-install -n CentOS5PV -r 1024 -p -f /etc/xen/images/CentOS5.img
\
-l nfs:IP-Dom0:/mnt/tmp
However with Xen Hypervisor 3.3 you might have reissue
# vncviewer localhost:0
several times during installation procedure, to get reconnected
Be sure it''s there on display 0 ( port 5900 ) .
Virt-install option <--nographics> will allow you to get text
mode install.
When graphical install gets done:-
# xm start CentOS5PV
# vncviewer localhost:0
When text mode install gets done :-
# xm start -c CentOS5PV
Personally, i have never suggested you to run rinse & xen-tools on
system
with virt-install ready to go.
The other person did. Keep track of your threads
Regards.
B.
--- On Tue, 3/31/09, Andrew Kilham <andrew@estyles.com.au>
wrote:
From:
Andrew Kilham <andrew@estyles.com.au>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: bderzhavets@yahoo.com
Cc: "Fajar A. Nugraha" <fajar@fajar.net>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 7:34 AM
Hmm, someone told me the other day
that I should be using xen-tools and
rinse, and NOT virt-install (see
http://lists.xensource.com/archives/html/xen-users/2009-03/msg00742.html).
So which one should I use and why? And if I should be using
virt-install, can someone please take a look at my initial problem that
I still haven''t fixed in the above thread? :p
Cheers,
Andrew
Boris Derzhavets wrote:
Sure, getting this rinse bug fixed you''ll get login
to
DomU.
I just cannot understand why old fashioned style of PV DomUs
setup ( with all kind of debootstrap''s fun) seems so attractive on the
system having virt-install ready to go.
Please, advise. Where i am wrong ?
Boris.
--- On Tue, 3/31/09, Fajar A. Nugraha <fajar@fajar.net>
wrote:
From:
Fajar A. Nugraha <fajar@fajar.net>
Subject: Re: AW: [Xen-users] DomU freezes during boot
To: "Andrew Kilham" <andrew@estyles.com.au>
Cc: "Carsten Schiers" <carsten@schiers.de>,
xen-users@lists.xensource.com
Date: Tuesday, March 31, 2009, 3:00 AM
On Mon, Mar 30, 2009 at 8:00 PM, Andrew Kilham
<andrew@estyles.com.au>
wrote:> Here is my complete /etc/inittab file on domU:
> # Run gettys in standard runlevels
> 1:2345:respawn:/sbin/mingetty tty1
> Nothing like the line you said. Should I add it in exactly as you typed
it?
Yup. Put it before the line "1:2345:respawn:" ...
I think what happens is your domU boots succesfully, but it does not
display any login prompt on console (which is xvc0).
Oh and you should also add "xvc0" to /etc/securetty.
Regards,
Fajar.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: 03/30/09
17:56:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.35/2033 - Release Date: 03/31/09
13:05:00
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2009/3/31 Fajar A. Nugraha <fajar@fajar.net>> On Tue, Mar 31, 2009 at 2:15 PM, Boris Derzhavets <bderzhavets@yahoo.com> > wrote: > > Sure, getting this rinse bug fixed you''ll get login to DomU. > > I just cannot understand why old fashioned style of PV DomUs > > setup ( with all kind of debootstrap''s fun) seems so attractive on the > > system having virt-install ready to go. > > Please, advise. Where i am wrong ? > > I don''t know about Andrew''s reasons for using rinse or xen-tools > (which I never use), but personally I prefer manual-way instead of > virt-install because I''m using a template (tar.gz) for domU deployment > so I can create a new domU in 5 minutes or less. >Sorry to resurrect this thread, I hope that''s not out of etiquette. But anyway, Fajar, I would appreciate it if you could elaborate on your template deployment method? I have recently been thinking about the best way to approach this. After creating some CentOS, Debian, and Ubuntu PV DomUs (each have their own kernel in the FS) which work; I''m now wondering the best way to capture them to use as a template in the future. I made all installations using LVM volumes, -disk, and -swap files. I was first planning on simply cloning the LVM volumes but it doesn''t seem efficient. I take it you simply have archived the entire disk filesystem and just extract into new disk images/LVM files when deploying? With scripts to modify config files? Is this the generally accepted ''best solution'' for DomU deployment? Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2009-Apr-03 10:05 UTC
[Xen-users] Virt-install at Xen 3.3.0 CentOS 5.2 Dom0 (port via http://gitco.de/repos/xen3.3.0)
That''s my old Howto. I just forgot about this post.
Not sure you are still interested, however i have decided
to provide a link :-
http://lxer.com/module/newswire/view/107922/index.html
Looks like 3.3.1 is also available in meantime at http://gitco.de/repos
Some new stuff seems to be there:-
pypxeboot-0.0.2-2.noarch.rpm 29-Dec-2008 00:14 14K
python-virtinst-0.400.0-5.noarch.rpm 07-Dec-2008 15:08 333K
qemu-0.9.1-10.x86_64.rpm 06-Dec-2008 02:23 11M
qemu-debuginfo-0.9.1-10.x86_64.rpm 06-Dec-2008 02:29 23M
qemu-img-0.9.1-10.x86_64.rpm 06-Dec-2008 02:29 76K
B.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boris Derzhavets
2009-Apr-03 16:08 UTC
Re: [Xen-users] Virt-install at Xen 3.3.0 CentOS 5.2 Dom0 (port via http://gitco.de/repos/xen3.3.0)
Install Xen Hypervisor 3.3.1 on CentOS 5.3 via
http://gitco.dehttp://bderzhavets.blogspot.com/2009/04/install-xen-hypervisor-3.html
Virt-install and virt-manager are both functional on the most recent
Gitco''s port Xen 3.3.1
to CentOS 5.3. I had to disable checksum offloading at CentOS 5.2 PV DomU.
That is only only issue i''ve got in meantime.
B.
--- On Fri, 4/3/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-users] Virt-install at Xen 3.3.0 CentOS 5.2 Dom0 (port via
http://gitco.de/repos/xen3.3.0)
To: "Andrew Kilham" <andrew@estyles.com.au>
Cc: xen-users@lists.xensource.com
Date: Friday, April 3, 2009, 6:05 AM
That''s my old Howto. I just forgot about this post.
Not sure you are still interested, however i have decided
to provide a link :-
http://lxer.com/module/newswire/view/107922/index.html
Looks like 3.3.1 is also available in meantime at http://gitco.de/repos
Some new stuff seems to be there:-
pypxeboot-0.0.2-2.noarch.rpm 29-Dec-2008 00:14 14K
python-virtinst-0.400.0-5.noarch.rpm 07-Dec-2008 15:08 333K
qemu-0.9.1-10.x86_64.rpm 06-Dec-2008 02:23 11M
qemu-debuginfo-0.9.1-10.x86_64.rpm 06-Dec-2008 02:29
23M
qemu-img-0.9.1-10.x86_64.rpm 06-Dec-2008 02:29 76K
B.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users