I am having problems getting a fedora7 domu running under my Centos5 Dom0 (this is a centos5 server no graphical interface) I followed the same steps to created the fedora 7 domu as I have for creating the cenots5 domu that I have on the same box. I downloaded the vmlinux and initrd from here ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ images/xen/ Xm config: kernel = "/boot/vmlinuz-f7xeninstall" ramdisk = "/boot/initrd-f7xeninstall" extra = "text ks=http://www.mcdees-specialties.com/fed7/minimal-ks.cf" name = "fed7" memory = "230" disk = [ ''tap:aio:/var/lib/xen/images/fed7.img,xvda,w'', ] #vif = [ '''', ] vif = [ ''bridge=xenbr0'', ] ip = "192.168.1.202" netmask = "255.255.255.0" gateway = "192.168.1.1" vcpus=1 on_reboot = ''destroy'' on_crash = ''destroy'' When I run xm create -c fed7inst it gets to here and stops ..................................... Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Any and all ideas are welcome
"Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes:> I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/ > > Xm config: > > kernel = "/boot/vmlinuz-f7xeninstall" > ramdisk = "/boot/initrd-f7xeninstall" > extra = "text ks=http://www.mcdees-specialties.com/fed7/minimal-ks.cf" > name = "fed7" > memory = "230" > disk = [ ''tap:aio:/var/lib/xen/images/fed7.img,xvda,w'', ] > #vif = [ '''', ] > vif = [ ''bridge=xenbr0'', ] > ip = "192.168.1.202" > netmask = "255.255.255.0" > gateway = "192.168.1.1" > vcpus=1 > on_reboot = ''destroy'' > on_crash = ''destroy'' > > When I run > xm create -c fed7inst > > it gets to here and stops > > ..................................... > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762k > > Any and all ideas are welcomeHow exactly do you start your guest? What does starting your guest write to /var/log/xen/ and xm dmesg ?
On Wed, 6 Jun 2007, Brian McDonald wrote:> I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/> When I run > xm create -c fed7inst > > it gets to here and stops > > ..................................... > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762khttp://www.mail-archive.com/fedora-xen@redhat.com/msg00676.html Paul
How exactly do you start your guest?
What does starting your guest write to /var/log/xen/ and xm dmesg ?
I start using the xm command
xm create -c fed7inst
Where fed7inst is the name of the config file
Xend.log
[2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:190)
XendDomainInfo.create([''vm'', [''name'',
''fed7''], [''memory'',
''230''], [''
on_reboot'', ''destroy''],
[''on_crash'', ''destroy''],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-f7xeninstall''], [''ramdisk'',
''/boo
t/initrd-f7xeninstall''], [''ip'',
''192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off''],
[''args'', ''text
ks=http://www.mcdees-specialties.
com/fed7/minimal-ks.cf'']]], [''device'',
[''tap'', [''uname'',
''tap:aio:/var/lib/xen/images/fed7.img''],
[''dev'', ''xvda''], [''mode'',
''w'']]],
[''device'',
[''vif'', [''bridge'',
''xenbr0'']]]])
[2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:296)
parseConfig: config is [''vm'', [''name'',
''fed7''], [''memory'',
''230''], [
''on_reboot'', ''destroy''],
[''on_crash'', ''destroy''],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-f7xeninstall''], [''ramdisk'',
''/bo
ot/initrd-f7xeninstall''], [''ip'',
''192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off''],
[''args'', ''text
ks=http://www.mcdees-specialties
.com/fed7/minimal-ks.cf'']]], [''device'',
[''tap'', [''uname'',
''tap:aio:/var/lib/xen/images/fed7.img''],
[''dev'', ''xvda''], [''mode'',
''w'']]],
[''device''
, [''vif'', [''bridge'',
''xenbr0'']]]]
[2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:397)
parseConfig: result is {''shadow_memory'': None,
''start_time'': None, ''
uuid'': None, ''on_crash'': ''destroy'',
''on_reboot'': ''destroy'',
''localtime'':
None, ''image'': [''linux'',
[''kernel'', ''/boot/vmlinuz-f7xeninstall''],
[''
ramdisk'', ''/boot/initrd-f7xeninstall''],
[''ip'',
''192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off''],
[''args'', ''text
ks=http://www.mcde
es-specialties.com/fed7/minimal-ks.cf'']],
''on_poweroff'': None,
''bootloader_args'': None, ''cpus'': None,
''name'': ''fed7'', ''backend'':
[],
''vcpus'':
1, ''cpu_weight'': None, ''features'': None,
''vcpu_avail'': None, ''memory'': 230,
''device'': [(''tap'', [''tap'',
[''uname'', ''tap:aio:/var/lib/xen/images/
fed7.img''], [''dev'', ''xvda''],
[''mode'', ''w'']]), (''vif'',
[''vif'', [''bridge'',
''xenbr0'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:1264)
XendDomainInfo.construct: None
[2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:1296)
XendDomainInfo.initDomain: 28 1.0
[2007-06-06 13:18:41 xend 2642] DEBUG (balloon:127) Balloon: 236344 KiB
free; need 235520; done.
[2007-06-06 13:18:41 xend 2642] INFO (image:136) buildDomain os=linux dom=28
vcpus=1
[2007-06-06 13:18:41 xend 2642] DEBUG (image:199) dom = 28
[2007-06-06 13:18:41 xend 2642] DEBUG (image:200) image
/boot/vmlinuz-f7xeninstall
[2007-06-06 13:18:41 xend 2642] DEBUG (image:201) store_evtchn = 1
[2007-06-06 13:18:41 xend 2642] DEBUG (image:202) console_evtchn = 2
[2007-06-06 13:18:41 xend 2642] DEBUG (image:203) cmdline
ip=192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off text ks=http:
//www.mcdees-specialties.com/fed7/minimal-ks.cf
[2007-06-06 13:18:41 xend 2642] DEBUG (image:204) ramdisk
/boot/initrd-f7xeninstall
[2007-06-06 13:18:41 xend 2642] DEBUG (image:205) vcpus = 1
[2007-06-06 13:18:41 xend 2642] DEBUG (image:206) features [2007-06-06
13:18:41 xend 2642] DEBUG (blkif:24) exception looking up device
number for xvda: [Errno 2] No such file or directory:
''/dev/xvda''
[2007-06-06 13:18:41 xend 2642] DEBUG (DevController:110) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''51712'',
''device-type'':
''disk'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/tap/28/51712''} to
/local/domain/28/device/vbd/51712.
[2007-06-06 13:18:41 xend 2642] DEBUG (DevController:112) DevController:
writing {''domain'': ''fed7'',
''frontend'': ''/local/domain/28/device/vbd/5
1712'', ''dev'': ''xvda'',
''state'': ''1'', ''params'':
''aio:/var/lib/xen/images/fed7.img'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''28'',
''type'': ''ta
p''} to /local/domain/0/backend/tap/28/51712.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:110) DevController:
writing {''backend-id'': ''0'',
''mac'': ''00:16:3e:4f:c2:71'',
''handle'': ''0''
, ''state'': ''1'', ''backend'':
''/local/domain/0/backend/vif/28/0''} to
/local/domain/28/device/vif/0.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:112) DevController:
writing {''bridge'': ''xenbr0'',
''domain'': ''fed7'',
''handle'': ''0'', ''script
'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''frontend'':
''/local/domain/28/device/vif/0'', ''mac'':
''00:16:3e:4f:c2:71'', ''online'':
''1'',
''front
end-id'': ''28''} to /local/domain/0/backend/vif/28/0.
[2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:715)
Storing VM details: {''shadow_memory'': ''0'',
''uuid'': ''4a437037-a07f-7c
e9-4128-086fb2a1ae92'', ''on_reboot'':
''destroy'', ''start_time'':
''1181150322.24'', ''on_poweroff'':
''destroy'', ''name'': ''fed7'',
''xend/restart_count'':
''0'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''230'',
''on_crash'':
''destroy'', ''image'': "(linux (kernel
/boot/vmlinuz-f7xeninstall) (ramdisk /b
oot/initrd-f7xeninstall) (ip
192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off) (args ''text
ks=http://www.mcdees-specialties.com/fed7/
minimal-ks.cf''))", ''maxmem'':
''230''}
[2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:750)
Storing domain details: {''console/ring-ref'':
''103594'', ''console/port
'': ''2'', ''name'':
''fed7'', ''console/limit'':
''1048576'', ''vm'':
''/vm/4a437037-a07f-7ce9-4128-086fb2a1ae92'',
''domid'': ''28'',
''cpu/0/availability'': ''on
line'', ''memory/target'': ''235520'',
''store/ring-ref'': ''103595'',
''store/port'':
''1''}
[2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:940)
XendDomainInfo.handleShutdownWatch
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices vif.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:149) Waiting for 0.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vif/28/0/hotplug-status.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices usb.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices vbd.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices irq.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices vkbd.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices vfb.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices pci.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices ioports.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices tap.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:149) Waiting for 51712.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/tap/28/51712/hotplug-status.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for
devices vtpm.
[2007-06-06 13:18:42 xend 2642] INFO (XendDomain:370) Domain fed7 (28)
unpaused.
"Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes:> I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/Wait a sec! You simply plunked kernel & initrd into your /boot? That bypasses the scripts in the rpms, and you know, those are there for a reason. Can you try installing kernel-xen with yum? [...]
-----Original Message----- From: Markus Armbruster [mailto:armbru@redhat.com] Sent: Wednesday, June 06, 2007 1:51 PM To: Brian McDonald Cc: fedora-xen@redhat.com Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU "Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes:> I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here >ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/> images/xen/>>Wait a sec! You simply plunked kernel & initrd into your /boot? That >>bypasses the scripts in the rpms, and you know, those are there for a >>reason. Can you try installing kernel-xen with yum?You can not use yum if the operating system is not installed in the domU This is a centos5 server that I am trying to load a fedora7 domU
"Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes:> -----Original Message----- > From: Markus Armbruster [mailto:armbru@redhat.com] > Sent: Wednesday, June 06, 2007 1:51 PM > To: Brian McDonald > Cc: fedora-xen@redhat.com > Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU > > "Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes: > >> I am having problems getting a fedora7 domu running under my Centos5 Dom0 >> (this is a centos5 server no graphical interface) >> >> I followed the same steps to created the fedora 7 domu as I have for >> creating the cenots5 domu that I have on the same box. >> >> I downloaded the vmlinux and initrd from here >> > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ >> images/xen/ > >>>Wait a sec! You simply plunked kernel & initrd into your /boot? That >>>bypasses the scripts in the rpms, and you know, those are there for a >>>reason. Can you try installing kernel-xen with yum? > > You can not use yum if the operating system is not installed in the domU > This is a centos5 server that I am trying to load a fedora7 domUWhy can''t you simply create the guest with virt-install?
On Wed, 6 Jun 2007, Brian McDonald wrote:> I am using the new fedora 7 image, you mean fedora 7 does not like to be a > DOMU? This does make any sense.The Fedora initrd on the Dom0 cannot be used to start xenu''s because the initrd is lacking xenblk and xennet. Basically, you can only use pygrub with the dom0 and unchanged initrd''s, which means that you can only run FC6 and/or F7 machines. As soon as you need to brung up other OSes (eg FC3 or RHEL4 or Centos or Debian), you will need a custom made initrd. Paul
On Wednesday 06 June 2007 12:00pm, Brian McDonald wrote:> -----Original Message----- > From: Markus Armbruster [mailto:armbru@redhat.com] > Sent: Wednesday, June 06, 2007 1:51 PM > To: Brian McDonald > Cc: fedora-xen@redhat.com > Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU > > "Brian McDonald" <brian.mcdonald@mcdees-specialties.com> writes: > > I am having problems getting a fedora7 domu running under my Centos5 Dom0 > > (this is a centos5 server no graphical interface) > > > > I followed the same steps to created the fedora 7 domu as I have for > > creating the cenots5 domu that I have on the same box. > > > > I downloaded the vmlinux and initrd from here > > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os >/ > > > images/xen/ > > > >>Wait a sec! You simply plunked kernel & initrd into your /boot? That > >>bypasses the scripts in the rpms, and you know, those are there for a > >>reason. Can you try installing kernel-xen with yum? > > You can not use yum if the operating system is not installed in the domU > This is a centos5 server that I am trying to load a fedora7 domUYes, you can. Loopback mount (or whatever) the F7 domU to /mnt/temp/ (or whatever), run "chroot /mnt/temp/" (as root) and then you can run yum and do all kinds of other things from within there. I haven''t tried this yet with F7 or C5, but I have gotten things working just fine to create F6 and SLES10 on RHEL5. -- Lamont Peterson <lamont@gurulabs.com> Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT''s.