[prev in list] [next in list] [prev in thread] [next in thread]
List: xen-users
Subject: [Xen-users] Passthrough NIC not connecting to guest or reporting cable unplugged.
From: "Marc Tousignant" <myrdhn () gmail ! com>
Date: 2019-06-20 13:09:49
Message-ID: 000001d52769$71d76ad0$55864070$ () gmail ! com
[Download RAW message or body]
This is a multipart message in MIME format.
[Attachment #2 (multipart/alternative)]
This is a multipart message in MIME format.
So apparently I am the only one having this issue, which is weird in and of
itself. But I have been having this issue since I attempted to go to 4.7
back in 2017, where it happened in 4.6 and 4.8 when I was trying to resolve
it. And it is still there in 4.10 now. My system ran fine on 4.5.
https://lists.gt.net/xen/users/458441
https://lists.gt.net/xen/users/549380
The dmesgs I provided in the second link above a few months ago, but no one
has responded.
I have new, if weird, info..
When the guest is started after a reboot of the box, there are no issues.
NIC passthrough works without issue.
When the guest is rebooted, actually told to reboot from within the guest
session. The domU restarts, and the NIC devices are not assigned??
When the guest is told to shutdown/power off, and then a new create of the
guest is performed from the host, the NIC devices are assigned. But then it
gets a bit weird.
* If the guest is Linux based, the NICs assigned and work properly.
One of my guests is a Sophos UTM being run virtually and assigned 2 physical
devices.
* If the guest is Windows based, the NICs are assigned, however they
report media state disconnected. One of my guests is a Windows 2012 server
and assigned 1 physical device.
The NIC I am assigning to pass through is a 4 port Intel 82580 card assigned
id's 04:00.0 to 04:00.3.
MarcT
[Attachment #5 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:181673363;
mso-list-type:hybrid;
mso-list-template-ids:-1856706058 67698689 67698691 67698693 67698689 67698691 \
67698693 67698689 67698691 67698693;} @list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" \
vlink="#954F72"><div class=WordSection1><p class=MsoNormal>So apparently I am the \
only one having this issue, which is weird in and of itself… But I have been \
having this issue since I attempted to go to 4.7 back in 2017, where it happened in \
4.6 and 4.8 when I was trying to resolve it. And it is still there in 4.10 now. My \
system ran fine on 4.5.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal><a href="https://lists.gt.net/xen/users/458441">https://lists.gt.net/xen/users/458441</a><o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a \
href="https://lists.gt.net/xen/users/549380">https://lists.gt.net/xen/users/549380</a><o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The dmesgs I provided in the \
second link above a few months ago, but no one has responded.<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have new, if weird, \
info..<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When \
the guest is started after a reboot of the box, there are no issues. NIC passthrough \
works without issue.<o:p></o:p></p><p class=MsoNormal>When the guest is rebooted, \
actually told to reboot from within the guest session. The domU restarts, and the NIC \
devices are not assigned??<o:p></o:p></p><p class=MsoNormal>When the guest is told to \
shutdown/power off, and then a new create of the guest is performed from the host, \
the NIC devices are assigned. But then it gets a bit weird.<o:p></o:p></p><ul \
style='margin-top:0in' type=disc><li class=MsoListParagraph \
style='margin-left:0in;mso-list:l0 level1 lfo1'>If the guest is Linux based, the NICs \
assigned and work properly. One of my guests is a Sophos UTM being run virtually and \
assigned 2 physical devices.<o:p></o:p></li><li class=MsoListParagraph \
style='margin-left:0in;mso-list:l0 level1 lfo1'>If the guest is Windows based, the \
NICs are assigned, however they report media state disconnected. One of my guests is \
a Windows 2012 server and assigned 1 physical device.<o:p></o:p></li></ul><p \
class=MsoNormal>The NIC I am assigning to pass through is a 4 port Intel 82580 card \
assigned id’s 04:00.0 to 04:00.3.<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal>MarcT<o:p></o:p></p></div></body></html>
[Attachment #6 (text/plain)]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic