Received Xen 4.3 yesterday on Ubuntu 13.10, switched to xl, and
everything works. Not sure that xm will work too (I tried a lot of
different configurations with xm/xl, but as I remember, it worked with
xm as well).
--
You received this bug notification because you are a member of Ubuntu
Server
Received Xen 4.3 yesterday on Ubuntu 13.10, switched to xl, and
everything works. Not sure that xm will work too (I tried a lot of
different configurations with xm/xl, but as I remember, it worked with
xm as well).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just to add my 2 cents, I also get this error when I try and pass though
a pci-e usb card or try to include the hdmi audio device from a ATI
Radeon HD 7770 on Raring. The pass through of 2 gfx to 2 different vms
works though, and pciback is used via an initscript.
(XEN) Xen version 4.2.1 (Ubuntu
Just to add my 2 cents, I also get this error when I try and pass though
a pci-e usb card or try to include the hdmi audio device from a ATI
Radeon HD 7770 on Raring. The pass through of 2 gfx to 2 different vms
works though, and pciback is used via an initscript.
(XEN) Xen version 4.2.1 (Ubuntu
I'm running LM 14 (= Ubuntu 12.10) and get the same error since xen
4.1.3-3ubuntu1.5.
NOTE: This is Xen 4.1 and I'm using the xm toolstack!
Here is the xm dmesg output (shortened):
(XEN) Xen version 4.1.3 (Ubuntu 4.1.3-3ubuntu1.7) (stefan.ba...@canonical.com)
(gcc version 4.7.2 (Ubuntu/Linaro
This bug appears also in xen 4.1 used in Quantal and Precise, one of
which is a LTS release affecting many users.
Would upgrading to Xen 4.1.5 stable fix this issue in Quantal and
Precise ? See https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1180396
One more thing: Considering the number of
Xen 4.1.2-2ubuntu2
When i am create vm with pci pass got this error
xm create win2008ex
Using config file ./win2008ex.
Error: (22, 'Invalid argument')
Have different servers ubuntu 12.04.2 this error
Security updates come ))) but )))
I'am still falback on 4.1.2-2ubuntu2.7 or
Still affected on Ubuntu 13.10 with version 4.2.1-2ubuntu2
Proposed solution didn't help, the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error: (22, 'Invalid
After last update 4.1.2-2ubuntu2.10 LTS version 12.04.02 is no longer affected.
All pci passtrough configurations are working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Well, I rushed last comment.
Error: (22, 'Invalid argument') still appears in LTS 4.1.2-2ubuntu2.10, but
only if I add Radeon HDA HDMI audio device.
It isn't nessessary, since Xen is adding it automatically, and then it works,
but listing it explicit in pci=['xx:xx.x'] is still causing bug to
So, for graphics card passtrough it is necessary to listing only one PCI
device, not two as before. Am I right?
Instead of
xen-pciback.hide=(04:00.0)(04:00.1)
only
xen-pciback.hide=(04:00.0)
right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nope, you have to hide both from kernel. It's just, that listing 04:00.1 in
config file is causing error. At least with xm stack.
Xen is attaching it anyway runtime, so it has to be hidden or you get does not
belong to pciback error.
BTW atm im passing pci=['01:00.0','00:1a.0','04:00.0'] to the
Ubuntu 12.04.02 LTS is also affected.
Bug was introduced in:
xen-hypervisor-4.1-amd64 4.1.2-2ubuntu2.8
and still present in latest 4.1.2-2ubuntu2.9.
Downgrading to 4.1.2-2ubuntu2.7 resolves the issue.
Possible solution is here:
http://xen.crc.id.au/bugs/view.php?id=5
but i couldn't compile
Misiek, mark, please, that this bug affects you too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error: (22, 'Invalid argument')
To manage notifications about this bug go to:
Latest Xen release, still affected by this bug!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error: (22, 'Invalid argument')
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xen (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error:
Same problem. 4.2.1-0ubuntu3 works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error: (22, 'Invalid argument')
To manage notifications about this bug go to:
The same on official ubuntu kernels 3.8/3.9 and compiled 3.10-rc1.
Ubuntu 13.10 affected too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175155
Title:
Error: (22, 'Invalid argument')
To manage
** Attachment added: Log file
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1175155/+attachment/3661465/+files/qemu-dm-windows8.log
** Description changed:
Error occured after yesterday update. After reboot I'm not able to start
virtual machine that works fine before.
Config and
** Description changed:
Error occured after yesterday update. After reboot I'm not able to start
virtual machine that works fine before.
Config and log in attachment.
Ubuntu 13.04, kernel 3.9.0-rc8
+ CPU AMD FX-8120
+
+ Downgrade from version 4.2.1-0ubuntu3.1 to 4.2.1-0ubuntu3 returns
20 matches
Mail list logo
