Re: [CentOS-virt] xen hvm domU and > 3 nic's... bug?

[Christoph]

It seems to be a problem with kernel... I use the kernel-ml there
(5.5.6)... with kernel from centos-virt repo (4.9.*) it works without
this problem...

---
--
Greetz

Am 27.02.2020 07:50, schrieb Christoph:

Hi

I cant start a hvm domU with more than 3 nic's configured... why? it is
a bug?
With previous versions it was possible...

here the config - it is an opnsense (openbsd) hvm domU:

name = "fenrir.chao5.int"
uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859"
maxmem = 2048
memory = 2048
loader = '/usr/lib64/xen/boot/hvmloader'
type = "hvm"
vcpus = 2
rtc_timeoffset = 0
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vnc = 1
vncunused = 0
vncdisplay = 100
vnclisten = "0.0.0.0"
keymap = "de"
vif = [
"mac=00:16:3e:05:30:04,bridge=xenbr5,script=vif-bridge,model=e1000",
"mac=00:16:3e:04:30:04,bridge=xenbr4,script=vif-bridge,model=e1000",
"mac=00:16:3e:15:30:04,bridge=xenbr15,script=vif-bridge,model=e1000",
"mac=00:16:3e:14:30:04,bridge=xenbr14,script=vif-bridge,model=e1000" ]
parallel = "none"
serial = "none"
disk = [ "phy:/dev/vg_lamia/lv_fenrir_root,hda,rw",
 "phy:/dev/vg_lamia/lv_fenrir_swap,hdb,rw" ]
pci_power_mgmt=1
xen_platform_pci=1
pci_msitranslate=1
viridian=0
hpet=1
acpi=1
apic=1
pae=1
pvh=1

with 3 nic's it does work...
--
--
Greetz
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] xen hvm domU and > 3 nic's... bug?

[Sarah Newman]

On 2/27/20 5:12 AM, Christoph wrote:

It seems to be a problem with kernel... I use the kernel-ml there
(5.5.6)... with kernel from centos-virt repo (4.9.*) it works without
this problem...


Have you made some pass to look for related problems on the xen-users or xen-devel mailing list or in the git commit history of mainline since 5.5.6 
was released?


If you can't find any evidence the bug has been reported or fixed already, I would encourage you to do so on the xen-devel mailing list since Linux 
4.9 won't be supported forever.


But in addition to the example configuration file, you may need to provide details about exactly what happens with 4 NICs to get a useful response. 
The output from running the xl create command, the kernel log, or the xen-hotplug log would likely contain more information.


--Sarah
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Question about latest CentOS 7 AWS AMI

[Edward Mossman]

Hi,

I'm seeing some strange behavior when trying to use the latest CentOS 7 AMI
from the AWS marketplace.

The AMI that we've been using previously is "ami-02eac2c0129f6376b"
released January 30, 2019 at 6:40:58 PM

Today I saw a new AMI with ID "ami-0c3b960f8440c7d71" that was released
February 21, 2020 at 3:50:07

Both these AMIs are owned by AWS account 67959241.

Before I was able to use the latest AMI released February 21, I was
prompted to subscribe to new marketplace terms and conditions. The link
that I received was an AWS marketplace page owned by a vendor named
"Supported Images" that seemed highly suspicious.

My questions are:

1. Did CentOS release an AWS AMI on February 21?
2. Has anything about the distribution of official CentOS AWS AMIs changed?
3. Is there a better channel for me to speak with someone involved in the
release process that might know more?

Thank you,
Edward Mossman

-- 
[image: Cloudreach] 
*Edward Mossman*
Cloud Systems Developer Tech Lead
+1 646 799 1311 <+1+646+799+1311> | +1 212 335 0700 | www.cloudreach.com
1095 Ave of the Americas – 14th Floor, 3 Bryant Park, New York, NY 10036
USA
[image: LinkedIn]  [image: Twitter]
 [image: Facebook]  [image:
Glassdoor]  [image: Instagram]

Cloudreach named in Gartner's Magic Quadrant for Managed Services


-- 
The above terms reflect a potential business arrangement, are provided 
solely as a basis for further discussion, and are not intended to be and do 
not constitute a legally binding obligation. No legally binding obligations 
will be created, implied, or inferred until an agreement in final form is 
executed in writing by all parties involved.


This email may be 
confidential or privileged. If you received this communication by mistake, 
please don't forward it to anyone else, please erase all copies and 
attachments, and please let us know that it has gone to the wrong person.



Cloudreach Inc. is registered in Delaware, with the registered office at 
1679 S. DuPont Highway, Suite 100, Dover, Kent, DE 19901 and registration 
number 5427661.
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt