Xen devel - Mar 2012 - linux-3.4-rc0 XENBUS: Device with no driver: device/vbd/51713

Hi Konrad,

I just tried linux-3.4-rc0 (linus his tree, last commit
f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your
tree pulled on top of that:

branch stable/for-ingo-3.4.v2     (required for dom0 to boot)
branch stable/for-jens-3.4
branch stable/for-jens-3.4-bugfixes

Hypervisor is xen-4.1.3-rc1-pre
linux 3.3 vanilla works fine

Booting dom0 goes fine, but PV-guests don''t work, it seems something
goed wrong with registrering the devices.
Which is kind of strange because i compiled the kernel with the same .config
(all xen stuff is compiled in, no modules).

Nothing else is changed in between, I also tried reverting some of the xen-front
patches but all to no avail .. do you have any suggestions ?

.config is attachted


This is on the guest console:

[    0.219507] TCP: cubic registered
[    0.219513] NET: Registered protocol family 17
[    0.219530] Bridge firewalling registered
[    0.219536] Ebtables v2.0 registered
[    0.219550] Registering the dns_resolver key type
[    0.219736] registered taskstats version 1
[    0.219748] XENBUS: Device with no driver: device/vbd/51713
[    0.219752] XENBUS: Device with no driver: device/vbd/51714
[    0.219757] XENBUS: Device with no driver: device/vif/0
[    0.219789]   Magic number: 1:252:3141
[    0.219840] console [netcon0] enabled
[    0.219844] netconsole: network logging started
[    0.219848] saa7134 ALSA driver for DMA sound loaded
[    0.219852] saa7134 ALSA: no saa7134 cards found
[    0.220222] Freeing unused kernel memory: 716k freed
Loading, please wait...
mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/xvda2 does not exist.  Dropping to a shell!


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

On Fri, Mar 30, 2012 at 10:52:51PM +0200, Sander Eikelenboom
wrote:
> Hi Konrad,
> 
> I just tried linux-3.4-rc0 (linus his tree, last commit
f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your
tree pulled on top of that:
> 
> branch stable/for-ingo-3.4.v2     (required for dom0 to boot)
> branch stable/for-jens-3.4
> branch stable/for-jens-3.4-bugfixes
> 
> Hypervisor is xen-4.1.3-rc1-pre
> linux 3.3 vanilla works fine
> 
> Booting dom0 goes fine, but PV-guests don''t work, it seems
something goed wrong with registrering the devices.
> Which is kind of strange because i compiled the kernel with the same
.config (all xen stuff is compiled in, no modules).
> 
> Nothing else is changed in between, I also tried reverting some of the
xen-front patches but all to no avail .. do you have any suggestions ?
Your .config looks right. Let me try it out as well. Thanks for reporting!
> 
> .config is attachted
> 
> 
> This is on the guest console:
> 
> [    0.219507] TCP: cubic registered
> [    0.219513] NET: Registered protocol family 17
> [    0.219530] Bridge firewalling registered
> [    0.219536] Ebtables v2.0 registered
> [    0.219550] Registering the dns_resolver key type
> [    0.219736] registered taskstats version 1
> [    0.219748] XENBUS: Device with no driver: device/vbd/51713
> [    0.219752] XENBUS: Device with no driver: device/vbd/51714
> [    0.219757] XENBUS: Device with no driver: device/vif/0
> [    0.219789]   Magic number: 1:252:3141
> [    0.219840] console [netcon0] enabled
> [    0.219844] netconsole: network logging started
> [    0.219848] saa7134 ALSA driver for DMA sound loaded
> [    0.219852] saa7134 ALSA: no saa7134 cards found
> [    0.220222] Freeing unused kernel memory: 716k freed
> Loading, please wait...
> mount: mounting none on /dev failed: No such device
> W: devtmpfs not available, falling back to tmpfs for /dev
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> done.
> Begin: Waiting for root file system ... done.
> Gave up waiting for root device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>    - Check rootdelay= (did the system wait long enough?)
>    - Check root= (did the system wait for the right device?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  /dev/xvda2 does not exist.  Dropping to a shell!

On Fri, Mar 30, 2012 at 10:52:51PM +0200, Sander Eikelenboom
wrote:
> Hi Konrad,
> 
> I just tried linux-3.4-rc0 (linus his tree, last commit
f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your
tree pulled on top of that:
> 
> branch stable/for-ingo-3.4.v2     (required for dom0 to boot)
> branch stable/for-jens-3.4
> branch stable/for-jens-3.4-bugfixes
> 
> Hypervisor is xen-4.1.3-rc1-pre
> linux 3.3 vanilla works fine
> 
> Booting dom0 goes fine, but PV-guests don''t work, it seems
something goed wrong with registrering the devices.
> Which is kind of strange because i compiled the kernel with the same
.config (all xen stuff is compiled in, no modules).
> 
> Nothing else is changed in between, I also tried reverting some of the
xen-front patches but all to no avail .. do you have any suggestions ?

I think you are hitting this bug (hadn''t yet stuck in my
for-jens-3.4-bugfixes branch):

commit 252e60f73b023bdbb7c82c05e2c3d97a1233bd9f
Author: Igor Mammedov <imammedo@redhat.com>
Date:   Tue Mar 27 19:31:08 2012 +0200

    xen: only check xen_platform_pci_unplug if hvm
    
    commit b9136d207f08
      xen: initialize platform-pci even if xen_emul_unplug=never
    
    breaks blkfront/netfront by not loading them because of
    xen_platform_pci_unplug=0 and it is never set for PV guest.
    
    Signed-off-by: Andrew Jones <drjones@redhat.com>
    Signed-off-by: Igor Mammedov <imammedo@redhat.com>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
index d5e1ab9..98cbeba 100644
--- a/drivers/block/xen-blkfront.c
+++ b/drivers/block/xen-blkfront.c
@@ -1475,7 +1475,7 @@ static int __init xlblk_init(void)
 	if (!xen_domain())
 		return -ENODEV;
 
-	if (!xen_platform_pci_unplug)
+	if (xen_hvm_domain() && !xen_platform_pci_unplug)
 		return -ENODEV;
 
 	if (register_blkdev(XENVBD_MAJOR, DEV_NAME)) {
diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c
index 663b32c..0ebbb19 100644
--- a/drivers/net/xen-netfront.c
+++ b/drivers/net/xen-netfront.c
@@ -1965,7 +1965,7 @@ static int __init netif_init(void)
 	if (xen_initial_domain())
 		return 0;
 
-	if (!xen_platform_pci_unplug)
+	if (xen_hvm_domain() && !xen_platform_pci_unplug)
 		return -ENODEV;
 
 	printk(KERN_INFO "Initialising Xen virtual ethernet driver.\n");

Saturday, March 31, 2012, 12:07:58 AM, you wrote:
> On Fri, Mar 30, 2012 at 10:52:51PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>> 
>> I just tried linux-3.4-rc0 (linus his tree, last commit
f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your
tree pulled on top of that:
>> 
>> branch stable/for-ingo-3.4.v2     (required for dom0 to boot)
>> branch stable/for-jens-3.4
>> branch stable/for-jens-3.4-bugfixes
>> 
>> Hypervisor is xen-4.1.3-rc1-pre
>> linux 3.3 vanilla works fine
>> 
>> Booting dom0 goes fine, but PV-guests don''t work, it seems
something goed wrong with registrering the devices.
>> Which is kind of strange because i compiled the kernel with the same
.config (all xen stuff is compiled in, no modules).
>> 
>> Nothing else is changed in between, I also tried reverting some of the
xen-front patches but all to no avail .. do you have any suggestions ?
> I think you are hitting this bug (hadn''t yet stuck in my
for-jens-3.4-bugfixes branch):
You were right as usual :-)
Boots fine with this extra patch !
Still seem to have some strange behavior, seems with pci-passthrough
i''m able to make network / ahci go berserk on dom-0 by booting the
3.4-rc0 kernel as guest and using the device.
But haven''t done enough tests to pinpoint anything. Will keep you
posted if i find anything.

Thx so far !
--
Sander
> commit 252e60f73b023bdbb7c82c05e2c3d97a1233bd9f
> Author: Igor Mammedov <imammedo@redhat.com>
> Date:   Tue Mar 27 19:31:08 2012 +0200
>     xen: only check xen_platform_pci_unplug if hvm
>     
>     commit b9136d207f08
>       xen: initialize platform-pci even if xen_emul_unplug=never
>     
>     breaks blkfront/netfront by not loading them because of
>     xen_platform_pci_unplug=0 and it is never set for PV guest.
>     
>     Signed-off-by: Andrew Jones <drjones@redhat.com>
>     Signed-off-by: Igor Mammedov <imammedo@redhat.com>
>     Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index d5e1ab9..98cbeba 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -1475,7 +1475,7 @@ static int __init xlblk_init(void)
>         if (!xen_domain())
>                 return -ENODEV;
>  
> -       if (!xen_platform_pci_unplug)
> +       if (xen_hvm_domain() && !xen_platform_pci_unplug)
>                 return -ENODEV;
>  
>         if (register_blkdev(XENVBD_MAJOR, DEV_NAME)) {
> diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c
> index 663b32c..0ebbb19 100644
> --- a/drivers/net/xen-netfront.c
> +++ b/drivers/net/xen-netfront.c
> @@ -1965,7 +1965,7 @@ static int __init netif_init(void)
>         if (xen_initial_domain())
>                 return 0;
>  
> -       if (!xen_platform_pci_unplug)
> +       if (xen_hvm_domain() && !xen_platform_pci_unplug)
>                 return -ENODEV;
>  
>         printk(KERN_INFO "Initialising Xen virtual ethernet
driver.\n");