Liang Yang
2006-Aug-24 17:49 UTC
[Xen-users] How to expose physical hard drives directly to HVM domain?
Hi, Do you know how to expose physical drives directly to Windows Guest Domain without using Dom0 Device Model, i.e. I want my Windows can directly access those hard drives without defining them in HVM config file? Thanks, Liang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Horn
2006-Aug-24 19:15 UTC
Re: [Xen-users] How to expose physical hard drives directly to HVM domain?
On Thu, Aug 24, 2006 at 10:49:16AM -0700, Liang Yang wrote:> Do you know how to expose physical drives directly to Windows Guest Domain > without using Dom0 Device Model, i.e. I want my Windows can directly access > those hard drives without defining them in HVM config file?Considered iscsi? Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Aug-24 20:19 UTC
Re: [Xen-users] How to expose physical hard drives directly to HVMdomain?
Hi Chris, You mean scsi, right? I don''t use scsi drives. I only used SATA or SAS hard drives. Anyone has idea to let Windows domain recognize these SATA/SAS drives directly? Liang ----- Original Message ----- From: "Christian Horn" <chorn@fluxcoil.net> To: "Liang Yang" <multisyncfe991@hotmail.com> Cc: <xen-users@lists.xensource.com> Sent: Thursday, August 24, 2006 12:15 PM Subject: Re: [Xen-users] How to expose physical hard drives directly to HVMdomain?> On Thu, Aug 24, 2006 at 10:49:16AM -0700, Liang Yang wrote: >> Do you know how to expose physical drives directly to Windows Guest >> Domain >> without using Dom0 Device Model, i.e. I want my Windows can directly >> access >> those hard drives without defining them in HVM config file? > > Considered iscsi? > > Christian > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Horn
2006-Aug-25 07:05 UTC
Re: [Xen-users] How to expose physical hard drives directly to HVMdomain?
On Thu, Aug 24, 2006 at 01:19:09PM -0700, Liang Yang wrote:> You mean scsi, right?No, its a protocoll that takes a disc in one place to make it available via network, and a client can grab it and offer it to the OS the client runs on. There are many ways to do this, iscsi is a way i know there is a client for windows. You got the hints you need, google how it works exactly and if it fits your needs. Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I just have a question about setting up domU, except the filesystem, do I need to create a swap partition for the domU? How to do it? Thanks, Liang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tim Wood
2006-Sep-07 18:58 UTC
Re: [Xen-users] Do I need to specify swap parition for domU?
You don''t need to setup a swap partition, but it is generally a good idea. If you are using file backed disk partitions, you can create one like so: dd if=/dev/zero of=vmSwapFile bs=1k seek=512k count=1 mkswap vmSwapFile That will make a 512 MB swap file named "vmSwapFile" On 9/7/06, Liang Yang <multisyncfe991@hotmail.com> wrote:> Hi, > > I just have a question about setting up domU, except the filesystem, do I > need to create a swap partition for the domU? How to do it? > > Thanks, > > Liang > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-07 19:05 UTC
Re: [Xen-users] Do I need to specify swap parition for domU?
Hi Tim, Thank you for your reply. However, I would like to use logic volumes directly instead of using file backed disk partition for swap partition. For example, I created two logic volumes, LogVol00 is reserved as the swap partition for domU (1GB)(I copied the whole RedHat filesystem to LogVol01 as the / for domU). But I don''t know how to specify LogVol00 in xen config file as the swap partition for domU. Could you shed more lights on this issue? Thanks, Liang ----- Original Message ----- From: "Tim Wood" <twwood@gmail.com> To: "Liang Yang" <multisyncfe991@hotmail.com> Cc: <xen-users@lists.xensource.com> Sent: Thursday, September 07, 2006 11:58 AM Subject: Re: [Xen-users] Do I need to specify swap parition for domU?> You don''t need to setup a swap partition, but it is generally a good idea. > > If you are using file backed disk partitions, you can create one like so: > > dd if=/dev/zero of=vmSwapFile bs=1k seek=512k count=1 > mkswap vmSwapFile > > That will make a 512 MB swap file named "vmSwapFile" > > On 9/7/06, Liang Yang <multisyncfe991@hotmail.com> wrote: >> Hi, >> >> I just have a question about setting up domU, except the filesystem, do I >> need to create a swap partition for the domU? How to do it? >> >> Thanks, >> >> Liang >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tim Wood
2006-Sep-07 19:20 UTC
Re: [Xen-users] Do I need to specify swap parition for domU?
I think you just need to add your swap volume to the config file with something like: disk = [''phy:vg/LogVol00,sda1,w'', ''phy:vg/LogVol00,sda2,w''] then you may have to add a line in your domU''s /etc/fstab file to mount the swap drive, ie: /dev/sda2 none swap sw 0 0 See the xen users manual for more info on setting up disks in teh config files: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03300000000000000000 good luck _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
specify the swap LV just like you did the root LV. As far as your guest knows, its a disk or partition just like another other LV you export. Then once you are in the DomU, add a swap line pointing to that disk in your /etc/fstab ie /dev/hda2 swap swap defaults 0 0 then just mkswap /dev/hda2 swapon -a Liang Yang wrote:> Hi Tim, > > Thank you for your reply. However, I would like to use logic volumes > directly instead of using file backed disk partition for swap > partition. For example, I created two logic volumes, LogVol00 is > reserved as the swap partition for domU (1GB)(I copied the whole > RedHat filesystem to LogVol01 as the / for domU). But I don''t know how > to specify LogVol00 in xen config file as the swap partition for domU. > > Could you shed more lights on this issue? > > Thanks, > > Liang > > ----- Original Message ----- From: "Tim Wood" <twwood@gmail.com> > To: "Liang Yang" <multisyncfe991@hotmail.com> > Cc: <xen-users@lists.xensource.com> > Sent: Thursday, September 07, 2006 11:58 AM > Subject: Re: [Xen-users] Do I need to specify swap parition for domU? > > >> You don''t need to setup a swap partition, but it is generally a good >> idea. >> >> If you are using file backed disk partitions, you can create one like >> so: >> >> dd if=/dev/zero of=vmSwapFile bs=1k seek=512k count=1 >> mkswap vmSwapFile >> >> That will make a 512 MB swap file named "vmSwapFile" >> >> On 9/7/06, Liang Yang <multisyncfe991@hotmail.com> wrote: >>> Hi, >>> >>> I just have a question about setting up domU, except the filesystem, >>> do I >>> need to create a swap partition for the domU? How to do it? >>> >>> Thanks, >>> >>> Liang >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-07 22:19 UTC
[Xen-users] Why is the size of vmlinuz-2.6-xen0 and vmlinuz-2.6-xen different?
Hi, I downloaded xen-3.0.2-2 source and did the following commands to build and install Xen. make world KERNELS="linux-2.6-xen0 linux-2.6-xenU" make install After the above commands are done, I got a vmlinuz-2.6.16-xen in /boot directory and the size of this file is 1547132, I get another two Xen-Linux kernel files in /tmp/xen-3.0.2-2/dist/install/boot directory. The size of vmlinuz-2.6.16-xen0 is 2277107 and the vmlinuz-2.6.16-xenU is 1235921. I understand vmlinuz-2.6.16-xenU should be smaller as no device drivers are included, but I don''t understand why the size of vmlinuz-2.6.16-xen0 and vmlinuz-2.6.16-xen is different. They should be same, right? Could you someone explain what the difference between the file vmlinuz-2.6.16-xen0 and vmlinuz-2.6.16-xen is? Thanks, Liang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-07 22:25 UTC
[Xen-users] Why is the size of vmlinuz-2.6-xen0 and vmlinuz-2.6-xen different?
Hi, I downloaded xen-3.0.2-2 source and did the following commands to build and install Xen. make world KERNELS="linux-2.6-xen0 linux-2.6-xenU" make install After the above commands are done, I got a vmlinuz-2.6.16-xen in /boot directory and the size of this file is 1547132, I get another two Xen-Linux kernel files in /tmp/xen-3.0.2-2/dist/install/boot directory. The size of vmlinuz-2.6.16-xen0 is 2277107 and the vmlinuz-2.6.16-xenU is 1235921. I understand vmlinuz-2.6.16-xenU should be smaller as no device drivers are included, but I don''t understand why the size of vmlinuz-2.6.16-xen0 and vmlinuz-2.6.16-xen is different. They should be same, right? Could you someone explain what the difference between the file vmlinuz-2.6.16-xen0 and vmlinuz-2.6.16-xen is? Thanks, Liang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-09 03:14 UTC
[Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
Hi,
I installed Xen 3.0.2 on RedHat Enterprise AS 4.4. Now I try to create domU
from dom0. I copied the whole filesystem of a RedHat to the logic volume
group (/dev/VG_Dom6_Linux/LogVol00) I created for domU. I then start the
domU kernel, however I got the following errors:
*****************Message when booting domU kernel***************************
..
..
..
INIT: version 2.85 booting
Welcome to Red Hat Enterprise Linux AS
Press ''I'' to enter interactive startup.
Starting udev: [ OK ]
Initializing hardware... storage network audio done[ OK ]
raidautorun: failed to open /dev/md0: 6
Configuring kernel parameters: [ OK ]
Setting clock (localtime): Fri Sep 8 19:41:07 MST 2006 [ OK ]
Setting hostname localhost.localdomain: [ OK ]
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VG_Dom6_Linux/LogVol00
fsck.ext3: /dev/VG_Dom6_Linux/LogVol00:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
No such file or directory while trying to open /dev/VG_Dom6_Linux/LogVol00
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
Login incorrect.
Give root password for maintenance
(or type Control-D to continue):
Here is the content of my domU config file:
kernel = "/boot/vmlinuz-2.6-xenU"
ramdisk = "/boot/initrd-2.6-xen.img"
memory = 512
name = "domain1"
extra = "3"
vif = [ ''bridge=xenbr0'' ]
dhcp = "dhcp"
disk = [''phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w'' ]
root = "/dev/sda1 ro"
Could anyone help me this? I got stuck for this issue for two days.
Thanks,
Liang
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Tom Z. Napierala
2006-Sep-10 15:34 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
Dnia Saturday 09 September 2006 04:14, Liang Yang napisał:> Hi, > > I installed Xen 3.0.2 on RedHat Enterprise AS 4.4. Now I try to create domU > from dom0. I copied the whole filesystem of a RedHat to the logic volume > group (/dev/VG_Dom6_Linux/LogVol00) I created for domU. I then start the > domU kernel, however I got the following errors:[...]> Checking root filesystem > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VG_Dom6_Linux/LogVol00 > fsck.ext3: /dev/VG_Dom6_Linux/LogVol00: > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > > No such file or directory while trying to open /dev/VG_Dom6_Linux/LogVol00 > [FAILED][...] Your DomU is trying to access logocal volume as root instrad of sda1.> > Here is the content of my domU config file: > kernel = "/boot/vmlinuz-2.6-xenU" > ramdisk = "/boot/initrd-2.6-xen.img" > memory = 512 > name = "domain1" > extra = "3" > vif = [ ''bridge=xenbr0'' ] > dhcp = "dhcp" > disk = [''phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w'' ] > root = "/dev/sda1 ro" >Check your DomU fstab. Regards, -- Tom Napierala DB Alliance Limited North Point House, New Mallow Road, Cork, Ireland The National Software Centre, Mahon, Cork, Ireland _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-10 23:24 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
Hi Tom, I can not even boot my domU, how can I check my domU fstab? Thanks, Liang ----- Original Message ----- From: "Tom Z. Napierala" <tom@dba.ie> To: <xen-users@lists.xensource.com> Sent: Sunday, September 10, 2006 8:34 AM Subject: Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4? Dnia Saturday 09 September 2006 04:14, Liang Yang napisał:> Hi, > > I installed Xen 3.0.2 on RedHat Enterprise AS 4.4. Now I try to create > domU > from dom0. I copied the whole filesystem of a RedHat to the logic volume > group (/dev/VG_Dom6_Linux/LogVol00) I created for domU. I then start the > domU kernel, however I got the following errors:[...]> Checking root filesystem > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VG_Dom6_Linux/LogVol00 > fsck.ext3: /dev/VG_Dom6_Linux/LogVol00: > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > > No such file or directory while trying to open /dev/VG_Dom6_Linux/LogVol00 > [FAILED][...] Your DomU is trying to access logocal volume as root instrad of sda1.> > Here is the content of my domU config file: > kernel = "/boot/vmlinuz-2.6-xenU" > ramdisk = "/boot/initrd-2.6-xen.img" > memory = 512 > name = "domain1" > extra = "3" > vif = [ ''bridge=xenbr0'' ] > dhcp = "dhcp" > disk = [''phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w'' ] > root = "/dev/sda1 ro" >Check your DomU fstab. Regards, -- Tom Napierala DB Alliance Limited North Point House, New Mallow Road, Cork, Ireland The National Software Centre, Mahon, Cork, Ireland _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Luke Crawford
2006-Sep-10 23:39 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
if you are using the partition-within-the-domU method that makes it difficult to mount it outside, make the problem domU the second disk in a good domU... you can boot the good domU and the mount the second disk and mess with it. On Sun, 10 Sep 2006, Liang Yang wrote:> Date: Sun, 10 Sep 2006 16:24:40 -0700 > From: Liang Yang <multisyncfe991@hotmail.com> > To: Tom Z. Napierala <tom@dba.ie>, xen-users@lists.xensource.com > Subject: Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4? > > Hi Tom, > > I can not even boot my domU, how can I check my domU fstab? > > Thanks, > > Liang > > ----- Original Message ----- From: "Tom Z. Napierala" <tom@dba.ie> > To: <xen-users@lists.xensource.com> > Sent: Sunday, September 10, 2006 8:34 AM > Subject: Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4? > > > Dnia Saturday 09 September 2006 04:14, Liang Yang napisał: >> Hi, >> >> I installed Xen 3.0.2 on RedHat Enterprise AS 4.4. Now I try to create >> domU >> from dom0. I copied the whole filesystem of a RedHat to the logic volume >> group (/dev/VG_Dom6_Linux/LogVol00) I created for domU. I then start >> the >> domU kernel, however I got the following errors: > > [...] > >> Checking root filesystem >> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VG_Dom6_Linux/LogVol00 >> fsck.ext3: /dev/VG_Dom6_Linux/LogVol00: >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the superblock >> is corrupt, and you might try running e2fsck with an alternate >> superblock: >> e2fsck -b 8193 <device> >> >> No such file or directory while trying to open >> /dev/VG_Dom6_Linux/LogVol00 >> [FAILED] > > [...] > > Your DomU is trying to access logocal volume as root instrad of sda1. > >> >> Here is the content of my domU config file: >> kernel = "/boot/vmlinuz-2.6-xenU" >> ramdisk = "/boot/initrd-2.6-xen.img" >> memory = 512 >> name = "domain1" >> extra = "3" >> vif = [ ''bridge=xenbr0'' ] >> dhcp = "dhcp" >> disk = [''phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w'' ] >> root = "/dev/sda1 ro" >> > Check your DomU fstab. > > Regards, > -- > Tom Napierala > DB Alliance Limited > North Point House, New Mallow Road, Cork, Ireland > The National Software Centre, Mahon, Cork, Ireland > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tom Brown
2006-Sep-11 00:54 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
On Sun, 10 Sep 2006, Luke Crawford wrote:> > > if you are using the partition-within-the-domU method that makes it difficult > to mount it outside, make the problem domU the second disk in a good domU... > you can boot the good domU and the mount the second disk and mess with it.The hvm install docs also covers this well.... there''s a -o offset parameter you can use for losetup... which will let you mount the partition from dom0 http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION04330000000000000000 that''s appendix a.3 Make the file system and install grub # ln -s /dev/loop0 /dev/loop # losetup /dev/loop0 hd.img # losetup -o 16384 /dev/loop1 hd.img ^-- MAGIC # mkfs.ext3 /dev/loop1 # mount /dev/loop1 /mnt # mkdir -p /mnt/boot/grub # cp /boot/grub/stage* /boot/grub/e2fs_stage1_5 /mnt/boot/grub # umount /mnt # grub grub> device (hd0) /dev/loop grub> root (hd0,0) grub> setup (hd0) grub> quit # rm /dev/loop # losetup -d /dev/loop0 # losetup -d /dev/loop1 The losetup option -o 16384 skips the partition table in the image file. It is the number of sectors times 512. We need /dev/loop because grub is expecting a disk device name, where name represents the entire disk and name1 represents the first partition. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tom Z. Napierala
2006-Sep-11 09:39 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
> Hi Tom, > > I can not even boot my domU, how can I check my domU fstab? > > Thanks, > > LiangAs far as I see, your partition is on LVM volume /dev/VG_Dom6_Linux/LogVol00 Under your Dom0 create temporary folder : # mkdir /mnt/temp then mount your partition there (assuming it''s ext3, if not, add -t option and appriopriate fs): #mount /dev/VG_Dom6_Linux/LogVol00 /mnt/temp -o defaults All contents will be available under /mnt/temp, so edit /mnt/temp/etc/fstab. That''s the simplest way. Don''t play with losetup, as you already have partition. Besides losetup is for file-based partitions. Regards, -- Tom Napierala DB Alliance Limited North Point House, New Mallow Road, Cork, Ireland The National Software Centre, Mahon, Cork, Ireland _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2006-Sep-11 16:20 UTC
Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
Hi Tom, Thank you very much. You are right, no need to play with losetup stuff, just mount the logic volume, edit fstab and it works. BTW, I found one weird thing: I heard RAMDISK is not required for domU, but it seems I have to add RAMDISK to my domU config file, otherwiese the domU will hang up when it is booting. Please see the message below, the domU booting hangs up after "Continuing..." Do you have any clue for this issue? (xen-friendly glibc is already installed) Thanks, Liang ----------------------Begin of Message---------------------------------------------- xen]# xm create domain1.xm -c Using config file "domain1.xm". Started domain domain1 Linux version 2.6.16-xen (root@localhost.localdomain) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Fri Sep 8 18:40:45 MST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020000000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. ACPI in unprivileged domain disabled IRQ lockup detection disabled Built 1 zonelists Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro 3 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 2666.662 MHz processor. Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-fb7fe000, maxmem 33ffe000 Memory: 514048k/532480k available (2250k kernel code, 9780k reserved, 708k data, 172k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5334.98 BogoMIPS (lpj=26674902) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: L3 cache: 4096K Checking ''hlt'' instruction... OK. Brought up 1 CPUs migration_cost=0 Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Subsystem revision 20060127 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. blkif_init: reqs=64, pages=704, mmap_vstart=0xdf800000 netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx Registering block device major 8 ide-floppy driver 0.99.newide usbmon: debugfs is not available usbcore: registered new driver libusual mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 8 NET: Registered protocol family 20 Using IPI No-Shortcut mode EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 172k freed Warning: unable to open an initial console. *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is ** ** slow. To ensure full performance you should ** ** install a ''xen-friendly'' (nosegneg) version of ** ** the library, or disable tls support by executing ** ** the following as root: ** ** mv /lib/tls /lib/tls.disabled ** ** Offending process: init (pid=1) ** *************************************************************** *************************************************************** Continuing... ----------------------End of Message---------------------------------------------- ----- Original Message ----- From: "Tom Z. Napierala" <tom@dba.ie> To: <xen-users@lists.xensource.com> Sent: Monday, September 11, 2006 2:39 AM Subject: Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?>> Hi Tom, >> >> I can not even boot my domU, how can I check my domU fstab? >> >> Thanks, >> >> Liang > > As far as I see, your partition is on LVM volume > /dev/VG_Dom6_Linux/LogVol00 > Under your Dom0 create temporary folder : > # mkdir /mnt/temp > then mount your partition there (assuming it''s ext3, if not, add -t option > and > appriopriate fs): > #mount /dev/VG_Dom6_Linux/LogVol00 /mnt/temp -o defaults > > All contents will be available under /mnt/temp, so edit > /mnt/temp/etc/fstab. > That''s the simplest way. Don''t play with losetup, as you already have > partition. Besides losetup is for file-based partitions. > > Regards, > -- > Tom Napierala > DB Alliance Limited > North Point House, New Mallow Road, Cork, Ireland > The National Software Centre, Mahon, Cork, Ireland > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users