[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN-4.1.0 2.6.39-gentoo Error: Device 768 (vbd) could not be connected



>> On Wed, Jul 13, 2011 at 9:56 AM,  <lionel@xxxxxxxxxxx> wrote:
>>> Hello
>>> since i've changed kernel from 2.6.34-xen to 2.6.39-gentoo i've got
>>> this
>>> problem. with 2.6.34-xen all is ok.
>>> linux # xm create virt
>>> Using config file "/etc/xen/virt".
>>> Error: Device 768 (vbd) could not be connected. Path closed or removed
>>> during hotplug add: backend/vbd/1/768 state: 1
>>> is that my config-related problem with 2.6.39-gentoo or udev problem?
>>>
>>
>> You should post your domU config file so that we can make suggestions.
>>
>> Thanks,
>> Todd
>>
> this is dom0 problem i suppose. i've changed only dom0 kernel.
> dom0 config is in attach
>>>
and in addition
when i'm trying to start 2.6.39-gentoo guest with 2.6.32-xen host i get
this in XEN dmesg:
(XEN) [2011-07-14 22:06:18] [VT-D]iommu.c:853: iommu_fault_status: Primary
Pending Fault
(XEN) [2011-07-14 22:06:18] [VT-D]iommu.c:828: DMAR:[DMA Write] Request
device [05:10.0] fault addr 0, iommu reg = ffff82c3fff57000
(XEN) [2011-07-14 22:06:18] DMAR:[fault reason 05h] PTE Write access is
not set
(XEN) [2011-07-14 22:06:18] print_vtd_entries: iommu = ffff8301bf61e5b0
bdf = 5:10.0 gmfn = 0
(XEN) [2011-07-14 22:06:18]     root_entry = ffff8301bf602000
(XEN) [2011-07-14 22:06:18]     root_entry[5] = 80f5001
(XEN) [2011-07-14 22:06:18]     context = ffff8300080f5000
(XEN) [2011-07-14 22:06:18]     context[80] = 102_51cb005
(XEN) [2011-07-14 22:06:18]     l4 = ffff8300051cb000
(XEN) [2011-07-14 22:06:18]     l4_index = 0
(XEN) [2011-07-14 22:06:18]     l4[0] = 51ca003
(XEN) [2011-07-14 22:06:18]     l3 = ffff8300051ca000
(XEN) [2011-07-14 22:06:18]     l3_index = 0
(XEN) [2011-07-14 22:06:18]     l3[0] = 51c9003
(XEN) [2011-07-14 22:06:18]     l2 = ffff8300051c9000
(XEN) [2011-07-14 22:06:18]     l2_index = 0
(XEN) [2011-07-14 22:06:18]     l2[0] = 51c8003
(XEN) [2011-07-14 22:06:18]     l1 = ffff8300051c8000
(XEN) [2011-07-14 22:06:18]     l1_index = 0
(XEN) [2011-07-14 22:06:18]     l1[0] = 0
(XEN) [2011-07-14 22:06:18]     l1[0] not present

and guest network doesn't work even if i destroy 2.6.39 guest and start
2.6.34-xen guest which is working ok. and it is until reboot, while system
hangs up and hardware reset reqired

>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>>
>>
>>
>>
>> --
>> Todd Deshane
>> http://www.linkedin.com/in/deshantm
>> http://www.xen.org/products/cloudxen.html
>> http://runningxen.com/
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>

Attachment: conf
Description: Binary data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.