Displaying 4 results from an estimated 4 matches for "new_dev".
Did you mean:
net_dev
2006 Aug 11
2
Subversion: 400 Bad request error
...e/jean/dev and then svn
update, it gives me this error:
bash-3.00$ cd ~/dev/sysadmin/
bash-3.00$ svn update
svn: REPORT request failed on '/svn/code/!svn/vcc/default'
svn: REPORT of '/svn/code/!svn/vcc/default': 400 Bad Request
(https://subversion)
bash-3.00$
bash-3.00$ cd /local/new_dev/sysadmin/
bash-3.00$ svn update
At revision 30009.
bash-3.00$
As you can see if I am still on centos and I create a /local on the
*local drive*, then I can check out code or documents there and do
everything else. Again, while I am on the nfs mounted dir it does not
works, once I get out of the...
2010 Jan 29
7
with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don''t own device"
testing,
uname -ri
2.6.33-rc5-4-xen x86_64
rpm -qa | grep -i Xen-4
xen-4.0.0_20873_01-29.1.x86_64
cat test.cfg
name = ''test''
builder = ''linux''
bootloader = ''/usr/lib/xen/boot/domUloader.py''
bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen''
disk = [
2010 Oct 25
0
Re: Re: Unable to pass device to IOMMU
...dDomainInfo.py", line
> 934, in pci_device_configure
> vdevfn = self.hvm_pci_device_insert(dev_config)
> File
> "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line
> 800, in hvm_pci_device_insert
> return self.hvm_pci_device_insert_dev(new_dev)
> File
> "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line
> 828, in hvm_pci_device_insert_dev
> raise VmError("Failed to assign device to IOMMU (%s)" % bdf_str)
> VmError: Failed to assign device to IOMMU
> (0000:0e:00.0@100,msitr...
2010 Sep 16
5
Unable to pass device to IOMMU
Hello,
I''m hoping someone may be able to push us in the right direction. I''m trying
to get one of our products to work with the current branch of Xen
(4.0/4.0.0) but I''m hitting a problem.
We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270
blades) this works great.
But when we upgrade to Xen 4.0/4.0.1 we get the following message when