WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [Fwd: Re: [Xen-users] Driver domain problem]

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Fwd: Re: [Xen-users] Driver domain problem]
From: Kevin Fox <Kevin.Fox@xxxxxxx>
Date: Thu, 14 Jul 2005 15:20:31 -0700
Delivery-date: Thu, 14 Jul 2005 22:19:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I think this may be a bug? Trying the devel list.

Kevin
--- Begin Message ---
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Driver domain problem
From: Kevin Fox <Kevin.Fox@xxxxxxx>
Date: Thu, 14 Jul 2005 11:28:02 -0700
In-reply-to: <1121270601.14928.14.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1121270601.14928.14.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I recompiled xen with make xen verbose=y debug=y debugger=y trace=y

And it still doesn't work, but the xm dmesg does give a little more info
then before:
(XEN) (file=extable.c, line=71) Pre-exception: fc53247e -> fc532534
(XEN) (file=traps.c, line=463) Page fault: fc532549 -> fc506fc0

Not too useful, but might give a clue.

Kevin

On Wed, 2005-07-13 at 09:03 -0700, Kevin Fox wrote:
> I'm trying to setup a xenU virtual machine that has a physical network
> card assigned to it and a virtual nic assigned to it. I've gotten the
> dom0 kernel to ignore the card but I have run into a problem. When I try
> to compile a xenU kernel with CONFIG_XEN_PHYSDEV_ACCESS, the kernel will
> no longer boot. If I remove the CONFIG_XEN_PHYSDEV_ACCESS, the kernel
> boots fine. It gets to the unpausing phase and then just disappears.
> Nothing in dmesg, xm dmesg, or on the console and the xm log is not very
> helpful either. I'm probably missing something important but can't find
> anything I'm missing. Any ideas? I'm running current xen stable 2.0.6.
> 
> Thanks,
> Kevin
> 
> Grub.conf stuff:
> title Xen 2.0.6 / XenLinux 2.6.11.10
>    kernel /boot/xen-2.0.6.gz dom0_mem=32768
> console=vgaphysdev_dom0_hide=(00:0c.0)
>    module /boot/vmlinuz-2.6.11.10-xen0 root=/dev/md0 ro
> 
> 
> xenU config:
> kernel = "/boot/vmlinuz-2.6.11.10-xenU"
> memory = 32
> nics=1
> pci = ['00,0c,0']
> disk = [ 'file:/images/fw1disk,sda1,w' ]
> root = "/dev/sda1 ro"
> extra = "4"
> 
> 
> xm log:
> [2005-07-09 19:20:18 xend] DEBUG (XendDomainInfo:720) init_domain>
> Created domain=6 name=FW1 memory=64
> [2005-07-09 19:20:18 xend] INFO (console:94) Created console id=13
> domain=6 port=9606
> [2005-07-09 19:20:18 xend] DEBUG (XendDomainInfo:1130) Creating vbd
> dom=6 uname=file:/images/fw1disk
> [2005-07-09 19:20:19 xend] DEBUG (blkif:155) Connecting blkif
> <BlkifBackendInterface 6 0>
> [2005-07-09 19:20:19 xend] DEBUG (XendDomainInfo:1107) Creating vif
> dom=6 vif=0 mac=aa:00:00:0c:52:cb
> [2005-07-09 19:20:19 xend] INFO (XendRoot:112) EVENT>
> xend.console.create [13, 6, 9606]
> [2005-07-09 19:20:19 xend] INFO (XendRoot:112) EVENT> xend.domain.create
> ['FW1', '6']
> [2005-07-09 19:20:19 xend] INFO (XendRoot:112) EVENT>
> xend.domain.unpause ['FW1', '6']
> [2005-07-09 19:20:20 xend] DEBUG (XendDomain:244) XendDomain>reap>
> domain died name=FW1 id=6
> [2005-07-09 19:20:20 xend] INFO (XendDomain:564) Destroying domain:
> name=FW1
> [2005-07-09 19:20:20 xend] DEBUG (XendDomainInfo:665) Destroying vifs
> for domain 6
> [2005-07-09 19:20:20 xend] DEBUG (netif:305) Destroying vif domain=6
> vif=0
> [2005-07-09 19:20:20 xend] DEBUG (XendDomainInfo:674) Destroying vbds
> for domain 6
> [2005-07-09 19:20:20 xend] DEBUG (blkif:552) Destroying blkif domain=6
> [2005-07-09 19:20:20 xend] DEBUG (blkif:408) Destroying vbd domain=6
> idx=0
> [2005-07-09 19:20:20 xend] DEBUG (XendDomainInfo:634) Closing console,
> domain 6
> [2005-07-09 19:20:20 xend] DEBUG (XendDomainInfo:622) Closing channel to
> domain 6
> [2005-07-09 19:20:20 xend] INFO (XendRoot:112) EVENT> xend.virq 4
> [2005-07-09 19:20:20 xend] DEBUG (blkif:363) Unbinding vbd (type file)
> from /dev/loop0
> [2005-07-09 19:20:20 xend] INFO (XendRoot:112) EVENT> xend.domain.exit
> ['FW1', '6', 'crash']
> [2005-07-09 19:20:20 xend] INFO (XendRoot:112) EVENT>
> xend.domain.destroy ['FW1', '6']
> [2005-07-09 19:20:21 xend] INFO (XendRoot:112) EVENT> xend.domain.died
> ['FW1', '6']
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--- End Message ---
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [Fwd: Re: [Xen-users] Driver domain problem], Kevin Fox <=