Robert Story wrote:
On Fri, 29 Jun 2007 19:17:54 -0700 FCXen wrote: F> > Are you sure you're not missing the domU's console? I noticed that with F> > at least the FC6 and F7 domUs, the boot output starts on the serial F> > console, then transfers to the graphical console. I'm not familiar with F> > the Centos domU's behavior, but it might be something to check. F> F> I think this is a big problem, it happened to me.* Unfortunately, I was trying F> on FC6 Test 2/3 so I was told to get the F7 release version and try that. F> F> There is no clear step by step how to on how to build GUI-less domUs for FC6
*
F> or F7
I simply edit the xen config file and comment out the virtual frame buffer line (vfb = [...]), and it works fine w/out a GUI...
How? For creating a domain, "we" (the headless/ssh/GUI-less/text-based people) can't get through the creation process. And I thought that the F7 Xen didn't have config files anymore, that it was all stored in an XML blob in a db somewhere. Is that not the case?
I am pretty sure that it is not possible to do an interactive text based creation of a F7 domU on an F7 dom0 via the virt-install command. And since I posted my previous msg there have been at least 2 more people posting (here and the Xen list) with the same problem AFAICT. I'll contact Thomas Chung http://fedoraproject.org/wiki/ThomasChung when I get a chance and ask him to create a Xen F7 QuickStart page so that it can get in the search engines and people can find out that they need to use some other method for doing Xen installs on F7. Unless there actually is a secret way to do it, if that is the case I'll try to send him the actual step for people to follow.
* Sorry, I should have said specifically F7... I was testing on F6 test 2/3 so those weren't really FC6.
----- "FCXen" fcxen@itsbeen.sent.com wrote:
Robert Story wrote:
I simply edit the xen config file and comment out the virtual frame
buffer
line (vfb = [...]), and it works fine w/out a GUI...
How? For creating a domain, "we" (the headless/ssh/GUI-less/text-based people) can't get through the creation process. And I thought that the F7 Xen didn't have config files anymore, that it was all stored in an XML blob in a db somewhere. Is that not the case?
Yes, virsh dumpxml NAME > NAME.xml; vi NAME.xml; virsh define NAME.xml but there is no vfb line.
I am pretty sure that it is not possible to do an interactive text based creation of a F7 domU on an F7 dom0 via the virt-install command.
= fc6 domU = On F7 dom0 if I do a fc6 domU install without a kickstart it begins in my terminal window, throws up a graphical console window if I've done xhost + dom0_server etc. This serial console window just has a dozen lines ending with a memory count. Then back in my terminal the typical anaconda installer shows up and all is fine.
== fc6 domU serial console == Bootdata ok (command line is dhcp method=http://ks/fedora/linux/core/6/x86_64) Linux version 2.6.18-1.2798.fc6xen (brewbuilder@hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000040800000 (usable) No mptable found. Built 1 zonelists. Total pages: 264192 Kernel command line: dhcp method=http://ks/fedora/linux/core/6/x86_64 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2588.848 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Software IO TLB disabled Memory: 1013760k/1056768k available (2323k kernel code, 34168k reserved, 1328k data, 172k init)
= f7 domU = If I do a f7 domU install without a kickstart it does something similar.
virt-install --name=f7-inter --ram=1024 \ --file=/var/lib/xen/images/f7-inter.xen \ --file-size=10 --nographics \ --location=http://ks/fedora/linux/releases/7/Fedora/x86_64/os \ --extra-args='dhcp nofb' \ --bridge=br101 --mac=AA:00:46:8D:7F:C8 --debug
It throws up the graphical serial console app but this window contains many more lines and the terminal never fires up anaconda. I tried adding nofb, selinux=0, and noacpi to the extra args. That didn't help.
Again, with kickstart it works eventually, but I don't see anything happening.
== f7 domU serial console == Linux version 2.6.20-2925.9.fc7xen (kojibuilder@xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007 Command line: dhcp nofb method=http://ks/fedora/linux/releases/7/Fedora/x86_64/os 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: dhcp nofb method=http://ks/fedora/linux/releases/7/Fedora/x86_64/os Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2589.272 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.. 6476.02 BogoMIPS (lpj=12952058) 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) (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
== f7 domU terminal window== That window ends with ... 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 XInputWireToEvent: UNKNOWN WIRE EVENT! type=110 XInputWireToEvent: UNKNOWN WIRE EVENT! type=110 <repeats>
-- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3