[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: [Fedora-xen] Fw: XEN Guest Install problem



mmacdonald@xxxxxxxxxx a écrit :
>
> Hey I am trying to install a new XEN guest up and running on Fedora 7
> x86_64 and it hangs everytime:
>
> I am using the following command:
>
> virt-install --paravirt -b virbr0 --nographics --debug -n foafdz01 -r
> 1024
> -lnfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7
> -f /dev/vg01/dblv01 -x ks=http://10.229.70.234/ks/foafdz01.cfg
>
> and I get the following:
>
> Thu, 09 Aug 2007 11:55:02 DEBUG    Path is block file: Assuming Block
> disk type.
>  
>  
> Starting install...
> libvir: Xen Daemon error : GET operation failed:
> Thu, 09 Aug 2007 11:55:02 DEBUG    Preparing mount at
> /var/lib/xen/virtinstmnt.S6wuva
> Thu, 09 Aug 2007 11:55:02 DEBUG    Acquiring file from
> /var/lib/xen/virtinstmnt.S6wuva/Fedora
> Thu, 09 Aug 2007 11:55:02 DEBUG    Found a directory
> Thu, 09 Aug 2007 11:55:02 DEBUG    Detected a Fedora distro
> Thu, 09 Aug 2007 11:55:02 DEBUG    Acquiring file from
> /var/lib/xen/virtinstmnt.S6wuva/images/xen/vmlinuz
> Thu, 09 Aug 2007 11:55:02 DEBUG    Saved file to
> /var/lib/xen/virtinst-vmlinuz.kVhm-B
> Thu, 09 Aug 2007 11:55:02 DEBUG    Acquiring file from
> /var/lib/xen/virtinstmnt.S6wuva/images/xen/initrd.img
> Thu, 09 Aug 2007 11:55:03 DEBUG    Saved file to
> /var/lib/xen/virtinst-initrd.img.GVqMWE
> Thu, 09 Aug 2007 11:55:03 DEBUG    Cleaning up mount at
> /var/lib/xen/virtinstmnt.S6wuva
> libvir: Xen Daemon error : GET operation failed:
> Thu, 09 Aug 2007 11:55:03 DEBUG    Creating guest from '<domain
> type='xen'>
>   <name>foafdz01</name>
>   <currentMemory>1048576</currentMemory>
>   <memory>1048576</memory>
>   <uuid>80291afd-cbef-a8b1-d868-730c0d316efc</uuid>
>   <os>
>     <type>linux</type>
>     <kernel>/var/lib/xen/virtinst-vmlinuz.kVhm-B</kernel>
>     <initrd>/var/lib/xen/virtinst-initrd.img.GVqMWE</initrd>
>     <cmdline>ks=http://10.229.70.234/ks/foafdz01.cfg
> method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7</cmdline>
>
>   </os>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>destroy</on_reboot>
>   <on_crash>destroy</on_crash>
>   <vcpu>1</vcpu>
>   <devices>
>     <disk type='block' device='disk'>
>       <source dev='/dev/vg01/dblv01'/>
>       <target dev='xvda'/>
>     </disk>
>  
>     <interface type='bridge'>
>       <source bridge='virbr0'/>
>       <mac address='00:16:3e:1b:e5:9e'/>
>     </interface>
>  
>  
>   </devices>
> </domain>
> '
> Creating domain...                                                 0 B
> 00:00
> Thu, 09 Aug 2007 11:55:04 DEBUG    Created guest, looking to see if it
> is running
> Thu, 09 Aug 2007 11:55:04 DEBUG    Launching console callback
> Thu, 09 Aug 2007 11:55:04 DEBUG    Saving XML boot config '<domain
> type='xen'>
>   <name>foafdz01</name>
>   <currentMemory>1048576</currentMemory>
>   <memory>1048576</memory>
>   <uuid>80291afd-cbef-a8b1-d868-730c0d316efc</uuid>
>   <bootloader>/usr/bin/pygrub</bootloader>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <vcpu>1</vcpu>
>   <devices>
>     <disk type='block' device='disk'>
>       <source dev='/dev/vg01/dblv01'/>
>       <target dev='xvda'/>
>     </disk>
>  
>     <interface type='bridge'>
>       <source bridge='virbr0'/>
>       <mac address='00:16:3e:1b:e5:9e'/>
>     </interface>
>  
>  
>   </devices>
> </domain>
> '
> Linux version 2.6.20-2925.9.fc7xen
> (kojibuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2
> 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007
> Command line: ks=http://10.229.70.234/ks/foafdz01.cfg
> method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7
>
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000040800000 (usable)
> end_pfn_map = 264192
> Zone PFN ranges:
>   DMA             0 ->   264192
>   DMA32      264192 ->   264192
>   Normal     264192 ->   264192
> early_node_map[1] active PFN ranges
>     0:        0 ->   264192
> No mptable found.
> PERCPU: Allocating 26368 bytes of per cpu data
> Built 1 zonelists.  Total pages: 259481
> Kernel command line: ks=http://10.229.70.234/ks/foafdz01.cfg
> method=nfs:10.229.70.234:/data/mirror/redhat/pub/redhat/linux/fedora/x86_64/7
>
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> Xen reported: 2194.496 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: 1015932k/1056768k available (2207k kernel code, 32024k
> reserved, 1347k data, 192k init)
> Calibrating delay using timer specific routine.. 5488.99 BogoMIPS
> (lpj=10977983)
> 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
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 1024K (64 bytes/line)
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> (SMP-)alternatives turned off
> Brought up 1 CPUs
> Grant table initialized
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: Fatal: No config space access function found
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> xen_mem: Initialising balloon driver.
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> PCI: System does not support PCI
> PCI: System does not support PCI
> NetLabel: Initializing
> NetLabel:  domain hash size = 128
> NetLabel:  protocols = UNLABELED CIPSOv4
> NetLabel:  unlabeled traffic allowed by default
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
> TCP established hash table entries: 131072 (order: 10, 4194304 bytes)
> TCP bind hash table entries: 65536 (order: 9, 2097152 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> checking if image is initramfs... it is
> Freeing initrd memory: 7236k freed
> IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
> audit: initializing netlink socket (disabled)
> audit(1186674904.434:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> SELinux:  Registering netfilter hooks
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> Linux agpgart interface v0.101 (c) Dave Jones
> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
> input: Macintosh mouse button emulation as /class/input/input0
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> usbcore: registered new interface driver libusual
> usbcore: registered new interface driver hiddev
> usbcore: registered new interface driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> TCP bic registered
> Initializing XFRM netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> XENBUS: Device with no driver: device/vbd/51712
> XENBUS: Device with no driver: device/vif/0
> Write protecting the kernel read-only data: 938k
>
> ------------------------
>
> I have tried some other options and I just can't seem to get past this
> stage.  Any thoughts would be great 
I do experience the same issue.

Because there is no graphics (option "--nographics"), it is not possible
to see the display inside virt-manager for example. I say this because
it's the setup that I am using :
when I encountered the problem, my workaround was to launch the
installation with --vnc instead of --nographics and to use virt-manager
to open the VM's display and continue the installation in graphic mode.
If you have installed dom0 without the X server, you will maybe have to
install fonts for virt-manager (I experienced this and had to install
the fonts with : "yum install fonts-truetype-apl fonts-x11-apl")

Note that the same virt-install command line options launched for an
installation of Fedora Core 6 ("-l
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/"; as
of "man virt-install" examples) will work nicely with "--nographics"!

Now, I suspect the kernel used for booting the installation (the one
located in "redhat/linux/fedora/x86_64/7/os/images/xen/", which is in
fact dowloaded by virt-install to launch the installation), to use a tty
different from the standard one.

Maybe you can change this behaviour by changing the parameters passed to
the kernel with the "-x" option.
In your example, "-x" is used to give the kickstart location. Maybe you
can try to append something like "-x tty=xvc0" (xvc0 seems to be the tty
used when doing "virsh/xm console domU")

If anyone have a more precise solution.. Don't hesitate !

-- 
Maxim Doucet - www.alamaison.fr
sys admin @ la maison


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.