RE: Newby Help

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

 



(resend to all + additional comment)

try the --nogfx option with virt-install, and/or use -x "linux text"
which should cause the install to proceed in a text mode. From the looks
of that message things are actually installing but showing in a
graphical console which you can't see (for whatever reason..)

Mark

On Tue, 2008-04-08 at 11:44 -0700, Walter Coole wrote:
> Thanks for the suggestion.  I tried it and Alt-F3 showed a message about
> dropping to a serial console due to lack of memory, so I tried it again
> with this command line:
> 
> sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s
> 4 --vnc -l
> http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/
> Password:
> 
> 
> Starting install...
> libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID
> Retrieving file fedora.cs 100% |=========================| 2.3 kB
> 00:00
> Retrieving file vmlinuz.. 100% |=========================| 1.8 MB
> 00:00
> Retrieving file initrd.im 100% |=========================| 5.6 MB
> 00:00
> libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName
> Creating storage file...  100% |=========================| 4.0 GB
> 00:00
> Creating domain...                                                 0 B
> 00:00
> 
> VNC Viewer Free Edition 4.1.2 for X - built Jul 18 2006 06:59:52
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> 
> Tue Apr  8 11:14:19 2008
>  main:        unable to resolve host by name: Success (0)
> Domain installation still in progress.  You can reconnect to
> the console to complete the installation process.
> 
> and a dialog box with the same message:
> 
> unable to resolve host by name: Success (0)
> 
> popped up on my workstation.  Despite that, Virtual Machine Manager was
> able to open it, so I see the Anaconda window.  Most of the console
> windows are blank, but a screenshot of Alt-F3 is attached, in hopes
> someone can interpret it with more success than I've had.  The serial
> console shows:
> 
> 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
> IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
> audit: initializing netlink socket (disabled)
> audit(1207679422.076: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 4D36EEF71C3A3150
> - User ID: Red Hat, Inc. (Kernel Module GPG key)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> Linux agpgart interface v0.101 (c) Dave Jones
> RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> Console: switching to colour frame buffer device 100x37
> input: Xen Virtual Keyboard/Mouse as /class/input/input0
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with
> idebus=xx
> ide-floppy driver 0.99.newide
> usbcore: registered new driver libusual
> usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> 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/51712
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/vkbd/0
> XENBUS: Device with no driver: device/vfb/0
> Write protecting the kernel read-only data: 440k
> 
> Looking at the screen shot, it appears that several transfers from the
> tree were successful, which makes it seem as though basic networking is
> working.  Since the messaging for stage2.img is the same, it looks as
> though that was also successful and the hang up is in the next item.
> Not having seen it, I'm pretty vague on what it is or why it might fail.
> I didn't check Alt-F4, as that causes the window to go away (on Windows
> XP), is it likely to be interesting?  If so, is there an alternate way
> to get at it?
> 
> Continued thanks!
> Walter
> 
> 
> -----Original Message-----
> From: Walter Coole 
> Sent: Monday, April 07, 2008 3:41 PM
> To: 'Markus Armbruster'
> Cc: Chris Lalancette; fedora-xen@xxxxxxxxxx
> Subject: RE:  Newby Help
> 
> The originating host (where I'm running virt-install) has SELinux in
> "Permissive" mode.  The web server (192.168.1.117) had SELinux in
> "Secure" mode, so I changed it to "Permissive" mode.  I don't think
> SELinux is started on the system being installed, but if someone knows
> how to set or confirm that, I'd be happy to be corrected.  I'm not
> finicky about the path where the file lives, so I tried it with
> /var/lib/xen/images/hockey.img.  The symptom is unchanged: stuck at
> minstg2.img.
> 
> The revised command line is:
> 
> sudo virt-install -n hockey -r 256 -f /var/lib/xen/images/hockey.img -s
> 4 --nographics --noautoconsole -l
> http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/
> 
> Thanks!
> Walter
> 
> 
> -----Original Message-----
> From: Markus Armbruster [mailto:armbru@xxxxxxxxxx] 
> Sent: Friday, April 04, 2008 12:58 AM
> To: Walter Coole
> Cc: Chris Lalancette; fedora-xen@xxxxxxxxxx
> Subject: Re:  Newby Help
> 
> "Walter Coole" <WCoole@xxxxxxxxxxxxxxx> writes:
> 
> > Thanks for the hint; sorry it took so long for me to try several
> > different approaches.
> >
> > I hadn't tried virt-install; I had assumed that virt-manager's Create
> > Wizard did the equivalent job.
> 
> Uh, I must have somehow missed that you used virt-manager, not
> virt-install.  Telling us exactly how you interact with either is
> fine.  Telling us how you run virt-install is easier, though.
> 
> > Trying virt-install, this is what my session looked like:
> >
> > sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4
> > --nographics --noautoconsole -l
> > http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/
> > Password:
> 
> This is an unusual image location.  Is SELinux enabled?  Does
> /var/lib/xen/images/hockey.img work?
> 
> [...]
> --
> Fedora-xen mailing list
> Fedora-xen@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-xen
-- 
Mark Nielsen, RHCE
Red Hat, Inc.
mnielsen@xxxxxxxxxx

Attachment: smime.p7s
Description: S/MIME cryptographic signature

--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen

[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux