7:04 p.m.
I'm having trouble getting Xen up on Fedora 6. Following the
instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 ,
I've got xend running, but haven't gotten a viable image running.
I tried (per the above) virt-manager. I guessed that
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ was
a suitable install tree, but when the installer (Anaconda, I guess) gets
to some point (it varies with each attempt) it stalls, sometimes
complaining about not getting a file.
I also tried xm, but haven't figured out how to deal with the error:
Cannot open root device "sda1"
Virsh throws a different error:
Domain not found: xenUnifiedDomainLookupByName
I'm befuddled by having tried several different sources, each of which
said "it's soooo easy", but failing to provide sufficient information to
get me past these issues, so I'd be grateful if someone could point me
to instructions geared to the meanest understanding.
Walter
8:01 p.m.
Hi Walter, sorry to hear you're having trouble.
Walter Coole wrote:
I’m having trouble getting Xen up on Fedora 6. Following the
instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 ,
I’ve got xend running, but haven’t gotten a viable image running.
I tried (per the above) virt-manager. I guessed that
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
was a suitable install tree, but when the installer (Anaconda, I
guess) gets to some point (it varies with each attempt) it stalls,
sometimes complaining about not getting a file.
What type of system are you running this on? Is it 32 or 64 bit? What
kernel are you running? (uname -a)
I also tried xm, but haven’t figured out how to deal with the error:
Cannot open root device "sda1"
um... what disk are you presenting to your guest? Installing from the
http:// tree would indicate that you're installing a para-virt guest,
but it's looking for sda1. Typically the disk inside the guest is known
as xvda, which makes me wonder if you're presenting sda1 to the guest as
its root. Is that the same root disk that your host is using?
Virsh throws a different error:
Domain not found: xenUnifiedDomainLookupByName
yeah, hate to say this, but the xen logs can be very confusing and hard
to read until you get used to the various errors and what they *really*
mean sometimes.
I’m befuddled by having tried several different sources, each of which
said “it’s soooo easy”, but failing to provide sufficient information
to get me past these issues, so I’d be grateful if someone could point
me to instructions geared to the meanest understanding.
Yep, it actually is relatively easy, but that is assuming all the
requirements are met. Those are usually the hardest parts to figure out!
Mark
Walter
------------------------------------------------------------------------
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
8:24 p.m.
uname -a
Linux cloudy 2.6.20-1.3002.fc6xen #1 SMP Mon Aug 13 14:21:21 EDT 2007
x86_64 x86_64 x86_64 GNU/Linux
FWIW, the file that Anaconda is complaining about is
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima
ges/stage2.img , which seems to be sitting there as advertised, although
my link is pretty slow; could it be timing out over the transfer?
If understand the flags:
[wcoole@cloudy ~/Desktop]$ egrep "svm|vmx" /proc/cpuinfo
[wcoole@cloudy ~/Desktop]$
I cannot run Fully-virtualized guests, which seems to imply that I have
to run a para-virt guest.
I was imagining that it would be simplest to use a file (on the host
filesystem) as the filesystem for the guest, but I've probably mangled
the configuration. I'm using this command to start it:
sudo /usr/sbin/xm create -c football.cfg
It seems likely that I haven't got the config set right; here's
football.cfg:
cat football.cfg
kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen"
memory = 256
name = "football"
vif = [ '' ]
dhcp = "dhcp"
disk = ['file://xen/fedora/football.img,sda1,w',
'file://xen/fedora/football.swap,sda2,w']
root = "/dev/sda1 ro"
I got the img, swap, and cfg files from the tarball at
http://jailtime.org/download:fedora:fc6 , but copied and hacked them
without really knowing what I was doing. I'm not fixated on any
particular approach, just trying to do the easy thing to get started so
I can fool myself into thinking I know what I'm doing.
Thanks
Walter
-----Original Message-----
From: Mark Nielsen [mailto:mnielsen@redhat.com]
Sent: Tuesday, March 25, 2008 6:01 PM
To: Walter Coole
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
Hi Walter, sorry to hear you're having trouble.
Walter Coole wrote:
I'm having trouble getting Xen up on Fedora 6. Following the
instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 ,
I've got xend running, but haven't gotten a viable image
running.
I tried (per the above) virt-manager. I guessed that
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
was a suitable install tree, but when the installer (Anaconda, I
guess) gets to some point (it varies with each attempt) it stalls,
sometimes complaining about not getting a file.
What type of system are you running this on? Is it 32 or 64 bit? What
kernel are you running? (uname -a)
I also tried xm, but haven't figured out how to deal with the error:
Cannot open root device "sda1"
um... what disk are you presenting to your guest? Installing from the
http:// tree would indicate that you're installing a para-virt guest,
but it's looking for sda1. Typically the disk inside the guest is known
as xvda, which makes me wonder if you're presenting sda1 to the guest as
its root. Is that the same root disk that your host is using?
Virsh throws a different error:
Domain not found: xenUnifiedDomainLookupByName
yeah, hate to say this, but the xen logs can be very confusing and hard
to read until you get used to the various errors and what they *really*
mean sometimes.
I'm befuddled by having tried several different sources, each of which
said "it's soooo easy", but failing to provide
sufficient information
to get me past these issues, so I'd be grateful if someone could point
me to instructions geared to the meanest understanding.
Yep, it actually is relatively easy, but that is assuming all the
requirements are met. Those are usually the hardest parts to figure out!
Mark
Walter
------------------------------------------------------------------------
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
8:37 p.m.
Walter Coole wrote:
uname -a
Linux cloudy 2.6.20-1.3002.fc6xen #1 SMP Mon Aug 13 14:21:21 EDT 2007
x86_64 x86_64 x86_64 GNU/Linux
ok, so it's 64 on 64, just making sure. I've seen similar random crash
during install errors when people try to run 32 on 64 PV (not supported
and buggy)
FWIW, the file that Anaconda is complaining about is
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima
ges/stage2.img , which seems to be sitting there as advertised, although
my link is pretty slow; could it be timing out over the transfer?
hm, I've seen the same thing many times, failing to get stage2. The
typical problem is networking. dom0 gets the initial images to set the
install up, then somewhere around the time stage2 gets picked up,
networking is set up inside the guest to download the packages. I
strongly suspect some networking issue with the bridge not correctly
configured. Unfortunately that's going to be a little harder to
troubleshoot... maybe someone can chime in that's an expert on
troubleshooting bridges. One easy way to fix this might be to download
the FC6 ISOs and create your own install repo on the local network, or
even the same machine if possible.
If understand the flags:
[wcoole@cloudy ~/Desktop]$ egrep "svm|vmx" /proc/cpuinfo
[wcoole@cloudy ~/Desktop]$
I cannot run Fully-virtualized guests, which seems to imply that I have
to run a para-virt guest.
correct
I was imagining that it would be simplest to use a file (on the host
filesystem) as the filesystem for the guest, but I've probably mangled
the configuration. I'm using this command to start it:
sudo /usr/sbin/xm create -c football.cfg
It seems likely that I haven't got the config set right; here's
football.cfg:
cat football.cfg
kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen"
memory = 256
name = "football"
vif = [ '' ]
dhcp = "dhcp"
disk = ['file://xen/fedora/football.img,sda1,w',
'file://xen/fedora/football.swap,sda2,w']
root = "/dev/sda1 ro"
I use LVMs for my guest root and other disks.. again hopefully someone
else can chime in to verify if that's correct. One thing I do notice
here is that the vif is blank. That could be an issue related to the
problem above?
I got the img, swap, and cfg files from the tarball at
http://jailtime.org/download:fedora:fc6 , but copied and hacked them
without really knowing what I was doing. I'm not fixated on any
particular approach, just trying to do the easy thing to get started so
I can fool myself into thinking I know what I'm doing.
Mark
Thanks
Walter
-----Original Message-----
From: Mark Nielsen [mailto:mnielsen@redhat.com]
Sent: Tuesday, March 25, 2008 6:01 PM
To: Walter Coole
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
Hi Walter, sorry to hear you're having trouble.
Walter Coole wrote:
> I'm having trouble getting Xen up on Fedora 6. Following the
> instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 ,
>
> I've got xend running, but haven't gotten a viable image running.
>
> I tried (per the above) virt-manager. I guessed that
> http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
> was a suitable install tree, but when the installer (Anaconda, I
> guess) gets to some point (it varies with each attempt) it stalls,
> sometimes complaining about not getting a file.
>
>
What type of system are you running this on? Is it 32 or 64 bit? What
kernel are you running? (uname -a)
> I also tried xm, but haven't figured out how to deal with the error:
>
> Cannot open root device "sda1"
>
>
um... what disk are you presenting to your guest? Installing from the
http:// tree would indicate that you're installing a para-virt guest,
but it's looking for sda1. Typically the disk inside the guest is known
as xvda, which makes me wonder if you're presenting sda1 to the guest as
its root. Is that the same root disk that your host is using?
> Virsh throws a different error:
>
> Domain not found: xenUnifiedDomainLookupByName
>
>
yeah, hate to say this, but the xen logs can be very confusing and hard
to read until you get used to the various errors and what they *really*
mean sometimes.
> I'm befuddled by having tried several different sources, each of which
>
> said "it's soooo easy", but failing to provide sufficient information
> to get me past these issues, so I'd be grateful if someone could point
>
> me to instructions geared to the meanest understanding.
>
>
Yep, it actually is relatively easy, but that is assuming all the
requirements are met. Those are usually the hardest parts to figure out!
Mark
> Walter
>
>
>
------------------------------------------------------------------------
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
7:28 a.m.
Walter Coole wrote:
cat football.cfg
kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen"
memory = 256
name = "football"
vif = [ '' ]
dhcp = "dhcp"
disk = ['file://xen/fedora/football.img,sda1,w',
'file://xen/fedora/football.swap,sda2,w']
This is wrong. For paravirtualized guests, you want to use xvda1 and
xvda2. Also, you want to use tap:aio, otherwise you will corrupt your
guest disks if the dom0 crashes. So your disk line really wants to look
like:
disk =
['tap:aio:/xen/fedora/football.img,xvda1,w','tap:aio:/xen/fedora/football.swap,xvda2,w']
It might be easier, though, just to use virt-install and/or virt-manager
to install your guests; they take care of these details for you.
Chris Lalancette
3:13 p.m.
Agreed, it might be easier to use virt-manager, if Anaconda didn't
complain about not getting
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima
ges/stage2.img . Is
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ the
best URL for a Fedora install tree?
I tried your xvda suggestion, but got an error:
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
I changed the root clause to:
root = "/dev/xvda1 ro"
, which changed the error to:
VFS: Cannot open root device "xvda1" or unknown-block(0,0)
Please append a correct "root=" boot option
I'm unclear whether the problem is in creating the virtual disk or in
being able to mount it after it's been created.
On the virt-manager front I tried copying the install disks I have onto
a local directory, but got the error:
Unable to complete install: 'Invalid install location: Mounting location
/install/fc6/ failed'. Apparently, the local path for Create Wizard
needs to be a device that it can mount, because it gets farther if I use
/dev/cdrom.
Pulling directly from the CD fails with the error:
Unable to complete install: 'virDomainCreateLinux() failed POST
operation failed: (xend.err "Error creating domain: (22, 'Invalid
argument')")'
, but I'm unclear on which argument is invalid.
Thanks for your help so far!
Walter
-----Original Message-----
From: Chris Lalancette [mailto:clalance@redhat.com]
Sent: Wednesday, March 26, 2008 5:29 AM
To: Walter Coole
Cc: mnielsen(a)redhat.com; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
Walter Coole wrote:
cat football.cfg
kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen"
memory = 256
name = "football"
vif = [ '' ]
dhcp = "dhcp"
disk = ['file://xen/fedora/football.img,sda1,w',
'file://xen/fedora/football.swap,sda2,w']
This is wrong. For paravirtualized guests, you want to use xvda1 and
xvda2. Also, you want to use tap:aio, otherwise you will corrupt your
guest disks if the dom0 crashes. So your disk line really wants to look
like:
disk =
['tap:aio:/xen/fedora/football.img,xvda1,w','tap:aio:/xen/fedora/footbal
l.swap,xvda2,w']
It might be easier, though, just to use virt-install and/or virt-manager
to install your guests; they take care of these details for you.
Chris Lalancette
7:23 a.m.
Hello,
I can offer some input from my own experiences regarding mounting root.
On Wed, Mar 26, 2008 at 9:13 PM, Walter Coole <WCoole(a)aperiogroup.com>
wrote:
Please append a correct "root=" boot option
I changed the root clause to:
root = "/dev/xvda1 ro"
, which changed the error to:
VFS: Cannot open root device "xvda1" or unknown-block(0,0)
Please append a correct "root=" boot option
I'm unclear whether the problem is in creating the virtual disk or in
being able to mount it after it's been created.
I found that the default initrd did not contain the xenblk driver and so it
could not access the root filesystem. See here:
http://lists.xensource.com/archives/html/xen-users/2008-03/msg00000.html
You might even want to use the --preload option of mkinitrd. My exact
mkinitrd was:
# mkinitrd -v --preload=sd_mod --preload=xenblk --with=xennet
--with=xenblktap\
--with=xenbus_be /tmp/test `uname -r`
Then I copied /tmp/test to /boot/initrd-2.6.21.7-2.fc8xen.img. This worked
for me - YMMV.
Cheers,
Fred.
7:47 a.m.
You need to tell us *exactly* how you run virt-install, and what error
you get back.
1:04 p.m.
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.
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:
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:01
libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName
Creating storage file... 100% |=========================| 4.0 GB
00:00
Creating domain... 0 B
00:00
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
I got to virt-manager, where a new machine named "hockey" has just
showed up, which I open and view serial console. I see what looks like
an Anaconda session, asking "Choose a Language".
I pick English, US, deselect dynamic IP and IPv6, set
192.168.1.201/24,192.168.1.1,192.168.1.2 . It says "Retrieving
images/minstg2.img..." and stays there forever
192.168.1.117 is our internal Apache server, to which I've mirrored
download.fedora.redhat.com/pub/fedora. Just as a check, I downloaded
http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/images/sta
ge2.img with my browser and got a 78M file.
It seems as though the image is being built by virt-install, but that
the network settings aren't allowing the virtual machine to talk to the
install server properly. I don't know Anaconda well enough to change or
even examine the network settings it uses. Perhaps there is a problem
with not using DHCP?
It seems that several of other approaches I've tried are encountering
the same underlying issue, but with different symptoms.
Thanks!
Walter
-----Original Message-----
From: Markus Armbruster [mailto:armbru@redhat.com]
Sent: Thursday, March 27, 2008 5:47 AM
To: Walter Coole
Cc: Chris Lalancette; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
You need to tell us *exactly* how you run virt-install, and what error
you get back.
2:57 a.m.
"Walter Coole" <WCoole(a)aperiogroup.com> 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?
[...]
5:41 p.m.
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@redhat.com]
Sent: Friday, April 04, 2008 12:58 AM
To: Walter Coole
Cc: Chris Lalancette; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
"Walter Coole" <WCoole(a)aperiogroup.com> 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?
[...]
5:52 a.m.
Walter Coole wrote:
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/
Use a VNC console so that you can look at the extra screens of info from
anaconda.
In VNC use ALT-F[0-7] to switch console windows. Alt-F2 and Alt-F3 are
usually
interesting.
Barry
1:44 p.m.
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(a)veritas.com>
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(a)redhat.com
Subject: RE: [Fedora-xen] 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@redhat.com]
Sent: Friday, April 04, 2008 12:58 AM
To: Walter Coole
Cc: Chris Lalancette; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
"Walter Coole" <WCoole(a)aperiogroup.com> 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?
[...]
2:01 p.m.
(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(a)veritas.com>
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(a)redhat.com
Subject: RE: [Fedora-xen] 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@redhat.com]
Sent: Friday, April 04, 2008 12:58 AM
To: Walter Coole
Cc: Chris Lalancette; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
"Walter Coole" <WCoole(a)aperiogroup.com> 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(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
--
Mark Nielsen, RHCE
Red Hat, Inc.
mnielsen(a)redhat.com
2:32 p.m.
My version of virt-install doesn't understand --nogfx, but I tried:
sudo virt-install -n hockey -r 512 -f /var/lib/xen/images/hockey.img -s 4 --nographics -x
"linux text" -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os
, which led to a partial success. Anaconda got well beyond the minstg2.img step (although
I don't really know why this would work. It did give me this:
┌────────────────────────────┤ Error ├────────────────────────────┐
│ │
│ Unable to read package metadata. This may be due to a missing │
│ repodata directory. Please ensure that your install tree has │
│ been correctly generated. Cannot open/read repomd.xml file │
│ for repository: anaconda-base-200610172015.x86_64 │
│ │
│ ┌───────┐ │
│ │ Abort │ │
│ └───────┘ │
│ │
│ │
└─────────────────────────────────────────────────────────────────┘
I don't really understand what it's looking for, since
http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/repodata/re... is there
and looks like sensible XML to a casual glance. It doesn't refer to anything like
"anaconda-base-200610172015.x86_64".
192.168.1.117/mirror has a copy of download.fedora.redhat.com/pub/fedora, as I don't
know of a better place to get a tree from. I'm running out of space and bandwidth, so
it's not complete, but pub/fedora/linux/core/6/x86_64 looks complete.
Walter
-----Original Message-----
From: Mark Nielsen [mailto:mnielsen@redhat.com]
Sent: Tuesday, April 08, 2008 12:01 PM
To: Walter Coole
Cc: barry.scott(a)onelan.co.uk; Markus Armbruster; fedora-xen(a)redhat.com
Subject: RE: [Fedora-xen] Newby Help
(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(a)veritas.com>
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(a)redhat.com
Subject: RE: [Fedora-xen] 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@redhat.com]
Sent: Friday, April 04, 2008 12:58 AM
To: Walter Coole
Cc: Chris Lalancette; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newby Help
"Walter Coole" <WCoole(a)aperiogroup.com> 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(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
--
Mark Nielsen, RHCE
Red Hat, Inc.
mnielsen(a)redhat.com
2:41 p.m.
On Tue, Apr 08, 2008 at 12:32:40PM -0700, Walter Coole wrote:
My version of virt-install doesn't understand --nogfx, but I
tried:
It is --nographics actually
Check 'man virt-install' or 'virt-install --help' for more details
Dan.
--
|: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
5872
days inactive
5885
days old
15 comments
7 participants
participants (7)
-
Barry Scott -
Chris Lalancette -
Daniel P. Berrange -
Friedrich Clausen -
Mark Nielsen -
Markus Armbruster -
Walter Coole