I''ve built Xen with the latest hg source pull, and I am not able to boot domU on my x86_64 boxes using configurations and setups that have previously worked. Has something changed since late last week that would require a change in my domU configuration file? When creating DomU, I get the following error message: VFS: Cannot open root device "sdb2" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) The file system for DomU is ext3, and I''ve made sure that it is built in xenU kernel. This are the xm dmesg lines displayed when error occurs: (XEN) (file=grant_table.c, line=1071) Grant unref rd(5) ld(0) frm(d485) flgs(0). (XEN) (file=traps.c, line=878) Non-priv domain attempted RDMSR(00000000c0000080,00020000,00020000). (XEN) (file=traps.c, line=870) Non-priv domain attempted WRMSR(00000000c0000100,00000000,00000000). (XEN) (file=traps.c, line=870) Non-priv domain attempted WRMSR(00000000c0000102,00000000,00000000). (XEN) (file=traps.c, line=878) Non-priv domain attempted RDMSR(00000000c0000080,00000000,00000000). stop_this_cpu disable_local_apic This is the domU configuration file: # Kernel image file. kernel = "/boot/vmlinuz-2.6-xenU" # Optional ramdisk. # ramdisk = "/boot/initrd-2.6.11.12-xenU" # The domain build function. Default is ''linux''. builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. # memory = 256 memory = 512 # A name for your domain. All domains must have different names. name = "vm1" disk = [ ''phy:sdb1,0811,w'',''phy:sdb2,0812,w'' ] # Set if you want dhcp to allocate the IP address. # vif = [ ''mac= AA:00:00:47:CB:34, bridge=xen-br0'' ] # Set if you want dhcp to allocate the IP address. #dhcp="dhcp" # Set netmask. #netmask = ''255.255.255.0'' # Set default gateway. # gateway = ''9.53.94.0'' # Set the hostname. # hostname= "vm%d" % vmid # Set root device. root = "/dev/sdb2 ro" # Sets runlevel 4. # extra = "4" #============= David F Barrera _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
So, I am not the only one, then. Thanks for your reply. David Robin van Leeuwen wrote:> I have the same here after last pull > > VFS: Cannot open root device "hda1" or unknown-block(0,0) > > only my hda1 maps to a ext3 on a lvm device... > > [Debian unstable/testing, last pull 22-08-05 18:00] > > > David F Barrera wrote: > >> I''ve built Xen with the latest hg source pull, and I am not able to >> boot domU on my x86_64 boxes using configurations and setups that >> have previously worked. Has something changed since late last week >> that would require a change in my domU configuration file? >> >> When creating DomU, I get the following error message: >> >> VFS: Cannot open root device "sdb2" or unknown-block(0,0) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> >> The file system for DomU is ext3, and I''ve made sure that it is built >> in xenU kernel. >> >> This are the xm dmesg lines displayed when error occurs: >> >> (XEN) (file=grant_table.c, line=1071) Grant unref rd(5) ld(0) >> frm(d485) flgs(0). >> (XEN) (file=traps.c, line=878) Non-priv domain attempted >> RDMSR(00000000c0000080,00020000,00020000). >> (XEN) (file=traps.c, line=870) Non-priv domain attempted >> WRMSR(00000000c0000100,00000000,00000000). >> (XEN) (file=traps.c, line=870) Non-priv domain attempted >> WRMSR(00000000c0000102,00000000,00000000). >> (XEN) (file=traps.c, line=878) Non-priv domain attempted >> RDMSR(00000000c0000080,00000000,00000000). >> stop_this_cpu disable_local_apic >> >> This is the domU configuration file: >> >> # Kernel image file. >> kernel = "/boot/vmlinuz-2.6-xenU" >> # Optional ramdisk. >> # ramdisk = "/boot/initrd-2.6.11.12-xenU" >> # The domain build function. Default is ''linux''. >> builder=''linux'' >> # Initial memory allocation (in megabytes) for the new domain. >> # memory = 256 >> memory = 512 >> # A name for your domain. All domains must have different names. >> name = "vm1" >> disk = [ ''phy:sdb1,0811,w'',''phy:sdb2,0812,w'' ] >> # Set if you want dhcp to allocate the IP address. >> # vif = [ ''mac= AA:00:00:47:CB:34, bridge=xen-br0'' ] >> # Set if you want dhcp to allocate the IP address. >> #dhcp="dhcp" >> # Set netmask. >> #netmask = ''255.255.255.0'' >> # Set default gateway. >> # gateway = ''9.53.94.0'' >> # Set the hostname. >> # hostname= "vm%d" % vmid >> >> >> # Set root device. >> root = "/dev/sdb2 ro" >> # Sets runlevel 4. >> # extra = "4" >> #=============>> >> David F Barrera >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh
2005-Aug-22 21:23 UTC
RE: [Xen-devel] x86_64 - Unable to boot DomU
I am also running into the same issue on the ES7000 and Dell x86_64 boxes running SLES9 SP2.> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of David F Barrera > Sent: Monday, August 22, 2005 5:23 PM > To: Robin van Leeuwen > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] x86_64 - Unable to boot DomU > > So, I am not the only one, then. Thanks for your reply. > > David > > Robin van Leeuwen wrote: > > > I have the same here after last pull > > > > VFS: Cannot open root device "hda1" or unknown-block(0,0) > > > > only my hda1 maps to a ext3 on a lvm device... > > > > [Debian unstable/testing, last pull 22-08-05 18:00] > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
To make the story more complete:
during the DomU boot it hangs for a while on:
Blkif frontend is using grant tables.
xen_blk: Initialising virtual block device driver
And then spits out:
xen_blk: Timeout connecting to device!
David F Barrera wrote:
> So, I am not the only one, then. Thanks for your reply.
>
> David
>
> Robin van Leeuwen wrote:
>
>> I have the same here after last pull
>>
>> VFS: Cannot open root device "hda1" or unknown-block(0,0)
>>
>> only my hda1 maps to a ext3 on a lvm device...
>>
>> [Debian unstable/testing, last pull 22-08-05 18:00]
>>
>>
>> David F Barrera wrote:
>>
>>> I''ve built Xen with the latest hg source pull, and I am
not able to
>>> boot domU on my x86_64 boxes using configurations and setups that
>>> have previously worked. Has something changed since late last week
>>> that would require a change in my domU configuration file?
>>>
>>> When creating DomU, I get the following error message:
>>>
>>> VFS: Cannot open root device "sdb2" or unknown-block(0,0)
>>> Please append a correct "root=" boot option
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(0,0)
>>>
>>> The file system for DomU is ext3, and I''ve made sure that
it is
>>> built in xenU kernel.
>>>
>>> This are the xm dmesg lines displayed when error occurs:
>>>
>>> (XEN) (file=grant_table.c, line=1071) Grant unref rd(5) ld(0)
>>> frm(d485) flgs(0).
>>> (XEN) (file=traps.c, line=878) Non-priv domain attempted
>>> RDMSR(00000000c0000080,00020000,00020000).
>>> (XEN) (file=traps.c, line=870) Non-priv domain attempted
>>> WRMSR(00000000c0000100,00000000,00000000).
>>> (XEN) (file=traps.c, line=870) Non-priv domain attempted
>>> WRMSR(00000000c0000102,00000000,00000000).
>>> (XEN) (file=traps.c, line=878) Non-priv domain attempted
>>> RDMSR(00000000c0000080,00000000,00000000).
>>> stop_this_cpu disable_local_apic
>>>
>>> This is the domU configuration file:
>>>
>>> # Kernel image file.
>>> kernel = "/boot/vmlinuz-2.6-xenU"
>>> # Optional ramdisk.
>>> # ramdisk = "/boot/initrd-2.6.11.12-xenU"
>>> # The domain build function. Default is ''linux''.
>>> builder=''linux''
>>> # Initial memory allocation (in megabytes) for the new domain.
>>> # memory = 256
>>> memory = 512
>>> # A name for your domain. All domains must have different names.
>>> name = "vm1"
>>> disk = [
''phy:sdb1,0811,w'',''phy:sdb2,0812,w'' ]
>>> # Set if you want dhcp to allocate the IP address.
>>> # vif = [ ''mac= AA:00:00:47:CB:34,
bridge=xen-br0'' ]
>>> # Set if you want dhcp to allocate the IP address.
>>> #dhcp="dhcp"
>>> # Set netmask.
>>> #netmask = ''255.255.255.0''
>>> # Set default gateway.
>>> # gateway = ''9.53.94.0''
>>> # Set the hostname.
>>> # hostname= "vm%d" % vmid
>>>
>>>
>>> # Set root device.
>>> root = "/dev/sdb2 ro"
>>> # Sets runlevel 4.
>>> # extra = "4"
>>> #=============>>>
>>> David F Barrera
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>>
>>
>>
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
I tested again this morning (8/23) using the following changeset, with the same results: changeset: 6328:b0d820178b8109f2d081e50920aac2c6b8273af6 tag: tip user: kaf24@firebug.cl.cam.ac.uk <mailto:kaf24@firebug.cl.cam.ac.uk> date: Tue Aug 23 04:49:12 2005 summary: This patch extends I/O APIC guest writes so that the correct destination Bugzilla # 176. (http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176) This is what is displayed on the serial console from the time that Dom0 comes up until I tried to create DomU. EXT3-fs: mounted filesystem with ordered data mode. store_evtchn = 14 XENBUS xs_read_watch: 0 (XEN) (file=traps.c, line=878) Non-priv domain attempted RDMSR(00000000c0000080,00020000,00020000). (XEN) (file=traps.c, line=870) Non-priv domain attempted WRMSR(00000000c0000100,00000000,00000000). (XEN) (file=traps.c, line=870) Non-priv domain attempted WRMSR(00000000c0000102,00000000,00000000). (XEN) (file=traps.c, line=878) Non-priv domain attempted RDMSR(00000000c0000080,00000000,00000000). stop_this_cpu disable_local_APIC (XEN) (file=grant_table.c, line=526) Bad handle (0). (XEN) (file=grant_table.c, line=1071) Grant unref rd(1) ld(0) frm(d4a2) flgs(0). This is the entire domU boot log: Started domain vm1 Linux version 2.6.12-xenU (root@bl2-10.ltc.austin.ibm.com <mailto:root@bl2-10.ltc.austin.ibm.com>) (gcc version 4.0.0 20050405 (Red Hat 4.0.0-0.40)) #1 SMP Tue Aug 23 08:23:02 CDT 2005 kernel direct mapping tables upto ffff880020000000 @ 800000-902000 Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000) Built 1 zonelists Kernel command line: root=/dev/sdb2 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) Xen reported: 3600.120 MHz processor. Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Memory: 504576k/524288k available (1574k kernel code, 9172k reserved, 528k data, 136k init) Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K CPU: Physical Processor ID: 3 Brought up 1 CPUs WARNING: 1 siblings found for CPU0, should be 2 NET: Registered protocol family 16 xen_mem: Initialising balloon driver. Grant table initialized IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ audit: initializing netlink socket (disabled) audit(1124805941.510:0): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. xen_blk: Initialising virtual block device driver xen_blk: Timeout connecting to device! Netdev frontend (TX) is using grant tables. Netdev frontend (RX) is using grant tables. xen_net: Initialising virtual ethernet driver. ���Bmd: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 32Kbytes TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "sdb2" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Robin van Leeuwen wrote:> To make the story more complete: > > during the DomU boot it hangs for a while on: > > Blkif frontend is using grant tables. > xen_blk: Initialising virtual block device driver > > And then spits out: > > xen_blk: Timeout connecting to device! > > > David F Barrera wrote: > >> So, I am not the only one, then. Thanks for your reply. >> >> David >> >> Robin van Leeuwen wrote: >> >>> I have the same here after last pull >>> >>> VFS: Cannot open root device "hda1" or unknown-block(0,0) >>> >>> only my hda1 maps to a ext3 on a lvm device... >>> >>> [Debian unstable/testing, last pull 22-08-05 18:00] >>> >>> >>> David F Barrera wrote: >>> >>>> I''ve built Xen with the latest hg source pull, and I am not able to >>>> boot domU on my x86_64 boxes using configurations and setups that >>>> have previously worked. Has something changed since late last week >>>> that would require a change in my domU configuration file? >>>> >>>> When creating DomU, I get the following error message: >>>> >>>> VFS: Cannot open root device "sdb2" or unknown-block(0,0) >>>> Please append a correct "root=" boot option >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown-block(0,0) >>>> >>>> The file system for DomU is ext3, and I''ve made sure that it is >>>> built in xenU kernel. >>>> >>>> This are the xm dmesg lines displayed when error occurs: >>>> >>>> (XEN) (file=grant_table.c, line=1071) Grant unref rd(5) ld(0) >>>> frm(d485) flgs(0). >>>> (XEN) (file=traps.c, line=878) Non-priv domain attempted >>>> RDMSR(00000000c0000080,00020000,00020000). >>>> (XEN) (file=traps.c, line=870) Non-priv domain attempted >>>> WRMSR(00000000c0000100,00000000,00000000). >>>> (XEN) (file=traps.c, line=870) Non-priv domain attempted >>>> WRMSR(00000000c0000102,00000000,00000000). >>>> (XEN) (file=traps.c, line=878) Non-priv domain attempted >>>> RDMSR(00000000c0000080,00000000,00000000). >>>> stop_this_cpu disable_local_apic >>>> >>>> This is the domU configuration file: >>>> >>>> # Kernel image file. >>>> kernel = "/boot/vmlinuz-2.6-xenU" >>>> # Optional ramdisk. >>>> # ramdisk = "/boot/initrd-2.6.11.12-xenU" >>>> # The domain build function. Default is ''linux''. >>>> builder=''linux'' >>>> # Initial memory allocation (in megabytes) for the new domain. >>>> # memory = 256 >>>> memory = 512 >>>> # A name for your domain. All domains must have different names. >>>> name = "vm1" >>>> disk = [ ''phy:sdb1,0811,w'',''phy:sdb2,0812,w'' ] >>>> # Set if you want dhcp to allocate the IP address. >>>> # vif = [ ''mac= AA:00:00:47:CB:34, bridge=xen-br0'' ] >>>> # Set if you want dhcp to allocate the IP address. >>>> #dhcp="dhcp" >>>> # Set netmask. >>>> #netmask = ''255.255.255.0'' >>>> # Set default gateway. >>>> # gateway = ''9.53.94.0'' >>>> # Set the hostname. >>>> # hostname= "vm%d" % vmid >>>> >>>> >>>> # Set root device. >>>> root = "/dev/sdb2 ro" >>>> # Sets runlevel 4. >>>> # extra = "4" >>>> #=============>>>> >>>> David F Barrera >>>> >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>> >>> >>> >>> >>> >>> >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel